JP1 Remotes

The Robman · Posted: Thu Dec 10, 2009 10:09 am Post subject:

R2 is right, you don't want to remove any device types from the RDF, regardless of whether the type in question is supported by the remote itself. Every device type falls into one of 4 groups: TV, Cable, Video and Audio.

This is most evident on non-LCD remotes that only have 4 device buttons because the manual itself will tell you that cassette players use the VCR button, and HOME AUTO devices use the Audio button, etc. In LCD remotes, HOME AUTO usually has it's own device type, in non-LCD remotes it will be part of the CD device group if it's available, otherwise it's part of the AUDIO device group.

In the JP1 world, we will try to keep each device type in the correct master group, but on some 2 and 3 device remotes there aren't enough device modes available, so we will group them under the best device mode available.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

wnewell · Joined: 13 Jan 2009 Posts: 158 Location: DFW, Texas

The more I worked with this, I think it's just an RMIR problem. When the upgrade is loaded into rmir, it doesn't change the device type from its alias to the actual type. IOW's if it's a Home Auto device type in the rmdu file, it stays that when loaded into rmir instead of changing to Audio. In ir.exe it gets changed to Audio. I removed Home Auto from my rdf, but agree it should probably be left in for distribution. Hopefully, some the the problems I've found in rmir will get fixed someday as it's easier to use for me, being a linux user.

The Robman · Posted: Thu Dec 10, 2009 5:00 pm Post subject:

If you know that this flaw exists in RMIR, why don't you just change the device types in your upgrades to the right ones for your remote, at least until such time that RMIR is fixed.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

R2-M0 · Joined: 14 Aug 2009 Posts: 92

I have a couple minor tweaks to make to the RDF before I'm ready to call it 100% complete. But I'm hoping somebody can help clarify a few things for me first.

When I view my map on the "Layout" tab of RM, there are 4 buttons across the bottom that don't actually map to physical buttons on the remote. Three of these are Dev4, 5, and 6. However, the circles for Dev4 and 5 are outlined in yellow, but Dev6 is not. In that respect, RM is treating it the same as the Setup button and the three Multi-Macro buttons.

My question is why? I'm not sure how RM has determined that Dev6 is special, except that the button code for Dev6 ($41) doesn't appear in the #3 ButtonMap (code $42 appears twice there, which I think is a blooper).

Which brings me to my second question: Anybody have any idea where that last remaining non-physical button came from, and/or what it's supposed to be? RM just labels it as "button3F" (which it appears to be picking up from the ButtonMaps section since that's the only place I can find a $3F in the RDF).

unclemiltie · Posted: Thu Dec 10, 2009 6:23 pm Post subject:

I'd have to go look at the RCA in more detail (when I write the extender some day) but I can tell you from the Atlas remotes, there were special keypresses that the remote internally changed from the key that was pressed to another key value. One of them was $3F, and that $3F ended up in the button list. (unfortunately)

I thought that Greg was going to go into RM and put some code that "if button is not defined but is in the button maps, don't put it in the list of buttons" but I'm not sure. (we talked off line about this a long, long time ago but I can't remember the outcome)

As for the $42 duplication: Given that I did the work to figure out the button maps, I'm gonna have to go look at the repeat of $42 to make sure that is not a typo. I'd bet that it is though, I've never seen a remote that has a duplicate button code in one of the button maps. The stuff that I used to generate the original rdf is on my other Mac (at home) so it'll be a day or so till I can fire it up and look.
_________________
this JP1 stuff is a sickness!

mdavej · Expert Joined: 08 Oct 2003 Posts: 4501

Bill,

The duplicate isn't totally unprecedented. The 15-13x's have a duplicate ($2C). I brought this up when we first made the RDFs, and binky confirmed it was correct.

Are you saying if we make 3F a phantom it could walk on something else?

R2-M0 · Joined: 14 Aug 2009 Posts: 92

[Edit: Completely rewritten. Forgive me stumbling around a little blindly here, folks. I learn best by getting my hands dirty with a little trial and error, but it ain't a pretty sight for others to have to watch...]

I gotta think that first $42 in the #3 Audio map needs to become a $41. The same sequence in all the other three maps is "$09, $01, $0A, $11, $12, $40, $41, $42" -- in other words, all eight device buttons. And I can't see any reason why you would want the Dev6 phantom device button to be inactive in Audio mode.

Of course, I also can't see any reason why you'd want to let the user try to assign a function to a phantom device button via RM, but...

With that straightened out, and with unclemiltie's explanation for that oddball $3F button, I think this RDF is looking pretty solid. I've updated the file I previously posted to add PVR to the alias list and to change that $42 to a $41. I also pulled the Pause Protocol not-a-comment into a separate readme file.

I'll let WagonMaster know about this latest version so he can include it in the next Big Bundle o' RDFs that he's working on.

unclemiltie · Posted: Fri Dec 11, 2009 12:56 am Post subject:

re: the extra dev buttons in the list

The reason is there is likely an 8-device in the works and they're planning on using the same firmware (and hopefully not the same signature, but I'll bet that they do) This is exactly what they did with the Radio Shack 15-13x remotes. All of the same sigs, more or less devices and a different button set but the lists are all the same.

What's odd in this one is that all of the keys are the same in all of the lists, so why make the 4 button lists and not just one?
_________________
this JP1 stuff is a sickness!

R2-M0 · Joined: 14 Aug 2009 Posts: 92

vickyg2003 · Posted: Fri Dec 11, 2009 7:18 am Post subject:

unclemiltie · Posted: Fri Dec 11, 2009 11:58 pm Post subject:

pxpto · Joined: 13 Dec 2013 Posts: 2

3FG · Expert Joined: 19 May 2009 Posts: 3367

The OARP05S is internally identical to the RCRP05B, so just use the RCRP05B RDF. The latest RDF is here, and also in SourceForge.
Both remotes have a signature of 3179.

pxpto · Joined: 13 Dec 2013 Posts: 2

Thank you 3FG.

I noticed you submited this http://www.hifi-remote.com/forums/dload.php?action=file&file_id=10764

Which is different from trunk (http://sourceforge.net/p/controlremote/code/HEAD/tree/trunk/remotes/rdfs/31793179%20%28RCA%20RCRP05B%20black%29.rdf)

Which one should I use?

3FG · Expert Joined: 19 May 2009 Posts: 3367

The one from the link is newer and corrects an error in the list of protocol executors. Just now, I updated SourceForge with the newer file.