JP1 Remotes

fichmana2003 · Joined: 30 Dec 2003 Posts: 49

Just got my 8811 and went exploring. I decided to get my cable box (Thomson) in first so got the remote and was shocked to see the UEI symbol on the back (never noticed it before). opened the batt lock and there is the JP1 connector!
So I decided to look inside this remote first. IR.EXE identified it as a FORCE remote and under the Devices tab was the complete cable box data as an upgrade. So, I copied it to RM one by one, assigned the keys and tried it... The buttons work (mostly), but are all scrambled up - '1' is 4, '0' is power etc.
looked at the data and saw that "Fixed Data" is 34 on my FORCE remote (the original) and 30 on my upgrade, with no posibility to change it.
what did I do wrong?

thanks!
_________________
alexf

ddsmith60 · Joined: 20 Dec 2003 Posts: 34

I don't think there is an easy way to go backwards so to speak. What I would do if I was you would be to learn a command or two to the 8811. Then plug it in to IR.EXE and see what it shows under learned signal tab. This should give you the information needed for the upgrade code protocol. You may be able to utilize the efc's you already have when you determine the protocol required to be entered in RM. I hope that is correct. I'm use to using KM not RM but I'm sure Robman or one of the many other experts will be along sometime soon to help.

johnsfine · Posted: Tue Dec 30, 2003 6:16 pm Post subject:

I never heard of a FORCE remote, but if IR.EXE identified it, you must have an RDF for it.

If you copied button definitions accuratly but the results were scrambled, maybe that RDF doesn't have correct details for that remote. Digits are especially hard to get correct enough in an RDF that IR can correctly display an upgrade.

However, another possibility is that the FORCE uses the other version of pid 004B than the one the 8811 uses. In that case the EFC numbers are wrong. It is then just an accident when one key's wrong EFC happens to be another key's right EFC (vs. an RDF error in which every key's wrong EFC is necessarily another key's right EFC because the EFCs are right and the keys are wrong).

Since IR can't tell you the OBC numbers you'd need RM to translate the EFC numbers. My best guess is the 7541 would use the same EFC numbers as your remote, so you could switch the upgrade's choice of remote to 7541 and put in EFC numbers from IR.EXE then switch RM back to 8811 and RM should preserve the OBC values created from those EFCs and compute the new EFC values that fit the 8811.

RM also thinks that Thomson device 3 is fixed data 34 on the 7541 but device 3 is fixed data 30 on the 8811, so your fixed data difference is probably also due to the difference in versions of pid 004B.

fichmana2003 · Joined: 30 Dec 2003 Posts: 49

I learned the 0-9 numbrt keys from the otiginal, and the EFC codes are the same. The odd thing is IR.EXE, while also stating the correct EFC's, gives me funny data on the learned keys (more than one line, sometimes 3).
While one of the lines always states the correct Thomson protocol (4B), it always gives the EFC's in the format "xxx OR yyy", when one of the choices is the one I also have assigned on the original. All the learned numeric buttons work correctly.

John, what is this 7541 you are talking about? I am a newbie at JP1, so some of the things you said went right over my head...
_________________
alexf

johnsfine · Posted: Tue Dec 30, 2003 7:14 pm Post subject:

The URC-7541 is a model of OFA remote that you can find on RM's pull down menu of which remote model you want to build an upgrade for. (I think all the 75xx models: 7544, 7560, etc. actually do Thomson the same so it wouldn't matter which you choose).

When you decode a learned signal, IR displays both the EFC number that a 7541 etc. would use for that signal and the EFC that an 8811 would use. I forget which is which but it's consistent (whichever is first in one decode is first in all decodes).

When you look at your preloaded upgrade (in that remote I've never heard of) in IR's devices tab, it only shows one EFC. I think that is the EFC a 7541 would use and not the EFC an 8811 would use.

johnsfine · Posted: Tue Dec 30, 2003 7:20 pm Post subject:

BTW, my decoder (used by IR.EXE) frequently gives extra lines, that are nonsense decodes, before or after (or both) the real decode.

Usually it is easier for a human than a program to distinguish the real decodes and ignore the nonsense. If you didn't start out knowing that the "Thomson" are real and the others nonsense, the usual hint is that the real decode should appear at least once on almost every key with a consistent protocol and device number and with varying OBC numbers (different keys have different OBC numbers). The nonsense decodes probably are less consistent about protocol name or device number (or whether they're there at all) and/or too consistent about OBC number.

jamesgammel · Posted: Tue Dec 30, 2003 7:24 pm Post subject:

The rdf for the force remote bundled with the 1.0 version doesn't have the protocols list. If that's the rdf you are using, then RM wouldn't know just which version of PID 0048 the force remote has native.
Jim

Mark Pierson · Posted: Tue Dec 30, 2003 7:26 pm Post subject:

johnsfine · Posted: Tue Dec 30, 2003 7:39 pm Post subject:

fichmana2003 · Joined: 30 Dec 2003 Posts: 49

fichmana2003 · Joined: 30 Dec 2003 Posts: 49

Uploaded file "THOMSON DCI46GC.rmdu" to RM Upgrades section in Yahoo Groups for anyone who needs it.
_________________
alexf

usblipitor · Joined: 10 Oct 2003 Posts: 516 Location: Greenbelt, MD

johnsfine · Posted: Wed Dec 31, 2003 9:40 am Post subject:

Mark Pierson · Posted: Wed Dec 31, 2003 11:27 am Post subject:

fichmana2003 · Joined: 30 Dec 2003 Posts: 49