I have a list of RC5 codes for a Trinnov AVR that I am trying to convert to a hex string to use in my MX-990. Samples are below. I have looked at the Pronto-era programs on Remote Central such as IRScrutinizer, MakeHex, and RC5 to Hex, but don't have enough knowledge to make them work. Guidance would be greatly appreciated!

Address: 13h (group 19: Pre-Amp2)
button: code (standard RC5)
-------------------------------
Format left : 4Eh (linear function down) (new button)
Format right : 4Dh (linear function up) (new button)
1: 01h (1) => 1
2: 02h (2) => 2
3: 03h (3) => 3
4: 04h (4) => 4
5: 05h (5) => 5
6: 06h (6) => 6
7: 07h (7) => 7
8: 08h (8) => 8
9: 09h (9) => 9
10: 68h (10) => 104

--Charlie

Thank you for the lead to IRScrutinizer and the Render function. If I can impose further, I still need to know how to take the info I have - address, group, RC5 code, etc., and give IRScrutinizer what it is looking for as inputs - D and F (and others?). Could you show me how to do that, or point me to some documentation that would let me figure it out?

Thanks, again.

--Charlie

In IrScrutinizer: for the "Protocol", select "RC5" from the pull-down menu. In IrScrutinizer, that protocol has two parameters: D (device), and F (function). From the context, we conclude that


means that D=19 (or 13 in hexadecimal). It is the parameter that is constant for all commands. You can enter either form; using the prefix "0x" to indicate hecadecimal (as in the sceendump).

In the same way, the command number is the "F", enter as decimal or hexadecimal as you like. After entering protocol and parameter values, just press "Render". (Earlier versons said "Generate" instead of "Render".)

(Strictly speaking, there is a toggle parameter ("T") too, but for most purposes, you can just ignore it.)

The full manual is available here: [Link: harctoolbox.org]

Thanks again for the explanation, but I cannot get the results you show in your screenshot, even though I am using what appears to be the same version of IRScrutinizer.  My screenshot is attached.  Can you tell me where I might be going wrong?

Sorry, my screenshot did not come out very clear. The result shown is:

Freq=36000Hz[][+1778,-889,+889,-1778,+1778,-889,+889,-1778,+889,-889,+889,-889,+1778,-1778,+1778,-889,+889,-889,+889,-90886][]

Select Options (in the top row)-> Output text format and make sure "Pronto Hex" is selected.

Thank you - it works perfectly! (I never would have gotten there without your assistance.) As a reference for Trinnov users wanting to try this, I have posted two of the hex codes rendered by IRScrutinizer, which I can confirm work on the Trinnov when pasted into the URC Universal Browser.

Preset 1: 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

Preset 2: 0000 0073 0000 000A 0020 0020 0040 0040 0040 0020 0020 0040 0020 0020 0040 0020 0020 0020 0020 0020 0020 0040 0040 0CC8

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.

If a parameter value on the Render pane starts with a leading 0, it is interpreted as an octal number.


The best, "most correct" format is the one with parameters, D and F. One reason is that the RC5 format toggles, so there is not one but two rendered form of a signal given by D and F. (For T=0 and T=1 respectively.)


Sorry, I cannot make sense of that statement.

So, if I understand correctly, "1" will be read as decimal and "01" as octal?


This explains the problem I am seeing -- for many of the codes, I was seeing a different T value from Charlie. It seems that the renderer shifts from T=0 to T=1 if you click "Render" another time with the same input. Do I have this right?

How does the T value affect the behaviour of the IR code?

Hi, Charlie --

Are you using an AL16 or an AL32? I submitted your Pronto code set to Logitech for my Harmony remote.

For some reason, my Altitude16 switches inputs, instead of presets, in response to the codes.

I'm trying to troubleshoot this.

Thanks,
Neil.

Exactly. Possibly better example: "10" will be read as 10, "010" as 8, and "0x10" as 16.


That was to be expected.


Yes, it is the intended behavior with T left blank. You can of course also fill in a T value explicitly (talking about the "Render" pane).


It is used to tell a long keypress from a repeated key press of the same button. Unless the toggling is working (meaning that you really have two hexes for every key), you may not be able to (e.g.) turn a TV to channel 11.

Understood. Thanks again for your help.

thanks