JP1 Remotes

Agreed.The problem is that the titles of the RDF and signatures from the remote make it difficult to select the correct one when doing an upgrade in RM.
One example. When I attempt to download from one of the JP1.3 remotes, IR asks me to choose the remote from 2 different 30003000 titles, neither one of which I can get to use in RM to create upgrades. After choosing one (either one) IR returns an error message that the fixed data in $200 does not match. Is this an RDF issue?
Also, after doing an upgrade using the Atlas JP1.3 definition available in RM, IR returns an error message saying that the signatures don't match.

I guess I should remove the [FixedData] section from these remotes as it is unlikely the data here will match between different cable company remotes.

I've also changed the RDF Name to have 3000 or 3033 inside it so when RM displays it, it'll be unique(i.e. Atlas 5-Device PVR Day 3000 JP1.3 and Atlas 5-Device PVR Day 3033 JP1.3).

I've uploaded new RDF's for 30003000 here and for 30333033 here.

You should have only one 30003000 and one 30333033 RDF in your RDF folder so IR shouldn't have to ask you to choose an RDF. You should delete the old ones.

speaker.guy wrote:Agreed.The problem is that the titles of the RDF and signatures from the remote make it difficult to select the correct one when doing an upgrade in RM.
One example. When I attempt to download from one of the JP1.3 remotes, IR asks me to choose the remote from 2 different 30003000 titles, neither one of which I can get to use in RM to create upgrades. After choosing one (either one) IR returns an error message that the fixed data in $200 does not match. Is this an RDF issue?
Also, after doing an upgrade using the Atlas JP1.3 definition available in RM, IR returns an error message saying that the signatures don't match.

Sounds like you have old "straggler" rdf's floating around in your rdf folder. Do a detailed scrub of the folder and find every iteration of any rdf that has those sigs (30003000 and 30333033). Delete all of them and then add the two latest versions that Binky linked to above. Then IR should find only ONE matching sig when you download from the remote, and that is the sig you should use when building RM files.

I will let you know tomorrow....

Sleeoing on it raises a question. The ones marked JP1(3 of the new 7, and the eight other ones that have been defying me for 2 weeks): Is it possible that these are JP1.1, which might not be compatible with my DIY cable (pure JP1.2)???

I went back in this morning (at 5:30AM) and edited my JP1 directory (which contains ALL of my JP1 programs and files) to get only the current rdf(s) for the atlas remotes, RM is still presenting me with a strange list of remotes which seem to have no relationship to what is in that directory. It is referred to as "available remotes". Where does that come from and how do I get to the current rdf (s) in my JP1 directory?
To clarify this, the first 8 entries in the remotes pull down menu are:
12
3000-
3033-
Anthem
Arcam CR80
Atlas 4-device
Atlas 5-device PVR Day (NOTE) This is the 10251025 that works
Atlad PVR/DVR 5-device

This is all I see that may be applicable....

Some progress. Was able to successfully program the JP1.2 version using 10251025. I still can't get the newly downloaded 30003000 rdf to show up in RM, so I can't try the JP1.3, and as I said before, I suspect the JP1 marked remotes may well be JP1.1 and I can't do those with the cable (DIY) I have.

RM builds the list of available remotes from the RDF file names.
You can see what directory RM loads the RDFs from on the About panel (Help -> About).

If you want to change it, you can edit the entry for RDFPath in the RemoteMaster.properties file.

Thank you. "About" panel says C:/JP1 where I expect them to be. Unfortunately, the list in RM has no relationship to the rdf file names in the JP1 directory!

You should probably create a separate subdirectory C:\JP1\RDF to only contain the RDFs. Edit RemoteMaster.properties to point to this new folder. In my list of Atlas Remotes, RM displays The Windows filenames are Your list of Remotes seems to imply your filenames may be misnamed.

I will try that.
Anyplace I can lay my hands on a JP1.1 compatible cable quick?
BTW:Rob has the remote now, and Binky and Kupkai will each have one in a couple of days, so maybe one of them can provide an answer before I can!

There definitely is a relationship between the RDF file names and the remote names as listed by RM.

A properly names RDF file has a file name of the form

<signature> (<display name>).rdf

where

• the bold parts (parens and extension) are required and used as delimeters for parsing.
• <signature> is the remote's signature, which is NOT displayed by RM
• <display name> is the name displayed by RM. If the display name contains underscores (_), RM assumes the RDF refers to multiple remotes, and will generate multiple entries in the list for a single RDF. For example, the RDF HUD0HUD0 (URC-9800_8800_8780 Producer 8).rdf produces the entries
  • URC-9800 Producer 8
  • URC-8800 Producer 8
  • URC-8780 Producer 8

Note that RM searches for RDF files at startup, so if you change the files in the RDF directory while RM is running, it will not detect the changes. You must stop and restart RM to handle that.

OK. I created a new directory with RM1.79 installed and deliberately put an abbreviated group of rdf I use in that directory. Opened RM and still get a different, longer list of remotes. About panel points to the correct directory. If I go into Options/remotes, I get a list of available remotes which still bears no relationship to what is in my home directory!

Your list of Remotes seems to imply your filenames may be misnamed

I never touched any of those names. They are as they were downloaded.

What directory does RM say it is using for RDFs?

What are the RDF files in that directory?

What is the list of remotes that RM displays?