For battery equipment suppliers, inverter partners and energy storage integrators, this service addresses communication differences between an existing BMS and a target inverter. Work covers application protocols, data validity, state interaction and fault recovery. A project can start with a prototype on a customer-supplied board. Supported models, firmware and functions depend on project documentation and device testing.
Applicable Tasks and Project Inputs
Typical tasks include connecting an existing battery and BMS to a different inverter, or converting battery data into messages recognized by the target device. Inputs include both device models and firmware, the actual CAN protocols, connector pinouts, supply and grounding conditions, message samples, test equipment and functional boundaries. RS485 is included only when separately specified.
Development Work Packages
| Work Package | Review and Development | Possible Deliverables |
|---|---|---|
| Protocol review | Frame format, identifiers, node roles, fields, units, direction, periods and timeouts | Protocol differences, missing inputs and functional scope |
| Data and state mapping | Voltage, current, SOC, temperature, permitted limits, alarms and enable states | Mapping table, validity rules and samples |
| Gateway firmware | Receive and transmit scheduling on both sides, configuration, logs, watchdog and recovery | Agreed firmware, build and flashing instructions |
| Prototype integration | Startup, normal interaction, link loss, stale data and recovery | Test cases, logs, issue list and milestone findings |
Dual CAN and Board Requirements
A dual CAN gateway needs two independently usable controller, transceiver and interface resources, with bus parameters reviewed separately. Two connectors do not prove the presence of two independent CAN controllers. Keeping networks separate also does not establish galvanic isolation. Customer-supplied boards require schematics, component details, board revision and driver information before firmware and hardware changes are scoped.
Milestone Delivery and Acceptance
Freeze the protocol and functional scope before field sample checks, prototype integration and testing on the agreed devices. Acceptance records identify equipment versions, board and firmware, input messages, expected states, actual outputs and recovery behavior. An SOC display is one check; limits, alarms, enable states, timeouts and recovery rules also need verification. Thresholds and run duration are defined in the project test plan.
From Prototype to a Custom Gateway
After prototype validation, a separate stage can assess a custom PCB, isolation and interface protection, enclosure, materials, samples, programming and production tests. Software, hardware design, sample materials, device integration and small batch manufacturing have separate scope and cost items. Prototype communication alone does not establish product or batch acceptance.
Protection Responsibilities and Project Information
The communication gateway does not replace BMS protection, battery contactor logic or the inverter safety mechanisms. Define which device generates limits, which executes control, how operation is inhibited when data becomes invalid and what permits recovery. Share equipment, protocols and test conditions to establish verifiable functions and deliverables.
Online
Phone
WeChat
Top