JP1 Remotes

jnormandin · Joined: 12 Jan 2004 Posts: 4

Okay... I've spent some time getting familiar with IR and KM and I'm starting to get my head around the basics. I've had most of my questions answered in the 'JP1 for Beginners" guide or old forum posts but one remains.

I'm using RS 15-2116 and select this remote model in KM. The button list updates to represent the remote but identifies some of the buttons with a '@' symbol. From what I understand the '@' symbol identifies a button which doesn't exist on the remote but can be referenced in a macro or somesuch. Some of the buttons (PIP, +100, etc.) DO exist on the remote and are still showing up with this symbol. What am I missing?

Thanks in advance,

Jason

johnsfine · Posted: Mon Jan 12, 2004 2:12 pm Post subject:

@ identifies a button which can't be included in the main body of an upgrade in the current device type. It doesn't tell you whether or not the button physically exists.

KM can define buttons as KeyMoves when they can't be included in the main body of the upgrade. It doesn't make much difference unless you're short of KeyMove memory.

Chuck_IV · Joined: 14 Dec 2003 Posts: 54 Location: Connecticut

johnsfine · Posted: Mon Jan 12, 2004 2:24 pm Post subject:

I have no direct knowledge of the design process at UEI, so I can only answer this sort of "why" question with "Someone at UEI designed it that way".

When (as in this case) a given design detail represents significant effort expended by UEI in order to make the product LESS flexible, I can't begin to answer the real "why".

I realize that for those with less JP1 experience, it is not obvious which stupid restrictions exist because UEI designed it that way, vs. which stupid restrictions exist because the programmers in this group didn't have time to do something in a more flexible way. There are both kinds, but this one is definitely UEI's.

jnormandin · Joined: 12 Jan 2004 Posts: 4

Okay, to make sure I've got this right:

For RS 15-2116, PIP is a '@' Key. This means I can't assign an EFP code directly. The workaround is to create a keymove that accesses the same device?

So if I wanted to assign PIP to EFP 216 for my DVD player(1931), I would have to make a keymove something like this:

Bound Device: DVD
Bound Key: PIP
=
Device Button: DVD
Device Type: DVD
Setup Code: 1931
EFC: 216

The Robman · Posted: Mon Jan 12, 2004 2:42 pm Post subject:

johnsfine · Posted: Mon Jan 12, 2004 2:42 pm Post subject:

1) Whether PIP is '@' on a 2116 depends on your choice of device mode. Look at the layout tab of KM for a list of which keys can be in the upgrade body in which device modes.

Neither the fact that the real device is a DVD, nor the fact that you want to use the DVD device button constrains you to use a DVD type upgrade. You can use any type. However, the type does affect what is displayed in the LCD for this device and THAT might make you choose DVD.

2) KM can create the KeyMove for you. Just ignore the '@' and assign the function(s) the way you want. The KeyMove it creates ends up exactly the same as if it were created in IR, but has the advantage of being shown in the buttons and KeyMap tabs of KM (making it easier for you to see what you intended the KeyMove for when you forget that later).

3) If you want to do that KeyMove in IR, I think what you described is correct. Try it. Does it work?

jnormandin · Joined: 12 Jan 2004 Posts: 4

This is making more sense to me now. Unfortunately, I get wierd looks when I drag my entertainment system to work with me, so I'll have to wait 'till I get home to play around with it.

Thanks for the assistance! I'm sure I'll be back with more questions when I decide to tackle that toad/frog/dude/grasshopper extension stuff.

Jason