[mythtv-users] Help Setting up serial IR blaster for Comcast/Pace DC50X

[Brian Wood]

On Thursday 14 May 2009 08:46:52 Brad Fuller wrote:
> On Thu, May 14, 2009 at 6:29 AM, John H <arizonamythtv at gmail.com> wrote:
> >>> btw, lircd1 is not created by default. The following are default
> >>> device nodes that are created when lircd starts.
> >>> /dev/lirc0
> >>> /dev/lircd
> >>>
> >>> So, I think I'm fine here, since the only difference is the name. But,
> >>> tell me if I"m wrong.
> >>
> >>Those are the default devices created for a single instance of LIRC.
> >
> > Yes, /dev/lirc0 and /dev/lircd are the default devices that get
> > created at modprobe
> >
> > I believe if you start lirc with the command below then look at your
> > /dev folder you'll see a new device created called lircd1.
> > lircd --device=/dev/lirc0 --output=/dev/lircd1
> >
> > Then check lirc is going ps -A | grep lirc
> >
> > Then you just connect irsend to the socket and you should be good to go
> > irsend --device=/dev/lircd1 SEND_ONCE Remote_Name power
>
> Tried it. no go.
> I updated modules, I 'modprobe -r lirc_dev' then 'modprobe lirc_serial' too
>
> I also added
> options lirc_serial irq=4 io=0x3f8 type=0 softcarrier=1 txsense=0 debug=1
>
> that Nick suggested, but no go.
>
> (BTW, with debug=1 no new output to /var/log/messages is seen.)
>
> I should put some DC on the LED to see if it really lights!

Sounds like the time for standard electronic troubleshooting procedures:

Putting DC across the LED (in the forward direction) should cause it to 
illuminate, but be sure you limit the current somehow to prevent blowing up 
the LED.

Test the LED with an ohmeter. It shoud behave like any other diode, conducting 
more in the forward direction than the reverse.  I can't give you precise 
values, since ohmeters vary in the voltage they apply to the circuit under 
test, and you don't know where you are on the curve of the device.

Test all of the connections in your device somehow, either testing the 
connections with an ohmeter or somehow checking them. A visual inspection 
(which I'm sure you have done many times) often picks up problems.

Test the port somehow, perhaps with another device known to be working 
connected to the port.

It's sounding more and more like you have a hardware problem.

-- 
beww
beww at beww.org