8810 device multiplexer help needed
Moderator: Moderators
-
zaphod7501
- Posts: 539
- Joined: Mon Aug 02, 2004 7:07 pm
- Location: Peoria Illinois
8810 device multiplexer help needed
Sorry to bother but I don't have Excell to get the device and protocol upgrades for the Device Multiplexer from the special protocols spreadsheet. I was wondering if someone could help me out. It's for the URC-8810 remote. I'm using the extender version 3 (3.2 I believe) The extender for my 6131 had it built in but the 8810 didn't.
Just call me Zaphod (or Steve) --- I never should have started using numbers in a screen name but I just can't stop now.
-
zaphod7501
- Posts: 539
- Joined: Mon Aug 02, 2004 7:07 pm
- Location: Peoria Illinois
Thanks for trying but still no go. My problem seem similar to this I've found several versions but they don't seem to work in the extender. I've run through a lot of the old Yahoo forum , but there are 29000 entries and the search feature doesn't work well.
I found this one in the source directory for special protocols.
Upgrade protocol 0 = 01 FE (S3C80)
00 00 12 08 68 CF 10 C0 C4 04 C4 97 40 4E 97 50
4F AF
End
And this one in a discussion thread.
Upgrade protocol 0 = 01 FE (S3C8)
00 00 02 08 7E 02 00 06 C0 4E F5 03 C0 83 C0 04
AF
End
And yours.
Upgrade Protocol 0 = 01 FE (S3C8+) Multiplexer
00 00 02 08 66 02 00 06 C0 4E F5 03 C0 83 C0 04
AF
End
I had thought that the solution was to read the Exel special protocol spreadsheel but it looks like that doesn't list a version for the extender I'm using and I have no idea how to modify the protocol as mentioned in the link I found above. I think the ones I've found are probably for the non-extended 8810.
I found this one in the source directory for special protocols.
Upgrade protocol 0 = 01 FE (S3C80)
00 00 12 08 68 CF 10 C0 C4 04 C4 97 40 4E 97 50
4F AF
End
And this one in a discussion thread.
Upgrade protocol 0 = 01 FE (S3C8)
00 00 02 08 7E 02 00 06 C0 4E F5 03 C0 83 C0 04
AF
End
And yours.
Upgrade Protocol 0 = 01 FE (S3C8+) Multiplexer
00 00 02 08 66 02 00 06 C0 4E F5 03 C0 83 C0 04
AF
End
I had thought that the solution was to read the Exel special protocol spreadsheel but it looks like that doesn't list a version for the extender I'm using and I have no idea how to modify the protocol as mentioned in the link I found above. I think the ones I've found are probably for the non-extended 8810.
Just call me Zaphod (or Steve) --- I never should have started using numbers in a screen name but I just can't stop now.
Is the one comes with the 6131 extender working for you?
The one I posted is supposed to work in the same way, changes the code associated to the "O" device. If you wanted to change code for the "A"ctive device, then you can try replacing 66 at the 5th byte with 69.
I chose "O" instead of "A" because I find it a bit confusing as the "A" device changes depending on what key you use for the multiplexer.
Hal
The one I posted is supposed to work in the same way, changes the code associated to the "O" device. If you wanted to change code for the "A"ctive device, then you can try replacing 66 at the 5th byte with 69.
I chose "O" instead of "A" because I find it a bit confusing as the "A" device changes depending on what key you use for the multiplexer.
Hal
-
zaphod7501
- Posts: 539
- Joined: Mon Aug 02, 2004 7:07 pm
- Location: Peoria Illinois
OOPS , I took the calculated value for the new device codes from my 6131 worksheet without changing the remote type to 8810 so my hex codes are wrong (20 21 for vcr0033 with the 6131 probably should have been 10 21 for the 8810). My codes were probably not valid , so nothing changed from the previous code (which was VCR 0033).
Your protocol was probably working but I was sending invalid device codes.
Quick check --- now it works , Just need to clean up all my experimenting.
Thanks very much for your help , it's a steep learning curve but the results are worth it.
Your protocol was probably working but I was sending invalid device codes.
Quick check --- now it works , Just need to clean up all my experimenting.
Thanks very much for your help , it's a steep learning curve but the results are worth it.
Just call me Zaphod (or Steve) --- I never should have started using numbers in a screen name but I just can't stop now.