JP1 Remotes

[WagonMaster]

In my continuing slog through the RDFs in preparation for a new release of the RDF/map/image files, I've encountered something that doesn't make sense.

The previous release (1.28) of these files by Nils Ekberg has 3 RDFs for the unextended URC-6131n (aka 'URC-6131nw') model, 2 of which are for remotes with 2 KB of EEPROM:

• PVR0PVR0 (URC-6131(Old)_6131nwB00 PVR Remote 2K).rdf
• PVR0PVR0 (URC-6131nwB00 PVR Remote 2K FIXED).rdf

Although it's not obvious without seriously re-shuffling some of the lines around, the actual differences between these 2 files are quite small. It boils down to this:

[ElizabethD]

Perhaps somebody cut some traces and made'm into separate buttons??

Hmmm, the facts don't support above!
I just took 6131nw, did 981 reset, coded a macro on shift-5 consisting of:
MACROS:
# Target Key Macro Keys Note
1 SHIFT-5 Angle{Sleep};ClosedCaption;Audio;Subtitle
Darn, I can't see hex in the Summary?????
Raw data says in hex: 9A 14 26 45 37 25
So they're separate?????????????????????????????
I hate facts. This can't be real.

In case I'm not insane, the sticker inside the battery compartment is G052501. I hate it when they put 0 and O and I can't tell the difference.

EDIT: the plot thickens:
Not being sure if above disproves/proves anything, I just made two macros, one on Audio, one on CC. Sure enough they're different, bound keys are $37 and $45.I might put'm through the Widget later to see if they send things I coded on them.

EDIT2:
This is a standard remote. I don't recall how to use it.
Widget/IRscope results:
One-button macros were 8 on CC and 9 on Audio.
With unknown device selected, I pressed Audio and then CC and got 2 identical results Tivo unit=0 Device 133.48 Key 48 hex F3.
Then I selected the TV button which is supposed to be RCA, two identical results: RCA, Device 15, Key 57, hex 39.
So they're not functionally distinct, are they?
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride

[whompus]

Wow its been a while sense I have been here.

I do remember the fixed rdf was for a modded remote. The pix of the mod is in the file section under hardware.

[WagonMaster]

Many thanks for the great input, Liz! I'm following the first part of your post and the 1st edit just fine, but the "EDIT2:" part is confusing me (over my head?). So I still can't decide out what to do with the RDFs. Do I need to wait for other URC-6131n owners (possibly with slightly different variants) to test and compare to your results?

[ElizabethD]

WagonMaster,
Edit1 shows that given that "Fixed" RDF, the CC and Audio buttons are separate key codes. I'm sure we agree on that. But then I thought that was not sufficient, since how it's used matters, so ...
Edit2, in my humble opinion, shows that no matter what freaking thing you assign to those TWO buttons, in my case I assigned 8 to one macro, and nother macro was to press 9, each macro sends the same signal as the other macro (e.g. RCA obc 15). Which, I think supports what Rob wrote, that the code is common, taken from 6131old, so it's useless to separate them and give people a false hope that they got a button.

Anything else I should try to settle this in the absence of experts?

As far as what whompus said, and I recall some cutting thread as well, I think it's impossible to have it functioning, considering those are called by the native remode code, not even the extender. But then what do I know.

Hi whompus, long time no talk? Take a look at some enormous advancements in RM, KM and mostly IRv8. You not gonna believe it
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride

[WagonMaster]

Thanks for the clarification, Liz.

I'm wondering if you could try this simple test, which would be conclusive enough for my purposes, at least until someone else says otherwise:

• Do a '981' reset.
  
• Program a macro on both the 'Audio' and 'CC' keys, but using the remote keypad directly (i.e. with the 995 code).
  
• Download from the remote into IR and check the 'advanced code' area on the 'Raw Data' page for the macro assignments, to see which code is used for the "bound" key.
  

Bill

[ElizabethD]

I have no clue HOW to do that.
I just dug out the 6131 booklet, and see nothing about macros, other than 995 used to set master power.

In any case, tried something and failed. Then I used something advanced to fill the remote with zeros, did 981 reset and tried again, nothing comes out. I have to look someplace how to make a macro. 8910 booklet is of no help to me 'cause it has LCD instructions. Maybe 7800 has something. Bear with me, I've never done it.

I'd expect to see the macro in the macro list, as well as someplace past $400 in raw data.
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride

[WagonMaster]

[WagonMaster]

Oh, I forgot to mention....

Some manuals (like my RS 15-135) stupidly don't bother to tell you that '995' is a macro programming code. They just describe it as a "Programming Master Power" function. My bet is that it will work fine on your URC-6131n for generic macro programming, just as it does on my RS 15-135 remote.

Bill

[ElizabethD]

Still struggling. I only know how to do from keyboard on 8910 'cause the LCD talks back to me
So as a replacement I made two keymoves one on Audio one on CC but I only see $37 in raw data and see only one keymove. I have to repeat and try the macro thing again 'cause I didn't know about that SET at the end.

EDIT1:
Macro making is not taking. Remote doesn't even blink at the widget.

So I redid the keymoves, like this:
Set, 2 blinks, 994, TV, 5, DVD, Audio button, 2blinks
Set, 2 blinks, 994, TV, 6, DVD, CC button, 2 blinks

Edited -This paragraph is wrong - IRscope shows just one OBC.
IRscope shows
Audio button sent RCA dev.15, obc 53 and
CC button sent RCA dev.15, obc 54.

BUT, download into IR shows only one, $37 keymove:
DVD/Audio = Tv,Tv,0047, keycode $1B, efc or keyname 6.
Raw data says: $37 83 10 2f 1B (6131-old keymoves are weird) ends with 00.
What now? Let's call it a day, can do more tomorrow + try macro again.
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride

[WagonMaster]

Actually, if these 2 physical buttons share the same button code as we suspect, it probably makes perfect sense that you only saw one keymove (assuming you made the keymoves directly on the remote keypad, with the '994' code). The last one blew away the first one.

In fact, I suppose even if you enter 2 macros with the '995' code, it's entirely possible (probable?) that only the last one will "survive" to be seen in the "Raw Data" output. I guess if that happens, a good test then would be to do the sequence of programming the 2 macros twice -- once with "Audio" first and "CC" second and then, after checking the raw data, once again with with "CC" first and "Audio" second.

To me, assuming that only the last macro appears in raw data and that it has hex code $37 both times (but with a macro sequence of '1', '1' in one case and '2', '2' in the other case), that would be quite conclusive evidence that the 2 buttons share the $37 button code!

Does that all make sense?

Bill

[ElizabethD]

Yes it makes sense.
And I think I lied about what IRscope showed, that mayhave been a wrong place I looked. Because only the CC keymove comes through as I repeat things now. So at least it's consistent

I too though of reversing the sequence - tomorrow.
Let me know if you need some IR file, I don't think you do.
_________________
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride

[WagonMaster]

[mr_d_p_gumby]

I also have no idea where that RDF came from (and designating it as "FIXED" seems like a poor choice). I do recall that when I first got a URC-6131nw, I took it apart and verified that the two buttons are physically wired together. Without some sort of modification, the firmware in the remote would have no way of differentating between the two buttons. While it is certainly possible that someone modified a remote by rewiring one of the buttons and then creating the RDF in question, it seems quite odd that this person then went ahead and inserted the new key code in the keymap. Since the keymaps in the RDF are to reflect the keymaps in the remote's ROM firmware, I wonder how this person could have also modified the ROM firmware.
_________________
Mike England

• JP1 Group at Yahoo!, JP1 Files Area

[WagonMaster]

Thanks for your input, Mike -- it's always helpful!

My plan, assuming tests by Liz or anyone with an unmodified URC-6131n{w} model don't show otherwise, is to assume that the RDF in question with the $45 button code for "CC" is a fluke. I do not intend to include it in the aggregate set, where it is currently (even in the last [version 1.28] release). I completely agree that putting "FIXED" in the RDF's filename was a poor choice -- something like "h/w hacked" would have been more appropriate.

Bill