· SH Energy editorial
The battery is usually the easy part. What decides whether an expansion works is whether the packs can be addressed distinctly, whether the parallel bus and the inverter accept another unit, and whether the current shares evenly. All of that is answerable in writing before you buy.
1. What actually changes when you add a unit
A single pack is a battery. Two packs are a small network, and networks have rules. Adding a unit changes four things at once:
- Addressing — each pack needs its own identity on the parallel bus.
- Current sharing — charge and discharge current now splits between units, and it splits by resistance, not by goodwill.
- Cable and breaker sizing — the busbar and protection were sized for one unit.
- The inverter's view — the inverter has its own maximum, its own protocol behaviour and its own firmware assumptions.
Most failed expansions are a mismatch in one of those four, not a dead battery.
2. Addressing: the two-minute check that stops most of them
Parallel packs are distinguished by an address, usually set with a physical DIP switch on the unit. In our stackable configuration the addressing is a 4-position DIP switch, giving pack addresses from 1 to 15 — the same range the system ceiling is expressed in.
Two packs left on the same address is one of the commonest reasons a new unit “does not come up”. Nothing is broken; the system simply cannot tell the units apart. Set addresses before energising, photograph the switch positions, and record them on the commissioning sheet so the next engineer does not have to guess.
3. What the datasheet will and will not tell you
A datasheet can state the platform limit. For our stackable system it states expansion to up to 15 units in the stackable configuration, with the parallel bus on RS485 and inverter communication on CAN.
What that sentence does not mean: that fifteen units are right for your site. A platform limit is a ceiling, not a design. The binding constraint is usually one of these:
- The inverter's own maximum — it will cap the number of packs before the battery platform does.
- Current per pack — if the site's charge rate exceeds what the packs accept, the extra packs add runtime but not charging speed.
- The bus and protection — cable length and breaker rating are site-specific.
- Physical space and access — clearance for ventilation and service is not a datasheet number.
That is why the final count is confirmed for the exact configuration rather than quoted from a table.
4. Mixing an old pack with a new one
This is where buyers most often assume too much. “Same model number” is not the same as “confirmed compatible”. What matters:
- Cell batch and age — an aged pack and a new pack have different internal resistance and will not share current evenly on their own.
- Firmware — the two units must be on firmware versions the manufacturer confirms can run in parallel together.
- BMS behaviour — protection thresholds and derating logic must agree, or one pack will drop out first under load.
Ask for a written confirmation covering the specific pairing you intend: model, revision, firmware and batch, if the manufacturer tracks batches. If the answer is “it is the same model, so yes”, that is not a confirmation.
For the wider version of this question — what evidence should exist before two devices are paired — see four compatibility checks.
5. The expansion that looks fine and fails at commissioning
Three failure modes repeat:
Communication up, power down. The packs see each other on the bus, the app shows the new capacity, but the system derates under load because current is not sharing evenly. Usually a wiring or addressing asymmetry.
One pack drops out under surge. The older pack's protection trips first, the remaining pack takes the whole load, and the system shuts down under exactly the condition you bought it for.
The inverter refuses the second pack. Frequently a firmware or protocol issue, and it is worth checking before delivery rather than after installation.
6. Six checks before you expand
7. Why "expandable" is a planning word, not a promise
Buying expandable hardware and planning the expansion are different things. If the site may grow, three decisions are cheaper to make at the start than later: leave physical clearance for another unit, size the busbar and protection for the eventual total, and record addresses and firmware from day one. None of those cost much when the wall is open; all of them cost a site visit afterwards.
For the module platform itself, see SH-Stack. For the inverter side, see SH-Inverter.
FAQ
Can I add a second battery to an existing system later?
Sometimes, and the deciding factor is rarely the battery. Addressing, the parallel bus, cable and breaker sizing, firmware and whether the inverter accepts a second pack all have to line up. Each of those is answerable in writing before you buy.
Does a higher parallel limit mean the system will work at that limit?
No. A configuration limit is the maximum the platform supports, not a promise for your site. Current sharing, cable length and the inverter's own limit usually bind first, which is why the final number is confirmed for the exact configuration.
What does DIP-switch addressing do in a parallel battery system?
It gives each pack a unique address so the system can tell them apart on the parallel bus. Two packs set to the same address is one of the commonest reasons an expansion refuses to start, and it is a two-minute check before energising.
Do older and newer packs of the same model mix?
Only within what the manufacturer confirms in writing for that model and firmware. Mixing batches is a chemistry and firmware question, not a marketing one, so ask for the confirmation per case rather than assuming the model number is enough.
Talk through an expansion
Send the existing model, the proposed addition and the site's load to jimmy@sunhongenergy.com, or message the desk on WhatsApp. Model-level documents are on the documents centre.
Scope
This guide explains how expansion is decided and verified. Parallel limits, addressing ranges and firmware compatibility are confirmed per model and configuration in writing; platform limits describe what the platform supports, not what a specific site should install. No prices, lead times or warranty terms are stated here.