JP1 Remotes

The Robman wrote: What does "repeated the previous key press" mean? Do you mean that, if you press POWER, for example, and then press shift-MENU, it will send POWER again?

Yes. I have seen that when adding EFC key moves to Magnavox setups (TV-1963 & TV-1944) on the Charter URC. Every other setup that I used accepted EFC key moves if the protocol/device no. was the same. Beyond that, key moves were unreliable. Volume Punch Through seemed to work as expected, though.

You say the other keymoves all work, and they're all shifted, so that seems to imply that the Shift feature does work. Your DVD keymoves are all using an upgrade that uses NEC1, so in theory the ones that I added should work, the only difference is that they're using built in setup codes rather than upgrades.

I meant that the RMDU-assigned shifted key moves worked when the upgrade was not a combo.

I had an idea that I can check out. What if we grabbed the key moves from the combo upgrade itself?

I had an idea that I can check out. What if we grabbed the key moves from the combo upgrade itself?

That was a bust. The OBCs were correct but their device nos. were garbage.

The Robman wrote:The original learned signal decoder (DecodeIR) translates such learns without a sub-device, but the more recent IrTransDemogifier always gives a sub-device code, even when one is not needed.

This is actually, as many things in IrpTransmogrifier, configurable. The defalt is to supress defaulted parameters. (extra linefeeds inserted for layout), but this is governed by a parameter: In IrScrutinizer, this parameter is available to the user as Options -> Remove defaulted parameters in decode (with the opposite meaning), In RMIR it appers to be set to "keep". This can either be changed to "remove", or the parameter can be made accessable to the user, as in IrScrutinizer.

The call is org.harctoolbox.irp.Decoder.DecoderParameters.setRemoveDefaultedParameters(boolean removeDefaultedParameters))

If I can find that charter remote in my collection I will do some tests
I suspect that being a cable remote some things are actually built in default to the cable device
As a test. Set the cable device setup code to the same as the TV device
Then test your shift keys both in TV and cable device mode's

SysTech_Larry wrote:I meant that the RMDU-assigned shifted key moves worked when the upgrade was not a combo.

The keymoves generated as part of an upgrade are no different to keymoves entered by hand, RMIR just locks them into the upgrade, so you can't edit them on the keymoves tab.

SysTech_Larry wrote:I had an idea that I can check out. What if we grabbed the key moves from the combo upgrade itself?

That was what was in the v2 file, but that meant that the keymoves came from a combo upgrade. What I did in v2 was I manually created keymoves against the built in setup codes, as those should have the right device codes in them.

In this new v4 file, I have re-created the shifted keymoves as external functions:
http://www.hifi-remote.com/forums/dload ... e_id=26952

In case that doesn't work, which I don't expect it will, here's v5 where I've taken a different approach. In this file I have added 2 "helper" upgrades to replicate NEC1 135.34 and 132.224, then I created manual keymoves based on the "key" rather than the "EFC".

http://www.hifi-remote.com/forums/dload ... e_id=26953

That worked. Will I be able to reassign keys going forward?

How is what you did different from my upgrades 1821 & 1154?

To answer my own question, choosing "key" rather than "function" solved the problem, even using 1821 & 1154.
But my fix stopped working.

There are 2 styles of keymoves, those that carry the EFC (in hex format of course) and those that carry the keycode of the button that the code comes from. The drawback of the "key" format is that the function in question needs to be programmed to an actual button in the upgrade itself. The benefit is that it's a single byte code, even if the upgrade is a combo that uses multiple bytes of data for each button.

In my case, as I was creating "helper" upgrades, which were never going to be assigned to actual device buttons, I thought I might as well assign the functions to buttons. In your case, if you're creating an upgrade that you will be assigning to a device button, you would need to assign the functions, that you want to assign to shifted buttons, to non-shifted buttons that you hadn't intended to use, then you can create manual keymoves that copy them to the shifted buttons. Also, avoid the buttons with * (asterisk) in the name because those will result in keymoves.

For example, looking at your original TV/1945 upgrade, I see the following buttons are un-used: REC, LIVE, PIP Swap

So, if you were to program Setup, Open/Close and Em:OK to those 3 buttons, you could then keymove them to the 3 shifted buttons that you want to use. v6 shows how to do this:
http://www.hifi-remote.com/forums/dload ... e_id=26954

I believe that I stumbled on the same thing. I was able to key move unshifted keys, but not shifted ones.

SysTech_Larry wrote:I believe that I stumbled on the same thing. I was able to key move unshifted keys, but not shifted ones.

The key thing to understand is, the "key" that you're trying to keymove needs to be part of the upgrade itself. RMIR tries to make so many things easy for you by doing stuff behind the scenes and one of the things that it does is to create keymoves for you if you try to include a button in an upgrade when that button isn't available, which is the case for all of the shifted buttons, and a few other buttons too. That's why I said to watch out for buttons with an asterisk because those are not part of the upgrade. The way to check is, when you're in edit mode on an upgrade (ie, you're in the RM pop-up screen), go to the Output tab, because there you can see if you're generating keymoves. For example, in your original RMIR file, you should see this:

Upgrade Code2 = 17 99 (TV/1945) Magnavox NF102UD-Emerson NH303UD Hybrid (RMDU v3.0.15)
01 AD 00 FE FE 7E DA FE F1 1E BB 68 97 1E BB 04
FB 1E BB 78 87 1E BB B8 47 1E BB 38 C7 1E BB D8
27 1E BB 58 A7 1E BB 98 67 1E BB 18 E7 1E BB E8
17 1E BB F0 0F 1E BB 70 8F 1E BB 30 CF DE F8 F5
0A DE F8 75 8A 1E BB F8 07 1E BB C5 3A 1E BB 4C
B3 1E BB 90 6F 1E BB 10 EF 1E BB 1C E3 1E BB 9C
63 1E BB B1 4E DE F8 E1 1E 1E BB 31 CE 1E BB 2C
D3 DE F8 F6 09 1E BB F4 0B 1E BB EC 13 1E BB 85
7A 1E BB 25 DA 1E BB B5 4A 1E BB 35 CA 1E BB F9
06 DE F8 F1 0E 1E BB 8C 73 1E BB 6C 93 1E BB 0C
F3 1E BB 71 8E 1E BB F1 0E 1E BB C8 37 DE F8 3E
C1 DE F8 86 79 1E BB E5 1A 1E BB 05 FA 1E BB 45
BA DE F8 27 D8 DE F8 59 A6
KeyMoves
AE F0 05 17 99 00 00 C2?Setup??
AD F0 05 17 99 00 00 BC?Em:OK??
8E F0 05 17 99 00 00 C2?Open/Close?
End

You cannot keymove a keymove. To do a "key" keymove, the "key" in question needs to be part of the upgrade itself. Worst case, if you don't have any spare buttons, just create a "helper" upgrade. Of course, if you're going to do that, no need to have the helper upgrade be a combo, just create multiple helper upgrades, like I did in v5.

SysTech_Larry wrote:I believe that I stumbled on the same thing. I was able to key move unshifted keys, but not shifted ones.

The key thing to understand is, the "key" that you're trying to keymove needs to be part of the upgrade itself. RMIR tries to make so many things easy for you by doing stuff behind the scenes and one of the things that it does is to create keymoves for you if you try to include a button in an upgrade when that button isn't available, which is the case for all of the shifted buttons, and a few other buttons too. That's why I said to watch out for buttons with an asterisk because those are not part of the upgrade. The way to check is, when you're in edit mode on an upgrade (ie, you're in the RM pop-up screen), go to the Output tab, because there you can see if you're generating keymoves. For example, in your original RMIR file, you should see this:

Upgrade Code2 = 17 99 (TV/1945) Magnavox NF102UD-Emerson NH303UD Hybrid (RMDU v3.0.15)
01 AD 00 FE FE 7E DA FE F1 1E BB 68 97 1E BB 04
FB 1E BB 78 87 1E BB B8 47 1E BB 38 C7 1E BB D8
27 1E BB 58 A7 1E BB 98 67 1E BB 18 E7 1E BB E8
17 1E BB F0 0F 1E BB 70 8F 1E BB 30 CF DE F8 F5
0A DE F8 75 8A 1E BB F8 07 1E BB C5 3A 1E BB 4C
B3 1E BB 90 6F 1E BB 10 EF 1E BB 1C E3 1E BB 9C
63 1E BB B1 4E DE F8 E1 1E 1E BB 31 CE 1E BB 2C
D3 DE F8 F6 09 1E BB F4 0B 1E BB EC 13 1E BB 85
7A 1E BB 25 DA 1E BB B5 4A 1E BB 35 CA 1E BB F9
06 DE F8 F1 0E 1E BB 8C 73 1E BB 6C 93 1E BB 0C
F3 1E BB 71 8E 1E BB F1 0E 1E BB C8 37 DE F8 3E
C1 DE F8 86 79 1E BB E5 1A 1E BB 05 FA 1E BB 45
BA DE F8 27 D8 DE F8 59 A6
KeyMoves
AE F0 05 17 99 00 00 C2<<Setup>>|
AD F0 05 17 99 00 00 BC<<Em:OK>>|
8E F0 05 17 99 00 00 C2<<Open/Close>>
End

You cannot keymove a keymove. To do a "key" keymove, the "key" in question needs to be part of the upgrade itself. Worst case, if you don't have any spare buttons, just create a "helper" upgrade. Of course, if you're going to do that, no need to have the helper upgrade be a combo, just create multiple helper upgrades, like I did in v5.

Very helpful.

We missed an obvious resource for Em:OK, TV-1864: OK/Select.

The 3660 allows me to use non-existent keys [in the form of EFCs] from other devices, where the Charter URC does not.

In an earlier iteration, I assigned TV-1864 EFC# 00195 (AV Mode, OBC=131) to the TV-1963 List button and it was retained as an Emerson key (even when none of my devices were set to TV-1864).
TV-1864 does not include that as an available function.

On the Charter, at best, it would be read as TV-1963 OBC=131 (not assigned) or whatever setup code I subsequently changed it to.

You have lots of other keymoves in the charter, are you saying that none of them work?

Before RMIR, most of them worked when generated within a device (with the exception of TV-1963/1944*).
None of them accepted EFC keymoves from other devices.** They accepted active keys, but they still caused crashes.

RMIR seems to have solved the first problem, but not the second. (That is why I was looking at combos.)

*If you have a Charter,

1. set the TV to 1963,
2. key move Mode [EFC=00228, OBC=92] to the Menu key.

If you only press the Menu key, it works fine.
If you press any other assigned key, first, it repeats that key.

**[Dev2] [Setup] [994] [Setup] [EFC#] [Dev1] [assigned key]