ERR: arbitration lost + scan failed

[jstoki]

Hi
I have the following configuration:
temperature sensor VRC 693
boiler VC PL 246/5-5
VRC 700/4 and VR 91 controllers
VR71 module
Adapter Shield C6 (Version 2025-02-16) connected with GPIO Raspberry Pi3 B+ (bookworm 64)

/etc/default/ebusd
EBUSD_OPTS="--scanconfig --device=ens:/dev/ttyAMA0 --latency=30"

/boot/firmware/config.txt

[all]
enable_uart=1
dtoverlay=miniuart-bt

Unfortunately, after connecting, the system does not download configuration files and there are a lot of errors in the log.
What could be the reason ?
A few years ago, I used an older version of the adapter but gave up because it sometimes interfered with the outdoor temperature sensor, which would no longer be visible in the EBUS network and the boiler would strongly heat the apartment.

ebusctl i

version: ebusd 24.1.24.1
update check: OK
device: /dev/ttyAMA0, serial high speed, enhanced
signal: acquired
symbol rate: 23
max symbol rate: 118
reconnects: 0
masters: 4
messages: 18
conditional: 0
poll: 0
update: 10
address 03: master #11
address 08: slave #11
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=70000;SW=0419;HW=4603"
address 26: slave
address 30: master #3
address 31: master #8, ebusd
address 36: slave #8, ebusd

/var/log/ebusd.log

2025-03-16 09:10:49.376 [update notice] received unknown MS cmd: 1026b5230f05ffff00001400ffffffff00008900 / 0101
2025-03-16 09:10:49.625 [update notice] received unknown MS cmd: 1026b5230402000135 / 020105
2025-03-16 09:10:49.874 [update notice] received unknown MS cmd: 1026b5230402010137 / 020119
2025-03-16 09:10:56.171 [update notice] received unknown MS cmd: 1008b5110101 / 0936351002ffff0000ff
2025-03-16 09:10:56.472 [update notice] received unknown MS cmd: 1026b5230106 / 109d019801840100809f021d01c0014000
2025-03-16 09:10:56.769 [update notice] received unknown MS cmd: 1026b5230107 / 0f008000800080008003c80000805504
2025-03-16 09:10:57.041 [update notice] received unknown MS cmd: 1008b5100900003affffff000000 / 0101
2025-03-16 09:10:58.473 [main notice] starting initial broadcast scan
2025-03-16 09:10:59.024 [bus error] send to fe: ERR: arbitration lost, retry
2025-03-16 09:10:59.443 [update notice] received unknown MS cmd: 1026b5230f05ffff00001400ffffffff00008900 / 0101
2025-03-16 09:10:59.693 [update notice] received unknown MS cmd: 1026b5230402000135 / 020105
2025-03-16 09:10:59.697 [bus error] send to fe: ERR: arbitration lost, retry
2025-03-16 09:10:59.942 [update notice] received unknown MS cmd: 1026b5230402010137 / 020119
2025-03-16 09:11:00.297 [bus error] send to fe: ERR: arbitration lost
2025-03-16 09:11:00.297 [main error] initial scan failed: ERR: arbitration lost
2025-03-16 09:11:06.237 [update notice] received unknown MS cmd: 1008b5110101 / 0936351002ffff0000ff
2025-03-16 09:11:06.538 [update notice] received unknown MS cmd: 1026b5230106 / 109c019801840100809f021e01c0014000
2025-03-16 09:11:06.835 [update notice] received unknown MS cmd: 1026b5230107 / 0f008000800080008003c80000805504
2025-03-16 09:11:07.108 [update notice] received unknown MS cmd: 1008b5100900003bffffff000000 / 0101
2025-03-16 09:11:09.554 [update notice] received unknown MS cmd: 1026b5230f05ffff00001400ffffffff00008700 / 0101
2025-03-16 09:11:09.803 [update notice] received unknown MS cmd: 1026b5230402000135 / 020105
2025-03-16 09:11:10.053 [update notice] received unknown MS cmd: 1026b5230402010137 / 020119
2025-03-16 09:11:10.298 [main notice] starting initial broadcast scan
2025-03-16 09:11:10.849 [bus error] send to fe: ERR: arbitration lost, retry
2025-03-16 09:11:11.421 [bus error] send to fe: ERR: arbitration lost, retry
2025-03-16 09:11:11.993 [bus error] send to fe: ERR: arbitration lost
2025-03-16 09:11:11.993 [main error] initial scan failed: ERR: arbitration lost

[jstoki]

Hi
I changed the configuration to the following to save the logs, which I attach.
EBUSD_OPTS="--scanconfig --device=ens:/dev/ttyAMA0 --latency=50 --receivetimeout=10000 --acquireretries=10 --acquiretimeout=20000 --loglevel=debug --logfile=/var/log/ebusd.log --lograwdata --lograwdatafile=/var/log/ebusdraw.log --dump --dumpfile=/var/log/ebusdump.log"
ebusd.log
ebusdraw.log
ebusdump.log

[maleadt]

I have the same issue on the 2025-02-16 firmware, combined with a Raspberry Pi 5 and the C6 shield:

$ podman run --rm --device=/dev/ttyAMA0 --group-add keep-groups -p 8888:8888 john30/ebusd --device=ens:/dev/ttyAMA0 --log=all:notice --latency=50
2025-03-22 15:29:21.098 [device notice] transport opened
2025-03-22 15:29:21.100 [main notice] ebusd 24.1.24.1 started with broadcast scan on device: /dev/ttyAMA0, serial high speed, enhanced
2025-03-22 15:29:21.326 [bus notice] bus started with own address 31/36
2025-03-22 15:29:21.326 [bus notice] signal acquired
2025-03-22 15:29:21.328 [mqtt notice] connection established
2025-03-22 15:29:25.587 [bus notice] new master 10, master count 2
2025-03-22 15:29:25.656 [bus notice] new master 03, master count 3
2025-03-22 15:29:25.656 [update notice] received unknown MS cmd: 1008b5110101 / 093435401431360000ff
2025-03-22 15:29:25.951 [update notice] received unknown MS cmd: 1052b5230103 / 0f008000800080008047014a01c87d00
2025-03-22 15:29:26.223 [update notice] received unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2025-03-22 15:29:26.482 [update notice] received unknown MS cmd: 1052b523080100ff0000ffff00 / 0101
2025-03-22 15:29:26.730 [update notice] received unknown MS cmd: 1052b5230402010000 / 02019c
2025-03-22 15:29:31.327 [main notice] starting initial broadcast scan
2025-03-22 15:29:31.879 [bus error] send to fe: ERR: arbitration lost, retry
2025-03-22 15:29:32.446 [bus error] send to fe: ERR: arbitration lost, retry
2025-03-22 15:29:33.013 [bus error] send to fe: ERR: arbitration lost
2025-03-22 15:29:33.013 [main error] initial scan failed: ERR: arbitration lost
2025-03-22 15:29:35.729 [update notice] received unknown MS cmd: 1008b5110101 / 093435401431360000ff
2025-03-22 15:29:36.024 [update notice] received unknown MS cmd: 1052b5230103 / 0f008000800080008047014a01c87d00
2025-03-22 15:29:36.298 [update notice] received unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2025-03-22 15:29:36.559 [update notice] received unknown MS cmd: 1052b523080100ff0000ffff00 / 0101
2025-03-22 15:29:36.808 [update notice] received unknown MS cmd: 1052b5230402010000 / 02019c
2025-03-22 15:29:43.013 [main notice] starting initial broadcast scan
2025-03-22 15:29:43.576 [bus error] send to fe: ERR: arbitration lost, retry
2025-03-22 15:29:44.143 [bus error] send to fe: ERR: arbitration lost, retry
2025-03-22 15:29:44.710 [bus error] send to fe: ERR: arbitration lost
2025-03-22 15:29:44.710 [main error] initial scan failed: ERR: arbitration lost
2025-03-22 15:29:45.764 [update notice] received unknown MS cmd: 1008b5110101 / 093435401431360000ff
^C2025-03-22 15:29:45.902 [main notice] SIGINT received
2025-03-22 15:29:46.061 [update notice] received unknown MS cmd: 1052b5230103 / 0f008000800080008047014a01c87d00
2025-03-22 15:29:46.333 [update notice] received unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2025-03-22 15:29:46.425 [device error] transport closed
2025-03-22 15:29:46.426 [main notice] ebusd stopped

Downgrading to 2025-01-20 has helped:

2025-03-22 15:37:54.197 [device notice] transport opened
2025-03-22 15:37:54.198 [main notice] ebusd 24.1.24.1 started with broadcast scan on device: /dev/ttyAMA0, serial high speed, enhanced
2025-03-22 15:37:54.645 [bus notice] bus started with own address 31/36
2025-03-22 15:37:54.645 [device notice] reset, supports info
2025-03-22 15:37:54.645 [bus notice] signal acquired
2025-03-22 15:37:54.645 [bus notice] new master 10, master count 2
2025-03-22 15:37:54.646 [mqtt notice] connection established
2025-03-22 15:37:54.648 [device notice] extra info: firmware 1.1[5114].1[5114], jumpers 0x03
2025-03-22 15:37:59.675 [bus notice] new master 03, master count 3
2025-03-22 15:37:59.675 [update notice] received unknown MS cmd: 1008b5110101 / 093434701431350000ff
2025-03-22 15:37:59.970 [update notice] received unknown MS cmd: 1052b5230103 / 0f008000800080008047014b01c87d00
2025-03-22 15:38:00.241 [update notice] received unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2025-03-22 15:38:01.237 [update notice] received unknown MS cmd: 1052b523080100ff0000ffff00 / 0101
2025-03-22 15:38:01.486 [update notice] received unknown MS cmd: 1052b5230402010000 / 02019c
2025-03-22 15:38:04.646 [main notice] starting initial broadcast scan
2025-03-22 15:38:04.737 [update notice] sent write Broadcast Queryexistence QQ=31:
2025-03-22 15:38:09.816 [update notice] received unknown MS cmd: 1008b5110101 / 093434701431350000ff
2025-03-22 15:38:10.113 [update notice] received unknown MS cmd: 1052b5230103 / 0f008000800080008047014b01c87d00
2025-03-22 15:38:10.385 [update notice] received unknown MS cmd: 1008b51009000000ffffff010000 / 0101
2025-03-22 15:38:11.380 [update notice] received unknown MS cmd: 1052b523080100ff0000ffff00 / 0101
2025-03-22 15:38:11.630 [update notice] received unknown MS cmd: 1052b5230402010000 / 02019c
^C2025-03-22 15:38:12.243 [main notice] SIGINT received
2025-03-22 15:38:12.747 [device error] transport closed
2025-03-22 15:38:12.747 [main notice] ebusd stopped

[jstoki]

@maleadt
Thank you very much for the recommendation. Indeed downgrading the frimware version helped immediately

[maleadt]

@john30 Maybe this should become an issue then?