MCE receiver problem

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

MCE receiver problem

Petric Frank

Hello,

 

maybe this is not exactly a lirc problem. Please point me to correct location if i am wrong here.

 

I've got a MCE-like ir remote together with a USB receiver.

 

Looks like it is detected by the kernel and a input device was created. Most of the keys are working. But - for example - the color buttons do not generate any output.

 

ir-keytable (version 1.10.1) returns:

Couldn't find any node at /sys/class/rc/rc*.

Using for test

ir-keytable -d /dev/input/eventxx -r

i got:

------------------- cut --------------------

scancode 0x700e0 = KEY_LEFTCTRL (0x1d)
scancode 0x700e1 = KEY_LEFTSHIFT (0x2a)
scancode 0x700e2 = KEY_LEFTALT (0x38)

...

Enabled protocols: other lirc rc-5 jvc sony nec sanyo mce-kbd rc-6 sharp xmp
------------------- cut --------------------

 

There is no definition of the color buttons in the list above.


ir-keytable can also not switch the protocol (maybe due to missing
/sys/class/rc/rc*).

 

Tests were done using this command:

ir-keytable -d /dev/input/eventxx -t

 

Any hints ?

 

 

Is it possibe to see the scancodes received by the USB-receiver to validate that the remote really sends data for the color buttons.

(and i am not barking at the wrong tree)

 

 

Some info about my system:

 

Kernel 4.9.6 (amd64) custom configured

Distribution: Gentoo

 

lsmod output:

----------------------- cut --------------------------

Module                  Size  Used by
ir_rc6_decoder          3153  0
ir_lirc_codec           4867  0
lirc_dev                7999  1 ir_lirc_codec
rc_rc6_mce              1580  0
mceusb                 10365  0
rc_core                16719  5 mceusb,ir_rc6_decoder,rc_rc6_mce,ir_lirc_codec,lirc_dev
usb_storage            48619  0
hid_generic             1385  0
usbhid                 35380  0
input_leds              3022  0
led_class               3975  1 input_leds
snd_hda_codec_generic    52071  2
ohci_pci                3272  0
xhci_pci                4958  0
xhci_hcd              101734  1 xhci_pci
r8169                  67900  0
mii                     4099  1 r8169
ehci_pci                4103  0
ohci_hcd               27022  1 ohci_pci
ehci_hcd               41036  1 ehci_pci
usbcore               165285  9 mceusb,usbhid,usb_storage,ehci_hcd,ohci_pci,xhci_pci,ohci_hcd,xhci_hcd,ehci_pci
usb_common              2222  1 usbcore
snd_hda_intel          18065  0
snd_hda_codec          73835  2 snd_hda_intel,snd_hda_codec_generic
snd_hwdep               5866  1 snd_hda_codec
snd_hda_core           40055  3 snd_hda_intel,snd_hda_codec,snd_hda_codec_generic
snd_pcm                78737  3 snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer              19336  1 snd_pcm
snd                    55051  6 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_generic,snd_pcm
soundcore               5231  1 snd
----------------------- cut --------------------------


The remote looks like this one:

https://www.mythtv.org/wiki/File:Philips-remote.jpg

 

but its branded as olidata.

 

The receiver is detected as (syslog):

----------------------- cut --------------------------

[    6.937470] usb 4-2: new low-speed USB device number 3 using xhci_hcd
[    7.117723] usb 4-2: New USB device found, idVendor=0471, idProduct=0613
[    7.117730] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    7.117735] usb 4-2: Product: MCE USB IR Receiver- Spinel plus
[    7.117740] usb 4-2: Manufacturer: PHILIPS
[    7.132840] input: PHILIPS MCE USB IR Receiver- Spinel plus as /devices/pci0000:00/0000:00:15.2/0000:04:00.0/usb4/4-2/4-2:1.0/0003:0471:0613.0003/input/input19
[    7.185141] hid-generic 0003:0471:0613.0003: input,hiddev0,hidraw2: USB HID v1.00 Keyboard [PHILIPS MCE USB IR Receiver- Spinel plus] on usb-0000:04:00.0-2/input0
[    7.191372] usbcore: registered new interface driver mceusb
-
---------------------- cut --------------------------

 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|

Re: MCE receiver problem

Alec Leamas
Hi!

On 15/03/17 01:29, Petric Frank wrote:
> Hello,
>
>
>
> maybe this is not exactly a lirc problem. Please point me to correct
> location if i am wrong here.
>

As presented, this is a kernel issue - the basic decoding and
ir-keytable is part of the kernel package. Getting help on these usually
best done on the distribution help channels (gentoo in your case, but it
might make sense to try one of the bigger distros if you don't get any
answer)

It might be that adding new keys to the remote is complicated using the
kernel stuff - to be honest, I'm not quite sure. In this case, one
option is to use the LIRC decoding instead of the kernel tools. If this
is what you want, you might want to look into [1]. To be able to use
keys not supported by the kernel you need to use the 'default' driver.


Cheers!

--alec


[1] http://lirc.org/html/configuration-guide.html

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|

Re: MCE receiver problem

Petric Frank

Hello Alec,

 

On Friday, March 17, 2017 Alec Leamas wrote:

> On 15/03/17 01:29, Petric Frank wrote:

> > maybe this is not exactly a lirc problem. Please point me to correct

> > location if i am wrong here.

>

> As presented, this is a kernel issue - the basic decoding and

> ir-keytable is part of the kernel package.

 

This was my impression also. I think the main problem here ist that the ir remote is not detected as remote control device and no entry /sys/class/rc/rc* is created. So i was not able to switch to the correct keymap and i'm stuck with the default one.

 

> Getting help on these usually

> best done on the distribution help channels (gentoo in your case, but it

> might make sense to try one of the bigger distros if you don't get any

> answer)

 

Will do.

 

But the starting point is to find out wether the (non working) keys are seen at the USB receiver before going further. This to exclude a hardware problem.

 

Is there an easy way to "sniff" the ir receiver ?

And perhaps evaluate the correct (kernel) scan codes as result ...

 

> It might be that adding new keys to the remote is complicated using the

> kernel stuff - to be honest, I'm not quite sure. In this case, one

> option is to use the LIRC decoding instead of the kernel tools. If this

> is what you want, you might want to look into [1]. To be able to use

> keys not supported by the kernel you need to use the 'default' driver.

 

Currently lirc 0.9.0 is marked stable in gentoo. Would it be better to use the latest unstable version in gentoo of lirc (0.9.4) ?

 

At a first read of [1] - take the data via devinput driver by lirc from /dev/input/eventxx, correct ?

As i have read older versions of lirc had a driver named mceusb(2). This module seem no more part of lirc. Would this be a problem ?

 

kind regards

Petric

 

[1] http://lirc.org/html/configuration-guide.html

 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Reply | Threaded
Open this post in threaded view
|

Re: MCE receiver problem

Alec Leamas
In reply to this post by Alec Leamas
Hi again!


> Hello Alec,
>
> On Friday, March 17, 2017 Alec Leamas wrote:
>> On 15/03/17 01:29, Petric Frank wrote:
>> > maybe this is not exactly a lirc problem. Please point me to correct
>> > location if i am wrong here.
>>
>> As presented, this is a kernel issue - the basic decoding and
>> ir-keytable is part of the kernel package.
>
> This was my impression also. I think the main problem here ist that the ir
> remote is not detected as remote control device and no entry
> /sys/class/rc/rc* is created. So i was not able to switch to the correct
> keymap and i'm stuck with the default one.

It might be that the kernel now uses it as a hid device. The output
(tail) from dmesg when (re-)inserting the USB dongle is the key info here.

> Is there an easy way to "sniff" the ir receiver ?
> And perhaps evaluate the correct (kernel) scan codes as result ...

Basically, no idea. This is hairy, kernel stuff.

> Currently lirc 0.9.0 is marked stable in gentoo. Would it be better to use
> the latest unstable version in gentoo of lirc (0.9.4) ?

Perhaps. But it's not just to install, you need to do some packaging or
similar to be able to install it. To make things more complicated. 0.9.4
is systemd-oriented...

> At a first read of [1] - take the data via devinput driver by lirc from
> /dev/input/eventxx, correct ?

Only if you get all keys from the kernel. Otherwise, you need to use the
default driver, if the kernel provides a /dev/lirc0 device.

> As i have read older versions of lirc had a driver named mceusb(2). This
> module seem no more part of lirc. Would this be a problem ?

No. The former mcesub lirc driver has been upstreamed to the kernel
since long.


--alec

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot