question

oxident avatar image
oxident asked

Occasional Modbus timeouts on Cerbo GX since 2.93

Hello,

after updating my Cerbo GX from 2.92 to 2.93, I get occasional timeouts while reading registers periodically. Exactly every 45min, my client (ioBroker) reports an "undefined" Modbus error, resulting in a timeout. Immediate reconnection works like a charm for another 45min.

Is anyone aware of this?

cerbo gxModbus TCP
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

1 Answer
lucode avatar image
lucode answered ·

I have the same issue but with Home Assistant. In Home Assistant it could be a bugy Python library, but in your case with IoBroker (JS) I don't know? https://github.com/home-assistant/core/issues/88800

I did have a look at the Release note of the versions 2.92 to 2.93 of Venus GX, but couldn't find any direct issues. But in 2.93 they changed something which could ev. cause the issue:

https://professional.victronenergy.com/news/detail/186/

Restore Modbus-TCP register 31, VE.Bus State. Per a recent version, that register returned "Ext. control" which broke customer implementations. Now the register will return the usual status (Bulk, Absorption, Float, etc) again, when the inverter/charger is in fact externally controlled by a smart battery.

But there where some major changes to Modbus TCP in v2.90 – September 12th 2022. Because I do have Autoupdate I'am not quite sure when mine gets a new version.

https://professional.victronenergy.com/downloads/firmware/file-download/?name=Venus%20OS%20%28CCGX%2C%20Venus%20GX%2C%20Cerbo%20GX%20and%20other%20GX%20products%29/Venus%20OS%20-%20firmware%20changelog.docx

2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.