URC-9950 JP1 compatible ?

[David Lewis]

You'll still need an RDF in order to get RM to generate a device upgrade for the 9990, which you can then import into MosAsm.

OK, thanks for the advice. What about protocol upgrades?

I notice that in RM, if I watch one of my existing protocol upgrades while I select different RDFs, it normally doesn't change with RDFs. Or if it does, it's just one of the last bytes. But sometimes it changes a lot. Hence my question about the compatibility of upgrades - what determines whether any given protocol upgrade is compatible with any given remote?

Sorry to ask so many questions; I really appreciate the help you guys give. By the way, the Robman (thanks!) has created a starter RDF for the URC-9990, which is based on a Slingbox RDF, so I'll be trying that. I don't yet know whether it'll be worthwhile spending time editing that RDF. I'd just like to understand how "universal" upgrades are...

[The Robman]

There is a starter RDF here:
https://www.hifi-remote.com/forums/dload ... le_id=3022

This one uses the US "USM0" signature, if you have the European version of the remote you would need to create a copy that uses the European "EML2" signature.

I've been told that this remote uses one of UEI's "blaster" chips, so the button layouts should be similar to those used for the old ReplayTV units and the various Slingboxes, so that's what I based the starter RDF on.

You can experiment by creating upgrades using this starter RDF (thru RM) and then see if the functions end up on the correct buttons. If they don't, you can adjust the RDF.

[gfb107]

There are lots of potential differences between remotes. They've got different keys (with different keycodes) and different keymaps, and differnet processors (this is what can cause the protocol upgrade to change signficantly, as it is executable code).

Raw upgrades are remote specific.

KM/RM upgrades are also remote specific, but the remote can easily be changed in KM/RM, allowing you to generate a raw upgrade for your remote.