diy solar

diy solar

EG4 PowerPro batteries suddenly died

thepetersms

New Member
Joined
Jan 30, 2024
Messages
34
Location
Texas
I have two eg4 powerpro wall mount batteries hooked up to one eg4 18kpv. All has been working great lately until tonight. I go into my shop/office tonight and look at the system as I do almost every night and notice the batteries are at 0%. This had me scratching my head as I looked earlier today and they were fully charged.
I've restarted everything, updated the inverter firmware with no success. Even the small LCD screen on the batteries is in protection mode and at 0%.
I tried setting it to grid charge and it won't even charge from that. Screenshot 2024-04-06 204836.png
Anyone have any ideas?
 
Just picture Gavin Newsom saying…That’s Eg4! Instead of “That’s California” 😁
 
Since it looks like Batt-Inverter communication was lost first then the low batt warnings came second. I would suggest trying to establish coms and if that doesn't work. Shut off coms and SoC control and go back to voltage based charging. Let us know if that worked.
 
Since it looks like Batt-Inverter communication was lost first then the low batt warnings came second. I would suggest trying to establish coms and if that doesn't work. Shut off coms and SoC control and go back to voltage based charging. Let us know if that worked.
I swapped out the battery com cable from inverter to main battery and changed it to voltage charging. It's now charging. But the big question is where the heck did all the power go from both batteries???? It was at 99% charged as then 2 minutes later it went to 0
 
I swapped out the battery com cable from inverter to main battery and changed it to voltage charging. It's now charging. But the big question is where the heck did all the power go from both batteries???? It was at 99% charged as then 2 minutes later it went to 0
The SOC could be out of calibration - try charging them up as much as you can and it should reset the reading. The other thing could be the 100% was a false reading somehow, and once the batteries detected they were empty you experienced a system shutdown and they updated their reading.
 
Monitor the recharge cycle with regard to time and how many Ah it takes to reach full charge. You may find the battery was not actually at 0%. The theory being if the coms failed, one would not expect the readings to be accurate anymore.
 
Ok batteries are fully charged and I updated the firmware on both batteries. I'll continue to monitor the system.
One question I have, what's the difference between the eg4/lux and P07-Lux CAN protocols?
One would think the main battery should be set to eg4/lux but signature solars setup video says to put it on P07-LUX
 

Attachments

  • 20240407_142155.jpg
    20240407_142155.jpg
    156.1 KB · Views: 16
  • 20240407_142242.jpg
    20240407_142242.jpg
    135.2 KB · Views: 16
I had that happen one night as well. Never figured out were all that battery power went either
 
Ok batteries are fully charged and I updated the firmware on both batteries. I'll continue to monitor the system.
One question I have, what's the difference between the eg4/lux and P07-Lux CAN protocols?
One would think the main battery should be set to eg4/lux but signature solars setup video says to put it on P07-LUX

They are functionally similar; however, I would recommend using CAN communication over RS485 if given the option. Also, if this continues, I would make sure to check the link on the ethernet cable as well.
 
I had that happen one night as well. Never figured out were all that battery power went either
It didn't go anywhere, it never existed in the first place. Once the battery SOC calibration drifted enough that the battery thought it was fully charged when it was nearly discharged, you were in for a rude awakening when you used the last of the (actual) power in the battery and it shut down. [Hopefully the new firmware solved the problem as I've got a similar setup on the way, and am curious how to reset SOC occasionally (and how often?) to prevent calculated versus actual SOC from causing the above issue.]
 
Back
Top