search

john30 / ebusd-configuration

ebusd configuration files
GNU General Public License v3.0
174 stars 273 forks source link

"device invalid" after upgrade to version 3.2 #112

Closed stefaanv closed 5 years ago

stefaanv commented 5 years ago

Hi, I had a rather successfull deployment of ebusd but decided to upgrade from 3.0 to 3.2 because I had a problem writing the Hc1OPMode parameter. However, after the upgrade ebusd is unable to communicate with the eBUS Koppler Ethernet (esera) at the IP address which is still the same like before. Below is the error message. ebusd is running on an AMD64 computer (an intel NUC) with Ubuntu 16.04 Xenial operating system. Pinging the esera device from the computer works fine.

Any ideas on this ?

$ebusd --scanconfig -f -d 192.168.0.36:5000
2018-11-03 19:43:37.972 [main notice] ebusd 3.2.v3.2 started with auto scan
2018-11-03 19:43:38.221 [bus error] unable to open 192.168.0.36:5000: ERR: generic I/O error
2018-11-03 19:43:38.222 [bus notice] bus started with own address 31/36
2018-11-03 19:43:38.222 [bus notice] device invalid
2018-11-03 19:43:43.223 [bus error] unable to open 192.168.0.36:5000: ERR: generic I/O error
2018-11-03 19:43:43.223 [bus notice] device invalid

$ ping 192.168.0.36
PING 192.168.0.36 (192.168.0.36) 56(84) bytes of data.
64 bytes from 192.168.0.36: icmp_seq=1 ttl=128 time=0.223 ms
64 bytes from 192.168.0.36: icmp_seq=2 ttl=128 time=0.449 ms
stefaanv commented 5 years ago

Sorry, wrong github site