Sky Digibox on URC-7555/7556

[engeeaitch]

1. Device: Sky Digibox (Pace)
2. Type of device: Satellite
3. Year: Unknown (1999?)
4. JP1/UEI Remote model: URC-7556
5. Do you have a JP1 cable? Yes
6. Still have original remote? Yes
7. Checked the file section? Yes
8. Checked Pronto file section (at R/C)? No
9. Partially working setup code? Yes
10. Learning remote question? No
11. Have you tried the JP1 Lookup Tool? Yes

I have programmed my URC-7556 using the built in seutp code 0847, and it works. However, I want to use RM to setup my own key mapping (and set up some macros). I have used the learning facility, and know that I need the RC6-6-20 protocol, Device ID = 0, Sub Device = 0. The latest version of the RDF file for the URC-7556 does not contain this protocol (but it does have the RC6-M-24 protocol). An older version which I had does contain the protocol (RC6-M-20N), but does not seem to work. I notice that this protocol contains Fixed Data E0 00.

I have downloaded a KM file and managed to get it working. This protocol uses Fixed Data A9 30 55 55 55.

Here is the device upgrade code from KM that works:
Upgrade Code 0 = 37 37 (SAT/1847) Sky Digibox (KM v9.21)
20 08 30 F8 02 FB A9 30 55 55 55 20 21 0C 58 59
5A 5B 5C 6D 6E 6F 70 CC CB 80
KeyMoves
37 F0 04 37 37 3C B3«text»
End

How can I get this to work within RM for my URC-7556?

[3FG]

The 7556 does have support for RC6-6-20, demonstrated by the fact that setup code cable 0847 partially works. The 7555/7556 remotes have Variant 2 of the 00 20 protocol executor, as we can see from the Lookup Tool.

The RDF file does correctly list the protocol executor as 00 20:2. The difficulty is in Protocols.ini, which is the file that tell RM how to accept user data and turn that into the hex data that each executor needs. Protocols.ini doesn't have an entry for the Variant 2 version of the 00 20 protocol executor for RC6-6-20. That's an omission.

If someone else doesn't post a fix earlier, I will work on it tonight.

[engeeaitch]

That all makes sense now. If you could post a fix, that would be much appreciated. Thank you.

[NBoater]

As a short term workaround - Is it possible to use RM to create the upgrade and then, once added to IR, change the fixed data on the upgrade on the devices tab?

NBoater

[3FG]

Add this into protocols.ini. It shouldn't matter where.

Code: Select all

[RC6-M-20n]
PID=00 20
VariantName=2
Notes=This protocol supports any RC6-M-20 variant where the toggle bit doesn't \
      actually toggle (in decodes the T value is always the same).\n\n\
      The only examples we have seen are for the "Sky" device.\n\
      In those examples M is always 6, Device is always 0, Sub Device is either 0 \
      or 12, and T is always 0. \
Typical frequency is 36KHz; check the box to generate 33.6KHz
DevParms=M=6,Device,Sub Device,T,33.6KHz=0:bool
DeviceTranslator=Translator(4,1,15) \
                           BitDoubler(0,3,2) \
                           BitDoubler(1,8,16) \
                           BitDoubler(2,4,32) \
                           Translator(3,1,08,0) Translator(3,1,10,0,comp) \
                           Translator(3,1,09,0) Translator(3,1,11,0,comp)
FixedData=80 00 00 00 00
CmdParms=OBC=0
CmdTranslator=Translator()

[engeeaitch]

Worked perfectly. Many thanks for your help.