A matching connector does not prove compatibility
CAN and RS485 describe communication layers, not a universal battery language. Two devices can use the same physical connector and still exchange different message formats, pinouts, baud rates or control logic. Never infer compatibility simply because both datasheets mention CAN or RS485.
Use the manufacturer compatibility list
Start with the inverter manufacturer’s current battery compatibility document and then check the battery manufacturer’s corresponding list. Record the exact battery module, control unit, inverter model and firmware range. If either manufacturer excludes the combination, treat it as unapproved until formal documentation says otherwise.
Firmware can change supported pairings
A hardware combination may require minimum inverter, battery-management-system or gateway firmware. Conversely, an old battery generation may not support a newer control mode. Capture software versions during commissioning so later troubleshooting can distinguish a wiring problem from a protocol or firmware mismatch.
Communication loss changes safe operation
Closed-loop lithium systems use the BMS to communicate state of charge, current limits, temperature and alarms. If communication fails, the inverter may stop charging/discharging or fall back to a restricted mode. Do not bypass BMS controls or substitute generic voltage settings unless the manufacturer explicitly supports that mode.
Keep the evidence with the system
Save the compatibility document, wiring diagram, termination requirements and commissioning screenshots. Use the battery-inverter compatibility guide and firmware compatibility checklist when evaluating a proposed pairing.
Record firmware and cable requirements
Compatibility can depend on more than the connector name. Record the battery firmware, inverter firmware, approved cable or pinout, termination requirements, device-address settings and any maximum battery-unit count stated by the manufacturers. Keep screenshots or commissioning records once communication is established. A future firmware change or replacement component is much easier to troubleshoot when the original working configuration is documented.