On 2022/02/01 at 2:01 PM, Tinbum said:

Anyone have a copy of the 2.6 firmware for the US3000C ?

us3000c_v2.6_Crc.bin

Thank you.

Ive received today 2x new Pylontech US3000C batteries.

I checked and it was old v1.9 firmware on it, so i update to v2.2-(which i have done sucesfully on my older US3000C batteries before). I must update because i have US3000B also in my stack.

But today no success it stopped at 83% and lost communication with battery.

Now the battery is dead and i cannot try update again, what must i do now?

Any one this happend before with?

 

14 minutes ago, PhillipMarx said:

Ive received today 2x new Pylontech US3000C batteries.

I checked and it was old v1.9 firmware on it, so i update to v2.2-(which i have done sucesfully on my older US3000C batteries before). I must update because i have US3000B also in my stack.

But today no success it stopped at 83% and lost communication with battery.

Now the battery is dead and i cannot try update again, what must i do now?

Any one this happend before with?

 

What firmware file did you use for the US3000B?

It is a different file to the US3000C. Latest firmware for US3000C is v2.6

Edited March 11, 20224 yr by PurePower

I used the us3000c v2.2_Crc file from this forum. The same file i used previously on my older us3000C batteries with success. 

Yes i know the US3000B has different file

 

16 minutes ago, PurePower said:

What firmware file did you use for the US3000B?

It is a different file to the US3000C. Latest firmware for US3000C is v2.6

I used us3000a V2.8_Crc.bin for my US3000B and us3000c v2.2_Crc.bin for my US3000C last year to do updates. Everthing is still working, today i wanted to update my New US3000C also to v2.2 and it failed and shutdown the battery.

Now it looks like its "Bricked"....

 

 

New version of battery view available.

 

https://l.facebook.com/l.php?u=https%3A%2F%2Fdrive.google.com%2Fdrive%2Ffolders%2F1ObOvQsTTTNH9zS2AtbvqYoB_8fIba57M%3Fusp%3Dsharing%26fbclid%3DIwAR10ku1CaWTtPdRspGpkO9_8bw-qJvmGJs-UEa_3nuXDyvuEs6fJcW2YFkE&h=AT0stEoxtZHC2R-NxmI5-hMb7GJirPa8suUZzGecwagnLMuuxGeU2iMiJ90JHoJajDagIED8ajWCDM7wNaafIZppq3ZYr8HjJiNcELX6kQY2MHJjGwmgIkbqccS7_WywLQ&__tn__=-UK-y-R&c[0]=AT2NAPlGpL97KMIDGxBXeaY8ULk1lAlfCaUPPWkegKjJkLUV4FWupCtFYKYsmsXzCt1zfbS0Z3lTNlGYG_4nD9iRkUytXg8UczIsYK89T07cfNBJUkRPqBNrZ_17FTwTmVm1N1CiwXREMMvZUtZEOyO6tIGr5o1GQ7uX4bTci8hY3FHFiAYySA2vljCNgFAhF_Z92x043v_yz-SWPPkFb5KRLMw4sbRhDUV9J_He1kEHqdz8bjf-

25 minutes ago, PurePower said:

It is a different file to the US3000C. Latest firmware for US3000C is v2.6

2.7 now.

7 minutes ago, PhillipMarx said:

today i wanted to update my New US3000C also to v2.2 and it failed and shutdown the battery.

Now it looks like its "Bricked"....

 

 

Can you downgrade batteries firmware as a new battery will have firmware later than 2.2??

Edited March 11, 20224 yr by Tinbum

The battery is dead can't log in on bms

Sorry edited my last comment a syou posted yours..

Your trying to put 2.2 on a new battery will be downgrading / rolling back the firmware which I don't know if that is possible and may have caused the problem. My new batteries were on 2.4 last year and this years were on 2.6 as supplied.

1 minute ago, Tinbum said:

Sorry edited my last comment a syou posted yours..

Your trying to put 2.2 on a new battery will be downgrading / rolling back the firmware which I don't know if that is possible and may have caused the problem. My new batteries were on 2.4 last year and this years were on 2.6 as supplied.

Ive checked before i did the upgrade and it was v1.9 otherwise i wouldn't have done an update.

Great. Perhaps a call to Pylontech then unfortunately.

 

As an aside, the new instructions for battery view now give a warning re firmware upgrade files and serial numbers and the version of battery view used on page 5 and the use of ZIP files not bin files.

9 minutes ago, Tinbum said:

Great. Perhaps a call to Pylontech then unfortunately.

 

As an aside, the new instructions for battery view now give a warning re firmware upgrade files and serial numbers and the version of battery view used on page 5 and the use of ZIP files not bin files.

Yup unfortunately supplier also said i have to bring in. Looks like I cant do anything about it now...

I read this on an other forum and just want to share here also.

Hi everyone,

Below are the latest firmware according to my supplier.

I think Jaco above mentioned. us_c_v.7_Crc to be used for US2000c and US3000c. However my supplier told me that the v2.7 is not formally been release to public yet. So I don’t know if it works or not. My supplier updated my US2000c’s with V2.6 as below attached.
us_c_v2.6_Crc.bin (224 KB)

For US2000b plus the below is apparently the updated version. I think Jaco also provided that in the previous chat.
us2000B_Plus_V3.4_Crc.bin (201 KB)

And finally here is the firmware latest version for US3000a batteries.
us3000a_V3.4_Crc.bin (214 KB)

I was also given the latest battery view software:
BatteryView_us2000b_series_3.0.28
Unfortunately I cannot share it on this page but If anyone is interested let me know and I will put it on Dropbox or somewhere for you to pick up.

I hope this help and if I have duplicated anything I apologies.

I also would like to share my experience regarding the firmware upgrade on my 3 new US2000c’s

I just replaced my US2000b Plus batteries with US2000c as 1 of the b+ batteries had a bad cell and the other one’s SOC will not go higher than 69%. I also decided to purchase another one so I can have 4 in my stack. There were no issues from Pylontech to replace them however the b and b+ batteries have been discontinued. Hence they replaced it with US2000c…(I think they have been discontinued for a while now.)

I brought my first US2000c home and before I installed it thought I would update the firmware first. The update stopped at 80% and the battery was dead. I could not start it up again . There was no voltage on the terminals. DEAD!!!
I took it back to the supplier asked them to check it out. After a long struggle the technician could also not get it started either. He tried everything to get it started again with no luck. He ended up changing the BMS board as per instructions from Pylontech. He replaced the board with a US3000c board. There after it worked fine and he could upgrade to the latest Firmware.

Now I thought this might just be a isolated instance but it was not, I replaced the other one this morning and purchased another one. While I was there I asked the technician to also update the firmware on the 2 new ones as well. However both of them gave exactly the same issue what I picked up. Luckily this time it happened to him and not me… He ended up changing those 2 BMS boards as well.

Personally I think there might be a problem with the BMS boards on the US2000c range that I received.
The batteries also did not have the same serial numbers as the old ones. The US2000b plus batteries started with PPTBH… but the new ones I received started with H21C… Not sure if this has any relevance but 3 brand new batteries gave exactly the same issue.

Just though I would share this info with you.
I would suggest when you do buy new US2000c batteries to let your supplier update the firmware for you. Just my suggestion

FYI

On my email from [email protected]

"Hi Marx,

 

Unfortunately, the new US3000C has upgraded the hardware so the old firmware will make the BMS board break."

 

This was a reply on my post on other forum:

 

Pylontech-Jeff 

 

Hi everyone!

We are very happy to announce that the new Pylontech US-C series batteries(US2000C/US3000C/UP5000) have made an evolution! To adapt to the new US-C batteries, we released the new BatteryView(3.0.28) software and new firmware upgrade method.

Now all firmware are compressed into a compressed package, the system will automatically select the most suitable firmware to upgrade your battery. At the same time, we have also made HUGE compatibility with the new upgrade method. The new BatteryView and firmware zip packs can also be used to upgrade older US-C series batteries.

The upgrade process is the same as before, the only difference is: Now you just need to “Browse” the firmware zip instead bin file before!

The download link of BatteryView 3.0.28 and new firmware zip can be referred by: New BatteryView(3.0.28) – Google Drive 17

Attention that please do not load the old firmware(.bin file) to the new batteries. Otherwise the battery BMS board will be clear the firmware and cannot be waken up.

 

I'm somewhat baffled by all of this as your battery came with firmware 1.9 which seems very old firmware for a new battery with the upgraded hardware. My new US3000C's came with 2.4 and 2.6 on. (2 different batches, 1 this year and 1 in AUG last year)

The two versions of 2.7 firmware on the other site are exactly the same. 🙄

 

What's the production date on your battery?

Edited March 14, 20224 yr by Tinbum

Is Jeff saying that there are 2 versions of the US3000C? If so, how does one distinguish them?

Edited March 14, 20224 yr by PurePower

 

35 minutes ago, Tinbum said:

I'm somewhat baffled by all of this as your battery came with firmware 1.9 which seems very old firmware for a new battery with the upgraded hardware. My new US3000C's came with 2.4 and 2.6 on. (2 different batches, 1 this year and 1 in AUG last year)

The two versions of 2.7 firmware on the other site are exactly the same. 🙄

 

What's the production date on your battery?

Baffled am I also, I’m just giving the replies through what everyone is saying.

The production date is: 2021-04-26 on my battery

What I’m trying to figure out is one of two things:

1: Does the "New" US3000C have a different BMS than the older US3000C, thus why it "Bricked" when I did update from v1.9 to v2.2(Not even the latest). I use v2.2, because I used it successfully on my other older US3000C batteries. According to Jeff there was a hardware change and if you update the “New” US3000C on the old way with the .bin file you will clear the firmware and BMS can’t be wake up again.

2: If there is no change in the US3000C BMS cards, then maybe there is a "bad'' batch of BMS cards that do that when updating

Only time will tell, I see there is another guy it happened with after me. So, it’s not an isolated incident in my opinion

By first batch are 28/05/2021 and the second 13/10/2021 and came with 2.4 and 2.6. I updated the 2.4 to 2.6 and then all have update OK with the 2.7 firmware (the first version posted and used as Bin file with battery view .23).

 

How can yours have the new hardware when it was produced before mine?

35 minutes ago, PurePower said:

Is Jeff saying that there are 2 versions of the US3000C? If so, how does one distinguish them?

Yes, i think so in the other forum and I would presume that it is by the serial numbers mentioned in the PDF that is with the battery view 3.0.28.

9 minutes ago, Tinbum said:

By first batch are 28/05/2021 and the second 13/10/2021 and came with 2.4 and 2.6. I updated the 2.4 to 2.6 and then all have update OK with the 2.7 firmware (the first version posted and used as Bin file with battery view .23).

 

How can yours have the new hardware when it was produced before mine?

Ha ha ha Then i bought new old stock with faulty bms perhaps lol.

There is massive confusion here. 

My US3000C production date is 27/02/2021 and it came shipped with v1.6 but was upgraded by Segen to v1.7. Since then i have been upgrading it successfully using a .bin file with BatteryView 3.0.24 and currently on v2.6. Now i am in two minds to going to v2.7 as its not clear from Jeff's posts if this latest update applies to my US3000C.

I am starting to think that Jeff is referring to BatteryView and not the US3000C. It seems that using BatteryView v3.0.28, one should always use the .zip file, for the previous BatteryView versions like 3.0.24, using the bin file is ok. 

53 minutes ago, PurePower said:

Is Jeff saying that there are 2 versions of the US3000C? If so, how does one distinguish them?

Page 5 

For upgrade US2000B/US3000A/Force-L series product:
Please select the correct .bin file for the upgrade, by any version of Batteryview.
For upgrade US2000C/US3000C/UP5000:
If the 8th and 9th of the product Serial Number is not ‘E2’ or ‘C3’, it can still select the
correct .bin file for the upgrade, by any version of Batteryview.
If the 8th and 9th of the product Serial Number is ‘E2’ or ‘C3’, please select the
correct .zip file for the upgrade, and require to use Batteryview V3.0.28 or higher.
*It`s suggested to always use the .zip file and Batteryview V3.0.28 for any
US2000C/US3000C/UP5000 upgrade to avoid wrong upgrade caused PCBA damage.

 

Pylontech Low Voltage Battery Mornitoring and Maintenance Tool Guidance 0228.pdf

6 minutes ago, PurePower said:

I am starting to think that Jeff is referring to BatteryView and not the US3000C. It seems that using BatteryView v3.0.28, one should always use the .zip file, for the previous BatteryView versions like 3.0.24, using the bin file is ok. 

I suspect this is 2 problems.

1 A couple of people have had problems updating and have bad BMS.

2 They are starting to produce a new hardware'd battery that needs to be updated by the ZIP file but we don't have that one.

 

And their for future upgrades 3.0.28 is recommended with ZIp files as you cant go wrong with new or old battery.