https://kodi.wiki/api.php?action=feedcontributions&user=Sashamalo&feedformat=atomOfficial Kodi Wiki - User contributions [en]2024-03-28T16:28:05ZUser contributionsMediaWiki 1.39.6https://kodi.wiki/index.php?title=HOW-TO:Set_up_an_MCE_remote_control_in_Linux&diff=64875HOW-TO:Set up an MCE remote control in Linux2013-10-23T12:09:26Z<p>Sashamalo: /* Edit the driver table */</p>
<hr />
<div>This guide will help to configure an MCE Remote on a linux HTPC, even if all the commands are specific to Ubuntu, the main steps are the same on any modern linux distribution.<br />
<br />
MCE remotes are IR remotes that split into two main categories:<br />
*MCE remotes that send keystrokes<br />
*Windows remotes also known as RC6 or eHome remotes<br />
<br />
Most remotes work out of the box through the kernel input event subsystem. However they are often unusable in this state due to laggy/buggy behavior. <br />
On Linux it is often easier to use the [http://www.wikipedia.org Lirc] package.<br />
<br />
== Install the remote == <br />
=== Simple Installation method with Lircd ===<br />
<br />
The easiest way is to use the lircd daemon shipped with lirc package.<br />
<br />
In terminal, use the following command:<br />
<pre>apt-get install -y lirc</pre><br />
<br />
After the installation a configuration dialog will appear on Ubuntu.<br />
Choose the correct values corresponding to your receiver (and eventually transmitter)<br />
<br />
you can now test if the correct value are send by the remote buttons by using the <code>irw</code> command tool and then launch XBMC and check if the main button are responding correctly.<br />
<br />
You can always reconfigure the lirc package with the dpkg-reconfigure command:<br />
<pre>dpkg-reconfigure lirc</pre><br />
<br />
If the remote don't work it is always a good idea to reconfigure lirc package by choosing one of those 2 generic value for the receiver option :<br />
*Windows Media Center Transceivers/Remotes (all)<br />
*Linux input layer (/dev/input/eventX)<br />
<br />
a more complete guide is available here : [[HOW-TO:Setup_Lirc|HOW-TO: Setup Lirc]]<br />
<br />
=== Alternative Installation method using InputLirc ===<br />
<br />
In some cases the simple method will work in a buggy way (keys pressed twice, key burst, laggy key, ... ).<br />
If this is the case or you want deeper control over the configuration then use inputlirc.<br />
Inputlirc is a small LIRC-compatible daemon that reads from /dev/input/eventX devices and sends the received keycodes to connecting LIRC clients.<br />
<br />
*It is important to disable lircd daemon from lirc package, On ubuntu launch the lirc reconfiguration process with :<br />
<pre>dpkg-reconfigure lirc</pre><br />
Then choose twice none for receiver and transmitter.<br />
<br />
Make sure that lircd is not running. The START_LIRCD parameter should be now set to false in /etc/lirc/hardware.conf configuration file.<br />
<br />
*Install now inputlirc :<br />
sudo apt-get install inputlirc<br />
<br />
*Before proceeding we need to know the eventX number corresponding to our remote :<br />
<pre>cat /proc/bus/input/devices</pre><br />
<br />
For instance on my xtreamer ultra V1, the nuvoton receiver remote correspond to event4<br />
<pre>cI: Bus=0019 Vendor=1050 Product=00c3 Version=0033<br />
N: Name="Nuvoton w836x7hg Infrared Remote Transceiver"<br />
P: Phys=nuvoton/cir0<br />
S: Sysfs=/devices/pnp0/00:09/rc/rc0/input4<br />
U: Uniq=<br />
H: Handlers=kbd event4<br />
...</pre><br />
<br />
*As the eventX number may sometimes varry upon reboot, one need to know a unique id value corresponding to our remote to further create a udev rule :<br />
<pre>udevadm info -a -p $(udevadm info -q path -n /dev/input/event4)</pre> <br />
For the nuvoton, the ATTRS(id) will be used from the following output<br />
<pre>looking at device '/devices/pnp0/00:09/rc/rc0/input4/event4':<br />
KERNEL=="event4"<br />
SUBSYSTEM=="input"<br />
DRIVER==""<br />
<br />
looking at parent device '/devices/pnp0/00:09/rc/rc0/input4':<br />
KERNELS=="input4"<br />
SUBSYSTEMS=="input"<br />
DRIVERS==""<br />
ATTRS{name}=="Nuvoton w836x7hg Infrared Remote Transceiver"<br />
ATTRS{phys}=="nuvoton/cir0"<br />
ATTRS{uniq}==""<br />
ATTRS{properties}=="0"<br />
<br />
looking at parent device '/devices/pnp0/00:09/rc/rc0':<br />
KERNELS=="rc0"<br />
SUBSYSTEMS=="rc"<br />
DRIVERS==""<br />
ATTRS{protocols}=="rc-5 nec [rc-6] jvc sony mce_kbd lirc"<br />
<br />
looking at parent device '/devices/pnp0/00:09':<br />
KERNELS=="00:09"<br />
SUBSYSTEMS=="pnp"<br />
DRIVERS=="nuvoton-cir"<br />
ATTRS{options}=="<br />
ATTRS{id}=="NTN0530"<br />
<br />
looking at parent device '/devices/pnp0':<br />
KERNELS=="pnp0"<br />
SUBSYSTEMS=="<br />
DRIVERS=="</pre><br />
<br />
*One can now create a permanent symbolic link to our eventX device by creating a custom udev rule :<br />
<pre>echo 'KERNEL=="event*",ATTRS{id}=="NTN0530",SYMLINK="input/myremote"' > /etc/udev/rules.d/10-persistent-ir.rules</pre> <br />
<br />
Restart udev or reboot the htpc and there should now be a symbolic link in /dev/input/myremote<br />
<br />
*Configure inputlirc by editing /etc/default/inputlirc like this :<br />
<pre>EVENTS="/dev/input/myremote"<br />
OPTIONS="-g -m 0 -c"</pre><br />
<br />
*Restart inputlirc<br />
<pre>/etc/init.d/inputlirc stop<br />
/etc/init.d/inputlirc start</pre><br />
<br />
*Copy the LircMap configuration file into the personal directory<br />
<pre>cp /usr/share/xbmc/system/Lircmap.xml ~/.xbmc/userdata/Lircmap.xml</pre><br />
<br />
*Edit the linux-input-layer remote section to add the remote link name, one should have something like this :<br />
<pre><remote device="linux-input-layer"><br />
<altname>cx23885_remote</altname><br />
<altname>devinput</altname><br />
<altname>/dev/input/myremote</altname><br />
<left>KEY_LEFT</left><br />
...</pre><br />
<br />
*Launch xbmc and test the working remote<br />
<br />
Based on : [http://www.mobidyc.net/2012/09/xtreamer-ultra-ubuntu-12-04/]<br />
<br />
== Configure the remote buttons ==<br />
=== Edit the driver table ===<br />
<br />
If you are using inputlirc or lircd with the <code>Linux input layer (/dev/input/eventX)</code> value for the receiver parameter, you can tweak the driver keycode/scancode table with the ir-keytable command line tool.<br />
In the following example one will make some changes on the driver table used by the nuvoton remote shipped with the Xtreamer Ultra V1. This example can be adapted to any remote.<br />
<br />
<br />
By default, after using the inputlirc method on ubuntu 13.04, the subtitle, tilte and enter button are mapped like this for this remote on this HTPC :<br />
<pre>subtitle => KEY_TITLE<br />
title => no key code sent<br />
enter => no key code sent</pre><br />
<br />
One will change the driver table to map those 3 buttons like this :<br />
<pre>subtitle => KEY_SUBTITLE<br />
title => KEY_TITLE<br />
enter => KEY_SELECT</pre><br />
<br />
*First install the ir-keytable package<br />
<pre>apt-get install ir-keytable</pre><br />
<br />
*Stop or kill any lirc daemon (inputlircd or lircd)<br />
<pre>pkill lirc</pre><br />
<br />
*Launch ir-keytable in test mode for the remote and read the scancode sent by pressing the buttons :<br />
<pre>ir-keytable -t --device=/dev/input/myremote</pre><br />
<br />
The output looks like this :<br />
<pre><br />
Testing events. Please, press CTRL-C to abort.<br />
1378830829.479887: event MSC: scancode = 800f044d<br />
1378830829.479887: event sync<br />
1378830829.728814: event key up: KEY_TITLE (0x0171)<br />
1378830829.728814: event sync<br />
1378830833.290068: event MSC: scancode = 800f0451<br />
...<br />
1379288588.428518: event MSC: scancode = 800f0437<br />
1379288588.428518: event sync<br />
...</pre><br />
<br />
By analyzing the ouput, one can determine the the button/scancode association :<br />
<pre>subtitle => 800f044d<br />
title => 800f0451<br />
enter =>800f0437</pre><br />
<br />
*Dump the driver table into /etc/lirc/myirtable.cfg<br />
<pre>ir-keytable -r --device=/dev/input/myremote > /etc/lirc/myirtable.cfg</pre><br />
<br />
*Analyse the table file and grep the line corresponding to KEY_TITLE, KEY_SUBTITLE and KEY_SELECT<br />
<pre>scancode 0x800f044d = KEY_TITLE (0x171)<br />
scancode 0x800f045a = KEY_SUBTITLE (0x172)</pre> <br />
<br />
As you can see, KEY_SELECT is not associated to any scancode, KEY_TITLE is associated to the subtitle button scancode and KEY_SUBTITLE is associate to a non existent scancode.<br />
<br />
*Before procedding, it is necessary to know the key hex value associated to KEY_SELECT<br />
<br />
Those are located in the kernel source code in include/uapi/linux/input.h file.<br />
One can browse the source code here : [https://github.com/torvalds/linux/blob/master/include/uapi/linux/input.h]<br />
<br />
<pre>#define KEY_SELECT 0x161</pre><br />
<br />
*Edit the table file dumped before to have this button key association :<br />
<pre>subtitle => 800f044d => KEY_SUBTITLE (0x172)<br />
title => 800f0451 => KEY_TITLE (0x171)<br />
enter =>800f0437 => KEY_SELECT (0x161)</pre><br />
<br />
after modifying the KEY_TITLE,KEY_SUBTITLE lines and adding the KEY_SELECT line the edited part should look like this : <br />
<pre>scancode 0x800f044d = KEY_SUBTITLE (0x172)<br />
scancode 0x800f0451 = KEY_TITLE (0x171)<br />
scancode 0x800f0437 = KEY_SELECT (0x161)</pre><br />
<br />
*Make sure with your favorite tool that there isn't two lines with the same scancode fot those buttons in the file and save it.<br />
<br />
*Clear the driver table and update it with the table file :<br />
<pre>ir-keytable -c --device=/dev/input/myremote<br />
ir-keytable --device=/dev/input/myremote --write=/etc/lirc/myirtable.cfg <br />
Wrote 63 keycode(s) to driver</pre><br />
<br />
*To make the changes persistent upon reboot add those 2 last command above to /etc/rc.local<br />
<br />
*One can now test if everything works correctly with ir-keytable test mode, then restart inputlirc or lircd and launch xbmc<br />
<br />
=== Edit LircMap.xml and Keyboard.xml===<br />
<br />
First thing to do is to check the LircMap.xml located in ~/.xbmc/userdata/Lircmap.xml.<br />
<br />
One can acquire the button key values with the help of irw and then edit this file to better suits our needs.<br />
This can even be mandatory sometimes. <br />
<br />
For instance some remotes will send KEY_NUMERIC_1 instead of KEY_1 for the numeric pad. It is then necessary to edit the file at the correponding remote section from <br />
<pre><one>KEY_1</one></pre><br />
to<br />
<pre><one>KEY_NUMERIC_1</one></pre><br />
<br />
A complete guide is available here : [[Userdata/lircmap.xml]]<br />
<br />
For further tweaking it is necessary to edit the Keyboard.xml file.<br />
A complete guide is available here : [[Keymap]]<br />
<br />
[[Category:Remotes]]<br />
[[Category:XBMC Manual]]</div>Sashamalohttps://kodi.wiki/index.php?title=HOW-TO:Set_up_an_MCE_remote_control_in_Linux&diff=64517HOW-TO:Set up an MCE remote control in Linux2013-09-27T18:30:45Z<p>Sashamalo: </p>
<hr />
<div>This guide will help to configure an MCE Remote on a linux HTPC, even if all the commands are specific to Ubuntu, the main steps are the same on any modern linux distribution.<br />
<br />
MCE remotes are IR remotes that split into two main categories:<br />
*MCE remotes that send keystrokes<br />
*Windows remotes also known as RC6 or eHome remotes<br />
<br />
Most remotes work out of the box through the kernel input event subsystem. However they are often unusable in this state due to laggy/buggy behavior. <br />
On Linux it is often easier to use the [http://www.wikipedia.org Lirc] package.<br />
<br />
== Install the remote == <br />
=== Simple Installation method with Lircd ===<br />
<br />
The easiest way is to use the lircd daemon shipped with lirc package.<br />
<br />
In terminal, use the following command:<br />
<pre>apt-get install -y lirc</pre><br />
<br />
After the installation a configuration dialog will appear on Ubuntu.<br />
Choose the correct values corresponding to your receiver (and eventually transmitter)<br />
<br />
you can now test if the correct value are send by the remote buttons by using the <code>irw</code> command tool and then launch XBMC and check if the main button are responding correctly.<br />
<br />
You can always reconfigure the lirc package with the dpkg-reconfigure command:<br />
<pre>dpkg-reconfigure lirc</pre><br />
<br />
If the remote don't work it is always a good idea to reconfigure lirc package by choosing one of those 2 generic value for the receiver option :<br />
*Windows Media Center Transceivers/Remotes (all)<br />
*Linux input layer (/dev/input/eventX)<br />
<br />
a more complete guide is available here : [[HOW-TO:Setup_Lirc|HOW-TO: Setup Lirc]]<br />
<br />
=== Alternative Installation method using InputLirc ===<br />
<br />
In some cases the simple method will work in a buggy way (keys pressed twice, key burst, laggy key, ... ).<br />
If this is the case or you want deeper control over the configuration then use inputlirc.<br />
Inputlirc is a small LIRC-compatible daemon that reads from /dev/input/eventX devices and sends the received keycodes to connecting LIRC clients.<br />
<br />
*It is important to disable lircd daemon from lirc package, On ubuntu launch the lirc reconfiguration process with :<br />
<pre>dpkg-reconfigure lirc</pre><br />
Then choose twice none for receiver and transmitter.<br />
<br />
Make sure that lircd is not running. The START_LIRCD parameter should be now set to false in /etc/lirc/hardware.conf configuration file.<br />
<br />
*Install now inputlirc :<br />
sudo apt-get install inputlirc<br />
<br />
*Before proceeding we need to know the eventX number corresponding to our remote :<br />
<pre>cat /proc/bus/input/devices</pre><br />
<br />
For instance on my xtreamer ultra V1, the nuvoton receiver remote correspond to event4<br />
<pre>cI: Bus=0019 Vendor=1050 Product=00c3 Version=0033<br />
N: Name="Nuvoton w836x7hg Infrared Remote Transceiver"<br />
P: Phys=nuvoton/cir0<br />
S: Sysfs=/devices/pnp0/00:09/rc/rc0/input4<br />
U: Uniq=<br />
H: Handlers=kbd event4<br />
...</pre><br />
<br />
*As the eventX number may sometimes varry upon reboot, one need to know a unique id value corresponding to our remote to further create a udev rule :<br />
<pre>udevadm info -a -p $(udevadm info -q path -n /dev/input/event4)</pre> <br />
For the nuvoton, the ATTRS(id) will be used from the following output<br />
<pre>looking at device '/devices/pnp0/00:09/rc/rc0/input4/event4':<br />
KERNEL=="event4"<br />
SUBSYSTEM=="input"<br />
DRIVER==""<br />
<br />
looking at parent device '/devices/pnp0/00:09/rc/rc0/input4':<br />
KERNELS=="input4"<br />
SUBSYSTEMS=="input"<br />
DRIVERS==""<br />
ATTRS{name}=="Nuvoton w836x7hg Infrared Remote Transceiver"<br />
ATTRS{phys}=="nuvoton/cir0"<br />
ATTRS{uniq}==""<br />
ATTRS{properties}=="0"<br />
<br />
looking at parent device '/devices/pnp0/00:09/rc/rc0':<br />
KERNELS=="rc0"<br />
SUBSYSTEMS=="rc"<br />
DRIVERS==""<br />
ATTRS{protocols}=="rc-5 nec [rc-6] jvc sony mce_kbd lirc"<br />
<br />
looking at parent device '/devices/pnp0/00:09':<br />
KERNELS=="00:09"<br />
SUBSYSTEMS=="pnp"<br />
DRIVERS=="nuvoton-cir"<br />
ATTRS{options}=="<br />
ATTRS{id}=="NTN0530"<br />
<br />
looking at parent device '/devices/pnp0':<br />
KERNELS=="pnp0"<br />
SUBSYSTEMS=="<br />
DRIVERS=="</pre><br />
<br />
*One can now create a permanent symbolic link to our eventX device by creating a custom udev rule :<br />
<pre>echo 'KERNEL=="event*",ATTRS{id}=="NTN0530",SYMLINK="input/myremote"' > /etc/udev/rules.d/10-persistent-ir.rules</pre> <br />
<br />
Restart udev or reboot the htpc and there should now be a symbolic link in /dev/input/myremote<br />
<br />
*Configure inputlirc by editing /etc/default/inputlirc like this :<br />
<pre>EVENTS="/dev/input/myremote"<br />
OPTIONS="-g -m 0 -c"</pre><br />
<br />
*Restart inputlirc<br />
<pre>/etc/init.d/inputlirc stop<br />
/etc/init.d/inputlirc start</pre><br />
<br />
*Copy the LircMap configuration file into the personal directory<br />
<pre>cp /usr/share/xbmc/system/Lircmap.xml ~/.xbmc/userdata/Lircmap.xml</pre><br />
<br />
*Edit the linux-input-layer remote section to add the remote link name, one should have something like this :<br />
<pre><remote device="linux-input-layer"><br />
<altname>cx23885_remote</altname><br />
<altname>devinput</altname><br />
<altname>/dev/input/myremote</altname><br />
<left>KEY_LEFT</left><br />
...</pre><br />
<br />
*Launch xbmc and test the working remote<br />
<br />
Based on : [http://www.mobidyc.net/2012/09/xtreamer-ultra-ubuntu-12-04/]<br />
<br />
== Configure the remote buttons ==<br />
=== Edit the driver table ===<br />
<br />
If you are using inputlirc or lircd with the <code>Linux input layer (/dev/input/eventX)</code> value for the receiver parameter, you can tweak the driver keycode/scancode table with the ir-keytable command line tool.<br />
In the following example one will make some changes on the driver table used by the nuvoton remote shipped with the Xtreamer Ultra V1. This example can be adapted to any remote.<br />
<br />
<br />
By default, after using the inputlirc method on ubuntu 13.04, the subtitle, tilte and enter button are mapped like this for this remote on this HTPC :<br />
<pre>subtitle => KEY_TITLE<br />
title => no key code sent<br />
enter => no key code sent</pre><br />
<br />
One will change the driver table to map those 3 buttons like this :<br />
<pre>subtitle => KEY_SUBTITLE<br />
title => KEY_TITLE<br />
enter => KEY_SELECT</pre><br />
<br />
*First install the ir-keytable package<br />
<pre>apt-get install ir-keytable</pre><br />
<br />
*Stop or kill any lirc daemon (inputlircd or lircd)<br />
<pre>pkill lirc</pre><br />
<br />
*Launch ir-keytable in test mode for the remote and read the scancode sent by pressing the buttons :<br />
<pre>ir-keytable -t --device=/dev/input/myremote</pre><br />
<br />
The output looks like this :<br />
<pre><br />
Testing events. Please, press CTRL-C to abort.<br />
1378830829.479887: event MSC: scancode = 800f044d<br />
1378830829.479887: event sync<br />
1378830829.728814: event key up: KEY_TITLE (0x0171)<br />
1378830829.728814: event sync<br />
1378830833.290068: event MSC: scancode = 800f0451<br />
...<br />
1379288588.428518: event MSC: scancode = 800f0437<br />
1379288588.428518: event sync<br />
...</pre><br />
<br />
By analysing the ouput, one can determine the the button/scancode association :<br />
<pre>subtitle => 800f044d<br />
title => 800f0451<br />
enter =>800f0437</pre><br />
<br />
*Dump the driver table into /etc/lirc/myirtable.cfg<br />
<pre>ir-keytable -r --device=/dev/input/myremote > /etc/lirc/myirtable.cfg</pre><br />
<br />
*Analyse the table file and grep the line corresponding to KEY_TITLE, KEY_SUBTITLE and KEY_SELECT<br />
<pre>scancode 0x800f044d = KEY_TITLE (0x171)<br />
scancode 0x800f045a = KEY_SUBTITLE (0x172)</pre> <br />
<br />
As you can see, KEY_SELECT is not associated to any scancode, KEY_TITLE is associated to the subtitle button scancode and KEY_SUBTITLE is associate to a non existent scancode.<br />
<br />
*Before procedding, it is necessary to know the key hex value associated to KEY_SELECT<br />
<br />
Those are located in the kernel source code in include/uapi/linux/input.h file.<br />
One can browse the source code here : [https://github.com/torvalds/linux/blob/master/include/uapi/linux/input.h]<br />
<br />
<pre>#define KEY_SELECT 0x161</pre><br />
<br />
*Edit the table file dumped before to have this button key association :<br />
<pre>subtitle => 800f044d => KEY_SUBTITLE (0x172)<br />
title => 800f0451 => KEY_TITLE (0x171)<br />
enter =>800f0437 => KEY_SELECT (0x161)</pre><br />
<br />
after modifying the KEY_TITLE,KEY_SUBTITLE lines and adding the KEY_SELECT line the edited part should look like this : <br />
<pre>scancode 0x800f044d = KEY_SUBTITLE (0x172)<br />
scancode 0x800f0451 = KEY_TITLE (0x171)<br />
scancode 0x800f0437 = KEY_SELECT (0x161)</pre><br />
<br />
*Make sure with your favorite tool that there isn't two lines with the same scancode fot those buttons in the file and save it.<br />
<br />
*Clear the driver table and update it with the table file :<br />
<pre>ir-keytable -c --device=/dev/input/myremote<br />
ir-keytable --device=/dev/input/myremote --write=/etc/lirc/myirtable.cfg <br />
Wrote 63 keycode(s) to driver</pre><br />
<br />
*To make the changes persistent upon reboot add those 2 last command above to /etc/rc.local<br />
<br />
*One can now test if everything works correctly with ir-keytable test mode, then restart inputlirc or lircd and launch xbmc<br />
<br />
=== Edit LircMap.xml and Keyboard.xml===<br />
<br />
First thing to do is to check the LircMap.xml located in ~/.xbmc/userdata/Lircmap.xml.<br />
<br />
One can acquire the button key values with the help of irw and then edit this file to better suits our needs.<br />
This can even be mandatory sometimes. <br />
<br />
For instance some remotes will send KEY_NUMERIC_1 instead of KEY_1 for the numeric pad. It is then necessary to edit the file at the correponding remote section from <br />
<pre><one>KEY_1</one></pre><br />
to<br />
<pre><one>KEY_NUMERIC_1</one></pre><br />
<br />
A complete guide is available here : [[Userdata/lircmap.xml]]<br />
<br />
For further tweaking it is necessary to edit the Keyboard.xml file.<br />
A complete guide is available here : [[Keymap]]<br />
<br />
[[Category:Remotes]]<br />
[[Category:XBMC Manual]]</div>Sashamalohttps://kodi.wiki/index.php?title=MCE_remote_controls&diff=64516MCE remote controls2013-09-27T18:29:19Z<p>Sashamalo: </p>
<hr />
<div>{{mininav|[[General topics]]|[[Remote controls]]}}<br />
<br />
MCE remotes are the cheapest and easiest remotes to use with XBMC. They are readily available in most computer hardware stores and there are many available at [http://shop.ebay.com/?_from=R40&_trksid=p5197.m570.l1311&_nkw=mce+remote&_sacat=See-All-Categories eBay] from far eastern sources.<br />
<br />
<br />
MCE remotes typically come with a usb IR receiver, making them the very good first remote. Because MCE remotes are so cheap, they are often cheaper than a standalone IR receiver, so people often buy them to use the receiver with a [[Remote Controls#All in One Remote|All in One remote]].<br />
<br />
<br />
XBMC (v10.0 and later) is set up so that most buttons on an MCE remote work straight away with no editing or setting up. Just connect the receiver and away you go.<br />
<br />
MCE remotes split into two main categories:<br />
* MCE remotes that send keystrokes<br />
* Windows remotes with (also known as RC6 or eHome remotes) using the Microsoft eHome device driver to send commands<br />
<br />
<br />
For more details on MCE remotes see:<br />
* MCE [[Remote Control Reviews]]<br />
* [[Using an MCE remote control in Windows]]<br />
* [[Using a Microsoft remote control in Windows]]<br />
* [[HOW-TO:Setup_an_MCE_remote_control_in_Linux|Using an MCE remote control in Linux]]<br />
* [[Using a remote control with XBMC]]<br />
* [[Hama MCE Remote]] (Ortek VRC-1100)<br />
* [[MS-Tech MC-1200 Remote]]<br />
<br />
[[Category:Remotes]]<br />
[[Category:XBMC Manual]]</div>Sashamalohttps://kodi.wiki/index.php?title=HOW-TO:Set_up_an_MCE_remote_control_in_Linux&diff=64515HOW-TO:Set up an MCE remote control in Linux2013-09-27T18:28:17Z<p>Sashamalo: Created page with "This guide will help to configure an MCE Remote on a linux HTPC, even if all the commands are specific to Ubuntu, the main steps are the same on any modern linux distribution...."</p>
<hr />
<div>This guide will help to configure an MCE Remote on a linux HTPC, even if all the commands are specific to Ubuntu, the main steps are the same on any modern linux distribution.<br />
<br />
MCE remotes are IR remotes that split into two main categories:<br />
*MCE remotes that send keystrokes<br />
*Windows remotes also known as RC6 or eHome remotes<br />
<br />
Most remotes work out of the box through the kernel input event subsystem. However they are often unusable in this state due to laggy/buggy behavior. <br />
On Linux it is often easier to use the [http://www.wikipedia.org Lirc] package.<br />
<br />
== Install the remote == <br />
=== Simple Installation method with Lircd ===<br />
<br />
The easiest way is to use the lircd daemon shipped with lirc package.<br />
<br />
In terminal, use the following command:<br />
<pre>apt-get install -y lirc</pre><br />
<br />
After the installation a configuration dialog will appear on Ubuntu.<br />
Choose the correct values corresponding to your receiver (and eventually transmitter)<br />
<br />
you can now test if the correct value are send by the remote buttons by using the <code>irw</code> command tool and then launch XBMC and check if the main button are responding correctly.<br />
<br />
You can always reconfigure the lirc package with the dpkg-reconfigure command:<br />
<pre>dpkg-reconfigure lirc</pre><br />
<br />
If the remote don't work it is always a good idea to reconfigure lirc package by choosing one of those 2 generic value for the receiver option :<br />
*Windows Media Center Transceivers/Remotes (all)<br />
*Linux input layer (/dev/input/eventX)<br />
<br />
a more complete guide is available here : [[HOW-TO:Setup_Lirc|HOW-TO: Setup Lirc]]<br />
<br />
=== Alternative Installation method using InputLirc ===<br />
<br />
In some cases the simple method will work in a buggy way (keys pressed twice, key burst, laggy key, ... ).<br />
If this is the case or you want deeper control over the configuration then use inputlirc.<br />
Inputlirc is a small LIRC-compatible daemon that reads from /dev/input/eventX devices and sends the received keycodes to connecting LIRC clients.<br />
<br />
*It is important to disable lircd daemon from lirc package, On ubuntu launch the lirc reconfiguration process with :<br />
<pre>dpkg-reconfigure lirc</pre><br />
Then choose twice none for receiver and transmitter.<br />
<br />
Make sure that lircd is not running. The START_LIRCD parameter should be now set to false in /etc/lirc/hardware.conf configuration file.<br />
<br />
*Install now inputlirc :<br />
sudo apt-get install inputlirc<br />
<br />
*Before proceeding we need to know the eventX number corresponding to our remote :<br />
<pre>cat /proc/bus/input/devices</pre><br />
<br />
For instance on my xtreamer ultra V1, the nuvoton receiver remote correspond to event4<br />
<pre>cI: Bus=0019 Vendor=1050 Product=00c3 Version=0033<br />
N: Name="Nuvoton w836x7hg Infrared Remote Transceiver"<br />
P: Phys=nuvoton/cir0<br />
S: Sysfs=/devices/pnp0/00:09/rc/rc0/input4<br />
U: Uniq=<br />
H: Handlers=kbd event4<br />
...</pre><br />
<br />
*As the eventX number may sometimes varry upon reboot, one need to know a unique id value corresponding to our remote to further create a udev rule :<br />
<pre>udevadm info -a -p $(udevadm info -q path -n /dev/input/event4)</pre> <br />
For the nuvoton, the ATTRS(id) will be used from the following output<br />
<pre>looking at device '/devices/pnp0/00:09/rc/rc0/input4/event4':<br />
KERNEL=="event4"<br />
SUBSYSTEM=="input"<br />
DRIVER==""<br />
<br />
looking at parent device '/devices/pnp0/00:09/rc/rc0/input4':<br />
KERNELS=="input4"<br />
SUBSYSTEMS=="input"<br />
DRIVERS==""<br />
ATTRS{name}=="Nuvoton w836x7hg Infrared Remote Transceiver"<br />
ATTRS{phys}=="nuvoton/cir0"<br />
ATTRS{uniq}==""<br />
ATTRS{properties}=="0"<br />
<br />
looking at parent device '/devices/pnp0/00:09/rc/rc0':<br />
KERNELS=="rc0"<br />
SUBSYSTEMS=="rc"<br />
DRIVERS==""<br />
ATTRS{protocols}=="rc-5 nec [rc-6] jvc sony mce_kbd lirc"<br />
<br />
looking at parent device '/devices/pnp0/00:09':<br />
KERNELS=="00:09"<br />
SUBSYSTEMS=="pnp"<br />
DRIVERS=="nuvoton-cir"<br />
ATTRS{options}=="<br />
ATTRS{id}=="NTN0530"<br />
<br />
looking at parent device '/devices/pnp0':<br />
KERNELS=="pnp0"<br />
SUBSYSTEMS=="<br />
DRIVERS=="</pre><br />
<br />
*One can now create a permanent symbolic link to our eventX device by creating a custom udev rule :<br />
<pre>echo 'KERNEL=="event*",ATTRS{id}=="NTN0530",SYMLINK="input/myremote"' > /etc/udev/rules.d/10-persistent-ir.rules</pre> <br />
<br />
Restart udev or reboot the htpc and there should now be a symbolic link in /dev/input/myremote<br />
<br />
*Configure inputlirc by editing /etc/default/inputlirc like this :<br />
<pre>EVENTS="/dev/input/myremote"<br />
OPTIONS="-g -m 0 -c"</pre><br />
<br />
*Restart inputlirc<br />
<pre>/etc/init.d/inputlirc stop<br />
/etc/init.d/inputlirc start</pre><br />
<br />
*Copy the LircMap configuration file into the personal directory<br />
<pre>cp /usr/share/xbmc/system/Lircmap.xml ~/.xbmc/userdata/Lircmap.xml</pre><br />
<br />
*Edit the linux-input-layer remote section to add the remote link name, one should have something like this :<br />
<pre><remote device="linux-input-layer"><br />
<altname>cx23885_remote</altname><br />
<altname>devinput</altname><br />
<altname>/dev/input/myremote</altname><br />
<left>KEY_LEFT</left><br />
...</pre><br />
<br />
*Launch xbmc and test the working remote<br />
<br />
Based on : [http://www.mobidyc.net/2012/09/xtreamer-ultra-ubuntu-12-04/]<br />
<br />
== Configure the remote buttons ==<br />
=== Edit the driver table ===<br />
<br />
If you are using inputlirc or lircd with the <code>Linux input layer (/dev/input/eventX)</code> value for the receiver parameter, you can tweak the driver keycode/scancode table with the ir-table command line tool.<br />
In the following example one will make some changes on the driver table used by the nuvoton remote shipped with the Xtreamer Ultra V1. This example can be adapted to any remote.<br />
<br />
<br />
By default, after using the inputlirc method on ubuntu 13.04, the subtitle, tilte and enter button are mapped like this for this remote on this HTPC :<br />
<pre>subtitle => KEY_TITLE<br />
title => no key code sent<br />
enter => no key code sent</pre><br />
<br />
One will change the driver table to map those 3 buttons like this :<br />
<pre>subtitle => KEY_SUBTITLE<br />
title => KEY_TITLE<br />
enter => KEY_SELECT</pre><br />
<br />
*First install the ir-keytable package<br />
<pre>apt-get install ir-keytable</pre><br />
<br />
*Stop or kill any lirc daemon (inputlircd or lircd)<br />
<pre>pkill lirc</pre><br />
<br />
*Launch ir-keytable in test mode for the remote and read the scancode sent by pressing the buttons :<br />
<pre>ir-keytable -t --device=/dev/input/myremote</pre><br />
<br />
The output looks like this :<br />
<pre><br />
Testing events. Please, press CTRL-C to abort.<br />
1378830829.479887: event MSC: scancode = 800f044d<br />
1378830829.479887: event sync<br />
1378830829.728814: event key up: KEY_TITLE (0x0171)<br />
1378830829.728814: event sync<br />
1378830833.290068: event MSC: scancode = 800f0451<br />
...<br />
1379288588.428518: event MSC: scancode = 800f0437<br />
1379288588.428518: event sync<br />
...</pre><br />
<br />
By analysing the ouput, one can determine the the button/scancode association :<br />
<pre>subtitle => 800f044d<br />
title => 800f0451<br />
enter =>800f0437</pre><br />
<br />
*Dump the driver table into /etc/lirc/myirtable.cfg<br />
<pre>ir-keytable -r --device=/dev/input/myremote > /etc/lirc/myirtable.cfg</pre><br />
<br />
*Analyse the table file and grep the line corresponding to KEY_TITLE, KEY_SUBTITLE and KEY_SELECT<br />
<pre>scancode 0x800f044d = KEY_TITLE (0x171)<br />
scancode 0x800f045a = KEY_SUBTITLE (0x172)</pre> <br />
<br />
As you can see, KEY_SELECT is not associated to any scancode, KEY_TITLE is associated to the subtitle button scancode and KEY_SUBTITLE is associate to a non existent scancode.<br />
<br />
*Before procedding, it is necessary to know the key hex value associated to KEY_SELECT<br />
<br />
Those are located in the kernel source code in include/uapi/linux/input.h file.<br />
One can browse the source code here : [https://github.com/torvalds/linux/blob/master/include/uapi/linux/input.h]<br />
<br />
<pre>#define KEY_SELECT 0x161</pre><br />
<br />
*Edit the table file dumped before to have this button key association :<br />
<pre>subtitle => 800f044d => KEY_SUBTITLE (0x172)<br />
title => 800f0451 => KEY_TITLE (0x171)<br />
enter =>800f0437 => KEY_SELECT (0x161)</pre><br />
<br />
after modifying the KEY_TITLE,KEY_SUBTITLE lines and adding the KEY_SELECT line the edited part should look like this : <br />
<pre>scancode 0x800f044d = KEY_SUBTITLE (0x172)<br />
scancode 0x800f0451 = KEY_TITLE (0x171)<br />
scancode 0x800f0437 = KEY_SELECT (0x161)</pre><br />
<br />
*Make sure with your favorite tool that there isn't two lines with the same scancode fot those buttons in the file and save it.<br />
<br />
*Clear the driver table and update it with the table file :<br />
<pre>ir-keytable -c --device=/dev/input/myremote<br />
ir-keytable --device=/dev/input/myremote --write=/etc/lirc/myirtable.cfg <br />
Wrote 63 keycode(s) to driver</pre><br />
<br />
*To make the changes persistent upon reboot add those 2 last command above to /etc/rc.local<br />
<br />
*One can now test if everything works correctly with ir-keytable test mode, then restart inputlirc or lircd and launch xbmc<br />
<br />
=== Edit LircMap.xml and Keyboard.xml===<br />
<br />
First thing to do is to check the LircMap.xml located in ~/.xbmc/userdata/Lircmap.xml.<br />
<br />
One can acquire the button key values with the help of irw and then edit this file to better suits our needs.<br />
This can even be mandatory sometimes. <br />
<br />
For instance some remotes will send KEY_NUMERIC_1 instead of KEY_1 for the numeric pad. It is then necessary to edit the file at the correponding remote section from <br />
<pre><one>KEY_1</one></pre><br />
to<br />
<pre><one>KEY_NUMERIC_1</one></pre><br />
<br />
A complete guide is available here : [[Userdata/lircmap.xml]]<br />
<br />
For further tweaking it is necessary to edit the Keyboard.xml file.<br />
A complete guide is available here : [[Keymap]]<br />
<br />
[[Category:Remotes]]<br />
[[Category:XBMC Manual]]</div>Sashamalohttps://kodi.wiki/index.php?title=MCE_remote_controls&diff=64176MCE remote controls2013-09-11T17:20:48Z<p>Sashamalo: /* MCE Remote */</p>
<hr />
<div>{{mininav|[[General topics]]}}<br />
{{cleanup}}<br />
<section begin="intro" />In XBMC the primary environment was designed for the living room ([[10-foot interface]]) and controlling it only with a remote control. While XBMC does support mouse, keyboard, and even touch controls, the remote control is typically how the GUI is designed around.<section end="intro" /><br />
<br />
This is why XBMC doesn't currently do things like dragging and dropping icons and things within its windows, since a remote control can't really do that. XBMC is still evolving, and using XBMC on touch screens, and other "2-foot interface" situations are causing XBMC to gain new ways to interface with it. While the "remote is king" is still true, XBMC will continue to add new ways to control it, so watch out for exciting new versions in the future.<br />
<br />
=Common controls=<br />
* Traditional remote control (IR or RF)<br />
* [[Keyboard]] / Mouse<br />
* [[CEC]]<br />
* [[Smartphone/tablet remotes]]<br />
* Touch screen<br />
<br />
== Types of Remotes ==<br />
<br />
There are 4 main types of remote controls that are commonly used with XBMC:<br />
* [[Remote Controls#MCE Remote|MCE Remote]]<br />
* [[Remote Controls#All in One Remote|All in One remote]]<br />
* [[Remote Controls#QWERTY Remote|QWERTY Remote]]<br />
* [[Remote Controls#Smart Phone Remote|Smart Phone Remote]]<br />
<br />
=== MCE Remote ===<br />
<br />
MCE remotes are the cheapest and easiest remotes to use with XBMC. They are readily available in most computer hardware stores and there are many available at [http://shop.ebay.com/?_from=R40&_trksid=p5197.m570.l1311&_nkw=mce+remote&_sacat=See-All-Categories eBay] from far eastern sources.<br />
<br />
<br />
MCE remotes typically come with a usb IR receiver, making them the very good first remote. Because MCE remotes are so cheap, they are often cheaper than a standalone IR receiver, so people often buy them to use the receiver with a [[Remote Controls#All in One Remote|All in One remote]].<br />
<br />
<br />
XBMC (v10.0 and later) is set up so that most buttons on an MCE remote work straight away with no editing or setting up. Just connect the receiver and away you go.<br />
<br />
MCE remotes split into two main categories:<br />
* MCE remotes that send keystrokes<br />
* Windows remotes with (also known as RC6 or eHome remotes) using the Microsoft eHome device driver to send commands<br />
<br />
<br />
For more details on MCE remotes see:<br />
* MCE [[Remote Control Reviews]]<br />
* [[Using an MCE remote control in Windows]]<br />
* [[Using a Microsoft remote control in Windows]]<br />
* [[HOW-TO: Install and Setup XBMC on an ION based machine#Microsoft MCE Remote|Using an MCE remote control in Linux]]<br />
* [[Using a remote control with XBMC]]<br />
* [[Hama MCE Remote]] (Ortek VRC-1100)<br />
* [[MS-Tech MC-1200 Remote]]<br />
<br />
=== All in One Remote ===<br />
<br />
All in One remotes cover a multitude of devices, starting at the simple universal remotes that don't cost much more than a MCE remote to the $1,500 [http://www.pronto.philips.com/index.html Phillips Pronto]. Probably the most famous all in one remote is the [http://www.logitech.com/en-us/remotes/universal-remotes Logitech Harmony Remotes].<br />
<br />
* HOW-TO: [http://www.loggn.de/htpc-media-center-logitech-harmony-reagiert-traege-unter-windows-und-linux/ Logitech Harmony - delay / lag / slow response on XBMC]<br />
* HOW-TO: [http://www.loggn.de/ubuntu-lirc-konfiguration-mit-rc6-ir605q-147a-e03e-und-logitech-harmony/ Ubuntu - LIRC configuration with MCE IR Receiver and Logitech Harmony (harmony-profile: Windows Media Center SE)]<br />
* HOW-TO: [http://www.loggn.de/linux-ubuntu-lirc-xbmc-mit-logitech-harmony-steuern-lircmap-xml-und-keyboard-xml/ Ubuntu/Linux – LIRC – control XBMC with Logitech Harmony remote – Lircmap.xml and Keyboard.xml]<br />
* HOW-TO: [http://www.loggn.de/arch-linux-lirc-konfiguration-mit-mce-rc6-ir-und-lircmap-xml-fuer-xbmc-logitech-harmony/ Arch Linux - LIRC Version 0.9.0, Kernel 3.2 and new Lircmap.xml for XBMC]<br />
<br />
As their name suggests, All in One remotes are designed so that one remote can control all the IR (and some times RF) devices in your entertainment room. To achieve this, the remote must be able to produce the IR signals of many different remote controls, this is typically done one of 3 ways:<br />
* The manufacture loads the remote with a database of IR signals and when you set up the remote you 'tell' the remote which TV, DVD, Set top box you have and it send the correct signal<br />
** This obviously limits you to the list of devices the remote manufacturer puts into the database<br />
* The remote is able to 'learn'. The remote has a built in receiver which allows you to 'record' other remote controls signals<br />
** This means that as long as you have the original remote, you can control (nearly) any IR device ever made<br />
** This feature is more common in more expensive remotes as the receiver is an added cost<br />
* A combination of the above. A lot of remotes (e.g. Harmony remotes) use a database system for a quick set up but also are able to learn in order to add other devices or fix mistakes in the database.<br />
** This is the best mix of features.<br />
<br />
<br />
* [[Default Controls#Universal Remote Control|XBMC Universal Remote Control]]<br />
* [[HOW-TO program your Philips Pronto Unviersal Remote for use with XBMC]]<br />
* [[HOW-TO Configure your Cyberlink Media Centre Remote for XBMC on Linux]]<br />
<br />
* INSERT LINK TO AN ALL IN ONE REMOTE REVIEW PAGE<br />
<br />
=== QWERTY Remote ===<br />
QWERTY Remotes are a relatively new phenomenon; the rise in popularity of Home Theatre PCs, software like XBMC and IPTV the need for a full qwerty keyboard is growing. Like an [[Remote Controls#All in One Remote|All in One remote]] a QWERTY remote vary in price from the relatively cheap [http://www.amazon.com/KeyMote-Remote-Keyboard-Controller-Playstation-3/dp/B001GIPNCK/ref=sr_1_16?ie=UTF8&qid=1291636872&sr=8-16 3 in 1 PS3 remote] to over $150.<br />
<br />
QWERTY remotes are still in their infancy and as such there are many different types with vastly different features sets and buttons. Currently there are two main designs:<br />
* The sliding keyboard, for example the [[TiVo Slide]]<br />
* The double sided remote, for example the Boxee Remote<br />
<br />
<br />
Each has advantages and disadvantages, and with new QWERTY remotes being launched regularly the rate of development is very high. It shouldn't be long before QWERTY remotes start taking ideas from All in One remotes, so in time we could have a remote with the features of a Harmony One with the keyboard of a TiVo Slide. <br />
<br />
INSERT LINK TO AN QWERTY REMOTE REVIEW PAGE<br />
<br />
=== Smart Phone Remote ===<br />
A Smart Phone Remote is simply an app installed on your iPhone/iPod/iPad or any other smart device capable of communicating with your XBMC machine through the internet. The remote control app can work through your home's wifi or even if you're away from home with the proper external IP address setup.<br />
<br />
There are several free and paid apps with various capabilities in addition to basic remote functionalities such as browsing your XBMC library remotely and bringing up a virtual keyboard for Qwerty needs.<br />
<br />
XBMC provides official iOS and Android remote control apps that you are welcome to try yourself. To learn more, visit the [http://xbmc.org/about/xbmc-software/ XBMC Software page].<br />
<br />
=== Other Remotes ===<br />
There are a few other forms of remote and remote-type devices that are also worth noting.<br />
<br />
==== Mini Keyboards ====<br />
Devices like the [http://www.logitech.com/en-us/keyboards/keyboard/devices/3848 Logitech diNovo Mini Keyboard] blurs the lines between a conventional remote and a keyboard.<br />
<br />
List of Mini Keyboards here<br />
<br />
==== Blue Tooth Remotes ====<br />
IR is an old technology now, IR remotes for TVs have been around since the 1950's, and it is starting to show its age when compared to other technologies.<br />
<br />
Disadvantages of IR:<br />
* Requires line-of-sight<br />
* Limited range<br />
* Unable to send multiple commands at the same time<br />
<br />
This is where technologies such as bluetooth have the potential to replace IR in the future. To a point this has already begun with the PS3 and a select few TV manufacturers using bluetooth remotes.<br />
<br />
Most bluetooth remotes are of no use as an All in One as there isn't enough devices out there that use bluetooth, but they are potentially an excellent way to control a media centre. Bluetooth receivers are very cheap these day $5-$10 and can be easily added to a HTPC.<br />
<br />
There are only a very small number of bluetooth remotes available at the moment, but this list is likely to grow over the next few years:<br />
* PS3 Remote<br />
* [[TiVo Slide]]<br />
* [http://www.blu-link.com/ Blu-Link Universal Remote] (bluetooth and IR)<br />
<br />
== Keymap.xml and Remote.xml ==<br />
<br />
* [[Keyboard.xml]]<br />
* [[Modifying keyboard.xml]]<br />
<br />
<br />
<br />
[[Category:Remotes|*]]<br />
[[Category:XBMC Manual]]<br />
[[Category:General topics]]</div>Sashamalohttps://kodi.wiki/index.php?title=Archive:Speedlink_SL-6399&diff=64175Archive:Speedlink SL-63992013-09-11T17:18:58Z<p>Sashamalo: add a link to SL-6399-SBK</p>
<hr />
<div>{{Remote<br />
|Name= Speedlink SL-6399<br />
|Image= remote-SL6399.jpg<br />
|Description= Cheap and cheerful remote. It simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX.<br />
<br />
Apparently there are different usb receivers that come with the remote.<br />
<pre><br />
ID 1241:1503 Belkin Keyboard // all keys seem to work<br />
ID 1241:e000 Belkin // keys Start, RTV, Videos, Music, Pictures, MyTV don't work<br />
</pre><br />
<br />
There are several extra buttons not on the standard MS remote. If you want to add mappings for<br />
these keys here are the entries you need in keyboard.xml.<br />
<br />
<pre>&lt;t mod="ctrl"&gt;Notification(Key, TV power, 3)&lt;/t&gt; &lt;!-- TV power --&gt;<br />
&lt;menu&gt;Notification(Key, More, 3)&lt;/menu&gt; &lt;!-- More --&gt;<br />
&lt;z mod="ctrl,shift"&gt;Notification(Key, Aspect, 3)&lt;/z&gt; &lt;!-- Aspect --&gt;<br />
&lt;e mod="ctrl"&gt;Notification(Key, Red/Videos, 3)&lt;/e&gt; &lt;!-- Red/Videos --&gt;<br />
&lt;m mod="ctrl"&gt;Notification(Key, Green/Music, 3)&lt;/m&gt; &lt;!-- Green/Music --&gt;<br />
&lt;i mod="ctrl"&gt;Notification(Key, Yellow/Pictures, 3)&lt;/i&gt; &lt;!-- Yellow/Pictures --&gt;<br />
&lt;t mod="ctrl,shift"&gt;Notification(Key, Blue/MyTV, 3)&lt;/t&gt; &lt;!-- Blue/MyTV --&gt;<br />
&lt;g mod="ctrl"&gt;Notification(Key, Guide, 3)&lt;/g&gt; &lt;!-- Guide --&gt;<br />
&lt;o mod="ctrl"&gt;Notification(Key, RTV, 3)&lt;/o&gt; &lt;!-- RTV --&gt;<br />
&lt;f1&gt;Notification(Key, Help, 3)&lt;/f1&gt; &lt;!-- Help --&gt;<br />
&lt;return mod="alt"&gt;Notification(Key, Maximise, 3)&lt;/return&gt; &lt;!-- Maximise/restore --&gt;<br />
&lt;a mod="ctrl"&gt;Notification(Key, Radio, 3)&lt;/a&gt; &lt;!-- Radio --&gt;<br />
&lt;m mod="ctrl,shift"&gt;Notification(Key, DVD, 3)&lt;/m&gt; &lt;!-- DVD --&gt;<br />
&lt;a mod="ctrl,shift"&gt;Notification(Key, Audio, 3)&lt;/a&gt; &lt;!-- Audio --&gt;<br />
&lt;u mod="ctrl"&gt;Notification(Key, Title, 3)&lt;/u&gt; &lt;!-- Title --&gt;</pre><br />
<br />
:''See also [[Speedlink_SL-6399-SBK|keyboard.xml sample for SL-6399-SBK]]''<br />
}}</div>Sashamalohttps://kodi.wiki/index.php?title=Archive:Asrock_Remote&diff=64169Archive:Asrock Remote2013-09-11T10:09:37Z<p>Sashamalo: </p>
<hr />
<div>{{Remote<br />
|Name= Asrock Remote<br />
|Image= AsrockRemote.jpg<br />
|Description= The Asrock ION PC's come with a remote control and some models the HT Also include a internal CIR receiver.<br />
<br />
== '''Windows''' ==<br />
=== '''Information''' ===<br />
This is compatible with the Microsoft remote, and in Windows 7 (and possibly Vista) the .reg files used to reconfigure the MS remote will also work with the Asrock remote. The .reg files will not work in Windows XP because Windows XP does not detect the remote as an eHome device and install the eHome driver. It is possible the eHome drive could be installed with suitable modifications to irbus.inf (see the review of the HP remote above) but so far this has not been explored.<br />
<br />
=== '''Configuration''' ===<br />
With the Remote-XBMC.reg config all the buttons work in XBMC except for the four buttons in the row above the coloured buttons. To configure these buttons to send the standard Media center keyboard shortcuts add the following to the .reg file:<br />
<br />
<pre><br />
47,00,00,00,04,01,10,\ ; Asrock remote: Music - sends ctrl-M<br />
49,00,00,00,04,01,0C,\ ; Asrock remote: Pictures - sends ctrl-I<br />
4A,00,00,00,04,01,08,\ ; Asrock remote: Movies - sends ctrl-E<br />
50,00,00,00,04,01,04,\ ; Asrock remote: Radio - sends ctrl-A<br />
</pre><br />
{{note|Some Asrock ION330HT ship with a Nuvoton W836x7HG CIR Device Driver with is not RC6 compatible. In this case the Windows registry fix for the ehome driver will not work. This is not true for Linux.}}<br />
<br />
== '''Linux Ubuntu''' ==<br />
<br />
=== '''Information''' ===<br />
Asrock ION330HT with remote and internal CIR receiver compatible with any MCE remote.<br />
<br />
From Ubuntu 11.10 and up-to 12.10 including 12.04LTS getting the internal CIR + remote to work with Lirc + XBMC is rather a simple process.<br />
<br />
=== '''Configuration''' ===<br />
If Lirc is not installed we install it now:<br />
<source lang="bash"><br />
sudo apt-get install lirc<br />
</source><br />
If LIRC is already installed do:<br />
<source lang="bash"><br />
sudo dpkg-reconfigure lirc<br />
</source><br />
Remote control configuration:<br />
* Windows Media Center Transceivers/Remotes (all)<br />
IR transmitter, if present:<br />
* None<br />
<br />
Next change the default configuration to work with the Nuvoton remote<br />
<source lang="bash"><br />
sudo nano /etc/lirc/hardware.conf<br />
</source><br />
Change the following 3 lines from:<br />
<source lang="xml"><br />
REMOTE="Windows Media Center Transceivers/Remotes (all)"<br />
REMOTE_MODULES="lirc_dev mceusb"<br />
REMOTE_DRIVER=""<br />
</source><br />
Into the following<br />
<source lang="xml"><br />
REMOTE="Nuvoton Transceivers/Remotes"<br />
REMOTE_MODULES="lirc_dev nuvoton-cir"<br />
REMOTE_DRIVER="default"<br />
</source><br />
Save changes with {{keypress|ctrl|O}} to save file & {{keypress|ctrl|X}} and close nano.<br />
<br />
Restart LIRC to apply the changes<br />
<source lang="bash"><br />
sudo service lirc restart <br />
</source><br />
<br />
And the remote should now be working with XBMC.<br />
}}</div>Sashamalo