JP1 Remotes

Thanks Rob for the explanation, it's clear now.

Hi,

Thanks for this modification, I can now assign any of the 5 codes (2000 to 2004) to the SAT button by the normal procedure on the remote (of course not all at a time on the same button !).

For my understanding, could you explain the principle of what you did ?
Did you change the group of the ...

Hi Rob,
Here is the RMIR with the 5 upgrades:
http://www.hifi-remote.com/forums/dload ... e_id=26030

Could you please be so kind to explain me how you fixed this file to make possible to assign these 5 setup codes to the SAT button.

Thanks in advance and kind regards,

Hervé

Please understand that these are not restrictions that we chose to program into RMIR, these are restrictions that are in the remote itself. When UEI creates these remotes, they create different keymaps for each device type and I don't know the thought process that goes into which buttons they ...

Hi Rob,
Thanks for the clarification, it works OK if I use DVD instead of SAT for example.

But it was absolutely not obvious that (only) the cable/SAT type of devices had a "keymove preallocation" to these 3 buttons ...
And I really don't see the purpose of this (besides drawbacks).

It's not the ...

Hi Rob,
Thanks for your answer however it does not work, if I remove these buttons I remove the function but the (unused) button stays with an asterisk and if I want to reuse it it will have a keymove.
I made a factory reset, and even if I add an upgrade which dont use these 3 buttons, the asterisk ...

Hi,
I made some device upgrades for my URC-7950 remote and I discovered that 3 buttons (REC, >>|, |<<) are followed with an asterisk (*) which means that they carry a keymove.

I did not want these keymoves and I don't know from where they come, but more annoyingly I did not find a means to remove ...

I recently bought this very cheap USB <-> UART adapter, it works perfectly with RMIR.
The only point is that RTS is not available on the main 6 pins connector (only DTR is available in addition to TXD and RXD on this connector) but it is available as one of the 8 additional signals (holes on the ...

Since there was no [NEC1 (no repeats)] entry in my protocols.ini file
Yes there is. The no-repeats entries are all together at the end of the file. That one is at line 6060. As I have said before, you have to check that the menu item "Options > Show Slingbox protocols " is checked, and if it is ...

Sure...

Step 1: go to your RM folder and look for a file called protocols.ini
Step 2: open it using Notepad and search for [NEC1 (no repeats)]
Step 3: replace the entry with the one I gave earlier, and save the file
Step 4: re-start RMIR and open your current RMIR file
Step 5: go to Devices ...

Thanks Rob for this entry however, to be honest, I don't really understand how to use it...

I tried to include in an existing RMU file for the Teox with setup code 2002 (modifying the NEC address from FF00 to 9F60) but it produces a code with NEC address FF00 with repeats....

So could you explain ...

URC-8350 has signature 11691169 and that means it is a HCS08 processor. Thanks 3FG for this info.
But do you know a possible reason why there is a timeout error with the GetCPUtype function ?

Edit: I do not find the HCS08 in the "dump" list of processors.
Might this be the reason of this problem ?

The URC-1580 uses an S3F8 processor with a JP1.4 interface. Just load one of your files (or download the remote) and open the Raw Data tab. There is various info about the remote there, as well as the raw data panel itself.

The NEC no repeats protocol should be supported by the remote. Check that ...

split from: http://www.hifi-remote.com/forums/viewtopic.php?t=102488

Dear Rob,
As you know I tried to add an RMDU with the NEC no repeats protocol on my URC-8350 and it was not possible, you told me that it's probably because the processor is not an S3F8.
So I tried to find which processor it uses ...

How do you know it worked before if the device buttons were locked? Hi Rob,
With your initial RDF the buttons to which new setup codes were allocated by RMIR were locked (impossible to modify the setup code on the remote itself after that), then you provided a second RDF where they were not locked ...