Most of the values in Pronto Hex are approximate durations, so slight changes in the numbers don't change the meaning at all. That is especially true of the last number. Even a much bigger change in the last number wouldn't change the meaning.

I guess we're using different versions of MakeHex. Occasionally I change the rounding rules or similar details in MakeHex because I find some obscure protocol where it matters. That tends to cause lots of tiny changes to the numbers in all the common protocols where such changes don't matter. Sorry for the confusion.


It is rarely correct to change anything other than the device number.

There might be a need to change T to be 1 instead of 0. RC5 has two versions of each signal. Changing T gets you the other version. The device won't accept the same version of the same signal twice in a row. If you need to use the same signal twice in a row in a macro, you may need to construct the two different versions of the signal to make that work. Of course you don't need that for discrete codes because you wouldn't want to use one twice in a row.

Other than Device and T, it is really rare to have reason to change something else in an IRP file.


I decode Pronto Hex with the JP1 version of IrTool.exe plus DecodeIr.dll
[Link: remotecentral.com]
[Link: john.fine.home.comcast.net]

With those I could see your two discretes were the same device and function but different values of T. So I knew they weren't really discretes, just sometimes acted like discretes (because sometimes the device will accept only the value of T that it didn't see last).

With those tools I also saw that the function number was 12. Almost all devices that use RC5 protocol use function 12 as their power toggle command.