JP1 Remotes

Three new Sky/Sky+ remotes have been hacked to install an EEPROM and JP1 header, and the IR downloads indicate an as-yet-unidentified rdf (BS03BS30).

How do I go about turning this raw IR data into an rdf? Is there a guide somewhere that describes the construction of an rdf?

I have looked at the (presumably similar) BSKY rdf and can make guesses about some of the stuff, but really don't know how to identify button definitions, protocols, memory areas, etc.

Please point me in the right direction, and I'll be happy to do the work.

mike-c wrote:IR raw dumps for each of the three Sky remotes are now posted in the Diagnosis Area.

Sky Digital Remote, Model 1600-00U Revision 6

Sky+ Digital Remote, Model 1650-01 B00 Revision 6

Sky+ Digital Remote, Model 1680-00U

I don't think we have anything written up unfortunately, and I don't have the time right now to walk you through it all. There are a few others that know about RDFs, so hopefully one of them can hep for now.

Basically, the RDF describes the layout of the EEPROM to IR.exe, so the first thing you need to do is figure out the layout. ie, where does the keymove section start, etc?

Right, and as these are actually OEM remotes that organically have only the ability to control a TV - minimally, at that - in addition to either the Sky or Sky+ box, it's unclear whether they can even support keymoves, or macros, or upgrades. The owner's documentation for the respective satellite boxes certainly make no mention of it.

I presume I would need to embark on a process of trial and error to see if any 9xx commands work, and then try to create some keymoves, etc, to help you sort out button mappings, key definitions, and memory boundaries and that sort of thing?

(Well, Rob, enjoy your vacation - this will certainly keep, if nobody steps up to walk me through immediately)

Take a look at the existing RDFs for Sky remotes and see what functionality they support. It's quite possible that all you'll need to do is re-name the RDF to the new sig, at least, that might be enough to get you started.

Yeah, been there, done that - get a

There is a conflict at fixed data address $00FC. Do you want to replace the existing data with the fixed data?

And depending on whether or not I choose "yes" or "no" I get different raw data in the raw data tab, but the regular tabs are all the same regardless, with <ERROR> listed for each device type in the general tab.

Does "existing data" refer to the IR file I am opening? or the rdf that is being 'imposed' upon it?

Comment out the fixed data entry until you can verify whether (a) there is any fixed data, and (b) if so where it's located, and (c) what value it holds.