diy solar

diy solar

LV6548 and SOK server rack battery communication warning 61

With help from Eric S. (not sure if forum member or not), I think I found why it works in my shop and not elsewhere. I am testing a fix on Monday (Once Amazon delivers my parts!) and will report back with results.
Ahh awaiting that Amazonian magic pixie dust eh?
Thanks for you support on all of this !
 
I have exactly the same issue with my a week old MPP LV6548 (watts247) and two Jakiper Pro batts (also delivered last week) I followed LithiumSolar's youtube video to set it up but got the same issue as many others in this thread. What I noticed and no one else mentioned here is the field "Inverter protocol" never gets filled with the currently set value it just stays empty no matter what I do. When I select pylon 485 from the dropdown list it states "Successfully updated" and the battery icon on the inverter starts blinking for a few seconds then error 61, low batt error, etc.
 
@fanchazstic @Scotts954 please send me your order numbers by PM as soon as possible so I can express-ship something to you.

@PlaneBatteries I know who you are so I've got stuff going in the mail today.

When you three get the part, test it and let me know if there is any changes.

I also have the firmware files for the inverter successfully running in my shop that we can try, if the new part doesn't work.
 
Hi all, I've been working on this issue w/ @HighTechLab. Props to him for really enthusiastic customer support.

My inverter is a Sun Gold SP6548. My understanding is that it is a relabel of the MPP, so presumably there is a shared root cause.

Here's a brief recap of my exploration:

At first I thought the battery was not configured for the correct protocol. @HighTechLab helped me out with this, but the configuration turned out to be correct. Also tested with a replacement cable, no dice.

So then I started digging. I made some breakout cables and inspected the signals with an oscope, and man, dirty signals. Lots of switching transients and just plain noisy on the inverter side (the SOK side was clean BTW). Figure maybe it was a data corruption issue. Played with terminations and filtering, cleaned up a little, but still no love.

Then I attached a RS-485 adapter to the line to monitor. Turns out the data seemed okay. Yay for differential signaling! Even checked all the packet checksums and they were all good. I also confirmed that the battery was indeed responding to query/commands from the inverter. Conclusion: it is not a data link integrity issue.

So, using protocol definitions found on the web, I started digging into the messages. The inverter scans for and queries the battery for its protocol version (CID2=4F) several times and then issues commands that are not in my documentation, but the battery responds. E.g. CID2 = 61, 62, 63. After several seconds of this, the inverter throws comms (61) error. Sometimes (I don't think every time, but I may be missing it) it throws a "low battery" (04) error first.

My current hypothesis is that the inverter and BMS have incompatible protocol implementations. Unfortunately, I don't have any documentation for what the messages *should* be, so it's hard to make more progress from here. I would suspect the Sun Gold was in error due to the undocumented command IDs, but the battery does respond, so... *shrug*

I'll be waiting to hear from Sun Gold support. Hopefully a firmware upgrade can fix this.

@Scotts954, did you ever get any response from Sun Gold?

If anyone has anymore information about the Pylontech protocol, please share!

A data capture for the interested:

~0002464F0000FD9A
~200246000000FDB2
~0002464F0000FD9A
~200246000000FDB2
~0002464F0000FD9A
~200246000000FDB2
~20024661E00202FD32
~200246008062CFCDFF8E510001000164640CFA000F0CF900100BB50BB900020BB200040BC30BC300010BC300010BC20BC200010BC20001E897
~20024661E00202FD32
~200246008062CFCDFF8E510001000164640CFA000F0CF900100BB50BB900020BB200040BC30BC300010BC300010BC20BC200010BC20001E897
~20024661E00202FD32
~200246008062CFCDFF8E510001000164640CFA000F0CF900100BB50BB900020BB200040BC30BC300010BC300010BC20BC200010BC20001E897
~20024662E00202FD31
~20024663E00202FD30
~20024600D012E100AF0003B603B6C0F9B5
~20024661E00202FD32
~200246008062CFCDFF8E510001000164640CFA000F0CF900100BB50BB900020BB200040BC30BC300010BC300010BC20BC200010BC20001E897
~20024662E00202FD31
~20024663E00202FD30
~20024600D012E100AF0003B603B6C0F9B5
~20024661E00202FD32
~200246008062CFCCFF8E510001000164640CFA000F0CF900100BB50BB900020BB200040BC30BC300010BC300010BC20BC200010BC20001E898
~20024662E00202FD31
~20024600800800000000FC22
~20024663E00202FD30
~20024600D012E100AF0003B603B6C0F9B5
~20024661E00202FD32
~200246008062CFCCFF8D510001000164640CFA000F0CF900100BB50BB900020BB200040BC30BC300010BC300010BC20BC200010BC20001E899
~20024662E00202FD31
~20024600800800000000FC22
~20024663E00202FD30
~20024600D012E100AF0003B603B6C0F9B5
~20024661E00202FD32
~200246008062CFCCFF8D510001000164640CFA000F0CF900100BB50BB900020BB200040BC30BC300010BC300010BC20BC200010BC20001E899
~20024662E00202FD31
~20024600800800000000FC22
~20024663E00202FD30
~20024600D012E100AF0003B603B6C0F9B5
<repeats>
 
Use at your own risk:

I don't totally recommend this for @esch or anyone using a non MPP branded unit, but I have the firmware files available that match what is working on my unit. I don't have a Sungold/EG4 inverter to test installing this firmware on, otherwise I would do a test before sharing this information.

Firmware w/ instruction PDF contained: https://www.currentconnected.com/wp-content/uploads/2022/06/LV6548-Fimrware-SOK-Working.zip

Not sure if this firmware can be loaded on non MPP-branded units, but you can try at your own risk (but do note that firmware update failures can brick your inverter).
 
Use at your own risk:

I don't totally recommend this for @esch or anyone using a non MPP branded unit, but I have the firmware files available that match what is working on my unit. I don't have a Sungold/EG4 inverter to test installing this firmware on, otherwise I would do a test before sharing this information.

Firmware w/ instruction PDF contained: https://www.currentconnected.com/wp-content/uploads/2022/06/LV6548-Fimrware-SOK-Working.zip

Not sure if this firmware can be loaded on non MPP-branded units, but you can try at your own risk (but do note that firmware update failures can brick your inverter).
@HighTechLab I tried the new cable you sent out but no dice on that, same behavior as before. I then tried flashing this firmware, but when I tried to flash the firmware I see the UPG YES pop up on the LCD, but then when it goes away the firmware is still at 69.02, not 45.07. I then tried to flash the LCD panel, but I get an error writing flash:

Capture.PNG

I've tried two different RS232 usb adapters (including one from Current Connected) and both fail to write. The flash was erased and won't write so the LCD is blank and not working at all now. Do you have access to the original 112.14 version my panel was running?
 
I will add that I have been having the same issues between my single EG4 6500EX-48 and my rack of 4 SK48v100's.

I used the protocol editor to verify and set all batteries to Pylon 485. I have tried the cable sent from Current Connected (verified pinout) and made my own following the pinouts from the SOK manual site. I have also noticed that communication does seem to work as it begins to properly report the battery power level (full) and it changes some of my settings. When not connected my EG4 6500EX-48 is miss reporting the actual battery power saying it's around 50% when in fact the batteries are all about 99%.

I have watched every YouTube video out there relating to this (Will, Signature Solar, Current Connected, LithiumSolar, Jakiper, etc) and I know I am doing everything correctly and have quadruple checked everything at this point.

I will also note that one of my 3 SK48v100 batteries is doing the same thing that savaga reported in that while I set it to Pylon 485 it never actually shows it under "Inverter Protocol" like my other 3 did. (Don't really think this is related to the Error 61 though)

WatchPower reports my EG4 6500EX-48 versions as follows:
1656609304994.png
Main CPU version: 00079.02
Remote Panel CPU version: 0061.00
BLE CPU version: 0000.00
 
I have exactly the same issue with my a week old MPP LV6548 (watts247) and two Jakiper Pro batts (also delivered last week) I followed LithiumSolar's youtube video to set it up but got the same issue as many others in this thread. What I noticed and no one else mentioned here is the field "Inverter protocol" never gets filled with the currently set value it just stays empty no matter what I do. When I select pylon 485 from the dropdown list it states "Successfully updated" and the battery icon on the inverter starts blinking for a few seconds then error 61, low batt error, etc.
Just wanted to chime in and report that 1 out of my 4 SK48v100's is doing exactly what you stated here. I set it to Pylon 485 it reports successful but never lists it under the Inverter Protocol field. The other 3 all report under Inverter Protocol field.

I have the battery with that issue on address 4 and have eliminated it from the error 61 by only testing with my first two batteries so I do not believe it is related. Regardless, it does concern me that it does not perform the same as my other 3.
 
I've had a few hours session with jakiper support and their engineers yesterday. Gave them access to my setup through teamviewer. They verified everything - cables, pinouts, settings, addresses etc, tried different pbmstools versions. I let them try it on two different inverters and two different batteries. Eventually they contacted with LV6548 OEM manufacturer and they said it could be inverter f/w issue and provided new firmware. I haven't tested it yet and now after @fanchazstic post regarding his re-flashing failure experience I'm afraid to give it a try. The firmware version is 112.19. Currently both of my inverters are running 112.14. I'm attaching it for the ones who brave enough to give it a go. Again: THIS IS NOT A MPPSOLAR OFFICIAL F\W it's OEM manufacturer provided f\w.

Update: Jakiper eng said the "inverter protocol" doesn't appear in the upper field anymore and this is totally normal.
2Update: Please read the thread to the end before you flash this file. It might not work and you'll brick you inverter.
 

Attachments

  • Remote Panel_Reflash_MCU(112.19).rar
    862.7 KB · Views: 46
Last edited:
I've had a few hours session with jakiper support and their engineers yesterday. Gave them access to my setup through teamviewer. They verified everything - cables, pinouts, settings, addresses etc, tried different pbmstools versions. I let them try it on two different inverters and two different batteries. Eventually they contacted with LV6548 OEM manufacturer and they said it could be inverter f/w issue and provided new firmware. I haven't tested it yet and now after @fanchazstic post regarding his re-flashing failure experience I'm afraid to give it a try. The firmware version is 112.19. Currently both of my inverters are running 112.14. I'm attaching it for the ones who brave enough to give it a go. Again: THIS IS NOT A MPPSOLAR OFFICIAL F\W it's OEM manufacturer provided f\w.
I'll give that a go, right now I have no working LCD so ¯\_(ツ)_/¯ it can't be worse haha

Edit: also just to confirm, that firmware came from voltronic?
 
@savaga I just tried flashing that firmware and I'm still getting the "Write fail!" message. It could be an issue with my unit but yeah I wouldn't recommend anyone else try flashing the LCD panel firmware or you risk ending up in the situation I'm in now
 
That's sad. I'm really sorry about this. Was going to flash mine but decided to check the forum first in case of some new info. Fortunately saw your post and put in on hold. My equipment isn't in production but I think I should contact watts247 first for approval

Update: @fanchazstic, I wonder if downgrade isn't possible here? Is main unit latest f\w available? So you can upgrade your main f/w then LCD
 
Last edited:
Yeah definitely good call to hold off. No worries, I'm the one who decided to try flashing that firmware. Someone has to be the guinea pig. I just emailed watts247 to see if they have any idea of how to fix my LCD. I'll let you know what they say when I hear back.
 
I contacted watts247 too and updated my post with attached f\w with additional warning so other people don't make anything bad
 
Update: @fanchazstic, I wonder if downgrade isn't possible here? Is main unit latest f\w available? So you can upgrade your main f/w then LCD
At least for the panel I don't think up/downgrade matters since it erases whatever is on there first. I think there's definitely a possibility that it won't let you downgrade the main unit firmware. That was kind of my thought as well with how it didn't change at all. But I think that main unit firmware won't matter much for the communication issues. I think that's primarily handled in the LCD box/firmware.
 
I have the Rich units so no bueno for me with the firmware. Looks like it's something I wouldn't want to try anyways.
I reached out to the tech email at rich solo asking about firmware .... crickets
 
@fanchazstic Could you confirm you were updating DSP with the 112.19 firmware? I have carefully re-read chat with jakiper and now a bit confused - they said it's MCU f/w.
 

Attachments

  • Screen Shot 2022-07-01 at 12.04.42 PM.png
    Screen Shot 2022-07-01 at 12.04.42 PM.png
    42.6 KB · Views: 12
@fanchazstic Could you confirm you were updating DSP with the 112.19 firmware? I have carefully re-read chat with jakiper and now a bit confused - they said it's MCU f/w.
I was updating the MCU firmware not DSP. The instructions PDF states to click the Update MCU button. I actually tried clicking the Update DSP button one time but it gave an error about the hex not being found.

Also as a bit of an update on my remote panel situation, I heard back from watts247 and they recommended that I contact MPP directly. I emailed them but it was already late Friday night in Taiwan so I'm not expecting to hear back until sometime next week.
 
To those who have SOK battery and their Inverter Protocol doesn't show the current one in the software, I suggest doing this one:

In PBMS Tools 2.5 folder, go to:

Config/XML/..

Rename InverterList.xml to InverterList.bak (for backup, or you could just copy paste for backup purposes)

Then,

Rename InverterList_default.xml to InverterList.xml

Then restart PBMS Tools 2.5.

Then re-do the video tutorial on how to change Inverter Protocol to Pylon RS485.

Disclaimer: DO AT YOUR OWN RISK. (though I believe there is no fireworks in this suggestion)
 
Back
Top