Why is my Pylontech Battery not fully charging?

Dear all,

I have 3 Pylontech US3000C in a system with 1 Multiplus II - 48/5000/70 - 48 and the CerboGX.

As you can see on the screenshot the Batteries are not charging to 100%. The status of the Battery BMS tells 76%, and below is the information of 85%.

So this really confuses me. How can I adjust the Battery charging to more than 76%?
Als ot tells me it is chargin (on the bottom) but there is no active charging.

Best regards

Hi. A bit of guessing here…
That “BAT1” tile is your Multiplus selected as an accessory monitor. It’s been renamed. It’s own SOC has been enabled, which Victron don’t recommend as it will be different, and that confuses people. As you’ve found.

It’s 52.38V is typical of Pylons at full (or very near) charge. So it’s trying. Yet the battery itself is only 51.02V. If that 76% was real the battery reading should be very close to that of the Multi, and accepting charge. So maybe there’s a disconnect between them in the wires, fuse, isolator? Or even the Can cables?

Yet 51.02V is still quite high for those Pylons and suggests they could be already at 100%, the CCL set to 0 and isolated from the Multi charge. Meaning the 76% is incorrect, might be possible but I’ve never heard of that happening.

You’re going to have to delve deeper to the detailed data to try to find something unusual. Like maybe not all 3 batts shown as connected. etc. if you need come back, there’s plenty here who know Pylons.

You could also try a complete shutdown and reboot of everything. Or a firmware upgrade of Multi and GX.

1 Like

Thanks a lot!
Firmware is up to date, already check.
With the BAT1 I just have to check.

In my devices list I have the Multiplis II named "Hub! and the Pylontech with its own name, “Pylontech battery” (which I didn’t touch). So continuing the check.

In CerboGX, menu “DVCC” I have as Controlling BMS the Pylontech Battery itself.

In System Setup it states “automatically selected” → Pylontech battery on CAN-bus.
Has DC Systemn is activated.
In the menu “System Setup” - “Battery measurement” (translated by me…) I see the Pylontech Battery and the Multiplus II. If I select Multiplus II the scrren as below is displayed. I will deactivate mutliplus II and see what happens. (This is where BAT1 is changed - I suppose by me …)

After the change I checked the Pylontech. These are the data:

And my system view changed to:

Unfortunately I can’t find the menu for SOC.

And here is some detailed data on the battery voltage und current. Seems all ok.


If you have a SmartShunt, post the setup data here.

If not : buy one

The V’s are different. VE.Bus is the Multi and System is the Pylons. That would appear to be the base issue. It’s not unusual for say 0.3V difference to show, but not that much. Might be time to break out the multimeter to see which is right. If both right then it’s your wires.

It’s ok to leave up that Multi tile, it won’t hurt. And there’s also a lot of Pylon data via Device List.

3 Likes

The pylontecs should be controlling the system through DVCC.

Othewise you have to set the ve bus charge voltages differently to the victron pylon guide.

1 Like

I don’t have one.

I just did some measurement with the multimeteer. all 3 Pylontech have 52.25V, the same at the connection to the Mutliplus II.So I wonder why the Dashboard says 51.00 to 51.08V

Yes, in DVCC the controlling BMS is Pylontech.

Usually the ve bus soc usually synchronises to the battery bms so that is strange.

It would seem then your other SOC device is not synchronising the same way.

The different V sounds like an issue in the Pylons. You could try switching to a different Master unit to see if that changes anything.

Do you have your system as an ess system have you tried with keep batteries charged?

Apparently, there is no PV in your system - so, you should validate your charge schedules. Do they have endet? Do they target a soc of only 76-80%?

If there is no charge schedule active right now, the system won’t charge.

If you use dynamic ess, the system may just have concluded that it is not required to charge more at current prices with regards to the forecasted consumption.

1 Like

Where do I access the menu you showed?

Right, I have no PV actually. I approach step-by-step.
I did not set any charging schedules. (I assume you mean setting them in VE Configure?)
Nevertheless the system did charge yesterday at the same time as now, it was at 37%.

I have also no ESS set.

Here a screenshot from the VE Configure charger settings:

What I just realized is a mismatch of the different voltage informations:

Hub1 is my multiplus II: It shows 52.38V, which is not so far from what I measured with the multimeter (52.25V); SOC is set o 85%.

Pylontech is showing me these data as actual values:

And these are the parameters of Pylontech. Here I see the 52.2V.

So my assumption is, that the multiplus has somehow the 52.38V, which are still below the charge voltage limit of 53.2V. and the pylontech BMS says actually it has 51.04V, which is not correct based on the multimeter measurement I did.

The charger tab in VEConfigure has no meaning, while there is BMS control.

It is just required to be configured in case there is a communication loss with the battery.

Well, if you don’t use the ESS Assistant, I can’t tell you how the charging is done. (With ESS, you could go to “Settings->Ess->Schedules” and define, that it should charge upto “X” in a defined time window.


What is your overall desired behaviour? Just an emergency batterie to be kept at 100% or do you want to actively use it for self-consumption and charge it when grid prices are cheap?

The ESS Assistant is my next step. You are absolutely right with you assumption for self-consumption and grid price alignment.

Target is to

  • Use the batteries in the time between 17:00 to 22:00.
  • Charge the batteries in a first step from grid in the times between 22:00 and 06:00
  • and in a second step charge the batteries during daytime when I include the PV from PV.

Yeah, then you should proceed to enable the ess assistant, it will give you the required schedule option to control the behaviour.

I.e. “charge from 22 to 6 to 100%” - self consume the stored energy from 6 to 22. (Well, every no-charge-window would be implicit self-consumption, so you need another schedule targeting 100% from 6 to 17 - it will then keep the battery charged.)

Which assistant do you advice to select?

I have 4 of them, and almost all show deprecated in the background when I start the assistant configuration.

  • ESS (018C)
  • Self-consumption Hub-1 (0186) → Deprecated watermark when on the “Select Policy” page
  • Self-consumption Hub2 v3 (0187) → Deprecated watermark when on the “Select Policy” page
    and 0168 / 0188 as deprecated

all is updated, the assistants and VE Configure?

ESS, all others are deprecated and only there for compatibility reasons.