EG4 Community Forum

BMS not correct in ...
 
Notifications
Clear all

BMS not correct in detecting capacity

2 Posts
2 Users
3 Reactions
10 Views
Posts: 1
Topic starter
(@middlesiggy)
New Member
Joined: 18 hours ago

I wanted to share a recent experience.

My setup is an EG4 18KPV with 3 Internal 280ah wall mount batteries in parallel.

I live in Ohio in the US and during this last 60 days I have only seen my batteries reach 100% twice.

Over the last 2 months I have experienced something odd twice, which is this:

I would wake up in the morning, and expecting to see my batteries at 20% (as I am using the EG4 setting for my lithium batteries and SOC settings to stop using batteries thru the night at 20%). But instead I woke up to my batteries at 0%, yet I still had power.

I state it this way because the only way they would go to 0% is if grid power were off, and for some reason my Generac generator did not turn on to charge the batteries. So this was odd...

This happened about a month ago, and then on Thursday.

So what was being displayed on each battery was, yes they were at 0% power, and also on the EG4 it stated that it had lost communication with the batteries, and checking the alerts, it did report multiple "low power" and then "loss of com". Deducing the problem, this was of course because the batteries were at 0%, and hence they did not communicate.

But this should not happen.. right?

Well in speaking with Signature Solar's Tech support (they are great BTW) I floated a hypothesis that the BMS was confused, and although it was stating the batteries were say at (some percentage) in reality they were not. The tech on the call agreed with my hypothesis and after sharing with him that the batteries never fully charged but twice in 2 months, that the BMS probably learned a different "high" and "low" mark and hence the percentage values must not be accurate.

So in the meantime we have flipped the system to "Lead-Acid" and coded in the proper voltages. He stated to keep it this way for minimally 7 days (oddly specific, but maybe someone can shed some light on that statement)

I also used the AC charge function to fully charge the batteries so they would at least get a full exercise.

So here is the real question for my EG4 friends...

1) Is my hypothesis correct? did the BMS get confused and then was not able to gauge the proper percentage and hence ran the battery down all the way inadvertently.

1.1) If this is the case, wouldn't it make sense to make a "battery protection" or a "BMS protection" mode, that allowed for a full charge via grid or generator after "X" number of days of not having a full charge, to make sure the BMS knows what is going on?

1.2) OR.. possibly utilize the voltage & the SOC values to add a secondary check on the system to make sure things are working as expected.

I bring this up, because not I am stuck with this problem, which is how do I get my wife to understand the issue, and the solution, when she thinks a light a switch is "magic"...

We need a way for the system to be "smarter" and to take care of it's own maintenance functions, or have the ability to enable the "Maintenance" functions for those of us in colder not always sunny climates.

Thoughts?

Thank you

1 Reply
Posts: 68
(@jlankford)
Trusted Member
Joined: 2 months ago

Many people ignore the SOC percentages and use voltages instead, to trust what their battery state is. If charging or discharging current is small, then it's likely the BMS is losing track of the SOC whenever current is below a measurement threshold. If the SOC is not able to reset to 100% with a full charge frequently, then day after day these periods of small current can cause the SOC to drift further from reality. EG4 has confirmed here that the current measurement threshold for the LL-S rack battery is 0.5A. I don't know what it might be for the wallmount - it could be larger. And note that you have three wallmounts, so any small current will be distributed across all units and make it even more likely the current at each one could fall below the threshold.

You may want to read this DIY thread - it gives a better explanation for why the BMS-calculated SOC will drift. Also note that this guy states here that a calculated SOC simply cannot be trusted on a system that does not charge to a full 100% every day. That might be an exaggeration, but I tend to agree with this statement.

https://diysolarforum.com/threads/tips-on-bms-balancer-optimization-and-various-discharge-curves-for-lf280k-v3.94834/#post-1270436

Personally, I've concluded that for my system I need to use closed loop communications, but voltage control and not SOC control. I can't trust the SOC control for the reason stated here.

Reply
Share: