From: Scott Baily <baily@us...> - 2002-04-30 00:00:12
At 06:10 AM 4/29/02 GMT, Christoph Bartelmus wrote:
>>> Menu 0x0000000000000012
>>> Ok 0x0000000000000817
>> Maybe they were learned incorrectly and changing them to 0x1012
>> and 0x1817 (to match the other buttons) would make it work?
>No, the codes are correct.
Well I'd certainly try this first before trying a workaround just in case.
>Andy, you're out of luck. WinLIRC is based on a LIRC release that
>incorrectly assumes that each RC5 code begins with a '1'. Current WinLIRC
>versions also won't analyse RC5 codes. Raw codes won't work because auf
>the toggle bit of the RC5 protocol. So, your current configuration is the
>optimum you can get with WinLIRC.
It is true that WinLIRC does not do a decent job of learning or analyzing
RC5 codes. And it certainly won't recognize them as being RC5, that code
is based on a very old version of LIRC (0.5.4pre9). But the receiving and
transmitting code is more up to date.
If RC5 codes have to start with 1 for winlirc to receive them, then please
let me know which LIRC version this was fixed in so I can find the correct
change to make, as fixing this should be easy. (And should be higher on my
priority list than adding RC6 support.)
Anyway, I think raw codes should work at least 50% of the time. and if you
use both codes then it should get them (just recognize them differently).
If use the raw codes as a separate remote, then you'll only need to have to
raw codes for Menu and Ok, because you can have multiple remotes in one
You seem to have a raw code sequence that works for Ok. You could probably
generate one from the lirc file.
I think menu should be something like:
1923 855 933 855 933 855 933 855 933 855 933 855 933 855 933 1710 1866 855
933 1710 1866 855
Note that the current version of the winamp plug-in ignores the remote
name, and only cares about the code name. (I suppose this is one of the
few cases where this could be called a FEATURE).
Sometimes you can trick winlirc into learning a remote by tapping the key
twice (instead of once) each time it asks you to press it.you can just use
the raw codes button on the reconfigure menu (since you only have to learn
you also might have more luck if you increase the error tolerance to around
50 when learning the remote.
Press the button once, then copy the data to a text file, then exit and do
this a couple of times just to make sure you didn't pick up some noise
instead of the remote signal. The code sequences should match
approximately. (except there will be two different results because of the
toggle bit). [toggle bit 2 just means that the 2nd bit toggles between 1
and 0 every other key press.]
This is why most of the codes alternate between 10xx and 18xx since 8 it
1000 in binary.
Anyway you can just paste a good one into the raw remote file (just remove
the text that says pulse or space).
Scott Baily "baily@..." wrote:
> If RC5 codes have to start with 1 for winlirc to receive them, then
> please let me know which LIRC version this was fixed in so I can find
> the correct change to make, as fixing this should be easy. (And should
> be higher on my priority list than adding RC6 support.)
CVS is your friend. I think the place to look at is the get_lead()
function. If the first bit is a '0' plead will be merged with the pulse of
the first bit.
> Anyway, I think raw codes should work at least 50% of the time. and if
> you use both codes then it should get them (just recognize them
> differently). If use the raw codes as a separate remote, then you'll
> only need to have to raw codes for Menu and Ok, because you can have
> multiple remotes in one configuration file.
Indeed, that's right. The only problem you might run into is when you want
to transmit RC5 codes. Then this workaround won't work. But if you only
want to receive codes it doesn't matter.