JP1 Remotes

Got a few questions before I buy a remote.

Looking at the 2116 from Radio shack, is it possible to program different codes for HOLDing down a button? (Also, in remote master, is this the "shift" option? the "xshift"? )

And can you put macros on the device buttons?


What I want to do is, have the device buttons act "normal" if you just press them (i.e. pressing DVD just switches control of the remote to DVD)
but pressing and HOLDing DVD does the activity buttons, similar to Harmony, where it turns on TV, switches to DVD input, turns on receiver, switches to DVD input, turns on DVD, etc etc.

Is this possible with the 2116? if not, is it possible with any of the OFA remotes?

Thanks.

scubasteve wrote:Got a few questions before I buy a remote.

Looking at the 2116 from Radio shack, is it possible to program different codes for HOLDing down a button? (Also, in remote master, is this the "shift" option? the "xshift"? ).

Shift and xShift are just functions of what happens when you press the setup (P) button before you press a regular button. This allows you to put up to 3 functions on a button.

scubasteve wrote:And can you put macros on the device buttons?.

The 2116/2117 is one of the few remotes that does let you put macros on the device buttons.

scubasteve wrote:What I want to do is, have the device buttons act "normal" if you just press them (i.e. pressing DVD just switches control of the remote to DVD) but pressing and HOLDing DVD does the activity buttons, similar to Harmony, where it turns on TV, switches to DVD input, turns on receiver, switches to DVD input, turns on DVD, etc etc.

Is this possible with the 2116?

What you are describing is the Long/Double Key press protocol (L/DKP). This is not built into the remote but is available by either installing an extender (which takes control of the remote and provides additional functionality that is not built into the remote). Or in the case of the 2116 there is a special protocol that can easily be installed to give you the L/DKP functionality without installing an extender.

Obviously to achieve all of this you will need to get the jp1 software and a cable since hardly any of this is doable without jp1

xshift also requires the extender (which is extra software installed into the remote via JP1). Without the extender, pressing P before another key shifts that key, but nothing xshifts. With the extender you can pick the key that shifts and if you like pick another key or double press of the first one as the key that xshifts.

Nils_Ekberg wrote:

scubasteve wrote:And can you put macros on the device buttons?.

The 2116/2117 is one of the few remotes that does let you put macros on the device buttons.

What you are describing is the Long/Double Key press protocol (L/DKP). This is not built into the remote but is available by either installing an extender (which takes control of the remote and provides additional functionality that is not built into the remote). Or in the case of the 2116 there is a special protocol that can easily be installed to give you the L/DKP functionality without installing an extender.

Obviously to achieve all of this you will need to get the jp1 software and a cable since hardly any of this is doable without jp1

So it sounds like the 2116 is a good choice for what I'm wanting.

I'm guessing the file I need can be found somewhere in the "special protocol" section of the yahoo group? I think I'll try to do it without the extender if possible, being that extenders seem even more complicated, and I'm a newbie.

Question: This L/DKP protocol, I've downloaded it, but don't know how to use it...

It comes with a readme file, a txt file, and a MS-Batch file.

I tried loading the txt file in remote master, but it says its not valid.

How do I use this?


Thanks.

scubasteve wrote:How do I use this?


Thanks.

The protocol itself is at the bottom of the readme file which needs to be loaded into your device via IR the same way you would as if it came out of KM or RM. You cut and paste the device upgrade into in the device tab (of IR) by using add and the protocol the same way on the protocol tab (of IR).

Here they are:

DEVICE:

Upgrade code 0 = CC 52 (MISC 1006)
F9 00 01
End

PROTOCOL:

Upgrade protocol 0 = 01 F9 (S3C8+)
00 00 03 76 00 20 EB 47 E4 03 4A 56 4A 0F F6 06
D3 76 03 10 EB 0B 76 03 20 EB 13 E4 04 7B 8D FF
5A F6 3B 67 FB F5 76 80 20 6B F6 8D FF 57 56 80
7F E6 F1 7F 6F 76 80 80 EB 08 76 80 20 6B F5 8D
FF 1B F6 3B 49 A6 79 00 6B E4 A4 79 7B 6B 08 C6
C4 0C 67 F6 0E B0 AF E4 05 7B 50 C0 50 C1 50 C2
50 C3 50 C4 C6 CA 15 1B 70 CB 70 CA 70 C4 70 C3
70 C2 30 C0
End

Thanks for all your help Nils.

Another question for anyone familiar with the 2116. I remember reading awhile back about the "whine" when the light is on, but to tell you the truth, I completely forgot about it until I was laying on the couch and heard it.

Does this happen on ALL the 2116, or just some (and I could maybe take it back and exchange it for one that doesn't)?

If it only happens on some, is this an indication of further problems to come (I may decide its not worth the hassle and just keep it)?

I think the 2116 uses the same arrangement of a small transformer with an electroluminescent (EL) sheet to provide the backlighting. The "whine" is caused by the transformer and typically does not indicate any impending failure. Some are just louder than others.

Shouldn't Macros button be on all devices by default? And I have to install a special protocol for DSM (device specific macros)?

I actually haven't installed the LKP protocol or DSM protocol or anything yet, but I have a macros on my sleep button, and its only working when in TV mode.

scubasteve wrote:Shouldn't Macros button be on all devices by default? And I have to install a special protocol for DSM (device specific macros)?

I actually haven't installed the LKP protocol or DSM protocol or anything yet, but I have a macros on my sleep button, and its only working when in TV mode.

I'll tell you what I know, and also what I DON'T know:

(1) Macros are, as you suspect, device-independent, so regardless of what device mode you're in, a button with an assigned macro will always execute that macro and nothing else;

(2) L/DKP works "kind'a like" a macro - in that within the L/DKP "keymove" hex code, you list particular keypress sequences you desire executed,
HOWEVER this sequence is not assigned on the "Macro" Tab, but is assigned like a keymove on the "Keymove" Tab, so it is inherently device-specific.

You can make a macro CALL on an L/DKP so that, for example, regardless of device mode, whenever you push, say, "DVD" a short press may set the remote to "DVD" mode while along push will power on and line up your system for DVD viewing (a fairly typical use of L/DKP).

(3) I have no idea about your "sleep" button anomaly, but I bet if you post your file and provide a link (follwoing the guidelines posted throughout this forum) one of the real experts can take a quick peek and help you out.

Can anyone help me find the hex codes for the buttons?

I'm following the directions in the readme. It says to use the DSM option in the special protocols spreadsheet, and use the "other data" to find the hex codes.

I'm doing that, but no matter what button I choose, it says #NAME? as the hex code.



EDIT actually I figured it out. I just jumped straight to the special protocols spreadsheet. I DL'd the regular keymaster and it told me I needed to install some Tool in Excel.

and while we're at it, it says

Byte 2
Set the second byte to the button hex code of the key with the macro that should be executed for a short key press (for LKP option), a single key press (for DKP option), or always (for DSM option).


What if I want short press to just act "normal" i.e. short press on DVD just puts the remote in DVD mode.

Do I need to go ahead and make a macros on, say, shift-5 that puts the remote in DVD mode?



thanks

If the normal function for the button was assigned to the button in question in KM/RM or even in IR, the L/DKP macro overrides it. However, the function is still there so what you need to do is make the hex code for the short press be shifted version of the button and it will pick up the original function. In the extender dos this is referred to as "shift cloaking"