The short answer: no
Having CAN or RS485 ports on both a UPS and a lithium battery system does not automatically mean that the two systems can communicate correctly. CAN and RS485 identify a possible physical communication path; they do not prove a shared protocol, message definition, data map or control behavior.
For a UPS lithium battery project, compatibility should be confirmed at the exact UPS model, firmware and BMS protocol level. A connector match is useful evidence to collect, but it is not a compatibility approval or a substitute for electrical matching.
Physical interface, protocol and message definition are different
A physical interface concerns how devices are connected and exchange signals. A communication protocol defines how those signals are organized and interpreted. Two devices can both use CAN, or both use an RS485 electrical interface, while expecting different identifiers, registers, frames, byte order, timing or command logic.
The practical review therefore has more than one layer. Confirm the interface first, then identify the protocol and configuration expected by each device. Do not describe CAN and RS485 as the same protocol, and do not assume that a common connector fixes protocol or firmware differences.
- Physical interface and connector or terminal arrangement
- Protocol name, revision and supported message definition
- Data format, registers, identifiers and byte order where applicable
- Node, device or address requirements where applicable
- Baud rate, CAN bitrate and other communication settings
- Required battery data points and update behavior
- Commands, permissions and control ownership
- Alarm, protection, shutdown and restart behavior
- UPS-side firmware or option-card support
- BMS-side protocol implementation and configuration
Confirm the UPS-side communication expectation
Start with the exact UPS brand, model and installed firmware or communication option where relevant. Ask whether the UPS expects battery communication, merely supports monitoring, or can operate through an agreed independent protection or dry-contact arrangement. The answer may vary between UPS families and revisions.
Request the UPS OEM manual, protocol document or written model-specific confirmation when it is available. Record the required data, supported settings, alarm behavior and any response expected when the battery reports a protection event. A generic statement that a UPS has CAN or RS485 is not sufficient for protocol matching.
Confirm the battery BMS-side implementation
The battery or BMS supplier should identify the physical interface, supported protocol direction, configuration options and the data that the selected BMS can provide. Depending on the approved system, this may include voltage, current, state of charge, temperature, alarms, protection state or charge and discharge limits. These are possible project data points, not a universal list for every BMS.
Also confirm whether the BMS implementation is fixed, configurable or subject to an approved protocol mapping. The BMS model, firmware and the cabinet or module architecture all matter. Do not claim that a battery supports a named UPS protocol until the relevant BMS documentation and exact project scope have been reviewed.
Data points and control behavior must be agreed
A UPS may only need a limited set of battery status information, while another project may expect alarms, charge limits, shutdown requests, restart conditions or monitoring values. The required data content, timing and response to missing or invalid data need to be agreed for the selected UPS and BMS pairing.
Model-specific protocol guides illustrate why this matters: they can define register maps, supported software versions, status flags and control values. Those documents are useful technical evidence, but a guide for one OEM system is not evidence that another UPS and battery combination will behave in the same way.
Communication may be optional or necessary
Some lithium battery projects may rely mainly on verified electrical compatibility and independent battery protection, with a limited agreed monitoring or dry-contact arrangement. Other UPS systems require, or strongly benefit from, active BMS communication for their intended alarm, control or monitoring behavior.
The correct approach depends on the UPS design, project architecture, OEM requirements, monitoring expectation and protection logic. Do not state that communication is always mandatory, or that it is never required, without checking the actual equipment and project responsibility.
Communication compatibility does not replace electrical matching
Even when a protocol path is available, the UPS DC-side review remains essential. Confirm nominal DC bus voltage, complete operating window, minimum DC voltage, charging voltage, charging current, actual load, required runtime, topology and center-tap or two-wire architecture.
Use the UPS DC Bus Voltage Checklist to collect that evidence and the UPS Lithium Battery Selection Guide to review the complete project boundary. A communication result does not establish a battery model, fixed runtime, certification scope or commercial approval.
Collect the protocol-matching record before quotation
A useful pre-RFQ record lets the UPS service company, battery side and project owner identify missing evidence before a configuration is presented. Mark unavailable documents for confirmation instead of replacing them with assumptions or a connector-only conclusion.
- UPS brand, exact model and firmware version if relevant
- Battery system and BMS model, including firmware where relevant
- CAN or RS485 interface, terminal arrangement and cable responsibility
- UPS protocol documentation or written OEM confirmation if available
- BMS protocol documentation, mapping or supported configuration if available
- Required data points, monitoring expectation and alarm behavior
- Baud rate, CAN bitrate, node or address requirements where applicable
- Shutdown, restart, contactor and protection responsibility
- Nominal DC bus, complete voltage window and charging information
Confirm the exact pairing before approval
Communication compatibility should be confirmed for the exact UPS model and BMS protocol implementation, not from the presence of a CAN or RS485 port alone. The final project review should identify the documents used, any configuration or test scope, unresolved values and the party responsible for local commissioning.
ZYKEVO's project judgment is to keep protocol review connected to the DC bus, charger, load, runtime, cabinet and site evidence. Final model, communication function, compatibility, documentation and delivery terms remain subject to written confirmation for the approved project.
Technical Sources
These external references explain communication layers or model-specific protocol documentation. They do not confirm compatibility for a particular UPS and battery pairing.
- CAN in Automation — CANopen communication profile Shows that a CAN-based application layer and communication profile define data types, services and protocols in addition to lower communication layers.
- Modbus Organization — Modbus Serial Line Protocol and Implementation Guide V1.02 Separates the Modbus serial protocol and transmission modes from the physical-layer characteristics of RS485 and RS232.
- Schneider Electric — UPS-Link Protocol Specification Example of a named UPS protocol document; it does not establish compatibility for another UPS or battery system.
- Vertiv — HPL Lithium-Ion Energy Storage System Protocol Guide Example of model-specific protocol versions, register mappings and battery-system status data; it is not transferable to other pairings.
Related project paths
- Review the high-voltage LiFePO4 battery platform
- Use the UPS lithium battery selection guide
- Collect the UPS DC-side evidence before protocol matching
- Compare High-Rate and Extended-Runtime battery duties
- Review 192V LiFePO4 battery directions
- Review 384V LiFePO4 battery directions
- Review 512V LiFePO4 battery directions
- Send Your Requirement