What's with these button groupings ?

[Andy]

Are the groupings of buttons that I find in the .RDF files a reflection of some feature that one4all put into their remotes, or simply a convenience invented by the JP1 community for saving memory ?

The reason for asking is that I'm trying to debug button position problems (as mentioned in rem's thread "rdf for OneForAll 7562 chipcode B01 sig EM60EM60 help"). I have a mind to try to get this thing back to basics by ungrouping all the buttons. But if it's a UEI thing then I guess I'll just be running away from the finishing line.

I started out on this route by trying to understand the upgrade code generated by KM/RM - which, as it goes straight into the memory must be a UEI format. Is there a definition of this anywhere ?

Many thanks (for help on this and all the great work that went before)

Andy

[johnsfine]

Are the groupings of buttons that I find in the .RDF files

What groupings?

Any structure you see to the layout of the [Buttons] section in the RDF is for readability in the RDF itself and/or UI in some program using the RDF. Nothing of that structure or sequence reaches the remote.

a reflection of some feature that one4all put into their remotes,

The [ButtonMaps] section of the RDF is a reflection of button grouping that UEI built into the firmware of the remote. Maybe that's what you're asking about.

or simply a convenience invented by the JP1 community for saving memory ?

Certainly not. We didn't invent the grouping and it usually costs memory (KeyMoves) not saves memory. I'm sure someone at UEI invented it to save memory, but they weren't really thinking things through when they did so.

[The Robman]

Those groupings are a reflection of the groupings that are hard coded into the remotes themselves. It sounds like the groupings in your RDF do not accurately reflect what's in your remote.

[Andy]

Thanks for these two great replies.

I think that this means that if UEI redefined the groupings (for the version of the 7562 that rem and I bought), then I have a bigger debugging job on my hands than I first thought. I guess I need to add one group or key at a time to see at what point it goes pear-shaped.

It sure would help to have a definition of the upgrade code - though partly I'm on the way. It looks like a few bytes of "this is an upgrade for TV code 2000" (presumably also with the protocol buried in there) followed by "here's some definitions for the n buttons from button x", followed by n bytes of hex straight from the button definitions. Long way to go !

Thanks

Andy