Jump to content

Featured Replies

Posted

Hello Guys

I hope you are well. I am trying to upgrade my Pylontech US3000A and US3000C batteries. I have the latest firmware as supplied by Segen. I have tried BatteryView v3.0.24, 28 and 33. When I try to connect to the batteries I get this error. Any hints to what is causing this?

Regards,
Simon

f4a1720f-ea2f-4725-b3e0-a3973f3c8967.jpeg

Hi, you need a cable for US3000A/B and a different cable for US3000C.

Are you using the correct cable?

Can you see all the cells when you connect, voltages etc? 

Make sure you have the correct firmware for A/B and C. There are various versions for type C depending on motherboard version. 

  • 2 weeks later...
On 2024/02/09 at 11:38 AM, Simon M. said:

Any hints to what is causing this?

Change region settings on computer to United States

  • Author

Ok, I will double check the settings. Yes I have two different sets of cables for the US3000A and the US3000C. I used to run the US3000A as the primary batteries (before getting the US3000C) and had the small terminator (whatever its name is). I use the different cable now to connect to the console of the US3000C. So I have both sets of cables. I will try set the regional settings to US and see what happens. Going to try it now. Thank you!

I suspect you might have an issue with the console cable. I had a similar situation and found that the cable was no longer working correctly. Check the windows device manager prior to plugging the cable in and then check it again after plugging it in to ensure you see both a COM port and a Universal Serial Bus controller.

Just for interest sake, why do you need to upgrade Pylontech batteries? Mine are a mix of 9 between 2-4 years old, are they supposed to be upgraded?

On 2024/02/28 at 12:14 PM, Simon M. said:

Set the region settings to the US and it still exceptioned.

Hurry up and time to wait for Segen again......

 

0974faf8-f0d5-4752-a559-fe1a24184750.thumb.jpg.0870b24c04bc88ac1dbb4889cfc5c217.jpg59152e73-8afa-4ace-a561-f89c9b62e47c.thumb.jpg.19881f46457ce48eee1611471be555ed.jpg01739c83-50bd-4cc0-9f4f-67a369da5694.thumb.jpg.9fc633a94961fd9f01f79d4f0afee4f3.jpgtioned.

It looks like it is an error with the date formatting the software is struggling with, it might be the order of the date, try changing it to day/month/year instead.

You might also need to change your number formatting to a . for decimals and a , for thousands seperator.

  • Author
On 2024/02/28 at 1:08 PM, JKKM said:

I suspect you might have an issue with the console cable. I had a similar situation and found that the cable was no longer working correctly. Check the windows device manager prior to plugging the cable in and then check it again after plugging it in to ensure you see both a COM port and a Universal Serial Bus controller.

Yeah it is showing up as COMX and device manager registering it too.

  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...