Question SOC Anomalies on Monitor after updates

@joel-brodeur

Yes!  I am seeing this same behavior on the same setup ... (2) 280Amp Indoor Batteries and a 6000XP ... latest firmware on both the batteries and the inverter.  I did not have this behavior prior to the battery firmware updates.

I looked at the data logs and it seems the batteries are discharging at ~0.9Amps (while there is available solar!!) ... the discharge forces the batteries from 100% to 99% and then the available solar charges them back to 100% ... this repeats until there is no more available solar (sun goes down) as far as I can tell.

The maxChgCurrent (BMS Limit Charge: on the monitor) seems to always be at 14A as well. 

Not exactly sure but might be related to one of these things ...???

That is what I was think as well.  It is a bit disconcerting seeing the change in monitoring methodologies.

Hopefully EG4 can chime in tell us if this is the new norm or if there is something we can do?

Thanks,

JB

@eg4eric

Any thoughts on this???

2 sets of screenshots ... Solar charged batteries to 100%, then solar cutoff but battery discharging at 0.7A ... will do this until batteries get to 99% then solar will charge batteries back to 100%.

Thinking the bouncing between 99% - 100% SOC is not a good thing??

I can share station name / serial number as needed.

Thank you.

99% to 100% ... discharge at 0.7A even though solar power is enough to offset consumption. 

Back down to 99% and charge back to 100%

Still occurring.  Was hoping that it would stabilize after a bit, but it hasn't.

@eg4eric would you have any suggestions?

I am just concerned if there is something going on with my batteries that should be concerned about of if this is just related to the new updates I installed?

Thanks much.

@yooperjay Have you seen any improvement or heard anything on this? 

I called my vendor (Signature Solar) and they said it was because my loads were greater than the solar input so it was drawing from Batteries.  There is a slight possibility that was the case at the time. 

But since calling them I have had days when there was more than sufficient solar and should have never pulled from the batteries.  Yet it continues.

Thanks,

JB

@joel-brodeur

I reverted the firmware back ... it mostly solved the problem of it bouncing between 99%-100%.

I no longer see the bouncing but sometimes either battery 0 or battery 1 will show 99% and a limit charge of 28A even though there is plenty of solar (sun) today.

This is off-grid cabin so right now we are not there so minimal consumption (charger for battery on generator and Starlink).

I'll be up at the cabin over the weekend and might try the new firmware again but will most likely be back to bouncing between 99%-100% as before.

I asked how I'm supposed to get to 80% DOD (100% - 20% - 100%) ... system gets down to 92% at night at then charges back to 100% within a couple hours once the sun comes up.  They (S2) said to just turn the solar off once a month so the system will get down to 20% and then let it charge back up.  I've done that once before but at the time I wasn't there to turn the solar back on so the generator kicked in to charge back to 100% (I updated to charge to 100% ... usually stop at 80% on generator).

I'm not sure if this is a long term harm to the batteries ... to cycle between like 90% - 100% (over 24 hours) when we aren't at the cabin but guess it is better than constant cycling between 99%-100%.

Sorry for the non (lengthy) answer.  

I think we both pinged @eg4eric on this ... 

Thanks.

@yooperjay Thanks for the update.

I too have been trying to figure out how to do the 80%DOD since I am not here all the time and don't want the Gen charging when I have plenty of sun.

Interesting that reverting cleared it up.  Must be something in the SOC reporting logic, or in the charge logic.  It almost seems like when the batteries hit 100% the inverter immediately starts drawing from the batteries instead of using solar as primary.

I am thinking about updating to the newest firmware and see if that resolves anything, but I am still very curious about what changed so I can understand what is happening.

Thanks again for the update.  If I hear anything or can figure it out, I will post here.