Panasonic combos in 6131 - my shifts don't work??

[ElizabethD]

This is probably in the "everybody knows" category. But a big surprise to me at this moment.
In KM, I just tried migration of Panasonic Combo, Panasonic Combo2, Panasonic Mix upgrades to unextended and extended 6131. <edited 1/14 - only unextended, extended is ok>
It didn't work too well, because the shift-buttons column is shaded out/unavailable

I had no problem doing one-byte protocols, now that I look at what worked, what didn't.
I tried, on the Setup sheet, several device types, but no luck yet.
Also some device types have a * (star) on them. What means "all share the current mode" (in the popup comment)? Any relation to what I see?

I tried NEW on the Setup sheet to rule out my upgrades, and the same shaded column greeted me. I'm not uploading any files, because I think it's bigger than an upgrade issue. I see the same restriction in RM.
Please tell me I'm imagining it. And a solution suggestion would be very welcome.

Now, I read there's something non-standard about 6131 keymoves, but I figured if I select the Extended remote on the Setup sheet it would do the job. No? Do it all in IR or something like that?

[Capn Trips]

I'm no 6131 guru, but viewing KM, I have these symptoms ONLY for the 6131 PVR remote using 2-byte keymoves. I'm pretty sure this is related to the anomalous construction/behaviour of 6131 standard keymoves (about which I know nothing).

For the 6131 PVR Extender, the keymoved button assignments are all available. If they are shaded in YOUR version of KM, then that is a local problem for you.

As for the asterisked device types, I'm pretty surre that this is just an informational feature in KM. KM's drop-down list makes available EVERY KNOWN device type that appears in ANY UEI remote for you to choose fom when building an upgrade. SOME UEI remotes do not differentiate between EACH and EVERY one of those device types, i.e. if I build an upgrade for my RS 15-1994 using the Tuner device type, or the AMP device type, the 1994 will process/recognize BOTH of them as an AUDIO device type. The asterisks provide you info as to which of the device types are "grouped" together as a single common device type with the CURRENTLY SELECTED device type for the currently selected remote.

Edit: In fact, if you take a look at the "Layout" worksheet in KM, the column headings tell you what device types are grouped together for a particular keymap for the selected remote.

[The Robman]

The Capn pretty much nailed it on the head. The keymove format is different in the 6131 compared to older remotes. It has two formats, one is a true keymove (ie, where you copy a button from one location to another) and one is when you program an advanced code (ie, you enter the 3-digit code on the remote). There is no support for 2-byte (or more) protocols with the later format, so if you need keymoves for those functions, you would need to create an additional upgrade and copy the buttons to the locations that you want them. (IR supports both formats, so you don't need to actually do the keymoves on the remote).

Now, what I just said only applies to the un-extended 6131 as the keymove format is the standard one in the extended 6131. KM has an additional selection for the extended 6131, and if you select it, it will let you do your keymoves.

[ElizabethD]

Rob, that is a great summary of the posts I should have read Thank you.
Now, regarding this, and only for unextended:

There is no support for 2-byte (or more) protocols with the later format, so if you need keymoves for those functions, you would need to create an additional upgrade and copy the buttons to the locations that you want them. (IR supports both formats, so you don't need to actually do the keymoves on the remote).

Now, what I just said only applies to the un-extended 6131…

I did no keymoves on the remote. Much too tough. I just built’m all in IR using the extra one-byte upgrades, and they work. But in IR's hex column I see values separated by OR, where the first value is the correct hex code for a command (minus subdevice). I’m ignoring that OR part– that’s OK isn’t it? The OR part is a bit of a pain when you edit a keymove, in that it has to be deleted. Am I missing something again?

KM has an additional selection for the extended 6131, and if you select it, it will let you do your keymoves.

Yup, this is no longer a problem, I messed up on this one, I was sure I selected extended. Clear as daylight.

For the 6131 PVR Extender, the keymoved button assignments are all available. If they are shaded in YOUR version of KM, then that is a local problem for you.

Thanks for checking for me. I messed up, and when I thought I was telling here about extended, it really was unextended, so there is NO PROBLEM.

In fact, if you take a look at the "Layout" worksheet in KM, the column headings tell you what device types are grouped together for a particular keymap for the selected remote.

As soon as I posted it, I thought of that as well , and sure enough it became clear.

[The Robman]

... in IR's hex column I see values separated by OR, where the first value is the correct hex code for a command (minus subdevice). I’m ignoring that OR part– that’s OK isn’t it? The OR part is a bit of a pain when you edit a keymove, in that it has to be deleted. Am I missing something again?

I forget what the second hex code is exactly, but it has something to do with the support that was added for EFC5 codes. If you keep it in EFC mode rather than HEX mode, you won't have this problem.

[ElizabethD]

Big thanks, again.
Yup, EFC, when building a keymove, does make editing simpler.
As far as those double codes go, I'm tossing it into a 'display feature' category, likely necessary at that. 6131 doesn't care, it uses the right stuff.