JP1 Remotes

bt102 · Joined: 26 Nov 2023 Posts: 5

I have a Cogeco remote and the stickers on the inside of the battery compartment say urc-10566bc4.

A few years ago, I uploaded some jp1 stuff to it, and I forget the whole experience and don't remember what I did. So I go back to it now to make some changes and upload.

I create some new upgrades using the urc-1056 template. I then go to upload, and it says that the device signature does not match. I do a download from the remote, and the signature is 356801 which is a urc-2025. Then I recall one thing from years ago, and that was I had to use the urc-2025 template for the upgrades, in order to upload. I don't recall the details as to why I used the urc-2025 template, but I assume it was the only way to upload at that time without a signature mismatch.

So here are my questions in order of priority:

Is it possible to treat this remote as a urc-1056 and safely upload to it? The reason this is my top priority is that the urc-1056 allows key moves, plus it is easier to do upgrades using the the urc-1056 template because the keys/picture matches the remote. Doing the upgrades with the wrong picture is a pain. When I download from the remote and get a signature of 356801, is that cast-in-stone that it does have the guts of a urc-2025, or did my uploading years ago simply overwrite this signature, and I can safely go back to urc-1056 and overwrite it again?

At a lower priority, if the above is not possible, and I do need to treat this remote as a urc-2025, is there at least a way to get the correct picture/key-mapping of this remote so that upgrades are easier?

mathdon · Posted: Tue Nov 28, 2023 1:33 pm Post subject:

I cannot find URC-1056bc4 among the supported remotes in RMIR, but a user cannot overwrite the signature with an upload so you need to accept 356801 as the true signature of your remote. So it appears that the URC1056bc4 is internally the same as the URC-2025B2 while externally different. To get the correct picture/key-mapping it needs a new RDF created that has most of the entries the same as the URC-2025B2 but with a different map and image file. I see that Rob created the map for the URC-2025B2. Perhaps he would be prepared to do one for a URC-1056bc4 with the correct map and image.
_________________
Graham

bt102 · Joined: 26 Nov 2023 Posts: 5

mathdon · Posted: Thu Nov 30, 2023 4:43 pm Post subject:

You have done a lot of research, so you should be able to do this yourself without the need for "MapThis!". You seem to have missed the linkages between the files, so here they are:

1. RMIR reads the signature of the remote, from which it identifies all RDFs with that signature. If more than one then it asks the user to pick the right one.

2. The RDF has an ImageMap entry in the [General] section that gives the name of the map file.

3. The map file contains an entry for the name of the JPG image.

You need to make a copy of the 2025B2 RDF, renaming the name in brackets, and a copy of the 2025B2 map renamed as you wish. Change the ImageMap entry in the RDF copy to that of your renamed map. That should make all the linkages work. Then update the RDF and map copies as required.

I am writing this in haste and will give you more help if you need it, but you seem to have found enough for yourself that this may do. Good luck and let me know the outcome.
_________________
Graham

cba123 · Joined: 09 Aug 2015 Posts: 9

cba123 · Joined: 09 Aug 2015 Posts: 9

I managed to create a new RDF and Map file for the Atlas 1056B04 remote (by modifying the existing 2025b02 rdf file and 1056B03 map file). The map file reuses the existing image file Atlas OCAP PVR 3033 JP1.3 (Black).jpg

I uploaded the zip file into the RDF development sections.
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=26796

Hopefully, the files can be included in the next version of RMIR.

mathdon · Posted: Sat Dec 09, 2023 7:01 am Post subject:

bt102 · Joined: 26 Nov 2023 Posts: 5