Why DVCC setting "Limit managed battery charge voltage" does not work?

Question

question

kirby asked Dec 7, '22

Why DVCC setting "Limit managed battery charge voltage" does not work?

Can someone tell me, why "limit charge voltage" doesn't work? But in the same time, current limit works well.
Cerbo GX is not connected to the battery.

For "Limit managed battery charge voltage" I set max value: 56.6V
For "Limit managed battery charge current" I set max value: 35A

Are there some pitfalls?

I have the system:

Victron MultiPlus 5000/48/70
Cerbo GX
LFP battery with I/O: 1x RS232 (RJ-11), 2x RS485 (RJ-45)
No CAN interface (RJ-45)
Like this one: https://www.xdbattery.com/512KWH-48V-lifepo4-Rack-Mounted-battery-module-309.html

cerbo gx multiplus ve.bus

image-2022-12-07-221542764.png (10.7 KiB)

2 |3000

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

Modifications Space

Node Red Space

Answer 1 · 2022-12-08T03:21:23Z

kevgermany answered · Dec 08, 2022 at 03:21 AM

Is the temperature compensation off? It should be for lithium.

2 |3000

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

Answer 2 · 2022-12-08T04:16:44Z

Alexandra answered · Dec 08, 2022 at 04:16 AM

@kirby

A couple of thoughts here.
A BMV is helful in non can interfaced batteries.

If what is pictured is the DC bus voltage widget then it is not a reflection of the battery voltage. Check you battery with a meter.

The balancing in the battery may also not be working fast enough, so charge at a lower amp rate. That can also cause overshoot.on battery voltage.

Battery bms switching off due to overcharge can cause that spike as well.

2 |3000

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

question