diy solar

diy solar

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

Try paceadmin for the Administrator Password.

The SOKTools I am using I downloaded from https://www.currentconnected.com/sk48v100-owner-operators-manual/#commintro
I downloaded the same, version 22 because 23 won't open, it gives me the following error:

Screenshot 2024-03-02 at 4.29.26 PM.png

I appreciate the password, but the only place I can see to input a password has a "change" button next to it, when I click that button, whether a password is input or not I get a change password dialog box and it doesn't accept paceadmin as the 'old password'. Either way, I don't want to change the password, I'd imagine I just want to 'unlock' the ability to write changes to the BMS. The 'write' button is grayed out.

This is the only page I see that has anything to do with password from what I can tell, bottom right:
Screenshot 2024-03-02 at 4.25.47 PM.png
 
Are you running windows or mac? I am running on windows 10. Can't run from the zip file, must extract it to a folder.

Open the zip file and extract to to a folder. The SOK Tools will be in the subfolder "Program"

Below is what my screen looks like. Enter paceadmin for the password. No need to hit enter, once you enter the "n" the software will unlock the addition functions and the Password textbox will turn green

SOK Tools


Screenshot 2024-03-02 195008.png
 
Are you running windows or mac? I am running on windows 10. Can't run from the zip file, must extract it to a folder.

Open the zip file and extract to to a folder. The SOK Tools will be in the subfolder "Program"

Below is what my screen looks like. Enter paceadmin for the password. No need to hit enter, once you enter the "n" the software will unlock the addition functions and the Password textbox will turn green

SOK Tools


View attachment 199601
I'm on a Mac running Windows 11, even when downloading your link I have the same net result. It's been unzipped etc
 
Try copying (copy don't move) all the ".dll" files in the Program\Config\ZL folder into the same folder as SOKTools.exe
 
Try copying (copy don't move) all the ".dll" files in the Program\Config\ZL folder into the same folder as SOKTools.exe
Much closer, I get an exception error and it's all in Chinese with no way to swap to English. I'll snag a windows computer tonight and get it sorted.. Stupid Parallels....

Screenshot 2024-03-02 at 5.51.11 PM.png
 
In the \Config\UpperDB folder there is a file Upper.db. Rename this file to Upper.db.save

Copy the attached file to the same folder and rename it Upper.db

There is a field in this database that sets the language. In this file it is set to English.

Also in the \Config\ZL\10950_x86 there is a file SQLite.Interop.dll. Copy it to the same folder as the SOKTool.exe file.

in the \Config\Log folder there might be a text file(s) that would give you a clue as to what the error is.
 

Attachments

  • Upper.zip
    133 KB · Views: 1
Last edited:
In the \Config\UpperDB folder there is a file Upper.db. Rename this file to Upper.db.save

Copy the attached file to the same folder and rename it Upper.db

There is a field in this database that sets the language. In this file it is set to English.

Also in the \Config\ZL\10950_x86 there is a file SQLite.Interop.dll. Copy it to the same folder as the SOKTool.exe file.

in the \Config\Log folder there might be a text file(s) that would give you a clue as to what the error is.
I sincerely appreciate the info, I’ll do that tomorrow on my Mac so I don’t have to snag a windows laptop in the future.

Just got home from a dinner and was able to make the changes, I’m now working to charge the batteries back up with the new settings in effect on pack #2. Hopefully that change has a real world effect.

It’s a good night to leave the batteries at 100%, it’s a full on blizzard outside.
 
I sincerely appreciate the info, I’ll do that tomorrow on my Mac so I don’t have to snag a windows laptop in the future.

Just got home from a dinner and was able to make the changes, I’m now working to charge the batteries back up with the new settings in effect on pack #2. Hopefully that change has a real world effect.

It’s a good night to leave the batteries at 100%, it’s a full on blizzard outside.
Try moving SQLite.Interop.dll into the same folder as SOKTools.exe. I am thinking for some reason you need all the dynamic link libraries (dll) in the same folder as the executable SOKTools.exe.

Ensure the \Config folder is a subfolder to the one SOKTool.exe is installed is as the software needs to load/access data in the subfolders
 
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.
 
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.

IMG_7805.png
 
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..
 
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.
 
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
 
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
 
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.
 
@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?
 
Updates?

Looks like Elvis has left the building
 
Last edited:
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.
 
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"
 
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.
 
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
 
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.
 

diy solar

diy solar
Back
Top