Forum

Full Version: Howto configure support for X10 remote model OR32E
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
I'd like to share what I did to configure X10 remote model OR32E in XBIAN 1.0a5, in case it helps anyone or just for improving xbian next versions.

Create /etc/modprobe.d with the following blacklisted modules:
Code:
blacklist rc_medion_x10_or2x
blacklist ati_remote
blacklist rc_core

Create /etc/lirc/hardware/custom.conf with the following content:
Code:
# /etc/lirc/hardware/custom.conf
#
# Arguments which will be used when launching lircd
#LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false

#Don't start irexec, even if a good config file seems to exist.
#START_IREXEC=false

#Try to load appropriate kernel modules
#LOAD_MODULES=false

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="atilibusb"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE="/dev/lirc"
#MODULES=""

# Default configuration files for your hardware if any
#LIRCD_CONF=""
#LIRCMD_CONF=""

Change /etc/lirc/lircd.conf to:
Code:
begin remote

  name          X10-OR32E
  bits           16
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  pre_data_bits   8
  pre_data       0x14
  post_data_bits  16
  post_data      0x0
  gap          139984
  min_repeat      2
  toggle_bit_mask 0x80800000

      begin codes
          KEY_POWER                0xD702
          KEY_RED                  0x0732
          KEY_YELLOW               0x89B4
          KEY_GREEN                0x0833
          KEY_TEXT                 0x6B96
          KEY_BLUE                 0x0A35
          KEY_BACK                 0x75A0
          KEY_INFO                 0x042F
          KEY_UP                   0x6F9A
          KEY_LEFT                 0xF21D
          KEY_OK                   0x739E
          KEY_RIGHT                0xF41F
          KEY_DOWN                 0x77A2
          KEY_TIMESHIFTING         0xED18
          KEY_EPG                  0x86B1
          KEY_DVDMENU              0xD904
          KEY_LIVETV               0x719C
          KEY_VOLUMEUP             0xDE09
          KEY_WINDOWS              0x709B
          KEY_CHANNELUP            0xE00B
          KEY_VOLUMEDOWN           0x5D88
          KEY_CHANNELDOWN          0xE10C
          KEY_MUTE                 0x5580
          KEY_PREVIOUS             0xF621
          KEY_NEXT                 0x78A3
          KEY_REWIND               0xF924
          KEY_PLAY                 0x7AA5
          KEY_FASTFORWARD          0xFB26
          KEY_RECORD               0x7CA7
          KEY_STOP                 0xFD28
          KEY_PAUSE                0x7EA9
          KEY_1                    0xE20D
          KEY_2                    0x638E
          KEY_3                    0x648F
          KEY_4                    0xE510
          KEY_5                    0x6691
          KEY_6                    0xE712
          KEY_7                    0x6893
          KEY_8                    0xE914
          KEY_9                    0x6A95
          KEY_*                    0x0C37
          KEY_0                    0x6C97
          KEY_#                    0x0D38
          KEY_CLEAR                0x85B0
          KEY_ENTER                0x0B36
      end codes

end remote

Create /home/xbian/.xbmc/userdata/Lircmap.xml with the following content:
Code:
<!-- This file contains the mapping of LIRC keys to XBMC keys used in Keymap.xml  -->

<lircmap>
        <remote device="X10-OR32E">
                <pause>KEY_PAUSE</pause>
                <stop>KEY_STOP</stop>
                <forward>KEY_FASTFORWARD</forward>
                <reverse>KEY_REWIND</reverse>
                <left>KEY_LEFT</left>
                <right>KEY_RIGHT</right>
                <up>KEY_UP</up>
                <down>KEY_DOWN</down>
                <select>KEY_OK</select>
                <pageplus>KEY_CHANNELUP</pageplus>
                <pageminus>KEY_CHANNELDOWN</pageminus>
                <back>KEY_BACK</back>
                <menu>KEY_WINDOWS</menu>
                <title>KEY_INFO</title>
                <info>KEY_TIMESHIFTING</info>
                <skipplus>KEY_NEXT</skipplus>
                <skipminus>KEY_PREVIOUS</skipminus>
                <display></display>
                <start>KEY_PLAY</start>
                <record>KEY_RECORD</record>
                <volumeplus>KEY_VOLUMEUP</volumeplus>
                <volumeminus>KEY_VOLUMEDOWN</volumeminus>
                <mute>KEY_MUTE</mute>
                <myvideo>KEY_GREEN</myvideo>
                <mymusic>KEY_RED</mymusic>
                <mypictures>KEY_YELLOW</mypictures>
                <mytv>KEY_BLUE</mytv>
                <one>KEY_ONE</one>
                <two>KEY_TWO</two>
                <three>KEY_THREE</three>
                <four>KEY_FOUR</four>
                <five>KEY_FIVE</five>
                <six>KEY_SIX</six>
                <seven>KEY_SEVEN</seven>
                <eight>KEY_EIGHT</eight>
                <nine>KEY_NINE</nine>
                <zero>KEY_ZERO</zero>
                <PlayDVD>KEY_DVDMENU</PlayDVD>
                <ShowVideoMenu>KEY_TEXT</ShowVideoMenu>
                <NextSubtitle>KEY_*</NextSubtitle>
                <AudioNextLanguage>KEY_#</AudioNextLanguage>
                <ContextMenu>KEY_ENTER</ContextMenu>
        </remote>
</lircmap>

Add the following line inside the file /home/xbian/.xbmc/userdata/advancedsettings.xml:

Code:
<remotedelay>17</remotedelay>
Can you try if "suppress_repeat" in the lircd.conf acts as a replacement for "<remotedelay>17</remotedelay>"?
Yes, it works fine also removing the <remotedelay>17</remotedelay> from the advancedsettings.xml and adding a "suppress_repeat 4" in the lircd.conf file.

Thanks
Then i don't have to tinker with the advancedsettings.xml. Great!
Can you share a lsusb, dmesg and cat /proc/bus/input/devices (on pastebin) so i can add the remote to our auto-detect script.
Here's the info in pastebin: http://pastebin.com/0VnhPxk1

You'll see info about a "Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver" that has nothing to do with the X10 receiver (it's the receiver of a wireless keyboard).

I've found an image of the X10 OR32E remote in Amazon:

http://ecx.images-amazon.com/images/I/41g8xm4PDjL._SL500_AA300_.jpg

Part of my configuration is based on a post about an X10 OR22V configuration for lirc you can find in:
http://www.mythtvtalk.com/how-configure-x10-wti-rf-receiver-8407/

It seems that both remotes (OR32E and OR22V) are pretty similar.
Can you try the files i put on git and see if they work?
(6th Mar, 2013 08:45 AM)CurlyMo Wrote: [ -> ]Can you try the files i put on git and see if they work?

No problem. Ley me know URL of the git and the files I must try. Did you include an alternative to the blacklisting of modules (ie: rmmod)?
Ok. I'll try it asap and ley you know how it goes. Thank you!
Hello,

it works OK. Good job!

I've added some keys of the remote that were missing in x10-or32e.conf and changed some mappings for my remote in Lircmap.xml to make it more usable.

New x10-or32e.conf is:
Code:
begin remote

  name          X10-OR32E
  bits           16
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  pre_data_bits   8
  pre_data       0x14
  post_data_bits  16
  post_data      0x0
  gap          139984
  min_repeat      2
  suppress_repeat 4
  toggle_bit_mask 0x80800000

      begin codes
          KEY_LIVETV               0x012C
          KEY_RECORDEDTV           0xF11C
          KEY_PHOTO                0x5A85
          KEY_MUSIC                0xDB06
          KEY_VIDEO                0x82AD
          KEY_BLUE                 0x8AB5              
          KEY_POWER                0xD702
          KEY_GREEN                0x0732
          KEY_YELLOW               0x89B4
          KEY_RED                  0x0833
          KEY_TEXT                 0x6B96
          KEY_BACK                 0x75A0
          KEY_INFO                 0x042F
          KEY_UP                   0x6F9A
          KEY_LEFT                 0xF21D
          KEY_OK                   0x739E
          KEY_RIGHT                0xF41F
          KEY_DOWN                 0x77A2
          KEY_TIMESHIFTING         0xED18
          KEY_EPG                  0x86B1
          KEY_DVDMENU              0xD904
          KEY_VOLUMEUP             0xDE09
          KEY_WINDOWS              0x709B
          KEY_CHANNELUP            0xE00B
          KEY_VOLUMEDOWN           0x5D88
          KEY_CHANNELDOWN          0xE10C
          KEY_MUTE                 0x5580
          KEY_PREVIOUS             0xF621
          KEY_NEXT                 0x78A3
          KEY_REWIND               0xF924
          KEY_PLAY                 0x7AA5
          KEY_FASTFORWARD          0xFB26
          KEY_RECORD               0x7CA7
          KEY_STOP                 0xFD28
          KEY_PAUSE                0x7EA9
          KEY_1                    0xE20D
          KEY_2                    0x638E
          KEY_3                    0x648F
          KEY_4                    0xE510
          KEY_5                    0x6691
          KEY_6                    0xE712
          KEY_7                    0x6893
          KEY_8                    0xE914
          KEY_9                    0x6A95
          KEY_*                    0x0C37
          KEY_0                    0x6C97
          KEY_#                    0x0D38
          KEY_CLEAR                0x85B0
          KEY_ENTER                0x0B36
      end codes

The new section covering this remote in Lircmap.xml is:
Code:
<remote device="X10-OR32E">
               <pause>KEY_PAUSE</pause>
               <stop>KEY_STOP</stop>
               <forward>KEY_FASTFORWARD</forward>
               <reverse>KEY_REWIND</reverse>
               <left>KEY_LEFT</left>
               <right>KEY_RIGHT</right>
               <up>KEY_UP</up>
               <down>KEY_DOWN</down>
               <select>KEY_OK</select>
               <pageplus>KEY_CHANNELUP</pageplus>
               <pageminus>KEY_CHANNELDOWN</pageminus>
               <back>KEY_BACK</back>
               <menu>KEY_WINDOWS</menu>
               <title>KEY_TIMESHIFTING</title>
               <info>KEY_INFO</info>
               <skipplus>KEY_NEXT</skipplus>
               <skipminus>KEY_PREVIOUS</skipminus>
               <display>KEY_YELLOW</display>
               <start>KEY_PLAY</start>
               <record>KEY_RECORD</record>
               <volumeplus>KEY_VOLUMEUP</volumeplus>
               <volumeminus>KEY_VOLUMEDOWN</volumeminus>
               <mute>KEY_MUTE</mute>
               <myvideo>KEY_VIDEO</myvideo>
               <mymusic>KEY_MUSIC</mymusic>
               <mypictures>KEY_PHOTO</mypictures>
               <mytv>KEY_LIVETV</mytv>
               <one>KEY_ONE</one>
               <two>KEY_TWO</two>
               <three>KEY_THREE</three>
               <four>KEY_FOUR</four>
               <five>KEY_FIVE</five>
               <six>KEY_SIX</six>
               <seven>KEY_SEVEN</seven>
               <eight>KEY_EIGHT</eight>
               <nine>KEY_NINE</nine>
               <zero>KEY_ZERO</zero>
               <PlayDVD>KEY_DVDMENU</PlayDVD>
               <ShowVideoMenu>KEY_BLUE</ShowVideoMenu>
               <NextSubtitle>KEY_RED</NextSubtitle>
               <AudioNextLanguage>KEY_GREEN</AudioNextLanguage>
               <ContextMenu>KEY_EPG</ContextMenu>
               <recordedtv>KEY_RECORDEDTV</recordedtv>
               <teletext>KEY_TEXT</teletext>
       </remote>

Kind regards
Changed. Thanks, let's hope the X10 problems are gone.
Just one thing I have noted. Sometimes after rebooting lirc doesn't start giving a message that it could initialize the USB receiver.

I remember that message because it's the same that I saw when trying to run lirc with atilibusb without removing the 3 kernel modules (ati_remote...). So I figure that lirc was starting before the modules where completely removed with the "modprobe -r". To solve it I've inserted a "sleep 2" after the three "modprobe -r" in hardware.conf, to give some time for the modules to unload completely.

I've rebooted three more times and it seems ok now.

I hope you understand me, my english is not native.

Regards
Updated...
(7th Mar, 2013 09:50 AM)CurlyMo Wrote: [ -> ]Updated...

Is there any solution for alpha5? Cant find these rows in .conf....
Pages: 1 2
Reference URL's