Forum

Full Version: Remote Control, ID 0bc7:0006
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hallo!

I'am a proud owner of a Raspberry Pi 2. Problem: My USB-Remote-Control doesn't work (under xbian). Sad

I read: http://wiki.xbian.org/doku.php/remotes
Terminal
root@xbian ~ # /etc/init.d/lirc stop
lirc stop/waiting
root@xbian ~ # mode2
mode2: could not get file information for /dev/lirc0
mode2: default_init(): No such file or directory
Remote isn’t recognized by the system.

I read: http://forum.xbian.org/thread-475.html
Terminal
root@xbian ~ # lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0bc7:0006 X10 Wireless Technology, Inc. Wireless Transceiver (ACPI-compliant)
O.k.! - this is the one: ID 0bc7:0006 X10 Wireless Technology

From an other system I have a correct lircd.conf (called pollin_x10.conf)
Where I have to store this and how can i activate it?

After reconnecting the remote control, it also appears under /proc/bus/input/devices (not directly after start up the Pi).
Terminal
root@xbian ~ # cat /proc/bus/input/devices
...
I: Bus=0003 Vendor=0bc7 Product=0006 Version=0100
N: Name="X10 WTI RF receiver"
P: Phys=usb-bcm2708_usb-1.4/input0
S: Sysfs=/devices/platform/bcm2708_usb/usb1/1-1/1-1.4/1-1.4:1.0/rc/rc0/input3
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=100013
B: KEY=c00 0 0 0 108fc030 2006049 0 0 0 4 8000 180 c0000001 9e1680 0 0 10000ffc
B: MSC=10

I: Bus=0003 Vendor=0bc7 Product=0006 Version=0100
N: Name="X10 WTI RF receiver mouse"
P: Phys=usb-bcm2708_usb-1.4/input1
S: Sysfs=/devices/platform/bcm2708_usb/usb1/1-1/1-1.4/1-1.4:1.0/input/input4
U: Uniq=
H: Handlers=mouse1 event2
B: PROP=0
B: EV=7
B: KEY=1b0000 0 0 0 0 0 0 0 0
B: REL=3

Just for info:
Terminal
root@xbian ~ # lsmod
Module Size Used by
rc_medion_x10_or2x 880 0
ati_remote 6410 0
rc_core 13880 3 rc_medion_x10_or2x,ati_remote
...

In Openelec the same remote control works ootb(!)
There exists a /etc/eventlircd.d/03_0bc7_0006.evmap

Do I have to use udev to aktivate the remote control? (How?)

Thank you in advance.
More than 40 readers and no answer ...
Is there no lirc expert? Sad
Most of us use CEC. Could you post lsmod output from openelec?
(28th Mar, 2015 09:34 AM)f1vefour Wrote: [ -> ]Could you post lsmod output from openelec?

For sure!

Terminal
kodi:~ # lsmod
Module Size Used by
bcm2708_rng 801 0

Yes, it's the complete output ... (I' am surprised). May be they prefer udev?!
Edited out since apparently the module is loaded.

Try this:
Terminal

sudo mv /etc/lirc/lircd.conf /etc/lirc/lircd.org
sudo cp pollin_x10.conf /etc/lirc/lircd.conf
sudo service lirc reload

Of course add the path to pollin_x10.conf in the above line.
(28th Mar, 2015 03:58 PM)f1vefour Wrote: [ -> ]Edited out since apparently the module is loaded.
...
Of course add the path to pollin_x10.conf in the above line.
Try to add dtoverlay=lirc-rpi into config.txt.

dtoverlay=lirc-rpi,gpio_out_pin=17,gpio_in_pin=18

Of course, edit chnge your io/out pins if needed.

I found this solution on Rasberryboom.com
Try to add dtoverlay=lirc-rpi into config.txt.

Unfortunately that wasn't the solution.

News ...

Last week I bought my second Pi2. Than I invested 2 day so solve my problem - without success. After investigation of the openelec system I noticed that they use eventlirc (https://code.google.com/p/eventlircd/) - in my eyes a good way to use remote controls.
Unfortunately I found no xbian/Debian package ... Sad

I decided a second time to use openelec - but I prefer the idea auf a Debian system. Wink

By chance I discovered osmc (https://osmc.tv/) - the perfect solution for me (sorry). A Debian with eventlirc - and my remote control worked ootb! Big Grin

Thank you for xbian, your engagement and your answers - but now I change over to the opposite camp.

crazydog
Reference URL's