• Have you tried out dark mode?! Scroll to the bottom of any page to find a sun or moon icon to turn dark mode on or off!

diy solar

diy solar

EG4 Lifepower4 V2 talking to Solar Assistant?

Garrik

New Member
Joined
May 9, 2020
Messages
35
I have a rack of 6 EG4 Lifepower4 v1 batteries talking to Solar Assistant no problem. Been running for a couple of years now. SA is set to Narada RS485. Batteries are running their original firmware, and are set to addresses 2-7.

I added two Lifepower4 v2 batteries to the stack, and so far, I can't get them to talk to Solar Assistant at all. I started just trying to get SA to talk to one of them by itself, no luck. Set the battery protocol switches to 5 and 6 down, all others up (which is supposed to be "simple mode"). No joy.

If you have done this, I would love to hear how you did it. Thanks!
 
I have a rack of 6 EG4 Lifepower4 v1 batteries talking to Solar Assistant no problem. Been running for a couple of years now. SA is set to Narada RS485. Batteries are running their original firmware, and are set to addresses 2-7.

I added two Lifepower4 v2 batteries to the stack, and so far, I can't get them to talk to Solar Assistant at all. I started just trying to get SA to talk to one of them by itself, no luck. Set the battery protocol switches to 5 and 6 down, all others up (which is supposed to be "simple mode"). No joy.

If you have done this, I would love to hear how you did it. Thanks!
First thing you need to do is upgrade the firmware on the V1 batteries. They have to be "multi-pack" version. Now a question: which port on the battery are you using to connect to the V2 with Solar Assistant? The V2 supports different protocols. You also need a custom cable between the V2 and the first V1.
 
Appreciate the response, thank you.

Right now, I am not even trying to get the V1's and V2's to talk to each other - just trying to get the V2's to talk to Solar Assistant.

But when I do get to the point of trying to get the V2's and V1's to talk:

- I have built the proper custom cable (missing pins 3 and 6, or only pins 7 and 8, have heard different suggestions from different people at Signature Solar).
- I have the multipack firmware ready to install on the V1's, and the latest firmware and multipack for the V2's, but am not going to touch the firmware on my working setup until I have the V2's talking to SA.

I tried both the RS485 port and the "Battery" port on the V2 (connecting to SA). Right now, I would really just love to hear from someone else who has got a V2 battery talking to SA so that I can hear/see their exact config/setup...
 
Appreciate the response, thank you.

Right now, I am not even trying to get the V1's and V2's to talk to each other - just trying to get the V2's to talk to Solar Assistant.

But when I do get to the point of trying to get the V2's and V1's to talk:

- I have built the proper custom cable (missing pins 3 and 6, or only pins 7 and 8, have heard different suggestions from different people at Signature Solar).
- I have the multipack firmware ready to install on the V1's, and the latest firmware and multipack for the V2's, but am not going to touch the firmware on my working setup until I have the V2's talking to SA.

I tried both the RS485 port and the "Battery" port on the V2 (connecting to SA). Right now, I would really just love to hear from someone else who has got a V2 battery talking to SA so that I can hear/see their exact config/setup...
Not able to provide real-world info just yet. I have a V2 arriving tomorrow as a warranty replacement so I'll be in the same boat. I have five V1 batteries in addition to the V2. The V1s are running V3.37 which has the multi-pack features. I think the current version is 3.4.
 
Ok, let's continue to compare notes please. I will experiment more the next time I am up there - likely later this week.
 
Ok, let's continue to compare notes please. I will experiment more the next time I am up there - likely later this week.
I sent a message over on the SA website asking for input on how to accomplish the connection.

Noticed for the LL battery you need to use MODBUS RS485 to talk to the battery...maybe change this:

1735493921185.png
 
Another question...what cable are you trying to use? Seems there is a specific one for battery to inverter that comes with the V2 and may be different.
 
I am using the same cable that I use between my SA box and my V1 batteries, which is just a pin 7 and 8 RS485 cable.

Solar Assistant doesn't mimic an inverter as best I can tell, it mimics a battery...
 
I am using the same cable that I use between my SA box and my V1 batteries, which is just a pin 7 and 8 RS485 cable.

Solar Assistant doesn't mimic an inverter as best I can tell, it mimics a battery...
Did you set the battery ID to 1? Seems that is the "host" battery.

9.3 PROTOCOL CHANGE/SELECTION PROCEDURE
REMINDER:
Only the host battery (Address 1) needs the inverter protocol to be set to communicate with
the inverter.
 
I'm in the same boat here, trying to get my v2 to talk to solar assistant.
Any luck?
Not so far. Finally got the V2 in the rack and connected communication cables. If I connect SA to the last battery I can still see all V1s in SA, but the V2 doesn’t show.

Just getting started.
 
The EG4 LifePower4 V1 batteries employ two separate RS485 busses in the two RJ45 jacks. Pins 1&2 running at 9600 baud are used by the BMS_Test software, Solar Assistant (Narada Protocol) or BMS To Inverter closed loop communications. Pins 7&8 running at 19200 baud are used by the "Master" BMS to pull data from the other batteries. I am assuming the EG4 LifePower4 V2 maintain this configuration for the Battery to Battery right two RJ45 jacks.

The EG4 LifePower4 V2 provided a separate RJ485 and CAN connection for the inverter so I suspect you can use pins 1&2 on the Battery To Battery RJ45 jacks for Solar Assistant.

See:

Issue:
• When communicating an EG4 Lifepower4 V2 with a EG4 Lifepower4 V1, a Rapid Shutdown Protection will occur when using the 1-foot CAT5 (T-568B) that is currently provided due to the EG4 Lifepower4 V2 utilizing the Battery-Com RJ45 Pins (3, 6) as its normally open circuit for
the rapid shutdown. Resolution:
• To resolve this issue, the 1-foot patch cable will need to be re-pinned on only one side of the
RJ45 as Pins (7,8). This will then bypass the EG4 Lifepower4 V2 rapid shutdown circuit and only allow the EG4 Lifepower4 V2 and EG4 Lifepower4 V1 to communicate correctly.
• This will ONLY have to be done x1 time between the first connection of the EG4 Lifepower4 V2 and the EG4 Lifepower4 V1. (Examples provided below)
• If needing a cable provided, please reach out to support@eg4electronics.com to haveone shipped

@EG4TechSolutionsTeam
 
Very helpful Marion. Is there any way to know if the V2 batteries are talking to the V1 batteries?

I have everything set up as you describe above, including the proper cable. But I can't tell if it is working lol
 
I don't have any V2, just six V1. Does Solar Assistant see all batteries when using pins 1&2 connected to an RS485 to USB converter and the Battery To Battery jacks (most likely the only open one would be on the bottom/last V1)

Don't know what you use to monitor your inverter but that software should show the entire battery stack/bank as one battery and the total capacity should be equal to all the batteries.

Use the BMS_Test software for the V1 which would be connected to the a V1 RJ45 jack using pins 1&2. Does the BMS_Test software show all batteries (V1 and V2)
 
Does Solar Assistant see all batteries when using pins 1&2 connected to an RS485 to USB converter and the Battery To Battery jacks (most likely the only open one would be on the bottom/last V1)

Yes, it sees the entire stack of V1 batteries.

Use the BMS_Test software for the V1 which would be connected to the a V1 RJ45 jack using pins 1&2. Does the BMS_Test software show all batteries (V1 and V2)

No. But the V1's are running at 19200 and the V2's at 9600, so that is never going to work :confused:
 
Yes, it sees the entire stack of V1 batteries.



No. But the V1's are running at 19200 and the V2's at 9600, so that is never going to work :confused:
Normally the V1 on pins 1&2 run at 9600.
Is the RS485 to USB using pins 1&2, sounds like it is using pins 7&8. The BMS_Test software will communicate with the V1 on pins 7&8 but there will be a conflict on the RS485 bus if you have a battery set as Master.

Did you fabricate the RS485 to USB cable or is it one you purchased.

Hold the RJ45 connector with the pins up and the locking tab away from you. Pins 1&2 will be on the left side and pins 7&8 will be on the right side. Signature Solar and other sell two different cables, one uses pins 1&2 and the other uses pins 7&8
 
Normally the V1 on pins 1&2 run at 9600.

"Normally" running which firmware?

My V1's used to run at 9600. Then I upgraded them to the latest firmware, 3.37 is what it shows in BMSTest, and now they are at 19200 baud.

Everything else stayed the same - same cable, same connector, etc.

I will check my cable when I am back up there Tuesday. I bought the cable that I am using.
 
Last edited:
"Normally" running which firmware?

My V1's used to run at 9600. Then I upgraded them to the latest firmware, 3.37 is what it shows in BMSTest, and now they are at 19200 baud.

Everything else stayed the same - same cable, same connector, etc.

I will check my cable when I am back up there Tuesday. I bought the cable that I am using.
V3.37 and V3.40 did bump the Pins 7&8 bus to 19200 as this allowed the "Master" to collect data faster. This was also required as the EG4 Communications Hub Battery bus runs at 19200. Pins 1&2 remained at 9600. It appears you are connecting to the V1 on pins 7&8 if you have to run the serial port at 19200. If the V2 is communicating with the V1 in the pins 7&8 bus then the BMS_Test software and Solar Assistant will have connection issues as you can only have one "Master" on an RS485 bus. Both BMS_Test and Solar Assistant are Masters. BMS_Test and Solar Assistant can communicate with the V1 on pins 7&8 running at 19200 baud but there will be communications errors if there is a Master BMS using the bus as well.
 
Hmmm, ok.

I will make up a pins 1 and 2 cable over the weekend and try that when I get up there Tuesday. Thanks!
 
Just curious what others have found regarding BMS TOOLS vs BMS TEST? According to the manual for the V2, it works with tools. I've not been able to connect to the V2 using the Test software. Also trying to determine what firmware is on the V2. With the Tools package, seems to be Z02T04.
 
Z02T05 is the latest for the V2 batteries I think. Mine also shipped with 04. I upgraded them easily using the upgrade tool.

Test -> V1, Tools -> V2 has been my experience.
 
We can definitely assist with connecting the LifePower4 V2 to the LifePower4 V1 if you still need it!

At the moment the only way to see if they are communicating is when you connect the batteries to the inverter, it will display the total Ah, which should match the capacity of your battery bank.
 
We can definitely assist with connecting the LifePower4 V2 to the LifePower4 V1 if you still need it!

At the moment the only way to see if they are communicating is when you connect the batteries to the inverter, it will display the total Ah, which should match the capacity of your battery bank.
Did the V2 continue the same wiring and protocol as the V1 on the two Battery To Battery RJ45 ports. In other words does the V2 (like the V1) support two independent RS485 busses on the Battery To Battery RJ45 ports like the V1.

The V1 uses pins 1&2 as one RS485 bus and pins 7&8 as a second independent RS485 bus.

I am hoping the V2 is just a V1 that also incorporates the EG4 Communications Hub and that the V2 Battery To Battery RJ45 jacks will allow for monitoring using pins 1&2
 
Ok, here is my latest update.

I verified that my pre-existing cable was a pin 7&8 cable.

I built a new pin 1&2 cable and brought it to the site.

Using that cable (pin 1&2) at 9600 baud (it also worked at 19200) I was able to run Get Boot Information successfully the first time using BMS Test 2.7.8. Without disconnecting the battery from the DC bus bar. Without setting the battery address to zero. Just plugged in, verified that BMS Test was reading data correctly, went to the update page, set the address to the battery address (two was my first one that I tried), ran Get Boot Info, it worked (0207), ran the update to multipack, that worked. Went on to each battery in sequence without any trouble, using their existing addresses.

Then I verified that Solar Assistant will still talk to the 6 V1 batteries, and it does. Using either cable (so poins 1&2 and 7&8, both work). BUT still only using Narada protocol. It will not connect to the V1 batteries using MODBUS protocol.

Then I went back to the V2 batteries. I cannot get them to talk on their "Battery-Comm" ports at all. Not on either pair of pins, not at any baud rate, not with either protocol.

I can connect to the V2 batteries using either BMS Tools or Solar Assistant (MODBUS) on the RS485 port.

So right now, I am nowhere on my original goal of getting the V1 and V2 batteries talking to Solar Assistant.
 

diy solar

diy solar
Back
Top