AthlonFX Posted April 2, 2022 Posted April 2, 2022 Hello everybody, I had a good running array of two US2000B-Plus (serial no starting with PPTBH0540181) combined with a Victron Multiplus-II GX. I decided to add another US2000, this time it was a US2000C. And then the problems started. It ran into Internal Failure alarms when discharging at higher loads (2000W for all the modules; no problem before I added the new module) or discharging below 60%. I charged the modules to 100% individually and kept them charged for some hours, put them back together and kept them charged again for some hours. But the problem persisted. I read on another forum that this might be a firmware issue. So I manufactured two cables, one for the RJ11 port and one for the RJ45 port. I determined the firmware versions with BatteryView mentioned in this post. The US2000C had the firmware V1.2, both of the US2000B-Plus V3.4. Jeff wrote: "Now all firmware are compressed into a compressed package, the system will automatically select the most suitable firmware to upgrade your battery." The Google Drive link in the post contains the BatteryView software and a zip archive with the firmware. I was able to upgrade the firmware of the US2000C module to V1.4. So I thought it would be a good idea to upgrade the firmware of the US2000B-Plus modules, too. I understood the quoted sentence of Jeff as the BatteryView software could determine if the archive contains a suitable firmware file for the connected module (no matter which version of the US2000 range it is). So I started the upgrade and at about 83%, the upgrade process stopped with an error. The module can’t be started anymore. If I turn on the main switch, the led turns on, but it can't be started with the SW button. BatteryView can't connect to the module anymore. I contacted the Pylontech service, but I didn't get an answer yet. Does anybody know how to revive it again? How to get the correct firmware installed again? Thanks in advance and Kind regards AthlonFX Quote
AthlonFX Posted April 14, 2022 Author Posted April 14, 2022 Hi everyone, I made some progress on diagnosing stuff. The used microcontroller is the Texas Instruments TM4C123BH6PZ, which can be programmed via JTAG. The board itself PHANTOM_SA_CMU_V10R07 has a jack (J304) which has pins connected to the microcontroller, fortunately the ones needed for connecting to it via JTAG. Firmware can be flashed using the Texas Instruments EK-TM4C123GXL Evaluation Board and Texas Instruments UniFlash software. I successfully flashed (verified afterwards) several different firmware .bin-files, but none of them brought my module back to life. If I pushed the SW button, at least some leds on both boards in the module turned on, but that was it. I've got the feeling that the microcontroller might need a bootloader which is not in the firmware .bin-files. I haven't received an answer from Pylontech service yet (Maybe they're in a lockdown?!), maybe they can provide the correct .bin-file with the bootloader included. I had the thought that I might be able to dump the whole memory of the microcontroller in the other US2000B-Plus module and flash it on the microcontroller of the broken one, but I'm still hesitant, because there'd be the possibility of breaking the good module, too. I'll share the information of the service, if I get any. If I can bring it back to life, I'll happily share the necessary steps including the JTAG pinout. Does anybody have an idea what else I could try? Kind regards AthlonFX Quote
AthlonFX Posted April 15, 2022 Author Posted April 15, 2022 (edited) I was able to read the whole memory of the microcontroller of the good module with UniFlash, it was quite easy (Memory pane, Export, range 0x0 to 0x3FFFF). After that, I successfully flashed the created .bin-file onto the microcontroller of the bad module. The good news is the good module still works. But the bad module is still as dead as it was before. My guess is that the original flash with the wrong firmware somehow damaged the hardware. Edited April 15, 2022 by AthlonFX Quote
Deyan Vitanov Posted April 17, 2022 Posted April 17, 2022 did you manage to resolve this @AthlonFX ? I doubt the wrong firmware damaged the hardware. I hope you found a solution. For the past few days I'm thinking how I want to expand my pylontech us3000c storage with custom LifePO4 cells, connected to pylontech us3000c BMS..but I could not find that bms sold anywhere These Pylontechs are getting more and more expensive. Please let me know if you manage to find a new bms board for your dead module Quote
AthlonFX Posted April 17, 2022 Author Posted April 17, 2022 @Deyan Vitanov no, I haven't been able to resolve the problem. I'm out of promising ideas. I hope the Pylontech service will answer some time soon (but I doubt it, there's still a lockdown in place in Shanghai). I tried to find a replacement BMS board before I tried to fix the "broken" one, but I couldn't find a source. I think they just don't sell these separately. Quote
Deyan Vitanov Posted April 17, 2022 Posted April 17, 2022 4 minutes ago, AthlonFX said: @Deyan Vitanov no, I haven't been able to resolve the problem. I'm out of promising ideas. I hope the Pylontech service will answer some time soon (but I doubt it, there's still a lockdown in place in Shanghai). I tried to find a replacement BMS board before I tried to fix the "broken" one, but I couldn't find a source. I think they just don't sell these separately. yeah, I also did not found any supplier for Pylontech BMS board. btw you can try to contact some supplier/retailers if they have some faulty pylontech batteries and are willing to sell the bms Quote
Coulomb Posted April 18, 2022 Posted April 18, 2022 On 2022/04/15 at 5:57 AM, AthlonFX said: The used microcontroller is the Texas Instruments TM4C123BH6PZ, which can be programmed via JTAG. The board itself PHANTOM_SA_CMU_V10R07 has a jack (J304) which has pins connected to the microcontroller, fortunately the ones needed for connecting to it via JTAG. Firmware can be flashed using the Texas Instruments EK-TM4C123GXL Evaluation Board and Texas Instruments UniFlash software. I successfully flashed (verified afterwards) several different firmware .bin-files, Respect! Quote
chinezbrun Posted October 2, 2022 Posted October 2, 2022 guys same happened to me after i flashed a wrong firmware for US2000c. i have now a dead pylontech module. any solution? i bought the module 5 days ago... Quote
AthlonFX Posted October 2, 2022 Author Posted October 2, 2022 After my attempts to revive the module, I had contact with an employee of Pylontech. He sent me a special flash tool (not BatteryView) and a firmware file. I tried flashing my dead module with no success. In the end I had to send it to the distributor to get the board replaced. I posted my problem in other forums. Other users had the same problem, some could solve it with the special flash tool and firmware file. I might send you the email address of the employee if you want to contact him. Quote
PurePower Posted October 7, 2022 Posted October 7, 2022 On 2022/10/02 at 10:34 PM, chinezbrun said: yes, please! Please share the special flash tool and firmware Quote
Tinbum Posted October 7, 2022 Posted October 7, 2022 3 hours ago, PurePower said: Please share the special flash tool and firmware I'm certain their is a link to it somewhere on this site if your search. Quote
PurePower Posted October 7, 2022 Posted October 7, 2022 9 minutes ago, Tinbum said: I'm certain their is a link to it somewhere on this site if your search. The special flash tool is not on this forum. BatteryView is not the special flash tool here that is spoken of either. Quote
Tinbum Posted October 7, 2022 Posted October 7, 2022 (edited) 2 hours ago, PurePower said: The special flash tool is not on this forum. BatteryView is not the special flash tool here that is spoken of either. I wasn't referring to battery view. I'm sure i've seen it on here. Edited October 7, 2022 by Tinbum Quote
PurePower Posted October 8, 2022 Posted October 8, 2022 That is an old tool and not suitable for the C models. Quote
Tinbum Posted October 8, 2022 Posted October 8, 2022 (edited) 5 hours ago, PurePower said: That is an old tool and not suitable for the C models. Apologies for trying to help. It's actually the US2000B-Plus the author has been trying to update the firmware on. Edited October 8, 2022 by Tinbum PurePower 1 Quote
Michele Posted December 1, 2022 Posted December 1, 2022 On 2022/10/02 at 10:01 PM, AthlonFX said: After my attempts to revive the module, I had contact with an employee of Pylontech. He sent me a special flash tool (not BatteryView) and a firmware file. I tried flashing my dead module with no success. In the end I had to send it to the distributor to get the board replaced. I posted my problem in other forums. Other users had the same problem, some could solve it with the special flash tool and firmware file. I might send you the email address of the employee if you want to contact him. I have the same problem, can I have the contact of pylontech? Quote
Riaan Claassens Posted March 16, 2023 Posted March 16, 2023 Hi everyone, Has anyone on the forum had any luck reviving a Pylontech US3000C battery after a failed firmware upgrade? The unit is dead after reaching 83% with the correct firmware, I have used this firmware on plenty Pylontech 3000C batteries without any issues. I was trying to update from V1.4 to V2.6. I don't know through which distributor the battery was purchased originally and nobody is willing to assist from a supplier point of view if the unit was purchased elsewhere. I did e-mail Pylontech support but with no feedback as of yet. Thank you in advance. Quote
PurePower Posted March 16, 2023 Posted March 16, 2023 27 minutes ago, Riaan Claassens said: Hi everyone, Has anyone on the forum had any luck reviving a Pylontech US3000C battery after a failed firmware upgrade? The unit is dead after reaching 83% with the correct firmware, I have used this firmware on plenty Pylontech 3000C batteries without any issues. I was trying to update from V1.4 to V2.6. I don't know through which distributor the battery was purchased originally and nobody is willing to assist from a supplier point of view if the unit was purchased elsewhere. I did e-mail Pylontech support but with no feedback as of yet. Thank you in advance. Check this post Quote
Tinbum Posted March 16, 2023 Posted March 16, 2023 33 minutes ago, Riaan Claassens said: Hi everyone, Has anyone on the forum had any luck reviving a Pylontech US3000C battery after a failed firmware upgrade? The unit is dead after reaching 83% with the correct firmware, I have used this firmware on plenty Pylontech 3000C batteries without any issues. I was trying to update from V1.4 to V2.6. I don't know through which distributor the battery was purchased originally and nobody is willing to assist from a supplier point of view if the unit was purchased elsewhere. I did e-mail Pylontech support but with no feedback as of yet. Thank you in advance. Just checking, you are aware their are two different firmware's for the US3000C depending on age. Going from 1.4 to 2.6 seems wrong. (1.4 to 1.8 I would have thought). Nexuss 1 Quote
PurePower Posted March 16, 2023 Posted March 16, 2023 4 hours ago, Tinbum said: Just checking, you are aware their are two different firmware's for the US3000C depending on age. Going from 1.4 to 2.6 seems wrong. (1.4 to 1.8 I would have thought). 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 Quote
Turnip26 Posted November 6, 2024 Posted November 6, 2024 On 2022/10/07 at 10:41 PM, AthlonFX said: I might have sent you a message Might I receive a message too? Quote
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.