Timacatri, Could you possibly upload batteryview 3.0.29.
Hi all,
I have a SOC issues with my US2000 batteries, if i connect though BatteryView i can view all the cells parameters but i get “null” for the SOC.
This means that my Aton Inverter can charge and discharge the batteries but doesn’t comunicate to the app batteries state of charge.
My batteries running 2.4 FW version, I’m thinking to upgrade to the latest 2.8 through latest battey View software.
Anyone’s on this forum with the same issue? Do yiu guys think the FW upgrade could solve it?
BatteryView_us2000b_series_3.0.29 B1.1.zip (3.7 MB)
(ZIP of the original RAR file from Pylontech. The forum does not accept RAR files, and if I recompress the files to ZIP format it exceeds the 4MB size limit.)
Thank you.
I don’t know why Timacatri wouldn’t upload it. (He has since deleted his post saying that).
US3000 and US3000c in the same installation.
Hi all
I’m a newbie to this site and Solar DIY.
Hoping the community can assist me.
I have had a solar installation done in 2020.A Victron inverter and Pylontech US3000 back then.
Last year with all the stage 6 issues etc. I asked my installer if its possible to add in more batteries.
Was told yes very do-able.
So they organised me 2 new US3000c units.
Installed at my place but they couldn’t get it to work and talk to the inverter and US3000 (older batteries)
Then they reassured me its a firmware issue (battery side as Victron already running the latest firmware) and a quick software update will sort it all out.
November is over, December is gone and now Jan 2023 as well. They have completely ghosted me.
I have 2 brand new US3000c just lying about and nobody (ie no other installer wants to help)
Can anyone guide me on how I resolve this?
Thanks in advance
FYI @Pylontech-Jeff
Hi ats
How many older US3000’s do you have? Also, did you try the two new batteries on their own, connected to your system, to make sure they are working?
I know that Pylontech says your newest batteries must be in charge, so did you set one of the new ones up as the master battery?
2 Likes
Hi Deon
I have 6 older units.
I’m not sure if my installer tried the new units in isolation at all.
My firmware is the issue and not really sure on how to upgrade it.
Don’t want to brick the units or anything.
I have mixed older and newer units before, every time I had only had to put the new C models as master and it just worked.
1 Like
Ah, ok. If I were in your shoes, I would firstly check the two new batteries on their own.
I suggest testing them individually, to also check their respective state of charge, and to then charge both up to 100%. Once they are both fully charged, then connect both new models together on your system.
Retest and if successful, then make one new battery the master, and re-connect all batteries back in the stack.
If you are at all unsure, then rather get another installer to come and assist you with the set up.
2 Likes
Ok cool
Yeah I must be honest. I lack the experience currently.
Hence trying to get an installer that can help and also learn a bit more. So don’t get b’ssed.
This is the best approach.
If the errors still occur after having mixed new and old batteries connected, then its firmware related.
1 Like
Hi all.
Thanks again for all the advice.
So I managed to achieve the following this past few days.
- Charge the one US3000C unit.
- Connect it to the other older us3000 and balance them out.
- Connect it back to my Victron system as the new us3000c acting as the master.
- Connect a new type A cable from the new master to the Victron CCGX unit on the V.Can port.
- Configure the speed to 500 and ensure the terminator plug is inserted.
I also followed the following instructions and steps.
https://www.victronenergy.com/live/battery_compatibility:pylontech_phantom
The system is working fine (so far) in regards to charging and switch over during load shedding.
The Victron is not showing the batteries on device lists.
- The Victron firmware is all up to date since it’s done via the net including my inverter and mppts.
- Firmware on batteries I have no idea. I need to still buy a cable.
My other us3000c however is giving me issues.
- Unit is stuck in alarm mode.
- When tried to charge it by itself over night all I got was low battery errors along with High Ripple DC warning.
Any recommendations on how I get my units to show up on the CCGX and what to do with my other us3000c battery.
@JacoDeJongh tagging you as you the Victron guy…
I have a US2000B like that at R&D headquarters right now. “Internal failure” alarm. The ripple warning when charging, and the low battery errors, is because the battery has disconnected the cells from the DC bus, presumably because there is a low cell in there.
The interwebz says you need to turn the battery off, then turn it back on, then hold the red start button for 4 seconds.
What I would do is apply a low charge current (ie there must be voltage on the DC terminals of the battery), and then reset the battery. Hopefully it will start charging.
If all else fails… well my plan is to open it up and check the cells directly. But hopefully it doesn’t come to that.
1 Like
Hi Jeff, please can you advice where we can download the zip package from?
Hi all,
can anyone please provide me with a recent firmware package for the Force L2 (I don’t have any version for that) and possibly also the Force H2 models (I do have 1.6) ?
Thank you very much in advance!
Michael
You can bring dead batteries back to life after a failed firmware update without the help of Pylontech Support. If you turn on the small main switch while holding down the red start button, only the boot loader starts.
First you download the package with firmware and the flash program:
https://www.effekta.com/download/firmwareupdate-for-us2000c-3000c/
Unzip “Firmware update Pylontech US2000C_3000C V3_0.zip”.
Turn off the battery
Call “Update Tool.exe” in the “Upgrade Tool V1.0.9” folder
Choose serial port
Leave baud rate 115200
Click Immediate Update
click Connect
click Browse
Select firmware file: NT1.7+ST2.8.zip
(If you know what you are doing, you can also choose bin-files,
e.g. Us_c_Nt_V1.7_Crc.bin for the newer US3000C)
Start bootloader (press and hold red button and turn on main switch)
program
When finished, turn off the main switch, turn it on again, press the start button.
If “Unknown Input String” comes up when you click program, unfortunately you can’t select the
zip file (e.g. NT1.7+ST2.8.zip) with Browse, but must first unpack the zip and
select the appropriate bin file (e.g. Us_c_Nt_V1.7_Crc.bin).
As a new user I could not attach the latest FW I found. It runs on my US3000C (1.8):
“NT1.8+ST2.8.zip”
You can find it here:
https://powerforum.co.za/applications/core/interface/file/attachment.php?id=32876&key=9efed6356a5129f3598c3002f9dce902
1 Like
HI,
I tried this on my UP5000 and get a message “failed to get in bootloader mode”. I’m I doing something wrong? I do get “connected” before switching on. Just to confirm the dip switches needs to be 1-0-0-0 ? and if you hold the red button and then switch on the main switch, you can release the red button after switch on? then press “program” on Upgrade Tool?
UPDATE: I realized the error in your process above from another post: "4. Then click Program and switch on the battery by hard switch and the red soft start button immediately.
This will bring the battery back to normal."
This means you have to click “Program” first and then quickly switch on the Main switch while pressing the Red button at the same time. Then it goes into Bootloader mode. so all working now firmware related
BUT:
Now I get an alarm "red light " on the UP5000 and via the BatteryView 3.0.28 I can connect and when switch on after a few seconds it gives me an Alarm: “Addr Allocation ERR”… anyone knows what this means and how to fix?
thanks for you help 
PS. Does Pylontech_jeff still reply to emails?
Hi Jaco. Please can I ask for your assistance with my bricked US3000C! I used an incorrect upgrade process/bin file (from V1.3 to V2.2) last night and it will no longer turn on.
Many thanks!
UPDATE
Thanks to @nowayza I managed to get the UpgradeTool V1.0.9 to push the V1.7 update to my (newer chip) US3000C. I was also getting the “Fail to get into bootloader mode” error message previously, because I hadnt correctly understood that one needs to quickly turn on main switch whilst holding down the red SW button after clicking the “Program” button.
Thanks Jacques and everyone else for their posts which helped solve the issue.
My guess would be that two batteries are claiming the same address (ie, have their DIP switches set to the same value). But that’s just a guess.