0000 006D 0000 000D 0022 0022 0044 0021 0022 0022 0022 0022 0022 0022 0022 0022 0022 0022 0022 0022 0022 0043 0022 0022 0022 0022 0022 0022 0022 0D56

0000 006D 0000 000B 0022 0022 0044 0021 0022 0022 0022 0022 0022 0022 0022 0022 0022 0022 0022 0043 0044 0021 0022 0043 0044 0D78

0000 006D 0000 000B 0022 0022 0044 0021 0022 0022 0022 0022 0022 0022 0022 0022 0022 0022 0022 0043 0044 0043 0044 0043 0022 0D56

0000 006D 0000 000C 0022 0022 0044 0021 0022 0022 0022 0022 0022 0022 0022 0022 0022 0022 0022 0043 0044 0021 0022 0043 0022 0022 0022 0D56

0000 006D 0000 000B 0022 0022 0044 0021 0022 0022 0022 0022 0022 0022 0022 0022 0022 0043 0044 0021 0022 0022 0022 0043 0044 0D78

0000 006D 0000 000C 0022 0022 0044 0021 0022 0022 0022 0022 0022 0022 0022 0022 0022 0043 0022 0022 0022 0022 0022 0022 0022 0022 0044 0D78

The signals you posted are RC5 protocol but at 38.4KHz instead of the usual 36KHz. I'm glad you posted the extra info, because learning often gets the wrong frequency, even as wrong as 36KHz to 38.4KHz.

I generated the above signals at 38KHz. No IR device actually cares about the difference between 38 and 38.4. It might care about the difference between ordinary RC5 at 36KHz and this device's RC5 at 38KHz.


I'm not sure, but I think that means it barely cares about frequency errors as big as 3.8, so it should work well all the way from 34.2KHz up to 41.8KHz.

Depending on the model of Pronto you have, you might get significantly better behavior from digits and maybe a few other functions if the Pronto is programmed to specifically know the signal is RC5 rather than using learned signals. But for discrete codes that isn't a consideration.

So the Pronto Hex I posted should be OK for discrete codes, but signals you already learned may work better (especially in macros) if you program them in ProntoEdit selecting RC5 protocol, System 0, and the correct command data for each signal. Your digits 1 to 3 have command data 6, 7 and 8. Power toggle is 5. Digits 4 to 9 probably have command data values 9 to 14. Digit 0 might be 15, but that is barely more than a guess.

If you program them that way, they would be at 36KHz instead of the learned frequency of 38.4, but I think that won't matter, while having the Pronto know it is RC5 (rather than a pure learned signal may matter).

See if a macro can tune channel 11 (or 22 or 33, etc.). If there is a problem doing so, that would be a symptom of the problems caused by using learned signals instead of having the Pronto know it is RC5.