I have an 18kpv with 6 eg4 rack mount batteries (ll-s and ll v1) running the multipack firmware. Up until recently the max charge current was always 100A or more depending on the state of charge. Lately unless the battery SoC is near 100 the max charge shows 50A (even when the stack is very low.) The batteries take charge with a chargeverter and generator just fine, it seems the communication with the inverter has gotten out of sync. Running the latest inverter firmware. Any thoughts as to why I am seeing this behavior and what I can do to get it back to where it was before, at some point it showed 300A charge 600A discharge but now it only shows 50A/100A looking at historical data
historical data from 12/30:
for last few days:
Did the number of recognized batteries also change? Does the inverter still show 6 batteries and 600Ah of capacity? The new numbers look like only one battery is connected. The max charge current parameter changes dynamically as the BMS adjusts the charging cycle, but I've never seen the max discharge current value change.
Unfortunately, it doesn't look like the battery count and capacity are stored in the data history, so you'll have to go on real time values.
Per the mobile app it shows 6 batteries, 600AH capacity, 50A limit charge, 100A limit discharge. Number of batteries haven't changed. It is almost as if the charge limit is only for one battery, but all 6 are detected.
I agree those are expected charge and discharge values for one LL-S battery.
I would reboot everything. If you're unable to restart your inverter, then I'd try shutting down 1/2 of the batteries and wait to see if the battery count and capacity adjusts - for me those values will update on the fly, but it may take a few minutes. If that works, I'd next turn off all but one battery, wait to see the inverter update. And then finally turn all batteries back on and hopefully see all 4 parameters update to expected values.
Good morning. I did all of that, the parallel number and capacity change, but the charge/discharge settings do not.
That's too bad. Did you reboot all, or just shutdown some of the batteries?
rebooted everything. started with just the LL-S, waited until everything came back up, showed 50A/100A with 100Ah cap. Put 1 V1 in the loop, cap went to 200Ah but charge limits didnt change. Same thing with batteries 3-6, cap went up by 100 each. Doesn't really make any sense, it was all working perfectly for a couple weeks (had to replace a v1 with the LL-S under warranty.) I spent some time going through the historical data and it looks like 2 days ago this started, the batteries topped off and ever since then its almost as if the V1s are reporting capacity but not communicating they will take charge to the inverter. They definitely will take charge, i can use my chargeverter to charge up the stack to account for solar loss (the inverter seems to be capping the battery charge at 50A due to this, sunny day and the MPPTs look to be trimming any excess.) Normally on a sunny day the stack will fully charge before noon, but last two days it did not which is how I noticed this, the stack got down to ~38% which is unusual for a sunny set of days for me so I started investigating.
I'm out of ideas. Hopefully EG4 support will get involved with this thread.
It's true the inverter will follow that max current parameter from the master BMS. I see this frequently with AC charging, all the way down to 5A when the SOC is approaching 100%. A temporary fix for you to utilize all your solar would be to switch to open loop and have the inverter control charging only based on voltage.
Good idea. That will at least let me charge the batteries until they can help address the issue. You wouldn't happen to know the values to set for voltage offhand, otherwise I will look them up.
Best to look them up.
And actually, I have one more idea - what happens if you completely remove the LL-S and reconfigure all the comms to have a bank of all the same battery model? This seems like a problem with comms and the mix of battery types, but I don't know how to fix it. I would call EG4 support instead of waiting for them to respond here - sometimes that takes days. But, please report back the solution here if you can.