Jason answered well enough, but I'll add some detail anyway.
On January 18, 2009 at 05:16, laurent_michel said...
I believe these are 4 HEX digits = 16 bits codes ...
Actually they are 8 bit function numbers with another 8 bits as a check byte. That is typical.
I've been through all Makehex formats, and they all use
a 8 bits "function" code.
MakeHex can use over 8 bits for function and a few .irp files do. But when there is a check byte, the .irp file includes the logic to compute its value.
Shall i use the device code
for the first 8 bits ?
They didn't tell you the device code, nor the protocol, which would be a problem if you didn't have Pronto Hex for some signal of the same device
On January 18, 2009 at 06:40, laurent_michel said...
Below a learned code that works with my U5-112, that's
the "Power OFF" discrete code :
Does it work as a "power off" or a "power toggle"?
I don't have decode software handy. I trust Jason's decode of that as function 20, which matches what you posted first as "power", not as "off".
On January 18, 2009 at 08:23, Jasonvp said...
Protocol: NEC1
Device:134.21
So if you use MakeHex, you would use nec1.irp and set device=134.21
Up 5E A1 = 94
In each of those codes the first byte (such as 5E) is the function number in hex. Convert that to decimal to get the function number used with MakeHex. 5E hex is 94 decimal. Ignore the second byte (A1). If you care the second byte is always FF hex minus the first byte (FF minus 5E equals A1).
