JP1 Remotes

I have a UK(PAL) version of the slingbox and am using the latest version of Slingplayer (1.3.0.176).
I am trying to use a Thomson PVR for which I have downloaded the .rmdu file and loaded it into RM with the UEI RV chip remote selected. I re-allocate a few buttons that do not match, however when I try to use the resulting .bin file in slingplayer, the buttons - although using the correct protocol, do not issue the correct commands. For example the number button 3 switches the PVR to standby.
I have checked the button allocations and they all look OK. Does anyone have any idea where the mis-match might be?

Many thanks.

This is the link to the file that does not work: https://www.hifi-remote.com/forums/dload ... le_id=3565

OK, I have discovered how to get this to work. The problem was I used a rmdu file for the Thomson box I found in the archives.
When I decided to make a new file from scratch, I noticed that when I looked at the 'learned signals' I had downloaded from my URC-7562, that the hex cmds were shown as 'FC or FE' (example). Simply using the OBC code (as JP1 for beginners tells you to do) gives the wrong outputs. However by putting the alternative hex codes into RM solves the problem!!

This is the link to the file that does work: https://www.hifi-remote.com/forums/dload ... le_id=3566

Could you provide a link to the file in your first post?
Also, could you upload YOUR upgrade file and link to it?

It sounds like the protocol is not using the correct translation from OBC to hex, and an expert might need to look to see if any corrections are required in KM and/or RM.

Megaflash wrote: I looked at the 'learned signals' I had downloaded from my URC-7562, that the hex cmds were shown as 'FC or FE' (example). Simply using the OBC code (as JP1 for beginners tells you to do) gives the wrong outputs. However by putting the alternative hex codes into RM solves the problem!!

I'm confident those decoded OBC numbers are correct.

DecodeIR uses a guess about the protocol executor you might use in order to compute those hex cmds FROM those OBC numbers. If I understand you correctly, your testing confirms that DecodeIR's guess matches the executor in the Slingbox.

RM's failure to match that OBC to hex translation means either the .rdf file for that Slingbox is incorrect (lists the wrong varient for that PID) or the protocols.ini file has the wrong translation rules for the right varient.

I've added the links to the two files, I hope one of the experts will be able to see what the error is.

many thanks