BMS and Inverter Firmware Version Control

BMS and Inverter Firmware Version Control Before You Order

A sample pack talks to the hybrid inverter. State of charge appears on the display, and charge current follows the battery limits. The purchase order goes out on the back of that result. Weeks later the production lot arrives, or the inverter applies a field update, and the same CAN or RS485 port no longer behaves like the sample. The datasheet still says the interface is present. The protocol name on the brochure has not changed. What changed is the firmware, the protocol document revision, or the system software that sits between the battery and the charger.

This page is a procurement control for BMS and inverter firmware version control. It is not a brand compatibility list, and it is not a promise that any named inverter, PCS or BMS will work with a pack from LJY Energy. A physical port is not a protocol, and a protocol name is not a frozen revision. Confirm the pairing on the exact models and firmware you will install, then write those identities into the order.

Why a passing sample can fail on the production lot

Closed-loop control depends on more than a matching connector. The battery management system (BMS) has to send live limits and status — typically charge voltage limit (CVL), charge current limit (CCL), discharge current limit (DCL), state of charge (SOC), temperature and alarm flags — and the inverter or power conversion system (PCS) has to apply those values. The closed-loop inverter communication guide explains that exchange and the difference between a documented setting, a protocol-compatible claim, and voltage-only (open-loop) operation.

Firmware sits underneath that exchange. A later BMS build can change message identifiers, scaling, alarm bits or timing. A later inverter or gateway build can change which battery profile is offered, which port speed is assumed, or whether the charger follows the BMS request at all. If the purchase order only says “CAN” or names a protocol family, there is no agreed baseline when the software moves.

Public manufacturer documentation already shows this risk in systems that have been formally tested. Victron’s published integration note for specified Pylontech models requires a GX device on the battery CAN link, states a minimum Venus firmware of v3.50 for new systems, and recommends current firmware on the GX device, inverter/charger and MPPT controllers because updates are issued regularly. The same note records that one UP2500 hardware version has no CAN-bus port and is not supported, while a later version with the port is. It also documents a system-level override: when DVCC is enabled, the Pylontech battery requests a charge voltage of 53.2 V, but Victron caps charge voltage at 52.4 V because the requested value was found too high in practice. That is Victron’s documented behaviour for that published combination. It is not a test result for other brands or for LJY Energy packs, and it is not a reason to assume that a “Pylontech-compatible” label will behave the same way. It is a reason to treat firmware, document revision and system software as part of the product you are buying.

What “version” must mean in the RFQ

Ask for identities you can put on a nameplate photo and a purchase order line, not a marketing sentence.

Identity to freeze What to record Why it matters Status
Battery model and suffix Full model string, including hardware letters or regional suffixes A suffix can add or remove a communication port, as in the published UP2500 CAN-bus example Confirmed per project
Battery serial or production batch Serial number and, if issued, batch or date code of the approved sample Ties the test result to a physical unit Confirmed per project
BMS hardware and firmware BMS board or module identity and the firmware version shown in the tool, display or log The control logic and message map live here Confirmed per project
Protocol name and document revision The exact profile name plus the protocol manual, register map or CAN frame list and its revision or date “Pylontech CAN” or “Modbus” without a revision is not a frozen map Confirmed per project
Inverter, PCS or gateway model Nameplate model, not only the brand or series Protocol menus and ports vary by model Confirmed per project
Inverter, PCS or gateway firmware Main, DSP and communication-board versions if the device shows them separately A later build can change profile lists, port speed or charge-voltage handling Confirmed per project
Intermediate device Whether a gateway, GX-class device, logger or energy management system (EMS) sits on the link, and its firmware Some families do not terminate the battery link on the inverter itself Confirmed per project
Communication settings used in the test Interface (CAN or RS485), bitrate or baud, parity and stop bits if serial, address or node ID, termination Settings are part of the approved configuration Confirmed per project
Cable and pinout used in the test Connector, pinout drawing and cable part if a special lead was used A straight network cable is not a universal CAN or RS485 lead Confirmed per project

The BMS selection guide already puts the buyer question as “interface + protocol + tested inverter list.” Add the firmware and document revision to that list, or the tested list cannot be replayed.

Interface, protocol and revision are three different facts

CAN and RS485 describe the physical layer. High-speed CAN is specified in ISO 11898-2. CAN in Automation describes a line topology terminated at both ends with 120-ohm resistors that match the cable, and a maximum high-speed bit rate of 1 Mbit/s, with usable length falling as the bit rate rises. National Instruments’ physical-layer guide likewise states that both ends of CAN_H and CAN_L must be terminated in 120-ohm resistors for high-speed CAN, and that 500 kbit/s is a common automotive rate — not a universal energy-storage default. Victron’s published note, for the combinations it covers, tells the installer to select the “CAN-bus BMS (500 kbit/s)” profile when the battery is connected to a VE.Can port rather than a BMS-Can port. That figure applies to that documented setup. Do not copy it onto another inverter family.

RS485 (TIA/EIA-485) is also a physical layer. Texas Instruments’ RS-485 Design Guide describes differential signalling on a cable trunk that is commonly specified at 120 ohm and terminated with a matching resistor at each end, with short stubs. Modbus is not that cable. The Modbus Organization states that Modbus is an application-layer protocol and can run on EIA/TIA-485, EIA/TIA-232 or TCP/IP. The official serial-line guide (V1.02) treats RTU and ASCII as transmission modes on top of the physical interface, and requires unique slave addresses in the range 1 to 247, with address 0 reserved for broadcast. Those numbers are protocol rules, not proof that a given battery speaks the register map your PCS expects.

A CANopen battery profile is another example of a named higher layer. CiA 418 specifies a CANopen interface for battery modules intended to work with chargers that follow CiA 419, and lists mandatory data such as battery type, capacity, number of cells, maximum permissible charge current and battery temperature. Naming “CANopen” in an RFQ without the profile, object list and firmware that implements it is still incomplete. The J1939 versus CANopen guide covers how to specify those vehicle and machine buses. Residential hybrid inverters often use a different, vendor-specific CAN or RS485 profile. Do not treat one named stack as a substitute for another.

What to freeze in the purchase order

After a sample test — or after a supplier provides a dated test record against your exact inverter model and firmware — write the approved identities into the order. The aim is a configuration baseline, not a slogan.

  1. Record the sample. Photograph the battery nameplate, the inverter or PCS nameplate, the communications settings screens, and the firmware or version pages. Keep a short log or screenshot that shows the inverter detecting the battery and displaying SOC, voltage and the charge and discharge limits.
  2. Quote those strings in the purchase order. The production units should match the approved battery model and suffix, BMS firmware, protocol document revision, and the inverter or PCS firmware used in the test, unless a deviation is agreed in writing before shipment.
  3. State what happens if software changes. If the supplier needs to ship a later BMS firmware, or if the inverter manufacturer issues an update, the change should be notified, compared with the approved baseline, and re-tested on the same interface before the lot is accepted.
  4. Say who is allowed to update firmware after delivery. Field updates by the installer, the inverter vendor or a remote service tool can move the system off the approved pair. Agree whether updates are frozen until a re-test, and what evidence you will receive.
  5. Keep the protocol document with the order file. A register map, CAN frame list or DBC file without a revision and date cannot be used later to explain a mismatch.

LJY Energy can help you collect these fields for a quoted pack and state, in the quotation, what has actually been checked for your combination. Items that have not been checked stay as “confirmed per project.” LJY Energy does not appear on inverter manufacturers’ approved battery lists, and this page does not add any unofficial list.

What this control does not replace

Version control does not replace a live communication test. It also does not replace voltage-class, current, protection and pre-charge checks. If the inverter and battery never share a matching protocol, the system may still run open-loop on a user-defined lithium profile copied from the battery datasheet, as described in the communication guide. In that case there is no closed-loop firmware pair to freeze — and you should not describe the job as a closed-loop supply.

Do not treat a logo wall, a “supports CAN” line, or a calculator first-pass as a frozen configuration. The inverter battery compatibility calculator is a planning check of voltage class and protocol family. It is not a compatibility guarantee and it does not lock firmware.

What to send when you enquire

If you want a pack quoted against a specific inverter or PCS, send what you already have rather than a brand name alone:

  • inverter or PCS brand, exact model, and firmware versions if they are visible
  • photographs or exports of the battery-protocol menu and communication settings
  • whether the link must be closed-loop, or whether a documented open-loop fallback is acceptable
  • how many packs will share the bus, and any gateway or EMS in the path
  • any protocol document, pinout or cable drawing you have already been given

Use the contact page and include those items in the message. The same checklist belongs in a wider commercial and industrial RFQ when a PCS or EMS is part of the scope.

Related reading already on this site: the closed-loop communication guide, the BMS selection guide, the J1939 versus CANopen guide, and the inverter pre-charge and BMS trip guide. Companion drafts in this offline pack cover the closed-loop acceptance test and the Modbus/RS485 RFQ checklist; those URLs must not be published as internal links until the pages are live.

Contact LJY Energy · WhatsApp +86 159 8945 0735