Writing to the bus not working - ESERA USB

[mwildbolz]

Description

Suddenly my ESERA EBUS USB adapter stopped working - "Arbitration lost" was the error message. Reading messages from the bus was possible, but no writing (and of course no scanning) any more.

In the meantime I already did some investigations:

• the eBUS adapter went back to ESERA and they changed the main pcb but with no change on the behaviour with the repaired model.
• I already adjusted the potentiometer several times. My best fit is to get rid of the "Arbitration lost" messages but now I have
  [bus debug] ERR: SYN received during receive command ACK, switching to ready or other errors stating, that that what should be on the bus is not there.
• playing with latency values, acquiretimeout and receivetimeout (like others reported success with in the forum)
• checked other hardware (old raspberry pi where ebusd was working some weeks ago) - no change
• checked other ebusd versions (starting from 22.1) - no change

As I couldnt bring it to work, do you have any additional idea what I could try to get the system running again?
ESERA say's that they tested the adapter and everything was fine...

Actual behavior

Arbitration is won but there are wrong symbols received during polls and scans (see log snippets)

Expected behavior

Reading and sending to the bus working

ebusd version

22.4

ebusd arguments

--configpath=/etc/ebusd/configuration/ --pollinterval=5 --enablehex --httpport=8889 --mqttjson --mqttpass=xxx --mqttport=1883 -d /dev/ttyUSB0

Operating system

Debian 11 (Bullseye) / Ubuntu 20-21 / Raspbian 11 / Raspberry Pi OS 11 (including lite)

CPU architecture

x64

Dockerized

same as ebusd version

Hardware interface

Esera USB

Related integration

No response

Logs

2022-11-13 15:44:29.973 [bus notice] <aa
2022-11-13 15:44:30.017 [bus notice] <aa
2022-11-13 15:44:30.018 [bus notice] max. symbols per second: 110
2022-11-13 15:44:30.018 [bus info] poll cmd: 3115b52406020002001e00
2022-11-13 15:44:30.018 [bus debug] start request 31
2022-11-13 15:44:30.018 [bus debug] arbitration start with 31
2022-11-13 15:44:30.060 [bus notice] <aa
2022-11-13 15:44:30.060 [bus notice] >31
2022-11-13 15:44:30.066 [bus notice] <31
2022-11-13 15:44:30.066 [bus debug] arbitration won
2022-11-13 15:44:30.066 [bus debug] arbitration delay 129 micros
2022-11-13 15:44:30.066 [bus info] arbitration delay 129 - 227 micros
2022-11-13 15:44:30.066 [bus debug] switching from ready to send command
2022-11-13 15:44:30.067 [bus notice] >15
2022-11-13 15:44:30.073 [bus notice] <15
2022-11-13 15:44:30.073 [bus debug] send/receive symbol latency 6 ms
2022-11-13 15:44:30.073 [bus info] send/receive symbol latency 5 - 6 ms
2022-11-13 15:44:30.074 [bus notice] >b5
2022-11-13 15:44:30.079 [bus notice] <b5
2022-11-13 15:44:30.079 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:30.080 [bus notice] >24
2022-11-13 15:44:30.085 [bus notice] <24
2022-11-13 15:44:30.085 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:30.086 [bus notice] >06
2022-11-13 15:44:30.091 [bus notice] <06
2022-11-13 15:44:30.091 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:30.092 [bus notice] >02
2022-11-13 15:44:30.097 [bus notice] <02
2022-11-13 15:44:30.097 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:30.098 [bus notice] >00
2022-11-13 15:44:30.103 [bus notice] <00
2022-11-13 15:44:30.103 [bus debug] send/receive symbol latency 4 ms
2022-11-13 15:44:30.103 [bus info] send/receive symbol latency 4 - 6 ms
2022-11-13 15:44:30.103 [bus notice] >02
2022-11-13 15:44:30.108 [bus notice] <02
2022-11-13 15:44:30.108 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:30.109 [bus notice] >00
2022-11-13 15:44:30.114 [bus notice] <00
2022-11-13 15:44:30.114 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:30.115 [bus notice] >1e
2022-11-13 15:44:30.120 [bus notice] <1e
2022-11-13 15:44:30.120 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:30.121 [bus notice] >00
2022-11-13 15:44:30.126 [bus notice] <00
2022-11-13 15:44:30.126 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:30.126 [bus debug] switching from send command to send command CRC
2022-11-13 15:44:30.127 [bus notice] >cd
2022-11-13 15:44:30.132 [bus notice] <cd
2022-11-13 15:44:30.132 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:30.132 [bus debug] switching from send command CRC to receive command ACK
2022-11-13 15:44:30.146 [bus notice] <aa
2022-11-13 15:44:30.146 [bus debug] notify request: ERR: SYN received
2022-11-13 15:44:30.146 [bus error] poll 700 Hc1PumpStatus failed: ERR: read timeout
2022-11-13 15:44:30.146 [bus debug] ERR: SYN received during receive command ACK, switching to ready
2022-11-13 15:44:30.150 [bus notice] <10
2022-11-13 15:44:30.154 [bus notice] <08
2022-11-13 15:44:30.158 [bus notice] <b5
2022-11-13 15:44:30.163 [bus notice] <10
2022-11-13 15:44:30.167 [bus notice] <09
2022-11-13 15:44:30.171 [bus notice] <00
2022-11-13 15:44:30.175 [bus notice] <00
2022-11-13 15:44:30.180 [bus notice] <30
2022-11-13 15:44:30.184 [bus notice] <ff
2022-11-13 15:44:30.188 [bus notice] <ff
2022-11-13 15:44:30.192 [bus notice] <ff
2022-11-13 15:44:30.196 [bus notice] <06
2022-11-13 15:44:30.201 [bus notice] <00
2022-11-13 15:44:30.205 [bus notice] <00
2022-11-13 15:44:30.209 [bus notice] <06
2022-11-13 15:44:30.214 [bus notice] <00
2022-11-13 15:44:30.223 [bus notice] <01
2022-11-13 15:44:30.228 [bus notice] <01
2022-11-13 15:44:30.232 [bus notice] <9a
2022-11-13 15:44:30.236 [bus notice] <00
2022-11-13 15:44:30.236 [update notice] received unknown MS cmd: 1008b51009000030ffffff060000 / 0101
2022-11-13 15:44:30.240 [bus notice] <aa
2022-11-13 15:44:30.283 [bus notice] <aa
2022-11-13 15:44:30.326 [bus notice] <aa

2022-11-13 15:44:47.919 [bus notice] <aa
2022-11-13 15:44:47.962 [bus notice] <aa
2022-11-13 15:44:48.005 [bus notice] <aa
2022-11-13 15:44:48.005 [bus info] poll cmd: 3115b52406020003000f00
2022-11-13 15:44:48.005 [bus debug] start request 31
2022-11-13 15:44:48.005 [bus debug] arbitration start with 31
2022-11-13 15:44:48.048 [bus notice] <aa
2022-11-13 15:44:48.048 [bus notice] >31
2022-11-13 15:44:48.054 [bus notice] <31
2022-11-13 15:44:48.054 [bus debug] arbitration won
2022-11-13 15:44:48.054 [bus debug] arbitration delay 153 micros
2022-11-13 15:44:48.054 [bus debug] switching from ready to send command
2022-11-13 15:44:48.054 [bus notice] >15
2022-11-13 15:44:48.060 [bus notice] <15
2022-11-13 15:44:48.060 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:48.060 [bus notice] >b5
2022-11-13 15:44:48.066 [bus notice] <b5
2022-11-13 15:44:48.066 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:48.066 [bus notice] >24
2022-11-13 15:44:48.073 [bus notice] <24
2022-11-13 15:44:48.073 [bus debug] send/receive symbol latency 6 ms
2022-11-13 15:44:48.073 [bus notice] >06
2022-11-13 15:44:48.079 [bus notice] <06
2022-11-13 15:44:48.079 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:48.079 [bus notice] >02
2022-11-13 15:44:48.085 [bus notice] <02
2022-11-13 15:44:48.085 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:48.085 [bus notice] >00
2022-11-13 15:44:48.091 [bus notice] <00
2022-11-13 15:44:48.091 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:48.091 [bus notice] >03
2022-11-13 15:44:48.097 [bus notice] <03
2022-11-13 15:44:48.097 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:48.097 [bus notice] >00
2022-11-13 15:44:48.103 [bus notice] <00
2022-11-13 15:44:48.103 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:48.103 [bus notice] >0f
2022-11-13 15:44:48.109 [bus notice] <0f
2022-11-13 15:44:48.109 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:48.109 [bus notice] >00
2022-11-13 15:44:48.115 [bus notice] <00
2022-11-13 15:44:48.115 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:48.115 [bus debug] switching from send command to send command CRC
2022-11-13 15:44:48.115 [bus notice] >3a
2022-11-13 15:44:48.121 [bus notice] <3a
2022-11-13 15:44:48.121 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:48.121 [bus debug] switching from send command CRC to receive command ACK
2022-11-13 15:44:48.134 [bus notice] <aa
2022-11-13 15:44:48.134 [bus debug] notify request: ERR: SYN received
2022-11-13 15:44:48.134 [bus error] poll 700 z1RoomTemp failed: ERR: read timeout
2022-11-13 15:44:48.134 [bus debug] ERR: SYN received during receive command ACK, switching to ready
2022-11-13 15:44:48.177 [bus notice] <aa
2022-11-13 15:44:48.219 [bus notice] <aa
2022-11-13 15:44:48.262 [bus notice] <aa
2022-11-13 15:44:48.304 [bus notice] <aa

2022-11-13 15:44:35.958 [bus notice] <aa
2022-11-13 15:44:36.001 [bus notice] <aa
2022-11-13 15:44:36.044 [bus notice] <aa
2022-11-13 15:44:36.044 [bus info] poll cmd: 3115b52406020002010700
2022-11-13 15:44:36.044 [bus debug] start request 31
2022-11-13 15:44:36.044 [bus debug] arbitration start with 31
2022-11-13 15:44:36.086 [bus notice] <aa
2022-11-13 15:44:36.086 [bus notice] >31
2022-11-13 15:44:36.091 [bus notice] <31
2022-11-13 15:44:36.091 [bus debug] arbitration won
2022-11-13 15:44:36.091 [bus debug] arbitration delay 214 micros
2022-11-13 15:44:36.091 [bus debug] switching from ready to send command
2022-11-13 15:44:36.092 [bus notice] >15
2022-11-13 15:44:36.097 [bus notice] <15
2022-11-13 15:44:36.097 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:36.098 [bus notice] >b5
2022-11-13 15:44:36.103 [bus notice] <b5
2022-11-13 15:44:36.103 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:36.104 [bus notice] >24
2022-11-13 15:44:36.109 [bus notice] <24
2022-11-13 15:44:36.109 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:36.110 [bus notice] >06
2022-11-13 15:44:36.115 [bus notice] <06
2022-11-13 15:44:36.115 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:36.116 [bus notice] >02
2022-11-13 15:44:36.121 [bus notice] <02
2022-11-13 15:44:36.121 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:36.122 [bus notice] >00
2022-11-13 15:44:36.127 [bus notice] <00
2022-11-13 15:44:36.127 [bus debug] send/receive symbol latency 5 ms
2022-11-13 15:44:36.128 [bus notice] >02
2022-11-13 15:44:36.131 [bus notice] <25
2022-11-13 15:44:36.131 [bus debug] notify request: ERR: wrong symbol received
2022-11-13 15:44:36.131 [bus error] poll 700 Hc2ActualFlowTempDesired failed: ERR: wrong symbol received
2022-11-13 15:44:36.131 [bus debug] ERR: wrong symbol received during send command, switching to skip
2022-11-13 15:44:36.135 [bus notice] <fc
2022-11-13 15:44:36.172 [bus notice] <aa
2022-11-13 15:44:36.215 [bus notice] <aa
2022-11-13 15:44:36.258 [bus notice] <aa
2022-11-13 15:44:36.301 [bus notice] <aa
2022-11-13 15:44:36.344 [bus notice] <aa```

[john30]

there is no solution for things like sending >02 but receiving <25. This can't be fixed in software.

the other issue with SYN received is a debug level message and is the expected behaviour when a sent message is not answered by the receiver (timeout).

[mwildbolz]

What else could i check? Under the assumption, that the ebus coupler from ESERA is ok, like they say.

Maybe cable length are an influencing factor?
I didn't change anything, but maybe the cables get older?

Just looking for additional ideas. :-(

[polprog]

My ESERA adapter was (and still is) faulty, it does not pull the bus voltage down enough to send valid symbols. Perhaps yours is similar. An oscilloscope trace of the bus is the best way to check this problem

[mwildbolz]

Getting my oscilloscope was the next thing I wanted to try.
Did you manage to get rid of this problem? If yes, how??

[polprog]

I did not yet. My adpater was serviced by Esera but that did not change anything. I will have to do a few more measurements to see if my boiler's mainboard isnt faulty, and perhaps take the adapter apart to investigate. Please see my issue thread here: #635 (comment)
the few last images are my scope traces.

[mwildbolz]

I got the same oscilloscop traces.
Changed today to a new adapter from ebusd.eu - works like a charm.

I also informed ESERA about their malfunctional devices, but they say, that they have thousands of them in the field with no problems?!? So, definitely a hardware problem of the ESERA adapter output stage!

[polprog]

Can you tell more about how you got the adapter from ebusd.eu? I got the impression the are not immediately available, and only made when enough orders come in

[mwildbolz]

I ordered the adapter a while ago via the homepage. I would also suggest to do it this way :-)
Main problem - as far as I know - is, that there are not enough electronic parts available to produce the adapters... But there are other discussions handling this topic - search the wiki/issues...