LinHES Forums
http://forum.linhes.org/

HOWTO: R5.5 iMON PAD, Veris Basic, etc
http://forum.linhes.org/viewtopic.php?f=11&t=19744		 Page 1 of 3
Author:  christ [ Sun Mar 29, 2009 2:33 pm ]
Post subject:  HOWTO: R5.5 iMON PAD, Veris Basic, etc
I've configured yet another front end but for space geometry issues, I was not able to use anothe Antec Fusion case so I ended up getting an Antec Veris Basic which fits into a spare 3.5" bay of, in my case, a Sonata 3.

The best thing about these IR detectors (Fusion & Veris) is that they can power on your system from cold. In effect the power button is daisy chained through the IR receiver before going to the Motherboard. So no more messing with BIOS settings etc.

While the Antec Fusion understands MCE remotes, Antec Veris understands the iMon remotes only. They are easiest to recognize by executing "lsusb" and looking for:
Code:
Bus 001 Device 003: ID 15c2:0043 SoundGraph Inc.
where the "15c2:0043" identifies this device. You will also see after updating lirc that both /dev/lirc0 & /dev/lirc1 exist.

While the Veris Basic only comes with a small remote control, the IR receiver actually understands the entire range. So in my case I use a Harmony 890 and use the setting of "SoundGraphRM200" which programs up the entire IR range. Not bad for C$42 device!

To support this device you will need lirc-0.8.5pre1 or later. This device actually shows up as TWO lirc devices (lirc0 and lirc1) so you will need a little more magic to combine these too.

In my config files, I tried not to modify the /home/mythtv/.mythtv/lircrc so that these config files would be as generic as possible (and help with inclusion in the build ) so I modified the lirc?.conf files to map into them. The only exception was the "tab" and "shift tab" options which I changed to "PreChapter" and "NextChapter". Modify either to suit.

In my case since I was using a Harmony remote, I also configured a separate "Power Off" button to allow the Harmony to shut down the PC when I am completely done and shutting the system down avoiding the need to suspend.

I have also label the Harmony labels in the lirc?.conf files in case you are trying to use that remote as well.

Enjoy!
Christ.
============

What you will require:
Installed KM with iMon remote (just puts most files in the right place)

lirc-0.8.5pre1 (or higher)

a custom /etc/init.d/lirc
-- this is needed to merge lirc0 & lirc1 into one socket for mythtv

lirc0.conf & lirc1.conf
-- my versions are below

PREPARING:
move the old lirc_imon.ko out of the way or it will interfere with loading the new one:
Code:
mv /lib/modules/2.6.23-chw-4/misc/lirc_imon.ko /lib/modules/2.6.23-chw-4/misc/lirc_imon.ko.old

In part as referenced in the how-to: http://www.knoppmythwiki.org/index.php?page=LIRCHowTo
Code:
cd /usr/src

verify sources point to stable and update apt.
Code:
vi /etc/apt/sources.list
apt-get update

Now get rid of the old stuff:
Code:
apt-get remove lirc

Code:
m-a update
m-a prepare

You also need to link the headers to the linux directory:
Code:
ln -s linux-headers-2.6.23-chw-4 linux

Double check that no ".ko" or ".so" files exist for lirc_imon or imonlcd
Code:
find / -name lirc\_imon\* -print

If you find some, move them out of the way by adding say ".old" to the file name. But the above procedures should have removed anything.

LIRC:
-------
Get and unpack the latest lirc:
Code:
cd /usr/src
wget http://www.lirc.org/software/snapshots/lirc-0.8.5pre1.tar.bz2
tar jxvf lirc-0.8.5pre1.tar.bz2
cd lirc-0.8.5pre1

Configure it by executing the following and choose "Driver Configuration" then "USB Devices" then "Soundgraph iMON IR/LCD", then "Save configuration and exit".
Code:
./setup.sh

After you run "setup.sh" you need to do edit the file "configure.sh" and add the line "--prefix=/usr \" so that "configure.sh" looks something like this:
Code:
#! /bin/sh
./configure \
--with-moduledir=/lib/modules/2.6.18-chw-13/misc \
--with-tty=/dev/ttyUSB0 \
--with-x \
--with-driver=usb_uirt_raw \
--with-major=61 \
--with-port=none \
--with-irq=none \
--prefix=/usr \
"$@"

Now configure, make and install:
Code:
sh configure.sh
make
make install

Now you can copy the hardware.conf, lirc0.conf, and lirc1.conf files to:
Code:
/etc/lirc/hardware.conf
/etc/lirc/lirc0.conf
/etc/lirc/lirc1.conf

and modify them as you see fit.

You should also verify "/home/mythtv/.mythtv/lircrc" to ensure your key mappings are to your liking. I increased the direction keys' "repeat" to about 9 as the sensitivity was a bit high in my case.

Finally copy the "/etc/init.d/lirc" code to "/etc/init.d/lirc"

After all this, reboot your system and everything should be working other than some custom tweaking.



DEFAULT FILES:
-------------------
These are for reference, modify to suit.

/etc/lirc/hardware.conf:
Code:
# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Soundgraph iMON IR/LCD"
REMOTE_MODULES="lirc_dev lirc_imon"
REMOTE_DRIVER="default"
REMOTE_DEVICE="/dev/lirc0"
REMOTE_LIRCD_CONF="/etc/lirc/lirc0.conf"
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="Soundgraph iMON IR/LCD"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER="default"
TRANSMITTER_DEVICE="/dev/lirc1"
TRANSMITTER_LIRCD_CONF="/etc/lirc/lirc1.conf"
TRANSMITTER_LIRCD_ARGS=""

#Enable lircd
START_LIRCD="true"

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

#Try to load appropriate kernel modules
LOAD_MODULES="true"

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

#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""



/etc/lirc/lirc0.conf: (** all new created with my Harmony remote **)
Code:
# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.8.4(default) on Sat Oct 18 02:21:26 2008
#
# contributed by Jean-Yves Avenard
#
# brand:                       Antec Fusion Remote
# model no. of remote control: MX200
# devices being controlled by this remote:
#

begin remote

  name  rm200
  bits           32
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  gap          195997
  toggle_bit   0

      begin codes
          PadKeyUp                 0x1008000  #Harmony labels this DirectionUp
          PadKeyLeft               0x1000080  #Harmony labels this DirectionLeft
          PadKeyRight              0x100007F  #Harmony labels this DirectionRight
          PadKeyDown               0x1007F00  #Harmony labels this DirectionDown
          Select                   0x2000028  #Harmony labels this Enter
          Enter                    0x200002C  #Harmony labels this Select
          Backspace                0x200002A
          Menu                     0x2000065  #Harmony labels this Menu (DropDown)
          WindowsKey               0x2800000  #Harmony labels this Menu (Windows)
          LClick                   0x1010000
          RClick                   0x1020000
          Esc                      0x2000029  #Harmony labels this Escape
          1                        0x200001E
          2                        0x200001F
          3                        0x2000020
          4                        0x2000021
          5                        0x2000022
          6                        0x2000023
          7                        0x2000024
          8                        0x2000025
          9                        0x2000026
          0                        0x2000027
          *                        0x2200025  #Harmony labels this Left
          #                        0x2200020  #Harmony labels this Right
      end codes

end remote



/etc/lirc/lirc1.conf: (** This is based on the default iMon lircd in KnoppMyth **)
Code:
# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.7.1pre2(imon) on Tue Mar  1 23:15:44 2005
#
# brand:                       iMON-New
# model no. of remote control: iMON-PAD
# devices being controlled by this remote:
#

begin remote

  name     iMON-PAD
  bits           32
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  gap          235965
  min_repeat      1
  toggle_bit      29


      begin codes

          AppExit                  0x288195B7
          Power                    0x289115B7  #Harmony labels this Pwr
          Record                   0x298115B7
          Play                     0x2A8115B7
          SlowMotion               0x29B195B7  #Harmony labels this Eject
          Rewind                   0x2A8195B7
          Pause                    0x2A9115B7
          FastForward              0x2B8115B7
          PrevChapter              0x2B9115B7  #Harmony labels this SkipBackward
          Stop                     0x2B9715B7
          NextChapter              0x298195B7  #Harmony labels this SkipForward

          Esc                      0x2BB715B7  #Harmony labels this Escape
          Eject                    0x299395B7  #Harmony labels this Open/Close
          AppLauncher              0x29B715B7
          Computer                 0x2AB195B7  #aka MultiMon on other iMon remotes
          TaskSwitcher             0x2A9395B7
          Mute                     0x2B9595B7
          Vol+                     0x28A395B7  #Harmony labels this VolumeUp
          Vol-                     0x28A595B7  #Harmony labels this VolumeDown
          Ch+                      0x289395B7  #Harmony labels this ChannelUp
          Ch-                      0x288795B7  #Harmony labels this ChannelDown
          Timer                    0x2B8395B7

          1                        0x28B595B7
          2                        0x2BB195B7
          3                        0x28B195B7
          4                        0x2A8595B7
          5                        0x299595B7
          6                        0x2AA595B7
          7                        0x2B9395B7
          8                        0x2A8515B7
          9                        0x2AA115B7
          0                        0x2BA595B7
          ShiftTab                 0x28B515B7  #not on Harmony
          Tab                      0x29A115B7  #not on Harmony

          MyMovie                  0x2B8515B7  #Harmony labels this Red
          MyMusic                  0x299195B7  #Harmony labels this Green
          MyPhoto                  0x2BA115B7  #Harmony labels this Blue
          MyTV                     0x28A515B7  #Harmony labels this Yellow

          Bookmark                 0x288515B7
          Thumbnail                0x2AB715B7
          AspectRatio              0x29A595B7  #Harmony labels this Aspect
          FullScreen               0x2AA395B7

          MyDVD                    0x29A295B7
          MyDVD                    0x29A395B7
          Menu                     0x2BA385B7
          Menu                     0x2BA395B7
          Caption                  0x298595B7
          Language                 0x2B8595B7

          MouseKeyboard            0x299115B7  #Harmony labels this Mouse/Keyboard
          SelectSpace              0x2A9315B7
          MouseMenu                0x28B715B7
          MouseRightClick          0x688481B7
          Enter                    0x28A195B7
          MouseLeftClick           0x688301B7
          WindowsKey               0x2B8195B7
          Backspace                0x28A115B7

          PadKeyUp                 0x690281B7
          PadKeyDown               0x688291B7
          PadKeyLeft               0x6A8281B7
          PadKeyRight              0x688A81B7

# cursor pad - GMC AVC-S7 case
          KeyAVCenter              0x0000000F
          KeyBack                  0x00000017
          KeyUp                    0x00000012
          KeyDown                  0x00000013
          KeyLeft                  0x00000014
          KeyRight                 0x00000015
          KeyOK                    0x00000016

      end codes

end remote



/etc/init.d/lirc: (** courtesy of JY Avenard **)
Code:
#! /bin/sh
### BEGIN INIT INFO
# Provides:          lirc
# Required-Start:    $syslog
# Required-Stop:     $syslog
# Should-Start:      $local_fs
# Should-Stop:       $local_fs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Starts LIRC daemon.
# Description:       LIRC is used to control different
#                    infrared receivers and transceivers.
### END INIT INFO

load_modules ()
{
    local MODULES_MISSING=false

    log_daemon_msg "Loading LIRC modules"
    for mod in $*
    do
        if [ $mod = "udev" ]; then
            log_end_msg 0
            log_success_msg "Restarted via udev, don't reload modules"
            break
        else
            modprobe -k $mod 2> /dev/null || MODULES_MISSING=true
        fi
    done
    log_end_msg $?

    if $MODULES_MISSING; then
        log_failure_msg "Unable to load LIRC kernel modules. Verify your"
        log_failure_msg "selected kernel modules in /etc/lirc/hardware.conf"
        START_LIRCMD=false
        START_LIRCD=false
    fi
}

build_remote_args ()
{
    local REMOTE_ARGS="$*"

    #For remote only detection support, we need
    #both REMOTE_DEVICE and TRANSMITTER_DEVICE undefined
    if [ -z "$REMOTE_DEVICE" ] && [ -z "$TRANSMITTER_DEVICE" ]; then
        for dev in /dev/lirc0; do
            if [ -c $dev ]; then
                REMOTE_DEVICE="$dev"
                break
            fi
        done
    fi

    #If we have a REMOTE_DEVICE or REMOTE_DRIVER defined (either because no devices
    #were defined, OR if we explicitly did), then populate REMOTE_ARGS
    if [ ! -z "$REMOTE_DEVICE" ] || [ ! -z "$REMOTE_DRIVER" ]; then
        if [ -n "$REMOTE_DEVICE" ] && [ "$REMOTE_DEVICE" != "none" ]; then
            REMOTE_ARGS="--device=$REMOTE_DEVICE $REMOTE_ARGS"
        fi
        if [ -n "$REMOTE_DRIVER" ] && [ "$REMOTE_DRIVER" != "none" ]; then
            REMOTE_ARGS="--driver=$REMOTE_DRIVER $REMOTE_ARGS"
        fi

        #Now, if we ALSO have a transmitter defined, add some args
        #To make the first lircd listen up
        if [ ! -z "$TRANSMITTER_DEVICE" ] || [ ! -z "$TRANSMITTER_DRIVER" ]; then
            REMOTE_ARGS="$REMOTE_ARGS --output=/dev/lircd --listen"
        fi
    fi
    echo $REMOTE_ARGS
}

build_transmitter_args ()
{
    local TRANSMITTER_ARGS="$*"

    #Transmitters must be explicitly be defined
    if [ ! -z "$TRANSMITTER_DEVICE" ] || [ ! -z "$TRANSMITTER_DRIVER" ]; then
        if [ -n "$TRANSMITTER_DEVICE" ] && [ "$TRANSMITTER_DEVICE" != "none" ]; then
            TRANSMITTER_ARGS="--device=$TRANSMITTER_DEVICE $TRANSMITTER_ARGS"
        fi
        if [ -n "$TRANSMITTER_DRIVER" ] && [ "$TRANSMITTER_DRIVER" != "none" ]; then
            TRANSMITTER_ARGS="--driver=$TRANSMITTER_DRIVER $TRANSMITTER_ARGS"
        fi

        #Now, if we ALSO have a remote defined, add some args
        #To make the second lircd connect
        if [ ! -z "$REMOTE_DEVICE" ] || [ ! -z "$REMOTE_DRIVER" ]; then
            TRANSMITTER_ARGS="$TRANSMITTER_ARGS --output=/dev/lircd --connect=localhost:8765 --pidfile=/var/run/lircd1.pid"
        fi
    fi
    echo $TRANSMITTER_ARGS
}

. /lib/lsb/init-functions

test -f /usr/sbin/lircd || exit 0
test -f /usr/sbin/lircmd || exit 0

START_LIRCMD=true
START_LIRCD=true

if [ -f /etc/lirc/hardware.conf ];then
    . /etc/lirc/hardware.conf
fi

if [ ! -f /etc/lirc/lircd.conf ] \
    || grep -q "^#UNCONFIGURED"  /etc/lirc/lircd.conf;then
    if [ "$1" = "start" ]; then
        log_success_msg "No valid /etc/lirc/lircd.conf has been found."
        log_success_msg "Remote control support has been disabled."
        log_success_msg "Reconfigure LIRC or manually replace /etc/lirc/lircd.conf to enable."
    fi
    START_LIRCD=false
    START_LIRCMD=false
fi
if [ ! -f /etc/lirc/lircmd.conf ] \
    || grep -q "^#UNCONFIGURED" /etc/lirc/lircmd.conf;then
    START_LIRCMD=false
fi

case "$1" in
    start)
        if [ "$LOAD_MODULES" = "true" ] && [ "$START_LIRCD" = "true" ]; then
            load_modules $2 $REMOTE_MODULES $TRANSMITTER_MODULES $MODULES
        fi
        if $START_LIRCD; then
            log_daemon_msg "Starting remote control daemon(s) : LIRC "
            REMOTE_LIRCD_ARGS=`build_remote_args $REMOTE_LIRCD_ARGS $REMOTE_LIRCD_CONF`
            TRANSMITTER_LIRCD_ARGS=`build_transmitter_args $TRANSMITTER_LIRCD_ARGS $TRANSMITTER_LIRCD_CONF`

            #if we have a remote defined, it is primary process
            if [ ! -z "$REMOTE_LIRCD_ARGS" ]; then
                start-stop-daemon --start --quiet --exec /usr/sbin/lircd -- $REMOTE_LIRCD_ARGS < /dev/null
                log_end_msg $?

                #now if we additionally have a transmitter defined, it is secondary process
                if [ ! -z "$TRANSMITTER_LIRCD_ARGS" ]; then
                    /usr/sbin/lircd $TRANSMITTER_LIRCD_ARGS < /dev/null
                fi
            elif [ ! -z "$TRANSMITTER_LIRCD_ARGS" ]; then
                start-stop-daemon --start --quiet --exec /usr/sbin/lircd -- $TRANSMITTER_LIRCD_ARGS < /dev/null
            else
                log_end_msg 1
            fi
        fi
        if $START_LIRCMD; then
            log_daemon_msg "Starting remote control mouse daemon : LIRCMD "
            start-stop-daemon --start --quiet --exec /usr/sbin/lircmd < /dev/null
            log_end_msg $?
        fi
        ;;
    stop)
        if $START_LIRCMD; then
            log_daemon_msg "Stopping remote control mouse daemon: LIRCMD"
            start-stop-daemon --stop --quiet --exec /usr/sbin/lircmd
            log_end_msg $?
        fi
        if $START_LIRCD; then
            log_daemon_msg "Stopping remote control daemon(s): LIRC"
            start-stop-daemon --stop --quiet --exec /usr/sbin/lircd
            log_end_msg $?
        fi
        ;;
    reload|force-reload)
        if $START_LIRCD; then
            start-stop-daemon --stop --quiet --signal 1 --exec /usr/sbin/lircd
        fi
        if $START_LIRCMD; then
            start-stop-daemon --stop --quiet --signal 1 --exec /usr/sbin/lircmd
        fi
        ;;
    restart)
        $0 stop
        #passes parameter $2 which is possibly our udev paramater
        $0 start $2
        ;;
    *)
        echo "Usage: /etc/init.d/lircd {start|stop|reload|restart|force-reload}"
        exit 1
esac

exit 0
Author:  speed32219 [ Sat May 09, 2009 2:36 pm ]
Post subject: 
I have been trying to get the Veris basic 0043 device working now for 2 weeks.
lsusb Bus 001 Device 004: ID 15c2:0043 SoundGraph Inc.

I am so glad I found your post, it is nice to know that someone has got this thing working.

I do not have KM installed but I have been following your directions without success. KM must have installed some part of lirc that I am missing. I do not show /dev/lirc0 or lirc1 in the /dev directory, only lircd is there. I also tried installing lirc 8.0.4a first & then removing followed up by. lirc-0.8.5pre1 and the continued steps from your post. I made so many changes, was close at one time I think, but never saw anything register when using irw or irrecord, except for the little blue light flashing on the veris device when it saw a key depressed.

I just now re-installed ubuntu 2.6.27.7 since I had so many changes, I had lost count. I do have another machine with the Imon IR and LCD working, ANtec Veris Fusion Black V2 case, which came with the LCD and IR installed. I only wanted a front end with a small inexpensive $42 remote, but it is killing me. I have backup up root just in case I screw everything up again, it takes time installing all the restricted drivers and special programs I have. LOL!

Any suggestions, like first install lirc from the repositories and start on line one of your post? Does KM install lirc and client sw from the get go?

Thanks for your post, like I said it is good to see someone that has this running.
Author:  christ [ Mon May 11, 2009 11:39 am ]
Post subject: 
Don't give up!

I think you haven't installed the driver properly. The correct driver should create /dev/lirc0 and lirc1.

You need at least lirc-0.8.5pre1 (I know pre2 is out now). 0.8.4.a doesn't have the changes in it for this device.

Verify the lirc version using:
Code:
lircd -v

I haven't used Ubuntu so I can't help with that but to I would remove any existing lirc (using whatever package manager is on ubuntu) and then make sure it is gone by setting aside the .ko files (like I explain in the How-to but your will be in a different place)

From there get either pre1 or pre2 and compile and install it. If you get this right, you should have lirc0 and lirc1 in your /dev folder.

BTW, I also have the Antec Fusion for another front end and it works great too but is a very different device from this one.
Author:  marc.aronson [ Sat May 23, 2009 9:34 pm ]
Post subject: 
I am attempting to follow the instructions but I am hitting a snag. lircd is somehow being installed in /usr/local/sbin/lircd and /usr/sbin/lircd still has the old version. This is causing all kinds of problems. Any help would be greatly appreciated.

Updated May 24, 2009: Found out why it's being installed in the wrong directory -- there is a missing step in Christ's instructions. After you run "setup.sh" you need to do edit the file "configure.sh" and add the line "--prefix=/usr \" so that "configure.sh" looks something like this:
Code:
#! /bin/sh
./configure \
--with-moduledir=/lib/modules/2.6.18-chw-13/misc \
--with-tty=/dev/ttyUSB0 \
--with-x \
--with-driver=usb_uirt_raw \
--with-major=61 \
--with-port=none \
--with-irq=none \
--prefix=/usr \
"$@"
Author:  marc.aronson [ Sun May 24, 2009 2:07 am ]
Post subject: 
Well, this device is not working out well for me. I cannot get my Harmony 676 to work properly with this puppy. Based on what I've read in the Harmony forums, it looks like some of the Harmony remotes do not play well with the RM100 & RM200 remotes. I have submitted a ticket to Harmony support.
Author:  christ [ Sun May 24, 2009 10:56 am ]
Post subject: 
Hi Marc,
I too have them both but the paths are set up to find the /usr/local/sbin/ first. From root:
Code:
echo $PATH

I suppose the one in /usr/sbin should be removed and expected "apt-get remove lirc" would have removed it. That fact my search order is correct probably deals with this. However if any program directly referenced it then it would cause a problem. I don't know of any program/script that does. If you feel this is the source of your problem then you could try copying/linking the new version to the old location.

Before doing so verify the dates (to ensure your install worked) via:
Code:
ls -l /usr/sbin/lircd
ls -l /usr/local/sbin/lircd

You mention all kinds of problems but you don't say what they are. So I can't help with that.

Interesting question about the 676. How do you know it is not working? Did you in fact get the above problem worked out or are you testing this in some other manner? It will be useful to others to know of your outcome with the 676.

I have tested this with Harmony 880, and Harmony 890 via an IR extender.
Author:  marc.aronson [ Sun May 24, 2009 11:15 am ]
Post subject: 
Christ, the /etc/init.d/lirc script that is in your original post has several direct path references to /usr/sbin. The problem I was hitting was that I was still running the old version of LIRC. I've edited my original post and provided directions on how to get things installed to the correct location -- might be a good idea to add those directions to your original post.

I believe that my root PATH is still the R5.5 default, which places "/usr/sbin" before "/usr/local/sbin".

I've had a phone call with Harmony level 1 support. They tried several things without success, but they have passed it up to level 2. The guy on level 1 felt it was very likely that level 2 could solve the problem. I'll update on that later.

BTW, when you did you search for the remote in the harmony app, what manufacturer and model did you use? thanks!

marc
Author:  christ [ Sun May 24, 2009 11:50 am ]
Post subject: 
After I wrote that I went out to work on one of my cars and then it came to me that you are in fact correct. But now I wonder why mine worked. My suspicion is that the key piece is the drivers themselves and they happened to be compatible with the version of lircd I had. Did you use pre1 or pre3?

For the Harmony search, I believe I searched on iMon or possible Rm200. When I check with the Harmony software it identifies it as "SoundGraph RM200 Media Center PC"

I'll update the How-to later tonight.

C
Author:  marc.aronson [ Sun May 24, 2009 11:56 am ]
Post subject: 
christ wrote:
Interesting question about the 676. How do you know it is not working? Did you in fact get the above problem worked out or are you testing this in some other manner? It will be useful to others to know of your outcome with the 676.

I have tested this with Harmony 880, and Harmony 890 via an IR extender.

Christ, I realized that I didn't respond to this part of your previous post with specifics. There are actually several different issues:

1. If I attempt to add the device that corresponds to Manufacturer=Antec and Model=200 I get the following error message from the logitech tool when I try to update the remote: "Invalid protocol -- Context: HarmonyRemote=Harmony676, ConfiguratorName=Antec2 -- 1 Parameters: Imon Multi Bit Hex 7".

2. If I try to "teach" the harmony remote from the original RM100 remote using the standard learning technique, the harmony thinks it is successful but the recorded commands do not work in a consistent fashion. ie, sometimes a button press is ignored and sometimes it behaves as if I hit the button multiple times. Attempts to tune with the harmony sensitivity settings don't solve the problem

3. If I try to "teach" the harmony remote from the original RM100 remote using raw mode I see two different outcomes:

3a. If I hold the RM100 button for at least 1 second it will work, but it sends anywhere from 4-8 repeats of the same command when i use the Harmony remote. This creates horrible lag. ie, If I hit a button 3 times in a row, the 3 presses are processed with a 1-second delay between each response.

3b. If I hold the button for less than 1 second during the learning process, it just doesn't work.

4. If I try to use the database IR codes associated with the Manufacturer=Antec, model=100 the system does not respond to the remote at all.

Thoughts?
Author:  marc.aronson [ Sun May 24, 2009 12:01 pm ]
Post subject: 
christ wrote:
After I wrote that I went out to work on one of my cars and then it came to me that you are in fact correct. But now I wonder why mine worked. My suspicion is that the key piece is the drivers themselves and they happened to be compatible with the version of lircd I had. Did you use pre1 or pre3?

For the Harmony search, I believe I searched on iMon or possible Rm200. When I check with the Harmony software it identifies it as "SoundGraph RM200 Media Center PC"

I'll update the How-to later tonight.

C


We're exchange messages in semi-real-time. I used pre1, per your post. Is pre3 a more recent version? Perhaps i should give it a try.

BTW, the install process installs new versions of many utilities including irrecord, irw, etc. Unfortunately I still have everything installed in two places as I wasn't sure how to do a clean uninstall of the stuff in /usr/local/*, but I do have the same version of everything installed in both locations. I notice that the Makefile does have an "uninstall" target, so I may try to clean things up.
Author:  christ [ Sun May 24, 2009 7:25 pm ]
Post subject: 
Hi Marc,
Did you verify your change to configure.sh? If yes then I will update the how-to with this.

You alluded to other issues due to this. Once you made the configure.sh change did it otherwise work (at least with the RM100 remote)?

pre1 should be all you need as that has the correct drivers. I'm just puzzled why mine would work and yours did not given we are both using R5.5.

The essential difference, I believe is that pre1 includes the mods to the imon driver so in theory it would work with the old lircd anyway. I just don't know what you were seeing in terms of issues.
Author:  marc.aronson [ Sun May 24, 2009 10:30 pm ]
Post subject: 
Christ, the changes I listed to configure.sh are confirmed. I pulled them from the KM wiki LIRC article.

The RM100 remote is working properly, but getting there was very time consuming. I had to go through the "irrecord" process to create an appropraite lirc0.conf & lirc1.conf. (The two you posted don't work properly with the RM100 -- I look forward to being able to use them once harmony tech support gets my 676 behaving like an RM200 remote.) Normally creating a lirc.conf file isn't that hard, but irrecord with this device is tricky because you have to know in advance which button on the remote is recognized by which lirc device (0 or 1). If you accidentally try to "irrecord" the "OK" button via /dev/lirc1 LIRC hangs up and you have to go through a reset process to get things flowing again because "OK" is only recognized on /dev/lirc0. The final bit of pain is that the toggle_bit_mask created by irrecord isn't correct, resulting in some keys sending multiple keys with 1 press. After several google searchs I found the right settings.

In any event, here are the files for the rm100:

/etc/lirc/lirc0.conf:
Code:
# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.8.5pre1(default) on Sat May 23 19:34:46 2009
#
# contributed by
#
# brand:                       asdf
# model no. of remote control:
# devices being controlled by this remote:
#

begin remote

  name  lirc0
  bits            8
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  pre_data_bits   24
  pre_data       0x20000
  gap          211988
  toggle_bit_mask 0x14

      begin codes
          KEY_OK                   0x28
          KEY_MENU                 0x65
          KEY_ESC                  0x2A
      end codes

end remote


Here is /etc/lirc/lirc1.conf:
Code:
# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.8.3-CVS-pvr150-2(default) on Sat May 23 19:15:59 2009
#
# contributed by
#
# brand:                       lirc1.conf
# model no. of remote control:
# devices being controlled by this remote:
#

begin remote

  name  lirc1.conf
  bits           24
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  post_data_bits  8
  post_data      0xB7
  gap          211988
#  toggle_bit_mask 0x4000
  toggle_bit_mask 0x2000
#  toggle_bit_mask 0x200000000000
#  toggle_bit_mask 0x0

      begin codes
          Green                    0x288195
          Power                    0x289115
          Up                       0x2AA515
          Down                     0x289515
          Left                     0x29A515
          Right                    0x2BA515
          Vol+                     0x28A395
          Vol-                     0x28A595
          Mute                     0x2B9595
          Ch+                      0x289395
          Ch-                      0x288795
          Rewind                   0x298315
          Play                     0x2A8315
          Forward                  0x2B8315
          Go                       0x2AB195
      end codes

end remote
Author:  christ [ Mon May 25, 2009 8:42 am ]
Post subject: 
Thanks for confirming Marc. I'll update this right away. Did you also have to run configure.sh before the make? Or did the make pick this up?

BTW, I seem to recall some RM100 codes when I did a google search. I also note that the codes are very close except for direction keys (up,down, left, right) and possibly a couple of others. That's likely why they worked for me but given the bulk of my testing was with the Harmony remote I probably didn't notice the discrepancies.

Once you are comfortable with the RM100 codes then we can add these as RM100 specific codes and attached them to my feature request ticket in flyspray.
Author:  marc.aronson [ Mon May 25, 2009 10:10 am ]
Post subject: 
christ wrote:
Thanks for confirming Marc. I'll update this right away. Did you also have to run configure.sh before the make? Or did the make pick this up?

Yes, I did run "./configure.sh" before running make. This is necessary as "./configure.sh" creates the Makefile that is read by make.

christ wrote:
BTW, I seem to recall some RM100 codes when I did a google search.

I also found some, but they didn't work for me.

christ wrote:
Once you are comfortable with the RM100 codes then we can add these as RM100 specific codes and attached them to my feature request ticket in flyspray.


The RM100 codes work and are good to go.
Author:  christ [ Mon May 25, 2009 10:40 am ]
Post subject: 
Marc, thanks for verifying and fixing! ;-)

I've updated the how-to per your comments. Let me know if you see anything else.

I'll add the RM100 codes to my flyspray ticket as well.
Page 1 of 3 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/