JP1 Remotes

[davecs]

If you download the files from the extenders page for these remotes (they're the same remote apart from the colour, except for a later version of the 7562), you get some instructions how to add an extender to it.

Trouble is, the "devices" you have to add cannot be added to RMIR, as the instructions are for IR.exe, and I can't see a way to interpret them for RMIR.

When I just built my Arduino-based interface for the old EEPROM type remotes, I thought I might resolve the issue by downloading the old remote. However, I must have had the remotes from before I started using this site, as there were only built-in codes and a couple of learns on them.

So if anyone can show me how to carry out these instructions using RMIR:

http://www.hifi-remote.com/forums/dload.php?action=category&cat_id=57

OR... if someone has a URC-7560 settings file which includes the extender, and can upload it, I could delete your devices and just leave the extender behind.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[davecs]

The Windows partition on my computer is rather neglected and doesn't seem to want to install drivers for either the Arduino or FD232 chip. So basically I can't use it to install anything using IR.exe 6.2. But what I did do, was to do a 981 reset on my 7562, download it to RMIR, and exported it was an .ir file. I got all the stuff relating to the 7562 extender, along with the ir file, and saved it onto a pendrive.

I was able to load the ir file into IR6.2, and successfully carry out all the steps to create the extended 7562 ir file. But when I went back to my Linux setup and tried to load it, into RMIR, it refused to load it, citing an error that there was no remote found with signature starting EBX0 with a 2k EEPROM.

Other errors have also occurred but the problem seems to be that RMIR doesn't like the EBX0EBV0 rdf supplied with the extender stuff, and that IR doesn't like the latest EBX0EBV0 file supplied with RMIR. As a result, an otherwise empty extended .ir file produced by IRv6.2 cannot be loaded into RMIR.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[mathdon]

[davecs]

After writing all this, I now think that the following two posts are the relevant ones. Who knew?

Where do I start?

1. Firstly, I did a 981 on the remote and downloaded it. This showed me it was "31" at byte 0009 in the raw data (new ROM).

2. It then tells me to save and make changes to the rmir file, which is easy enough. Even though the line start convention has changed, RMIR understands it and when you...

3. load the file back into RMIR the changes in the raw data look correct. However, there is no sign of the extender, for example, there is still space for learned signals.

4. Thanks for letting me know about the options on the advanced menu for RMDU. If I run RMDU from RMIR those options aren't there. I assume that I put in the Protocol at the same time as the first extender device as its PID is 0180 and the first two bytes of the device code as 80 01. However there is no option for "Device Type 4". (defaulted to Cable)

5. The other two don't appear to require protocol upgrades, the only problem being that there is no such device option as "Special". (tried to default to Cable which of course clashed so changed them to "OEM Mode"

6. Having saved the Device Upgrades as upgrade1.rmdu, upgrade2.rmdu and upgrade3.rmdu, I now add them to RMIR. Trouble is, RMIR is still using the unextended RDF and there appears to be no way to change it.

7. I uploaded to the remote. Definitely some action after pressing 10 + AV together, but nothing when I pressed 0 after that. No sign of the extender.

8. I downloaded it again, no sign of an extender being installed.

9. Second attempt, this time using New and starting with the Extender. The 31 at byte 0009 has become 30. Am I supposed to change it? Well, I did. Then I saved it as an RMIR file.

10. Repeat 2-7. Obviously RMIR is using the extended RDF file this time, but when I upload to the remote, this time it's totally dead. The only way I can bring it back to life is to upload the unextended file.

Hope that's all clear.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[davecs]

OK! I've got that it should have been 30 not 31. If you have the newer ROM (31) you need that information, but then the instructions should have read that you change it to 30. EBV0EBV1 > EBX0EBV0 — got that now.

The other issue is... the devices... what device types to allocate to the 3 extender devices? Solve that and I might have the solution!
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[davecs]

One more thing... the little adventure I had in Windows almost worked. I got the file I'd saved in Windows using ir.exe, and changed that 31 to 30 and opened it with RMIR. I only got this one error:

No device type alias found for Device Upgrade DevType4/0000. The device upgrade could not be imported and was discarded.

Special was changed to OEM Mode.

So if the equivalent to DevType4 can be established, I think we have liftoff!
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[The Robman]

Can you post your RMIR file and I'll try to follow the old instructions using RMIR instead and post the results.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

[davecs]

[davecs]

If you look in the RDF file, both the "Special" and "DevType4" types are changed to "OEM Mode", but Special/0000 and DevType4/0000 can't both be changed to OEM Mode/0000. I tried changing one to 0002 but that doesn't appear to do anything.

The other thing is that on the Special Functions tab, the New > Type pulldown is blank, so I can't allocate a Special Function.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[mathdon]

I believe I have this sorted. Please await a later post with full details. If I am right, I do not see how what he has posted could ever have worked, in either IR.exe or RMIR.
_________________
Graham

[mathdon]

Here are my instructions for installing the URC7560 extender with RMIR. I have tested them as far as possible with an empty setup created with File > New but of course cannot test whether the resulting setup actually works. Do please let me know.

[davecs]

[mathdon]

[mathdon]

Sorry, but it is not the original RDFs you need to change, it is the extender one. So you need to edit EBX0EBV0 (URC-7560_7562 Extender).rdf and in the [DeviceTypeAliases] section change the three OEM Mode entries to OEM Mode 1, OEM Mode 2, OEM Mode 3 for DevType4, DevType5, Special respectively.

If it works, I will fix the instructions tomorrow.
_________________
Graham

[davecs]

EDIT: Oops we crossed over....

1. If I don't change the 31 to 30 at byte 0009, in addition to the other instructions, I get this error:

No remote found with signature starting EXB0 and EEPROM size 2k

So I changed it to 30 and it loads.

2. Now I have RMIR open with the device EXB0EVB0.

3. Trying to add the first "device" and "protocol". The problem is that in "OEM Mode 1/0000" the OEM Mode 1 part is not recognised, no more than the DevType4 was, and RMDU changes it to "Cable". There is an OEM Mode, but not OEM Mode 1 or OEM Mode 3.

4. Trying to add the second and third "device", OEM Mode 3 isn't recognised either, any more than "Special" was, and is also converted to Cable. Now we have two devices that cannot co-exist, both Cable/0000.

So your revised instructions have had no effect, the outcome is exactly the same as the original set.

As I said, the instructions DO work in IR.exe 6.2, with the addition to change that rogue 31 to 30. The problem is that "Special" is changed to OEM Mode, but it doesn't know what to do with "DevType4", so doesn't accept it.

And yet you can assign DevType4 and Special to a device on the "general" page, but not in RMDU. And I think that holds the key to it.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661