[bus error] device status: host comm error: framing
Closed this issue · 1 comments
Description
I'm using docker image john30/ebusd:v23.3 with default options except the following variables:
EBUSD_DEVICE: "enh:192.168.8.148:5001"
EBUSD_LOG: "all:info"
EBUSD_LATENCY: 75
On running I get the errors bus error] device status: host comm error: framing in enhanced TCP mode and
[bus error] send to fe: ERR: wrong symbol received, retry in non-enhanced mode (see logs I added)
How can I debug this, please? I have no idea where this error might originate from.
I have an Esera ECO 305 ETH ebusd gateway connected via LAN cable to my router. I can reach the integrated web server of that eBUS gateway without problems.
That gateway is connected to the eBUS of a Vaillant multiMATIC VRC 700
I also tried versions v23.1, v23.2 and devel, but the behavior was the same.
Do you maybe have an idea what to investigate next?
Actual behavior
On enhanced mode I receive bus error] device status: host comm error: framing errors.
On non-enhanced mode I receive [bus error] send to fe: ERR: wrong symbol received, retry errors.
Expected behavior
ebusd should be able to read the signal from the gateway just fine.
ebusd version
23.3
ebusd arguments
EBUSD_DEVICE=enh:192.168.8.148:5001 EBUSD_LOG=all:info EBUSD_LATENCY=75
Operating system
other
CPU architecture
x64
Dockerized
same as ebusd version
Hardware interface
other
Related integration
TCP (cmdline client like ebusctl or netcat)
Logs
Enhanced TCP:
2024-02-05 18:43:02.028 [main info] configPath URL is valid
2024-02-05 18:43:02.054 [bus notice] device status: transport opened
2024-02-05 18:43:02.054 [main info] registering data handlers
2024-02-05 18:43:02.054 [main info] registered data handlers
2024-02-05 18:43:02.055 [main notice] ebusd 23.3.23.3 started with broadcast scan on device: 192.168.8.148:5001, TCP, enhanced
2024-02-05 18:43:02.055 [main info] loading configuration files from https://cfg.ebusd.eu/
2024-02-05 18:43:02.177 [main info] reading templates /
2024-02-05 18:43:02.319 [main info] read templates in /
2024-02-05 18:43:02.319 [main info] reading file broadcast.csv
2024-02-05 18:43:02.462 [main info] successfully read file broadcast.csv
2024-02-05 18:43:02.462 [main info] reading file memory.csv
2024-02-05 18:43:02.605 [main info] successfully read file memory.csv
2024-02-05 18:43:02.605 [main info] read config files, got 11 messages
2024-02-05 18:43:02.606 [bus notice] bus started with own address 31/36
2024-02-05 18:43:02.606 [bus notice] signal acquired
2024-02-05 18:43:11.752 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.052 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.095 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.294 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.334 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.353 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.359 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.375 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.573 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.606 [main notice] starting initial broadcast scan
2024-02-05 18:43:12.606 [bus info] send message: 31fe07fe00
2024-02-05 18:43:12.615 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.622 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.781 [bus info] arbitration delay 6 - 6 micros
2024-02-05 18:43:12.811 [bus info] send/receive symbol latency 29 - 29 ms
2024-02-05 18:43:12.901 [bus info] send/receive symbol latency 29 - 30 ms
2024-02-05 18:43:12.931 [update info] sent BC cmd: 31fe07fe00
2024-02-05 18:43:12.931 [update notice] sent write broadcast queryexistence QQ=31:
2024-02-05 18:43:12.994 [bus error] device status: host comm error: framing
2024-02-05 18:43:12.999 [bus error] device status: host comm error: framing
The logs then continue with just more of the [bus error] device status: host comm error: framing lines.
These are the logs with the "not-enhanced" mode:
2024-02-05 19:11:23.420 [main info] configPath URL is valid
2024-02-05 19:11:23.447 [bus notice] device status: transport opened
2024-02-05 19:11:23.447 [main info] registering data handlers
2024-02-05 19:11:23.447 [main info] registered data handlers
2024-02-05 19:11:23.447 [main notice] ebusd 23.3.23.3 started with broadcast scan on device: 192.168.8.148:5001, TCP
2024-02-05 19:11:23.447 [main info] loading configuration files from https://cfg.ebusd.eu/
2024-02-05 19:11:23.613 [main info] reading templates /
2024-02-05 19:11:23.741 [main info] read templates in /
2024-02-05 19:11:23.741 [main info] reading file broadcast.csv
2024-02-05 19:11:23.888 [main info] successfully read file broadcast.csv
2024-02-05 19:11:23.888 [main info] reading file memory.csv
2024-02-05 19:11:24.035 [main info] successfully read file memory.csv
2024-02-05 19:11:24.035 [main info] read config files, got 11 messages
2024-02-05 19:11:24.037 [bus notice] bus started with own address 31/36
2024-02-05 19:11:24.037 [bus notice] signal acquired
2024-02-05 19:11:34.038 [main notice] starting initial broadcast scan
2024-02-05 19:11:34.038 [bus info] send message: 31fe07fe00
2024-02-05 19:11:34.149 [bus info] arbitration delay 6 - 6 micros
2024-02-05 19:11:34.195 [bus error] send to fe: ERR: wrong symbol received, retry
2024-02-05 19:11:34.308 [bus info] arbitration delay 5 - 6 micros
2024-02-05 19:11:34.357 [bus error] send to fe: ERR: wrong symbol received, retry
2024-02-05 19:11:34.520 [bus error] send to fe: ERR: wrong symbol received
2024-02-05 19:11:34.520 [main error] initial scan failed: ERR: wrong symbol received
2024-02-05 19:11:44.520 [main notice] starting initial broadcast scan
2024-02-05 19:11:44.520 [bus info] send message: 31fe07fe00
2024-02-05 19:11:44.772 [bus error] send to fe: ERR: wrong symbol received, retry
2024-02-05 19:11:44.885 [bus info] arbitration delay 2 - 6 micros
2024-02-05 19:11:44.931 [bus error] send to fe: ERR: wrong symbol received, retry
2024-02-05 19:11:45.090 [bus info] arbitration delay 2 - 9 micros
2024-02-05 19:11:45.136 [bus error] send to fe: ERR: wrong symbol received
2024-02-05 19:11:45.136 [main error] initial scan failed: ERR: wrong symbol received
@john30 I was able to fix this problem by improving the power supply. Before, the power plug of the ebusd gateway was put into a multi-plug. When I changed it to a single plug which is also on the same circuit as the heating system the ebusd connection started working as expected. Those errors only appear rarely now and don't seem to have a bad impact.
There was a similar issue (#435) with another device, so those kind of errors seem to be often caused by the power supply.
Do you want me to collect some metrics or more logs for you? I guess I could reproduce the failing setup. Just tell me, if I should test anything. If not, then this issue can be closed. Thanks anyway for this great tool! 🙂