JP1 Remotes

[Ghallo]

I have the 15-2117, and on the Keymap master file it lists buttons like this:

@ phantom1
@ phantom2
@ phantom3
@ phantom4
@ phantom5
@ DiscreteON
@ DiscreteOFF
@ setup
@ light
@ my system


Some of these buttons I can actually see on the remote (Light and My System) but none of the other buttons exist - how do I get access to these buttons on this remote? Is there a "shift" function or some such?

[mr_d_p_gumby]

[ek2116]

Hi,

Sorry if I'm going over past issues, but I'm confused about this point.
I'm working on a device upgrade for my receiver (Denon A/V 3803).
It shows the following keys as "@" keys on the "buttons" tab: sleep,
pip, info, swap, move, +100, freeze. But, my remote (2116) has these keys. Since the keys are physically on the remote, why are they listed
as "@" keys?

Thanks.

[gfb107]

The @ means that the key is not in the button map for the device type you have chosen for your upgrade. This just means that any functions you assign to these buttons will be transferred over to IR as keymoves. You can try different device types to see if you get more of the buttons you want without the @.

The @ does not mean that the button is a phantom button.

There is not real connection between the @ and phantom buttons. The phantom buttons will always have an @ because they are never part of the the default button map for a device mode.
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)

[asinsh]

In KM, you will see a tab called something like "Layout" which tells you which physical buttons can be assigned EFCs through device code upgrades in which modes. In the 2116, you will find that CBL mode allows you to assign more buttons via device upgrade than any other mode. (None of the modes include all of hte buttons, but CBL has the most.) So if the device you are setting up an upgrade for has too many buttons for the mode you think makes sense and you don't like the 'layout' of that mode, you can specify any other mode for the device. For example, I usually specify that every one of my device upgrades is for a CBL device even though some are for a TV or a DVD or a receiver etc., so that I can assign as many functions as possible through a device upgrade. The only downside to this approach is that every device will then show up in the LCD when pressed as 'CBL', but since I don't care what the display says this doesn't bother me.

If you are using a mode for a device upgrade that does not allow you to assign a function to a button directly, you can still assign things to that button using a keymove. And whenever KM refers to a button with an '@' in front of it, that's what it is telling you -- that KM will assign the function to the button that is not available in that mode via a keymove rather than as part of the device upgrade. The drawback to using too many of those kinds of keymoves instead of using a mode that allows you to directly assign more buttons via device upgrade is that keymoves take up much more memory than an upgrade code so you may end up running out of memory if you do this too much.
_________________
Alan

[ek2116]

Ok thanks for the replies. That clears up the @, but as usual,
more information brings more questions. BTW, I'm using extender2.

If I take your suggestion to the extreme, and say, create
6 CBL devices that run 6 actual components, what will that do
to macros, toadtogs, etc?

Can I create my own button layouts, or are they hard-coded
in the chip?

Eric

[gfb107]

Having 6 cable device upgrades does not cause issues with macros and toad togs.

You cannot create your own button maps.
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)

[asinsh]

[The Robman]