Page 2 of 4
Posted: Tue Sep 07, 2010 3:29 pm
by The Robman
This is coming from the Slingbox? If so, that implies that UEI has already created a Thomson combo protocol. Can you tell what setup code you are using?
Posted: Tue Sep 07, 2010 3:45 pm
by alanrichey
No, I am still at the stage of doing a proper learn from the Harmony Remote So we can do a comparison. I'll build another ICT file so you can see what I mean.
And I have to say the OBC codes don't make much sense either. With 'good' remotes you tend to see that Ch+ and CH- are one code apart. Same with Skip+ and Skip-. This one has the codes all over the place. Makes me wonder if DECODEIR is not working properly for that protocol.
Back when I can build the file.
Al
Posted: Tue Sep 07, 2010 3:57 pm
by alanrichey
Sorry, ignore previous comments, I just noticed the Thomson IR Protocol in RM does support another device, but in the Functions TAB rather than the Setup TAB. I'll carry on with building the files.
Posted: Tue Sep 07, 2010 4:54 pm
by alanrichey
OK, there is definately a mismatch here. I picked 7 buttons at random and got the following results:
Code: Select all
Sling Harmony
OBC Device OBC Device
Power toggle 23 03 46 03
6 17 03 34 03
Up Arrow 05 35 11 03
Exit 02 35 05 03
Red 22 03 44 03
Play 56 03 48 35
Stop 44 03 24 35
(
Later: OK that didn't work
. All the spaces got stripped. Basically the 5 columns are 'Button', OBC Sling, Device Sling, OBC Harmony, Device Harmony)
I trust the Harmony ones a bit more as all the normal buttons use Device 3 and the PVR buttons use Device 35. So something is changing in translation in RM.
The 2 ICT files for those buttons are at
https://www.hifi-remote.com/forums/dload ... le_id=8898
Posted: Tue Sep 07, 2010 5:22 pm
by vickyg2003
Okay, I'm a little confused.
Is the Harmony remote is what you used to create fill in the information?
And
Is the Sling ICT what we are sending out from the upgrade you created?
If both answers are "yes", this would certainly be the reason you've 'never been able to get this protocol to work'.
Which RDMU is the one that gave you the garbage?
Posted: Tue Sep 07, 2010 6:47 pm
by alanrichey
vickyg2003 wrote:Okay, I'm a little confused. Is the Harmony remote is what you used to create fill in the information?
Yes, I don't have access to the real remote so I installed the device on my Harmony
vickyg2003 wrote:Is the Sling ICT what we are sending out from the upgrade you created? If both answers are "yes", this would certainly be the reason you've 'never been able to get this protocol to work'.
Yes. Basically the information I am putting into RM is not being replicated when I install the upgrade to the Slingbox. Does the same happen with a JP1 remote ? Does the output match the input ?
vickyg2003 wrote:Which RDMU is the one that gave you the garbage?
A new one I built, I have added it to the 2 ICT files.
Al
Posted: Tue Sep 07, 2010 7:42 pm
by vickyg2003
Good news, its just a problem with Protocols.ini
The Hex for the buttons is not correct.
I'm just not sure how to fix it.
Posted: Tue Sep 07, 2010 8:15 pm
by The Robman
vickyg2003 wrote:Good news, its just a problem with Protocols.ini
The Hex for the buttons is not correct.
I'm just not sure how to fix it.
What did you find?
Posted: Tue Sep 07, 2010 8:28 pm
by vickyg2003
The Thomson Command byte hex isn't being set correctly because the dev bit and the function bits are in the wrong order.
The Dev is 1 bit
The Function is 6bots
The command byte hex should be
dffffffx
I've been looking at the code, but I can't decipher what the translator numbers mean.
[Thomson]
PID=00 4B
VariantName=7
DefaultCmd=00
DevParms=Device:4=0
DeviceTranslator=Translator(lsb,comp,0,4)
FixedData=00
CmdParms=OBC:6=0,Dev:0|1
CmdTranslator=Translator(lsb,comp,0,6) Translator(comp,1,1,6)
CmdParmInit=ParmInitializer(1,0,5,1)
DefaultCmd=00
Posted: Tue Sep 07, 2010 10:01 pm
by vickyg2003
hmm, it appears that the function is not right justified in DCBUF+1
dffffffx
C4 = dEV 3 , OBC 46 (the power button)
44 = dev 35 OBC 46
That's part of why the function was nearly half the value it should be.
The reason most of the OBC's were about 1/2 of what they should be was that they were shifted 1, essentially dividing them by 2, the other part is that the dev is going in bit 1, (ffffffdx). So that was changing the OBC value too.
So I played and played with the Thomson, but protocols.ini is even harder than the RDF's. I can't figure out how to make the new entries.
Posted: Wed Sep 08, 2010 1:00 pm
by The Robman
I've looked into this and it appears that UEI used to regard the Thomson protocol as having a 6-bit device code and a 6-bit OBC, and this is how they originally setup the executor. Then, at some point, they discovered that it really has a 5-bit device code and a 7-bit OBC, so they modified their executor.
Unfortunately, it appears that we followed the 6-6 format instead of the 5-7 format, so DecodeIR is decoding the signal as 6-6. I will put a request in for DecodeIR be fixed, but in the meantime, here's what you need to do. I have created a new protocols.ini entry for Thomson below.
To correct the OBCs given by DecodeIR you should multiply them by 2, and when the device code given is greater than 31, you should add 1 to them also. So, for example, if DecodeIR says "dev 3, OBC 46", the real OBC is 92 (ie, 46*2). If DecodeIR says "dev 35, OBC 24", the real OBC is 49 (ie, 24*2 + 1)
[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,7)
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
Posted: Wed Sep 08, 2010 1:16 pm
by 3FG
If DecodeIR says "dev 35, OBC 24", the real OBC is 49 (ie, 24*2 + 1)
And the real device is 3 rather than 35, right?
Also, perhaps I don't understand what you're doing, but I think
DevParms=Device:4=0
should instead be
DevParms=Device:5=0
Posted: Wed Sep 08, 2010 1:26 pm
by alanrichey
I assume we use '3' as the device code, even when it has decoded as 35 ?
Posted: Wed Sep 08, 2010 1:30 pm
by alanrichey
And the Play button decodes as 35:112 but when I try and change the OBC to 225 it tells me I am limited to 0-127.
Al
Posted: Wed Sep 08, 2010 2:02 pm
by The Robman
alanrichey wrote:I assume we use '3' as the device code, even when it has decoded as 35 ?
Yes, because 35 - 32 = 3, and because the Thomson protocol only supports one device code.
alanrichey wrote:And the Play button decodes as 35:112 but when I try and change the OBC to 225 it tells me I am limited to 0-127.
It displays as "dev 35, OBC 48" when I look at your Harmony.ict file, where are you seeing 112? The correct OBC is 97 (ie, 48*2 plus 1)
3FG wrote:Also, perhaps I don't understand what you're doing, but I think
DevParms=Device:4=0
should instead be
DevParms=Device:5=0
Good eyes, the 5th bit is the toggle bit, it's not part of the device code itself.