Youda

11th battery has to be totaly separate, in terms of data communication. Nothing in its LinkPorts0/1, nothing in CAN/RS485 ports.Only Console port can be connected to a computer with BV or SA running. But since you dont have RJ11 console cable, you can do just like you said - put it in the group, after you remove those 2 bad.

What about battery #11 - that one is working okay? You might use BatteryView for checking that. But you would need RJ-11 usb to serial cable...

Analog CT have just 2 wires normally. Anything based on a twisted pair should be okay. Just keep in mind that CT is direction sensitive. If the export reading will be incorrect, just open the CT and clamp it in reverse direction on that wire. (Some CTs have an arrow mark on the body and the orientation is noted in the manual)

Yeah, that's normal. I assume that those three US3000C's are newer than the rest of batteries and therefore their internal resistance is lower. That's the reason why they are suppling more current during discharge.....and receiving more current during charge.

CT needs to be installed on the line from the grid (meter) to the house. The current going from the inverter to the house loads must NOT pass through CT:

Oh yes - there was a V2.9 firmware for US2KBPL released, that had "V2.8" written inside. I bet that you flashed this version. There should be a file named US2000BPLS_V2.9_Crc.bin somewhere in the Pylontech Firmware Bundle and this should report as V2.9 correctly. Both files are dated as 21-04-29. On the other hand, there's absolutely no difference in functionality between the two files. It's just that version number and CRC. BTW: The most recent FW for US2KBPL that I have is us2000B_Plus_V3.4_Crc.bin dated 21-08-07. So maybe you want to flash this one directly.

Hi Simon, how are your batteries after a week? Any new discovery?

Nice. Let's see how the SOC of individual batteries will change during this night.

Oh yes. You must power OFF/ON all the pylontech batteries whenever you change DIP switch settings or whenever you change cables between the batteries. The BMS reads this and initializes itself accordingly only after reboot. Rewiring on the fly is not possible.

Turn all the batteries OFF Remove ALL data cables, except the one leading to SA. Connect batteries together with the UTP cables wired like this: Turn all the batteries ON one by one. Start with the master (the one having connection to SA), then follow the UTP cable and turn each battery on.

Ok, that might be even better for the wiring. Let me draw you a template. And what type of USB to console cable you have?

I assume that: First two banks are made entirely of 4x US3000A 3rd bank is made of 3x US3000C You are not able to shuffle batteries around, physically If that's the case then this is the way how to daisy-chain them: For now, there's now way how to daisy chain 8th US3000A. Just skip it. Double-check the USB-to-console cable type that you have. There are two types: 1) USB to RJ-11 (works with US3000A) 2) USB to RJ-45 (works with US3000C) You need USB to RJ-45 cable for the above scenario.

@Vaughn Kretzmann according to the specsheet, inverter SUN-12K-SG04LP3-EU has 2 MPPT trackers, equipped with 3 physical inputs. Just put your panels into PV1 and you are okay. Use one pair of MC4 +/- terminals. Leave PV2 empty, for the future use. 17 Amps is not an issue for a single MC4 connector with a 6mm2 solar cable, therefore you don't need to combine both +/- terminals of PV1 together. Just make sure the MC4 crimp is done correctly and there's a good contact of male and female connectors when plugged in. BTW: This setup of having two different MPPT inputs with 3 sets of terminals is quite common these days (at least in Europe). PV1 is meant for combining two strings, East + West. PV2 is meant for South string. (Yes, we face our panels South in the Europe).

oh my....

Oh my, that's really 25-30kWh every day! What are you doing with all that electricity? Mining Bitcoin? Charging EV? Or is it the Air Condition maybe? If that's A/C, then your consumption should go down in the winter, I suppose. Anyway, I would suggest to try being disconnected from the grid for as long as possible, and get some consumption stats for the 1st year. Then you can decide what to upgrade, if anything. Just remember - speaking of solar, the only thing that generates electricity are the panels. So there's no point in increasing capacity of batteries if you lack PV generation each and every day for a week or two. Batteries will help you bridge a day or two, but not a week or month.

Are you sure? That would be 30kWh/day. Not only that's a lot, but your current system should not be able to provide so much during those cloudy days. Can you double-check the numbers for different days, as @JayMardern suggested, please?

Assumptions: all the panels are facing north, with a slope at least 15° no shading of panels with trees, buildings etc daily consumption around 10 000 Wh (based on 40% of 15kW battery remaining in the morning after a cloudy day) Looks like you will be good, even during winter: https://re.jrc.ec.europa.eu/pvg_tools/en/tools.html There will be a couple of days when your battery will run flat (below 20%), but you can bridge this with a genset easily. Just really watch your daily consumption: With the assumed 10kWh/day it's okay (as seen above). With 15kWh/day of consumption there will be 4% of days with the empty battery. And 20kWh/day is not feasible with the current system (you would need to double the amount of panels and add another 5kWh of battery at least). Good luck! Youda

for example something like this: https://scoop.co.za/linkbasic-3-meter-utp-cat5e-flylead-grey.html

This story deserves to be turned into a movie!

Normally SA uses USB-to-serial cable that goes into serial port on the master and polls the BMS via CLI. On the battery, serial port is labeled as CONSOLE, while on the LV HUB serial port is labeled as RS232. For a shame, CLI of the LV HUB is a bit different than the CLI of master BMS. You can try it, but I would not expect too much. USB-to-CAN cable is not a good option here: It works with LV HUB, but you will lose a ton of information when compared to CONSOLE/RS232/CLI method, since the CAN protocol contains just an aggregated info like total SOC, total SOH etc. There's no detailed info about the SOC of individual batteries, nor individual cell votages etc. when CAN protocol is used.

To be honest, it's not ICM's fault. AFAIK, for Pylontech only the master battery tracks SOH and it's System SOH. (CLI command "pwrsys") Newer models, for example US3000C, have a SOH Counter for every battery, but it's empty. (CLI command "stats" followed by a number of battery you want to query) Luckily, at least the Cycle Count is tracked per battery

Good. I see that you have RCT and Infinisolar in your setup. Not sure whether they are combined in parallel or standalone, but this is reality: If parallel, then they are not able to talk to Pylontech If standalone, one of them can be connected to LV HUB via RS485 and a special RS485 BMS card (aka Goldfinger) from Voltronic. But I tried that in the past and it sucked. Not worth the hassle. Just a note: in your setup the LV HUB is completely useless. If it is not being used by the inverter nor by the Solar Assistant then there is no point of having it in the system. Focus on creating one large group and connecting its master to the SA.

Pylontech US3000 after 6 years of usage:

Hi guys, I've realized that my first Pylontech battery will be 6 years old this March, so I've pulled some stats on the SOH and Cycles to share together with my thoughts. CC = 52.5V CV = 52.5V 8x US3000 System SOH : 96 % Power Volt Curr Tempr Tlow Thigh Vlow Vhigh Base.St Volt.St Curr.St Temp.St Coulomb Time B.V.St B.T.St 1 50955 -260 23000 20000 21000 3390 3399 Dischg Normal Normal Normal 100% 2025-01-30 22:16:53 Normal Normal 2 50965 -256 23000 20000 21000 3390 3400 Dischg Normal Normal Normal 100% 2025-01-30 22:16:52 Normal Normal 3 50970 -260 23000 20000 20000 3392 3402 Dischg Normal Normal Normal 100% 2025-01-30 22:16:52 Normal Normal 4 50948 -252 23000 20000 20000 3387 3399 Dischg Normal Normal Normal 100% 2025-01-30 22:16:52 Normal Normal 5 50969 -256 23000 20000 20000 3389 3399 Dischg Normal Normal Normal 100% 2025-01-30 22:16:52 Normal Normal 6 50975 -262 22000 20000 20000 3392 3400 Dischg Normal Normal Normal 100% 2025-01-30 22:16:52 Normal Normal 7 50959 -268 22000 19000 19000 3391 3399 Dischg Normal Normal Normal 100% 2025-01-30 22:16:52 Normal Normal 8 50945 -260 21000 18000 18000 3388 3398 Dischg Normal Normal Normal 100% 2025-01-30 22:16:52 Normal Normal CYCLE Times : 267 CYCLE Times : 518 CYCLE Times : 521 CYCLE Times : 523 CYCLE Times : 529 CYCLE Times : 520 CYCLE Times : 511 CYCLE Times : 501 8x US3000C System SOH : 98 % Power Volt Curr Tempr Tlow Thigh Vlow Vhigh Base.St Volt.St Curr.St Temp.St Coulomb Time B.V.St B.T.St MosTempr M.T.St 1 50890 0 22100 19900 19900 3387 3396 Idle Normal Normal Normal 100% 2025-01-30 23:52:12 Normal Normal 20600 Normal 2 50903 -203 22300 19900 20200 3378 3397 Dischg Normal Normal Normal 100% 2025-01-30 23:52:10 Normal Normal 21000 Normal 3 50897 -256 23300 19700 20100 3386 3396 Dischg Normal Normal Normal 100% 2025-01-30 23:52:08 Normal Normal 21300 Normal 4 50906 -256 22300 18900 19300 3386 3396 Dischg Normal Normal Normal 100% 2025-01-30 23:52:08 Normal Normal 20600 Normal 5 50895 -258 22000 19000 19400 3385 3395 Dischg Normal Normal Normal 100% 2025-01-30 23:52:08 Normal Normal 20200 Normal 6 50896 -266 21900 18300 18600 3385 3397 Dischg Normal Normal Normal 100% 2025-01-30 23:52:08 Normal Normal 19900 Normal 7 50896 -260 20900 17900 18200 3386 3395 Dischg Normal Normal Normal 100% 2025-01-30 23:52:08 Normal Normal 19200 Normal 8 50901 -264 20600 17100 17500 3387 3397 Dischg Normal Normal Normal 100% 2025-01-30 23:52:08 Normal Normal 18900 Normal 9 - - - - - - - Absent - - - - - - - 10 - - - - - - - Absent - - - - - - - 11 - - - - - - - Absent - - - - - - - 12 - - - - - - - Absent - - - - - - - 13 - - - - - - - Absent - - - - - - - 14 - - - - - - - Absent - - - - - - - 15 - - - - - - - Absent - - - - - - - 16 - - - - - - - Absent - - - - - - - CYCLE Times : 140 CYCLE Times : 141 CYCLE Times : 246 CYCLE Times : 233 CYCLE Times : 240 CYCLE Times : 249 CYCLE Times : 249 CYCLE Times : 247 At a first look, it's not that bad with 96% SOH on a 6yrs old battery. But on the other hand, it's been 4% down for just roughly 500 cycles it made in that time. If linear, then after around 2500 cycles made in total, it will be at 80% SOH. If 500 cycles took me 6yrs then after 2500 cycles done in total the battery will be 30 years old. No way the battery will last for that long. Based on this, I would say that the battery will die of age well before it dies on cycles. What do you think? Youda

Great. So the SolarAssistant is connected to the Console (RS232) port of the Bank1 master. That makes sense. It also means, that you will not be able to see in SA anything else than the batteries that are in Bank1. If you want to see more batteries in the SA, you will need to make Bank1 larger. For example with that standard computer 3m UTP Cat5E cable. Q: Is inverter connected to the LV HUB somehow? For example via CAN or RS485.