Battery-Inverter Protocols — CAN, RS485 & Modbus

Closed-loop communication means the inverter receives live instructions and status from the battery BMS. Instead of guessing from voltage, the inverter can use battery-reported state of charge, charge current limit, discharge current limit, maximum voltage, minimum voltage, temperature warnings, alarm states and sometimes cell-level protection data. This is the preferred setup for many modern lithium batteries.

Open-loop or user-defined voltage mode means the inverter charges and discharges based mainly on voltage thresholds and current settings. This can work when correctly configured, but it is less intelligent. LiFePO4 batteries have a very flat voltage curve, so voltage alone can be a poor state-of-charge indicator. A system may look stable until it suddenly reaches a BMS cutoff.

Closed-loop mode is especially useful for home batteries because it helps prevent overcharge, over-discharge and charge current errors. It also improves monitoring accuracy. However, closed-loop mode only works when the battery and inverter use a compatible protocol profile. “CAN” on both devices is not enough if the message format is different.

When open-loop may still be used

Some off-grid systems, DIY battery packs or older inverters operate in voltage-control mode. In those cases, settings must be conservative and based on the battery manufacturer’s charge voltage, discharge cutoff, current limits and temperature restrictions. Extra monitoring is recommended because the inverter may not see detailed BMS alarms.

CAN bus is common in lithium battery systems because it is robust, fast and suitable for real-time control messages. Many rack batteries and high-voltage home battery systems use CAN to communicate with hybrid inverters or gateways. The battery may send messages such as SOC, SOH, charge current limit, discharge current limit, voltage, current, temperature and alarm state.

In practice, CAN compatibility depends on more than the port. You must check the CAN profile supported by the inverter. Many inverters include profiles for specific battery brands such as Pylontech, BYD, Dyness, Huawei, LG, SolarEdge, GoodWe-compatible batteries or generic lithium profiles. If the wrong battery profile is selected, the inverter may not detect the battery or may show communication alarms.

CAN wiring often uses an RJ45 connector in residential battery systems, but it is not Ethernet. The pins may carry CAN-H, CAN-L and sometimes wake-up or ground references depending on the manufacturer. Some systems require a special cable, not a straight-through patch lead. Termination and cable length can also matter, especially with multiple devices.

Common CAN settings to confirm

• Battery profile selected in the inverter menu.
• Correct CAN port, not the RS485 or Ethernet port.
• CAN-H and CAN-L pinout.
• Baud rate required by the battery.
• Termination resistor requirement.
• Master battery DIP switch or address setting.

RS485 is not a battery protocol by itself. It is an electrical standard for serial communication over differential wires, often labelled A and B or D+ and D-. It is popular because it works over relatively long cable runs, supports multiple devices on a bus and is common in industrial environments. In solar and battery systems, RS485 is used for smart meters, inverter monitoring, battery data ports and Modbus RTU communication.

For lithium batteries, RS485 may be used for inverter communication, battery-to-battery communication, computer monitoring or firmware tools. Some batteries use one RJ45 port for CAN to the inverter and another RJ45 port for RS485 battery linking. Others allow RS485 as an alternative communication method if the inverter supports that battery protocol.

The most common RS485 problem is polarity or parameter mismatch. If A/B are reversed, or if baud rate, parity, stop bits or slave address are wrong, communication fails. Some devices label A and B differently, so installers sometimes need to follow the manual rather than assuming colors or pin numbers.

RS485 best practices

• Use twisted-pair cable for differential lines.
• Keep polarity consistent from end to end.
• Set unique addresses when multiple devices share a bus.
• Use termination where required by cable length and topology.
• Avoid star wiring unless the manufacturer supports it.
• Keep communication cables away from noisy AC/DC power cables where practical.

Modbus is a widely used open communication protocol in industrial automation and energy systems. It is often used to read and write registers such as voltage, current, power, energy, temperature, alarms and setpoints. In the battery-inverter world, Modbus is common for monitoring and EMS integration, and it can also be used for control where the manufacturer exposes supported registers.

Modbus RTU usually runs over RS485 serial wiring. A master or client sends a request to a slave device address, and the device returns data from its register map. Modbus TCP runs over Ethernet/IP networks and is common for data loggers, gateways, building management systems and advanced energy management systems.

The critical point is that Modbus needs a register map. Even if two devices both support Modbus, one system may store battery SOC at a different register than another. Some registers are read-only, while others allow control. Writing the wrong register or using the wrong scale factor can cause bad data or unsafe behavior. For this reason, Modbus integration should be done from official documentation.

Where Modbus is useful

• Reading inverter power, energy, status and alarms.
• Logging battery SOC and voltage through a gateway.
• Connecting an inverter to an energy management system.
• Setting power limits or export controls where supported.
• Integrating solar, batteries and loads in commercial systems.

If the inverter shows “BMS communication fail,” “battery not detected,” “CAN fault,” “485 comm fail” or “lithium battery disconnected,” start with basic checks. Make sure the battery is powered on, the master battery is selected correctly, the communication cable is plugged into the correct ports, and the inverter is set to the correct battery profile. Many faults are solved by moving the cable from an RS485 port to the CAN port or replacing a straight-through cable with the manufacturer’s required pinout.

Next, check addresses and firmware. Multi-battery stacks often require one master battery with a specific DIP switch setting, while the other modules use link ports or sequential addresses. If firmware is old, the inverter may not support the latest battery protocol. Some batteries also need a wake-up signal or a minimum voltage before communication begins.

For Modbus problems, use the official register map. Confirm slave ID, baud rate, parity, stop bits, function code, register offset and scaling. Some documentation uses one-based register numbering while software libraries use zero-based addressing. This can make every register appear “one off.”

Fast diagnostic flow

1. Check battery and inverter are both powered and awake.
2. Confirm exact battery model is selected in inverter settings.
3. Verify cable pinout from both manuals.
4. Check DIP switches, address and master battery setting.
5. Update inverter and battery firmware if compatibility notes require it.
6. Read live values: SOC, voltage, current and alarms.
7. If values are wrong, stop and recheck protocol/register map before operating under load.

Battery communication is a safety-related function. If the inverter cannot see BMS alarms, it may continue trying to charge or discharge when the battery wants to stop. A good BMS will still protect the cells by disconnecting internally, but repeated cutoffs can stress equipment and cause nuisance shutdowns.

Warranty claims can also depend on approved integration. If a battery is used with an unsupported inverter, wrong protocol, wrong cable or voltage-only mode against manufacturer instructions, support may be limited. Always save commissioning screenshots, battery profile settings, firmware versions, cable pinout notes and serial numbers.

For larger home or commercial systems, communication wiring should be documented like power wiring. Label the ports, keep a copy of the pinout, record Modbus addresses, and note whether the battery is running closed-loop CAN, closed-loop RS485 or open-loop voltage mode.