diy solar

diy solar

Anyone else with a recent EG4 48v Lifepower4 battery purchase getting a "Charging MOS fault alarm" that can't be reset?

Wolfpack7483

New Member
Joined
Dec 21, 2023
Messages
12
Location
Charlotte, NC
Got my battery last week, but today was the 1st time to get a full charge on it. Everything was great @ 99.6%, cells balancing, current curtailed, but I had to leave. Got back about 1 1/2 hours later to the beeping & red light associated with the fault. Re-set didn't work & I couldn't find anything online about it. Called Signature Solar support, and they said this has been an issue with a recent batch of batteries. They asked me to open the battery & send them a picture of the CMOS, to make sure it wasn't a real fault. It wasn't, & they sent instructions to go into the config tab and enter a settings change in the "reading and writing of MOS adhesive fault codes" That did the trick, just hope it doesn't come back again in the future.
 
Thanks. As soon as I read your post I did mostly what you did (before you provided the response). I already knew the password.
I first read all the other batteries and the "reading and writing of MOS adhesive fault codes" was 00.
For the failed battery I entered FF set it, then read to see if it took, it did. I then entered 00 and set it then read to see if it took and it did. Now it reads the same as the other 5 and the alarm has cleared.

The CMOS and DMOS are now both on and the battery is taking a charge. You saved the day.

Thanks for the post...
 
Dbarr Issue: 04-01-24 (Not an April fools joke)

EG4 PowerPro4 48v100Ah Battery SOC low Alarm


The batteries (Both attached in parallel) voltage dropped to 51.2v and caused an alarm light to flash.

The Fix: Charge batteries up to at least 53v, then turn breakers off, unhook batteries from everything, push “RESET” button. Then turn batteries back on one at a time to make sure everything is working. Turn breakers off; Hook everything back up, Turn breakers on one at a time.

Looked into forum for posts similar, tried the MOS rewrite with no success and the above is what worked for me.
(Note): I just received the two EG4 batteries less then a week age and have them to recharge my EcoFlow Delta Pros.
 
Got my battery last week, but today was the 1st time to get a full charge on it. Everything was great @ 99.6%, cells balancing, current curtailed, but I had to leave. Got back about 1 1/2 hours later to the beeping & red light associated with the fault. Re-set didn't work & I couldn't find anything online about it. Called Signature Solar support, and they said this has been an issue with a recent batch of batteries. They asked me to open the battery & send them a picture of the CMOS, to make sure it wasn't a real fault. It wasn't, & they sent instructions to go into the config tab and enter a settings change in the "reading and writing of MOS adhesive fault codes" That did the trick, just hope it doesn't come back again in the future.
same on my 2 batteries, first time i'm charging them. got them in february, so they sat for 2 months but still reported 2/4 LEDs SOC.

i dont have time to pull the batteries from the rack right now. is the inspection needed? what would cause a false alarm?
 
I think it's likely that most are false alarms. The inspection is to see visually that the mosfets aren't fried. If the setting change works, I'd think everything should be OK.
 
same on my 2 batteries, first time i'm charging them. got them in february, so they sat for 2 months but still reported 2/4 LEDs SOC.

i dont have time to pull the batteries from the rack right now. is the inspection needed? what would cause a false alarm?
I didn't do the inspection, just did the reset. Figured if that didn't work I would do the inspection. Mine was caused because I didn't have the most up to date firmware on all the batteries. Was mixing firmware unknowingly. Signature Solar doesn't do a good job at instructing new buyers to update firmware after purchase and before install...
 
Signature Solar doesn't do a good job at instructing new buyers to update firmware after purchase and before install...
Hi! :) I just wanted to pop in and clarify, per EG4, we really don’t recommend immediately updating firmware after purchase/before install as it could possibly cause it to stop functioning, becoming a brick. Basically, we advise that unless there is an issue, don't adjust the firmware.
 
Last edited:
If you are not running Version 3.37 firmware (have an older one) and you are using an EG4 Communications Hub you will need to update to v3.37 as the firmware update increased the baud rate on the pins 7&8 RS485 port to 19,200 which is what the BAT Input on the Hub requires. This increased baud rate becomes even more important as you add additional batteries to your stack.
 
Last edited:
Hi! :) I just wanted to pop in and clarify, we really don’t recommend immediately updating firmware after purchase/before install as it could possibly cause it to stop functioning, becoming a brick. Basically, we advise that unless there is an issue, don't adjust the firmware.
Is this advice limited to the eg4 batteries or the aios as well?
 
Hi! :) I just wanted to pop in and clarify, we really don’t recommend immediately updating firmware after purchase/before install as it could possibly cause it to stop functioning, becoming a brick. Basically, we advise that unless there is an issue, don't adjust the firmware.
That's what I was told as well by SS technical support. However, when you purchase batteries at three different times months apart the firmware differences do cause issues. Maybe a general training at SS needs to occur to address these different case scenarios? Then the sales staff could pass on that information to returning customers, like myself.
 
Hi! :) I just wanted to pop in and clarify, we really don’t recommend immediately updating firmware after purchase/before install as it could possibly cause it to stop functioning, becoming a brick. Basically, we advise that unless there is an issue, don't adjust the firmware.
I would be curious what eg4 says about those comments. From someone who creates firmware, if what you are saying is true about firmware update bricking, it's a major design flaw. Recommending someone not update is a poor solution, because some people won't have a choice.
 
I would be curious what eg4 says about those comments. From someone who creates firmware, if what you are saying is true about firmware update bricking, it's a major design flaw. Recommending someone not update is a poor solution, because some people won't have a choice.

EG4 recommends that you keep your batteries up to date. Provided that the appropriate guides and correct cables are utilized, updating the battery straight out of the box should pose no issue.

The guides and firmware can be found here: https://eg4electronics.com/categories/batteries/
 
Last edited:
Supposedly the Firmware Update Device (with 3.37) can restore a bricked BMS.

If you have the EG4 Communications Hub you might have to update the LifePower4 battery firmware because the Hub expects one of the RS485 ports on the batteries (pins 7&8) to be at 19200 baud (not the original 9600). In the end, I believe you should update the firmware in the Hub and in the LifePower4 batteries. Of course you can read the firmware version with the BMS_Test software and if it is 3.37 there is no need to update.

I would expect by now that all EG4 LifePower4 batteries are shipped with firmware version 3.37

And as @EG4_Jared pointed out, the correct cables ARE required.
 
Back
Top