Sol-Ark 15K + SOK batteries = Weird SOC issue

[Nobodybusiness]

I suppose I can just unplug the comms cable to accomplish this and let it sit at 57.6v for a while?

I'm right at 99% state of charge, but what has me confused now is the charge current limit of 47A rather than what I would expect closer to 300A, any ideas how it would come up with that number? Discharge of 285A looks correct, there are (3) SOK batteries connected to the Sol-Ark, but the 47A number seems, uh, odd?

View attachment 195343

It’s probably tail current.

 

[Watts Happening]

Thus far things are going somewhat better, the two newest batteries are the least balanced haha! As soon as they start drawing down even 1% they end up pretty darn close, but at the top, look at this.

 

[marionw]

I believe @marionw has done a lot of digging into the firmware iterations. Hoping they’ll chime in with potentially useful information

Edit. I see they’ve already contributed in here. I saw a separate post in Kenny’s thread this morning which made me think of it

SGP got back to me and requested pictures of the barcode off of each battery. Sent them the pictures and they responded that my batteries have the latest firmware. In other words the blew me off. If SOK is shipping batteries with newer firmware then I expect the SGP and Jakiper will also be shipping with updated firmware and no way to update batteries with older firmware. SGP did not respond as to how well their batteries with different firmware will integrate particularly in a closed loop configuration. Still trying to get answers..

 

[Kenny_]

They tend to give me that response a lot.

 

[Watts Happening]

I’m at a similar point. Dexter set me up with Jason at Current Connected, he sent me a PM early Friday morning. I responded immediately and have tagged him a couple times in this thread. I also sent another PM last night, haven’t heard anything back.

 

[marionw]

Just got SGP Reply:

Based on the battery serial number, you already have the updated software.
It's not a necessity for the battery with the latest firmware to need to be designated the “Master/Host” battery.

I am not necessarily buying it. Need to do further testing

 

[Watts Happening]

Just got SGP Reply:

Based on the battery serial number, you already have the updated software.
It's not a necessity for the battery with the latest firmware to need to be designated the “Master/Host” battery.

I am not necessarily buying it. Need to do further testing

I can’t remember what the process is for re-addressing, obviously in could just flip dip switches, but don’t I need to restart the BMS or something to that effect? I can go try right now, but battery 3 will remain battery 3 haha

 

[DougfromdaUP]

Don’t worry about your batteries being out of balance at the extreme top. That’s going to happen.

Have you actually measured the battery voltages? They must be disconnected internally to have such different voltages if they’re connected to the bus.

 

[1201]

@Watts Happening Has this issue been fixed? Ie are all your parallel batteries now showing the same voltage? Did you ever measure with a multimeter?

 

[1201]

Updates?

Looks like Elvis has left the building

 

[Bullitt]

Regarding the grid force-charge, I am still waiting on further response/instruction from the manufacturer's firmware team. They are very slow to respond. I am against a wall on what I can test/fix on my own in this case.

Did anyone ever get an answer to the grid force-charge issue? I am also seeing my batteries override the TOU settings at about 20% SOC. I tried lowering the SOC low alarm in each BMS but that does not seem to be what controls the force charge request from the battery. So far as I know, there is no way to set the Sol-ark to prioritize the TOU schedule over a force charge request from the BMS.

 

[marionw]

Did anyone ever get an answer to the grid force-charge issue? I am also seeing my batteries override the TOU settings at about 20% SOC. I tried lowering the SOC low alarm in each BMS but that does not seem to be what controls the force charge request from the battery. So far as I know, there is no way to set the Sol-ark to prioritize the TOU schedule over a force charge request from the BMS.

Did anyone ever get an answer to the grid force-charge issue? I am also seeing my batteries override the TOU settings at about 20% SOC. I tried lowering the SOC low alarm in each BMS but that does not seem to be what controls the force charge request from the battery. So far as I know, there is no way to set the Sol-ark to prioritize the TOU schedule over a force charge request from the BMS.

What protocol are you using between the master BMS and the inverter? CAN or RS485?

How do you know the BMS is sending a "force charge request"

 

[Bullitt]

1. CAN
2. Because the Solark displays "Request Force Charge" on the Li-Batt info tab when the override is happening. If you'd like to see a picture of what it looks like, see post #28 of this thread.

 

[marionw]

1. CAN
2. Because the Solark displays "Request Force Charge" on the Li-Batt info tab when the override is happening. If you'd like to see a picture of what it looks like, see post #28 of this thread.

CAN as the physical port/bus selection. What communications protocol is also selected; i.e. Pylontech, Growatt etc

 

[Bullitt]

The inverter has “BMS Lithium Batt” enabled and set its value to “00”, in accordance with page 29 of the Sol-Ark battery integration guide. I believe that is what dictates the communications protocol.