Page 2 of 2
Outlaw remote problem
Posted: Fri Feb 10, 2006 12:56 am
by krisdz
Hi,
The RM is more human friendly. But the Outlaw audio remote is older version, so the buttons don’t match.
I guess I need create my own RDF file for the Outlaw 990 remote.
Where I can find documentation how the RDF file works?
IR has some but it is not for beginners.
Regards
Posted: Fri Feb 10, 2006 2:13 am
by Capn Trips
There IS no documentation. See
this thread in which I'm trying to create an rdf for a Sky remote. We just have to wait for an expert to have some time to walk us through it. In the meantime, I'll continue experimenting with "intuitive" stuff - inspecting OTHER rdfs and comparing - to see if I can get close.
Re: Outlaw remote problem
Posted: Fri Feb 10, 2006 8:50 am
by The Robman
krisdz wrote:Hi,
The RM is more human friendly. But the Outlaw audio remote is older version, so the buttons don’t match.
I guess I need create my own RDF file for the Outlaw 990 remote.
Where I can find documentation how the RDF file works?
IR has some but it is not for beginners.
Regards
In your case, you have found an RDF that works for your remote, the only problem is that some of the button labels in the Gateway RDF don't match the button labels on the Outlaw remote. Therefore, all you need to do is edit the button names in the RDF to the correct ones.
IIRC, this remote supports macros, so what you need to do is create a macro where the included buttons are in a sequence that's logical to you (ie, so you'll remember it) then download the memory and compare the buttons that you programmed into the macro with the ones displayed on the screen. When you spot errors, correct them in the button list in the RDF.
When you're entering the new button names you should enter them in such a way that you'll be able to tell which names you added, just in case you introduce duplicates. For example, let's say that the RDF-button "GUIDE" is really the "MENU" button on your remote, so you change GUIDE to MENU in the RDF. Well, there was probably already a MENU button in the RDF, so when you eventually get to your (let's say) INFO button and you see that it's displayed as MENU, you will need to know which MENU is the one you added and which is the one that was there already, so you'll know which one to replace.
Also, you'll need to know that IR only re-loads RDFs when the remote changes, so simply saving the new RDF won't cause the changes to appear in IR. Therefore, you should open an IR file for a different remote then re-download from your remote. If you don't have any other IR files, use the File > New > Select option to create one.
Outlaw 990 remote problem
Posted: Fri Feb 10, 2006 10:37 am
by krisdz
It is not only the buttons order. Some of the buttons can’t be assign i.e. play. Whatever I do (Or I’m doing something wrong) the play button is not responding. It appears on the different button i.e. rec and works.
I download the picture of the Gateway TV Remote so I can create spreadsheet and coross-reference the buttons and create hex map of the buttons.
In RDF file the order of the buttons in determine by their position, right?
[Buttons]
TV2, button #1 or 01 hex or $01
Setup, button #2 or 02 hex or $02
POWER, button #3 or 03 hex or $03
And so on
What is the purpose of?
[DeviceButtons]
[ButtonMaps]
[DigitMaps]
[Protocols]
Regards
Kris
Posted: Fri Feb 10, 2006 1:23 pm
by gfb107
If you want to know the details of the RDF file format, read RDFSpec3.doc, which comes with IR.
Posted: Fri Feb 10, 2006 1:32 pm
by krisdz
Hi,
The RDFSpec3.doc is not too extensive in explanation.
If some one could explain those settings in more friendly way, I will be appreciated
Regards
Kris
Outlaw remote problem
Posted: Fri Feb 10, 2006 7:16 pm
by krisdz
Hi,
I uploaded two files:
Outlaw Model 990 Remote RDF
https://www.hifi-remote.com/forums/dload ... le_id=2787
Outlaw Model 990 Remote + Oppo OPDV-971H IR file
https://www.hifi-remote.com/forums/dload ... le_id=2786
Both are working flawlessly
Enjoy
Kris