The charge voltage is controlled by the battery anyway. You can set the MPPT settings (just in case it ever ends up in standalone mode by accident), but in a system with a managed battery, those voltages are not used. The voltage requested by the battery is used. So it is good and fine that you want to tidy up a bit, but it is not going to make the battery charge to 100% (well, Murphy might try to prove me wrong, but I don’t expect it will make a difference).
What I think is going on is the usual SOC estimate shenanigans. One module is probably slightly lower than the rest, but it has a high cell that needs to balance away. While this is ongoing, the BMS estimates the SOC as some weighted average of the whole, and as such it cannot get over 97%. It will get there in time.
The battery I see this most often with, is Dyness. I’ve seen Dyness batteries that doesn’t reset to 100% unless you exceed the voltage they asked for.
I have set all MPPT’s as per Freedom Won’s recommendations, absorption and float at 55,8% and will see what happens over time.
Another issue I picked up on, is that the installer never upped the battery capacity from 300Ah to 400 Ah with the new battery. This I have now changed with TTT’s help on VE Configure. Seems the battery lasts longer now if going by the rate the SOC percentage drops.
So now I have a new issue now, please help.
This morning I tried to update the Venus. It showed as version 3.12 and showed same must be updated.
Well it was seemingly unsuccessful as I got an error that there was no response from the GX device during the upload process, but two way communication is enabled.
Then when I exited, and checked/scanned again, it showed the GX as up to date now, but still with V3.12???
Oh and now, my batteries are shown on the remote console as Pylontech, as opposed to Freedom Won.
Also… not a number that is used during normal operation. The battery measures the SOC. That Ah number in the Multi is only used when the Multi is doing the SOC. So again, for neatness, you can make them the same, but in practice having a wrong number here doesn’t do anything bad.
For the “Pylon issue”, there is a “Redetect battery” option. Try that. Although it is weird that it identifies incorrectly. Maybe the new battery installed is now the master, and it has the wrong profile loaded?
Let me explain a bit about the detection. The way we detect Pylontech, is we look for the CAN-bus frame 0x359 (which also carries alarm info). There are only a hand full of batteries using 359 (instead of 35A) for this. The Pylontech battery also identifies itself on this frame, by placing the letters PN in the relevant locations.
Now in theory… if another battery maker wants to use this same protocol, they should leave that PN out of that frame. But many of them don’t, and to make it worse, some inverters (Sunsynk… cough!) won’t detect the battery at all without those letters (we, on the other hand, will probably missdetect it as an LG Resu… oops). Anyway…
So in order to support different inverter brands, the battery maker loads the right profile onto the BMS, so it speaks the language of the inverter correctly. Lots of them do this, not just FreedomWon.
If the wrong profile is loaded, ie if the battery was specced to be used in a sunsynk system, then a Victron system will detect it as a Pylontech battery. And then only charge it to 52.4V.
One solution might be to move the cables and make one of the other modules the master. But I am totally guessing. @JacoDeJongh is the expert when it comes to the Pace BMS.
No.
Just do it. This has happened automatically for years, but there is a very very small chance the inverter might restart during the update (and drop your power), which is why it is now a manual thing. At least this one time.
1 = Top left
2 = Bottom left
3 = Bottom Right
4 = Top Right
The Pace bms have two communication protocols, one on the RS485 / Can to inverter and one for the RS485 between the batteries. Both have multiple protocols you can select. Normally the protocol to inverter is unique to the battery brand and as a standard the protocol between batteries are set to Pylontech.
I suspect the BMS of the 4th battery was not configured correctly and used the Pylontech protocol on the Can to inverter. This is a bit worrying as i am not convinced that the rest of the config was done correctly. I will pop in and set it up for you to be the same as the other 3.
After the change we can see the Freedom Wons again.
Jaco de Jongh will probably weigh in now, but he assisted telephonically with what you guys are suggesting and did a quick test. Made the top left battery the Master and redirected the cables and all is well.
He says that the BMS of the new battery is still on a different protocol or firmware and that he will fix that for me. System now again shows Freedom bats.
