Thread: [Bcusdk-list] BCU SDK 0.0.4 RC1
Brought to you by:
e9925248
Menu
▾
▴
bcusdk-list
|
From: <mko...@au...> - 2008-12-18 11:02:25
|
I have just put the release candidate for bcusdk 0.0.4 online: http://www.auto.tuwien.ac.at/~mkoegler/eib/new You find the update documentation, sources and precompiled version for Debian/Ubuntu, OpenSuse and Fedora. | The biggest change is the remove of exceptions. This should result in | a better stability on cygwin. On embedded system, you can now compile | eibd without any C++ library (--without-libstdc++) with gcc. | | The C# client library is now offical part of the sources. | | A few new example programs were added (groupsocketswrite, | groupsocketwrite, knxtool). | | The EIBnet/IP Tunneling client has some NAT support [although its from | the security point of view better to use a VPN tunnel instead]. | | The rest of the changes are mostly bug fixes. Please give it a try on your systems. If no big problems are found, I intend to release these files as bcusdk 0.0.4. mfg Martin Kögler |
|
From: Jens H. <je...@he...> - 2008-12-21 20:38:51
|
Martin, eibd compiles well and runs as well as the 0.0.3 version. I have it running on a Buffalo Linkstation with Andrés 2.6.25.20 Kernel. (http://hvkls.dyndns.org/) I do all the ./configure & make on the linkstation. Especially ./configure ... ran well. (I tried to use previous files from the git - but creation of configure failed with autoconf / automake). But this was probably my lack of experience. But I have another issue, which I thought could have been fixed with this version. I'm not sure, whether this is a bug or impossible by design: The -e EIBADDR does not work for my USB-interface. My EIB-Access works over USB to a Buschjäger USB interface to a Powernet BCU. (BJE 6123 + 6920U-102). I just use the USB-backend in the eibd. ./configure --prefix=/mnt/opt/bcusdk --enable-onlyeibd --enable-usb --enable-eibnetipserver --enable-java=no The eibd in my case always uses the "0.0.0" source Address. (not even the 0.0.1) - even if I enter the '-e "x.y.z' command-line option. The "0.0.0" seems to cause a problem with my Media-coupler between EIB Powernet and EIB Twisted pair, which I use in my home-installation. The coupler expects a device in a certain Address line to forward these addresses to twisted pair... In generally it works for the normal groupadresses - but not for programming. If I use the falconlib, in which the source address can also be specified together with the Powernet ID (1 byte) - it works well. I ran a test to connect the ETS to the EIBD. Connection works well. I can reach the powernet devices but connection to devices behind the media-coupler causes problems. In the ETS connection settings (Falcon) one can also set the "physical source" Address. If I do this and change this from the preset 0.0.0 to any other value, I receive an "memory write-error" from the falcon/ETS. If I connect the USB-Interface directly to the ETS, it works. ... Can you help? Is there some option, how I can change this? (by the way, the USB-Powernet-BCU was beforehand programmed with BJ-Powerproject and has a correct Powernet Line Address + the Net-ID) But EIBD always works with the 0.0.0 address..) Thanks in advance, best Regards, Jens -----Original Message----- From: Martin Koegler [mailto:mko...@au...] Sent: Donnerstag, 18. Dezember 2008 12:02 To: bcu...@li... Subject: [Bcusdk-list] BCU SDK 0.0.4 RC1 I have just put the release candidate for bcusdk 0.0.4 online: http://www.auto.tuwien.ac.at/~mkoegler/eib/new You find the update documentation, sources and precompiled version for Debian/Ubuntu, OpenSuse and Fedora. | The biggest change is the remove of exceptions. This should result in | a better stability on cygwin. On embedded system, you can now compile | eibd without any C++ library (--without-libstdc++) with gcc. | | The C# client library is now offical part of the sources. | | A few new example programs were added (groupsocketswrite, | groupsocketwrite, knxtool). | | The EIBnet/IP Tunneling client has some NAT support [although its from | the security point of view better to use a VPN tunnel instead]. | | The rest of the changes are mostly bug fixes. Please give it a try on your systems. If no big problems are found, I intend to release these files as bcusdk 0.0.4. mfg Martin Kögler ---------------------------------------------------------------------------- -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Bcusdk-list mailing list Bcu...@li... https://lists.sourceforge.net/lists/listinfo/bcusdk-list |
|
From: <mko...@au...> - 2008-12-21 21:13:19
|
On Sun, Dec 21, 2008 at 09:14:08PM +0100, Jens Hetmanek wrote: > Martin, eibd compiles well and runs as well as the 0.0.3 version. > > I have it running on a Buffalo Linkstation with Andrés 2.6.25.20 Kernel. > (http://hvkls.dyndns.org/) I do all the ./configure & make on the > linkstation. Especially ./configure ... ran well. (I tried to use previous > files from the git - but creation of configure failed with autoconf / > automake). But this was probably my lack of experience. > > But I have another issue, which I thought could have been fixed with this > version. > > I'm not sure, whether this is a bug or impossible by design: > The -e EIBADDR does not work for my USB-interface. -e is only for devices, which don't have their own address (eg. TPUART, EIBnet/IP routing). Its ignored for the USB backend. > My EIB-Access works over USB to a Buschjäger USB interface to a Powernet > BCU. (BJE 6123 + 6920U-102). > I just use the USB-backend in the eibd. > ./configure --prefix=/mnt/opt/bcusdk --enable-onlyeibd --enable-usb > --enable-eibnetipserver --enable-java=no > > The eibd in my case always uses the "0.0.0" source Address. (not even the > 0.0.1) - even if I enter the '-e "x.y.z' command-line option. > The "0.0.0" seems to cause a problem with my Media-coupler between EIB > Powernet and EIB Twisted pair, which I use in my home-installation. > > The coupler expects a device in a certain Address line to forward these > addresses to twisted pair... > In generally it works for the normal groupadresses - but not for > programming. > > If I use the falconlib, in which the source address can also be specified > together with the Powernet ID (1 byte) - it works well. > > I ran a test to connect the ETS to the EIBD. Connection works well. I can > reach the powernet devices but connection to devices behind the > media-coupler causes problems. In the ETS connection settings (Falcon) one > can also set the "physical source" Address. If I do this and change this > from the preset 0.0.0 to any other value, I receive an "memory write-error" > from the falcon/ETS. If I connect the USB-Interface directly to the ETS, it > works. > ... > Can you help? Is there some option, how I can change this? > > (by the way, the USB-Powernet-BCU was beforehand programmed with > BJ-Powerproject and has a correct Powernet Line Address + the Net-ID) But > EIBD always works with the 0.0.0 address..) The USB backend of EIBD uses the settings programmed into the interface. Therefore I suggest to program the USB interface with the intended configuration via ETS: * Add the USB interface to an ETS project * Adjusts all settings * Download it mfg Martin Kögler |
Thanks for helping keep SourceForge clean.
X