Closed-Loop BMS–Inverter Communication Acceptance Test
The pack is on site, the communication cable is in, and the inverter has a lithium or BMS menu selected. That is the start of acceptance, not the end. A closed-loop BMS–inverter communication acceptance test is the set of pass or fail checks — and the records you keep — before you sign for a closed-loop battery supply. It is how a buyer turns a “compatible” sentence into an observed result on the exact inverter or PCS and firmware that will remain in service.
This page does not certify any brand pairing, and it does not replace the inverter manufacturer’s commissioning procedure or a licensed installer’s safety rules. It does not ask anyone to run destructive tests. If the project is specified as open-loop, do not use this page to describe the job as closed-loop. For how closed-loop and open-loop differ, and for the RFQ fields that belong in the first enquiry, see the closed-loop inverter communication guide.
What you are accepting
In a closed-loop link the battery management system (BMS) sends live data and limits, and the inverter, hybrid inverter or power conversion system (PCS) follows them. Buyers usually need at least:
- the inverter or PCS detects the battery under the selected profile and keeps the link up
- pack voltage and state of charge (SOC) shown on the inverter agree with the BMS closely enough to be used for operation, and they move together as the pack charges or discharges
- charge current limit (CCL) and discharge current limit (DCL) from the BMS are visible and are followed, rather than a fixed inverter current that ignores the battery
- charge voltage limit (CVL), or the equivalent voltage target, is visible, and any override by a gateway or system function is recorded rather than discovered later
- alarms and protection flags from the BMS appear on the inverter or monitoring device
- a controlled loss of communication puts the system into the behaviour documented for that inverter, and a restart returns it to the approved mode
Those are acceptance observations. They are not a laboratory certification, and they are not a promise that the same result will hold after an unrecorded firmware change. Freeze the software identities as described in the companion firmware version-control draft in this pack, and in the communication guide’s sample-test notes.
When to run the checks
Treat the work as one evidence chain, not three unrelated events.
| Stage | Purpose | Typical location | What “pass” must be tied to |
|---|---|---|---|
| Sample or factory test | Approve a configuration before a volume order or shipment | Supplier bench, or your own inverter of the same model and firmware | The exact battery model and suffix, BMS firmware, protocol revision, cable, settings, and inverter or PCS firmware used |
| Incoming or delivery check | Confirm the delivered units still match the approved baseline | Goods receipt, before the pack is treated as accepted | Nameplates, firmware strings, documents and, if agreed, a repeat of the communication checks |
| Site acceptance | Confirm the installed system, cable route, addresses and termination still produce the same result | The working installation | The installed inverter or PCS, the final cable, the parallel set if several packs share the bus, and the as-built settings |
A result from a different inverter model, a different firmware, a bench cable that will not be shipped, or a single pack when the site will run a parallel group, is not an acceptance result for that site. The communication guide already makes this point for sample tests; it applies equally at sign-off.
If a commercial and industrial battery energy storage system (BESS) is involved, put the communication witness points into the commercial and industrial RFQ checklist so they are agreed before anyone travels to the factory or the site.
Pass and fail checks
Run the checks in normal operation, within the limits in the battery and inverter manuals. Do not use short-circuit tests, forced over-voltage, or any other destructive method to “prove” communication. If a check cannot be performed safely or the inverter has no way to display the value, record it as not done, with the reason — do not mark it as passed.
| Check | Pass condition | Fail or hold | Evidence to keep |
|---|---|---|---|
| Configuration baseline | Model, suffix, serial or batch, BMS firmware, inverter or PCS firmware, protocol name and document revision, and communication settings match the approved record, or a written deviation exists | Any unrecorded difference in model, firmware or protocol revision | Nameplate photographs, firmware screens, settings export or written copy |
| Link and profile | The inverter or PCS detects the battery on the selected profile and the link stays up during the test window | No detection, repeated drop-outs, or a different profile than the one agreed | Screen photographs or a commissioning log with time and profile name |
| Voltage and SOC | Inverter and BMS values are stable and move together during a normal charge or discharge interval agreed for the test | Large unexplained disagreement, frozen SOC, or values that do not move when current is flowing | Side-by-side readings with timestamps |
| Charge limit | The charger or inverter follows the BMS charge-current limit, including a documented reduction if one is shown (for example a temperature or high-SOC derating that the BMS actually reports) | The unit continues at a fixed current that ignores the BMS limit | Recorded CCL and measured charge current |
| Discharge limit | The inverter follows the BMS discharge-current limit under a controlled, agreed load | The inverter exceeds or ignores the reported DCL | Recorded DCL and measured discharge current |
| Charge voltage handling | The displayed CVL or charge-voltage target is recorded; if a gateway or system function caps or replaces the BMS request, that override is written down | An undocumented cap or a voltage that does not match either the BMS request or a documented system rule | Parameter screen plus a note of any documented override |
| Alarms | A non-destructive, supplier-agreed alarm or warning from the BMS appears on the inverter or monitor, with the code or text recorded | No path for battery alarms, or codes that cannot be mapped to the protocol document | Alarm text or code, time, and the document clause used to interpret it |
| Communication loss | With the method agreed in advance (for example disconnecting the communication cable only, never the power circuit, and only if the manuals allow it), the system enters the documented protection or fallback state | Undocumented shutdown, a hazardous uncontrolled state, or no defined behaviour in the manual | Test note, result, and the manual clause |
| Restart | After the agreed restore steps, the battery is detected again and the approved mode returns | Link does not return, or settings have changed | Restart record |
| Parallel set, if specified | Every pack that should be on the bus is visible, addresses or IDs match the agreed table, and termination is only where the wiring standard and the manuals require it | Missing packs, duplicate addresses, or intermittent faults after a wrong ID | Address table, wiring sketch, and monitor list |
CAN and RS485 physical rules still apply during these checks. High-speed CAN (ISO 11898-2) is a line topology that CAN in Automation and National Instruments both describe as terminated at each physical end with 120-ohm resistors matching the cable. Texas Instruments’ RS-485 Design Guide describes the same idea for a 120-ohm RS485 trunk: terminate both ends and keep stubs short. Extra terminations, missing terminations, or a straight network cable with the wrong pinout are common reasons a “correct protocol” still fails. Record the cable and the termination points you actually used.
How to keep the evidence
A verbal “it worked” is not an acceptance record. Keep a short file that a later technician can replay:
- identities from the baseline table, including firmware strings
- the protocol document revision used to interpret registers or CAN frames
- the checks run, the result (pass, fail, or not done), and the time
- photographs or exports of the detection, SOC, limits and alarm screens
- open items, with an owner and whether they block shipment or site sign-off
- the name of the person who accepts the result, and the date
If a check fails, do not close it with a comment alone. Record the deviation, the proposed fix (settings, cable, firmware, or a change to open-loop if that is the agreed fallback), and the re-test that will be required. Production firmware that does not match the approved sample is a failed baseline, not a minor note. That is also why firmware version control belongs in the purchase order, not only in the commissioning folder.
LJY Energy can state in a quotation which of these checks have been run for a named combination and which remain “confirmed per project.” This page does not claim a factory laboratory, does not publish a universal pass certificate, and does not place LJY Energy on any inverter manufacturer’s approved list.
What to send when you enquire
If you want help preparing a communication acceptance record for a pack you are quoting or receiving, send:
- inverter or PCS model and firmware, plus any gateway or EMS in the path
- the protocol profile you intend to select, and any document or pinout you already have
- whether the test is a sample approval, an incoming check, or a site sign-off
- how many packs will share the bus
- any checks your inspector or owner already requires, so they are not duplicated or missed
Use the contact page and attach those items. For first-pass voltage class and protocol family only, the inverter battery compatibility calculator is a planning tool, not an acceptance record.
Related reading already on this site: the closed-loop communication guide, the BMS selection guide, the installers’ 51.2 V storage page, and the inverter pre-charge and BMS trip guide.
