Linux Infrared Remote Control

Hi!

JAmes Atwill "lirc@..." wrote:

> I'm trying to get lirc working with my Slink-e, but I seem to be at a
> loss. I tried to use irrecord to make a file, but it blows up,

Could you be a *little* more concrete about your problem...

> Has anyone gotten this to work?

Try asking Max, the author of the Slink-e driver.

Christoph

> > I'm trying to get lirc working with my Slink-e, but I seem to be at a
> > loss. I tried to use irrecord to make a file, but it blows up,
> 
> Could you be a *little* more concrete about your problem...

Sure.  I've started by attempting to have the slink-e record my remote.  I
run "irrecord testfile".  It gives me the preamble, I hit Enter, then:

[...]
Don't stop pressing buttons until two lines of dots (2x80) have been
generated.

/irrecord: read() failed
/irrecord: Resource temporarily unavailable
/irrecord: gap not found, can´t continue

The read() failed comes as a response to me pressing a button on my remote.

I've also noticed that running lircd doesn't open the serial port (where the
slink-e is attached).  I can understand this being by design (since lircd
would ignore all the S-Link packets), but I'm not sure how to test it (ie, a
program that actually does listen on the serial port - besides irrecord).

> Try asking Max, the author of the Slink-e driver.

Is he on this list? :)

	JAmes

Hi!

JAmes Atwill "lirc@..." wrote:

[...]
> The read() failed comes as a response to me pressing a button on my
> remote.

I see. Due to the internal structure of the Slink-e irrecord won't work
with this device in this mode. Max has created all his config files
manually and obviously we never tried irrecord. But it should work if you
use the new template feature of the irrecord version that is included in
the current CVS snapshot. You can use an existing config file of the same  
brand to create a new config file. In this mode irrecord will read all  
protocol parameters from the existing config file and will skip the first  
part of the learning process. You'll find template files for the most  
common protocols in the remotes/generic directory of the current  
snapshots.

> I've also noticed that running lircd doesn't open the serial port
> (where the slink-e is attached).  I can understand this being by design

lircd will not open the port before a client has connected.

[...]
>> Try asking Max, the author of the Slink-e driver.

> Is he on this list? :)

I don't think so.

Christoph