ebus log analysis

[mf76130]

Hi,
i have a vaillant arotherm vwl 115/2.
For the ebus connection i am using a asera usb adapter (nothing else was buyable) and a raspberry pi 3 with actual bullseye image.
My main problem is that i am not getting all data i want, thats all i get:

config:
EBUSD_OPTS="--configpath=/etc/ebusd/ -d /dev/ttyUSB0 --latency=20 --loglevel=debug --lograwdata=bytes --poll=9 --scanconfig=full --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqttjson --mqtthost=192.168.0.17 --mqttport=1883 --mqttuser= --mqttpass= --mqttjson"

broadcast outsidetemp = 14.750
broadcast vdatetime = 04:49:34;01.09.2022
hmu currenterror = -;-;-;-;-
hmu DateTime = nosignal;-:-:-;-.-.-;-
hmu SetMode = auto;0.0;-;-;1;1;1;0;0;0
hmu Status01 = 17.5;16.5;-;-;-;off
hmu StatusCirPump = off
scan.08 = Vaillant;HMU01;0306;8802
scan.76 = Vaillant;VWZIO;0111;0103

ebusctl info:
version: ebusd 22.3.p20220508
device: /dev/ttyUSB0
signal: acquired
symbol rate: 154
max symbol rate: 180
min arbitration micros: 321
max arbitration micros: 572
min symbol latency: 3
max symbol latency: 9
reconnects: 0
masters: 5
messages: 72
conditional: 0
poll: 17
update: 10
address 00: master #1
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=HMU01;SW=0306;HW=8802", loaded "vaillant/08.hmu.csv"
address 10: master #2
address 15: slave #2
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanned "MF=Vaillant;ID=VWZIO;SW=0111;HW=0103"
address e8: slave

I tried to adjust the poti, but it seems it had already the best setup when i received the device.
Attached is the log file, if someone would have time to have a look and tell me what issues can be seen there, that would be very nice.
Can my adapter write?
Is the latency good?

ebusd.log

[mf76130]

pretty intersting, as i wanted to move my VR900 + the pi and ebus D adapter away from the heating, i did a new cabling with a cat 6 cable.
Not my ebus adapter gets all the data it should get, but the vr900 says i can't recognise your system

ok, only for a short time

[mf76130]

if you have problems getting correct data, don't use scanconfig

[john30]

as stated here, it should be better with the next release (or freshly built from the source)

[john30]

ebusd 22.4 is out and it continues to try scanning devices until successful, maybe that helps

[mf76130]

testing it, doesn't look that good at the moment, even no broadcasts are received, but lets wait: (without scanconfig it works straigt away)

version: ebusd 22.4.v22.4
device: /dev/ttyUSB0
signal: acquired
symbol rate: 100
max symbol rate: 164
min arbitration micros: 366
max arbitration micros: 485
min symbol latency: 5
max symbol latency: 6
reconnects: 0
masters: 5
messages: 16
conditional: 0
poll: 0
update: 4
address 00: master #1
address 03: master #11
address 08: slave #11, scanning
address 10: master #2
address 15: slave #2, scanning
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 71: master #9
address 76: slave #9, scanning
address e8: slave, scanning

2022-09-19 06:52:12.623 [bus info] scan 08 cmd: 3108070400
2022-09-19 06:52:12.632 [bus debug] start request 31
2022-09-19 06:52:12.632 [bus debug] arbitration start with 31
2022-09-19 06:52:12.681 [bus debug] arbitration won
2022-09-19 06:52:12.681 [bus debug] arbitration delay 399 micros
2022-09-19 06:52:12.681 [bus debug] switching from ready to send command
2022-09-19 06:52:12.688 [bus debug] send/receive symbol latency 6 ms
2022-09-19 06:52:12.695 [bus debug] send/receive symbol latency 6 ms
2022-09-19 06:52:12.702 [bus debug] send/receive symbol latency 6 ms
2022-09-19 06:52:12.709 [bus debug] send/receive symbol latency 6 ms
2022-09-19 06:52:12.709 [bus debug] switching from send command to send command CRC
2022-09-19 06:52:12.716 [bus debug] notify request: ERR: wrong symbol received
2022-09-19 06:52:12.716 [bus debug] ERR: wrong symbol received during send command CRC, switching to skip
2022-09-19 06:52:12.716 [main error] scan config 08: ERR: wrong symbol received
2022-09-19 06:52:14.354 [update info] received MS cmd: 1008b5110101 / 091c1a0080ffff0000ff
2022-09-19 06:52:14.354 [update notice] received unknown MS cmd: 1008b5110101 / 091c1a0080ffff0000ff
2022-09-19 06:52:14.621 [update info] received MS cmd: 1076b5110101 / 09ffff8500ff5a000031
2022-09-19 06:52:14.621 [update notice] received unknown MS cmd: 1076b5110101 / 09ffff8500ff5a000031

2022-09-19 06:52:14.717 [bus info] scan 15 cmd: 3115070400
2022-09-19 06:52:14.755 [bus debug] start request 31
2022-09-19 06:52:14.755 [bus debug] arbitration start with 31
2022-09-19 06:52:14.802 [bus debug] arbitration lost
2022-09-19 06:52:14.802 [bus debug] ERR: arbitration lost during ready, retry
2022-09-19 06:52:14.889 [update info] received MS cmd: 1076b512030f0201 / 07d602008d010903
2022-09-19 06:52:14.889 [update notice] received unknown MS cmd: 1076b512030f0201 / 07d602008d010903
2022-09-19 06:52:14.889 [bus debug] start request 31
2022-09-19 06:52:14.889 [bus debug] arbitration start with 31
2022-09-19 06:52:14.899 [bus debug] arbitration won
2022-09-19 06:52:14.899 [bus debug] arbitration delay 421 micros
2022-09-19 06:52:14.899 [bus debug] switching from ready to send command
2022-09-19 06:52:14.906 [bus debug] send/receive symbol latency 6 ms
2022-09-19 06:52:14.913 [bus debug] send/receive symbol latency 6 ms
2022-09-19 06:52:14.920 [bus debug] send/receive symbol latency 6 ms
2022-09-19 06:52:14.927 [bus debug] send/receive symbol latency 6 ms
2022-09-19 06:52:14.927 [bus debug] switching from send command to send command CRC
2022-09-19 06:52:14.935 [bus debug] notify request: ERR: wrong symbol received
2022-09-19 06:52:14.935 [bus debug] ERR: wrong symbol received during send command CRC, switching to skip
2022-09-19 06:52:14.935 [main error] scan config 15: ERR: wrong symbol received
2022-09-19 06:52:15.162 [update info] received MS cmd: 1008b51009000000ffffff070000 / 0101
2022-09-19 06:52:15.162 [update notice] received unknown MS cmd: 1008b51009000000ffffff070000 / 0101
2022-09-19 06:52:15.366 [update info] received MS cmd: 7108b507030bffff / 0100
2022-09-19 06:52:15.366 [update notice] received unknown MS cmd: 7108b507030bffff / 0100
2022-09-19 06:52:15.461 [update info] received MS cmd: 1076b51009000000ffffff010000 / 0101
2022-09-19 06:52:15.461 [update notice] received unknown MS cmd: 1076b51009000000ffffff010000 / 0101
2022-09-19 06:52:16.529 [update info] received MS cmd: 03e8b512060b0000000000 / 0b0000000001ffffffffff00
2022-09-19 06:52:16.529 [update notice] received unknown MS cmd: 03e8b512060b0000000000 / 0b0000000001ffffffffff00

[john30]

without scanconfig it works straigt away

sure, when your interface can't write or read reliably you don't have a better option actually. additionaly you'll not be able to reliably read from the bus actively, only listening to the traffic works fine in this case (onlyas long as the poti is adjusted well enough of course)

[mf76130]

its a pitty that nothing but esera bus adapter is available at the moment :-(