PurePower Posted February 11, 2023 Share Posted February 11, 2023 (edited) 41 minutes ago, Youda said: Hi @PurePower Just double-checked that and I can confirm that at the end of 2022 the latest FW versions for US2000 variants were: US2000plus = us2000b_v2.9_Crc.bin US2000plus95 = us2000B_Plus_V3.4_Crc.bin For a shame, I do not have the first file, just the second one. Sorry Also, there's no easy way of identify which variant you have, as both of the above are reporting device model = 2KBPL in the BatteryView. On top of that, beware that: - US3000 firmware is NOT compatible with US2000, so don't try to flash us3000a_V3.4_Crc.bin in the US2000. - US2000C and US3000C firmware IS unified. You can flash it into both, US2000C and US3000C. - US5000 has a special firmware. Like I wrote in the beginning - if it works, then don't repair it. However, if you have some problems and will be able to get us2000b_v2.9_Crc.bin from your seller or Pylontech support, then share it with the others afterwards, please. Thanks for the update, yip i am fully aware of not mixing the various firmware's. For the sake of science, I loaded the us3000a firmware onto a us2000b plus module. Firmware loaded fine but it registered the device as a 75ah module which it was not. The firmware load worked as they use the same CMU and PMU board just the us3000a has a larger capacity battery. Firmware's were specifically made for their respective capacity at the time. The C models are different as after the firmware load, you are asked to specify the aH of the battery, hence the reason why the US2000C and US3000C can use the same firmware zip files. I searched for v2.9 and managed to only find the us2000BPLS_v2.9_Crc.bin file. Here it is. US2000BPLS_V2.9_Crc.bin I am personally running v3.4 in 4 of my US2000B Plus modules with no issues. Edited February 11, 2023 by PurePower Youda 1 Quote Link to comment Share on other sites More sharing options...
Youda Posted February 11, 2023 Author Share Posted February 11, 2023 2 hours ago, PurePower said: For the sake of science, I loaded the us3000a firmware onto a us2000b plus module. Firmware loaded fine but it registered the device as a 75ah module which it was not. The firmware load worked as they use the same CMU and PMU board just the us3000a has a larger capacity battery. Oh man! Looks like you do know what the fear is 2 hours ago, PurePower said: Firmware's were specifically made for their respective capacity at the time. The C models are different as after the firmware load, you are asked to specify the aH of the battery, hence the reason why the US2000C and US3000C can use the same firmware zip files. Yeah, exactly. Funny is, that no matter what, the BatteryView is always asking user for entering the coulomb value at the end of the FW update, even if it cannot use it. For the models like US2000 or US3000 it logs error then, but for the C models it actually writes that value in the NVRAM as seen on the attached screenshots. It says coulomb, but it's actually expecting amp-hours, like 50 or 74: US3000: US3000C: Quote Link to comment Share on other sites More sharing options...
Youda Posted February 11, 2023 Author Share Posted February 11, 2023 On 2020/08/20 at 11:47 AM, Youda said: Last year, I added a wallbox to my solar, for charging electric vehicles. It's a single-phase 32A, so the max charging power is roughly 7.5kW. Some details are written in my previous post here: https://powerforum.co.za/topic/2322-youdas-off-grid-lab/page/2/?tab=comments#comment-58507 Personally, I don't own an EV, but for the nine months in a year the solar production is so excessive, that I have no use for all that power. Therefore, I offered EV charging for free and published the wallbox location on the PlugShare.com and on some other local charging maps too. Since then, curious EV drivers are stopping by, mostly just to check whether the charging a car from solar is really possible. And yes - it is Some of the cars that stopped for charging were Mitsubishi (hybrid), Citroen C-Zero, Hyundai Ioniq, Fiat 500e and the last one, just couple of days ago, was Hyundai Kona. Hyundai Ioniq: Fiat 500e: Hyundai Kona: Most of the drivers are charging just for 30 minutes or so, which equals to 3-4kWh and 15km of range. On the chart below, it's marked as "EVSE". If I do remember correctly, just one driver stayed longer than hour and took 8kWh. That equals to 30-40km, based on the model of the car. By the way - is there anybody else on the forum, charging his EV from the off-grid solar? If so, do you offer free charging to the other drivers or not? Since the original post above, dozens of hybrids and EV's stopped by my solar charger for a few kWh's. Here's a couple of them: The last one was funny: Renault was charging for an hour or so, then the Merc arrived and queued-up...on a slow solar charger The Renault let him to and the Merc was charging for 2,5hrs. Later that day, Renault arrived once again - as seen on the chart bellow: Power Me, Yellow Measure, jumper and 1 other 4 Quote Link to comment Share on other sites More sharing options...
Youda Posted February 11, 2023 Author Share Posted February 11, 2023 (edited) Driver of this Peugeot left me a message and attached the photo. Nice one! Edited February 11, 2023 by Youda jumper, Yellow Measure, iiznh and 1 other 4 Quote Link to comment Share on other sites More sharing options...
PierreJ Posted February 11, 2023 Share Posted February 11, 2023 8 hours ago, Youda said: Also, there's no easy way of identify which variant you have, as both of the above are reporting device model = 2KBPL in the BatteryView. Pylontech is sending out the us2000B_Plus_V3.4_Crc.bin firmware for older US2000B plus batteries as well, so I suspect that they might be allowing the 95% discharge even on the older batteries. Alternatively, the firmware could be smart and detect the minimum SoC from the serial number. I have never run any of my batteries down below 15% SoC, so I do not know. It could have been a mistake on their part, but since I only gave them the serial number for the battery (I didn't mention the model number) in my firmware request I reckon it's not likely. Youda 1 Quote Link to comment Share on other sites More sharing options...
PurePower Posted February 11, 2023 Share Posted February 11, 2023 54 minutes ago, PierreJ said: Pylontech is sending out the us2000B_Plus_V3.4_Crc.bin firmware for older US2000B plus batteries as well, so I suspect that they might be allowing the 95% discharge even on the older batteries. Alternatively, the firmware could be smart and detect the minimum SoC from the serial number. I have never run any of my batteries down below 15% SoC, so I do not know. It could have been a mistake on their part, but since I only gave them the serial number for the battery (I didn't mention the model number) in my firmware request I reckon it's not likely. This definitely sounds like what Pylontech is doing, its my suspicion as well. I am using US2000B's purchased between 2017 - 2019, all running v3.4 without any issues. Youda and PierreJ 2 Quote Link to comment Share on other sites More sharing options...
Youda Posted February 12, 2023 Author Share Posted February 12, 2023 (edited) BatteryView HV 3.5 and 3.8 Pylontech's "BatteryView HV" is a diagnostic tool used for the high-voltage batteries like: H48050 + external BMS Force H1 Force H2 If you are adding a new brick to the existing high-voltage stack, this tool might be useful for checking the voltage levels of the individual cells and ensuring that the stack is properly balanced. You'll need a Windows laptop with a serial port (or with USB2Serial converter) and a serial cable. Bear in mind that you will need real RS232 interface, NOT the 5V/3.3V UART. Common pinout of the RJ-45 CONSOLE port on the most of the Pylontech HV batteries: If your battery uses a different pinout, then consult the wiring with the product manual. Edited February 12, 2023 by Youda Yellow Measure 1 Quote Link to comment Share on other sites More sharing options...
Youda Posted February 12, 2023 Author Share Posted February 12, 2023 BatteryView HV 3.5 BatteryView 3.5 for HV Product.zip Quote Link to comment Share on other sites More sharing options...
Youda Posted February 12, 2023 Author Share Posted February 12, 2023 BatteryView HV 3.8.2 BatteryView 3.8.2 for HV Product.zip Quote Link to comment Share on other sites More sharing options...
Energy-Jason Posted February 13, 2023 Share Posted February 13, 2023 On 2023/02/11 at 7:33 PM, Youda said: Since the original post above, dozens of hybrids and EV's stopped by my solar charger for a few kWh's. Here's a couple of them: The last one was funny: Renault was charging for an hour or so, then the Merc arrived and queued-up...on a slow solar charger The Renault let him to and the Merc was charging for 2,5hrs. Later that day, Renault arrived once again - as seen on the chart bellow: This is amazing!! Quote Link to comment Share on other sites More sharing options...
tomvi Posted February 19, 2023 Share Posted February 19, 2023 On 12. 2. 2023 at 23:27, Youda said: BatteryView HV 3.8.2 BatteryView 3.8.2 for HV Product.zip 2.86 MB · 11 downloads Hello Youda, Do you know the password of the administrator in this version of the application please? In 3.5 it's "pylontech" but in 3.8 it doesn't work for me. After launching the app, it only shows me some data and I can't get anywhere. Thanks Tomas Quote Link to comment Share on other sites More sharing options...
Youda Posted February 20, 2023 Author Share Posted February 20, 2023 (edited) @tomvi for the BatteryView HV 3.8.2: User = user Administrator = Pylon2019001! Warning: Do not play with the stuff you are not trained on. Youda Edited February 20, 2023 by Youda Quote Link to comment Share on other sites More sharing options...
tomvi Posted February 20, 2023 Share Posted February 20, 2023 9 hours ago, Youda said: @tomvi for the BatteryView HV 3.8.2: User = user Administrator = Pylon2019001! Warning: Do not play with the stuff you are not trained on. Youda Thank you, i used terminal to scan batteries and i got very strange results. 5 batteries are ok, the last one is completely out of order. At the same time, BMS pretends that everything is in order and Gooodwe writes that the SOC is 50% Perhaps I can insert a slightly longer statement here pylon_debug>unit @ AverageTempr: 14111 Index Volt Curr Tempr AvgTempr BTlow BThigh BVlow BVhigh Base.St Volt.St Temp.St CoulombAH CoulombWH Time 1 49340 0 17000 12000 12000 12000 3287 3291 Idle Normal Normal 84% 41819 mAH 83% 1995 WH 2023-02-21 03:37:28 2 49335 0 18000 13333 13000 14000 3289 3289 Idle Normal Normal 84% 41819 mAH 83% 1995 WH 2023-02-21 03:37:28 3 49355 0 18000 14000 14000 14000 3290 3291 Idle Normal Normal 84% 41819 mAH 83% 1995 WH 2023-02-21 03:37:28 4 49346 0 18000 14000 14000 14000 3289 3290 Idle Normal Normal 84% 41819 mAH 83% 1995 WH 2023-02-21 03:37:28 5 49364 0 19000 15000 15000 15000 3290 3291 Idle Normal Normal 84% 41819 mAH 83% 1995 WH 2023-02-21 03:37:28 6 49311 0 20000 16333 16000 17000 3287 3288 Idle Normal Normal 50% 25123 mAH 54% 1286 WH 2023-02-21 03:37:28 Command completed successfully pylon_debug>bat @ Time: 2023-02-21 03:37:36 A.Tempr: 14111 C.Curr : 25000 mA D.Curr : -25000 mA B.State: Idle BalVolt: 3360 Bat Volt Curr Tempr V.State T.State AH(mAH) WH(mWH) Bal 0 3286 0 12000 Normal Normal 84% 41819 84% 133758 N 1 3291 0 12000 Normal Normal 84% 41819 84% 133748 N 2 3290 0 12000 Normal Normal 84% 41819 84% 133749 N 3 3290 0 12000 Normal Normal 84% 41819 84% 133751 N 4 3292 0 12000 Normal Normal 84% 41819 84% 133754 N 5 3289 0 12000 Normal Normal 84% 41819 84% 133752 N 6 3289 0 12000 Normal Normal 84% 41819 84% 133751 N 7 3290 0 12000 Normal Normal 84% 41819 84% 133750 N 8 3288 0 12000 Normal Normal 84% 41819 84% 133751 N 9 3290 0 12000 Normal Normal 84% 41819 84% 133753 N 10 3289 0 12000 Normal Normal 84% 41819 84% 133751 N 11 3289 0 12000 Normal Normal 84% 41819 84% 133748 N 12 3290 0 12000 Normal Normal 84% 41819 84% 133749 N 13 3290 0 12000 Normal Normal 84% 41819 84% 133752 N 14 3287 0 12000 Normal Normal 84% 41819 84% 133762 N 15 3289 0 14000 Normal Normal 84% 41819 84% 133741 N 16 3289 0 14000 Normal Normal 84% 41819 84% 133734 N 17 3289 0 14000 Normal Normal 84% 41819 84% 133737 N 18 3289 0 14000 Normal Normal 84% 41819 84% 133737 N 19 3289 0 14000 Normal Normal 84% 41819 84% 133738 N 20 3289 0 13000 Normal Normal 84% 41819 84% 133741 N 21 3289 0 13000 Normal Normal 84% 41819 84% 133734 N 22 3289 0 13000 Normal Normal 84% 41819 84% 133736 N 23 3289 0 13000 Normal Normal 84% 41819 84% 133736 N 24 3289 0 13000 Normal Normal 84% 41819 84% 133741 N 25 3289 0 13000 Normal Normal 84% 41819 84% 133743 N 26 3289 0 13000 Normal Normal 84% 41819 84% 133739 N 27 3289 0 13000 Normal Normal 84% 41819 84% 133738 N 28 3289 0 13000 Normal Normal 84% 41819 84% 133740 N 29 3289 0 13000 Normal Normal 84% 41819 84% 133743 N 30 3290 0 14000 Normal Normal 84% 41819 84% 133738 N 31 3290 0 14000 Normal Normal 84% 41819 84% 133734 N 32 3290 0 14000 Normal Normal 84% 41819 84% 133733 N 33 3290 0 14000 Normal Normal 84% 41819 84% 133736 N 34 3290 0 14000 Normal Normal 84% 41819 84% 133738 N 35 3290 0 14000 Normal Normal 84% 41819 84% 133739 N 36 3290 0 14000 Normal Normal 84% 41819 84% 133734 N 37 3291 0 14000 Normal Normal 84% 41819 84% 133732 N 38 3290 0 14000 Normal Normal 84% 41819 84% 133735 N 39 3290 0 14000 Normal Normal 84% 41819 84% 133737 N 40 3291 0 14000 Normal Normal 84% 41819 84% 133737 N 41 3291 0 14000 Normal Normal 84% 41819 84% 133734 N 42 3291 0 14000 Normal Normal 84% 41819 84% 133733 N 43 3291 0 14000 Normal Normal 84% 41819 84% 133734 N 44 3290 0 14000 Normal Normal 84% 41819 84% 133739 N 45 3290 0 14000 Normal Normal 84% 41819 84% 133726 N 46 3290 0 14000 Normal Normal 84% 41819 84% 133720 N 47 3290 0 14000 Normal Normal 84% 41819 84% 133720 N 48 3290 0 14000 Normal Normal 84% 41819 84% 133721 N 49 3290 0 14000 Normal Normal 84% 41819 84% 133722 N 50 3290 0 14000 Normal Normal 84% 41819 84% 133726 N 51 3290 0 14000 Normal Normal 84% 41819 84% 133721 N 52 3290 0 14000 Normal Normal 84% 41819 84% 133721 N 53 3289 0 14000 Normal Normal 84% 41819 84% 133721 N 54 3289 0 14000 Normal Normal 84% 41819 84% 133725 N 55 3290 0 14000 Normal Normal 84% 41819 84% 133726 N 56 3290 0 14000 Normal Normal 84% 41819 84% 133720 N 57 3290 0 14000 Normal Normal 84% 41819 84% 133720 N 58 3290 0 14000 Normal Normal 84% 41819 84% 133719 N 59 3290 0 14000 Normal Normal 84% 41819 84% 133725 N 60 3291 0 15000 Normal Normal 84% 41819 84% 133732 N 61 3291 0 15000 Normal Normal 84% 41819 84% 133728 N 62 3291 0 15000 Normal Normal 84% 41819 84% 133726 N 63 3291 0 15000 Normal Normal 84% 41819 84% 133731 N 64 3291 0 15000 Normal Normal 84% 41819 84% 133735 N 65 3291 0 15000 Normal Normal 84% 41819 84% 133731 N 66 3291 0 15000 Normal Normal 84% 41819 84% 133728 N 67 3291 0 15000 Normal Normal 84% 41819 84% 133730 N 68 3291 0 15000 Normal Normal 84% 41819 84% 133728 N 69 3290 0 15000 Normal Normal 84% 41819 84% 133734 N 70 3291 0 15000 Normal Normal 84% 41819 84% 133735 N 71 3291 0 15000 Normal Normal 84% 41819 84% 133729 N 72 3291 0 15000 Normal Normal 84% 41819 84% 133730 N 73 3291 0 15000 Normal Normal 84% 41819 84% 133728 N 74 3291 0 15000 Normal Normal 84% 41819 84% 133733 N 75 3287 0 17000 Normal Normal 50% 25123 52% 83829 N 76 3288 0 17000 Normal Normal 53% 26413 55% 87951 N 77 3288 0 17000 Normal Normal 52% 26123 54% 86995 N 78 3288 0 17000 Normal Normal 50% 25123 52% 83777 N 79 3288 0 17000 Normal Normal 54% 26913 56% 89658 N 80 3288 0 16000 Normal Normal 52% 25913 54% 86393 N 81 3287 0 16000 Normal Normal 50% 25123 52% 83719 N 82 3287 0 16000 Normal Normal 53% 26413 55% 87940 N 83 3287 0 16000 Normal Normal 51% 25623 53% 85361 N 84 3287 0 16000 Normal Normal 51% 25623 53% 85457 N 85 3287 0 16000 Normal Normal 53% 26413 55% 88060 N 86 3288 0 16000 Normal Normal 52% 25913 54% 86391 N 87 3288 0 16000 Normal Normal 51% 25623 53% 85404 N 88 3288 0 16000 Normal Normal 51% 25623 53% 85418 N 89 3287 0 16000 Normal Normal 53% 26413 55% 88086 N Command completed successfully Quote Link to comment Share on other sites More sharing options...
PurePower Posted March 6, 2023 Share Posted March 6, 2023 (edited) On 2023/02/02 at 11:26 PM, Youda said: 5) This list indicates firmware version suitable for the each model and what file to flash: Model: US2000plus FW: V2.9 FLASH: us2000b_v2.9_Crc.bin Model: US2000plus95 FW: V3.4 FLASH: us2000B_Plus_V3.4_Crc.bin Model: US3000 FW: V3.4 FLASH: us3000a_V3.4_Crc.bin Model: US2000C (original chip) FW: V2.8 FLASH: NT1.7+2.8.zip Model: US3000C (original chip) FW: V2.8 FLASH: NT1.7+2.8.zip Model: US2000C (new chip) FW: V1.7 FLASH: NT1.7+2.8.zip Model: US3000C (new chip) FW: V1.7 FLASH: NT1.7+2.8.zip Model: US5000 (original chip) FW: V1.3 FLASH: US5000 ST+NT 1.3.zip Model: US5000 (new chip) FW: V1.3 FLASH: US5000 ST+NT 1.3.zip New firmware for the C model range. Its an update to v1.8 for the new chip C models. NT1.8+ST2.8.zip Edited March 6, 2023 by PurePower PierreJ and Youda 2 Quote Link to comment Share on other sites More sharing options...
gt4020 Posted April 12, 2023 Share Posted April 12, 2023 (edited) Hi all, i'm using Pylontech US3000c in a custom solar system. My question is: is it possible to leave a 53V fixed charger voltage even if battery is 100% charged? In my system this can happen during the daylight since i don't manage charger stop when battery reached 100% SOC or "charge enable" flag from battery is "0". I'm not sure if the charger stop is mandatory in these condition or not... Edited April 12, 2023 by gt4020 Quote Link to comment Share on other sites More sharing options...
Youda Posted April 12, 2023 Author Share Posted April 12, 2023 Yes, it is possible, but: 1) You don't have to stop the charger once the Pylontech is charged to 100% SoC, as once the voltage of battery reaches the voltage set on the charger then the charging current will quickly drop to zero. You just have to watch for the situations where the voltage of charger suddenly jumps up. This might happen when large AC load is switched off, while the sun is fully shining. This might cause overvoltage alarm, if the resting voltage of the battery is already too high. Therefore, if you don't have a way how to disable the charger, it's better to set the charger to 52,5V (15x 3,5V). Such a voltage is still able to charge Pylontech to 100% SoC, while leaving sufficient "voltage margin" for these unexpected jumps. Got it? 2) Even some basic chargers have 2 settings that you can combine, in order to protect the battery from overvoltage and/or overcharging: CC voltage = 53V CV voltage = 52,5V. When both settings above are used together, the battery is charged to 53V first, then the charger lowers it's voltage to the resting 52,5V. 3) This is how the charging current looks in the last stage of charging, when the voltage of the Pylontech starts to reach the voltage set on the charger: From 10:00 the charging currents starts to drop quickly, reaching zero amps at 10:25. Note a small current spike at 10:46 - it's caused by a sudden voltage jump mentioned above. Quote Link to comment Share on other sites More sharing options...
warick_wrx Posted April 12, 2023 Share Posted April 12, 2023 I would assume senario 2 would be using the inverter's communication link to Pylontech BMS and these particular settings would be available to configure in the inverter/charger software. Seem to recall seeing it on my Multiplus. Quote Link to comment Share on other sites More sharing options...
gt4020 Posted April 12, 2023 Share Posted April 12, 2023 1 hour ago, Youda said: Yes, it is possible, but: 1) You don't have to stop the charger once the Pylontech is charged to 100% SoC, as once the voltage of battery reaches the voltage set on the charger then the charging current will quickly drop to zero. You just have to watch for the situations where the voltage of charger suddenly jumps up. This might happen when large AC load is switched off, while the sun is fully shining. This might cause overvoltage alarm, if the resting voltage of the battery is already too high. Therefore, if you don't have a way how to disable the charger, it's better to set the charger to 52,5V (15x 3,5V). Such a voltage is still able to charge Pylontech to 100% SoC, while leaving sufficient "voltage margin" for these unexpected jumps. Got it? 2) Even some basic chargers have 2 settings that you can combine, in order to protect the battery from overvoltage and/or overcharging: CC voltage = 53V CV voltage = 52,5V. When both settings above are used together, the battery is charged to 53V first, then the charger lowers it's voltage to the resting 52,5V. 3) This is how the charging current looks in the last stage of charging, when the voltage of the Pylontech starts to reach the voltage set on the charger: From 10:00 the charging currents starts to drop quickly, reaching zero amps at 10:25. Note a small current spike at 10:46 - it's caused by a sudden voltage jump mentioned above. Ok, i noticed the Pylon charge current behaviour when i designed my solar charger (it is a charger produced by me), so i assumed that Pylontech bms is able to manage itself entirely charge process. For this reason i did not add a way to stop charge at 100 % or when charge enable flag is 0. Lately however i tested an Mpp solar inverter with Pylontech batteries and i noticed that they completely stop charge when battery is 100%. For this reason i was asking what is the correct way to manage a fully charged Pylon battery. Response seems to be that leaving fixed 53V or stopping charger at 100% soc is indifferent... Do you agree? Quote Link to comment Share on other sites More sharing options...
Youda Posted April 12, 2023 Author Share Posted April 12, 2023 Not really @warick_wrx Scenario 2 is possible even without any comm cable between the Pylontech BMS and Inverter. It works purely based on the analog voltage and current measurement. It's basically the same logic that was used for lead-acid batteries in the old times when there were no BMS. If you have a comm cable and working communication between the BMS and the inverter, the possibilities are even richer. Quote Link to comment Share on other sites More sharing options...
Youda Posted April 12, 2023 Author Share Posted April 12, 2023 9 minutes ago, gt4020 said: Ok, i noticed the Pylon charge current behaviour when i designed my solar charger (it is a charger produced by me), so i assumed that Pylontech bms is able to manage itself entirely charge process. For this reason i did not add a way to stop charge at 100 % or when charge enable flag is 0. Lately however i tested an Mpp solar inverter with Pylontech batteries and i noticed that they completely stop charge when battery is 100%. For this reason i was asking what is the correct way to manage a fully charged Pylon battery. Response seems to be that leaving fixed 53V or stopping charger at 100% soc is indifferent... Do you agree? Yeah, in reality, both of these have a very similar effect. Let me just repeat that 53V is too much. Set your charger to 52,5V and that's it. No communication with the BMS necessary. In order to be precise: Normally, Pylontech BMS does NOT limit charging current. Yes, there is FET in the BMS input, but it's used as ON/OFF protective device only. The reason why you see that the charging current is going down is based purely on the fact that the battery is full and it's not accepting charge anymore. Lead-acid battery, without any BMS, has a very similar curve too. The only difference is that with the lead-acid the last stage of charging takes much longer, the amps curve is not so steep....and voltage levels per cell are different, of course: Example of practical implementation in a Mean Well charger: https://www.meanwell.com/newsInfo.aspx?c=5&i=946 PierreJ 1 Quote Link to comment Share on other sites More sharing options...
gt4020 Posted April 12, 2023 Share Posted April 12, 2023 1 hour ago, Youda said: Yeah, in reality, both of these have a very similar effect. Let me just repeat that 53V is too much. Set your charger to 52,5V and that's it. No communication with the BMS necessary. In order to be precise: Normally, Pylontech BMS does NOT limit charging current. Yes, there is FET in the BMS input, but it's used as ON/OFF protective device only. The reason why you see that the charging current is going down is based purely on the fact that the battery is full and it's not accepting charge anymore. Lead-acid battery, without any BMS, has a very similar curve too. The only difference is that with the lead-acid the last stage of charging takes much longer, the amps curve is not so steep....and voltage levels per cell are different, of course: Example of practical implementation in a Mean Well charger: https://www.meanwell.com/newsInfo.aspx?c=5&i=946 In my experience with Us3000 and US2000 i'm quite sure that during charge, when Soc rise to almost 100%,charging current has not a linear or parabolic descending curve, but it switch from full current charge to 10A and 2A (maintaining charger in CV @ 53V), so i think that bms has some sort of current modulation. I have an us3000c on my work table, tomorrow i will test again voltage/current charging curve... Quote Link to comment Share on other sites More sharing options...
JeanPhi90 Posted April 13, 2023 Share Posted April 13, 2023 On 2020/08/29 at 11:22 AM, Youda said: Hi guys, based on the fact that many forum users are trying to understand how to use Pylontech batteries efficiently, I've extracted some of the internal configuration values. It's from a stack of 8xUS3000. What instantly catched my eye are especially these values. So I added a couple of my comments and thougths: Total Num : 8 //Number of maximum daisy-chained bricks supported by the firmware. Present Num : 8 //Number of actually daisy-chained (RS485) bricks. Shut time : 72.0 H //If the brick is not charged/discharged for 3 days, it will auto-power off. Balance Volt : 30 mV Balance Start : 3360 mV //Looks like the BMS is able start balancing cells at this voltage it's not //a static top-balancing, as I know that the BMS chip is able to stop balancing //at a much higher voltage, if all the cells are at roughly the same voltage level. Recommend chg voltage : 53250 mV //This is what inverters like Axpert are reading //from the BMS and using as CC. Over VoltageR : 51000 mV //Strange, that this is triggered at 51V, given //the recommended CC=53.2V. High VoltageR : 52500 mV High Voltage : 53900 mV //Just 650mV of margin between recommended CC=53.2V and alarm. Over Voltage : 54000 mV //Just 750mV of margin between recommended CC=53.2V and panic. A complete list goes here. Please note that the column "Battery" means actually a CELL while the column "Power" means a single US3000 BRICK: Protect Attribution --------------------------------- Item Battery Power Over Voltage : 3700 54000 mV Over VoltageR : 3600 51000 mV High Voltage : 3650 53900 mV High VoltageR : 3500 52500 mV Low Voltage : 3050 46000 mV Low VoltageR : 3100 47000 mV Under Voltage : 2900 44500 mV Under VoltageR : 3250 49000 mV Sleep Voltage : 2500 38000 mV Charging OT : 61000 61000 mC Charging OTR : 55000 55000 mC Charging HT : 59000 59000 mC Charging HTR : 55000 55000 mC Charging LT : -9000 -9000 mC Charging LTR : -5000 -5000 mC Charging UT : -11000 -11000 mC Charging UTR : -5000 -5000 mC Discharging OT : 61000 61000 mC Discharging OTR : 55000 55000 mC Discharging HT : 59000 59000 mC Discharging HTR : 55000 55000 mC Discharging LT : -9000 -9000 mC Discharging LTR : -5000 -5000 mC Discharging UT : -11000 -11000 mC Discharging UTR : -5000 -5000 mC Charging OC : 102000 mA Charging OC Alarm : 50000 mA Charging OC AlarmR : 40000 mA Discharging OC : -100000 mA Discharging OC Alarm : -50000 mA Discharging OC AlarmR : -45000 mA OC Delay : 15000 mS OC Release : 60000 mS Charging OC2 : 200000 mA Discharging OC2 : -200000 mA OC2 Delay : 100 mS OC2 Release : 60000 mS Discharging SC : -400000 mA SC Delay : 0 mS SC Release : 60000 mS Charging Max Cur : 10000 mA Balance Start : 3360 mV Balance Volt : 30 mV Shut time : 72.0 H BUV/PUV time : 2400 S Sleep ctrl state : OFF Sleep every day StartTime : 20:00 EndTime : 08:00 HwSleepInfo HwSleepStatus : OFF HwSleepTime : 6 S HwWakeupTime : 60 S Data Save every day StartTime : 00:00 EndTime : 23:59 Save Interval : 1800 S Power System Information --------------------------------- System is idle Total Num : 8 Present Num : 8 Sleep Num : 0 System Volt : 49381 mV System Curr : -367 mA System RC : 352367 mAH System FCC : 585266 mAH System SOC : 60 % System SOH : 99 % Highest voltage : 3294 mV Average voltage : 3292 mV Lowest voltage : 3290 mV Highest temperature : 23000 mC Average temperature : 21875 mC Lowest temperature : 21000 mC Recommend chg voltage : 53250 mV Recommend dsg voltage : 47000 mV Recommend chg current : 296000 mA Recommend dsg current : -296000 mA Hope this helps all the young scientists that are developing their own monitoring and control solution for the batteries and inverters Youda A big thank for this informations! If I may ask a question, as I try to run a setup with presently 2 US2000 and 1 US200C, linked to Growatt inverter(s), but I have an issue with my 2nd inverter, it doesn't communicate with BMS, and thus I can't include it in my setup. This issue I try to solve with Growatt, but it may take some time, and I woud like to run the setup without BMS communication on both inverters, wich needs to set correct voltages in the inverters: Charge voltage, float voltage and low DC cut-off. Do you think that 53.2V for charge voltage, 52.5V for Float and 44,5V for low DC cut off are correct values for my 3 Pylontech stack? Quote Link to comment Share on other sites More sharing options...
svisagie Posted April 13, 2023 Share Posted April 13, 2023 Possibly a bit off topic here, but I'll ask anyway. Has anyone ever seen that US3000's report a SOC higher than 100% I have two in parallel and quite often find them to be 117% charged. They are obviously not overflowing with electrons, but I suspect that there is some kind of calibration issue with the SOC. Any ideas, comments, suggestions? Quote Link to comment Share on other sites More sharing options...
gt4020 Posted April 14, 2023 Share Posted April 14, 2023 (edited) On 2023/04/12 at 5:58 PM, gt4020 said: I'm testing an US3000C charge curve with CC/CV power supply at 52.85V. THis is the graph at the end of charge. I also tried to vary CV voltage from 52,85 to 53,25V (you can see a short current peak after voltage increase). I noticed that when battery is at 100% current drops near to 0A but battery cells are held at charger voltage/15 all the time. My question is: is it acceptable to maintain cells at maximum voltage for some hour per day even if they are fully charged? LiPoFe batteries life is not shorted when they stay at 100% voltage for many time? Edited April 14, 2023 by gt4020 Quote Link to comment Share on other sites More sharing options...
PurePower Posted April 23, 2023 Share Posted April 23, 2023 BatteryView HV 3.9 BatteryView 3.9.0 B1.2.zip Youda 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.