Most reacted posts

Unfortunately, I have had no success on this. So far my LL-S won't communicate to the "v1" LifePower4. I have a thread open on this issue.

I was using the cable SS ships, which is pinned on 1&2, to communicate between SA and the battery. The inverter is communicating on the CAN port of the first LL-S battery. But as you've noted, maybe it is also on 1&2? I'd have to open the inverter up and see what is pinned on that cable.

That port is explicitly for battery comms. I'm not sure it could be used for something else. That said, it seems to be a bigger pain than doing what I did and the docs (section 8.2) say it is the wifi port that shares the inverter comms. And I don't use wifi at all because it is so insecure. It...

I thought I saw someone, somewhere say something about changing a setting to 20% instead of the 15% default (max discharge?). But I just checked setting 11 and I couldn't set it to 20% on the inverter.

They are actually heavier than the LL-S series. And price is higher, as noted. I prefer the 100Ah versions as you can swap them out (lower cost and effort) if one were to go bad.

How would you manually upgrade an XP that is not attached to a network?

Bummer!

Adding @EG4_Jarrett @EG4-Jacob ... is this improper cabling (ie, a custom cable is needed between LL-S and LifePower4)? I am using a standard CAT5e cable (what appears to be the battery comm cable)

I have a small C# program that does a RS485 modbus request to the 6000XP inverter to get data.. dotnetcore runs cross platform and will run on the Pi.