JP1 Remotes

Anthony_Patrick · Joined: 13 Oct 2006 Posts: 104 Location: Burnaby, Canada

I can't get keymoves to work on my URC-2025. I first tried using RMIR to setup a keymove and everything looked like it worked (the correct keymove binary setup (JP2-EFC5) was loaded into the remote's memory) but the keymove didn't work. The re-programmed key operated just like the keymove didn't exist...

I then tried using the <setup> 994 method of entering a keymove but was answered by a single long blink (indicating the remote doesn't understand keymoves Surprised

)

This is a newer model of remote (it is a JP2 remote) and it supports macros and DSM's and setup multiplexing and upgrades etc. - but it doesn't appear to support keymoves! Does anyone know if UEI is getting out of the keymove business?
_________________
Tony

3FG · Expert Joined: 19 May 2009 Posts: 3367

The Atlas 1056B03 does not support keymoves as delivered from the factory, although Graham has provided an extender that implements keymoves. On the other hand, the Comcast 1067BC4 is also a JP2 remote, but it does support keymoves. I think it is a newer remote than the Atlas.

So it isn't clear to me if UEI is moving away from keymoves.

Anthony_Patrick · Joined: 13 Oct 2006 Posts: 104 Location: Burnaby, Canada

pH7_jp1 · Posted: Thu Sep 19, 2013 8:32 am Post subject:

Anthony_Patrick said:

pH7_jp1 · Posted: Thu Sep 19, 2013 8:44 am Post subject:

Anthony_Patrick said:

pH7_jp1 · Posted: Thu Sep 19, 2013 8:46 am Post subject:

Anthony_Patrick said:

3FG · Expert Joined: 19 May 2009 Posts: 3367

Keymoves are described in segment types $07 and $08. So change

Anthony_Patrick · Joined: 13 Oct 2006 Posts: 104 Location: Burnaby, Canada

Anthony_Patrick · Joined: 13 Oct 2006 Posts: 104 Location: Burnaby, Canada

Anthony_Patrick · Joined: 13 Oct 2006 Posts: 104 Location: Burnaby, Canada

I also tried setting:

KeyMoveSupport=N

in the [General] section of the RDF. It didn't seem to do anything. In fact this setting seems to be ignored if SegmentTypes $07 and $08 are enabled (because the "Key Moves" TAB comes back in RMIR regardless if KeyMoveSupport=N is included in the RDF)... Surprised

_________________
Tony

J Random Hacker · Joined: 05 Dec 2013 Posts: 16 Location: Seattle

3FG · Expert Joined: 19 May 2009 Posts: 3367

If I understand this correctly. your main issue is getting a way, with a single button press, to change from either watch cable or watch a Blu-ray. Keymoves aren't necessary to accomplish this. Instead macros and device upgrades for the TV, Cable box, and Blu-ray are needed.

To make this work reliably, the TV needs to respond to discrete IR signals for input selection. All components need to respond to discrete power on/off, or you have to be willing to leave the components on all the time. Typically TVs and Blu-rays do respond to discrete power signals, and most cable boxes do not. Most of us leave our cable boxes on all of the time-- note that turning a cable box off typically just blanks the display, and the power consumption is hardly reduced.

When I first started in JP1, I tended to use the built in setup codes, and then use keymoves to change the few functions that weren't right. But I saw that experienced users simply made an entire new upgrade, and I quickly learned that was a better way. So I recommend that you construct upgrades for all three components, even though it seems redundant, and include the necessary discrete signals. Then make a Cable "activity" macro which would look something like TV-Power On-DVD Power Off -TV-HDMI1 and assign it to a button. Your parents may need to press the button a second time after a few seconds, depending on how quickly the TV responds to commands after powering on. I don't have a URC-2025, but there is a pretty good chance that you can assign this macro to the Cable device mode button.

THe Blu-ray can be done the same way, with TV-Power On-DVD Power On-TV-HDMI2.

Define a third macro to power off the TV and Blu-ray. At our house this macro is assigned to the Power button.

Now, regarding Tony's point. The remote itself does not support keymoves, but even with a correct RDF file, stand-alone RM does generate spurious keymoves. I don't see this as a big problem, because each of the 2025 button maps include all buttons except Setup and the device mode buttons. Older remotes tended to allow one to only assign functions to a subset of buttons, and we used keymoves to get access to the other buttons. The 2025 button maps cover all of the ordinary buttons, and additionally allows one to assign a IR command to a device button, but only for the current device mode.

Again, I don't see how the keymove issue is important to your parents' need, so I would go ahead with the 2025.

J Random Hacker · Joined: 05 Dec 2013 Posts: 16 Location: Seattle

Thanks for your advice and encouragement. I'm very glad to hear that what I want to do can be done with a URC-2025.

I'll follow your advice and attempt to create complete device upgrade files for any of the devices that could benefit. The TV in question definitely responds to discrete signals for hdmi input selection as well as power on and power off, so I'll start with a TV upgrade file. I'll post any questions separately from this thread. Can you suggest some good reading material for someone about to write his first device upgrade file?

Thanks again.

3FG · Expert Joined: 19 May 2009 Posts: 3367

Typically, one can find an existing upgrade in the File Section for most components, and the easy approach is to just modify the existing upgrade if necessary. You can use the Lookup Tool (link at the top of this page) to compare the EFCs used by the built in setup codes to the one in a candidate upgrade.

J Random Hacker · Joined: 05 Dec 2013 Posts: 16 Location: Seattle

The topic of keymoves on a URC-2025 came up, so I’m back here.

I’m working on a device upgrade file for an LG BP200 Blu-ray player. I started with a JP1 file section file, posted by flo, entitled “LG BP420 Blu-Ray Player (Remote AKB73615701)”.

I verified that the OBC data in the original file was good by comparing it to what Logitech downloads into their Harmony remotes. Except for the addition of data for “power on” and “power off” functions, the data is almost identical, and if you assume the “rewind” and “fastforward” data were switched by mistake in the original file, the data are identical.

The data for “power on” and “power off” seem like all the other data in the list. Here they are, tacked on at the end of the list as entry 38 and 39, in RemoteMaster under the Functions tab:

I don’t have a BP200 sitting in front of me to test whether I could get this remote or any remote to send it these power on and power off signals to see if the device would respond. Also, Logitech doesn’t supply these data for use in their remotes for this device. The BP200 I’m attempting to control is a few hundred miles away.

I’m wondering what these keymoves described in the Device Output Code are.

In RemoteMaster, with this file loaded, under the Output tab, things look like this:

The original file was intended for use in another remote. There were a few more keymoves that were originally in this Device Upgrade Code box when I first started working with the file. The original author was controlling some things using the device buttons, and removing functions from those buttons removed some KeyMoves from this Device Upgrade Code. But nothing I do gets rid of these references to power off and power on in the screenshot.

Can you explain what is going on here?