Revision as of 18:44, 8 December 2014

The EIB / KNX bus can be accessed via the eibd daemon. The original distribution at TU Wien is no longer maintained. The work has been taken over on SourceForge.

Before all, make sure you have installed an xPL hub and a control user.

Install eibd

Note: to my experience, this works on x86 machines, but not on armhf boards.

Copy the PGP public key to a local file eibPgp.key on your computer. Add it to the list of trusted keys:

su
apt-key add path-to/eibPgp.key

Add the repository to the debian package maintenance system: edit /etc/apt/sources.list and add the lines:

## EIB
deb http://www.auto.tuwien.ac.at/~mkoegler/debian eib main
deb-src http://www.auto.tuwien.ac.at/~mkoegler/debian eib main

Install the package:

apt-get update
apt-get install bcusdk

On the EIB side, the IP Router should be configured as a bus coupler (address nn.nn.0) and be provided a fixed IP address. In the following description, the address is 192.168.1.204 .

Test it: start the daemon in a terminal window:

su control
eibd -S -D -i ipt:192.168.1.204

Open another terminal window and monitor the traffic:

su control
groupsocketlisten ip:localhost

Pushing on an EIB button should be reported in the last terminal window.

In a 3rd terminal window, light-on a bulb:

su control
groupswrite ip:localhost 1/1/1 1

Install xPL EIB bridge

Download the Tapko EIB bridge script.

Move the script to xPL scripts directory:

SCRIPTS_BASE_DIR=/home/control/Documents/Controls
mv xpl-eib-Tapko.pl $SCRIPTS_BASE_DIR
chown control:users $SCRIPTS_BASE_DIR/*.pl
chmod 775 $SCRIPTS_BASE_DIR/*.pl

Test xPL EIB bridge

The test is shown here on a Linux machine such as a BeagleBone. It has to be slightly adapted on Mac OS.

Open a first terminal window (on any machine with xPL installed) and monitor the xPL protocol:

SCRIPTS_BASE_DIR=/home/control/Documents/Controls
$SCRIPTS_BASE_DIR/xpl-monitor.pl -vf

If the xPL serial port device isn't running, launch it in a second window:

su control
SCRIPTS_BASE_DIR=/home/control/Documents/Controls
ll /dev/ttyO*
$SCRIPTS_BASE_DIR/xpl-serial_port.pl -h
$SCRIPTS_BASE_DIR/xpl-serial_port.pl -v -n eib -e '\x0A\x0D' /dev/ttyO1 baudrate 9600 databits 8 parity none stopbits 1 handshake none

Open a further terminal window and start the xPL EIB bridge:

SCRIPTS_BASE_DIR=/home/control/Documents/Controls
$SCRIPTS_BASE_DIR/xpl-eib-Tapko.pl -v -n home -s dspc-serPort.eib -v

Open yet another terminal and send a message to the EIB bridge:

su control
SCRIPTS_BASE_DIR=/home/control/Documents/Controls
$SCRIPTS_BASE_DIR/xpl-send.pl -v -t cmnd -d dspc-eib.home -c eib.basic group='1/1/1' data=0x01

This should turn on EIB device 1/1/1. The monitor window should show how the EIB budge message triggered a serial port message for the Tapko EIB/KNX to RS232 converter.

Launch the xPL serial port device at startup

The EIB bridge is to be launched after the xPL serial port device which in turn is to be launched after the xPL hub.

Installing the serial port device to launch at system boot is described in the xPL serial port page.

Ubuntu

On Ubuntu, the xPL serial port device emits xpl-eibSerialPort_started at startup. This will be used to state-up the xPL EIB bridge.

Edit /etc/init/xpl-eib.conf:

################################################################################
# xPL EIB bridge, interfaves to a Tapko serial port
#
description "xPL EIB bridge"
version     "1.0"
author      "Francois Corthay"

#-------------------------------------------------------------------------------
# Configuration variables
#
env SCRIPTS_DIR='/home/control/Documents/Controls'
env SCRIPT_NAME='xpl-eib-Tapko.pl'
env PARAMETERS='-n home -s dspc-serPort.eib'

#-------------------------------------------------------------------------------
# Start and stop conditions
#
start on xpl-eibSerialPort_started          
stop on shutdown
respawn
setuid control
setgid users

#-------------------------------------------------------------------------------
# Start daemon
#
exec $SCRIPTS_DIR/$SCRIPT_NAME $PARAMETERS

Start the device and test it:

su root
service xpl-eib status
initctl emit xpl-eibSerialPort_started
service xpl-eib status

SCRIPTS_BASE_DIR=/home/control/Documents/Controls
$SCRIPTS_BASE_DIR/xpl-send.pl -v -t cmnd -d dspc-eib.home -c eib.basic group='1/1/1' data=0x01
$SCRIPTS_BASE_DIR/xpl-send.pl -v -t cmnd -d dspc-eib.home -c eib.basic group='1/1/1' data=0x00

Reboot the PC and check for the daemons:

ps ax | grep -i xpl | grep -v grep
initctl list | grep xpl

Mac OS

On Mac OS, the xPL EIB bridge starts-up later than the xPL serial port.

Edit /Library/LaunchDaemons/eib.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>Label</key>
    <string>xPL EIB bridge</string>
    <key>OnDemand</key>
    <false/>
    <key>UserName</key>
    <string>control</string>
    <key>ProgramArguments</key>
    <array>
      <string>/Users/control/Documents/Controls/xpl-eib-Tapko.pl</string>
      <string>-n</string>
      <string>home</string>
      <string>-s</string>
      <string>dspc-serPort.eib</string>
      <string>-w</string>
      <string>30</string>
    </array>
  </dict>
</plist>

Start the device and test it:

su root
launchctl load /Library/LaunchDaemons/xpl-eib.plist

SCRIPTS_BASE_DIR=/Users/control/Documents/Controls
$SCRIPTS_BASE_DIR/xpl-send.pl -v -t cmnd -d dspc-eib.home -c eib.basic group='1/1/1' data=0x01
$SCRIPTS_BASE_DIR/xpl-send.pl -v -t cmnd -d dspc-eib.home -c eib.basic group='1/1/1' data=0x00

Reboot the Mac and check for the daemons:

ps ax | grep -i xpl | grep -v grep
launchctl list | grep xPL