Code translation bin to hex

[jfkispresident]

Hi Guys,

I am trying to create an update file for my Slingbox.

Status:
I've learned the Remote of my T-Home X 300T IPTV Receiver to an URC-7562.
I've already built a JP1 cable and successfully downloaded the learned codes to IR.

Now I'm stuck with the code transfer from IR to RM.
Unfortunately there are no Hex commands or OBC data. IR simply says:

Protocol: Phase-Encoded (RC-File)
Device: /
Subdevice: /
Hex Cmd: /
Misc: 19Bits, MSB value=1001100101001010100

Is there a "translation table" from the bin-code of IR to the categories of RM?

I feel like having lost track completely

Can you please help me out?

Thx, Jens

[Capn Trips]

When IR cannot decode your learned signals, the first recommendation is usually to ensure that you have the most recent version of decodeIR.dll in the same directory as IR.exe.

The second recommendation, only SLIGHTLY lagging the first, is to upload the IR file with your learned signals to the diagnosis area and post a link to it with your question. Someone is then more likely to diagnose it than guessing from what you have written.

[jfkispresident]

Thanks for the response.

I've added the IR-import file to the diagnosis area:

https://www.hifi-remote.com/forums/dload ... le_id=5428

The IPTV receiver is very similar in hard- and software to the Swisscom Bluewin device.

Maybe I can adapt slingbox files from there...

I keep testing. If you have any kind of suggestion, i'd appreciate!

[jfkispresident]

I've checked the decodeir.dll, the most current one is Version 2.36, the one I used.

...and some news: My slingbox accepts RV.bin for Swisscom Bluewin but does not react on remote commands.

What originally brought me to the idea of a translation table was this post:

https://www.hifi-remote.com/forums/viewt ... hlight=rc5

where there is a kind of transaltion of the bin-code to the categories of RM:

For example 0x1543
converted to binary, that is 1 0101 0100 0011
rearranged into RC5 fields it is 1 0 10101 000011

The last field (000011) is the OBC number (3).
The field before that (10101) is the device number (21).
The field before that (0) is the toggle bit (which is managed automatically by the RC5 protocol).
The field before that(1) is a strange feature of RC5. When it is 0, you must add 64 to the OBC number you got from the last field to get the true OBC number. But looking at the posted list of codes, it appears that never happens for this device.

I was just hoping that there may me a solution for my MSB value=1001100101001010100.

greetz, Jens

[Capn Trips]

I'm sure that you are right in the general approach. Unfortunately, we need an expert to weigh in at this point to solve this.