RDF file needed for a new JP1 remote

[dre]

I found a JP1 capable remote in the surplus section at Princess Auto ($5 for those of you in Canada). I can download from the remote, but it doesn't seem to have an existing RDF file.

I've posted the .IR file here:
http://www.hifi-remote.com/forums/dload ... le_id=5186

Can anyone create an RDF file for me? I'm wondering what it's capabilities are. The sticker inside the battery compartment says URC-414XXXB00. It's a 5-device remote, and pretty small (takes 2 AAA batteries). For me, it's perfect for those rooms that just need to consolidate a handful of devices.

Thanks,
/ac

[dre]

Hah. I can't count buttons. It's a 4-device remote (I thought the 'set' button said 'sat'). It looks remarkably like this guy here:

http://www.uei.com/category.php?page_id ... product=52

Thanks,
/ac

[dre]

Anyone? Or can someone at least give me a primer on how to create an RDF file? Once upon a time, I did some coding....
/ac

[mr_d_p_gumby]

Very basic starter RDF here. It will need a lot more work before it is fully functional, but this should get you started.

The next task is to define the key code for each button on the remote. We usually do this by creating as many macros as possible, including different keys in each macro. After downloading into IR, you can then match up the key code numbers with the button names. This info is then used to update the [Buttons] section of the RDF file.

BTW, a copy of the RDF specification is included in the IR zip file. This document details the syntax used in the RDF file.

[dre]

Thanks for the pointers... I've gotten the buttons defined -- it was pretty straight forward - Updated RDF is here:
http://www.hifi-remote.com/forums/dload ... le_id=5193

Do I need to define the [Protocols] section? If so, how?

Thanks,
/ac

[dre]

Okay, I've been trying to develop a device upgrade for this remote, and I've come to realize that I need to further update the [ButtonMaps] section of the RDF.... From what I can tell, the [ButtonMaps] section is used by RM / KM to determine what buttons can be mapped directly, vs. mapped as a Key Move.

How can you figure out which key codes need to be defined in the [ButtonMaps] section? Just trial and error? Any tips to speed up this process?

I've also figured out that the keycodes defined in parenthesis represent groups for certain common functions (eg, a group for channel numbers, a group for volume & mute, a group for channel controls) -- how do you know if a button should be group together with another set of buttons (eg, should the 'Last' button be in the same group as the Channel+ and Channel- buttons?)

Also, do the multiple button maps correspond to the device types? eg, in [ButtonMaps] there are 3 lines, each with a bunch of keycodes defined:
0 = .....
1 = .....
2 = .....

I'm assuming each one represents the [DeviceType] that was defined earlier? Can I just make them all the same? Or does UEI require a different set of key codes for each device (and why????)

Lots of questions.... Hope someone can help!

Thanks,
/ac

[mr_d_p_gumby]

Lots of questions.... Hope someone can help!

Yes, the [ButtonMaps] section needs to be defined next so that you can create upgrades that work. The [ButtonMaps] in the starter RDF I made for you are incomplete, and partially good guesses. You won't get too far until this is sorted out.

There is more than one way to do this. The trial-and-error method is one. You would create an upgrade that maps known function codes to all possible buttons, and then examine what code is transmitted for each button. I usually use the Sony protocol for this since it is easy to visually decode it on a scope. You could also learn them to another JP1 remote and use IR to examine the results. You would need to repeat this for each device button on the remote, since they potentially use different keymaps.

The grouping of the number keys, channel keys and volume keys is very standard for all UEI remotes. I have never seen them grouped in a different manner. The rest of the buttons are never included in the groups.

As to what the [ButtonMaps] represent, they define for JP1 programs the internal keymaps used by the remote. Usually, each device type uses a different keymap. On simpler remotes each device button would typically be a different device type. More complex remotes with, say, 8 device buttons, may assign a device type to more than one device button.

You ask why things are done this way. Only UEI can answer that question properly, but I'm sure from their viewpoint, it has to do with protecting their intellectual property.

This "next step" could get quite technical and would likely bore everyone reading this thread, so I think we should take this off-line. Check your PMs.

[dre]

Okay, it's been a while since I had a chance to try defining [ButtonMaps], and I'm not sure I've been very successful. Here's why.

I started by updating the RDF with all key codes defined within [ButtonMaps], I then created a device upgrade that maps to all keys. I figured that any keys that didn't work should be removed from the [ButtonMaps], and would have to be mapped via a key move.

However.... using this method, it would appear that all of the navigation keys (up, down, left , right, select, guide, info, exit, menu, page+, page-) must be mapped via key moves! I can't map them via a device upgrade. This seems... unusual. Am I doing something wrong?