Beta testers needed for RCA RCRP05B extender

[R2-M0]

I have a question regarding how the extender determines which LED to flash.

I have a macro on the CBL button...

Code: Select all

Dev_CBL,Phantom1,Dev_dev6,Phantom2

...where Phantom1 just issues my default series of Set_XXX commands. Similar macros exist on the DVD and AUD buttons.

dev6/Phantom2 is an LKP...

Code: Select all

[short]<blank>; [long]Dev_Cancel,Setup

...where Setup is a DSM for turning on the entire system (yes, I've remodeled my remote setup AGAIN )

So why is it when I do a short push on CBL or DVD, the AUD LED lights up? For that matter, why does AUD light up when I push any of the PIP buttons, which are always tied to dev6? Doesn't bother me all that much, but it looks like I'm going to be configuring one of these for my folks soon, and it might throw them for a loop.

LEDPatch on the General panel is set to Default, for whatever that's worth.

Am I at a point where with the RDF updates that have been discussed here that I could release this thing wider? I think that I'd like to have a wider beta for a couple of weeks and then general release.

Sounds perfectly reasonable to me.

[unclemiltie]

In general, the remote flashes the device that the command is being sent to. So if you have the Volume keys set to AUD and the menu keys set to CBL, then when you use a menu key you'll see the CBL flash and if you send a volume key you'll see the AUD flash.

As for the device buttons, right now they're not right. The code in V0.3 will flash the device when you do a Set_Other command.

As for the Default or All, what Vicky did with that patch was to tell the remote to flash other devices when dev4, dev5 and dev6 are selected. Which ones, I can't remember. Vicky, that's probably something I need in the Readme.

I'm wondering if I got the logic backwards on the settings and you're seeing "all" when you really thought you were getting "default" I'll have to check that.

[ElizabethD]

I have LED patch set to ALL, and they flash most of the time correctly. Except shift-Audio which is really dev4 flashes DVD.
And, since all my device macros start with "Dev_AUD;set_Vol", when I press any device button it always flashes AUD, but then when I press other buttons the correct buttons flash. Hope this is of some help.

8910 does the same - first it shows AUD on the LCD screen then follows with the device I just pressed, so I think that's to be expected.

[ElizabethD]

I've built and updated V0.3 that has all of the changes that we have discussed so far. I think that I'd like to have a wider beta for a couple of weeks and then general release. Sound like a plan?

Sounds fine to me. Let's nitpick a little bit longer. But can we get v0.3 to use?

Has anybody run Multiplex yet? I have not.

[R2-M0]

As for the Default or All, what Vicky did with that patch was to tell the remote to flash other devices when dev4, dev5 and dev6 are selected. Which ones, I can't remember. Vicky, that's probably something I need in the Readme.

I'm wondering if I got the logic backwards on the settings and you're seeing "all" when you really thought you were getting "default" I'll have to check that.

There's another possibility. I toyed with setting LEDPatch to All for a while, and then decided to switch back. Perhaps it just didn't get cleared out properly when that happened?

[R2-M0]

Based on Vicky's post, it looks like setting LEDPatch to "All" should result in...

dev4 will light the DVD/VCR LED
dev5 will light the CBL/SAT LED
dev6 will light the DVR/AUX LED

Which still leaves me vaguely befuddled as to why my AUD light is the one turning on.

[mdavej]

Mine works as advertised. Can you post your IR file?

[ElizabethD]

1. With the LED patch=ALL, what I see is this:
dev4 flashes DVD (I already said that before)
dev5 flashes CBL
dev6 flashes AUD, not what Vicky expects

2. I started playing with multiplex and get inconsistent results.
> device setup is definitely switching fine, signals go to the expected device, no problem here.
> on one pair of devices (both audio type), keymoves travel with the new setup code. No problem here. Other than that surprised me, they never did in 8910.
> but on another pair (both dvd type), keymoves stay glued to one device, the one originally defined on DVD (I tested on a keymove which occurs in both devices). I wonder why. And where should I look for a reason?

3. I assigned dev5 to xshift-DVD, and dev6 to xshift-AUD. That didn't work at all, signals weren't going to dev5 and dev6. They work fine when mapped to other buttons such as A and B or Macro1 and Macro2.
Is this normal?

[unclemiltie]

1. With the LED patch=ALL, what I see is this:
dev4 flashes DVD (I already said that before)
dev5 flashes CBL
dev6 flashes AUD, not what Vicky expects

just checked the code, this is what is in there

2. I started playing with multiplex and get inconsistent results.
> device setup is definitely switching fine, signals go to the expected device, no problem here.
> on one pair of devices (both audio type), keymoves travel with the new setup code. No problem here. Other than that surprised me, they never did in 8910.
> but on another pair (both dvd type), keymoves stay glued to one device, the one originally defined on DVD (I tested on a keymove which occurs in both devices). I wonder why. And where should I look for a reason?

the keymoves should stay with the original device. I'm surprised that one "moved" as you said above. are you sure?

The keymoves have stored in them the target key, the setup code for the value to be moved and either the hex/EFC value or the key from that setup code depending on the type of keymove.

3. I assigned dev5 to xshift-DVD, and dev6 to xshift-AUD. That didn't work at all, signals weren't going to dev5 and dev6. They work fine when mapped to other buttons such as A and B or Macro1 and Macro2.
Is this normal?

I'd say not. Are you sure that you fixed the Xshift value to be $C0 in the RDF? The extender code is expecting the Xshift keys to be there.

[unclemiltie]

for wider distribution now that some people have verified that most of the extender works.

This should fix all of the RDF issues that we saw in V0.02 and should also see a device key flash when you do a Set_Other key on that temp device. (useful in macros when you want to indicate which device the remote is controlling)

I've also updated the readme to remove the references to things that were in the Atlas extender and are not in here (i.e. the keymove to deactivate, using long-press to change the backlight toggle, etc)

have at it!

[R2-M0]

Could somebody who's set their LEDPatch to "All" please attempt resetting it back to "Default" and see whether the change takes?

I'm still getting the "All" behavior, even after setting it back to "Default", after doing a 981 reset, and after upgrading to v0.03 of the extender. I suspect that there's something going on here so that you can set it once, but you can't unset it if you change your mind.

The good news is that, now that v0.03 blinks on Dev_Other, the AUD blink on my device macros is so short that you barely notice it. But it's definitely still there. When I press my TV button (which doesn't include the same dev6/Phantom2 LKP that triggers the blink on the rest of the devices), it's clear that the AUD button isn't blinking at all.

Edit: P.S. Should "All" mode be modified to match Vicky's originally posted LED selections? I think her reasoning for using the DVR/CBL/DVD buttons was because they already have the AUX/SAT/VCR labels above them, so it sort of made sense for the extra devices to piggyback on those three.

[unclemiltie]

You have to deactivate the extender, then change it and then re-activate. This is done only at activation time.

resetting, upgrading to V0.03 or doing a 981 reset will not change the state of the LED feature.


I have no issue changing the LED flashing feature to match the previous behavior. It's a trivial change in rebuilding the extender.

I can also make the blink longer if I have to, or do a blink twice. (to distinguish it from a "transmit blink" that happens when you press any key on the remote)

[R2-M0]

You have to deactivate the extender, then change it and then re-activate. This is done only at activation time.

Grrr! I swear I'd tried that. More than once. Really, I did read the ReadMe.txt file!

Clearly, however, I must've mucked up that previous attempt. Apparently, I got it right this time. Thanks again for your assistance and patience. We now return you to your regularly scheduled beta testing.

[unclemiltie]

so far two suggested changes to V0.03

1: match up the LED flashing to Vicky's original picks
2: rearrange the key values in the RDF into "keyboard order" to make finding things easier within the tools.

[R2-M0]

No problems so far with the updated RDF/extender. But I found a few lingering references to the old extender in the ReadMe.txt file

• Several places refer to X_ selections instead of DEV_ selections, including the "FAST MACROS", "HOLDING LAST STEP OF A MACRO", and "TROUBLE SHOOTING" sections
• The "Changing the Shift Key" section still refers to three separate settings for the Shift/Alt-Shift keys, instead of the two settings for Shift/XShift Keycodes.