Baby steps - cannot find remote

[jacobacci]

I ran into something I would like to get my head around.
The dCS Power Toggle code is not listed in the dCS IR codes document. However it exists in the Logitech profile.
So I learned it to the Apps button using the Harmony 950. I have posted the image here:
http://www.hifi-remote.com/forums/dload ... e_id=26860
I found that if I want to translate the learned code into a code for the functions tab, I need to take the OBC value in the Learned Signals Tab to be Hex, convert it from Hex to Decimal and then use that in the Functions Tab of the RMDU file.
Both the learned signal and the code I put into the RMDU work fine.
Is this correct?

[The Robman]

Close but not exactly. Your learned signal clearly shows the OBC is 12, no need to mess with the hex code. The other item that you need is the device code, which in this case is 20. So when you add this to your RMDU, you need to select the 20 device code and enter 12 as the OBC.

You will notice that RC-5 splits OBCs into those below 64 and those 64 and up, but the good news in your case is that all of your OBCs are under 64, so there's no need to worry about that.

[jacobacci]

It all jives now.
The dCS document lists the codes as hex.
Vol+ is 5000000000000001000D0010
0D being the device code (13)
10 (Hex) being the function code (16)

That's where my confusion came from, not from the learned codes.
I had tried Vol+ with 10 and that didn't work. Only when I looked at the other codes (some of which are obviously hex), did I get that I had to convert 10 (hex) to 16(dec).

It all works great now. A BIG THANKS to all who helped with Baby Steps

[The Robman]

It all jives now.
The dCS document lists the codes as hex.
Vol+ is 5000000000000001000D0010
0D being the device code (13)
10 (Hex) being the function code (16)

That's where my confusion came from, not from the learned codes.
I had tried Vol+ with 10 and that didn't work. Only when I looked at the other codes (some of which are obviously hex), did I get that I had to convert 10 (hex) to 16(dec).

It all works great now. A BIG THANKS to all who helped with Baby Steps

Yup, you got it, if you learn a signal using a JP1 remote, RMIR will give you the exact info that you need, there'll be no need to mess with hex codes. But if you get the data from other sources, it could be in any number of formats. In this case, you are correct that the "0D" portion of the data string is the device code in hex (and those 2 positions will be the device code for the other signals. The, and the "10" portion is the OBC in hex. Those same 2 positions will be the dev and OBC codes for all the other signals listed too.

[jacobacci]

My suggestion is to ask OfA what this file contains, as at present I have no idea what it is they are trying to give you. I would not suggest to them an alternative file type such as RMDU until we know more about what they are trying to provide.

I asked OfA and they came back asking what file format I would like instead. I asked them twice and they did not seem to want to give any further information on the content of the bin file.

Probably best to tell them to send an RMDU file. What do you think, Graham? Any other file format I could suggest?

Maybe this link helps?
https://www.youtube.com/watch?v=Ftji-iJyizs

[The Robman]

They're unlikely to be able to send an RMDU file, best you can probably expect is a setup code number (eg, DVD/1234) and a list of advanced codes (aka EFCs).