Probleme MX500, OFA8811 and JP1

[fish95]

Hi,

first, excuse me for my english but i'm french...

i have learned signal from my thomson's tv with my 8811. After that i have created a device, and automatically create an upgrade protocol (Why ? What does it mean?). It work very good but when i want send the signal from my 8811 to my mx500 it doesn't work very well : It a function button wich repeat the same action several time (go down in a list by example). It work with 8811 but it go down only one time with my mx500

Help me please...

Lionel

[The Robman]

Hi Lionel,
For us to better understand what is happening, we would need to see 2 files from you:

1) the file saved from IR.exe that shows your learned signals
2) the file saved from KM that shows the upgrade that you created

Could you please zip them together and load them into the Diagnosis Area folder at Yahoo.

[johnsfine]

i have learned signal from my thomson's tv with my 8811. After that i have created a device, and automatically create an upgrade protocol (Why ? What does it mean?).

An upgrade protocol is produced when KM or RM (I don't know which you used) decides the required protocol isn't included in your model of remote (8811). You didn't mention the protocol name, but I assume it is Thomson protocol or some other close relative of RECS80 protocol. Those are mainly used in European devices, so likely to be missing from the 8811.

It work very good but when i want send the signal from my 8811 to my mx500 it doesn't work very well : It a function button wich repeat the same action several time (go down in a list by example). It work with 8811 but it go down only one time with my mx500

RECS80 (and all the protocols similar to it) switches back and forth between two different versions of each signal. I assume the 8811 is working correctly and also alternates between two different versions.

But the mx500 learned only one of the two versions of each key, so it can't correctly send the same key twice in a row. The device only accepts the same command twice in a row when it is the two different versions of the command, not when it is the same version twice.

There are several ways to work around the problem, but I don't know enough about mx500's to provide details. Maybe you should try an mx500 forum and ask how to handle a protocol with a "toggle bit".