RDF Files For Unsupported Remotes

This is the JP1 beginners forum. There's no such thing as a stupid question in here, so post away, but this forum is just for JP1 users and people considering JP1, non-JP1 users please use the appropriate forum above!

Moderator: Moderators

Post Reply
davida62
Posts: 5
Joined: Sun Feb 06, 2005 2:47 pm
Location: Portsmouth, NH USA
Contact:

RDF Files For Unsupported Remotes

Post by davida62 »

I would like to add some unsupported remotes which have a JP1 plug and are manufactured by UEI. When trying to read one such remote, I receive an error message from IR600 about device type "RUS0RUS0" not being recognized. There's definitely no RDF file in the RDF folder which has the device in it.

I do have a Radio Shack 8 in One that IR600 is perfectly happy talking to.

Searching around led me to the RDF3 Protocol spec documents. Do I have to build an RDF file from scratch or is there a way to make one? Or do I need to submit a raw data file?

TIA,
David
mr_d_p_gumby
Expert
Posts: 1370
Joined: Sun Aug 03, 2003 12:13 am
Location: Newbury Park, CA

Post by mr_d_p_gumby »

If you've read the RDF3 spec (and the addendum), then you know the RDF file needs to provide a great deal of information about the remote. However, the spec document isn't going to tell how to gather it.

In a case such as yours, where you've encountered a remote with a new signature ("RUS0RUS0"), the best thing to do is to capture a download of the remote's EEPROM in IR, save it to a file, and upload that file here in the diagnostic area and post a message to that effect (with a link to the file in the post). Usually Rob or one of the other experts can create a starter RDF from that information, or at least ask you for more details as needed.
davida62
Posts: 5
Joined: Sun Feb 06, 2005 2:47 pm
Location: Portsmouth, NH USA
Contact:

Post by davida62 »

Hi, Mike,

Thanks for the response. I assume you mean setting the Advanced / Enable Raw Download option and saving the associated IR file which is produced. Then, take the downloaded file and post it to the Diagnostics area?

I'll send a file to you soon. I have a pile of remotes that are very close, but just a bit different from each other. You'll see in the files what I mean.

Regards,
David
The Robman
Site Owner
Posts: 21997
Joined: Fri Aug 01, 2003 9:37 am
Location: Chicago, IL
Contact:

Post by The Robman »

What remote is this? Is it a retail remote or did it come with a piece of equipment?
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
davida62
Posts: 5
Joined: Sun Feb 06, 2005 2:47 pm
Location: Portsmouth, NH USA
Contact:

Post by davida62 »

It's a remote that comes with the Russound CAV-6.6 and CAM-6.6 amplifiers.

See:
http://groups.yahoo.com/group/jp1/files ... A48C480.ir
davida62
Posts: 5
Joined: Sun Feb 06, 2005 2:47 pm
Location: Portsmouth, NH USA
Contact:

Post by davida62 »

The file: CA48C480.ir can also be found on this site at:

Forum Index -> Download Database -> JP1 File Section -> Diagnosis Area
mr_d_p_gumby
Expert
Posts: 1370
Joined: Sun Aug 03, 2003 12:13 am
Location: Newbury Park, CA

Post by mr_d_p_gumby »

What happened to the RUS0RUS0 remote?

Anyway, the CA48C480 remote signature matches the Gateway remote that Rob was working on a while back. Rob, did you ever make a starter RDF for the Gateway?
The Robman
Site Owner
Posts: 21997
Joined: Fri Aug 01, 2003 9:37 am
Location: Chicago, IL
Contact:

Post by The Robman »

mr_d_p_gumby wrote:Anyway, the CA48C480 remote signature matches the Gateway remote that Rob was working on a while back. Rob, did you ever make a starter RDF for the Gateway?
I sure did, it's in the RDF folder.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
davida62
Posts: 5
Joined: Sun Feb 06, 2005 2:47 pm
Location: Portsmouth, NH USA
Contact:

Post by davida62 »

I had noticed the same code, too. But it's not for a Russound remote control, so I was confused about that. I will try it on my remote. I have a couple other codes to provide for very, very, very similar remotes.

All the remotes I have look like this one with slight differences in the area at the bottom which is just a sticky template:

http://www.russound.com/images/calrc1_image.jpg

The RUS0RUS0.ir file has been uploaded to the Diags area.

Thanks for bearing with my newbie tendencies.

Regards,
David
mr_d_p_gumby
Expert
Posts: 1370
Joined: Sun Aug 03, 2003 12:13 am
Location: Newbury Park, CA

Post by mr_d_p_gumby »

davida62 wrote:I had noticed the same code, too. But it's not for a Russound remote control, so I was confused about that.
In cases where the remote signature is the same as another remote, the RDF is probably correct enough to work. This implies that UEI used the same CPU in the remotes, and usually the main differences are that some buttons will be named differently, though sometimes the two remotes may have a different complement of buttons. For example, the OEM4OEM0 series includes the Outlaw, Anthem, Ayre and Zap Station remotes (and probably others we don't know about). The main difference in the RDFs for those remotes is the button names.
classicsat
Posts: 279
Joined: Fri Feb 20, 2004 2:24 pm

Post by classicsat »

Looking, the Russound remote is visually the same as the Gateway remote, except the GW remote is in a silver case, possibly backlit.
pcorpe
Posts: 9
Joined: Sat Aug 13, 2005 3:49 am

russound remote

Post by pcorpe »

Gents i'm very interested on the outcome of this thread, I'm a real newbie, cable arrived today, still getting to grips with all the help files and teminology etc.

I have a RUSORU5O remote also, (i think thats o's not 0's?)

any advice/suggestions, many thanks



Pete
Post Reply