JP1 Remotes

[ron_by]

1. Device: Thomson DCI 5211
2. Type of device: Cable Box
3. Year: recent (2009-2010 i think)
4. JP1/UEI Remote model: Slingbox (no JP1 or UEI remote)
5. Do you have a JP1 cable? no
6. Still have original remote? yes
7. Checked the file section? yes
8. Checked Pronto file section (at R/C)? yes
9. Partially working setup code? no
10. Learning remote question? n/a

Thanks in advance

[alanrichey]

I've built a test remote for you at http://www.hifi-remote.com/forums/dload.php?action=file&file_id=8725

Although it uses a protocol I have never got to work yet. But there is always a first time

[ron_by]

Thanks very much.

My slingbox seems to have stopped working for some reason, so I can't test it now. But hopefully I'll get it working again tomorrow and then I'll be able to test it and see if it works. I'll report back here after I do that.

[ron_by]

Just tried it. Not working unfortunately.

No reaction at all. After the power button didn't work I went ahead anyway to check other buttons, but no luck. Playing with the placement of the IR thingies didn't do the trick either.

[alanrichey]

Pity. I assume you did the camera check on the blasters ?

As I said I wasn't confident as I have never managed to build a working remote with the Thomson IR protocol.

Have you checked out http://betaremotes.com to see if you build your own remote ?

[The Robman]

Alan, if you load your RM file, I can take a look to see if you did anything wrong. I might also need your ICT file to compare it with.
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

[alanrichey]

Sorry, thought it was already in. Added now.

And an ICT file for Power, 1, 2 & 3.

[The Robman]

Try creating a bin file using this RMDU file:
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=1562

This one also uses Thomson with device code 3 but the OBCs are different.

Plus, there appears to be a problem with the S3C8 code in protocols.ini, I think it should be replaced with this...

Code.S3C80=76 76 11 8B 0E C5 41 05 07 00 F2 03 ED 00 F2 08 \
DE 9C 2C 76 00 01 6B 03 B6 03 08 8D 01 46
_________________
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!

[alanrichey]

OK, new effort at http://www.hifi-remote.com/forums/dload.php?action=file&file_id=8737 using that RMDU file and the new code.

And the original one rebuilt with the changed code, http://www.hifi-remote.com/forums/dload.php?action=file&file_id=8725

ron_by: Do either of these work ?

[alanrichey]

Any luck ?

[ron_by]

no, didn't work.

sorry not reporting back here sooner. i thought i'd go get a new IR blaster cable, just in case that's where the problem lies (though I doubt it, since i did the camera check and it seemed fine), but haven't managed to get one yet.

any idea what the problem might be? anything else i should check?

[alanrichey]

Afraid all my ideas are in the Readme file. So maybe we still don't have the Thomson protocol right.

[ron_by]

got a new IR blaster cable and tried again, but still no luck.

any other ideas, anyone?

[vickyg2003]

Alan, do you have the same sling as ron-by? If so can you capture the sling output from your sling to irscope too?
_________________
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.

[alanrichey]

With great difficluty. But there is another problem now i have tried re-learning the codes and that is that some buttons decode as Thomson 3 and some as Thomson 35, and we can't use both in RM ?