RM: need "Manual Settings" help

Post by **The Robman** » Wed Apr 08, 2009 11:45 am

Hey Greg,
I created a new protocol for Control4 and the KM upgrade loads into RM just fine. Here's the KM file...

http://www.hifi-remote.com/forums/dload ... le_id=6523

However, my user needs to combine unit codes into a single upgrade, so I changed the protocol for a 3-fixed, 1-variable, to a 2-fixed, 2-variable format, but I can't figure out how to get this info into RM.

Here's the new KM file...
http://www.hifi-remote.com/forums/dload ... le_id=6524

If you try top open the new KM file using RM, you cannot access the Functions tab. So, I opened the old KM file and tried to change the settings using the "manual settings" menu option, but I can't figure out how you're supposed to add or remove entries here.

Could you show me how set up an RM file for this upgrade please?

gfb107 · Post by **gfb107** » Mon Apr 13, 2009 8:00 am

Found a bug in the import code that this particular KM upgrade uncovered.
I've fixed it for v1.91, but until I release that you can use the .rmdu file I saved after importing: http://www.hifi-remote.com/forums/dload ... le_id=6548

I'll come back later and look at how you would create this upgrade in RM from scratch.

Post by **The Robman** » Mon Apr 13, 2009 3:18 pm

Thanks Greg.

Could you also help me with another file that I'm having a problem with.

http://www.hifi-remote.com/forums/dload ... le_id=6547

I received an email from a Slingbox user who's using the C1630 code on an RV box, which is a built-in code. He said that not all of the buttons work, so he wants to be able to manipulate the code. Therefore, I created a KM file using Manual Settings to replicate the code and then imported it into RM, where I changed the selected remote to the RV version of the Slingbox. However, it looks like RM is including the protocol code in the upgrade (and this uses $0161, which is a HUGE protocol) even though the RV box already has the $0161 protocol (and the RDF correctly states this). So, I tried changing the selected protocol from Manual Settings to $0161 but then RM did what I was describing earlier and zeroed out all of the data in the Functions tab, and it reduced the variable data from 2-bytes to 1-byte.

I don't know how to format an RM file for this code so that it will work with the RV Slingbox, that doesn't need a protocol upgrade.

gfb107 · Post by **gfb107** » Tue Apr 14, 2009 1:01 pm

Part of the problem is that the entry for PID 01 61 in protocols.ini only has code for the HCS08 processor, which has 3 fixed bytes and 1 variable byte.

The protocol code in the upgrade file is for the S3C80 processor and uses 5 fixed bytes and 2 variable bytes.

This results in RM treating the protocol code embedded in the upgrade as a custom protocol that just happens to re-use a known PID, and therefore the code is required.

I'll have to try a few things to figure out how to deal with this situation.

gfb107 · Post by **gfb107** » Tue Apr 14, 2009 1:25 pm

I think we're going to need to define multiple variants of 01 61 in protocols.ini in order to handle this. Which means we'll have to change the RDFs to reflect which variant they have.

BTW, I have a number of changes coming in v1.91 dealing with Manual Settings and unnamed protocols that fix many lost data scenarios.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Tue Apr 14, 2009 1:58 pm

OK, let's call the 5 fixed/2 variable version variant 5 (0161:5). The existing 3 fixed/1 variable can be variant 3. There is another older version in old Dreambox remotes that is 1 fixed/2 variable, which can be variant 1.

Here's the code for variant 5:

Code: Select all

Code.S3C80=43 8B 52 8B 16 83 80 80 03 08 00 00 9E 00 00 00 \
           00 00 8E 97 B5 01 E2 01 CE 06 F4 68 09 37 6C 03 \
           E4 05 03 37 6A 03 E4 06 04 18 07 37 10 09 E6 0E \
           2C E6 0F 5D F6 01 55 19 06 E4 08 05 37 6E 3D C4 \
           22 1C B0 04 B0 05 37 60 03 46 03 01 37 62 03 46 \
           03 02 37 69 13 F6 FF A3 F6 FF 8A F6 01 0A 7B FB \
           56 03 FC F6 FF A3 8B 22 37 67 05 E4 08 05 8B 03 \
           E4 08 04 F6 FF A3 F6 FF 8A 7B FB AF F6 FF A3 F6 \
           FF 8A 7B FB 46 04 80 F6 FF A3 1C 1E F6 01 4C 1C \
           14 F6 01 64 76 03 C0 EB 02 77 71 F6 01 70 77 70 \
           8D 01 0A 56 06 F0 B0 C2 3C 04 87 53 02 02 25 F0 \
           C5 02 25 3A F5 56 C2 0F 44 C2 06 E6 10 04 8D 01 \
           73
Code.HCS08=20 19 22 47 52 83 80 80 03 08 00 00 98 00 00 00 \
           00 00 A2 97 C9 01 E1 01 E2 07 08 0D 66 03 4E 62 \
           60 0B 66 03 4E 63 61 01 64 08 45 17 30 35 A7 CD \
           FF 6E 4E 64 63 4E 65 62 0F 66 3A 55 7A 35 74 3F \
           61 3F 62 01 66 02 10 60 03 66 02 12 60 08 66 13 \
           AD 3D AD 2B 11 25 CD FF 92 25 F9 11 60 13 60 AD \
           2E 20 1C B6 65 06 66 04 B7 62 20 02 B7 61 AD 1F \
           AD 0D 25 FC 81 AD 18 AD 06 25 FC 1E 61 AD 10 AE \
           76 CD FF 65 AE 6C CD FF 68 CD FF 62 CC FF 92 B6 \
           63 A4 F0 B7 63 3F 52 45 00 04 E6 5F 62 BB 52 EB \
           5F B7 52 5B F5 A4 0F BA 63 B7 63 6E 04 A9 CC FF \
           86

Variant 5 is in the following remotes:
URC-8210, URC-8305, URC-7950, URC-7555, URC-7525, Arcam CR-100, Atlas URC-1055 (JP1.3), Atlas URC-1056, Cricket, Cox URC-7820B, RS 15-133/4/5, Slingbox RV

Variant 3 is in the following remotes:
URC-6820/8820/10820, URC-8203/4/6, URC-6690, Atlas URC-1055 (JP1.2), Catlayst 48 (JP1.2)

Variant 1 is in the following remotes:
Dreambox V1/V2/V3, Force

gfb107 · Post by **gfb107** » Tue Apr 14, 2009 8:38 pm

Thanks Mike. Have you got protocol code for variants 3 and 1? I already had HCS08 code for variant 3 in protocols.ini, but that's all.

Post by **The Robman** » Tue Apr 14, 2009 8:59 pm

Here's the version 1 (S3C8):
3D 92 12 8B 16 49 05 08 00 84 01 75 00 84 03 87 83 C2 00 00 00 00 00 00 03 5F A0 48 05 37 40 06 28 03 77 26 29 03 0C 05 76 03 01 6B 0D E4 25 1C E4 26 1D 0C 03 09 12 E6 24 02 18 03 90 C1 0A FC 19 05 A6 0D 02 6B 0B B0 C6 F6 FF 58 37 61 02 7B F6 AF F6 FF 58 F6 FF 58 B0 C5 60 04 60 05 F6 01 46 F6 01 0A 7B 02 6C FF 60 C5 EB EE AF

And here's version 3 (S3C8):
43 8B 31 8B 14 83 80 80 03 08 00 00 9E 00 00 00 00 00 8E 97 B5 01 E2 01 CE 68 05 E4 06 05 69 06 20 10 37 60 09 E6 0E 2C E6 0F 5D F6 01 55 F6 FF 34 46 04 80 F6 FF 56 F6 01 73 1C 1E F6 01 4C 1C 14 F6 01 64 76 03 C0 EB 02 77 71 F6 01 70 77 70 F6 01 0A 7B E5 AF B0 C3 4C 03 28 06 F0 C2 87 53 03 02 25 F0 C5 02 25 3E 4A F4 56 C2 0F 56 06 F0 44 C2 06 AF

I don't think there is an HCS08 version 1 variant.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Wed Apr 15, 2009 1:11 pm

The Robman wrote:I don't think there is an HCS08 version 1 variant.

I don't have any record of an HCS08 variant 1 either.

Rob, can you detail the fixed & variable data for each variant?

gfb107 · Post by **gfb107** » Sat Apr 25, 2009 7:16 am

Do we have a name for this protocol? Or shall we continue to refer to it by PID?

binky123 · Post by **binky123** » Sat Apr 25, 2009 8:18 am

Names I've seen for 0161 are i3micro or Telefonica or NightHawk or 4PPM.

Post by **The Robman** » Sat Apr 25, 2009 10:06 am

Let's call it ADB as the main user seems to be the Advanced Digital Broadcast STBs.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Sun Apr 26, 2009 12:05 pm

The two bytes in red need to be corrected:

The Robman wrote:Here's the version 1 (S3C8):
3D 92 12 8B 16 49 05 08 00 84 01 75 00 84 03 87 83 C2 00 00 00 00 00 00 03 5F A0 48 05 37 40 06 28 03 77 26 29 03 0C 05 76 03 01 6B 0D E4 25 1C E4 26 1D 0C 03 09 12 E6 24 02 18 03 90 C1 0A FC 19 05 A6 0D 02 6B 0B B0 C6 F6 FF 58 37 61 02 7B F6 AF F6 FF 58 F6 FF 58 B0 C5 60 04 60 05 F6 01 46 F6 01 0A 7B 02 6C FF 60 C5 EB EE AF