DBus-Fronius: DC values per MPPT (Pv/x/V, Pv/x/P) are off by a factor of 10

Hello everyone,

System: Cerbo with Venus OS v3.79, dbus-fronius 1.7.20, Symo 15.0-3-M with the firmware and Data Manager versions, setting “int + SF”, model 160 from register 40253

Symptoms:

Again and again, at regular intervals, Victron / Telegraf writes some very strange DC-side values to my InfluxDB: >6000V, etc.:

VRM also displays these errors:

The strings according to Solar.web:

Claude thinks it is some kind of dbus-fronius driver that is providing/reading incorrect values here because a factor is not being applied correctly or is only being applied after a delay.

Is this a known issue?

Best regards,

Thomas

This is why we repeatedly tell members not to rely on an AI, nor, per guideline, to use its content on the forum. It is wrong far too often.
Rather just ask the community for guidance, that is easier than trying to correct an AI via a human proxy.

There were some scaling issues on different (newer?) Fronius models, I don’t recall it applying to this model. A change was made in the 3.80 beta, you can try this or wait until it is in production, hopefully next week.

That’s why I’m posting here—and the fact that something is wrong should be obvious from the screenshots. I’ve searched and tried to find out what’s causing it, but haven’t reached any conclusions. Hence this post—and the reference to the AI, which is what it thinks after reviewing my data.

There were some scaling issues with various (newer?) Fronius models

The Symo is old, and according to Fronius nothing new will be coming for it any more. At least as far as new features are concerned; that’s what I was told in response to another enquiry. I don’t know whether that also includes firmware updates.

In my opinion, however, it must be something to do with Victron / Cerbo and the integration with the Fronius, since Fronius’s Solar.web displays the data correctly

see Wrong Fronius Modbus value interpretation - v3.80~39

Right, so I’ll have to wait for 3.8 and then wait for another update. I’m glad it’s already known about and fixed.

Thanks!

According to Victron problem got fixed, but solution might be too late for 3.80 release.

As far as I am aware, it is in as 3.80 was not released when it was expected to.