Remote Master - Manual Settings

[johnsfine]

they ALL decode as Nokia32 See Diagnosis File

They really are Nokia32. They have no resemblence to RC6-6-20 signals.

I guess this device recognises both protocols. It sounds like it even uses the same set of OBC numbers for these two protocols. I haven't yet looked for the protocol executor for Nokia32. I don't even know if it is a UEI pid or one of our custom ones. But at the time I added that to DecodeIr, I apparently knew that it used MSB translation between OBC and EFC, which happens to be the same that the RC6 protocols use. So the match of OBC numbers results in a match of EFC numbers.

the Pace box may well use the same protocol and EFCs... I won't know till dad brings his remote control down...

If I understand that correctly, your dad has a Sky system of the type whose original remote natively generates the Sky (RC6-6-20) signals. So if you use his remote on your Sky system, it should work (as it would be the same signals as your upgrade now generates).

If you learn signals from his remote and decode them, you should be able to see that they really are RC-6-20 and DecodeIr does get that right.

What I'm really wondering is what would happen if you tried the remote that generates Nokia32 signals on his Sky system. Do all the Sky systems accept a second protocol, or just the one you have?

[harley]

<chuckle>

So am I lucky or is it just that you guys are smarter than me?

I am finding a quirk or two now that I look into it, but it could well be my imagination...

[harley]

OK, I don't have anything more to report except extended befuddlement.

I have 4 EFC's that are different between Silrons original file, and my 8910 learned codes.

Box Office: Silron = 169 Me = 100
Interactive/Active: Silron = 101 Me = 165
Planner: Silron = NA (maybe 193) Me = 109
AV: Silron = 238 Me = 211

Now I am at the point were this should go to code search, but....

If I learn those four Commands I get Nokia32 Dev 33 Sdev 160 and the EFC above (not matching Silrons). I also get misc X=38 (what's that mean, John?)

If I learn any of the other commands on the remote the output is exactly the same, save for the EFC matches what Silron originally posted.

Now - If we go back and use the KM generated protocol AND KM upgrade file AND silron's EFC's as above then those four buttons work. (the just took a little tweaking to Foxtel terminology)

So...

I'm going to let you chaps talk amongst yourselves for a while, most of what you say goes over my head, but if there's anything I can do to help solve this puzzle then please let me know.

[johnsfine]

I also get misc X=38 (what's that mean, John?)

I wish I knew. A Nokia32 signal has four values in it. One of those is the OBC number. I don't really know what the other three mean.

The interface between IR and DecodeIr allows for "device" and "subdevice", so I called two of the three non varying unknown values device and subdevice. Then I just called the last value "X".

So I really just know these signals all include the number 33, 160 and 38. I don't know what those three numbers mean. For practical JP1 purposes you don't need to know what they mean, just how to duplicate them.

Now - If we go back and use the KM generated protocol AND KM upgrade file AND silron's EFC's as above then those four buttons work.

I missed something. Did you ever tell us whether they worked using the learned EFC numbers? I assume the learned signals themselves work. Does this mean these four commands are different depending on the choice of protocol?

I'm going to let you chaps talk amongst yourselves for a while, most of what you say goes over my head, but if there's anything I can do to help solve this puzzle then please let me know.

Is there any more for us (experts) to say amongst ourselves about this?

It would be nice if one of us made a Nokia32 entry for protocols.ini. But I think that just requires effort, not communication.

Did you see my edits to my previous post in this thread? I'm still curious to know what a different brand of Sky device would do with the Nokia32 signals.

[The Robman]

Here's some additional info for y'all.

The actual code used by the URC-1633 B00 remote is SAT/1356, here's a copy of an upgrade formatted for the URC-8910...

Upgrade Code 0 = 7D 4C (SAT/1356)
73 00 F6 F4 3E C1 02 21 A0 26 00 01 02 03 04 05
06 07 08 09 10 11 0D 20 21 0C 0F 58 59 5A 5B 5C
CC 38 2C 30 29 28 31 37
End

Upgrade Protocol 0 = 01 73 (S3C8+)
47 93 41 8B 15 00 00 54 00 77 00 54 00 CA 00 54
01 1D 00 54 01 71 00 D0 00 77 A6 0D 02 EB 03 E6
0D 12 76 03 01 6B 08 76 00 01 6B 03 B6 06 80 F6
FF 56 6C 09 F6 01 0A FB 0B C6 F8 13 88 F6 01 58
6A F2 8B EB 76 03 02 EB 01 AF C6 F8 13 88 F6 01
58 6A F7 46 06 80 1C 22 F6 01 4C B0 C4 87 34 04
F6 FF 6C 4E 37 44 F6 1C 12 8D 01 4C 5C 04 90 C3
90 C3 08 C3 56 C0 03 86 04 C0 06 C1 12 F6 01 4C
5A EC AF
End

Regarding the 2-byte vs. 6-byte versions of the $0020 protocol, I just got a copy of the current official UEI version and it uses 5-bytes, here's a copy of SAT/0847 formatted for the URC-8910...

Upgrade Code 0 = 7E 4F (SAT/0847)
20 00 B6 F7 A9 30 55 55 55 00 01 02 03 04 05 06
07 08 09 20 21 0C CB 58 59 5A 5B 5C CC 83
End

Upgrade Protocol 0 = 00 20 (S3C8+)
47 93 51 8B 13 8E 04 08 08 00 DE 00 00 00 00 00
CC EE BA 05 35 01 A8 04 08 04 37 00 09 E6 0E 4D
E6 0F A0 F6 01 55 18 08 2C 08 CF 10 09 10 08 DF
10 09 10 08 90 C1 FB 03 B6 09 03 2A ED E6 10 02
E6 11 05 F6 01 46 C6 F8 01 2E F6 01 58 F6 01 0A
7B F1 AF
End

[mtakahar]

Greg,

If I open a KM upgrade with a custom protocol then save it as a .rmdu file, is the protocol supposed to be saved in the protocols.ini, .rmdu or somewhere else? Is there something I need to do to let RM save it, am I supposed to add it to protocols.ini manually, or would this be just another "more manual settings fix" candidate?

I'm seeing an error:
No protocol found with name="Roomba",ID=01 60, and variantName=""
when I reopen the created .rmdu file.

Here's what I did:
1. Start RM, Choose "File"/"Open..."
2. Anser "No" to "Save upgrade?"
3. Set "Files of Type" to "KeyMapMaster device upgrade files", choose iRobot_RoomBa.txt
4. "Sony TiVo ... Extender2 2K", click on "OK".
5. "Advanced"/"Manual Settings...", enter "Roomba" in the "Name:" field, click on "OK".
6. "File"/"Save as...", click on "Save" to accept the default name.
7. "File"/"Exit"
8. Repeat step 1 - 2, then choose iRobot_RoomBa.rmdu just created, then RM pops up the error I mentioned above.

I tried it on the latest v1.18.

Thanks,
Hal

[gfb107]

Hal,

If you leave out step 5 (renaming the manual protocol), it'll work just fine.

[mtakahar]

Ah, yes. It worked if I skip the step 5. I somehow thought I should name the protocol and it was a necessary step.

Hal