Quick Answer

When several LiFePO4 battery packs operate in parallel, each pack may have its own BMS and its own SOC, voltage, current, temperature and status data.

The key question is not simply whether all BMS units can communicate. It is: what battery information does the inverter receive from the multi-pack system, and what must be verified before commissioning?

A typical data path is: Individual Pack BMS → BMS Identification → Multi-Pack Communication → System Data Handling → CAN/RS485 Protocol → Inverter / EMS.

The most important distinction is simple: individual pack data is not automatically the same as the system-level information reported to the inverter.

1. How Does the Multi-Pack Data Path Work?

Start with each battery pack. Its BMS monitors pack-level information such as voltage, current, SOC, temperature, operating status and alarms. In a multi-pack system, the individual BMS units must also be identifiable so the system can distinguish one pack from another.

For supported DALY 4th Gen configurations, up to 16 battery packs can operate in parallel. The system supports automatic BMS addressing, internal RS485 communication, individual pack visibility, and CAN or RS485 communication toward the inverter.

Once this communication path is established, the next question is not whether the packs are online. It is what the information sent upstream actually represents.

2. Pack Data Is Not Automatically System Data

Suppose three parallel battery packs display SOC values of 90%, 82% and 78%. Seeing these three values confirms that the individual packs can be monitored. It does not, by itself, tell you what SOC value the inverter should receive.

The same distinction applies to other data. Before commissioning, the project should define how system-level information is handled rather than assuming that individual pack values are automatically converted into one universal system value.

Customer rule: Multi-pack visibility does not define system-level data handling. Do not assume a simple average or a universal limit/alarm rule.

3. Check the Inverter Requirement Before Configuring the BMS

Work backward from the inverter: Exact Inverter Model → CAN/RS485 Interface → Required Protocol → Required Battery Data.

Depending on the inverter and communication protocol, the required battery information may include SOC, voltage, current, temperature, alarms, operating status, and charge or discharge limits. The exact fields are not universal.

This is why a CAN or RS485 connector alone does not confirm compatibility. Interface compatibility, protocol compatibility and battery-data compatibility are three separate checks.

4. What Does DALY 4th Gen Support?

For supported multi-pack energy storage configurations, DALY 4th Gen provides the communication and monitoring functions needed to build the data path from individual packs toward the inverter.

Supported functions include up to 16 parallel packs, automatic BMS addressing, internal RS485 communication, individual pack monitoring, and CAN/RS485 communication with supported inverter protocols. Applicable protocols can be selected or configured through the relevant APP or PC software depending on the project configuration.

Available product materials reference inverter ecosystems such as Pylontech, Growatt, Deye, SRNE, Luxpower, Sofar, Sacolar and Voltronic Power. Compatibility should still be verified against the exact inverter model and applicable protocol requirement.

Multi-pack monitoring can show individual pack information such as pack number, state, voltage, current, SOC, CHG-MOS and DSG-MOS status. This visibility helps commissioning and diagnosis, but it should not be treated as proof of a universal system-level aggregation rule.

If your project requires a specific method for system SOC, system current, charge/discharge limits, alarm coordination or other upstream system-level information, confirm that behavior for the selected BMS configuration and inverter protocol before sample testing.

5. Multi-Pack BMS Integration Checklist

If the required system-level behavior cannot be documented, move it to project-specific technical verification instead of making an assumption.

6. What Should You Send DALY for Verification?

To verify a multi-pack BMS and inverter integration efficiently, prepare the following project information:

• Battery chemistry
• Series configuration
• Capacity per PACK
• Number of parallel PACKs
• BMS model or current requirement
• Exact inverter brand and model
• CAN or RS485 requirement
• Required communication protocol
• Protocol documentation, if available

Example: LiFePO4 + 16S + 100Ah/PACK + 4 PACKs in parallel + 150A BMS requirement + exact inverter model + CAN + required protocol.

FAQ

Does a CAN connection mean the BMS is compatible with the inverter?

No. A matching physical interface is only the first step. The communication protocol and the battery data expected by the inverter must also match.

If I can see the SOC of every battery pack, does that mean the inverter receives the correct system SOC?

Not necessarily. Individual pack visibility and the system-level SOC reported upstream are different questions. Verify the applicable BMS configuration and inverter protocol.

What information should I provide DALY for a multi-pack inverter project?

Provide the battery chemistry, series count, capacity per pack, number of parallel packs, BMS requirement, exact inverter model, CAN/RS485 requirement, protocol name and available protocol documentation.

Verify Your Multi-Pack BMS and Inverter Integration

Before sample testing or commissioning, send DALY your Battery Configuration + Pack Capacity + Number of PACKs + BMS Requirement + Inverter Brand/Model + CAN/RS485 + Communication Protocol.

DALY's technical team can then confirm the applicable communication configuration and project-specific data requirements.