AgroVenturesPeru
New Member
- Joined
- Sep 19, 2020
- Messages
- 411
Well thanks for the suggestions. How should I go about doing this? Just unplug the CAN cable on the top battery of the stack, which connects the batteries to the CerboGX so that it no longer communicates with the CerboGX? What could go wrong?I thought about this thread overnight and the only thing I can come up with is what I stated already: Disconnect communication between the BMS and the rest of the system and see what happens.
How about your other suggestion of charging to what Pylontech wants vs. what Victron thinks Pylontech should charge to? I can set absorption voltage and float voltage as well as absorption time with the VEconfigure software I have. What should I set for each value?
It is my understanding that a Pylontech US3000 battery has a built-in BMS, therefore I'm not sure your comment makes sense. I'm not the kind of person that opens and dissects batteries like Will Prowse. Even if I were, I would refrain since they're under warranty.Have you tried disconnecting the BMS communication from the rest of the system?
For what it's worth, the Victron Touch50 (the touchscreen visual front-end for the CerboGX) on my system tells me the temperature of (I'm assuming) the battery whenever the battery triggers a low temperature alarm, which means that the system itself is able to measure such temperatures. Therefore, in my opinion if this is the root problem I'm having with the batteries then the system should be able to override the erroneous alarm. I don't think that is the root problem. I'm leaning more towards the "info" from the Cerbo being a misidentification of the actual problem. Either way, it sounds like a very annoying, minor, hard-to-diagnose glitch that sounds perhaps like a preview of coming attractions for dealing with this system over the course of its lifetime.
No. Pylontech said I would need some special cable set for that. I reached out to my distributor. Crickets. Reached out to another vendor in Peru. More crickets. Looks like I'd have to have Pylontech send them directly from China. (Unless you can help me come up with another way to verify voltage and soc of each battery).Have you verified that all four batteries are at the exact same voltage and state of charge?
Here is my latest update from the Victron forum I posted today. The only other thing I tried were the suggestions from Snoobler about Float/absorption/absorption time. Finally had the time today to try those suggestion. It didn't matter. No difference:
From what I can gather, there are two issues:
1) The third battery in the battery bank is preventing the entire battery bank from charging to full capacity.
2) This battery has a red alarm light that comes on once or twice a week. The cerbogx states this is a low battery temperature alarm even when the temperature is 25C (77F). I'm thinking the cerbogx is just misidentifying/mislabelling the actual problem.
Hypothetically speaking, if you could somehow get just one battery in your stack to reach dangerous low temperatures, would that cause the entire battery bank to stop charging when in the 84-89% range?
Yes, my batteries now will not even get above 84% SOC!
The low temperature alarm may or may not be the root cause of this issue. If there's a faulty temperature sensor, then why would it cause the batteries to limit capacity even when no alarm is triggered? As I said, the low temperature alarm is only triggered randomly a couple times per week at most.