Skip to main content
Skip table of contents

Goodwe ET to support multiple battery string

Overview

The GW25K-ET, GW29.9K-ET and GW30K-ET inverters have two battery input ports, allowing multiple battery strings to be connected simultaneously. The LIFEPOWR EMS supports this configuration with the following constraints.

Limitations

The EMS manages both battery ports as a single combined battery. This means:

  • State of Charge is reported as the average across all connected strings

  • Charge and discharge limits apply to the combined system — per-port limits are not configurable

  • If strings have asymmetric SoC, the EMS operates on the average; balancing between ports is handled by the inverter hardware

  • Individual port monitoring is not available in the portal

  • Asymmetric and mixed-model configurations are supported via "Unsupported Battery" — see the setup procedure below for how to calculate the correct combined parameters

  • Use "Unsupported Battery" when configuring dual-port installations. Selecting a named battery model will cause portal validation to reject a combined pack count that exceeds the single-port maximum. "Unsupported Battery" has no such limit and requires manually entering the electrical parameters from the battery datasheet

Setup Procedure

1. Physical installation

Connect battery strings to both battery input terminals following the Goodwe ET installation manual.

2. Configure the battery in the LIFEPOWR portal

In Step 9 of the device configuration wizard, select "Unsupported Battery" as the battery model and fill in the fields as follows.

Do not select the specific battery model (e.g., Pylontech Force H3, GoodWe Lynx Home F). The known-model entries have pack count limits designed for a single battery input and will reject configurations that exceed them.

Set Battery Pack Count and Cells Per Battery Pack both to 1. This treats the entire combined system as a single virtual unit. Calculate the remaining fields as follows:

Cell Nominal Voltage — always use 400 V.

Cell Capacity [Ah] — divide the total energy of the combined system by 400:

CODE
Cell Capacity = Total system energy [Wh] ÷ 400

Cell Maximum Current [A] — divide the combined battery system's maximum power (the lower of total charge and total discharge capability across both ports) by 400:

CODE
Cell Maximum Current = min(combined max charge power, combined max discharge power) [W] ÷ 400

The combined max power is the sum across all towers on both ports. For each tower, multiply the per-module max current by the tower's string voltage.

Battery Description — enter the battery brand, model, and a note indicating the dual-port setup (e.g., Pylontech Force H3 — 2 ports × 3 towers × 5 modules).


Example — GW25K-ET, 2 ports, each with 3 Pylontech Force H3 towers of 5 modules:

  • Total energy: 2 ports × 3 towers × 5 modules × 5.12 kWh = 153.6 kWh = 153 600 Wh

  • Combined max power: 6 towers × (50 A × 512 V) = 153 600 W (charge = discharge for H3)

Field

Value

Battery Pack Count

1

Cells Per Battery Pack

1

Cell Nominal Voltage

400 V

Cell Capacity

384 Ah (153 600 ÷ 400)

Cell Maximum Current

384 A (153 600 ÷ 400)

Battery Description

Pylontech Force H3 — 2 ports × 3 towers × 5 modules


Example — GW25K-ET, asymmetric: port 1 with 2 Pylontech Force H3 towers of 5 modules, port 2 with 2 towers of 3 modules:

  • Port 1 max power: 2 towers × (50 A × 512 V) = 51 200 W

  • Port 2 max power: 2 towers × (50 A × 307.2 V) = 30 720 W

  • Total energy: (2 × 5 × 5.12 kWh) + (2 × 3 × 5.12 kWh) = 81.92 kWh = 81 920 Wh

  • Combined max power: 51 200 + 30 720 = 81 920 W (charge = discharge for H3)

Field

Value

Battery Pack Count

1

Cells Per Battery Pack

1

Cell Nominal Voltage

400 V

Cell Capacity

204.8 Ah (81 920 ÷ 400)

Cell Maximum Current

204.8 A (81 920 ÷ 400)

Battery Description

Pylontech Force H3 — port 1: 2×5 modules, port 2: 2×3 modules

3. Set SoC limits

Configure minimum and maximum State of Charge as usual. These apply to the combined system.

4. Verify after commissioning

Confirm in the portal that:

  • Battery SoC is visible and stable

  • Charge and discharge power reflects the total combined capacity

What is and is not supported

Feature

Supported

Both battery ports active simultaneously

Yes

Combined charge / discharge management

Yes

Combined SoC reporting

Yes

Per-port SoC monitoring

No

Per-port charge / discharge limits

No

Mixed battery models across ports

Yes — use "Unsupported Battery" with the combined calculation procedure above

Asymmetric tower counts across ports

Yes — use "Unsupported Battery" with the combined calculation procedure above

Asymmetric module counts across ports

Yes — use "Unsupported Battery" with the combined calculation procedure above

Combined pack count exceeding per-port schema limit

Yes — use "Unsupported Battery" with manually entered specs

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.