Wondering if anyone can help with an odd BMS Issue with the combination of the below equipment combination.

 

Simple backup Inverter System - No Solar

1x Growatt SPF5000TL HVM

1x Dyness Powerbox - A48100 

Installation was completed late last year, on initial installation and setup of the battery as per the Dyness manual it is recommended that dip #2 & #3 are switched ON (SPF -HVM Series)  for correct communication between battery and inverter, the inverter programmed to LI with communication protocol 02 would not communicate with the BMS - code 20 and code 04.

After this fault supplier recommended Dip #2  ON only (SPH/SPA Series) which then established coms and I could see SOC values etc

This dip switch setting initially appeared to work and the system was happily functional and faultless  for roughly 2 days when the inverter then started disconnecting the supply and reconnecting again after about 30 sec each day, being  in the middle of festive season there was not much I could do but lived with the disconnection whilst still maintaining backup- the cause of the fault registering code 04 and 20 again each time the inverter disconnected and the reconnected after re establishing BMS!  

Fast forward to today the inverter disconnected but would not reboot automatically as it had done previously numerous times (completely dead until physically restarting the unit and battery with the power switches etc), a reset of the unit, re establishing or changing of BMS settings for the battery / Inverter, whatever has been tried will not allow the unit to communicate once again with the battery in LI Mode and the inverter shutdowns, the  inverter or possibly battery side of the BMS appears to be completely faulty now with code 04 and 20 being permanently displayed.

The connecting cables supplied with the dyness pack have both been checked and pin outputs appear correct between the inverter and battery BMS as well as the CAN and Rs485 Protocols - non however will work although it did initially the first 2 days🙈

In order to get the system functional again US2 (user defined option 2) has been configured instead temporarily and I have set all the charge characteristics manually and the inverter and battery are working and online again

Does anyone possibly have the same setup or similar experience and guidance in this case, before i pull the unit out and send it back to the manufacturer?

 

 

Edited January 17, 20223 yr by Tracsec

Hi，

1. The comms cable between the A48100 battery and the inverter is a standard cable sequence（Ordinary RJ45 network cable）.
2. The battery dip-switch is set to 0110.
3. Inverter setting 05 option choose LI and 36 option choose 01.
4. The inverter sets the cut-off SOC of 20 items to 20%（When you see that the cut-off of the inverter can be set to a percentage, it proves that the battery has successfully communicated with the inverter.）

If you have any other questions please contact me:

e-mail:[email protected]

Whatsapp:+8617625812876

 

Thanks

@Tracsec: Have been having this specific issue of random trips when in Li mode,  since day 1 of my install. In the meantime I have updated all Inverter FW, battery boards have been replaced as well as FW updated. When setting to Li mode and L01 it works fine, but minutes hours or days later it would randomly trip supply and restart the inverter. When set to Li mode and L01 everything is updated to % values and I can change and save these, so the comm is established and system runs perfectly. Untill the next restart....

Every now and then I get some hope and do yet another Inverter FW update as it is released and then run the system in Li mode with that worry in the back of my head. Only to be disappointed again and reset all and move back to USE mode.

On 2022/01/17 at 7:03 PM, Tracsec said:

Wondering if anyone can help with an odd BMS Issue with the combination of the below equipment combination.

 

Simple backup Inverter System - No Solar

1x Growatt SPF5000TL HVM

1x Dyness Powerbox - A48100 

Installation was completed late last year, on initial installation and setup of the battery as per the Dyness manual it is recommended that dip #2 & #3 are switched ON (SPF -HVM Series)  for correct communication between battery and inverter, the inverter programmed to LI with communication protocol 02 would not communicate with the BMS - code 20 and code 04.

After this fault supplier recommended Dip #2  ON only (SPH/SPA Series) which then established coms and I could see SOC values etc

This dip switch setting initially appeared to work and the system was happily functional and faultless  for roughly 2 days when the inverter then started disconnecting the supply and reconnecting again after about 30 sec each day, being  in the middle of festive season there was not much I could do but lived with the disconnection whilst still maintaining backup- the cause of the fault registering code 04 and 20 again each time the inverter disconnected and the reconnected after re establishing BMS!  

Fast forward to today the inverter disconnected but would not reboot automatically as it had done previously numerous times (completely dead until physically restarting the unit and battery with the power switches etc), a reset of the unit, re establishing or changing of BMS settings for the battery / Inverter, whatever has been tried will not allow the unit to communicate once again with the battery in LI Mode and the inverter shutdowns, the  inverter or possibly battery side of the BMS appears to be completely faulty now with code 04 and 20 being permanently displayed.

The connecting cables supplied with the dyness pack have both been checked and pin outputs appear correct between the inverter and battery BMS as well as the CAN and Rs485 Protocols - non however will work although it did initially the first 2 days🙈

In order to get the system functional again US2 (user defined option 2) has been configured instead temporarily and I have set all the charge characteristics manually and the inverter and battery are working and online again

Does anyone possibly have the same setup or similar experience and guidance in this case, before i pull the unit out and send it back to the manufacturer?

 

 

did you get this sorted ? I recently got the same setup and am having the same Error codes