JP1 Remotes

Yeah the file only allows you to specify the hex commands, I suppose the source may allow further changes unless it's a chipset that's doing all the decoding.

You can send the mx-500 to URC and have them add the code for the dreambox.

Really? That'd be pretty sweet, although are you sure they have a catch-all policy? This seems like a somewhat obscure German machine currently.

The sell mx-500's over in EU, they might ask for the oem remote too.

johnsfine wrote:

The Robman wrote:How much control does that file give you? I wonder if it's possible to make the Dreambox respond to a different signal all together.

I'm sure there is that much control somewhere in this open source design. But at the posted example of THAT file gives no hooks for changing any part of the IR signal other than the (two hex digit) command code.

It is possible, but it takes a lot more effort than editing rcdm700.xml.
http://t-hydron.verkoyen.be/index.php?p=20&c=1
http://t-hydron.verkoyen.be/index.php?p=23&c=1
http://t-hydron.verkoyen.be/index.php?p=25&c=1

MaskedMan wrote:You can send the mx-500 to URC and have them add the code for the dreambox.

If that's true and someone were to send in their MX-500 for an update, they could use IRClone to capture the data and share it with other MX-500 users.

MaskedMan wrote:The sell mx-500's over in EU, they might ask for the oem remote too.

I assume they have tools for using Pronto Hex, and I wouldn't assume they have IR capture tools good enough for a decent capture of this from the oem remote.

So if they want something to learn this code set from, I think you should direct them to Jon's posts at RC giving the protocol structure details and Pronto Hex for the full set of possible commands. That's a lot easier to give them than the Dreambox remote even if they do have good IR capture tools.