JP1 Remotes

I'll take a look, but be aware that there is the potential for cases when the user will need to use the UEI version even if they don't have it resident, and that's if we ever see a device that uses both OBC bytes at the same time.

Just a passing comment, but having said that all my XMP created BIN files are working I have found one anomaly.

When we originally built a working Slingbox Custom Remote for the Dreambox DM Series we used PID: 01 6C and fixed data of 0E 0F 44 1A (provided by Rob I think)

Now, when I install any of the Dreambox DM boxes onto my Harmony and learn the codes, IRScope gives me 'XMP-1' with device 26. Now when I enter those values into Remotemaster I obviously get the right Protocol ID of 01 6C, but the fixed data shows up as 1D 0F 44 1A 1F 00 40. And the remote does NOT work in real life, sending the wrong signals.

Please don't waste any time on this, as we already have a working system, but maybe it might be of academic interest to someone, as there does seem to be an error somewhere

Al

You're missing the sub-device, which is zero, if you enter that you'll get the correct hex code. So the question is, did IRScope give you a sub-device and you just missed it (the device code should have been shown to you as 26.0), or did it not give you the sub-device at all? If it's the latter, we'll need to get Graham to take a look at it.

My fault, as usual IRScope does give 26.0.

I keep learning, I have to admit I always assumed that a zero sub-device could be left as blank. Don't recall it ever causing a problem before.

I still get a slightly different fixed data, with 3 extra bytes at the end but I assume they aren't essential ?

Thanks for setting me straight

Al

The problem is that the default sub-device isn't 0, so if you leave it blank, you'll get a different value. The extra 3 bytes are for the JP1 version of the protocol (ie, the version that we wrote specifically so that it would fit in the Slingbox). If you switch to the UEI version, you'll just see 4 bytes (but it won't work in the Slingbox).

OK, I remember we had to apply that 'fiddle factor' to device numbers before you got the proper implementation. Makes sense now.

I just posted about what I think is a problem with this protocol - it does not see 2 signals when the same code is sent in a macro (e.g. channel 22)
http://www.hifi-remote.com/forums/viewt ... 0167#90167
and also that thread mentions that the signal doesn't repeat in a macro.