URC8811 sends signal twice to Sky digibox

supernath · Post by **supernath** » Sun Aug 15, 2004 8:09 am

I've got this problem too.

Does anyone know anything I can do within RM or IR to only send the signal once when the button is held down (for certain buttons only)?

jon_armstrong · Post by **jon_armstrong** » Sun Aug 15, 2004 10:32 am

There are two very different $0020 protocol upgrades depending on whether you use KM or RM. I assume KM's is the official UEIC version and may toggle, but here it is:

Upgrade Protocol 0 = 00 20 (S3C8+) Custom Protocol for SAT/1847 Sky Digibox (KM v8.25)
40 9A 21 8B 13 87 85 00 08 04 00 DE 00 00 00 00
00 CA F1 38 05 35 01 A8 E4 03 2D E4 04 2E E4 05
2F 08 2D F6 FF 62 19 03 E6 04 03 08 2E F6 FF 62
19 05 F6 FF 62 19 06 08 2D F0 C0 F6 FF 62 19 07
08 2F F6 FF 62 19 08 F6 FF 62 19 09 2C 04 10 09
10 08 10 07 10 06 10 05 10 04 2A F2 E6 10 06 8D
01 46 2C 04 CF 10 C1 DF 10 C1 90 C0 FB 03 B6 C1
03 2A F1 AF
End

This is RC6-6-20n from RM:

Upgrade protocol 0 = 00 20 (S3C80) RC6-M-20n
47 93 61 8b 12 87 05 08 04 00 de 00 00 00 00 00
ca d4 44 05 35 01 a8 0c 0a 18 07 02 11 10 08 10
07 10 09 10 c1 1e 10 08 10 07 0a ef 19 09 8d 01
46
End

I looked at Amazing's learned commands and with one excption there were exactly two frames sent with about 127mS gap between the two frames.

John, Mike, Rob, or other assembly language guru, what would you change to make RC6-M-20n send two frames only wirh a 127 mS gap between them.

Amazing and supernath since others apparently have gotten the KM version to work, try substituting the first protocol and see what happens. You can just change protocols in IR. Delete the other version and then add the one at the top of the post. Amazing you have two identical copies of $0020 in your protocol upgrade tab in IR delete both and try the first variant.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Sun Aug 15, 2004 12:48 pm

Jon, the two protocol upgrades you posted are incompatible. The first uses 2 bytes of fixed data, while the second uses 6. Each would require it's own device upgrade with the correct fixed data.

Neither protocol seems to specify any number of repeats; however, they both have a flag set to repeat as long as the button is held down. If you want to try it with this turned off, for the first protocol, change the 7th byte from 85 to 84. In the second, change the 7th byte from 05 to 04.

jon_armstrong · Post by **jon_armstrong** » Sun Aug 15, 2004 1:15 pm

mr_d_p_gumby wrote:Jon, the two protocol upgrades you posted are incompatible. The first uses 2 bytes of fixed data, while the second uses 6. Each would require it's own device upgrade with the correct fixed data.

Good point. The KM device uprade for the 8811 that should work with the longer protocol posted first is:

Upgrade Code 0 = 37 37 (SAT/1847) Sky Digibox (KM v8.25)
20 0E 38 FA 11 E0 00 20 21 0C 59 5A CC 5B 5C 58
70 6D
KeyMoves
0C F3 37 37 5C«select» ¦0F F3 37 37 CB«info»¦0B
F3 37 37 3C«text»¦0D F3 37 37 81«help»¦0E F3 37
37 6E«green» ¦10 F3 37 37 6F«yellow» ¦3E F3 37
37 69«fav/scan»
End

Neither protocol seems to specify any number of repeats; however, they both have a flag set to repeat as long as the button is held down. If you want to try it with this turned off, for the first protocol, change the 7th byte from 85 to 84. In the second, change the 7th byte from 05 to 04.

I have edited my earlier post to "bold" those bytes.

I would try Mike's suggestion first, to stop the repeat and see if that works. If not try the upgrade. supernath unless you have an 8811 that device upgrade from KM won't work. If you tell me your remote, I can post that version.

supernath · Post by **supernath** » Sun Aug 15, 2004 1:15 pm

Jon and Mike, thanks for the advice.

Indeed, the first protocol didn't work. I tried the second one with the byte change and it works! It means every button behaves in the same way, so the EPG directional buttons need to be repeatedly pressed, but that doesn't bother me too much.

Cheers,

Nathan.

johnsfine · Post by **johnsfine** » Sun Aug 15, 2004 1:24 pm

Does anyone know what change we ought to make to get this right?

1) Make it so only certain keys repeat while held?

2) All Keys repeat while held but with a longer gap than that RM protocol was generating?

3) Two frames per press, as Jon suggested? Nathan's last post makes that idea sound wrong.

4) Uneven gaps (longer gap second to third than first to second)?

mr_d_p_gumby · Post by **mr_d_p_gumby** » Sun Aug 15, 2004 1:35 pm

Just for fun, here's the second protocol (crudely) modified to send exactly two frames with 127 mS leadout off (was 109 mS):

Code: Select all

Upgrade protocol 0 = 00 20 (S3C8+)
 47 93 61 8B 12 87 04 08 04 00 DE 00 00 00 00 00 
 CA F8 0C 05 35 01 A8 0C 0A 18 07 02 11 10 08 10 
 07 10 09 10 C1 1E 10 08 10 07 0A EF 19 09 F6 01 
 46 8D 01 46
End

supernath wrote:It means every button behaves in the same way, so the EPG directional buttons need to be repeatedly pressed, but that doesn't bother me too much.

What you can do is to give this protocol a different number, and create a dummy upgrade using this protocol. Use the normal upgrade and protocol for most of the buttons, and create keymoves to the dummy upgrade for the problematic buttons.

jon_armstrong · Post by **jon_armstrong** » Sun Aug 15, 2004 1:54 pm

Mike/John, if you change the seventh byte to 06, won't that make it repeat only with V+/-, Ch+/-, FF ,REW, etc. Maybe cursor keys, too?

Is the only difference between RC6-6-20n and the long (and presumably official) protocol the fact that the latter toggles or is there some other behavior that it produces? Like an alternating gap?

mr_d_p_gumby · Post by **mr_d_p_gumby** » Sun Aug 15, 2004 2:04 pm

jon_armstrong wrote:if you change the seventh byte to 06, won't that make it repeat only with V+/-, Ch+/-, FF ,REW, etc. Maybe cursor keys, too?

Yes. Not sure what other keys, if any, would be affected (depends on the remote).

jon_armstrong wrote:Is the only difference between RC6-6-20n and the long (and presumably official) protocol the fact that the latter toggles or is there some other behavior that it produces? Like an alternating gap?

Neither one changes the gap in any way. The only difference is in how it manipulates the data before transmitting. I haven't dug into what they are doing, but I presume they eventually end up with the same data being transmitted. Given a cursory lookover, I also haven't seen a toggle bit being generated either.

jon_armstrong · Post by **jon_armstrong** » Sun Aug 15, 2004 2:29 pm

I just tested the Protocol/Device upgrade from KM and it doesn't toggle, appears to repeat on every key, but it does have a ~124 mS gap. So maybe its just a framing error??

Here are the two 0 Numeral commands. The top on is the KM upgrade the bottom is from RM (from Amazing's file loaded into my 8811):

+2664 -888 +444 -440 +444 -440 +444 -874 +444 -874 +888 -438 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -123588
+2664 -888 +444 -440 +444 -440 +444 -874 +444 -874 +888 -438 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -440 +444 -108754

jon_armstrong · Post by **jon_armstrong** » Sun Aug 15, 2004 2:39 pm

Try this protocol set back to repeating but a longer gap between frames:

Upgrade protocol 0 = 00 20 (S3C8+)
47 93 61 8B 12 87 05 08 04 00 DE 00 00 00 00 00
CA F8 0C 05 35 01 A8 0C 0A 18 07 02 11 10 08 10
07 10 09 10 C1 1E 10 08 10 07 0A EF 19 09 F6 01
46 8D 01 46
End

amazing · Post by **amazing** » Mon Aug 23, 2004 1:50 pm

Thanks to the Experts for all their help. I tried jon_armstrong's latest posted protocol. The arrow keys are still a bit too fast (some intented single key press are sent twice) - the channel keys are not repeated which is fine. I changed the protocol now to the one posted earlier by jon with no key repeats at all and this seems to be the best compromise so far. Many thanks.

Amazing