eBus adapter v3 + Ethernet = many bus errors?

[DaanOlbrechts]

Hi,

Today I installed a v3 eBus adapter - connected to eBus + Ethernet + USB power.
Unfortunately I am encountering many bus errors which seem to slow down/disrupt the expected interpretation of the messages on the bus.
I've experimented with some of the eBus options but none seem to improve the situation so to reproduce the problem I'm using a minimal docker command using a recent image (latest, I've also tried devel or an older version without success):
docker run -it --name=ebusd -p 8888 john30/ebusd:latest --scanconfig -d enh:192.168.xx.xx:9999

This results in the following logs:

2022-04-13 21:40:21.212 [main notice] ebusd 22.2.p20220227 started with auto scan on enhanced device 192.168.xx.xx:9999
2022-04-13 21:40:22.050 [bus notice] device status: resetting
2022-04-13 21:40:22.050 [bus notice] bus started with own address 31/36
2022-04-13 21:40:22.074 [bus notice] signal acquired
2022-04-13 21:40:22.864 [bus notice] device status: reset, supports info
2022-04-13 21:40:24.077 [bus notice] new master 10, master count 2
** 2022-04-13 21:40:24.088 [bus error] device status: unexpected available enhanced following byte 1
2022-04-13 21:40:24.398 [bus notice] new master 71, master count 3
2022-04-13 21:40:24.398 [update notice] received unknown MS cmd: 1076b5110101 / 09ffffc500ff65000047
2022-04-13 21:40:24.662 [update notice] received unknown MS cmd: 1076b512030f0001 / 072c03003d020f03
2022-04-13 21:40:24.858 [bus error] device status: unexpected available enhanced following byte 1
2022-04-13 21:40:25.076 [bus error] device status: unexpected available enhanced following byte 1
2022-04-13 21:40:25.409 [update notice] received unknown MS cmd: 1076b51009000000ffffff050000 / 0101
** 2022-04-13 21:40:25.869 [bus error] device status: unexpected available enhanced byte 2
2022-04-13 21:40:26.110 [bus error] device status: unexpected available enhanced following byte 1
2022-04-13 21:40:26.420 [bus notice] new master 03, master count 4
2022-04-13 21:40:26.420 [update notice] received unknown MS cmd: 1008b5110100 / 092801ff000000008000
2022-04-13 21:40:26.627 [bus error] device status: unexpected available enhanced byte 2
2022-04-13 21:40:26.829 [update notice] received unknown MS cmd: 7108b5110107 / 05000f000001
2022-04-13 21:40:26.950 [update notice] received unknown BC cmd: 10feb5160301600c
2022-04-13 21:40:27.048 [bus notice] max. symbols per second: 101
2022-04-13 21:40:29.907 [update notice] received unknown MS cmd: 7108b507030bffff / 0100
2022-04-13 21:40:31.867 [bus error] device status: unexpected available enhanced byte 2
2022-04-13 21:40:31.901 [bus error] device status: unexpected available enhanced following byte 1
** 2022-04-13 21:40:32.326 [main error] scan config 08: ERR: CRC error
2022-04-13 21:40:34.205 [update notice] received unknown MS cmd: 1008b5110101 / 0925230080ffff0000ff
2022-04-13 21:40:34.470 [update notice] received unknown MS cmd: 1076b5110101 / 09ffffc500ff65000047
2022-04-13 21:40:34.785 [bus notice] scan 15: ;Vaillant;70000;0613;6903
2022-04-13 21:40:34.785 [update notice] store 15 ident: done
2022-04-13 21:40:34.785 [update notice] sent scan-read scan.15  QQ=31: Vaillant;70000;0613;6903
2022-04-13 21:40:34.785 [bus notice] scan 15: ;Vaillant;70000;0613;6903
2022-04-13 21:40:34.841 [bus error] device status: unexpected available enhanced following byte 1
2022-04-13 21:40:35.010 [bus notice] max. symbols per second: 102
2022-04-13 21:40:35.033 [update notice] received unknown MS cmd: 1076b512030f0001 / 072c03003d020f03
2022-04-13 21:40:35.297 [update notice] received unknown MS cmd: 1008b51009000000ffffff070000 / 0101
2022-04-13 21:40:35.561 [update notice] received unknown MS cmd: 1076b51009000000ffffff050000 / 0101
2022-04-13 21:40:35.598 [main notice] read common config file vaillant/broadcast.csv
2022-04-13 21:40:35.951 [main notice] read common config file vaillant/scan.csv
2022-04-13 21:40:36.154 [main notice] read common config file vaillant/general.csv
2022-04-13 21:40:36.365 [main notice] read scan config file vaillant/15.700.csv for ID "70000", SW0613, HW6903
2022-04-13 21:40:36.568 [main notice] found messages: 437 (0 conditional on 0 conditions, 0 poll, 8 update)
2022-04-13 21:40:39.144 [bus error] device status: unexpected available enhanced following byte 1
** 2022-04-13 21:40:39.253 [main error] scan config 76: ERR: read timeout
2022-04-13 21:40:40.007 [update notice] received unknown MS cmd: 7108b507030bffff / 0100
2022-04-13 21:40:40.061 [bus error] device status: unexpected available enhanced following byte 1
2022-04-13 21:40:42.010 [bus error] device status: unexpected available enhanced byte 2
2022-04-13 21:40:42.743 [update notice] received unknown MS cmd: 7108b5110107 / 05000f000001
2022-04-13 21:40:44.207 [bus error] device status: unexpected available enhanced following byte 1
2022-04-13 21:40:44.460 [bus error] device status: unexpected available enhanced byte 2
2022-04-13 21:40:44.713 [bus error] device status: unexpected available enhanced byte 2
2022-04-13 21:40:44.747 [bus error] device status: unexpected available enhanced following byte 1
2022-04-13 21:40:44.792 [bus error] device status: unexpected available enhanced following byte 1
2022-04-13 21:40:44.977 [bus error] device status: unexpected available enhanced byte 2
2022-04-13 21:40:45.011 [bus error] device status: unexpected available enhanced byte 2
2022-04-13 21:40:45.011 [bus error] device status: unexpected available enhanced following byte 1
2022-04-13 21:40:45.286 [bus error] device status: unexpected available enhanced byte 2
2022-04-13 21:40:47.618 [main notice] SIGINT received
2022-04-13 21:40:50.095 [bus error] device status: unexpected available enhanced byte 2
2022-04-13 21:40:50.118 [bus error] device status: unexpected available enhanced following byte 1
2022-04-13 21:40:50.792 [update notice] received unknown MS cmd: 7108b5110107 / 05000f000001
2022-04-13 21:40:51.356 [main notice] ebusd stopped

I've highlighted some of the different errors encoutered:

• unexpected available enhanced following byte 1
• unexpected available enhanced byte 2
• ERR: CRC error
• ERR: read timeout

Using ebusctl I've been able to track the status and it seems like the devices do get recognized eventually, but the errors remain. What am I doing wrong? How should I troubleshoot this?

Yet another example of the troubled communication, this sequence of scans using ebusctl: (these commands are all executed in the same 10s)

root@ebusd:~/ebusd-configuration/latest/en# ebusctl scan result
15;Vaillant;70000;0613;6903

root@ebusd:~/ebusd-configuration/latest/en# ebusctl scan 8 
ERR: CRC error

root@ebusd:~/ebusd-configuration/latest/en# ebusctl scan result
08;Vaillant;HMU01;0306;8802
15;Vaillant;70000;0613;6903

root@ebusd:~/ebusd-configuration/latest/en# ebusctl scan 8
ERR: CRC error

root@ebusd:~/ebusd-configuration/latest/en# ebusctl scan 8
ERR: CRC error

root@ebusd:~/ebusd-configuration/latest/en# ebusctl scan 8
08;Vaillant;HMU01;0306;8802;21;19;38;0010019765;1610;005721;N3

root@ebusd:~/ebusd-configuration/latest/en# ebusctl scan result
08;Vaillant;HMU01;0306;8802;21;19;38;0010019765;1610;005721;N3
15;Vaillant;70000;0613;6903

Many thanks in advance.

[DaanOlbrechts]

To rule out some external factors I've today reconnected the eBus adapter, this time using another USB cable and different power supply, other cables to connect to the actual eBus... still the same behavior!
One more thing: if I set the jumper from "enhanced" to "standard" mode and modify the device string accordingly I no longer get the 'unexpected available enhanced (...)' errors, but the overall behavior is still the same (CRC errors constantly).

[john30]

which firmware version do you use on the adapter?

[DaanOlbrechts]

As a first step I upgraded the PIC firmware to version 20220327. Everything reported in this thread so far is on that version, I hadn't tried coupling the adapter to the eBus before flashing the firmware.

[john30]

I guess this is related to network traffic then. do you have the chance of recording some packets between ebusd and the adapter (tcpdump or wireshark) while simultaneously recording the ebusd log?

[john30]

wrong topic