Hi, Barf --

Thanks to you and Charlie for this work. I'm trying to do the same thing and had gotten a bit of a start before coming across this thread. I decided, therefore, to validate my results against Charlie's.

It seems that IRScrutinizer's Render tab gives slightly different results depending on the presence of a padding zero. I get a third version of the code if I import the entire code sheet from a CSV to IRScrutinizer, then export it to a text file:

Import/Export Method
0000 0073 0000 000B 0020 0020 0040 0040 0020 0020 0040 0020 0020 0040 0040 0020 0020 0020 0020 0020 0020 0020 0020 0040 0020 0CA8

Render Device 19, Function 1 or 0x1
0000 0073 0000 000B 0020 0020 0040 0040 0040 0020 0020 0040 0020 0020 0040 0020 0020 0020 0020 0020 0020 0020 0020 0040 0020 0CA8

Render Device 19, Function 01 or 0x01
0000 0073 0000 000C 0020 0020 0020 0020 0020 0020 0040 0020 0020 0040 0020 0020 0040 0020 0020 0020 0020 0020 0020 0020 0020 0040 0020 0CA8

How do I rectify which is "most" correct? I don't have an MX-990 remote -- I'm preparing the codes for submission to Logitech for entry to the Harmony database and don't have a good way to test the codes before submission.

It seems Charlie used the "0x1" version, which yields different Pronto HEX than the "0x01" notation for all values below 0x10. Clearly, Charlie's codes work for him, so I'm inclined to follow his lead.

FWIW, The official IR code list from Trinnov's website provides them in the two-digit Hex format.

Thanks in advance,
Neil.