AthlonFX

I might have sent you a message 😉

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.

@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.

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.

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

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