[mythtv-users] New 45-button hauppauge remote problem

[raptorjr]

Thank you for your help. But unfortunately it don't work.

As shown below, using the mode2 command, i get a lot of different
codes when pressing just one button. At this time i don't even use
the lircd.conf, just reading from the device and showing the hex values.
When i tried to make my own lircd.conf i got the same mess of hex
values with irrecord. I have tried to change batteries but no help there
either.
And if i use my old grey hauppauge i get the same hex value when
i press just one button. I think there must be something wrong with the
remote.
I am using the iMon inside ir-receiver that came with my Accent 400.
But that shouldn't be a problem since the old remote works?
I could always try with the ir-receiver on my pvr250.

Any more suggestions to find out if the remote is bad or if it is me?

/Stefan

----- Original Message ----- 
From: "Nick" <knowledgejunkie at gmail.com>
To: "Discussion about mythtv" <mythtv-users at mythtv.org>
Sent: Thursday, March 16, 2006 10:53 PM
Subject: Re: [mythtv-users] New 45-button hauppauge remote problem


On 16/03/06, raptorjr <raptorjr at hotmail.com> wrote:
> I wonder if anyone has a working setup with the new hauppauge 45-button
> remote?
> I recently bought one and have big problems. Dont know if it is the remote
> or lirc that is responsible.
> I also have the little older grey remote from hauppauge and that works
> perfect.
> This is what happends. With the old remote when i press f.ex. the Ok 
> button
> 10 times i get the following output with "mode2 -d /dev/lirc1":
>
> code: 0x2a828137
> code: 0x2a828137
> code: 0x2a828137
> code: 0x2a828137
> code: 0x2a828137
> code: 0x2a828137
> code: 0x2a828137
> code: 0x2a828137
> code: 0x2a828137
> code: 0x2a828137
>
> If i do the same thing with the new 45-button hauppauge remote i get this:
>
> code: 0x0ea99737
> code: 0x1aa99b37
> code: 0x06a99b37
> code: 0x12a99737
> code: 0x06a99337
> code: 0x1aa99b37
> code: 0x06a99b37
> code: 0x1aa99b37
> code: 0x06a99337
> code: 0x12a99337
>
> Do you see my problem? Impossible to map one key to all these codes. Dont
> know if there is any more codes than this for the Ok button. But more than
> one code is too much.
>
> So i wonder, is the remote broken? Or have hauppauge in some way changed 
> the
> protocol and lirc isn't treating it right? Would be interesting to hear
> other peoples experience with this new hauppauge remote.

If the remote is the current one
(http://registration.hauppauge.com/webstore/images/remote_small.jpg)
then make sure you are using the correct lircd.conf file. I'm using
one of these with no problems at all on a frontend system with the
serial receiver.

You can find the current lircd.conf here
(http://cvs.sourceforge.net/viewcvs.py/lirc/lirc/remotes/hauppauge/lircd.conf.hauppauge?view=markup)

The remote (as with all Hauppauge remotes) uses the RC5 protocol. I
would make sure you have the correct lircd.conf installed, then run
'irw' with the remote and see if the keys are consistently and
correctly identified. If you still see problems, such as keys not
being detected, or different output when pressing the same button,
check the batteries in the remote.

Nick
_______________________________________________
mythtv-users mailing list
mythtv-users at mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users