That must mean there is some bug in the software the Control 4 system uses for importing Pronto Hex.
Possibly some tiny difference in the Pronto Hex that wouldn't matter to a real Pronto is triggering that bug.
Post some samples of Pronto Hex that can be correctly imported into the Control 4 and maybe we will be able to guess what aspect of the Pronto Hex is confusing it.
The MakeHex program, that I think Jason used, is very adjustable and can produce the right Pronto Hex if we can figure out what Pronto Hex the Control 4 understands.
BTW, when you copied the Pronto Hex from Jason's post, I hope you understood the actual Pronto Hex string starts with the 0000. Everything before the 0000 is human readable labeling, not part of the Pronto Hex.
Also, it is possible that your browser and/or the method you use to copy/paste from the forum is changing the Pronto Hex string.
In the original string there is a single blank between each set of four hex digits. Where your browser shows you a line break within the string, there is no actual line break just an ordinary blank.
If the copy/paste process changes that visible line break into an actual line break, that might confuse a program that you paste the Pronto Hex into (or it might not care. It depends on how that program was coded).
Last edited by johnsfine on August 19, 2009 15:28.