Quick question, since loading 3013 BMS I have had 3 instances now of SOC dropping from 100% to 0% accompanied by BMS Over Voltage warnings.
I have been advised by GivE that another F/W fix is being worked on to address this.
Can someone from GivE please advise ETA of new F/W ?
Thanks.
Fireplex it's in beta at the moment. Was told around October a couple weeks ago. But take with a grain of salt. Can always downgrade back to 3012
Yeah I've had that as well. With the recent warm weather, it's been a daily occurrence this week. 3013 firmware on a gen 2 inverter.
lam22 I’ve only upgraded the firmware to 3013 on one of my batteries. This week I’ve seen several battery over voltage errors, and I rarely see them on the other (3012) battery.
It could be that 3013 is better at monitoring this than 3012 and I am missing out on potential errors in the battery, but for now I’m not inclined to upgrade the larger battery to 3013 as its stable on 3012.
I was under the impression that if this happens, I just need to wait a bit for the battery charge to drop slightly before they come online again and read accurately. 9 hours later though - still showing as 0. I've put the kettle on etc but all it does is draw grid power instead of battery.
Or do I just need to wait longer?
lam22 I just had my battery stuck on zero with a red flashing light on it. Tried resetting the inverter, reset to defaults, etc, no change. I powered off the battery with the side button and the breaker and its now at least partly alive, SoC is rising
I’ve had this since 3013 but fortunately only once. The battery voltage went over 60v so I hope that hasn’t damaged any cells. Since then I’ve been monitoring individual voltages and there are 3 cells that always have a higher voltage than the others when charging and lower when discharging, not by much but it is noticeable as the other are virtually identical.
geoffreycoan My battery isn’t alive. It seems to charge but won’t discharge and the SoC fluctuates all over the place. Battery temperature is reported in the inverter as -19 degrees and GivTCP can’t read any data from the battery (error all the time about zero read so previous value assumed).
Logged a call with GivEnergy who say it sounds like a stuck BMS and need my installer to come onsite to resolve it ☹️
I've set my battery charge to 98%. Fingers crossed this avoids the SoC drop as it only seems to happen when the battery is at 100%.
When the 100% > 0 SoC drop occurs, I've noticed the battery voltage needs to drop to about 53.6 for it to kick in again. As the battery isn't being used, this can take hours. I can attempt to restart the batteries to kick them into gear sooner but this is only partially successful. I've seen a few times the batteries come alive again only for the same thing to occur a few mins later.
lam22 I have done similar, but unfortunately the charge to % only works for grid charging. Solar will always push the batteries to 100. My batteries are at 98% currently so I’ve put my car on charge and the air con to pull that back down, to try and keep away from 100% in this heat.
ProximusAl Ah yeah you're right, that's a shame. Have you tried pausing the battery when it gets to the high 90-ish percentage mark? Admittedly that's a bit cumbersome, and having to monitor each battery individually to do it.
lam22 I find pause doesn’t exactly work like it should. When I pause, there is always an few hundred watts still pouring in.
ProximusAl If you set the charge rate to zero it stops charging (at least on my gen 1 inverters it does)
I found pause only worked for a fixed time period, up to 3 hours, then charging resumed but setting by setting charge rate to zero (in HA) I have been able to keep the SoC to a limit. If you have HA you could automate a forced discharge if the SoC gets too high as well.
...and...
NB I don't get any associated SoC drop when this happens. SoC stays fine - always has been on my Gen2 ("Gen1.5") hybrid.
My battery had many days in a deep-discharge state just after initial installation, because an Inverter firmware bug stopped it from charging. So my graph may well be indicative of physical damage rather than a BMS firmware glitch.
I've also had this on 3 separate occasions since the system was installed in August. Each time my installer has come out (the first time with a GivE technician as well) and found a burnt out cable between the battery and the inverter (I think). Replacing the cable has fixed the problem until the next time the battery reaches 100%, then it burns out again, effectively crippling the system. No mention of a F/W issue by the GivE tech, in fact no proper diagnosis at all.
Has anyone else had the burnt out cable problem? Or found any other solutions?
PMSol burnt out cables is a new one, never heard of anyone else on the forum reporting that issue. The cables are 10mm thick supplied by givenergy and look to be more than up to the job. I'm no electrician but to me having the cable burn out 3 times is indicative of an underlying hardware issue such as a poor connection to a plug socket in either the inverter or battery. It might be arcing and causing the cable to fail.
Definitely shouldn't be happening, and certainly not more than once
BMS 3013 is more sensitive to recording high voltage and has some faults so has been withdrawn by givenergy. The support team can downgrade you to 3012
Hi and thanks for your reply. A quick update: my installer has put in uprated cables and downgraded the firmware at GE's (and your) suggestion to 3012.
I'm aware from this and other threads that 3012 is not without issues but so far (and it's still early days), I've had no further problems or over voltage notifications.
GE downgraded me to 3012 and since then all good.
Pity no one from GE could answer my original query:
"I have been advised by GivE that another F/W fix is being worked on to address this.
Can someone from GivE please advise ETA of new F/W ?"