Sky Q Box (RC6-6-28)

[alanrichey]

OK, uploaded at https://www.hifi-remote.com/forums/dload ... e_id=13980 I'll leave it to you to edit the PID.

[The Robman]

The RC-6-28 has a complicated structure.
It is a bi-phase signal, which means that a 1 is represented by a +450, -450 timing pair and a 0 is -450+450 timing pair, where + timings mean that there is IR activity, and – times represent quiet times.

To use our regular terminology, we refer to "IR activity" as ON times, and "quiet times" as OFF times. So positive numbers are ON times, and negative numbers are OFF times.

But the RC-6 family of signals also have some structural timings inside the signal as well. So if you are looking at this on a graph, some of the bumps are 450 wide, others are 900 wide, but if you were to divide this up there are places where there are that around the 4th bit where its neither a zero, nor a 1. That is a structural timing.

The +900 or -900 thing is the result of two +450 or -450 times coming back to back, except for that one "double wide" pair, where you will see "-900 +900", which is common to all the RC6 family of protocols.

For anyone looking at bi-phase signals in IR or RMIR, once you've entered the rounding time, you can select ODD or EVEN and it will split the double times into two and separate the pairs with a semi-colon, which makes it a lot easier to decode by hand.

For example, the raw times for the POWER button here are:
+2676 -890 +444 -442 +444 -442 +450 -866 +450 -866 +892 -444 +444 -442 +444 -442 +444 -442 +444 -442 +444 -442 +444 -442 +444 -442 +892 -876 +444 -442 +444 -442 +444 -442 +444 -442 +444 -442 +892 -444 +450 -866 +892 -876 +444 -442 +444 -442 +444 -442 +444 -442 +892 -444 +450 -866 +444 -442 +448 -116504

Rounded to 450 they show as follows:
+2700 -900 +450 -450 +450 -450 +450 -900 +450 -900 +900 -450 +450 -450 +450 -450 +450 -450 +450 -450 +450 -450 +450 -450 +450 -450 +900 -900 +450 -450 +450 -450 +450 -450 +450 -450 +450 -450 +900 -450 +450 -900 +900 -900 +450 -450 +450 -450 +450 -450 +450 -450 +900 -450 +450 -900 +450 -450 +450 -116550

And with ODD selected, they show as follows:
+2700; -450 -450; +450 -450; +450 -450; +450 -450; -450 +450; -450 -450; +450 +450; -450 +450; -450 +450; -450 +450; -450 +450; -450 +450; -450 +450; -450 +450; -450 +450; +450 -450; -450 +450; -450 +450; -450 +450; -450 +450; -450 +450; -450 +450; +450 -450; +450 -450; -450 +450; +450 -450; -450 +450; -450 +450; -450 +450; -450 +450; -450 +450; +450 -450; +450 -450; -450 +450; -450 +450; -116550

If you then replace "+450 -450;" with "1" and "-450 +450; " with "0" you get:
+2700; -450 -450; 1110 -450 -450; +450 +450; 0000000010000001101000001100 -116550

which can be cleaned up to:
+2700 -900 1110 -900 +900 0000000010000001101000001100 -116550

the trick with selecting ODD or EVEN is to get the leadin off time correct

[vickyg2003]

To use our regular terminology, we refer to "IR activity" as ON times, and "quiet times" as OFF times. So positive numbers are ON times, and negative numbers are OFF times.

Yes, the reason I call it IR activity, was because trying to come to terms with how all the words + - and frequency came together, I was so extremely confused as to what a signal was.

When I started here I didn't realize that the IR ON time itself was really a rapidly flashing IR signal. How many times it flashes in that +450us is where that frequency comes in. I was thinking this was more like a sound wave. I thought the + number was how high the signal went, and the - number was how low the number went, like amplifying a sound wave, and that the frequency was how quickly the whole signal went by. But I was also one of those people that thought when I chose TV as a device type, that there was actually something in the signal that said only TV's should listen to it..... hahaha, it makes me laugh to think how far I've come.....

Rob, if you could have been in my head and saw what I thought was going on here, you would have never have wasted your time training me. lol.

Fortunately for me, I was able to get Tommy to build me one of Kevin Timmerman's Widgets. I have the second Widget Tommy ever made, he kept the first one for himself.. Once I could see the signals the whole thing started making sense.

[The Robman]

Rob, if you could have been in my head and saw what I thought was going on here, you would have never have wasted your time training me. lol.

But just for the record, I'm very glad I did!

And I think it's true for all of us, before we dug into remote controls, we had no idea what a remote control signal looked like, at least, I know I didn't. If you search for my name over at Remote Central there is a really old post where I speculate as to what it might be like (and am totally wrong, of course).

[The Robman]

I have modified the protocols.ini entry so that it generates the right code for S3C8 and HCS08 remotes.

Code: Select all

[RC6-6-28] 
PID=01 FF 
DevParms=Device=0,Sub Device=0 
DeviceTranslator=Translator(0,8,4) Translator(1,12,12) 
FixedData=E0 00 00 
CmdParms=OBC 
CmdTranslator=Translator(0) 
DefaultCmd=00 
CmdIndex=0 
Code.S3C80=40 9A 31 8B 0D 00 05 35 01 A8 00 DC 00 00 00 00 00 C3 1C 12 F6 01 4C 38 03 F6 FF 52 F6 FF 3F 38 03 F0 C3 F6 FF 52 6C 01 87 36 03 F6 FF 56 6E 37 64 F6 C6 F8 E3 8A F6 01 58 F6 01 0A 7B D4 AF F6 FF 4D F6 FF 4D F6 FF 48 1C 16 8D 01 4C 1C 1A 8D 01 4C 4C 04 8B 02 4C 08 37 3F 08 F6 FF 4D F6 FF 48 8B 06 F6 FF 48 F6 FF 4D 90 C3 4A EB AF

[RC6-6-28]
PID=01 FF 
DevParms=Device:8=0,Sub Device:12=0
DeviceTranslator=BitDoubler(0,8,16) \
                 BitDoubler(1,12,32)
FixedData=CA 93 55 55 55 55 55
CmdParms=OBC 
CmdTranslator=Translator(0,1,0,7) Translator(0,1,1,7,comp) \ 
                 Translator(0,1,2,6) Translator(0,1,3,6,comp) \ 
                 Translator(0,1,4,5) Translator(0,1,5,5,comp) \ 
                 Translator(0,1,6,4) Translator(0,1,7,4,comp) \ 
                 Translator(0,1,8,3) Translator(0,1,9,3,comp) \ 
                 Translator(0,1,10,2) Translator(0,1,11,2,comp) \ 
                 Translator(0,1,12,1) Translator(0,1,13,1,comp) \ 
                 Translator(0,1,14,0) Translator(0,1,15,0,comp)
DefaultCmd=55 55
CmdIndex=0 
Code.HCS08=20 15 24 4B 72 8F 05 08 08 00 DD 00 00 00 00 00 DE E0 9C 03 84 00 00 CC FF 5F

But Vicky, I have challenge for you, could you use the HCS08 version of the RC6-6-32 exec to add logic to your RC6-6-28 exec so that it doubles the command byte in the exec?

Here's a PB file for it...
https://www.hifi-remote.com/forums/dload ... e_id=13981

[vickyg2003]

But Vicky, I have challenge for you, could you use the HCS08 version of the RC6-6-32 exec to add logic to your RC6-6-28 exec so that it doubles the command byte in the exec?

Spoken like a true teacher, break the problem down to a managable task and feed it to the student. lol.

Yes I can, but I won't have the time until tomorrow. Today I'm away from my PC and only check on the forum with portable devices.

[The Robman]

I decided to try my hand at it myself, and the trick was figuring out that the FF8A call was to a bit doubler, then it was easy...

Code: Select all

[RC6-6-28] 
PID=01 FF 
DevParms=Device=0,Sub Device=0 
DeviceTranslator=Translator(0,8,4) Translator(1,12,12) 
FixedData=E0 00 00 
CmdParms=OBC 
CmdTranslator=Translator(0) 
DefaultCmd=00 
CmdIndex=0 
Code.S3C80=40 9A 31 8B 0D 00 05 35 01 A8 00 DC 00 00 00 00 00 C3 1C 12 F6 01 4C 38 03 F6 FF 52 F6 FF 3F 38 03 F0 C3 F6 FF 52 6C 01 87 36 03 F6 FF 56 6E 37 64 F6 C6 F8 E3 8A F6 01 58 F6 01 0A 7B D4 AF F6 FF 4D F6 FF 4D F6 FF 48 1C 16 8D 01 4C 1C 1A 8D 01 4C 4C 04 8B 02 4C 08 37 3F 08 F6 FF 4D F6 FF 48 8B 06 F6 FF 48 F6 FF 4D 90 C3 4A EB AF

[RC6-6-28]
PID=01 FF 
DevParms=Device:8=0,Sub Device:12=0
DeviceTranslator=BitDoubler(0,8,16) \
                 BitDoubler(1,12,32)
FixedData=CA 93 55 55 55 55 55
CmdParms=OBC 
CmdTranslator=Translator(0)
DefaultCmd=00
CmdIndex=0 
Code.HCS08=20 15 24 4B 71 8F 05 08 08 00 DD 00 00 00 00 00 DE E0 9C 03 84 00 00 B6 67 AE 08 CD FF 8C BF 67 B7 68 6E 02 AA CC FF 5F

[vickyg2003]

I was busy all day, but did get a chance to code a loop yesterday and then when I got home realized that the HCS08 has that vector call that doubles the bits as specified in the Vector variable sheet that I got with protocol builder. An interesting exercise non the less. I now know how to do it in assembler and using the vector call.

[alanrichey]

Just to let you know that the initial release had the wrong code for the Power button. The user didn't do a full check in his excitement I've updated both the BIN files and the RMDU files in the File Section with a fixed copy.

[3FG]

I want to add this to protocols.ini, but I also prefer to use the format of the UEI official executor PID 0240. It allows 36 and 33.5KHZ modulation, and can accept any 3 bit M value. It is not a true RC6-N-28, because like other "RC6" executors, the toggle burst pair isn't actually toggled. So following the naming practice we use, this is RC6-M-28n. I have executors for MAXQ and S3F80, but I need help with the HCS08 to add in the frequency selector code. Any takers?

Code: Select all

[RC6-M-28n]
PID=02 40
CmdTranslator=Translator()
CmdParms=OBC=0
DevParms=Device:8=0, Sub-Device:12=2074, M:3=6, Freq:36KHz|33.5KHz=0
DeviceTranslator=BitDoubler(0,8,16) \
                 BitExpander(1,4,32,8,2,01,02) \
			        BitExpander(1,8,40,0,2,01,02) \
                 BitDoubler(2,3,2) \
				     Translator(comp,3,1,15)
FixedData=A9 30 55 55 95 56 99
FixedDataMask=FF 00 FF FF FF FF FF
Code.S3C80=40 9A 71 8B 07 00 05 35 01 A8 00 DC 08 04 37 00 0D E6 0E 4D E6 0F A0 F6 01 55 0C 08 18 0A 04 0B 0B 10 0A 10 C1 10 0B 20 0B 10 0A 0A F1 1C 12 F6 01 4C C6 F8 00 C8 1C 16 4C 00 F6 FF 58 F6 FF 54 5C 07 F6 FF 58 5A FB C6 F8 E3 8A F6 01 58 F6 01 0A 7B DA AF 6C 04 8B 02 6C 08 87 24 03 10 C2 7B 05 F6 01 58 8B 05 1C 16 F6 01 64 6A F0 4E AF
#Code.HCS08=
Code.MAXQ610=35 6F 41 0E 10 00 00 00 00 00 10 00 11 0F 60 00 20 00 00 86 00 00 00 00 41 F0 04 50 D5 D4 D6 62 50 06 70 31 72 73 75 76