A battery-inverter CAN RS485 compatibility checklist should identify the exact equipment, the supported battery protocol, the firmware and the evidence needed to approve that combination. Matching port names alone cannot answer whether a system will exchange the information needed for controlled charging and discharging.
For an installer or distributor, the useful deliverable is a documented pairing that another technician can reproduce. Start with the intended battery configuration and inverter model, then record every condition attached to the compatibility claim.
Separate the interface from the application protocol
Texas Instruments explains that RS485 defines a physical layer; applications use protocols above it. A battery’s RS485 port could serve monitoring or service functions rather than the inverter control function required by your project. Ask what that particular port actually supports.
For CAN, request the supported battery application protocol and its revision as well. A CAN connector label does not establish that the receiving equipment interprets the battery’s messages correctly. Avoid choosing a generic communication cable solely because the plugs fit.
Build a pairing record before ordering
Use one record for each proposed combination. If the inverter has regional variants, identify the actual variant being purchased.
| Item | Evidence to request | Approval question |
|---|---|---|
| Battery identity | Pack model, BMS hardware and firmware | Does the evidence describe this build? |
| Inverter identity | Model, regional variant and firmware | Is this exact version covered? |
| Communication | Protocol name, revision and port purpose | Can both parties identify the same implementation? |
| Cable and configuration | Approved cable reference and setup document | Can the installation team reproduce the arrangement? |
| Battery arrangement | Supported module count and system topology | Does the proposed project meet those conditions? |
| Control behavior | Required signals, limits and response evidence | Has the complete pairing been evaluated? |
As an example of conditional compatibility documentation, Victron’s BYD integration guide specifies system components, firmware requirements and battery configuration conditions. It illustrates the level of detail to seek; it provides no approval for an evjrich battery.
Check electrical suitability separately
Successful communication does not prove that the battery can support the inverter’s demand. Request the permitted voltage range, charge and discharge limits, peak duration and any conditions attached to a multi-module arrangement. Keep nominal stored energy separate from continuous output capability.
Use the Products overview to identify the battery format under discussion. Then obtain the project-specific specification rather than treating a catalogue communication entry as confirmation of all supported inverters.
Define what the integration evaluation must show
Before a sample evaluation, agree which information the inverter must receive and how the system should respond. Depending on the design, the review may need to cover state of charge, charge and discharge permissions, current limits, alarms and the response when communication is lost. These are questions for the equipment suppliers and the responsible system engineer.
Ask the test owner to record the configuration, operating condition, expected response and observed response. A screenshot showing a battery icon is insufficient evidence that limit handling and fault reporting behave correctly. Any abnormal-condition evaluation needs an approved professional procedure; this guide does not prescribe fault injection or wiring changes.
Close the approval and control later changes
Give each open item an owner and a decision date. If the protocol documentation is unavailable, record compatibility as unconfirmed and agree what supplier evidence or supervised evaluation could resolve it. Do not convert a sales statement into a technical approval.
Keep the accepted firmware and cable references with the project record. Review later substitutions against that record, including changes to a gateway or battery module configuration. An earlier successful pairing is evidence about that configuration, rather than permission for every future version.
Use Customization to define the battery interface requirements. Share the inverter identity, firmware information and pairing matrix when you discuss your requirements via B2B enquiry, so the next discussion can address the specific evidence still needed.