Edit an RDF file

If you have a new remote that isn't recognized by RMIR, post the details here so we can help create a new RDF for it. Or, if there is an issue with an existing RDF or map, this is the place.
Post Reply
petehouk
Posts: 14
Joined: Sun Feb 22, 2015 7:46 am

Edit an RDF file

Post by petehouk »

I am trying to load the Ortev VRC-1100 upgrade to my RCA RCRP05B. There's a note on the page for the file download that says that I need to edit the RDF.

How do I edit that? I opened the file with Remotemaster and all of the fields that show "01ED" are grayed out and can't be edited.

Link to upgrade file:
http://www.hifi-remote.com/forums/dload ... e_id=10469
mdavej
Expert
Posts: 4631
Joined: Wed Oct 08, 2003 7:08 am

Post by mdavej »

Notepad
petehouk
Posts: 14
Joined: Sun Feb 22, 2015 7:46 am

Post by petehouk »

I did try opening it in notepad. I didn't see "01ED" in there. I did see "01 ED".

So should I replace "01 ED" with "01 ED:uei"?
petehouk
Posts: 14
Joined: Sun Feb 22, 2015 7:46 am

Post by petehouk »

I tried changing this line

Protocol=01 ED

to

Protocol=01ED:uei

and then to

Protocol=01 ED:uei

But it didn't work either way. I modified the file, then went to the "devices" tab of RMIR and then pressed the "open" button. I loaded the modified RDMU file, but it never loads the data into the device upgrade editor window. If I use the original line

Protocol=01 ED

then it will load into the upgrade editor window but when I upload to my remote the functions don't work.
3FG
Expert
Posts: 3434
Joined: Mon May 18, 2009 11:48 pm

Post by 3FG »

I suspect you are trying to modify the RMDU file. Instead you should modify the RDF file: 31793179 (RCA RCRP05B black).rdf, which will be located in your RDF file folder. If you are using RMIR 2.03 Alpha 28, the RDF folder is a subfolder of the main installation folder. Older instances of RMIR allowed you to put the RDFs anywhere.

Note that this renaming may be a temporary "fix", because the issue actually also affects
11781178 (URC-6820N_8820N_10820N).rdf
201009 (Atlas 1056 B03).rdf
202608 (Charter OCAP C4000 URC-1060BC2).rdf
31473147 (Insignia Remote 67100).rdf
329801 (OARI06G One For All 6+3).rdf
USB8011 (ARRX12G XSight 12).rdf
and the extender RDFs associated with these remotes.

The issue is caused by us-- we used PID 01ED for this OrtekMCE protocol executor, and now UEI has begun using it for a 40KHz NEC1-rnc IR protocol. That leads to a conflict. As a community, we may end up modifying protocols.ini instead.
petehouk
Posts: 14
Joined: Sun Feb 22, 2015 7:46 am

Post by petehouk »

Thanks, 3FG! That fixed it. Thanks for being patient on this. One other thing I noticed is that I had to shut down RemoteMaster and restart it before the change to the rdf file took effect.
Post Reply