JP1 Remotes

I'm fooling around with JP1 again and I've noticed something strange:

In Keymap Master, if I select 15-2116/15-2117 for my remote and then select Device type: "Satellite", the sleep button becomes a mandatory key move.

However, if I select Device Type: "Cable" then the sleep is NOT a key move.

Why are certain buttons key moves and others are not depending on the device type I'm selecting?

Should I use "Cable" for my satellite devices to avoid the extra key move? (not that it matters but it clutters up my key move listing IR)

EDIT: Actually, it seems like all devices except cable make sleep a mandatory key move.

Different device types specify different default key maps and the JP1 tools cannot override that. If you look at the Layout sheet in KM it will show you the available buttons in each device type for the selected remote.

sofakng wrote:Should I use "Cable" for my satellite devices to avoid the extra key move? (not that it matters but it clutters up my key move listing IR)

Yes you should. And it DOES matter since it will save move/macro memory.

Why are certain buttons key moves and others are not depending on the device type I'm selecting?

It also varies by remote. The latest radio shack remotes have nearly all key in all maps, so you rarely have mandatory key moves with those. Plus they have quite a bit more memory.

I'm surprised sleep is still a key move for a tv device.

Thanks for the replies!

I guess I'll have to reconfigure everything as a cable device since that seems to be the only device with a sleep button.

Thanks

Just be aware that this may break VPT.

For reasons only UEI knows, VPT only works when the device upgrade assigned to a device button uses the same device type as is 'native' to that button.

This is often OK, because it only takes 3 key moves to fix, which may be less than the number you save by changing the device type.

Gotcha. Thanks!

However, I'm using an extender which doesn't featuer VPT (eg. everything is manual so you must create "VPT" by yourself), so I don't think I have to worry about that.

By the way, do extenders generally speed up the regular button presses on a remote control? (eg. non-macro)

Another thing to keep in mind, when dealing with LCD remotes like the 15-2116, is that if you use "cable" for all of your upgrades, the screen will always read "cable" regardless of which device button you just pressed (unless the extender changes this).

So, personally, I would use the right device mode for the device button and use keymoves to program the missing buttons.

I agree with Rob, especially for the LCD remotes.

That is until you run out of advance code memory and want to start figuring out how to squeeze things. Then you'll pull out all of the stops to shrink things. But in general, assuming you have enough memory once everything is in the remote and it's working, there is no real advantage to using a keymove or an upgrade.

To pile on, with the extender, it is precisely the KeyMove memory that is vastly increased, while the upgrade memory remains the same (although it CAN overflow into other regions). So unless there is some other imperative (really tight on memory), it's not at all detrimental to have a KeyMove or two as part of your upgrade.

Thanks for all of the replies.

Is it bad to have an upgrade overflow? Here is the message I get from IR.exe:

"Upgrade overflow. There is more data in your device-independent upgrade section that can be stored in the remote. Do you want to move some upgrade devices and/or protocols to the Learned or AdvancedCode regions?"

Does the remote operate slower if I say "Yes" to this?

sofakng wrote:Thanks for all of the replies.

Is it bad to have an upgrade overflow? Here is the message I get from IR.exe:

"Upgrade overflow. There is more data in your device-independent upgrade section that can be stored in the remote. Do you want to move some upgrade devices and/or protocols to the Learned or AdvancedCode regions?"

Does the remote operate slower if I say "Yes" to this?

No.

sofakng wrote:Thanks for all of the replies.

Is it bad to have an upgrade overflow? Here is the message I get from IR.exe:

"Upgrade overflow. There is more data in your device-independent upgrade section that can be stored in the remote. Do you want to move some upgrade devices and/or protocols to the Learned or AdvancedCode regions?"

Does the remote operate slower if I say "Yes" to this?

no, there is just less room in the other areas, so as long as you're not tight there, you will see no difference and IR will manage all of this for you