Jump to content

PurePower

Members
  • Posts

    232
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by PurePower

  1. i would recommend the FTDI chipset for those cables. Don't use a cheap cable, they are not reliable.
  2. I'm interested to know the difference as well. Any update here?
  3. Item: Axpert 4kw/5kva x 4(Various brands but all compatible, they are not the clones/knock offs) Age: from 2018 onwards, I did not purchase them all at the same time. Price: R22k for all 4 Payment Method Accepted: EFT Condition: Good, all in working order Location: Jhb Reason: Upgrade Shipping: At the buyers cost and risk. Collection: Yes I have 4 x Axpert 4kw/5kva inverters. I currently only use 2 of them in parallel and 2 are backups. All are fully functional with the latest firmware from the Australian forum. They all have parallel cards in them and i have all the relevant cables required too. The 2 in use are paired up with my Pylontech battery bank. Looking to upgrade to a Sunsynk inverter. Any takers? Willing to accept R22000 for all 4. Please PM me.
  4. Thanks! Looks like v2.1 is for the 2000C/3000C using the newer chipset. Would be nice if Pylontech issued release notes...
  5. Identify the cells which are unbalanced with BatteryView then manually charge those cells(2 pouches make a cell) using a 3.7v charger with 1.5A max then add it back in. Assemble the battery again and test.
  6. Thank you @Tinbum, your guidance has worked.
  7. Batteries 8, 9 & 10 are the US2000B models and are at end of the pack...but after reading the manual again... you may be onto something. The below is from a US3000C manual: @Tinbum, you reckon if I shift the US2000B's into position 6, 7, & 8 then i should be good to go? Basically invert the order of batteries in the left cabinet and make the US3000C battery 9 and the US2000C battery 10... This actually makes sense now as the US2000B's only ever accommodated 8 in a single group... Lemme try this. PS: Note to self, don't commission new batteries into a pack at midnight!
  8. This looks like the correct thread to add my issue to. I too also have mixed Pylontech's in a single group but having issues when I recently added 2 more batteries to my existing pack of 8. I may have stumbled across a new issue. I had eight(batteries 3 - 10) in the pack but recently I have added two more batteries to my bank, totaling 10 modules now. Battery 1 and 2 are the latest additions. Below is a pic of them. Numbered from newest to oldest. Batteries 1 - 5 are the US3000C running the newer chipset and all have v1.8 firmware loaded. Battery 6 is a US3000C running the older chipset with v2.8 firmware. Battery 7 is a US2000C running v2.8 firmware. Batteries 8-10 are the US2000B's running v3.4 firmware. The manual always says that your newest battery should be the master which is how I have configured it but when you start the master(1) battery up(SW), it starts up each battery but when battery 9 is reached, it seems the BMS is not capable of dealing with more than 8 batteries in a single group even though the manual says that the C model battery can handle 16 batteries in a single group. All LED's on Battery 1 - 9 flashes and it attempts to restart each battery again. Battery 10 does not even start up. Unfortunately the battery pack does not start up and I can't even connect using BatteryView. I attempted to use Battery 6 as the master as it's using the older chipset, slaves starting then from 1 - 5 and continuing with 7 - 10. The same issue when reaching battery 9 as my previous point. I also then tried using Battery 6 again as the master but the order of the slaves are starting from 7 - 10 and continuing with 1 - 5. This seemed to have worked but can't connect to BatteryView for some reason still. Also this goes against having the newest battery higher up in the pack. At the moment I have disconnected Battery 1 and 2 like I had before so that I can continue to use my pack. This seems to be a firmware issue as I have double checked cabling and all is in order there. I even tried running Batteries 1 - 8 and there were no issues starting them up. This makes me believe that the firmware on the newer chipsets of the US3000C does not accommodate more than 8 batteries in a single group. I have emailed Pylontech and awaiting their response. Has anyone else experienced a similar issue?
  9. BatteryView HV 3.9 BatteryView 3.9.0 B1.2.zip
  10. Yeah, he needs to check whether he has the old or new chipset on the US3000C If OLD chip, then v2.8 is the latest firmware if NEW chip, then v1.8 is the latest firmware NT1.8+ST2.8.zip
  11. Yeah, you can upgrade straight to v1.8
  12. Board: NF4.E2 is the newer chipset and v1.8 is the latest available firmware for it. Use the tool and the zip file.
  13. New firmware for the C model range. Its an update to v1.8 for the new chip C models. NT1.8+ST2.8.zip
  14. You meant to say v1.8 is for the newer chipset Has anyone loaded v1.8? What has changed from v1.7?
  15. All info posted above. Always use the .zip file and BatteryView 3.0.28
  16. Cat 5 Standard Ethernet LAN cable will work. You can buy them anywhere or make them up as per the below colour guide.
  17. I am assuming you referring to the cable that goes into the Console port. The UP5000 uses the same RJ45 connection as a US3000C.
  18. SysError is a general error the BMS throws and usually shuts the pack down to protect it. It doesn't really give an explanation but that high voltage cell could very well be the reason in your case. I have seen SysError's on my US3000C when i mixed it with older US2000 plus modules. Only a firmware update to the US3000C's corrected that for me.
  19. Hey Greenman, I am literally looking for 1 cell, care to share? Also struggling to find US2000 Pylontech cells.
  20. This is spot on! The module experienced a high voltage as it reached 100%. Looks like the MPPT charge controller did not manage to drop the voltage to the pack and this more than likely popped the fuses. Command "datalist event 0" returned the following: pylon_debug> datalist event 0 @ Item Time Vo(mV) Cu(mA) Tempr Tlow Thigh Vlowest Vhighest Base.St Volt.St Curr.St Temp.St Per% Events SysErrCode 0 23-01-31 16:31:04 52541 752 33100 27700 28200 3480 3506 Charge Normal SC Normal 100% SC 1 23-01-31 16:59:44 53867 9525 33600 27600 28100 3561 3596 Charge High Normal Normal 100% PHV 2 23-01-31 17:00:08 53880 9203 33600 27600 28100 3562 3596 Charge High Normal Normal 100% PHV 3 23-01-31 17:00:30 53749 9167 33700 27600 28100 3555 3587 Charge High Normal Normal 100% PHV 4 23-01-31 17:00:54 53898 9568 33700 27600 28100 3564 3598 Charge High Normal Normal 100% PHV 5 23-01-31 17:01:16 53793 9718 33700 27600 28100 3559 3590 Charge High Normal Normal 100% PHV 6 23-01-31 17:01:40 53940 9963 33800 27600 28100 3568 3600 Charge High Normal Normal 100% PHV BHV 7 23-01-31 17:02:02 53790 9546 33900 27600 28100 3559 3590 Charge High Normal Normal 100% PHV 8 23-01-31 17:02:04 53930 9596 33900 27600 28100 3566 3600 Charge High Normal Normal 100% BHV 9 23-01-31 17:02:26 53817 8969 34000 27600 28100 3561 3592 Charge High Normal Normal 100% PHV 10 23-01-31 17:02:50 53893 8749 34100 27600 28100 3566 3597 Charge High Normal Normal 100% PHV 11 23-01-31 17:03:12 53762 9124 34200 27600 28100 3558 3588 Charge High Normal Normal 100% PHV 12 23-01-31 17:03:34 53767 10035 34300 27600 28100 3559 3589 Charge High Normal Normal 100% PHV 13 23-01-31 17:03:36 54016 10030 34300 27600 28100 3573 3605 Charge OV Normal Normal 100% POV BHV 14 23-01-31 17:03:58 53778 8507 34400 27600 28100 3559 3589 Charge High Normal Normal 100% PHV 15 23-01-31 17:04:20 53722 9732 34400 27600 28100 3556 3585 Charge High Normal Normal 100% PHV 16 23-01-31 17:04:22 53968 9706 34400 27600 28100 3571 3602 Charge High Normal Normal 100% BHV 17 23-01-31 17:04:44 53777 9056 34500 27600 28100 3559 3589 Charge High Normal Normal 100% PHV 18 23-01-31 17:07:04 53758 9852 34700 27600 28100 3558 3588 Charge High Normal Normal 99% PHV 19 23-01-31 17:08:36 53741 8325 34600 27600 28100 3557 3586 Charge High Normal Normal 99% PHV 20 23-01-31 17:09:20 53711 10368 34500 27600 28100 3555 3584 Charge High Normal Normal 99% PHV 21 23-01-31 17:09:22 54008 10204 34500 27600 28100 3573 3604 Charge OV Normal Normal 99% POV BHV 22 23-01-31 17:09:44 53893 10149 34500 27600 28100 3567 3597 Charge High Normal Normal 99% PHV 23 23-01-31 17:10:06 53715 9602 34500 27600 28200 3556 3584 Charge High Normal Normal 99% PHV 24 23-01-31 17:10:30 53818 9454 34500 27600 28200 3562 3591 Charge High Normal Normal 99% PHV 25 23-01-31 17:10:54 53881 9393 34400 27600 28200 3566 3596 Charge High Normal Normal 99% PHV 26 23-01-31 17:11:16 53809 9688 34400 27600 28200 3562 3591 Charge High Normal Normal 99% PHV 27 23-01-31 17:11:38 53714 9973 34400 27700 28200 3557 3584 Charge High Normal Normal 99% PHV 28 23-01-31 17:11:40 53961 9852 34400 27700 28200 3571 3601 Charge High Normal Normal 99% BHV 29 23-01-31 17:12:02 53839 9812 34400 27700 28200 3564 3593 Charge High Normal Normal 99% PHV 30 23-01-31 17:12:26 53923 9939 34400 27700 28200 3569 3598 Charge High Normal Normal 99% PHV 31 23-01-31 17:12:48 53820 9861 34400 27700 28200 3563 3591 Charge High Normal Normal 99% PHV 32 23-01-31 17:13:34 53740 9767 34400 27700 28200 3558 3586 Charge High Normal Normal 99% PHV 33 23-01-31 17:13:36 54015 9888 34400 27700 28200 3575 3605 Charge OV Normal Normal 99% POV BHV 34 23-01-31 17:13:58 53978 10446 34400 27700 28200 3573 3602 Charge High Normal Normal 99% PHV BHV 35 23-01-31 17:14:20 53781 9961 34400 27700 28200 3561 3589 Charge High Normal Normal 99% PHV 36 23-01-31 17:14:22 54251 10137 34400 27700 28200 3590 3621 Charge OV Normal Normal 99% POV BHV 37 23-01-31 17:14:30 53768 0 34400 27700 28200 3558 3588 Idle High Normal Normal 99% IDLE PHV 38 23-02-01 01:03:55 50756 0 28600 26900 27300 3375 3386 SysError Normal Normal Normal 100% SYSERR 0x200 A "SC" event is a Short Circuit, occurring at 23-01-31 16:31:04, this is more than likely when the MPPT failed. You can also see that the current was not tapering down even though the battery was at 100% SOC. Thereafter "PHV" (Pack High Voltage) events occurred several times. This event gets logged when the pack voltage reached 53.7v. Then also some cells hit a "BHV" (Battery cell High Voltage). This event gets logged when a cell voltage reached 3.6v. There are also "POV" (Pack Over Voltage) events. This get logged when the pack voltage reached 54v. Then around 23-01-31 17:14:30, which is 45 minutes later, there was no current sent to the pack. There after System errors are logged and the Battery more than likely went into an alarm state. From the logs, there doesn't seem to be any over current events logged but rather an over voltage event several times! The BMS board will need replacing but then you need to ensure that the cells are still in good condition as well.
×
×
  • Create New...