Recent content by EG4_Jared

It would not be a problem.

Could you DM the serial number for the inverter? I believe the firmware update may have not gone through successfully.

The dongle should be reset and ready to pair. As for the latest inverter firmware, it should be 180C0D and if the LifePower4 were upgraded in January, they should be ready to communicate.

It's possible to divide the batteries into three banks: one comprising two LL-S and one LifePower4, and the other two banks consisting of the indoor units, all paralleled to an external bus. However, it is advisable to routinely top balance the banks as outlined in the previously posted document.

I suggest reviewing this testing document. Regarding the variations, it's advisable to have each battery bank as equal in amp hours as possible. This could mean having two banks at 280Ah and a third at 300Ah, or one at 560Ah and another at 600Ah.

Feel free to DM me the serial number for the Wi-Fi dongle and inverter. I can look into this for you.

This is correct.

I apologize for the confusion. The Ethernet cable pins 3 and 6 should be connected to the open battery communication port of the master battery to NO. I will contact our technical writing team to look at improving this section of our manuals and reference sheets.

It would enable you to verify that only one neutral-ground bond is present in the system.

Also, if the 6500 is on the latest firmware of 79.71, you should have a setting 42 which can enable/disable the neutral-ground bond.

The optimal approach would involve setting up three battery banks: one featuring the 280Ah Wallmount and the other two comprising three 100Ah server racks each. Subsequently, you should parallel them to an external bus. They will be compatible with the LL models but not with the LifePower4...

I believe notifications should now be available on the APP.

I would recommend using an external bus bar to parallel these batteries together. Also, it would be recommended to have one Wallmount for every 3 server rack batteries.

It would be interesting to see if this issue reoccurred while set to user-defined for the battery charge and discharge. With the batteries not utilizing the 80% depth of discharge, it seems like the percentage reading needs to be calibrated through a deep cycle process.

Standard ethernet cat5/5e/6.