Hello all!
Recently I purchased a 8910 remote from Rob. A very versitile remote that I personally grew very accustomed to. The rest of the family however, still prefers the old trusty and perhaps easier to handle Dreambox remote. Obviously it has a fewer buttons for my macros and so I had to resort to shifted buttons. To get around that I would like to use the LKP/DKP feature but noticed there are no such protocols for this particular remote. Is it possible to "port" the currently existing protocols or in any other way solve my dilemma? Thank you.
LKP on Dreambox V3 remote
Moderator: Moderators
LKP protocol upgrade for Dreambox remote V3 (URC-39730 B02-00)
Upgrade protocol 0 = 01 82 (S3C8)
00 00 12 E4 03 4A F6 04 DC F6 2C 37 FB 0A 76 77
20 6B F6 E4 05 73 8B 03 E4 04 73 8D 0B CF
End
For device upgrade and instructions look at my post in this thread
http://www.hifi-remote.com/forums/viewtopic.php?t=2489
Upgrade protocol 0 = 01 82 (S3C8)
00 00 12 E4 03 4A F6 04 DC F6 2C 37 FB 0A 76 77
20 6B F6 E4 05 73 8B 03 E4 04 73 8D 0B CF
End
For device upgrade and instructions look at my post in this thread
http://www.hifi-remote.com/forums/viewtopic.php?t=2489
IR supports the ULKDP in the [SpecialProtocols] section. However, it uses a format of 3 bytes: 1st byte top nibble is DSM=0, LKP=1, DKP=2. 1st byte bot nibble is duration. 2nd byte is Short side. 3rd byte is Long side. You'll have to modify your protocol slightly as you have a fixed duration and only 2 var bytes.
That worked like a charm. The duration of a long key press is shorter than that I would have expected, but I am satisfied. Although I did have power macros I did not assign them to the power button as people customarily do, so I had no problems there. I figure I want it macro free because it happens that people miss one device and hit the other during a macro
No, I do not have discrete on/off for all my devices.
Dreambox remote, like other old remotes or remotes with older variant of S3C80 processorbinky123 wrote:IR supports the ULKDP in the [SpecialProtocols] section. However, it uses a format of 3 bytes: 1st byte top nibble is DSM=0, LKP=1, DKP=2. 1st byte bot nibble is duration. 2nd byte is Short side. 3rd byte is Long side. You'll have to modify your protocol slightly as you have a fixed duration and only 2 var bytes.
supports only 1 or 2 bytes long keymoves.
That's why duration is fixed byte in device upgrade.