February 13, 20233 yr Hi @PurePower, @Youda and PylonTech experts , I have a problem with US3000C remaining in 'Idle' mode. I have no experience or knowledge of Pylon batteries. The site it belongs to has 3 of these in parallel . A couple of days ago one of 2 Axpert Kings connected to this pack had an MPPT failure. The owner informed me that the battery pack went dormant after that , but without an error (alarm). When I visited the site the batteries had no problem to switch on and reset , and all of them had the green led flashing once every 4 seconds or so . No red alarm . However , the packs gave no voltage output on battery terminals. I isolated batteries and also tested them as standalone (no link port connections) , but still nothing. I revisited the site today , this time armed with a console RS232 cable and BatteryView version 3.0.28 , and a 60V variable power supply . Fortunately my homebrewed cable connected successfully and I was able to extract info from the individual batteries . The state is "IDLE" (not shown in the image") , but as you can see there is no protection alarms . The batteries are brand new. below is additional info , which indicates no error code , cycle count only 2. I went so far as to connect a 51V power supply to the terminals , to see if it would accept charge , but nothing. So as you can see everything looks pretty normal , the cells are well balanced. But I get no output from any of these 3 packs. Any help or pointers to what I can attempt next would be highly appreciated. Kind Regards
February 13, 20233 yr I see some more salvaged cells that need to be rebuilt. I know someone who can do this 🤣🤣🤣
February 13, 20233 yr I would pull the cycle and event logs from the each battery. It will tell a story. Share those logs here then we can attempt to analyse.
February 13, 20233 yr Author 28 minutes ago, PurePower said: I would pull the cycle and event logs from the each battery. It will tell a story. Share those logs here then we can attempt to analyse. Thanks, can I do this with BatteryView?
February 13, 20233 yr Author 1 hour ago, John said: May be the internal fuse if the mppt voltage shot up during the failure? Thanks, I didnt know of an internal fuse, makes sense. In fact the user manual troubleshooting section mention it :
February 13, 20233 yr Hi @BritishRacingGreen 1) First of all - if the US3000C is running and the RUN led is slowly blinking, then the battery should be supplying 48V to the output terminals. There's no need to connect the communication cables etc. 2) Just grab a voltmeter and check the terminals. Beware that the SurLok terminals have plastic-insulated pins. Therefore you have to touch the side of the pin, not the tip. Like this: 3) Test each battery, one by one. 4) The screenshots that you've provided in the first post show that all the usual suspects are okay: - BMS OK - Cells OK - Temperature OK So, if there's no voltage on the terminals then the internal fuse (or precharge circuit) has blown. Even the manual is clear on this: BTW: Reliable Pylontech distributors have some spare BMS boards on stock and are experienced with flashing firmware or swapping the boards as these batteries are being sold in thousands. So the repair should not take ages. And in this particular case it really might be just the fuse.
February 14, 20233 yr 11 hours ago, BritishRacingGreen said: Thanks, can I do this with BatteryView? Yip, use the History Data window
February 14, 20233 yr Author 11 hours ago, Youda said: Hi @BritishRacingGreen 1) First of all - if the US3000C is running and the RUN led is slowly blinking, then the battery should be supplying 48V to the output terminals. There's no need to connect the communication cables etc. 2) Just grab a voltmeter and check the terminals. Beware that the SurLok terminals have plastic-insulated pins. Therefore you have to touch the side of the pin, not the tip. Like this: 3) Test each battery, one by one. 4) The screenshots that you've provided in the first post show that all the usual suspects are okay: - BMS OK - Cells OK - Temperature OK So, if there's no voltage on the terminals then the internal fuse (or precharge circuit) has blown. Even the manual is clear on this: BTW: Reliable Pylontech distributors have some spare BMS boards on stock and are experienced with flashing firmware or swapping the boards as these batteries are being sold in thousands. So the repair should not take ages. And in this particular case it really might be just the fuse. Hi @Youda, thanks, I have focused on proper connection. I have, example set a 50V supply on one set of terminals, and check meter output one the other terminals, in order to verify. So far, with you and others feedback, it looks indeed like a blown intetnal fuse. I have brought this to the attention of owner, and he will negotiate with supplier/agent to what extent we can verify this on site.
February 14, 20233 yr Author 5 minutes ago, PurePower said: Yip, use the History Data window Beautiful, I look forward to my third visit in order to do extraction of logs,in the hope of seeing somethin significant.
February 14, 20233 yr Author 13 hours ago, Steve87 said: I see some more salvaged cells that need to be rebuilt. I know someone who can do this 🤣🤣🤣 Ah, vultures circling very early already😁😁
February 18, 20233 yr Author Hi @John, @PurePower, @Youda , I had a third visit to site and managed to non-intrusively gain access to the inside the battery box . The image below of BMS refers. I measured negative 50V at points 1,2.3,5 and 6. Nothing at 7. I deducted the following simplified schematic as seen below : EDIT : please note that the orientation of my CFET is wrong , it should be mirrored horizontally: The readings inferred that both CFET (ChargeMOSfet) and DFET (DischargeMOSfet) had been turned on (there was no forward voltage drops from the body diodes inside the mosfets). Please note that the components are actually duplicated in parallel , eg. there are 8 cfets,8dfets,8 sets of fuses. There was no reading on 7 , which inferred the second fuse array had blown. This is an interesting fuse in that it has 4 pins instead of 2. You can note that in the image as well. Turns out this is a very interesting fuse , some of you might be familiar with it , but me , never knew it even existed. Following is a link from a helpful guy that identified the fuse type and explained the working and meaning of it. http://www.karosium.com/2016/09/the-weird-fuses-in-laptop-batteries.html?m=1 I will continue this post in a next post. Edited February 18, 20233 yr by BritishRacingGreen
February 18, 20233 yr Author ... continued from previous post . Ah , beautiful , Pylontech ! I am supposed to be an experienced engineer that can at least change a fuse in an appliance , but no , apparently not ! Can you imagine what the owner thinks of me now !!! So the thermal fuse has a square of solder alloy which acts as the fusing element . So when the current approaches the critical region , it get hot and melts away into the cavity. In addition there is a mechanism for the BMS MCU to also trigger a meltdown. This is actually very powerful and adds an additional level of defense when things go wrong. So the MCU will switch on the heater resistor , which sits below the alloy , and concentrates about 10 watts to heat it. So the jackpot question is whether the fuse blew because of over current or did it blow via the heater resistor activated by the MCU. My opinion is the latter. Firstly, the first fuse array did not blow . Secondly , if there was an overcurrent then the first defense is the MCU turns of both DFET and CFET. Now we know the fets are still working so I assume that it would have cut off the surge current by this means. My take on this is that the battery had been confronted with an over voltage condition from outside. Under this circumstance it is not enough to turn off the fets as the over voltage would still sit on the outboard fets and there could have been a risk that it would kill that fet array . So the MCU blew the thermal fuse . This is the only logical explanation I have and would invite any other explanation from you. Pylontech fuses are NOT serviceable for various reasons . Firstly its an inseparable part of a very large BMS control board . Secondly its SMD devices directly soladered onto the cb pads , and there are no less than 8 of them in parallel to make up for the high current rating. And to get the SMD code of the devices is very difficult. On the Teardown thread of @PurePower there is a nice view of the US2000 fuse array and at least when can clearly see the 'Z' marking , which is 20A Fast Blow at 65Volts. Then the 4 pin fuses are probably very hard to get by , and I think if you don't match them correctly , you doing your BMS no good. So i am basically stepping down , the owner will attempt to get it fixed via warranty or void repair. I will be a watchdog for him to ensure that he does not pay exorbitant price for a battery that is otherwise working. Thank you so much for all your valuable inputs. NOTE : PylonTech looks quality . The only downside for me is the fact that all BMS subsystems are on one large pcb. I would have liked to see a controller pxb , a power train pcb (fets) and a fuse pcb with surge protection. Edited February 18, 20233 yr by BritishRacingGreen
February 18, 20233 yr Author @PurePower I also managed to extract logs , although their content made very little sense to me . Hope you might see something interesting . Please find the bundle of logs as a compressed zip file . Thank you logs.zip Edited February 18, 20233 yr by BritishRacingGreen
February 18, 20233 yr Pwr OV Times : 4 Pwr HV Times : 30 Definitely looks like it experienced some kind of high voltage. 469 23-01-31 16:44:30 52973 870 33800 27600 28100 3507 3535 Charge Normal Normal Normal 100% 470 23-01-31 17:14:30 53768 0 34400 27700 28200 3558 3588 Idle High Normal Normal 99% IDLE PHV You can see there something happens on line 469, Pack high voltage and then after that it never moved current again .
February 19, 20233 yr Author 14 hours ago, Nexuss said: Pwr OV Times : 4 Pwr HV Times : 30 Definitely looks like it experienced some kind of high voltage. 469 23-01-31 16:44:30 52973 870 33800 27600 28100 3507 3535 Charge Normal Normal Normal 100% 470 23-01-31 17:14:30 53768 0 34400 27700 28200 3558 3588 Idle High Normal Normal 99% IDLE PHV You can see there something happens on line 469, Pack high voltage and then after that it never moved current again . @Nexuss thank you for the analysis , it does align with my suspicion that the cause of the thermal fuses blown is due to high voltage.
February 19, 20233 yr On 2023/02/18 at 5:08 PM, Nexuss said: Pwr OV Times : 4 Pwr HV Times : 30 Definitely looks like it experienced some kind of high voltage. 469 23-01-31 16:44:30 52973 870 33800 27600 28100 3507 3535 Charge Normal Normal Normal 100% 470 23-01-31 17:14:30 53768 0 34400 27700 28200 3558 3588 Idle High Normal Normal 99% IDLE PHV You can see there something happens on line 469, Pack high voltage and then after that it never moved current again . 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.
February 19, 20233 yr This is not for the first time I have seen Pylontechs do this. A BMS should be able to protect itself from a high voltage event. How a high voltage event can fry a BMS is beyond me. If thats the case then they need to apply a Voltage & amperage fuse to prevent this. How can a global company send out a battery that renders it in need of repair for a high voltage event. Even the cheapest BMSs sold in the DIY market will voltage protect without damage. Pylontech needs to improve their product. It's well below expectation at the moment. Edited February 19, 20233 yr by Steve87
February 19, 20233 yr Anyone know what a SysError is? In a pack of 8 batteries I had one go into fault. Buzzer sounding and red led. I shut it down and restarted and it's been fine ever since. It was discharging at the time. 610 23-01-26 05:32:29 49167 -1000 8100 6500 6800 3276 3280 Dischg Normal Normal Normal 0x0 Normal 68% 74000 1 3278 6700 Normal Normal 68% 2 3278 6700 Normal Normal 68% 3 3277 6700 Normal Normal 68% 4 3280 6700 Normal Normal 68% 5 3278 6700 Normal Normal 68% 6 3277 6800 Normal Normal 68% 7 3278 6800 Normal Normal 68% 8 3278 6800 Normal Normal 68% 9 3279 6800 Normal Normal 68% 10 3279 6800 Normal Normal 68% 11 3277 6500 Normal Normal 68% 12 3278 6500 Normal Normal 68% 13 3277 6500 Normal Normal 68% 14 3277 6500 Normal Normal 68% 15 3276 6500 Normal Normal 68% 611 23-01-26 06:02:32 49281 0 9400 6300 6700 3284 3287 SysError Normal Normal Normal 0x8 Normal 67% 74000 1 3285 6600 Normal Normal 67% 2 3286 6600 Normal Normal 67% 3 3285 6600 Normal Normal 67% 4 3287 6600 Normal Normal 67% 5 3286 6600 Normal Normal 67% 6 3285 6700 Normal Normal 67% 7 3286 6700 Normal Normal 67% 8 3286 6700 Normal Normal 67% 9 3286 6700 Normal Normal 67% 10 3286 6700 Normal Normal 67% 11 3285 6300 Normal Normal 67% 12 3285 6300 Normal Normal 67% 13 3285 6300 Normal Normal 67% 14 3284 6300 Normal Normal 67% 15 3284 6300 Normal Normal 67% 640 23-01-26 20:34:15 49419 0 10100 5900 6100 3294 3296 SysError Normal Normal Normal 0x8 Normal 67% 74000 1 3294 6100 Normal Normal 67% 2 3295 6100 Normal Normal 67% 3 3294 6100 Normal Normal 67% 4 3296 6100 Normal Normal 67% 5 3295 6100 Normal Normal 67% 6 3294 6100 Normal Normal 67% 7 3295 6100 Normal Normal 67% 8 3295 6100 Normal Normal 67% 9 3295 6100 Normal Normal 67% 10 3295 6100 Normal Normal 67% 11 3294 5900 Normal Normal 67% 12 3295 5900 Normal Normal 67% 13 3294 5900 Normal Normal 67% 14 3294 5900 Normal Normal 67% 15 3294 5900 Normal Normal 67% Restart 641 23-01-26 20:59:20 49419 0 10200 5900 6100 3294 3296 Idle Normal Normal Normal 0x0 Normal 66% 74000 1 3294 6100 Normal Normal 66% 2 3295 6100 Normal Normal 66% 3 3294 6100 Normal Normal 66% 4 3296 6100 Normal Normal 66% 5 3295 6100 Normal Normal 66% 6 3294 6100 Normal Normal 66% 7 3295 6100 Normal Normal 66% 8 3295 6100 Normal Normal 66% 9 3295 6100 Normal Normal 66% 10 3295 6100 Normal Normal 66% 11 3294 5900 Normal Normal 66% 12 3295 5900 Normal Normal 66% 13 3294 5900 Normal Normal 66% 14 3294 5900 Normal Normal 66% 15 3294 5900 Normal Normal 66% 642 23-01-26 21:01:03 49976 5113 9700 5900 6200 3331 3334 Charge Normal Normal Normal 0x80000 Normal 67% 74000 1 3332 6100 Normal Normal 67% 2 3332 6100 Normal Normal 67% 3 3331 6100 Normal Normal 67% 4 3334 6100 Normal Normal 67% 5 3332 6100 Normal Normal 67% 6 3331 6200 Normal Normal 67% 7 3332 6200 Normal Normal 67% 8 3332 6200 Normal Normal 67% 9 3332 6200 Normal Normal 67% 10 3332 6200 Normal Normal 67% 11 3331 5900 Normal Normal 67% 12 3332 5900 Normal Normal 67% 13 3331 5900 Normal Normal 67% 14 3331 5900 Normal Normal 67% 15 3331 5900 Normal Normal 67% Edit found it- seems very strange though when the battery is discharging; 3 23-01-26 05:52:55 49965 -1015 8000 6400 6800 3275 4095 SysError Normal Normal Normal 0x8 Normal 67% 74000 1 4095 6600 High Normal 67% 2 3277 6600 Normal Normal 67% 3 3276 6600 Normal Normal 67% 4 3278 6600 Normal Normal 67% 5 3277 6600 Normal Normal 67% 6 3276 6800 Normal Normal 67% 7 3277 6800 Normal Normal 67% 8 3277 6800 Normal Normal 67% 9 3277 6800 Normal Normal 67% 10 3277 6800 Normal Normal 67% 11 3276 6400 Normal Normal 67% 12 3276 6400 Normal Normal 67% 13 3276 6400 Normal Normal 67% 14 3275 6400 Normal Normal 67% 15 3275 6400 Normal Normal 67% I see it's done it once more since but it didn't shut down, same cell. Edited February 19, 20233 yr by Tinbum
February 19, 20233 yr Author 3 hours ago, PurePower said: 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. Thank you so much for your input , and confirming . One thing is for sure , you know your Pylontech 👌
February 19, 20233 yr Author 2 hours ago, Steve87 said: This is not for the first time I have seen Pylontechs do this. A BMS should be able to protect itself from a high voltage event. How a high voltage event can fry a BMS is beyond me. If thats the case then they need to apply a Voltage & amperage fuse to prevent this. How can a global company send out a battery that renders it in need of repair for a high voltage event. Even the cheapest BMSs sold in the DIY market will voltage protect without damage. Pylontech needs to improve their product. It's well below expectation at the moment. Hi Steve , in PylonTech's defense , the battery did negate the high voltage / short circuit condition and passivated the pack . However , I do agree that the replacement of the fuses is a delicate SMT rework exercise only to be undertaken by very skilled personnel. If your local support agent is not equipped to do so , we in for a complete BMS replacement , because the fuse arrays are part of the BMS PCB . That does not go well down by me. Imagine the owner of a Pylontech in Pofadder!
February 19, 20233 yr Author 2 hours ago, Tinbum said: Anyone know what a SysError is? In a pack of 8 batteries I had one go into fault. Buzzer sounding and red led. I shut it down and restarted and it's been fine ever since. It was discharging at the time. 610 23-01-26 05:32:29 49167 -1000 8100 6500 6800 3276 3280 Dischg Normal Normal Normal 0x0 Normal 68% 74000 1 3278 6700 Normal Normal 68% 2 3278 6700 Normal Normal 68% 3 3277 6700 Normal Normal 68% 4 3280 6700 Normal Normal 68% 5 3278 6700 Normal Normal 68% 6 3277 6800 Normal Normal 68% 7 3278 6800 Normal Normal 68% 8 3278 6800 Normal Normal 68% 9 3279 6800 Normal Normal 68% 10 3279 6800 Normal Normal 68% 11 3277 6500 Normal Normal 68% 12 3278 6500 Normal Normal 68% 13 3277 6500 Normal Normal 68% 14 3277 6500 Normal Normal 68% 15 3276 6500 Normal Normal 68% 611 23-01-26 06:02:32 49281 0 9400 6300 6700 3284 3287 SysError Normal Normal Normal 0x8 Normal 67% 74000 1 3285 6600 Normal Normal 67% 2 3286 6600 Normal Normal 67% 3 3285 6600 Normal Normal 67% 4 3287 6600 Normal Normal 67% 5 3286 6600 Normal Normal 67% 6 3285 6700 Normal Normal 67% 7 3286 6700 Normal Normal 67% 8 3286 6700 Normal Normal 67% 9 3286 6700 Normal Normal 67% 10 3286 6700 Normal Normal 67% 11 3285 6300 Normal Normal 67% 12 3285 6300 Normal Normal 67% 13 3285 6300 Normal Normal 67% 14 3284 6300 Normal Normal 67% 15 3284 6300 Normal Normal 67% 640 23-01-26 20:34:15 49419 0 10100 5900 6100 3294 3296 SysError Normal Normal Normal 0x8 Normal 67% 74000 1 3294 6100 Normal Normal 67% 2 3295 6100 Normal Normal 67% 3 3294 6100 Normal Normal 67% 4 3296 6100 Normal Normal 67% 5 3295 6100 Normal Normal 67% 6 3294 6100 Normal Normal 67% 7 3295 6100 Normal Normal 67% 8 3295 6100 Normal Normal 67% 9 3295 6100 Normal Normal 67% 10 3295 6100 Normal Normal 67% 11 3294 5900 Normal Normal 67% 12 3295 5900 Normal Normal 67% 13 3294 5900 Normal Normal 67% 14 3294 5900 Normal Normal 67% 15 3294 5900 Normal Normal 67% Restart 641 23-01-26 20:59:20 49419 0 10200 5900 6100 3294 3296 Idle Normal Normal Normal 0x0 Normal 66% 74000 1 3294 6100 Normal Normal 66% 2 3295 6100 Normal Normal 66% 3 3294 6100 Normal Normal 66% 4 3296 6100 Normal Normal 66% 5 3295 6100 Normal Normal 66% 6 3294 6100 Normal Normal 66% 7 3295 6100 Normal Normal 66% 8 3295 6100 Normal Normal 66% 9 3295 6100 Normal Normal 66% 10 3295 6100 Normal Normal 66% 11 3294 5900 Normal Normal 66% 12 3295 5900 Normal Normal 66% 13 3294 5900 Normal Normal 66% 14 3294 5900 Normal Normal 66% 15 3294 5900 Normal Normal 66% 642 23-01-26 21:01:03 49976 5113 9700 5900 6200 3331 3334 Charge Normal Normal Normal 0x80000 Normal 67% 74000 1 3332 6100 Normal Normal 67% 2 3332 6100 Normal Normal 67% 3 3331 6100 Normal Normal 67% 4 3334 6100 Normal Normal 67% 5 3332 6100 Normal Normal 67% 6 3331 6200 Normal Normal 67% 7 3332 6200 Normal Normal 67% 8 3332 6200 Normal Normal 67% 9 3332 6200 Normal Normal 67% 10 3332 6200 Normal Normal 67% 11 3331 5900 Normal Normal 67% 12 3332 5900 Normal Normal 67% 13 3331 5900 Normal Normal 67% 14 3331 5900 Normal Normal 67% 15 3331 5900 Normal Normal 67% Edit found it- seems very strange though when the battery is discharging; 3 23-01-26 05:52:55 49965 -1015 8000 6400 6800 3275 4095 SysError Normal Normal Normal 0x8 Normal 67% 74000 1 4095 6600 High Normal 67% 2 3277 6600 Normal Normal 67% 3 3276 6600 Normal Normal 67% 4 3278 6600 Normal Normal 67% 5 3277 6600 Normal Normal 67% 6 3276 6800 Normal Normal 67% 7 3277 6800 Normal Normal 67% 8 3277 6800 Normal Normal 67% 9 3277 6800 Normal Normal 67% 10 3277 6800 Normal Normal 67% 11 3276 6400 Normal Normal 67% 12 3276 6400 Normal Normal 67% 13 3276 6400 Normal Normal 67% 14 3275 6400 Normal Normal 67% 15 3275 6400 Normal Normal 67% I see it's done it once more since but it didn't shut down, same cell. Turns out you might be assisted by @Nexussand/or @PurePower, as they helped me with my logs.
February 20, 20233 yr 13 hours ago, Tinbum said: Anyone know what a SysError is? In a pack of 8 batteries I had one go into fault. Buzzer sounding and red led. I shut it down and restarted and it's been fine ever since. It was discharging at the time. 610 23-01-26 05:32:29 49167 -1000 8100 6500 6800 3276 3280 Dischg Normal Normal Normal 0x0 Normal 68% 74000 1 3278 6700 Normal Normal 68% 2 3278 6700 Normal Normal 68% 3 3277 6700 Normal Normal 68% 4 3280 6700 Normal Normal 68% 5 3278 6700 Normal Normal 68% 6 3277 6800 Normal Normal 68% 7 3278 6800 Normal Normal 68% 8 3278 6800 Normal Normal 68% 9 3279 6800 Normal Normal 68% 10 3279 6800 Normal Normal 68% 11 3277 6500 Normal Normal 68% 12 3278 6500 Normal Normal 68% 13 3277 6500 Normal Normal 68% 14 3277 6500 Normal Normal 68% 15 3276 6500 Normal Normal 68% 611 23-01-26 06:02:32 49281 0 9400 6300 6700 3284 3287 SysError Normal Normal Normal 0x8 Normal 67% 74000 1 3285 6600 Normal Normal 67% 2 3286 6600 Normal Normal 67% 3 3285 6600 Normal Normal 67% 4 3287 6600 Normal Normal 67% 5 3286 6600 Normal Normal 67% 6 3285 6700 Normal Normal 67% 7 3286 6700 Normal Normal 67% 8 3286 6700 Normal Normal 67% 9 3286 6700 Normal Normal 67% 10 3286 6700 Normal Normal 67% 11 3285 6300 Normal Normal 67% 12 3285 6300 Normal Normal 67% 13 3285 6300 Normal Normal 67% 14 3284 6300 Normal Normal 67% 15 3284 6300 Normal Normal 67% 640 23-01-26 20:34:15 49419 0 10100 5900 6100 3294 3296 SysError Normal Normal Normal 0x8 Normal 67% 74000 1 3294 6100 Normal Normal 67% 2 3295 6100 Normal Normal 67% 3 3294 6100 Normal Normal 67% 4 3296 6100 Normal Normal 67% 5 3295 6100 Normal Normal 67% 6 3294 6100 Normal Normal 67% 7 3295 6100 Normal Normal 67% 8 3295 6100 Normal Normal 67% 9 3295 6100 Normal Normal 67% 10 3295 6100 Normal Normal 67% 11 3294 5900 Normal Normal 67% 12 3295 5900 Normal Normal 67% 13 3294 5900 Normal Normal 67% 14 3294 5900 Normal Normal 67% 15 3294 5900 Normal Normal 67% Restart 641 23-01-26 20:59:20 49419 0 10200 5900 6100 3294 3296 Idle Normal Normal Normal 0x0 Normal 66% 74000 1 3294 6100 Normal Normal 66% 2 3295 6100 Normal Normal 66% 3 3294 6100 Normal Normal 66% 4 3296 6100 Normal Normal 66% 5 3295 6100 Normal Normal 66% 6 3294 6100 Normal Normal 66% 7 3295 6100 Normal Normal 66% 8 3295 6100 Normal Normal 66% 9 3295 6100 Normal Normal 66% 10 3295 6100 Normal Normal 66% 11 3294 5900 Normal Normal 66% 12 3295 5900 Normal Normal 66% 13 3294 5900 Normal Normal 66% 14 3294 5900 Normal Normal 66% 15 3294 5900 Normal Normal 66% 642 23-01-26 21:01:03 49976 5113 9700 5900 6200 3331 3334 Charge Normal Normal Normal 0x80000 Normal 67% 74000 1 3332 6100 Normal Normal 67% 2 3332 6100 Normal Normal 67% 3 3331 6100 Normal Normal 67% 4 3334 6100 Normal Normal 67% 5 3332 6100 Normal Normal 67% 6 3331 6200 Normal Normal 67% 7 3332 6200 Normal Normal 67% 8 3332 6200 Normal Normal 67% 9 3332 6200 Normal Normal 67% 10 3332 6200 Normal Normal 67% 11 3331 5900 Normal Normal 67% 12 3332 5900 Normal Normal 67% 13 3331 5900 Normal Normal 67% 14 3331 5900 Normal Normal 67% 15 3331 5900 Normal Normal 67% Edit found it- seems very strange though when the battery is discharging; 3 23-01-26 05:52:55 49965 -1015 8000 6400 6800 3275 4095 SysError Normal Normal Normal 0x8 Normal 67% 74000 1 4095 6600 High Normal 67% 2 3277 6600 Normal Normal 67% 3 3276 6600 Normal Normal 67% 4 3278 6600 Normal Normal 67% 5 3277 6600 Normal Normal 67% 6 3276 6800 Normal Normal 67% 7 3277 6800 Normal Normal 67% 8 3277 6800 Normal Normal 67% 9 3277 6800 Normal Normal 67% 10 3277 6800 Normal Normal 67% 11 3276 6400 Normal Normal 67% 12 3276 6400 Normal Normal 67% 13 3276 6400 Normal Normal 67% 14 3275 6400 Normal Normal 67% 15 3275 6400 Normal Normal 67% I see it's done it once more since but it didn't shut down, same cell. What model is this? and is it the master battery?
February 20, 20233 yr 4 hours ago, PurePower said: What model is this? and is it the master battery? It's a US3000C and no it's the 7th. I'm going to look at the log for the 8th and see what voltage that shows at the same time, if its logged at that time. EDIT this is the log for the 8th battery which shows them discharging and also shows the voltages. It's not at the specific time of the error on the 7th. (The way the inverter is set up was to do a constant discharge at a set current during the hours of darkness). How is the battery pack voltage measured or is it calculated from the sum of all the cell readings? 594 23-01-26 05:02:26 49212 -1312 8200 6200 6400 3280 3282 Dischg Normal Normal Normal 0x0 Normal 70% 74000 1 3281 6400 Normal Normal 70% 2 3282 6400 Normal Normal 70% 3 3281 6400 Normal Normal 70% 4 3281 6400 Normal Normal 70% 5 3281 6400 Normal Normal 70% 6 3281 6200 Normal Normal 70% 7 3280 6200 Normal Normal 70% 8 3281 6200 Normal Normal 70% 9 3281 6200 Normal Normal 70% 10 3280 6200 Normal Normal 70% 11 3281 6400 Normal Normal 70% 12 3280 6400 Normal Normal 70% 13 3282 6400 Normal Normal 70% 14 3280 6400 Normal Normal 70% 15 3280 6400 Normal Normal 70% 595 23-01-26 05:32:29 49171 -1252 8000 6200 6300 3277 3279 Dischg Normal Normal Normal 0x0 Normal 69% 74000 1 3279 6300 Normal Normal 69% 2 3279 6300 Normal Normal 69% 3 3278 6300 Normal Normal 69% 4 3278 6300 Normal Normal 69% 5 3278 6300 Normal Normal 69% 6 3279 6200 Normal Normal 69% 7 3277 6200 Normal Normal 69% 8 3278 6200 Normal Normal 69% 9 3278 6200 Normal Normal 69% 10 3277 6200 Normal Normal 69% 11 3278 6300 Normal Normal 69% 12 3278 6300 Normal Normal 69% 13 3279 6300 Normal Normal 69% 14 3278 6300 Normal Normal 69% 15 3277 6300 Normal Normal 69% 596 23-01-26 06:02:33 49112 -1346 7800 6000 6200 3273 3275 Dischg Normal Normal Normal 0x0 Normal 68% 74000 1 3275 6200 Normal Normal 68% 2 3275 6200 Normal Normal 68% 3 3274 6200 Normal Normal 68% 4 3274 6200 Normal Normal 68% 5 3274 6200 Normal Normal 68% 6 3275 6000 Normal Normal 68% 7 3273 6000 Normal Normal 68% 8 3274 6000 Normal Normal 68% 9 3274 6000 Normal Normal 68% 10 3274 6000 Normal Normal 68% 11 3274 6100 Normal Normal 68% 12 3274 6100 Normal Normal 68% 13 3275 6100 Normal Normal 68% 14 3274 6100 Normal Normal 68% 15 3273 6100 Normal Normal 68% Edited February 20, 20233 yr by Tinbum
February 20, 20233 yr 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.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.