Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

getting irblaster(.info) to work

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


greg at gregandeva

Apr 21, 2009, 10:01 AM

Post #1 of 7 (1021 views)
Permalink
getting irblaster(.info) to work

I am having trouble getting my new serial IR blaster (the one from
irblaster.info) to work. I have followed steps in various howto guides I
have found, all of which seem quite out of date. Is there one that is up
to date for Fedora 10, Myth trunk, and lirc 0.8.4a?

Discussions I have been able to find in the list archives seem to be
specific to the PVR-150's blaster.

The problem I have is, although both copies of lircd are running
and /dev/lircd1 exists, irsend always fails:

irsend: command failed: SEND_ONCE Motorola_DCT6200 6
irsend: transmission failed

I have specified the correct device on the irsend command line as far as
I can tell: "irsend --device=/dev/lircd1". /dev/lircd1 is 0666 (writable
by all) so I don't think it's a permission issue.

Is it necessary to compile lirc from source to make this work?

I have installed the remote config for the Motorola_DCT6200 into my
lircd.conf, I have lirc_serial loaded with the correct irq and io
parameters (my PC has only one serial port and only ttyS0 shows up in
dmesg, but I tried the values for ttyS1 as well with no joy). Of course
in order to get lirc_serial to load, I did have to (and did) run
"setserial /dev/ttyS0 uart none".

Any ideas on how I can troubleshoot this? Any other info I could supply
that would help?

Thanks,
--Greg


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


c.assemvanhaaften at chello

Apr 21, 2009, 11:08 AM

Post #2 of 7 (983 views)
Permalink
Re: getting irblaster(.info) to work [In reply to]

Greg Woods schreef:
> I am having trouble getting my new serial IR blaster (the one from
> irblaster.info) to work. I have followed steps in various howto guides I
> have found, all of which seem quite out of date. Is there one that is up
> to date for Fedora 10, Myth trunk, and lirc 0.8.4a?
>
> Discussions I have been able to find in the list archives seem to be
> specific to the PVR-150's blaster.
>
> The problem I have is, although both copies of lircd are running
> and /dev/lircd1 exists, irsend always fails:
>
> irsend: command failed: SEND_ONCE Motorola_DCT6200 6
> irsend: transmission failed
>
> I have specified the correct device on the irsend command line as far as
> I can tell: "irsend --device=/dev/lircd1". /dev/lircd1 is 0666 (writable
> by all) so I don't think it's a permission issue.
>
> Is it necessary to compile lirc from source to make this work?
>
> I have installed the remote config for the Motorola_DCT6200 into my
> lircd.conf, I have lirc_serial loaded with the correct irq and io
> parameters (my PC has only one serial port and only ttyS0 shows up in
> dmesg, but I tried the values for ttyS1 as well with no joy). Of course
> in order to get lirc_serial to load, I did have to (and did) run
> "setserial /dev/ttyS0 uart none".
>
> Any ideas on how I can troubleshoot this? Any other info I could supply
> that would help?
>
> Thanks,
> --Greg
>

I have a mce receiver/transmitter and a serial IR Blaster.
On OpenSUSE 11.1, I need to compile the serial module everytime when I
install a new kernel.
I've also installed the default packages and replace the lirc_serial.ko
(/lib/modeles....kernelversion....) with the one I compiled myself.
I used for both the same version, 0.8.4a.

This is my .setup.config, located in the lirc-0.8.4a folder:

LIRC_DRIVER=serial
LIRC_PORT=0x3f8
LIRC_IRQ=4
LIRC_MAJOR=61
IRTTY=none
DRIVER_PARAM_TYPE=
DRIVER_PARAMETER=com1
SOFT_CARRIER=on
TRANSMITTER=on
IGOR=off
TIMER=65536
X11_WINDOWS=on
DEBUG=off
NO_DAEMONIZE=off
NO_LONG_CODES=off
USE_SYSLOG=off
DYNCODES=off


Hopes this helps you.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


greg at gregandeva

Apr 21, 2009, 11:11 AM

Post #3 of 7 (962 views)
Permalink
Re: getting irblaster(.info) to work [In reply to]

On Tue, 2009-04-21 at 20:08 +0200, Wilfred van den Assem wrote:

> On OpenSUSE 11.1, I need to compile the serial module everytime when I
> install a new kernel.

I guess I'd like to hear from people who have an irblaster.info device
working. Do you really have to compile lirc and/or the kernel from
source for this to work, even with a relatively recent OS like Fedora
10?

--Greg


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


knowledgejunkie at gmail

Apr 21, 2009, 1:29 PM

Post #4 of 7 (977 views)
Permalink
Re: getting irblaster(.info) to work [In reply to]

On 21/04/2009, Greg Woods <greg [at] gregandeva> wrote:

> I guess I'd like to hear from people who have an irblaster.info device
> working. Do you really have to compile lirc and/or the kernel from
> source for this to work, even with a relatively recent OS like Fedora
> 10?

My IR blaster is running on a FC4/2.6.16 kernel, which was released
long before LIRC was added to the mainline kernel.

When you modprobe lirc_serial (either automatically via
/etc/sysconfig/lirc.modules, or manually in rc.local) do you get a
/dev/lirc1 device created, and are you starting the second instance of
LIRC pointing to this device? The /dev/lirc1 device will need
read/write permissions.

What is the output of:

$ ls -la /dev/lirc*

In "the olden days" you had to compile a second differently-named
instance of LIRC when you wanted two separate devices to share the
same LIRC kernel module (I still believe this is the case today, but
could well be wrong). Commonly this was because a user had a serial
receiver on COM1 and a serial transmitter on COM2. Atter running with
two instances of LIRC for some time, I got the soldering iron out and
put the transmitter and receiver on the same socket, which simplified
things greatly and let a single LIRC instance control everything.

Nick

--
Nick Morrott

MythTV Official wiki:
http://mythtv.org/wiki/
MythTV users list archive:
http://www.gossamer-threads.com/lists/mythtv/users

"An investment in knowledge always pays the best interest." - Benjamin Franklin
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


greg at gregandeva

Apr 21, 2009, 1:30 PM

Post #5 of 7 (988 views)
Permalink
Re: getting irblaster(.info) to work [In reply to]

There is clearly something fundamental that I do not understand about
how to configure this. I noticed this in /var/log/messages:

Apr 21 14:26:29 confusion lircd-0.8.4a[2538]: accepted new client
on /dev/lircd1
Apr 21 14:26:29 confusion lircd-0.8.4a[2538]: invalid send buffer
Apr 21 14:26:29 confusion lircd-0.8.4a[2538]: this remote configuration
cannot be used to transmit
Apr 21 14:26:29 confusion lircd-0.8.4a[2538]: error processing command:
SEND_ONCE Motorola_DCT6200 enter
Apr 21 14:26:29 confusion lircd-0.8.4a[2538]: transmission failed
Apr 21 14:26:29 confusion lircd-0.8.4a[2538]: removed client

Is there something I need in lircd.conf other than the standard
configuration for the DCT6200 remote?

--Greg


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


greg at gregandeva

Apr 21, 2009, 1:41 PM

Post #6 of 7 (969 views)
Permalink
Re: getting irblaster(.info) to work [In reply to]

On Tue, 2009-04-21 at 21:29 +0100, Nick Morrott wrote:


> When you modprobe lirc_serial (either automatically via
> /etc/sysconfig/lirc.modules, or manually in rc.local) do you get a
> /dev/lirc1 device created

Looks like it:

# ls -l /dev/lirc*
lrwxrwxrwx 1 root root 5 2009-04-21 14:25 /dev/lirc -> lirc0
crw-rw---- 1 root root 61, 0 2009-04-21 14:25 /dev/lirc0
crw-rw---- 1 root root 61, 1 2009-04-21 14:32 /dev/lirc1
srw-rw-rw- 1 root root 0 2009-04-21 14:32 /dev/lircd
srw-rw-rw- 1 root root 0 2009-04-21 14:32 /dev/lircd1

> , and are you starting the second instance of
> LIRC pointing to this device?

As near as I can tell:

# ps wwuax | grep lircd
root 3787 0.0 0.0 26624 508 ? Ss 14:32
0:00 /usr/sbin/lircd --device=/dev/lirc0
root 3800 0.0 0.0 26624 560 ? Ss 14:32
0:00 /usr/sbin/lircd --driver=default --device=/dev/lirc1
--output=/dev/lircd1 --pidfile=/var/run/lircd1.pid



> The /dev/lirc1 device will need
> read/write permissions.

May be an issue later but for now I am running everything as root.

I'm sure it's something stupid but I just haven't been able to figure it
out and I've been working on it off and on all day.

--Greg


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


greg at gregandeva

Apr 21, 2009, 4:42 PM

Post #7 of 7 (950 views)
Permalink
Re: getting irblaster(.info) to work [In reply to]

On Tue, 2009-04-21 at 14:30 -0600, Greg Woods wrote:

> Apr 21 14:26:29 confusion lircd-0.8.4a[2538]: this remote configuration
> cannot be used to transmit

A little more random trial and error, and I solved my problem. It turns
out that there really is something wrong with the Motorola_DCT6200
configuration. As an experiment, I tried using the DCT2000 configuration
in lircd.conf instead, and poof! It worked. Now I just have to figure
out why only one of my PVR-500's tuners is working. The HD-PVR shows up
on /dev/video0, which used to be the first tuner of the
PVR-500. /dev/video1 is one of the PVR-500's tuners, but the other one
has vanished. /dev/video2 exists, but mythtv-setup says there is nothing
there. A Myth user's work is never done :-)

--Greg


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

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.