On Fri 19 Sep 2008 at 18:51:44 -0700, Patrick Kirchner wrote:
> --- On Wed, 9/17/08, Ian Macdonald <ian@...> wrote:
> > I recently became the owner of a CommandIR II unit, as
> > However, a problem occurs when I hold down some keys on the
> > remote
> > I've tried messing around with ./daemons/hw_commandir.h
> > and increasing
> > Finally, I tried playing with commandir_read_loop() in
> > ./daemons/hw_commandir.c, so that the CommandIR II's
> > buffer is not
> > allowed to fill as much before hardware_scan() is called.
> > This, too,
> > Has anyone else experienced this problem? I have an
> > expensive CommandIR
> > II unit that I can't use until I figure out how to keep
> > it functional
> > over a sustained period of time. Having the thing die every
> > time keys on
> > the remote-control are held down is simply not workable.
> In short, it doesn't seem like a configuration issue,
> > because the unit
> > works perfectly until the moment that it stops working.
> > Then, it needs a
> > hard reset to bring it back to life.
> > Any help will be greatly appreciated.
> I'm also the not so proud owner of a Command IR II, not to mention 1st
> generation Command IR. For over three months I emailed back and forth
> with Matthew Bodkin at innovationone dot ca. I was never able to
> successfully get the Command IR to send the IR signals to my AT&T
> Uverse STB despite having the IR codes that work with a serial
> blaster. After three months of back and forth Matthew finally let me
> know that I helped him identify a problem with the Command IR and
> higher IR frequencies. He thought he had a fix for it and sent me a
> new lircd.conf file but alas, it also didn't help. I was finally
> sent, at no extra charge, a CommandIR II, but again, unfortunately, I
> wasn't able to get it working.
> I don't have much too offer in the way of support but can share my
> empathy with you. I certainly hope you can work out the issue your
Well, in the absence of a solution, I do appreciate the empathy!
In my case, it's a case if 'so near, but still so far'. The unit works,
but gives up the ghost when keys are repeated in quick succession. It's
close, but not close enough to be useable.
I've since discovered that the unit only dies when keys are held down
while MythTV is playing back a recording. If I quit MythTV or go to a
different screen in MythTV, I can have the same keys repeat with no ill
So, it's some kind of poor interaction between LIRC and MythTV.
Unfortunately, it's beyond my comprehension of LIRC to fix it.
Matthew Bodkin is getting married today and then going off on his
honeymoon, so any potential fix from him is still some weeks away at
this point. In the interim, I've had to give up on the unit.
Before he went, he did say that my problem is reminiscent of one he saw
during the beta cycle of the CommandIR II, but that one was caused by
sending signals to the unit before any software on the box had connected
to lircd to read the signals.
That's not what's happening in my case, because I have irexec constantly
polling and, besides, I don't press any keys until the MythTV front-end
has been fired up.
Ian Macdonald | Trespassers will be shot. Survivors will
ian@... | be prosecuted.