JP1 Remotes

I feel that I have gone as far as I can with this remote now so I'll upload everything I've done which includes the URC-1660 RDF, URC-1660 Map, URC-1660 Image and my Technika Upgrade.

The [buttonmaps] from the URC-7555 RDF seem to work perfectly fine after my extensive testing, 3 buttons do no ...

I'm working with binky123 so hopefully he'll be able to compare it to the URC-7555 and discover any differences in the buttonmaps.

Bad idea. The button maps tell RM how to format the upgrade. This may have had an error, but you need an expert to make the modifcations.

I know it's not a solution to the problem but at least I know the thing works with the codes properly. My plan was to rebuild the [ButtonMaps] with trial and ...

My normal procedure has been a 981 reset, download, upgrade and then upload which has seemed to work fine.

I have just modified the [ButtonMaps] section in the RDF to remove everything apart from the 3 groups that are common to most remotes (numbers, channel navigation and volume/mute) for the TV ...

It seems all of my button addresses are actually correct, I've been through them all by assigning them to a macro and then inspecting the RAW HEX output. They match up perfectly with the ones I got initially (on page 2 of this thread).

I am still having trouble though, I have added all of the EFCs ...

All that tells you is that the 7555 RDF has the name Fav attached to the key code (evidently $24). The remote only knows keycodes. IR uses the RDF to translate that into a button name.

The 7555 RDF may be wrong, or UEI may have multiply defined $24.

I get it now, it appears that my key ...

mr_d_p_gumby wrote:Well, that's not an absolute truth. Case in point, URC6131N. However, this should be double-checked to make sure.

I've checked and the '16:9' key on my remote comes up as 'Fav' when I create a macro with it in so it must be correct.

vickyg2003 wrote:
However it does appear that there is an error in either the RDF or the key that you recorded as aspect ratio.

There is no way that FAV and Aspect Ratio can both be $24.

I'll investigate that, seems a bit odd.

(There is no mechanism for the RDF to display a different set of button names for each remote in a common RDF.

In that case I think it makes sense for it to be a separate RDF, whilst the URC-1660 shares the same signature as the URC-7555 some keys have differing names because the URC-1660 is a ...

Okay, thanks for the info, had a bit of a read through the RDF and the RDFspec_R004.pdf. I think I can handle the key mappings part, I'll have a play around with that shortly.

Back to a point raised by vickyg2003, would it be best for me to add support for the URC-1660 to the already existing RDF ...

I managed to create the map fairly easily, had a few problems getting the program to run on a 64-bit Windows 7 system but that's expected from a program designed in 1995. I labelled all of the keys with logical names and modified a couple of lines in the RDF file to get it into RemoteMaster.

The ...

Thanks for the helpful information, I have just started working on the map for this remote and I have a good photo of it. I'll move on to the RDF afterwards and let you know how I get on.

Okay I managed to create an upgrade under the URC-7555 but because the key layout on that remote differs from mine it wasn't that easy to see what I was mapping. The good news is that the functions I mapped works perfectly and I was able to control the power, volume, channels and numbers.

How would ...

You should also notice that most functions are grouped together with other similar functions, the prime example being the numeric buttons that all appear together and in order. When you find the play button, for example, you will probably find that pause, rewind, etc are all next to it in the OBC ...

Rob, how is the order or the list you generated determined? IE How do you know what OBC number is assigned to what EFC?