GPIO IR Help (SOLVED)
#1
I`ve bought some female to female jumper cables and tsop4838 receiver. When i type: dmesg | grep lirc_rpi
I receive the following message back from ssh:

[ 6.728070] lirc_rpi: module is from the staging directory, the quality is unknown, you have been warned.
[ 7.631844] lirc_rpi: auto-detected active low receiver on GPIO pin 18
[ 7.632250] lirc_rpi lirc_rpi.0: lirc_dev: driver lirc_rpi registered at minor = 0
[ 7.632264] lirc_rpi: driver registered!

Then: mode2 -d /dev/lirc0

But I receive the following messages

mode2: could not open /dev/lirc0
mode2: default_init(): Device or resource busy

Im just trying to see if the receiver is working

I`ve then typed irw /var/run/lirc/lircd-lirc0 and ssh doesn't do anything.

Does anyone know where Im going wrong?

EDIT: Tried again, and its working now
Reply
#2
Mce remotes work out of the box for me when plugged in the way this guide has it https://learn.adafruit.com/assets/5909

Mabye you need to kill lirc first?
Reply
#3
Assuming that you using Milhouse's builds, please see this thread http://forum.xbmc.org/showthread.php?tid=184791
Reply
#4
what addon, it doesnt say
Reply
#5
Quote:I`ve bought some female to female jumper cables

I don't know what you use these for, but has it occurred to you that there may be either a crossover you need, or a crossover you shouldn't have in the wires?
Derek
Reply
#6
(2014-04-08, 13:05)stuCONNERS Wrote: Then: mode2 -d /dev/lirc0

But I receive the following messages

mode2: could not open /dev/lirc0
mode2: default_init(): Device or resource busy
When using the mode2 command you should make sure lircd isn't running.

When using the irw command lircd has to run. But use:
Code:
irw /var/run/lirc/lircd
instead of
Code:
irw /var/run/lirc/lircd-lirc0

irw /var/run/lirc/lircd-lirc0 ends in:
Code:
connect: Connection refused
Reply
#7
This works for me with the Milhouse builds: http://wiki.openelec.tv/index.php?title=...O_Receiver
Reply
#8
(2014-04-09, 13:08)Ned Scott Wrote: This works for me with the Milhouse builds: http://wiki.openelec.tv/index.php?title=...O_Receiver
I also used this guide getting gpio ir to work with Milhouse builds. Also mapped the input to gpio22 (gpio18 is used by a 16x2 lcd). Newly the irw command works as described before for me (at setup like in the guide).
Reply
#9
(2014-04-08, 18:55)stuCONNERS Wrote: what addon, it doesnt say

Sure it does, the addon from *tas, see the first post of that thread for the link to the addon.

(2014-04-09, 13:08)Ned Scott Wrote: This works for me with the Milhouse builds: http://wiki.openelec.tv/index.php?title=...O_Receiver

This didn't work for me, but I understand that *tas' addon does something similar so in theory it should.
Reply
#10
(2014-04-09, 15:59)Bonzi Wrote: This didn't work for me, but I understand that *tas' addon does something similar so in theory it should.
This addon starts lircd at startup from xbmc/openelec
Code:
/usr/sbin/lircd --driver=default --device=/dev/lirc0 --uinput --output=/var/run/lirc/lircd --pidfile=/var/run/lirc/lircd-lirc0.pid /storage/.config/lircd.conf
You can also add this to "autostart.sh". Mine looks like this (cause of mapping input to gpio_in_pin=22):
Code:
#!/bin/sh
(kill -9 $(pidof lircd); \
modprobe -r lirc_rpi; \
modprobe lirc_rpi gpio_in_pin=22; \ #for new libgpio version
/usr/sbin/lircd --driver=default --device=/dev/lirc0 --uinput --output=/var/run/lirc/lircd --pidfile=/var/run/lirc/lircd-lirc0.pid /storage/.config/lircd.conf; \
)&
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
GPIO IR Help (SOLVED)00