Thomson DCI 5211 HOT Cable Box
Moderator: Moderators
-
alanrichey
- Expert
- Posts: 3533
- Joined: Mon Mar 24, 2008 7:14 am
- Location: UK/USA
Interesting, you are right of course, I remember it. What has happened is that when I replaced the [Thomson] entry in PROTOCOLS.INI and then started RM and loaded the old RMDU file it seems to have changed the OBC codes as well as removing the Device column ?
Look like I will have to go through the learn process all over again.
Or maybe I should wait until DECODEIR is fixed.
Look like I will have to go through the learn process all over again.
Or maybe I should wait until DECODEIR is fixed.
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Rob, are you saying that the IRP is incorrect
IRP notation: {33k,500}<1,-4|1,-9>(D:4,T:1,D:1:5,F:6,1,^80m)+
With UEI executor being OBC Comp?
Is wrong? That's how I got to the correct hex for device 3, OBC 46 as being C4, which is 3 46.
I thought the protocols.ini entry was wrong.
IRP notation: {33k,500}<1,-4|1,-9>(D:4,T:1,D:1:5,F:6,1,^80m)+
With UEI executor being OBC Comp?
Is wrong? That's how I got to the correct hex for device 3, OBC 46 as being C4, which is 3 46.
I thought the protocols.ini entry was wrong.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
The Robman
- Site Owner
- Posts: 22026
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
They were all wrong.
I've come up with a better idea, given that we're probably not going to get DecodeIR fixed any time soon. The new protocols.ini entry below will let you use the displayed OBCs, as long as the displayed device code is < 32, and when the displayed device code is 32+ you will need to add 64 to the OBC to make it correct.
[Thomson]
PID=00 4B
VariantName=7
DefaultCmd=00
DevParms=Device:4=0
DeviceTranslator=Translator(lsb,comp,0,4)
FixedData=00
CmdParms=OBC:7=0
CmdTranslator=Translator(lsb,comp,0,6,1) Translator(lsb,comp,0,1,0,6)
DefaultCmd=00
Code.S3C80=76 76 11 8B 0E C5 41 05 07 00 F2 03 DC 00 F2 08 BE 9C 40 31 02 27 07 03 31 C2 8D 01 46
Code.HCS08=20 11 3C 3C 11 C5 41 05 07 00 E5 04 01 00 E5 08 F2 9C 40 01 B3 06 B6 60 A8 08 B7 60 CC FF 5F
Code.740=0F 1D 11 80 0C E0 A2 01 10 05 07 03 97 06 E0 4E 14 17 5A 02 6F 5D 4C 00 FF
I've come up with a better idea, given that we're probably not going to get DecodeIR fixed any time soon. The new protocols.ini entry below will let you use the displayed OBCs, as long as the displayed device code is < 32, and when the displayed device code is 32+ you will need to add 64 to the OBC to make it correct.
[Thomson]
PID=00 4B
VariantName=7
DefaultCmd=00
DevParms=Device:4=0
DeviceTranslator=Translator(lsb,comp,0,4)
FixedData=00
CmdParms=OBC:7=0
CmdTranslator=Translator(lsb,comp,0,6,1) Translator(lsb,comp,0,1,0,6)
DefaultCmd=00
Code.S3C80=76 76 11 8B 0E C5 41 05 07 00 F2 03 DC 00 F2 08 BE 9C 40 31 02 27 07 03 31 C2 8D 01 46
Code.HCS08=20 11 3C 3C 11 C5 41 05 07 00 E5 04 01 00 E5 08 F2 9C 40 01 B3 06 B6 60 A8 08 B7 60 CC FF 5F
Code.740=0F 1D 11 80 0C E0 A2 01 10 05 07 03 97 06 E0 4E 14 17 5A 02 6F 5D 4C 00 FF
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
yes, but can you get the dev column to appear and put the dev in the first bit and then 06 bits in the function portion? If so its pretty easy in RM to enter the hex.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
The Robman
- Site Owner
- Posts: 22026
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
Man, figuring out how to set the protocols.ini variables is REALLY difficult, but I think I got it working...vickyg2003 wrote:yes, but can you get the dev column to appear and put the dev in the first bit and then 06 bits in the function portion? If so its pretty easy in RM to enter the hex.
[Thomson]
PID=00 4B
VariantName=7
DefaultCmd=00
DevParms=Device:4=0
DeviceTranslator=Translator(lsb,comp,0,4)
FixedData=00
CmdParms=Device:Dev. 1|Dev. 2,OBC:6=0
CmdParmInit=ParmInitializer(0,0,5,1)
CmdTranslator=Translator(0,1,comp) Translator(lsb,comp,1,6,1)
DefaultCmd=00
Notes=This executor will let you combine two Thomson device codes, where the second device code is 32 greater than the first. Enter the first (lower) device code.
Code.S3C80=76 76 11 8B 0E C5 41 05 07 00 F2 03 DC 00 F2 08 BE 9C 40 31 02 27 07 03 31 C2 8D 01 46
Code.HCS08=20 11 3C 3C 11 C5 41 05 07 00 E5 04 01 00 E5 08 F2 9C 40 01 B3 06 B6 60 A8 08 B7 60 CC FF 5F
Code.740=0F 1D 11 80 0C E0 A2 01 10 05 07 03 97 06 E0 4E 14 17 5A 02 6F 5D 4C 00 FF
[Thomson (old)]
PID=00 4B
DefaultCmd=00
DevParms=Device:6=0
DeviceTranslator=Translator(lsb,comp,0,4) \
Translator(comp,0,1,5,5)
FixedData=00
CmdParms=OBC:6=0
CmdTranslator=Translator(lsb,comp,0,6)
DefaultCmd=00
Notes=This is the older version of the Thomson executor, found in remotes like the URC-7560. You can use this as long as all the buttons use the same device code. If you have two device codes, switch to the newer version.
Code.S3C80=76 76 11 8B 0E C5 41 06 06 00 F2 03 DC 00 F2 08 BE 9C 40 31 02 27 07 03 31 C2 8D 01 46
Code.HCS08=20 11 3C 3C 11 C5 41 06 06 00 E5 04 01 00 E5 08 F2 9C 40 01 B3 06 B6 60 A8 08 B7 60 CC FF 5F
Code.740=0F 1D 11 80 0C E0 A2 01 10 06 06 03 97 06 E0 4E 14 17 5A 02 6F 5D 4C 00 FF
Last edited by The Robman on Thu Sep 09, 2010 12:43 pm, edited 1 time in total.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
-
The Robman
- Site Owner
- Posts: 22026
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
Any word, Alan and/or Vicky?
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
-
alanrichey
- Expert
- Posts: 3533
- Joined: Mon Mar 24, 2008 7:14 am
- Location: UK/USA
-
The Robman
- Site Owner
- Posts: 22026
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
You should replace all the Thomson entries in protocols.ini with the 2 entries that I created. The only reason that I created the "old" version was so that people with remotes that have the older version of the executor will still be able to create upgrades that don't require a protocol upgrade.
In the current protocols.ini, the two versions also represent the old and new versions of the executor, but as they use the same name, the user cannot control which one is used. The old version only has 740 code because that's all that whoever added it decided to add. Likewise, the newer version was missing the 740 code because the person who added the code didn't bother to generate it. I added all code versions to both Thomson versions.
In the current protocols.ini, the two versions also represent the old and new versions of the executor, but as they use the same name, the user cannot control which one is used. The old version only has 740 code because that's all that whoever added it decided to add. Likewise, the newer version was missing the 740 code because the person who added the code didn't bother to generate it. I added all code versions to both Thomson versions.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
I'm glad to year YOU say it. I worked on that for hours with no results.The Robman wrote: Man, figuring out how to set the protocols.ini variables is REALLY difficult, but I think I got it working...
I have tried and tried to read the comments section of protocols.ini to figure out what I need to do. Is there more documentation that I'm not seeing?
I actually hadn't seen your post, it wasn't showing up on my new posts.
I'll try to take a look but I really need to find a s3c8+ remote since my jp1.2/3 cable is out of commission.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
The Robman
- Site Owner
- Posts: 22026
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
I read the documentation a hundred times and it didn't help. The only reason I figured it out was because I noticed that the Akai protocol was doing something similar, so I copied the entry for that protocol and kept tweaking it until it did what I want.
If you need an S3C8+ remote, I can send you one.
If you need an S3C8+ remote, I can send you one.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
-
alanrichey
- Expert
- Posts: 3533
- Joined: Mon Mar 24, 2008 7:14 am
- Location: UK/USA
OK, let's hope ron_by is still monitoring the thread.
How about this Custom Remote ?
https://www.hifi-remote.com/forums/dload ... le_id=8927
How about this Custom Remote ?
https://www.hifi-remote.com/forums/dload ... le_id=8927
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Thank-you. I thought I was just being a dimwit. If you understand what you've done well enough to explain it I'd love to hear about it.The Robman wrote:I read the documentation a hundred times and it didn't help. The only reason I figured it out was because I noticed that the Akai protocol was doing something similar, so I copied the entry for that protocol and kept tweaking it until it did what I want.
I have plenty of s3c8+ JP1 remotes, the problem is they are all in-use or in FL. It was just finding one that I could use on the bench that was the problem. I went on a remote hunt and found I had URC-6011's in the guest room that won't be missed, there is still one remote in there. If I have guests they'll just have to share a remote!If you need an S3C8+ remote, I can send you one.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
alanrichey
- Expert
- Posts: 3533
- Joined: Mon Mar 24, 2008 7:14 am
- Location: UK/USA
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Yes, its too bad that he didn't stick around for the payoff.
However this fixed the thomson protocol for everybody so it was time well spent.
However this fixed the thomson protocol for everybody so it was time well spent.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
alanrichey
- Expert
- Posts: 3533
- Joined: Mon Mar 24, 2008 7:14 am
- Location: UK/USA