Difference between revisions of "User Manual:IR control via evdev"
(→Background Info) |
|||
Line 11: | Line 11: | ||
==Background Info== | ==Background Info== | ||
The aim for my installation was to be able to interact with an FE in as few clicks as possible on the remote. making use of MCE keyboard commands (ALT+..., WIN+..., CTRL+...) where the standard MCE Remote lacked. LIRC made this difficult due to how the NUC IR receiver was designed where some inputs would show on /dev/events/input3, and others to /dev/events/input4 depending on the exact command the remote sent. LIRC essentially had to monitor and function with 2 receivers and not the typical one. | The aim for my installation was to be able to interact with an FE in as few clicks as possible on the remote. making use of MCE keyboard commands (ALT+..., WIN+..., CTRL+...) where the standard MCE Remote lacked. LIRC made this difficult due to how the NUC IR receiver was designed where some inputs would show on /dev/events/input3, and others to /dev/events/input4 depending on the exact command the remote sent. LIRC essentially had to monitor and function with 2 receivers and not the typical one. | ||
+ | This guide does briefly touch on migration between lirc and evdev. | ||
==evdev== | ==evdev== | ||
− | Part of the core kernel packages so no work is needed here. | + | Part of the core kernel packages so no installation work is needed here. |
+ | It would be worth noting that evdev is not out-of-the-box configured for the best IR experience. | ||
+ | |||
+ | Depending on your hardware, the /dev/event/inputX event assignment may not be static between reboots. edev rules will need to be created to ensure the inputs stay the same. | ||
+ | |||
==ir-keytables== | ==ir-keytables== | ||
ir-keytable package will likely need to be installed. | ir-keytable package will likely need to be installed. | ||
− | <code><pre>sudo apt-get install ir- | + | <code><pre>sudo apt-get install ir-keytable</pre></code> |
− | Now that's installed, use the -t | + | Now that's installed, use the -t switch (test) to test what ir-keytable sees when you press buttons on your remote. Take note of the device name it uses. If you do not see any output when you press a key, then the ir-keytables will need to be told what to monitor with the -d switch (device). |
<code><pre>ir-keytable -t</pre></code> | <code><pre>ir-keytable -t</pre></code> | ||
+ | <code><pre>ir-keytable -t -d /dev/event/input4</pre></code> | ||
− | ==configuring== | + | configure ir-keytables if ghost or erratic keypresses exist (-D = delay, -P = period): |
+ | <code><pre>ir-keytable -D 500 -P 250 -d /dev/event/input3</pre></code> | ||
+ | == Misc configuring== | ||
+ | evdev does not allow running of scripts like lirc does, so if a suspend script was called via a lirc keypress, then we need to handle that slightly differently. Thankfully Mythtv has suspend ability built in. | ||
==testing== | ==testing== |
Revision as of 15:29, 29 July 2015
This page is up-to-date to MythTV version 0.27.5, the current release is 34.0
--THIS PAGE IS CURRENTLY UNDER CONSTRUCTION--
Overview
Lirc is typically no longer required for a range of common IR devices. IR support has been added in to the linux kernel using evdev (/dev/event/inputX) and works natively in mythbuntu14.04 and mythtv with little configuration.
The following information has been written based on Logitech myHarmony 'Microsoft MCE Keyboard' and 'Microsoft Windows Media Center SE' devices, with the Intel DN2820FYKH NUC built-in IR receiver.
Background Info
The aim for my installation was to be able to interact with an FE in as few clicks as possible on the remote. making use of MCE keyboard commands (ALT+..., WIN+..., CTRL+...) where the standard MCE Remote lacked. LIRC made this difficult due to how the NUC IR receiver was designed where some inputs would show on /dev/events/input3, and others to /dev/events/input4 depending on the exact command the remote sent. LIRC essentially had to monitor and function with 2 receivers and not the typical one. This guide does briefly touch on migration between lirc and evdev.
evdev
Part of the core kernel packages so no installation work is needed here. It would be worth noting that evdev is not out-of-the-box configured for the best IR experience.
Depending on your hardware, the /dev/event/inputX event assignment may not be static between reboots. edev rules will need to be created to ensure the inputs stay the same.
ir-keytables
ir-keytable package will likely need to be installed.
sudo apt-get install ir-keytable
Now that's installed, use the -t switch (test) to test what ir-keytable sees when you press buttons on your remote. Take note of the device name it uses. If you do not see any output when you press a key, then the ir-keytables will need to be told what to monitor with the -d switch (device).
ir-keytable -t
ir-keytable -t -d /dev/event/input4
configure ir-keytables if ghost or erratic keypresses exist (-D = delay, -P = period):
ir-keytable -D 500 -P 250 -d /dev/event/input3
Misc configuring
evdev does not allow running of scripts like lirc does, so if a suspend script was called via a lirc keypress, then we need to handle that slightly differently. Thankfully Mythtv has suspend ability built in.
testing
code tags