On January 27, 2009 at 10:44, digitaltrader said...
Actually they all work. I made them by using a global
cache unit with the remote and the global cache ir sensor.
That indicates the global cache software doesn't correctly understand Pronto Hex in either direction. It writes Pronto Hex incorrectly, then ignore the error when reading it.
Most other software will fail to understand the Pronto Hex strings you posted.
I'm not sure if maybe I held the button a little too
long.
No, that is NOT the problem.
Any ideas on discretes?
Use MakeHex with protocol NEC1 and device=32.221 to create the full set of 256 possible signals and test each to see what it does.
If you want to decode your learned signals with IrTool or use them with a real Pronto or other software expecting correct Pronto Hex, you need to correct the header error:
0000 006D
0000 000A 0156 00A9 0016 0014 0016 0014 0016 0014 0016 0014 0016 0014 0015 003F 0016 0014 0016 0014 0015 003F 0016 0014 0015 003F 0015 003F 0015 003F 0016 0014 0015 003F 0015 003F 0016 0014 0016 0014 0016 0014 0016 0014 0015 003F 0016 0014 0016 0014 0016 0014 0015 003F 0015 003F 0015 003F 0015 003F 0016 0014 0015 003F 0015 003F 0015 003F 0015 0612 0151 0054 0016 0ECB
In each Pronto Hex string the 0000 000A that I marked above in red should be changed to 0022 0002
On January 27, 2009 at 05:23, Jasonvp said...
Do any of these work,
Those are from an entirely different code set.
Last edited by johnsfine
on January 27, 2009 11:38.