EG4 Community Forum

48v LL Battery clus...
 
Notifications
Clear all

48v LL Battery cluster overloading charge amps modbus register

13 Posts
2 Users
0 Reactions
826 Views
SomeJ
Posts: 15
Topic starter
(@somej)
Active Member
Joined: 1 year ago

Hey support, I really need some help with this.  I did more digging and found the latest firmware package for the LL-s units actually have a change log (Z02T18).  It looks like this issues was fixed in firmware version Z02T13.

image

On that same firmware download page for the LL-S there is a firmware labeled multi pack communication. ( https://eg4electronics.com/categories/batteries/eg4-ll-s-48v-100ah-lithium-iron-phosphate-battery/)

image

I downloaded this package and tried it on a battery.  It looks like this firmware version is Z02T12.

I have 48 batteries, 6 of which are the 4dip LL units, 18 are the 6dip LL-v2(maybe some v1 in there, not sure), and 24 are the 6dip LL-S.  I have found that in order for the master battery to query all of the other batteries the firmware for every battery must be on the same version.  It also appears that you can put a V2 firmware on an LL-S unit so, when I had gotten all the LL-S units I had to downgrade them to the latest version that I could find that also had support for the 4dip units, which was Z02T12. 

Per the change log, the firmware that fixes my register overflow issues is Z02T13 which is also the last version listed as supporting the 4dip units per the change log.

 

So... Where can I find a download for this Z02T13 firmware that will fix my issue? I repeat, the firmware for the multi unit link on YOUR website has Z02T12, why not the LAST firmware that supports all models?

Please please please provide a link for the Z02T13 firmware!!!

Reply
EG4 Eric
Posts: 656
(@eg4eric)
Honorable Member
Joined: 12 months ago

As of now, the multipack firmware is the only way to allow all the batteries to communicate with each other.

If you'd like, you can post pictures of the batteries so I can confirm whether you have the LL-V1 model. If there aren't any LL-V1, communication would be possible without the multipack firmware.

Reply
1 Reply
SomeJ
(@somej)
Joined: 1 year ago

Active Member
Posts: 15

@eg4eric 

I posted the pics a few days ago... any progress?   My solar is tuned to produce the most during fall and spring, so I am seeing this register overrun happen on the daily again which in turn throws off all the energy tracking on my system.

 

Reply
SomeJ
Posts: 15
Topic starter
(@somej)
Active Member
Joined: 1 year ago

@eg4eric

This is a 4dip unit.

PXL 20251007 180210176

 

6dip unit, the "cluster master" is one of these.

PXL 20251007 180112758

 

6dip unit.

PXL 20251007 180141429

 

6dip unit, these were labeled as LL-S when purchasing.

PXL 20251007 180235376

 

I do NOT have any Lifepower4 units.  The multi pack firmware package has the firmware for 4 types of units.  LLv1, 4dip LLv2, 6dip LLv2, and Lifepower4; all listed as firmware version Z02T12.  

Per the firmware change logs, firmware version Z02T13 supports v1 and v2 units.  I will also repeat, that I currently have Z02T12 installed on ALL battery packs, even the LL-S units using the 6dip LLv2 firmware, so based on the change log info Z02T13 should be compatible with all of my units as it lists both v1 and v2 as being supported. The firmwares listed as v3 supported do NOT have a 4dip option included in the latest download so I am guessing the last firmware that would support all of my units would be Z02T13. 

I have NOT tried putting a firmware listed for v3 units on the 4dip units as there was no longer a 4 dip and 6dip option listed in the download package so I assumed said firmware would not support the 4dip unit and could possibly brick it.

Z02T13 is the firmware that I need a download link for to fix the mod bus register overflow issue. 

I suspect my 4dip units are actually v2 as they are still functional after putting the v2 4dip firmware on them.  With that said, would the latest firmware support being installed on my 4dip units without bricking them?  If not then I still need a download link for Z02T13.

 

Thanks!

Reply
EG4 Eric
Posts: 656
(@eg4eric)
Honorable Member
Joined: 12 months ago

I apologize for the delayed response. Based on the pictures provided, it appears the first battery is an LL-V2 model with four DIP switches. Unfortunately, we do not currently have the file you’re requesting. However, I will reach out to our battery technician to see if it can be located. Just want to let you know since these are legacy products, there’s a strong possibility the file may no longer be available, but I’ll do my best to obtain it for you.

Reply
3 Replies
SomeJ
(@somej)
Joined: 1 year ago

Active Member
Posts: 15

@eg4eric 

If i make one of the LL-S units the cluster master and put the 2T18 firmware on it, can that version still communicate with the 2T12 firmware that is on all of the v2 units?

I have not had very good luck with mixing firmware versions, but I have not tried 2T18 with an LL-S as the master.  Just trying to think outside the box here.  If an LL-S unit as the master with 2T18 on it can still query all of the units with 2T12 on them, then I would not need the 2T13 firmware.

Reply
EG4 Eric
(@eg4eric)
Joined: 12 months ago

Honorable Member
Posts: 656

@somej 
I would have to double check on that, but you can definitely try! Just make sure you set the LL-s as the master battery and make sure that the DIP switches are set correctly on the rest of the batteries.

Reply
SomeJ
(@somej)
Joined: 1 year ago

Active Member
Posts: 15

@eg4eric 

I did end up trying over the weekend... Put 2T18 on one of the LL-S units and set it to cluster master, set the com proto to Schneider, and change the dips on the old cluster master to another number (rebooting both units to apply the changes).  So 47 of the batteries had 2T12 on them, and the master/LL-S unit had 2T18 on it... The battery com ports for all of the batteries would no longer flash on the cluster, and the Insight Facility only reported a charge max amps of 50 with max discharge of 100, indicating the master battery was not able to query any of the other batteries.  I moved the test LL-S back over to its old dip setting, set the old master back to current master (rebooting both units again), and the Insight Facility then reported max discharge amps of 4700, i downgraded the LL-S back to 2T12, rebooted the master battery and then Insight Facility showed a max discharge amps of 4800. (each battery adds 100amps of max discharge to the cluster total, with 48 batteries that makes for a max discharge amps of 4800, max charge amps is half of the discharge amps so long as the batteries are not near 100%soc).

It looks like a LL-S battery with 2T18 on it can not communicate with any battery that has 2T12 on it.  Which means that I still need this 2T13 firmware to fix the register overflow/overrun issue when charging the cluster with more than 327amps.

Unless your battery engineer has a different solution???

Reply
Page 2 / 2
Share: