scan config 08: ERR: ACK error

[michapr]

Hi,

I get in log this error for a while (some hours, then file will be taken..) [main error] scan config 08: ERR: ACK error What does this mean - and what can I do?

This is what I get after some time then:

address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=BAI00;SW=0518;HW=7401", loaded "vaillant/bai.308523.inc" ([HW=7401]), "vaillant/08.bai.csv"
address 10: master #2
address 15: slave #2, scanned "MF=Vaillant;ID=47000;SW=0126;HW=6002", loaded "vaillant/15.470.csv"
address 31: master #8, ebusd
address 36: slave #8, ebusd

Thanks!

[john30]

what adapter do you use? the message means that the device does not answer the ID request with the expected value in the ACK state

[michapr]

I use the esera eBus ethernet adapter, direct connected to Raspberry And I had no problems with older ebusd version and have no problems with current version for all other parameters from the vaillant/15470.csv (Older working version ebusd 3.0.595c7c0 without scanning address 08)

This error is coming only using the bai include or using address 08.

EDIT: Not right,... similar error is coming also when starting old version, but it seems only once:

2021-10-26 20:53:25.481 [main notice] ebusd 3.0.595c7c0 started
2021-10-26 20:53:25.489 [bus notice] bus started with own address 31/36
2021-10-26 20:53:25.490 [bus notice] signal acquired
2021-10-26 20:53:27.681 [bus notice] new master 10, master count 2
2021-10-26 20:53:27.716 [bus notice] new master 03, master count 3
2021-10-26 20:53:27.716 [update notice] unknown MS cmd: 1008b5100900005864ffff00ff00 / 0101
2021-10-26 20:53:33.988 [update notice] unknown MS cmd: 1008b5110101 / 09544a000bff640100ff
2021-10-26 20:53:35.489 [main notice] starting initial broadcast scan
2021-10-26 20:53:44.532 [update notice] unknown MS cmd: 1008b5040100 / 0a0346532026100221000b
2021-10-26 20:53:45.702 [main error] scan config 08: ERR: ACK error
2021-10-26 20:53:47.831 [bus notice] scan 15: ;Vaillant;47000;0126;6002
2021-10-26 20:53:47.847 [main notice] read common config file /etc/ebusd/vaillant/broadcast.csv
2021-10-26 20:53:47.848 [main notice] read common config file /etc/ebusd/vaillant/scan.csv
2021-10-26 20:53:47.903 [main notice] read scan config file /etc/ebusd/vaillant/15.470.csv for ID "47000", SW0126, HW6002
2021-10-26 20:53:47.912 [main notice] found messages: 267 (0 conditional on 0 conditions, 0 poll, 11 update)
2021-10-26 20:53:48.698 [bus notice] scan 15: ;21;11;26;0020108127;0082;012157;N5
2021-10-26 20:53:49.002 [bus notice] max. symbols per second: 105
2021-10-26 20:53:52.954 [update notice] unknown MS cmd: 1008b5110101 / 09544c000bff640100ff

=> 2021-10-26 20:53:45.702 [main error] scan config 08: ERR: ACK error

[michapr]

After some hours read is ok,...

2021-10-28 13:24:22.002 [main notice] read scan config file vaillant/08.bai.csv for ID "bai00", SW0518, HW7401
2021-10-28 13:24:22.447 [bus error] send to 08: ERR: ACK error, retry
2021-10-28 13:24:23.081 [bus error] send to 08: ERR: ACK error, retry
2021-10-28 13:24:23.721 [bus error] send to 08: ERR: ACK error
2021-10-28 13:24:23.721 [bus error] send message part 0: ERR: ACK error

But anyway I get the ACK errors reading any value (only for the bai part - all other values will be received without problem).

Only once every 2-4 hours I get a value. In log I can see then: 2021-10-28 15:12:17.072 [update notice] sent read bai WaterPressure QQ=31: 1.638;ok

[john30]

looks like a potentiometer adjustment issue to me. provide some raw bytes logging, so we can check thath

[michapr]

ok, will do. Bu why I have these problems only with bai parameters? Is there something special?

[michapr]

(please take file below)

Here is the starting sequence and some working requests of other parameters inside. Additional the ACK error while "scan config 08"

If you need something else for checking please tell me.

Thanks!

[michapr]

ebusd.log.gz

Replaced file - here is better content... as sample this:

2021-10-29 19:51:20.902 [update notice] sent poll-read 470 YieldThisYear QQ=31: 0;0;0;0;0;0;0;0;0;0;0;0
2021-10-29 19:51:20.902 [bus notice] >3115b509030d3d584e<000200002c>00
2021-10-29 19:51:21.494 [bus notice] >31<0305ed12020300c6
2021-10-29 19:51:21.581 [main error] scan config 08: ERR: ACK error
2021-10-29 19:51:22.134 [bus notice] >3108070400d1<0ab54241493030051874012f
2021-10-29 19:51:22.245 [update notice] sent read 470 Hc1PumpLast24started QQ=31: yes
2021-10-29 19:51:22.246 [bus notice] >3115b509030d8400c9<0001019a>00

[michapr]

Here is a longer log, including the successful load of file vaillant/08.bai.csv, following errors while reading but also readings without error. ebusd-2.log.gz

thanks for checking!

[john30]

I meant using --lograwdata=bytes, but anyway the communication does not work very well according to the logs as there are many lines that look as if the controller (470) intervenes the data sent on the bus. this again suggests that the poti is not adjusted very good

[michapr]

ebus2.log.gz

attached the new log.

What I do not understand is the fact, that I receive all other values without problems or missing timeframes. Only after the bai include was added I can see the problems - why the "not adjusted poti" is only here a problem?

How can I see in log that it is optimal?

Thanks!

[john30]

the bai does not answer correctly. after sending the ID request the ACK symbol is missing (0x00). I'd try to adjust the poti a bit in one or the other direction and check if that helps. Might be a serial buffering issue as well with the USB to serial converter.

[michapr]

Might be a serial buffering issue as well... I really don't think so, because looks like it is related only to bai parameters.

Could it be possible that it is a timing problem in software, that software does not wait enough for an answer?

Anyway I will try again to move poti a bit into other direction, into first (I made today) didn't change anything.

[john30]

no, as some bytes on the wire are completely mssing from UART perspective

[michapr]

I have changed in both directions, no difference. Why this problem exist only for bai parameters?

[john30]

probably the recognition of the low level does not work good enough

[michapr]

I don't think so - because:

Why this problem exist only for bai parameters?

I have no problems with all other values - and no more errors in logs - only bai related...

[john30]

the bai is on another end of the cabling, isn't it? and that changes a lot. plus it is a different unit which might just have a little different requirements on the signal. fyi: i had the same issue with one of my circuits before I switched to another adapter

[michapr]

the bai is on another end of the cabling, isn't it?

No, not in my case, I have one output on Vaillant unit for the eBus interface. Same is going to the controller box at wall...

[john30]

do you this still with the current ebusd version?

[michapr]

Have no chance to test it now, will do it and tell you. Thanks for the reminder to try the update ;)

[michapr]

yes,... still the same. Have compiled latest version and tested - no difference.

2022-10-28 16:51:26.133 [update notice] sent read 470 DisplayedHc1RoomTempDesired QQ=31: 17.5
2022-10-28 16:51:26.363 [update notice] sent read 470 DisplayedHwcStorageTemp QQ=31: 47.0
2022-10-28 16:51:26.634 [update notice] sent read 470 DisplayedRoomTemp QQ=31: 20.81
2022-10-28 16:51:26.904 [update notice] sent read 470 Hc1ActualFlowTempDesired QQ=31: 0.0
2022-10-28 16:51:27.169 [update notice] sent read 470 Hc1DayTemp QQ=31: 22.5
2022-10-28 16:51:27.393 [update notice] sent read 470 Hc1HeatCurve QQ=31: 1.30
2022-10-28 16:51:27.612 [update notice] sent read 470 Hc1MinimalFlowTempDesired QQ=31: 15.0
2022-10-28 16:51:27.788 [update notice] sent read 470 Hc1NightTemp QQ=31: 17.5
2022-10-28 16:51:28.005 [update notice] sent read 470 Hc1Pump QQ=31: off
2022-10-28 16:51:28.229 [update notice] sent read 470 Hc1QuickVetoTemp QQ=31: 17.5
2022-10-28 16:51:28.463 [update notice] sent read 470 OutsideTemp QQ=31: 19.25;ok
2022-10-28 16:51:28.736 [update notice] sent read 470 RoomTemp QQ=31: 22.62;ok
2022-10-28 16:51:29.066 [update notice] sent read 470 HwcTempDesired QQ=31: 48.0
2022-10-28 16:51:29.283 [update notice] sent read 470 HwcActualTempDesired QQ=31: 48.0
2022-10-28 16:51:29.507 [update notice] sent read 470 Hc1SFMode QQ=31: quickveto
2022-10-28 16:51:34.189 [update notice] sent poll-read 470 YieldThisYear QQ=31: 0;0;0;0;0;0;0;0;0;0;0;0
2022-10-28 16:51:34.367 [update notice] sent poll-read 470 YieldThisYear QQ=31: 0;0;0;0;0;0;0;0;0;0;0;0
2022-10-28 16:51:34.547 [update notice] sent poll-read 470 YieldThisYear QQ=31: 0;0;0;0;0;0;0;0;0;0;0;0
2022-10-28 16:51:34.695 [main error] scan config 08: ERR: ACK error
2022-10-28 16:51:35.944 [update notice] sent poll-read 470 YieldThisYear QQ=31: 0;0;0;0;0;0;0;0;0;0;0;0

[john30]

this is to almost 100% related to bytes from the bus being misinterpreted due to non-matching poti adjustment

[michapr]

I have already tried to modify it (poti adjustment), but no changes, the readings for "470" get worse only in this case.

I have the problems only with the "bai" value - and I get it sometimes (about every hour). But maybe this is interface (esera eth) or heating device related... So you can close this issue, it is not a real top issue for me more.

Thanks for your time and your great tool!