[mythtv-users] LIRC v ir-keytable -- Remote Control

Mon Feb 9 14:34:53 UTC 2015

On 02/08/2015 09:54 PM, Stephen Worthington wrote:
> On Sun, 8 Feb 2015 18:47:58 -0500, you wrote:
>
>> On 02/08/2015 05:37 PM, Another Sillyname wrote:
>>> Well we've got to the first stage so believe it or not that's good.
>>>
>>> It's more likely that the keycode mapping file isn't the correct one
>>> for your remote (I had this problem and it took me a day to realise
>>> and sort it out).
>>>
>>> Do you have other keycode mapping files from that remote manufacturer?
>>>
>>>
>>>
>>> On 8 February 2015 at 21:47, jim <jim_32766 at hotmail.com> wrote:
>>>> On 02/08/2015 03:38 PM, Another Sillyname wrote:
>>>>> I used LIRC for years and just recently switched to use the Linux
>>>>> Kernel drivers, while it was a bit of a pain to get setup (as was LIRC
>>>>> originally frankly...) once working it's fairly straightforward.
>>>>>
>>>>> There is however conflicting information regarding the required
>>>>> location of the Remote Device files on the web.....I came to the
>>>>> conclusion that different distros were doing it in different
>>>>> ways.....anyway.
>>>>>
>>>>> If you want to try going the kernel drivers route.....
>>>>>
>>>>> Install v4l-utils (this should provide ir-keytable   - make sure it
>>>>> does in your distro)
>>>>>
>>>>> This 'should' setup a directory likely under
>>>>>
>>>>> /usr/lib/udev/rc_keymaps
>>>>>
>>>>> in this directory you'll find a load of mapping files for assorted
>>>>> different remote controls....find the one that matches your remote.
>>>>>
>>>>> make a directory (if it's not already there)
>>>>>
>>>>> /etc/rc_keymaps
>>>>>
>>>>> COPY the file you identified previously to this directory
>>>>>
>>>>> reboot
>>>>>
>>>>> login...etc....open command line terminal
>>>>>
>>>>> run (as root) ir-keytable -v -t
>>>>>
>>>>> press buttons on remote and see if you get output....
>>>>>
>>>>> GL
>>>>>
>>>>> On 8 February 2015 at 20:08, jim <jim_32766 at hotmail.com> wrote:
>>>>>> Up until now I have been running MythTV using a wireless keyboard that
>>>>>> has a
>>>>>> trackball and mouse buttons. It's time I integrated a remote for the
>>>>>> family.
>>>>>> I have been struggling to incorporate a new remote control and would like
>>>>>> some thoughts from the group.
>>>>>>
>>>>>> The remote is a combination IR remote, air mouse, and keyboard made by
>>>>>> Aerb.
>>>>>> It's an attractive unit and seems to be constructed well.
>>>>>>
>>>>>> http://www.amazon.com/Aerb-Multifunction-Wireless-Keyboard-3-Gsensor/dp/B00K768DHY/ref=sr_1_1?s=electronics&ie=UTF8&qid=1423425443&sr=1-1&keywords=aerb+remote
>>>>>> The air mouse and keyboard functions are achieved via the 2.4GHz
>>>>>> connection
>>>>>> and work out-of-the-box. Some of the IR remote keys work out-of-the-box
>>>>>> but
>>>>>> several do not. I've run ir-keytable -t and xev, plus showkey in a non-x
>>>>>> console in an attempt to learn the scan codes and key assignments. Only
>>>>>> showkey gives results for all keys and those results don't agree with the
>>>>>> few keys for which xev provides a report.
>>>>>>
>>>>>> The IR receiver is made by Topseed.
>>>>>>
>>>>>> http://www.amazon.com/USB-External-Infrared-Receiver-Cable/dp/B00J5NRWFO/ref=sr_1_19?s=electronics&ie=UTF8&qid=1423423247&sr=1-19&keywords=ir+receiver
>>>>>>
>>>>>> Are there multiple paths to integrating a new remote? Is there a
>>>>>> best-practice? Is LIRC the way to go?
>>>>>>
>>>>>> Here is the configuration I am running:
>>>>>>
>>>>>> Linux Mint 17.1
>>>>>> Kernel  3.13.0-24-generic (x86_64)
>>>>>> MythTV Version : v0.27.4-30-g3b43903
>>>>>> MythTV Branch : fixes/0.27
>>>>>> Network Protocol : 77
>>>>>> Library API : 0.27.20141016-1
>>>>>> QT Version : 4.8.6
>>>>>>
>>>>>> Thanks,
>>>>>> Jim
>>>>>> _______________________________________________
>>>>>> mythtv-users mailing list
>>>>>> mythtv-users at mythtv.org
>>>>>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>>>>>> http://wiki.mythtv.org/Mailing_List_etiquette
>>>>>> MythTV Forums: https://forum.mythtv.org
>>>>> _______________________________________________
>>>>> mythtv-users mailing list
>>>>> mythtv-users at mythtv.org
>>>>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>>>>> http://wiki.mythtv.org/Mailing_List_etiquette
>>>>> MythTV Forums: https://forum.mythtv.org
>>>> In Linux Mint the packages ir-keytable and v4l-utils are separate. I've
>>>> installed ir-keytable but not v4l-utils. Are both packages required?
>>>>
>>>> I don't have a /usr/lib/udev/rc_keymaps/ but I do have a /lib/rc_keymaps,
>>>> and many keymaps are in that directory. I've copied the one I believe is
>>>> correct to /etc/rc_keymaps/ as suggested. I've rebooted and run ir-keytable
>>>> -v -t. The number keys have a response, but they don't appear as scancode
>>>> and keycode, just their numeric value, e.g. pressing 1 results in a 1 on the
>>>> screen. Few other keys have a response.
>>>>
>>>> Something is stopping ir-keytable from showing the keycodes. I tried this
>>>> with MythTV running and with it shutdown; the results were the same in both
>>>> cases.
>>>>
>>>> Anyone else experience this problem?
>>>>
>>>>
>>>>
>> Unfortunately, I don't have a map from the manufacturer and don't see
>> one on their website. I've sent them an email just now. Hopefully,
>> they'll respond with something useful.
>>
>> I was hoping to get some report on scancode/keycode and build a custom
>> map if necessary.  Is there no utility that allows one to see the actual
>> scancodes from the remote? There are 120 maps in the rc_keymaps folder
>> and I would like to avoid trying one after another.
>>
>> Thanks for your assistance!
> Please post the output of a plain "ir-keytable" command.  Frequently,
> there are multiple IR remote inputs on systems with tuners, and you
> may just be using the wrong one.  It may be necessary to use udev
> rules to lock down which /dev/input/event address is used for each of
> the IR inputs.
>
> Also, make sure that lirc is not running when you try ir-keytable, or
> it may be taking the keystrokes and "ir-keytable -t" will not see
> them.
>
> Your Topspeed IR receiver is an RC-6 one, which means that it should
> receive codes from any remote that sends in RC-6 format (a very common
> format).  But I could not find anything on the Amazon page for the
> remote that said what code format it sends.
>

When I unplug the usb ir-receiver ir-keytable says no node found at 
/sys/class/rc/rc*. This must be the only discoverable IR receiver on the 
system. Plugging the IR receiver back into a usb port and continuing, I 
get the following results.

Running lsusb shows the TopSeed IR receiver at Device 006:
Bus 002 Device 002: ID 8087:8001 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 007: ID 05dc:c75c Lexar Media, Inc.
Bus 003 Device 006: ID 1784:0011 TopSeed Technology Corp. eHome Infrared 
Transceiver
Bus 003 Device 005: ID 099a:7202 Zippy Technology Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Here is the output from ir-keytable:
Found /sys/class/rc/rc0/ (/dev/input/event14) with:
     Driver mceusb, table rc-rc6-mce
     Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
     Enabled protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
     Name: Media Center Ed. eHome Infrared
     bus: 3, vendor/product: 1784:0011, version: 0x0100
     Repeat delay = 500 ms, repeat period = 125 ms

I've tested allowing only one "Enabled protocol" at a time, but that 
made no difference.

lirc has been removed from the system to ensure it is not interfering. 
Still something is grabbing the events and stopping ir-keytable -t from 
showing the scancode/keycode.

Some of the keys, such as volume up, result in a temporary pop-up window 
showing a speaker icon with associated increase in volume, but nothing 
is shown by ir-keytable -t on the command line.

Thanks again to all for the assistance. I am really stumped on this one.

Jim