HAB to Sol-Arc Comm Settings?

[Gubbool]

Has anyone been successful getting KiloVault’s HAB to communicate with a Sol-Ark inverter? (Directly - just using settings & cable)

The latest response from Kilovault via Alt-E states that comm does not work.

I have found several conflicting settings for the HAB, the Sol-Ark, and even the HAB IT app.

 

[CorkyL]

Have you gotten an answer to this? I have the same combo- and have a comm issue too. trying to get it fixed. Did you go with the 485 cable to the Solark or did you keep it canbus?

 

[budgetsolarinstall]

I have got the same response from HAB support via altE. Same issue.

I do know that (atleast to the best of my knowledge), the modbus port on the HAB connects to the Sol Ark and not canbus. Don’t take my word for it, but that is the conclusion after a detailed analysis of both systems and conflicting/ wrong information provided.

In this scenario, you have to configure the battery settings manually to keep its health.

Let me know if the issue gets resolved. No luck here, yet.

 

[networksguy]

I have a Sol-Ark 15k with two Kilovault 7.5 HABs. Installed Aug 2022 and they WERE communicting, closed loop, until a Kilovault firmware update on Dec 5th 2023.

During the orginal install the provided RS-485 cable was too short. Using a cable tester, I determined the 8 pin cable is just pin1 through 6, straight through , so I used a longer standard Ethernet cable in it's place, and it worked.

In Nov 2023, I had a few Sol-Ark glitches so they updated the firmware and recomended I also have the Kilovault BMS firmware updated.

Kilovault BMS
Old ver // New ver.
Wi-FI ver 1.0.9 // 1.09
MCU1 ver 0.1.15 // 0.1.15
MCU2 ver 1.0.14 // 1.0.26

Kilovault support (Alt-E) has told me I need a new cable and to connect Kilovault pin 1/2 to Sol-Ark Pins 4-5

The cable that was included with the batteries is actually not the correct cable for the 15k Sol-Ark. The pin out needs to be changed for the cable and the included cable is probably not going to be the best option.

The Sol-Ark 15K uses Pins 4 and 5 (Can Hi and CAN Lo)
our HAB uses Pins 1 and 2 (Inverter Comms)

Really, a firmware update, and I neeed a new cable? I went ahead and made a custom cable and it still doen't work.

So, does any one have Sol-Ark to Kilovault closed loop working? If so, what cable pin out are you using and what firmware version do you have?

 

[RickEV]

Dont know if you were able to solve your issue
As of this post was able to connect both the Solark-12k latest firmware (6222) and a master Kilovault HAB (MCU2 ver 1.0.14) with comms by using protocol 5 on the Solark-12k and protocol 2 on the HAB.
Those where from an old post around here.
The only problem I am seeing, on the Solark I am only reading the master battery and not the 2 other HABs. That should be not problem when charging but won't know until further testing.

 

[networksguy]

I resolved it back in February for my 15K.

It requiered a new custom cable and moving the cable from MODBUS port to CANBUS on the Kilovault.
Closed loop works perfectly now.

Date: Thu, Feb 29, 2024 at 6:05 PM Subject: Re: [## 163346 ##] 15k to Kilovault closed loop To: <support@sol-ark.com> Cc: Tech Support <ts@altestore.com> I FINALLY have Closed Loop working again! The final piece was a new custom cable; 8 pin connector on each end with just pins 4 and 5 swapped end to end. No other wires connected. According to manuals (HAB V4 series 5.1, Sol-Ark 15K April 18th, 2022) Kilovault CANBUS port, Pin 4 [CANL] to Sol-Ark "Combined RS-485 and CANBus" port Pin 5 [CAN Low] and Kilovault CANBUS port, Pin 5 [CANH] to "Sol-Ark Combined RS-485 and CANBus" port Pin 4 [CAN High] Sol-Ark Battery setting: Lithium Bat 00 and HABiT app "Inverter Protocol setting" 0010 I can't believe that it took Kilovault support almost 3 months to tell me they changed to the CANBUS port from the MODBUS port for inverter communications.

 

[RickEV]

I resolved it back in February for my 15K.

It requiered a new custom cable and moving the cable from MODBUS port to CANBUS on the Kilovault.
Closed loop works perfectly now.

Date: Thu, Feb 29, 2024 at 6:05 PM Subject: Re: [## 163346 ##] 15k to Kilovault closed loop To: <support@sol-ark.com> Cc: Tech Support <ts@altestore.com> I FINALLY have Closed Loop working again! The final piece was a new custom cable; 8 pin connector on each end with just pins 4 and 5 swapped end to end. No other wires connected. According to manuals (HAB V4 series 5.1, Sol-Ark 15K April 18th, 2022) Kilovault CANBUS port, Pin 4 [CANL] to Sol-Ark "Combined RS-485 and CANBus" port Pin 5 [CAN Low] and Kilovault CANBUS port, Pin 5 [CANH] to "Sol-Ark Combined RS-485 and CANBus" port Pin 4 [CAN High] Sol-Ark Battery setting: Lithium Bat 00 and HABiT app "Inverter Protocol setting" 0010 I can't believe that it took Kilovault support almost 3 months to tell me they changed to the CANBUS port from the MODBUS port for inverter communications.

Very valuable data Was reading manuals all over from both Sol-ark and Kilovault had my suspicions for the pinout but it varied between documents from Kilovault and had doubts. This will move comm from modbus to canbus and hopefully the solark and Kilovault will talk better with each. Thank you for sharing this information.
Edit: Reading it closely, I thought The pin was added on the modbus port on the kilovault when the firmware was updated, and not the canbus port itself. It will be fun rewiring battery comms first.
Can you share a sol-ark comm lithium data screen ? Would really appreciate it.

 

[networksguy]

Better late then never...

 

[plutoz]

HABiT app "Inverter Protocol setting" 0010

I don't seem to be able to change the Inverter Protocol Setting. It just keeps saying 'Sent failed' I guess you didn't have this issue? I'm stuck at 0002 (default I guess?)

I also have the Kilovault BMS firmware updated.

Kilovault BMS
Old ver // New ver.
Wi-FI ver 1.0.9 // 1.09
MCU1 ver 0.1.15 // 0.1.15
MCU2 ver 1.0.14 // 1.0.26

My MCU1 is 0.1.9 - when I click on it, it says 'Latest version already'
MCU2 is 1.0.13 and it says the same. Obviously not true based on your versions. How do you upgrade the firmware, does it have to be pushed out by Kilovault / altE?

 

[plutoz]

Tel:+86-755-2765 1888
E-Mail: support@topbandbattery.com

I was able to get the latest firmware pushed out to my HAB by contacting the OEM TopBrand at the email address posted in this thread (quoted above). It involved deleting the battery from the HABiT app and adding it to the TopBrand app called "Lithium Battery" found in the iOS app store but it isn't available on Google Play for Android, they sent me a link to download an APK file but I chose not to install it on my device. Anyway after I added it to their app and provided them with the serial number the technician at TopBrand (located in China) was able to push out the same version that networksguy listed above. Strangely after it finished upgrading the battery showed 'Offline' in the TopBrand app and I wasn't able to re-add it (got an error about the QR code being incorrect) but I was able to add it back into the HABiT app which is still working for me, although with an annoying habit of logging me out constantly.

Better late then never...

Curious if you are still using the closed loop networksguy? I noticed some weird things with mine, such as it ignoring the limits I had set such as 50A for charging and it also ignored the wattage limit I had set for charging under ToU on the SolArk. I went back to Batt V and it seems to be behaving a little bit better.

 

[networksguy]

I don't have the Kilovault batteries any more. I wanted to increase my capapticy but they are out of business.
I replaced them with 8 x Pytes v5.

 

[budgetsolarinstall]

What did you do with the old KiloVault?