Is the specified charging current in DCVV not being maintained?

Good morning,

All our systems are built the same way and consist of three MultiPlus units, a SmartShunt, a Cerbo GX and Smart batteries.
Using the settings under DCVV, we set the maximum charging current variably (via ModBus).
That works well.
But at the moment, we have a problem: it no longer works.
The charging current is fixed by the settings in the MultiPlus.

We’ve had this problem before. There was an issue with the Cerbo GX firmware.
We’re currently using firmware V3.13.

Has this issue been fixed in a newer version?
I don’t want to start experimenting at the customer’s site. The customers are rather “sensitive” :frowning:

Thanks, everyone.
Best regards,
Mandi

I’m currently having this problem too..

The power can be set/limited… but after 30-60 sec it goes back to the max value…

Has anyone found a solution to this problem yet?? (I’m using the latest update)

What kind of batteries do you have, and which version of Venus.os?

Everything is up to date … just updated a few days ago..

There are several Pylontech batteries .. they can handle over 200A.

For noise reasons, I sometimes want to limit the charging current..

I can set it to, say, 20 A … but after 30–40 sec. DVCC automatically changes the current back to the batteries’ maximum ::::

Not adhering to the ccl override is a known issue with 3.80 and pylontech. Already topics open for this. Upgrade to the beta or downgrade to 3.79. It should be addressed in 3.86.

You should be able to set this parameter via modbus, sounds like you’re setting something else if it keeps changing (also known behaviour).

You can set the DVCC max current limit (but this will be ignored if exporting is enabled and with the 3.80 bug).

via MQTT: W/dxxxxxxxxxxxx/settings/0/Settings/SystemSetup/MaxChargeCurrent