Problem with bash-dce-knx

[rages]

Hi,

I finally completed installation of my apartment.
I have installed a system of automation KNX (Merten) throughout the house, with an HDPC (core) and an MD 3M touchscreen 17 "whit an atom 330, everything seems to work, but I can not install the drivers "bash - DCE - KNX".

I get to point:

<sup>After DCE_PATH is set, and exported, you can build the package with this command, in the DCE-whisperer directory:

dpkg-buildpackage-b-rfakeroot-us-uc <return></sup>

   
and I have this answer:

^{dcerouter_1:/home/bash-dce-knx/bash-dce-knx/DCE-whisperer# dpkg-buildpackage -rfakeroot -b -us -uc
dpkg-buildpackage: source package is dce-whisperer
dpkg-buildpackage: source version is 1.0
dpkg-buildpackage: source changed by root <root@unknown>
dpkg-buildpackage: host architecture i386
dpkg-buildpackage: source version without epoch 1.0
dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 5)
dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting.
dpkg-buildpackage: (Use -d flag to override.)
dcerouter_1:/home/bash-dce-knx/bash-dce-knx/DCE-whisperer#}


Help me PLZ

[totallymaxed]

Hi,

I finally completed installation of my apartment.
I have installed a system of automation KNX (Merten) throughout the house, with an HDPC (core) and an MD 3M touchscreen 17 "whit an atom 330, everything seems to work, but I can not install the drivers "bash - DCE - KNX".

I get to point:

<sup>After DCE_PATH is set, and exported, you can build the package with this command, in the DCE-whisperer directory:

dpkg-buildpackage-b-rfakeroot-us-uc <return></sup>

   
and I have this answer:

^{dcerouter_1:/home/bash-dce-knx/bash-dce-knx/DCE-whisperer# dpkg-buildpackage -rfakeroot -b -us -uc
dpkg-buildpackage: source package is dce-whisperer
dpkg-buildpackage: source version is 1.0
dpkg-buildpackage: source changed by root <root@unknown>
dpkg-buildpackage: host architecture i386
dpkg-buildpackage: source version without epoch 1.0
dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 5)
dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting.
dpkg-buildpackage: (Use -d flag to override.)
dcerouter_1:/home/bash-dce-knx/bash-dce-knx/DCE-whisperer#}


Help me PLZ

You have an unmet dependency in debhelper;

apt-get install debhelper <return>

That should do it...

Andrew

[rages]

Tnx Andrew,

but now there's a new problem:

^{dcerouter_1:/home/bash-dce-knx/bash-dce-knx/DCE-whisperer# dpkg-buildpackage -rfakeroot -b -us -uc
dpkg-buildpackage: source package is dce-whisperer
dpkg-buildpackage: source version is 1.0
dpkg-buildpackage: source changed by root <root@unknown>
dpkg-buildpackage: host architecture i386
dpkg-buildpackage: source version without epoch 1.0
 fakeroot debian/rules clean
/usr/bin/dpkg-buildpackage: line 201: fakeroot: command not found}

[Marie.O]

sudo apt-get install fakeroot

[jbr]

Hi rages,

I have recently installed KNX in my house and I'm considering trying the LinuxMCE.

Pls let us know how you find LinuxMCE together with KNX (if you get it to work...  )

/jbr

[totallymaxed]

Hi rages,

I have recently installed KNX in my house and I'm considering trying the LinuxMCE.

Pls let us know how you find LinuxMCE together with KNX (if you get it to work...  )

/jbr

We have several customers using KNX now and these installations are all using our bash-dec-knx device. These are reasonably big KNX installations with several hundred channels in use per installation.

All the best

Andrew

[rages]

I have another problem Andrew:

^{dcerouter_1:/home/bash-dce-knx/bash-dce-knx/DCE-whisperer# dpkg-buildpackage -rfakeroot -b -us -uc
dpkg-buildpackage: source package is dce-whisperer
dpkg-buildpackage: source version is 1.0
dpkg-buildpackage: source changed by root <root@unknown>
dpkg-buildpackage: host architecture i386
dpkg-buildpackage: source version without epoch 1.0
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp
# Add here commands to clean up after the build process.
/usr/bin/make clean
make[1]: Entering directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
make[1]: *** No rule to make target `clean'.  Stop.
make[1]: Leaving directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
make: [clean] Error 2 (ignored)
dh_clean
 debian/rules build
dh_testdir
# Add here commands to configure the package.
touch configure-stamp
dh_testdir
# Add here commands to compile the package.
/usr/bin/make
make[1]: Entering directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
#docbook-to-man debian/dce-whisperer.sgml > dce-whisperer.1
touch build-stamp
 fakeroot debian/rules binary
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs
# Add here commands to install the package into debian/dce-whisperer.
/usr/bin/make DESTDIR=/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/debian/dce-whisperer install
make[1]: Entering directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
/usr/bin/make -C src
make[2]: Entering directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/src'
Computing dependencies for ShellInterface.cpp done
Computing dependencies for Whisperer.cpp done
Computing dependencies for Main.cpp done
make[2]: Leaving directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/src'
make[2]: Entering directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/src'
g++ -c -I. -I/home/bash-dce-knx/pluto/src -pipe -W -Wall -ggdb3  Main.cpp -o Main.o
g++ -c -I. -I/home/bash-dce-knx/pluto/src -pipe -W -Wall -ggdb3  Whisperer.cpp -o Whisperer.o
g++ -c -I. -I/home/bash-dce-knx/pluto/src -pipe -W -Wall -ggdb3  ShellInterface.cpp -o ShellInterface.o
g++ -I. -I/home/bash-dce-knx/pluto/src -pipe -W -Wall -ggdb3  -o DCE-whisperer Main.o Whisperer.o ShellInterface.o -L/home/bash-dce-knx/pluto/src/lib -lSerial
izeClass -lDCECommon -lPlutoUtils
make[2]: Leaving directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/src'
mkdir -p "/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/debian/dce-whisperer/usr/pluto/bin"
cp src/DCE-whisperer "/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/debian/dce-whisperer/usr/pluto/bin"
make[1]: Leaving directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
dh_testdir
dh_testroot
dh_installchangelogs
dh_installdocs
dh_installexamples
dh_installman
dh_link
dh_strip
dh_compress
dh_fixperms
dh_installdeb
dh_shlibdeps
dpkg-shlibdeps: warning: format of 'NEEDED libSerializeClass.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED libDCECommon.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED libPlutoUtils.so' not recognized
dh_gencontrol
dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
dh_md5sums
dh_builddeb
dpkg-deb: building package `dce-whisperer' in `../dce-whisperer_1.0_i386.deb'.
 dpkg-genchanges -b
dpkg-genchanges: binary-only upload - not including any source code
dpkg-buildpackage: binary only upload (no source included)
dcerouter_1:/home/bash-dce-knx/bash-dce-knx/DCE-whisperer#}





and then I did not understand what this means ...

Go in Lights, add a on/off light. Set its room. Write "$00 $03" (w/o the quotes) in the "Port/Channel number" Device Data

applies to all the lights $00 and $03? where i write my group address?

[totallymaxed]

I have another problem Andrew:

^{dcerouter_1:/home/bash-dce-knx/bash-dce-knx/DCE-whisperer# dpkg-buildpackage -rfakeroot -b -us -uc
dpkg-buildpackage: source package is dce-whisperer
dpkg-buildpackage: source version is 1.0
dpkg-buildpackage: source changed by root <root@unknown>
dpkg-buildpackage: host architecture i386
dpkg-buildpackage: source version without epoch 1.0
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp
# Add here commands to clean up after the build process.
/usr/bin/make clean
make[1]: Entering directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
make[1]: *** No rule to make target `clean'.  Stop.
make[1]: Leaving directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
make: [clean] Error 2 (ignored)
dh_clean
 debian/rules build
dh_testdir
# Add here commands to configure the package.
touch configure-stamp
dh_testdir
# Add here commands to compile the package.
/usr/bin/make
make[1]: Entering directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
#docbook-to-man debian/dce-whisperer.sgml > dce-whisperer.1
touch build-stamp
 fakeroot debian/rules binary
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs
# Add here commands to install the package into debian/dce-whisperer.
/usr/bin/make DESTDIR=/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/debian/dce-whisperer install
make[1]: Entering directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
/usr/bin/make -C src
make[2]: Entering directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/src'
Computing dependencies for ShellInterface.cpp done
Computing dependencies for Whisperer.cpp done
Computing dependencies for Main.cpp done
make[2]: Leaving directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/src'
make[2]: Entering directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/src'
g++ -c -I. -I/home/bash-dce-knx/pluto/src -pipe -W -Wall -ggdb3  Main.cpp -o Main.o
g++ -c -I. -I/home/bash-dce-knx/pluto/src -pipe -W -Wall -ggdb3  Whisperer.cpp -o Whisperer.o
g++ -c -I. -I/home/bash-dce-knx/pluto/src -pipe -W -Wall -ggdb3  ShellInterface.cpp -o ShellInterface.o
g++ -I. -I/home/bash-dce-knx/pluto/src -pipe -W -Wall -ggdb3  -o DCE-whisperer Main.o Whisperer.o ShellInterface.o -L/home/bash-dce-knx/pluto/src/lib -lSerial
izeClass -lDCECommon -lPlutoUtils
make[2]: Leaving directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/src'
mkdir -p "/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/debian/dce-whisperer/usr/pluto/bin"
cp src/DCE-whisperer "/home/bash-dce-knx/bash-dce-knx/DCE-whisperer/debian/dce-whisperer/usr/pluto/bin"
make[1]: Leaving directory `/home/bash-dce-knx/bash-dce-knx/DCE-whisperer'
dh_testdir
dh_testroot
dh_installchangelogs
dh_installdocs
dh_installexamples
dh_installman
dh_link
dh_strip
dh_compress
dh_fixperms
dh_installdeb
dh_shlibdeps
dpkg-shlibdeps: warning: format of 'NEEDED libSerializeClass.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED libDCECommon.so' not recognized
dpkg-shlibdeps: warning: format of 'NEEDED libPlutoUtils.so' not recognized
dh_gencontrol
dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
dh_md5sums
dh_builddeb
dpkg-deb: building package `dce-whisperer' in `../dce-whisperer_1.0_i386.deb'.
 dpkg-genchanges -b
dpkg-genchanges: binary-only upload - not including any source code
dpkg-buildpackage: binary only upload (no source included)
dcerouter_1:/home/bash-dce-knx/bash-dce-knx/DCE-whisperer#}





and then I did not understand what this means ...

Go in Lights, add a on/off light. Set its room. Write "$00 $03" (w/o the quotes) in the "Port/Channel number" Device Data

applies to all the lights $00 and $03? where i write my group address?

You need to define some group addresses in your SIM-KNX module that map to actual group address on the bus. The "$00 $03" and "$$ $32" are adresses in a SIM-KNX that map to ports on the bus. The SIM-KNX modules come with either 128 or 256 configurable memory locations that you can read/write to. Each memory location in the SIM-KNX reflects a group address on the actual bus. Therefore you need to program the SIM-KNX using a standard KNX-EIB tool like ETS3 or write your own. See http://www.tapko.de/uploads/tx_neofileshare/SIM-KNX_Documentation.pdf for technical details of the SIM-KNX.

We are looking at creating another version of bash-dce-knx that will talk directly to the KNX-EIB bus and will be implimented with the BCUSDK ( See http://www.usinglinux.org/net/bcusdk-eibd.html ) allowing us to read/write to the bus directly using an IP-KNX gateway.

All the best

Andrew

[rages]

then I have confused the RS232 interface for programming (I use that of merten http: / / www.merten.de/download/DL_doku/P6814xx_GB.pdf) with the SIM-KNX .
I thought they were the same thing

[totallymaxed]

then I have confused the RS232 interface for programming (I use that of merten http: / / www.merten.de/download/DL_doku/P6814xx_GB.pdf) with the SIM-KNX .
I thought they were the same thing

They are totally different. The SIM-KNX is about the same or less in cost terms however and provides a simpler interface to the bus. SIM-KNX 128 units can be purchased for just over 100Euro.

When we implement bash-dce-knx that will talk directly to the KNX-EIB bus using the the BCUSDK ( See http://www.usinglinux.org/net/bcusdk-eibd.html ) allowing us to read/write to the bus directly using an IP-KNX gateway...This could also be extended to use RS232 interfaces like the Merten.

All the best

Andrew

[jbr]

When we implement bash-dce-knx that will talk directly to the KNX-EIB bus using the the BCUSDK ( See http://www.usinglinux.org/net/bcusdk-eibd.html ) allowing us to read/write to the bus directly using an IP-KNX gateway...

Hi,
I have KNX in my house and are looking at LinuxMCE with great interest. I do the programming with ETS via an IP-KNX gateway but I still don't have anything intelligent running the system (in other words a computer for timers, sceneries, web-interface etc.)

I do find 1500-2000£ to expensive for the systems from Merten, Gira etc. which just are basic computers with a small toch-screen and a user friendly software...
So, Linux MCE would of course be a nice and competent solution.

So, since my KNX-system is already  a part of my network at home, Is there a qualified guess for when there might be a solution for running the KNX-system from Linux MCE over a IP-KNX gateway?
No promises, just an educated guess... 

Rgds. Jbr

[totallymaxed]

When we implement bash-dce-knx that will talk directly to the KNX-EIB bus using the the BCUSDK ( See http://www.usinglinux.org/net/bcusdk-eibd.html ) allowing us to read/write to the bus directly using an IP-KNX gateway...

Hi,
I have KNX in my house and are looking at LinuxMCE with great interest. I do the programming with ETS via an IP-KNX gateway but I still don't have anything intelligent running the system (in other words a computer for timers, sceneries, web-interface etc.)

I do find 1500-2000£ to expensive for the systems from Merten, Gira etc. which just are basic computers with a small toch-screen and a user friendly software...
So, Linux MCE would of course be a nice and competent solution.

So, since my KNX-system is already  a part of my network at home, Is there a qualified guess for when there might be a solution for running the KNX-system from Linux MCE over a IP-KNX gateway?
No promises, just an educated guess... 

Rgds. Jbr

Well adding support for IP-KNX gateways is something we're working on but I cant say what the timescale might be for this. The current SIM-KNX compatible DCE-Whisperer code though works fine with KNX (we have installers using ETS to configure installations with it now) and offers some advantages too. SIM-KNX can be used to abstract the actual bus addresses etc and in someways means you can have a more flexible installation.

Andrew

[hari]

So, since my KNX-system is already  a part of my network at home, Is there a qualified guess for when there might be a solution for running the KNX-system from Linux MCE over a IP-KNX gateway?
No promises, just an educated guess... 

we have an EIB driver in our mantis, written in c++, it utilizes eibd, that should be able to do KNX over IP. It might be a bit of work to properly integrate it into 0810, but I can help with that..

interested?

best regards,
Hari

[jbr]

Thank you for your replies, Andrew and Hari.

Since I already have an IP-KNX gateway it would be nice to be able to hook up Linux MCE via it. (even though a SIM-KNX isn't that expensive...)

Hari, I'm definitely interested in your solution. But, as I wrote earlier, I've just started looking at Linux MCE so I do have some work/reading that has to done...

Would you care to briefly describe how this setup works and what kind of functionally that can be achieved? Is the communication and are the functions fully bi-directional?

Regards, Jbr

[hari]

it is a DCE wrapper around eibd. Regarding the author it is bi-directional, but I could not verify it as I have no KNX hardware. We need to integrate the patch(es) from that mantis ticket into the 0810 devel branch.

This is the devel thread of the eibd based driver: http://forum.linuxmce.org/index.php?topic=5648.0

It is based on the existing template, so we should be able to compile it as 1:1 replacement for the shipped driver. I'm just looking at the old mantis bug tracking to collect the needed pieces.

br, Hari