Does anyone know if this is hardware specific or firmware specific.

I have have 6 US5000 and I can only get Batteryview v3.0.28 to see the module I have the cable plugged into. I am connecting using Console port to USB on Windows. Plugging the cable into the Master battery still only shows that battery in the left pane on the software. I presume this is a firmware issue. Anyone with more understanding of the software might be able to answer me.

Edited August 6, 20232 yr by ThomasT

Did you select the UNITED check box and number of units? You should then see all 6 listed in the device list window. The resulting scanlog.....xls file only shows the Module information for the master battery and scan data for all connected modules

I’m trying to do the same thing as the OP, display data on 2 x US5000 . Selecting the United checkbox and setting the units to 2, I get the following error:

Does anyone know the necessary edit to the config file please?

Hello - did anyone gave an explanation on this issue ? I face similar problem.

I'm using v3.0.37 - USB / COM / RJ45 - I have a pack of 1x US5000 + 4x US2000C

1° connecting with Windows 11 does not work - always error message with COM port 8
I only succeed to connect with one laptop with Window 10

2° I can only connect to single Pylontech batterie, where I'm connected to Console port
trying to go with "united" option does not work and lead to error msg

BatteryView 3.0.28 really does not work with some FW versions. For example, v3 FW for the new chip from 2025.

On the other hand BatteryView 3.0.37 should work with almost everything, including above v3 FW. Available in the Forum Downloads section.

Troubleshooting:

1. Get the cable with the correct wiring. Ideally one that already worked for someone. Or the cable that works for connecting Pylontech to your Solar Assistant (if you are using SA).

2. Identify that the COM port is the correct one. When using USB2Serial, start the BW first, note what COM port numbers are being visible in the drop-down menu. Then exit, plug the USB2Serial into laptop, start BW again and note the new port that was not visible first time. That's the right port.

3. Some USB2Serial chips works better than others. Also, laptop might have corrupted drivers for a particular USB2Serial chip. FTDI should work okay, CH340 too, Prolific might be stubborn.

4. Use BW 3.0.37

5. Set computer locale to US English.

6. First try a connection to the single master battery. Use RS232, 115 200 baud. Do NOT check "united" or "parallel".

7. If the connection a single master battery does not work, there's an issue with some of the previous bullets.

8. If the connection to a single master battery works, then connect again, now with "united" option. Set the number of "Units" to EXACT number of bricks that you have daisy-chained with Link0/1 ports. Use console port on the MASTER battery of the stack ONLY.

9. If connection to a single master battery works but connection to "United" throws an error then you have a WRONG NUMBER of Units set in the BW. Sometimes the case is that last one or two batteries in the stack are not communicating with the master. If that's the case, then turn everything off and start all the batteries again, using the procedure from User Manual. The key is that once the master battery is started by pressing the RED button, then all the subsequent batteries should start automatically and indicate that with their green LEDBARs blinking.

Hope this helpes

Edited October 12, 2025Oct 12 by Youda

I had same problem with my LEOCH 48100-TB packs. The setup with RS232 according to the manual didn't work. Finally the supplier came up with the solution:

Create a communication bus with all RS485 ports on the packs in parallel and connect with an RS485 adapter to the laptop. Also needed to change the software to PmodbusToos V1.20. Each pack must have a different address set by the dip switches. This way I can remote monitor every pack individually but not simultaneously. There is no master, all packs have same priority.

Hello, I had no "United" reading problems with 4 US5000 V1.3 using BatteryView 3.0.29.

Now I added a further US5000 with V2 firmware and made this device being the master. Everything works fine with the Victron environment.

Single readout with BatteryView works, but not "United".

Even scanning with BatteryView 3.0.37 fails with "fail to resolve the buffer: of the 3trys".

Any ideas on this issue?

Many thanks in advance for your kind recommendations.

Edited October 29, 2025Oct 29 by Solartrapper

Hello

after a firmware update (V2.3 SN xxxxxxxC5xxxxxxx : US_E3_V2.3_Crc.bin) of my 10 Pylontech US 5000 with VRM Victron Cerbo GX, Single readout with BatteryView works well on each battery console port (v2.3 update ok), but "United" on master battery console port don't work.

scanning with BatteryView 3.0.37 "United" quantity 10 fails with "fail to resolve the buffer: of the 3trys".

Now batteryview request me Serial Number at startup everytime

2 with firmware V1.3

4 with firmware v2.0

4 with firmware v2.3

the serial number is no more visible on bar code (it was already the case on my 4 v2.3 batteries, only visible for v1.3 & 2.0)

Edited May 15May 15 by jfbo37

19 hours ago, jfbo37 said:

scanning with BatteryView 3.0.37 "United" quantity 10 fails with "fail to resolve the buffer: of the 3trys"

I've seen this issue in 2 cases:

1) There was a Link0/1-cable problem betwen the batteries in the stack.

2) Batteries in the stack had too different firmware from each other.

IMHO, this looks like a case #2. You need to flash all the batteries to the same FW version one by one. Just take care of chipset as old ones will have a different chip and therefore will use different firmware BIN image. But the ZIP flashing method should take care of this.