So, you DO have a hub?Oh no hub. Sorry I had to set up.
Going to make some cables What battery type do you select in SA still Modbus?I know it's been a few months since there's been activity on this thread, but for anyone still interested I actually got this exact scenario working with the current release (2023-08-16) version of Solar Assistant on my EG4 LL-S batteries. Initially, I saw the exact same behaviour that @crzykidd reported above, and read the same comment on SA's help page that @fmeili1 refers to. Still, I thought I'd get out my RJ45 crimpers, open up BMSTools and see what exactly is being sent on each of the 2 RS485 busses.
The SA team is correct, by default if one of the batteries set to ID1 (i.e. master mode), the battery changes the protocol used and neither BMSTools nor SA can interpret it. You can increment all your battery IDs by 1 as suggested by the SA team, but then your battery bus has no master and your inverter won't detect anything. You can also see that your batteries aren't communicating with each other by the lack any activity on the batt comm ports' amber LEDs.
However, if you connect your 6000XP to the master battery via CAN bus on pins 4/5, and you connect Solar Assistant to the RS485 port via pins 1/2, AND you reconfigure all of your batteries to use the Schneider protocol on their RS485 ports instead of the default EG4 protocol, you can actually have the best of both worlds. I now have my inverter detecting and properly monitoring SOC, capacity, etc via CAN with by battery IDs starting at 1, and SA monitoring each individual pack via RS485.
Cheers,
-A
Yup. I’m still using USB modbus in SA.Going to make some cables What battery type do you select in SA still Modbus?
Thanks. I was just thinking "Enter" = "Return" solved.Nothing's changed as far as I know... are you sure you're holding the right button though? It's the "return" key, not the "enter" key. The second one from the right.
Thank you so much for this. So with the LL-S V4 and the LL V2 Batteries I had to do the following: Couldn't get them to work with just 4/5 on the Battery Coms connections. So had to hook up 1/2 4/5 and that got all 5 batteries (2 LL-S V4 and 3 LL V2) talking to the inverter with the battery set to RS485 Schneider. 6000xp set to EG4 battery. Then after that was working added everything to SA, but only wired pins 1/2 on the RS485 ports to SA.I know it's been a few months since there's been activity on this thread, but for anyone still interested I actually got this exact scenario working with the current release (2023-08-16) version of Solar Assistant on my EG4 LL-S batteries. Initially, I saw the exact same behaviour that @crzykidd reported above, and read the same comment on SA's help page that @fmeili1 refers to. Still, I thought I'd get out my RJ45 crimpers, open up BMSTools and see what exactly is being sent on each of the 2 RS485 busses.
The SA team is correct, by default if one of the batteries set to ID1 (i.e. master mode), the battery changes the protocol used and neither BMSTools nor SA can interpret it. You can increment all your battery IDs by 1 as suggested by the SA team, but then your battery bus has no master and your inverter won't detect anything. You can also see that your batteries aren't communicating with each other by the lack any activity on the batt comm ports' amber LEDs.
However, if you connect your 6000XP to the master battery via CAN bus on pins 4/5, and you connect Solar Assistant to the RS485 port via pins 1/2, AND you reconfigure all of your batteries to use the Schneider protocol on their RS485 ports instead of the default EG4 protocol, you can actually have the best of both worlds. I now have my inverter detecting and properly monitoring SOC, capacity, etc via CAN with by battery IDs starting at 1, and SA monitoring each individual pack via RS485.
Cheers,
-A