JP1 Remotes

I have my URC-9910 remote completely set up, but I want to map a few IR codes that were learned from another remote. (It's a strange remote that there are no definitions for.) Anyway, I learned the IR codes into my 9910, and I'm just trying to figure out how to map them to a button.

Do I do this with a macro? Do I need to add another protocol or something to my remote?

Under the learned signals tab, I have data for each learned button. Here is an example of one of the buttons...

# | Protocol | Device | OBC | Hex Cmd | EFC | Misc
1 | RC5 | 30 |59 |10 or 11 or 12 | 146 or 138 |T=0

Raw Data
Frequency 35714

Sent Once When Key is Pressed
<blank>

Sent Repeatedly While Key is Being Held:
+896 -882 +1764 -1790 +896 -882 +896 -882 +896 -882 +1764 -1790 +896 -882 +896 -882 +1764 -1790 +896 -882 +868 -90230


I also want to move this learned command into a remote with no learn functionality (an Extended URC-6131), and therefore no learned tab in IR. I can easily see the EFC for the button, but how do I know which 4 digit device setup code to use. Also, how would the remote know how to understand the device setup code if I don't load the correct protocol for it.

ed3120 wrote:I learned the IR codes into my 9910, and I'm just trying to figure out how to map them to a button.

When you learned them, that mapped each to a button. If you simply wanted to change which button each is mapped to (including changing the device mode if you like) that is easy to do in IR's learned signals tab.

BUT
You can't end up with one learn mapped to more than one button by that method. From your post it sounds like maybe you want to.
There are some operational flaws in using learned RC5 signals so maybe the method described below would be better anyway.
You need the method below for the 6131, so you may want to do the 9910 the same way.

ed3120 wrote: Do I need to add another protocol or something to my remote?

You need a new setup code (AKA "device upgrade"). It doesn't need a new protocol. RC5 protocol is already included in your remote.

ed3120 wrote: I can easily see the EFC for the button, but how do I know which 4 digit device setup code to use.

There is no built-in setup code for RC5 device number 30, so you need to add one.

ed3120 wrote:Also, how would the remote know how to understand the device setup code if I don't load the correct protocol for it.

Don't know what you mean. Hopefully I answered whatever you meant above or below:

Did you see any OBC numbers larger than 63? Those are rare. If you have some you'll need to get some extra instructions for dealing with them.

Do you want to dedicate a whole device mode to that device? Or just KeyMove a few functions of that device into the mode of a device key that is mainly used for something else?

For the former:

1) create an upgrade with either KM or RM specifying RC5 protocol, and device 30.
2) Select an arbitrary device type and setup code number for the upgrade you are creating.
3) Ignore the EFC numbers and define the functions on KM or RM's functions sheet using the OBC numbers.
4) Assign functions to buttons on the buttons sheet.
5) Copy the output of KM/RM to IR.exe as a new device upgrade.
6) Assign the setup code from (2) to the desired device key.

If you don't want to dedicate a whole device mode, skip steps 4 and 6 above. (You could also skip step 3, but there are some advantages to not skipping step 3). Then define KeyMoves within IR.exe using whatever bound device and key you like, using the setup code from step 2 and using EFC numbers. If you did step 3, get the EFC numbers from the Functions sheet in KM/RM. If you didn't do step 3, the first of the three EFC numbers listed in each learned signal decode is probably the best bet.

Where do I specify RC5 and Device 30 in KM? I thought I would need a remote def file to load into it.

The remote that I am trying to emulate is the Hauppauge grey remote that came with a PVR150. The setup code is apparently 2000. The defs for it are linked to at the bottom of this thread, but not all of the buttons are defined in the defs. (Maybe 32 of the 45 or so buttons) Hence, I am trying to "learn" the other 11 buttons.

The is a link to the remote def file is here:
https://www.hifi-remote.com/forums/dload ... ile_id=755

I found it referenced in this post:
https://www.hifi-remote.com/forums/viewt ... ght=pvr150

You seem to be confused with some of the JP1 concepts. What do you mean when you refer to a remote definition file? It seems like you are referring to an "upgrade file".

When a remote definition file (rdf) is referred to in this forum, it refers to the JP1 remote you are using (i.e. the 9910 in your case) for which the rdf most definitely exists. An rdf for your OEM (original equipment manufacturer) remote is immaterial (and meaningless in our context, if that remote is itself not a JP1 remote).

In building an upgrade, the OEM remote itself is immaterial except as a source of signals to learn and decode. Then you use the decoded information (that you have shown you can clearly read in IR) and use that in KM or RM to build your upgrade, which you subsequently copy into IR and upload to your remote.

You seem to have all of the data you require to build the upgrade you require using either KM or RM.

ed3120 wrote:Where do I specify RC5 and Device 30 in KM?

On the first worksheet (Setup Tab) in KM in the upper right hand area you enter all of this basic information. Then you enter the function names and OBCs on the next worksheet (Functions tab). All of this is in the beginner's documents. I recommend re-reading the beginner's documents (as a minimum to help you sort out the terminology) and then asking a specific question if you run up against a brick wall.

ed3120 wrote:Where do I specify RC5 and Device 30 in KM?

In the Protocol name field of the setup sheet and in one of the device number fields just below it.

ed3120 wrote:I thought I would need a remote def file to load into it.

Using the wrong terminolgy creates confusion. We're left guessing whether you used the wrong name for the right thing or the right name for the wrong thing.

An RDF file gives information about the JP1 remote you're trying to program to IR.exe and/or RemoteMaster. I'm sure you have a correct RDF file for your 9910.

ed3120 wrote: not all of the buttons are defined in the defs. (Maybe 32 of the 45 or so buttons) Hence, I am trying to "learn" the other 11 buttons.

Have you tested the ones that are defined there?

It is a little surprising that your learned signal had device number 30, but that posted upgrade had all device 31.

In fact and upgrade for RC5 protocol IS able to mix two (or even three) different device numbers. But first you should try to make sure that is correct for your device.

If so, it would be a little clearer in RemoteMaster than in KM, but it's doable in KM: Put the new device number (30) in the Device2 field of the upgrade and follow the instructions on the Protocol Help tab for how to set the byte2 column of the functions sheet.