Short answer: a stack of Pylontech batteries in parallel needs two separate chains: power cables (positive and negative, sized for the current) and a communication chain from LINK PORT 1 of one battery to LINK PORT 0 of the next. Each battery needs its own address. The inverter only ever sees the total; to see each battery and each cell, read the master battery's Console port, which works for up to 16 batteries, models and ages mixed.
What "parallel" means for a Pylontech stack
Pylontech's low-voltage modules (US2000, US3000, US5000 and the Force-L1 family) are designed to be stacked. Put two or more together, wire them correctly, and the inverter sees one bigger battery instead of several small ones. That is the whole idea: more kWh and more current from units small enough for one person to carry.
This guide is about the low-voltage US series. Pylontech's high-voltage towers (Force H2, H48050) use a different, rack-based layout; they have their own guide.
Two chains, two jobs: power and communication
Every battery you add needs two connections, and it is easy to get one right and forget that the other matters just as much:
- Power. Positive and negative cables in parallel, battery to battery, carrying the real charge and discharge current. Undersized or damaged power cables are a fire and performance risk long before they are a monitoring problem.
- Communication. An RJ45 chain through the LINK ports that lets the batteries agree on who is master, share their state, and appear to the inverter as one unit. This is the chain that fails silently: no smoke, no smell, just an inverter that stops seeing part of the stack.
The rule for the communication chain is simple and often got wrong: the cable leaves LINK PORT 1 on the master and goes into LINK PORT 0 on the next battery, then 1 → 0 again all the way down. Wired the other way round, the master never sees the others, and every tool (inverter included) reports a single battery. The full sequence, with photos, is in our installation guide.
The master battery talks to the inverter through its CAN or RS485 port. Its Console port stays free, and that is where a monitor plugs in. The other batteries only talk to their neighbours.
Addressing: how each battery knows which one it is
Batteries in the same stack need a unique address so the master can tell them apart when it reports per-module data. On most US models it is a DIP switch on the case; some newer models address themselves over the LINK chain. Either way, two things cause trouble again and again: two modules left on the same address, and an address changed after the stack was commissioned.
Mixing models and ages
Mixing a US2000 with a US3000C or a US5000, or batteries bought years apart, works. Customers ask us about it regularly: one had a US3000C master with four US2000C behind it, and all five are read and shown one by one; another mixed US2000 and US3000 of several generations, with the same result. What mixing does change is how the stack ages: the smallest or oldest module works harder and drifts away from the others faster. That is exactly why it is worth watching each battery separately rather than the total.
The cable that quietly breaks a stack
The RJ45 and power cables in the Pylontech box are sized for one layout: batteries stacked right on top of each other. Real installations are rarely that tidy. A rack on a different wall than planned, a battery added later where the original cable does not reach, an outdoor cabinet where an indoor cable has no business being. People then grab a generic network cable or a random pair of power cables from a drawer, and that is where a stack starts throwing intermittent communication faults or, worse, runs power cables too small for the current they now carry.
Pylon-Monitor does not sell cables, but our sister companies do: ParallelCables.com and Cables-Solaires.com make correctly rated Pylontech parallel cable sets, with Amphenol connectors and the right gauge for the current, in 48 cm, 70 cm, 1 m and 2 m long-reach pairs, for stacks that do not fit the standard layout.
Common wiring mistakes as a stack grows
| Mistake | What it causes |
|---|---|
| LINK chain wired 0 → 1 instead of 1 → 0 | The master sees only itself. Inverter and monitor both report one battery. |
| Two modules on the same address | Two modules report as the same unit; per-module readings become unreliable or one module disappears. |
| Mixed models or capacities | Works, but the stack ages unevenly: the smallest or oldest module cycles harder and drifts faster. |
| Power cable too thin or too long | Voltage drop under load, hot connectors, and in the worst case a safety issue. Not the place to improvise. |
| Communication cable under strain | Works on the bench, fails now and then once the cabinet is closed and the cable is pinched or stretched. |
| Inverter cable in the wrong socket | The stack does not present itself properly on the CAN/RS485 side. Explained in our inverter guide. |
What monitoring a stack shows you
This is where the two chains matter again. Your inverter reads the CAN/RS485 link, and to it a stack of one battery and a stack of sixteen look the same: one voltage, one current, one SOC. Anything happening to one module inside the stack is invisible from there. That is a protocol limit, not a software one.
The detail per module only exists on the Console side. Pylon-Monitor reads it from the master's Console port and reports up to 16 batteries one by one: SOC, SOH, voltage, current, state and temperature for each, with a battery selector on the dashboard, plus every cell voltage of all 16. In a stack, that per-module view is the difference between "the stack is fine" and "module 7 is ageing faster than the rest".
Before you switch on a new or extended stack
- Every module has its own address. Checked, not assumed, especially after adding or moving one.
- The LINK chain goes 1 → 0 from the master downwards.
- Power cables are rated for the stack's real current, not "the same as before".
- Communication cables reach without tension, loops or pinching when the cabinet closes.
- The inverter is connected to the master's CAN or RS485 port; the master's Console port stays free for a monitor.
- Modules run the firmware version Pylontech requires when you mix capacities.
Once it runs, the same eight-point check applies to each module, not just to the stack as a whole. That is the whole case for reading a stack battery by battery rather than as one number.
Frequently asked questions
- Can Pylontech batteries be connected in parallel?
- Yes — that's how a Pylontech bank works. Low-voltage US-series modules (US2000, US3000, US5000, Force-L1) are designed to be wired in parallel, with a shared power connection and a Console/Link communication chain so the inverter sees one combined battery instead of several separate ones.
- How many Pylontech batteries can be chained together?
- It depends on the model and the inverter's own limit, but stacks of well over a dozen low-voltage modules are common. Pylon-Monitor, for instance, reads and reports up to 16 batteries individually from the master unit's Console port.
- Do all the batteries in a parallel bank need to be identical?
- Not strictly, but same-model, same-age batteries age far more evenly. Mixing capacities or generations works in most cases but the smaller or older unit tends to cycle harder and drift from the rest of the stack faster — worth watching per-module rather than assuming.
- Why does my inverter only show one battery when I have several wired together?
- Because the inverter reads the CAN/RS485 link, which deliberately presents the whole stack as a single virtual battery — one voltage, one current, one SOC. Per-module detail only exists on the Console chain, which the inverter doesn't use.
- What usually causes a communication fault in a Pylontech multi-battery setup?
- Far more often a cabling issue than a failed battery — an RJ45 run that's too long, stressed, or of the wrong spec for the layout, or an address collision after a module was added or moved. Checking the physical cable run is the first step before suspecting a module itself.
Pylon-Monitor reads every battery in your stack separately: SOC, SOH, voltage, current and temperature for each, up to 16 batteries, from the master's Console port alone.
Order now — €59 One-time purchase, €59 total — no VAT, no subscription.