On June 3, 2007 at 17:15, booya said...
I've read how the Pronto Hex codes for NEC codes can be
generated from MakeHex, so I tried it and generated the
required hex, and consequently the ccf file from hex2ccf.
However, none of the nec protocol versions I tried worked.
I probably blame it on my lack of understanding of what
should be entered in the Device field, is it the decimal
equivalent of 01FE (510) or 01 (1) or FE (254)?
Most likely 1. But maybe 128. Manufacturers aren't always consistent about how they represent this info in hex.
It should also be noted that there is already a pcf file
for the neuston found in the database but I do not have
any software that can read or convert it
I'll see if I can find the file you mean and get some Pronto Hex strings out of it with some version of ProntoEditNG. Those can be decoded with IrTool to tell us whether we're reading that documentation correctly.
That was easier than I expected. I got the file from
[Link: remotecentral.com]I opened it and grabbed the Pronto Hex for Play/Pause, which was
0000 006D 0026 0000 0155 00AC 0016 0040 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0040 0016 0040 0016 0040 0016 0040 0016 0040 0016 0040 0016 0040 0016 0016 0016 0040 0016 0040 0016 0016 0016 0016 0016 0016 0016 0040 0016 0016 0016 0040 0016 0016 0016 0016 0016 0040 0016 0040 0016 0040 0016 0016 0016 0040 0016 05EB 0155 0056 0016 0E55 0155 0056 0016 00AC
I decoded that with IRtool and it is NEC1 device 1, function 70. Looking in the Neuston documentation you linked, Play/Pause is function 0x46. 46 hex is 70 decimal, so everything is as expected.
None of that explains what went wrong when you tried MakeHex, but if you give more details, we probably can figure it out.
Last edited by johnsfine
on June 3, 2007 18:11.
