jimmyge2001
New Member
The title says it all. Will?
We sure do need a video for communication between eg4 6000XP and Lifepower batteries including firmware update, inverter setup/sittings, and cabling.
- Thread starter jimmyge2001
- Start date
Maybe @EG4_Jarrett can help you with this.
EG4_Jarrett
Solar Enthusiast
Let me get with our social media team. See what we can do. Worst case scenario, it'll be me using my phone to show it.
jsmithtx
New Member
And add a LL-S to the mix as well 
EG4_Jarrett
Solar Enthusiast
I haven't forgotten about this post. Just have to stick with the schedule that was already put in place, and work with our video team. We gotchu though. ?And add a LL-S to the mix as well
Last edited:
Roofrunn3r
High Tek Red Neck. Q/T for a Nat'l Resi Company
I see plenty of videos on communication for batteries that have it as an option. What about for Lifepo4 batteries w/out communication? I habent cycled through every communication option yet. But am I stuck running it under Lead acid for now?
FullCircle
New Member
- Joined
- Mar 9, 2022
- Messages
- 20
I had the most bizarre road to getting mixed EG4-LL & Lifepower batteries to communicate with a new 6000xp... Only lead-acid mode would produce AC-Out at first. Flashing the firmwares didn't help. Finally we removed the LL, reducing the bank to just 2 Lifepowers, with all DIP switches down on the primary... and it worked! (After 3 days & 4 SS technicians I was surprised!) Then, leaving the system running, I set the (4-DIP, v2) LL back in service as primary with ID set to 1 (on/front, on/front, on/front, off/rear), cycled that BMS to activate & as soon as I began moving the inverter-to-battery cable from the Lifepower to the LL, the lights went out (no AC-out), until I put it in the LL, when all resumed working! It seems the comms are hypersensitive and intolerant of any AC power production when there's even the briefest of hiccups in inv-bat comms. (Why?)
The final test last night was to power it all down cold & see if the 6000xp could still work well in Li-Ion mode with the LL as primary... and it did. Whew!
In short, contrary to SS's instructions, the newest battery can't be "primary" when mixing with older Lifepowers, until after a Lifepower initiates communications.
Equally puzzling is: once the LL's "CAN protocol" is set to "6-Lux", nothing seems to allow returning to that screen to verify that setting. (This makes working with SS's round-robin of technicians very challenging, cuz each wants to verify what their predecessor did.)
Another oddity is: In defiance of the manual stating batteries' IDs must be sequential, the 1st Lifepower, which is the 1st "slave", works when its DIPs are set to "primary" (all down, for ID 0). I haven't yet tried reverting to all sequential IDs... but its odd that SS's rules & docs seem to often not appy!
So (even after re-flashing) why couldn't the LLv2 initiate comms, when the Lifepower could? Why cant we (SS or the user) verify the LL's protocol?
Lastly, the 6000's display has malformed characters in the battery data part of the screen (region 3 on page 44) . It's impossible to decipher what battery "brand" is selected when you're in 'settings' mode & equally impossible to read live battery data when you're in "run" mode. Could this have anything to do with all of the above?
Hopefully SS & EG4 will retest their recommendations (for mixed battery commissioning procedures) and bullet-proof their documentation.
In the meantime, I hope this helps some of you and/or you can help me understand!!
The final test last night was to power it all down cold & see if the 6000xp could still work well in Li-Ion mode with the LL as primary... and it did. Whew!
In short, contrary to SS's instructions, the newest battery can't be "primary" when mixing with older Lifepowers, until after a Lifepower initiates communications.
Equally puzzling is: once the LL's "CAN protocol" is set to "6-Lux", nothing seems to allow returning to that screen to verify that setting. (This makes working with SS's round-robin of technicians very challenging, cuz each wants to verify what their predecessor did.)
Another oddity is: In defiance of the manual stating batteries' IDs must be sequential, the 1st Lifepower, which is the 1st "slave", works when its DIPs are set to "primary" (all down, for ID 0). I haven't yet tried reverting to all sequential IDs... but its odd that SS's rules & docs seem to often not appy!
So (even after re-flashing) why couldn't the LLv2 initiate comms, when the Lifepower could? Why cant we (SS or the user) verify the LL's protocol?
Lastly, the 6000's display has malformed characters in the battery data part of the screen (region 3 on page 44) . It's impossible to decipher what battery "brand" is selected when you're in 'settings' mode & equally impossible to read live battery data when you're in "run" mode. Could this have anything to do with all of the above?
Hopefully SS & EG4 will retest their recommendations (for mixed battery commissioning procedures) and bullet-proof their documentation.
In the meantime, I hope this helps some of you and/or you can help me understand!!
