Battery-to-PCS/EMS Modbus and RS485 RFQ Checklist
A commercial or industrial buyer asks for a battery that “has RS485” or “supports Modbus,” then issues a request for quotation. The pack arrives with a port on the case. The power conversion system (PCS) or energy management system (EMS) has a port of the same name. Nothing useful is exchanged, or the values that do appear are scaled, swapped or signed incorrectly. The gap is almost never the word on the silkscreen. It is the missing Modbus and RS485 RFQ checklist: the physical interface, the application protocol, the map of registers or objects, and the evidence that the two maps actually meet.
This page is for buyers who must connect a battery management system (BMS) or battery cluster controller to a PCS, EMS or plant controller. It is not a LJY Energy register map, and it does not claim that any named PCS or EMS is compatible with a given pack. A port type is not a protocol. Confirm the map and a traffic record against the exact controller and firmware before you treat the link as part of the supply.
Residential hybrid-inverter pairings that use a vendor-specific CAN or RS485 profile are covered in the closed-loop inverter communication guide. Vehicle and machine buses are covered in the J1939 versus CANopen guide. Use this page when the plant side is specified as Modbus on serial or Ethernet.
Start from the layers, not the port label
The Modbus Organization describes Modbus as an application-layer messaging protocol. It defines function codes, addressing and data formatting, and it can run on more than one physical network, including EIA/TIA-485, EIA/TIA-232 and TCP/IP. That single point already splits a lazy specification into two questions: what cable and signalling you have, and which application protocol and map will run on them.
On serial lines, the official *MODBUS over Serial Line Specification and Implementation Guide* V1.02 (20 December 2006) adds a further split:
- Physical interface. TIA/EIA-485 (RS485) two-wire is described as the most common option. A four-wire RS485 interface may be implemented as an add-on, and TIA/EIA-232 may be used for short point-to-point links. A two-wire RS485 bus still needs a common (reference) conductor in addition to the balanced pair. Line terminations are required at each end of the trunk for impedance matching.
- Transmission mode. The serial-line guide specifies two modes, RTU and ASCII. Naming “Modbus” without the mode is incomplete.
- Addressing. The guide reserves address 0 for broadcast and assigns unique slave addresses in the range 1 to 247. Two devices with the same address will not give a stable master–slave bus.
- Signalling rates. The same guide requires 9600 bps and 19.2 kbps, with 19.2 kbps as the required default. Other rates may be offered. Every implemented rate must be respected to better than 1 percent in transmission and must accept a 2 percent error in reception.
- Character format. In RTU mode the guide requires one start bit, eight data bits, and even parity as the default. Other parity modes may be used; if no parity is used, two stop bits are required.
- Timing. For baud rates above 19200 bps, the guide recommends fixed inter-character and inter-frame timers (750 µs and 1.750 ms) rather than the character-time-based values used at 19200 bps and below.
The application-protocol specification V1.1b3 (26 April 2012) then defines the function codes that actually read and write data, and it records that Modbus on TCP/IP uses reserved system port 502. It also limits the protocol data unit (PDU) to 253 bytes, giving a 256-byte application data unit on RS485 (address plus PDU plus CRC) and a 260-byte unit on TCP (MBAP header plus PDU). If a supplier offers a “map” that cannot be fetched with the function codes and size limits the controller supports, the port will not save the project.
None of these official figures is a battery register map. They are the rules you use to test whether a supplier’s document is complete.
Physical RS485 is still a separate checklist
Even when the protocol is agreed, the cable can still be wrong. Texas Instruments’ RS-485 Design Guide describes a differential trunk on cable commonly specified at 120 ohm, terminated with a matching resistor at each end, with stubs kept short to limit reflections. Receivers are specified to detect a differential input down to 200 mV, and the same note discusses idle-bus failsafe biasing when the bus is not being driven. The companion TI article on termination explains that 120 ohm is the nominal characteristic impedance chosen in the RS-485 standard, so default termination resistors are also 120 ohm, and that termination can be omitted only in special cases where the two-way loop time is much shorter than a bit time. Do not assume an unterminated drop cable is acceptable on a plant trunk.
Ask the supplier, and write the answers into the RFQ, for:
- two-wire or four-wire
- connector type and the pinout of A/B (or D0/D1) and common, because A/B labelling is not consistent across vendors
- where the 120-ohm terminations sit, and whether they are switched or always in
- whether failsafe bias is provided, and at which end
- cable type, shield earthing, and the maximum trunk length they will support at the agreed baud rate
- how many devices will share the bus, and the unit-load assumption
The serial-line guide itself notes a length example of 1000 m at a maximum 9600 baud with AWG 26 or wider cable. That is a specification example, not a site survey of your cable route. Confirm length and noise environment per project.
What the RFQ must request on the protocol map
A complete supplier response names both sides of the link and then the map between them.
| RFQ field | What a usable answer looks like | What is not enough | Status |
|---|---|---|---|
| Role | Which device is Modbus client/master and which is server/slave | “Both ends support Modbus” | Confirmed per project |
| Transport | Modbus RTU or ASCII on RS485, or Modbus TCP on Ethernet (port 502 unless a different port is documented) | “RS485 / Ethernet” with no mode | Confirmed per project |
| Serial settings | Baud rate, parity, stop bits, and unique slave address in the range 1–247 | “Standard Modbus settings” | Confirmed per project |
| TCP settings | IP arrangement, unit identifier, and port | An IP address with no unit identifier or map | Confirmed per project |
| Function codes | Which public function codes are used, for example 03 (read holding registers), 04 (read input registers), 06 (write single register), 16 (write multiple registers), if those are the ones actually implemented | “Read/write supported” | Confirmed per project |
| Register or object map | Address, name, unit, scale, signed or unsigned, update rate, and which values are monitored versus commanded | A screenshot of a port, or a brand list | Confirmed per project |
| Multi-register values | Byte and word order for 32-bit values or floating-point pairs, stated in the document | A map that lists a float but not the packing | Confirmed per project |
| Required operating data | At least pack voltage, current, SOC, temperature, charge and discharge limits, and alarm or fault bits, if closed-loop or supervised operation is required | A map that only reports a single voltage | Confirmed per project |
| Command rights | Whether the PCS or EMS may send start, stop, limit or mode commands, and what the battery will do if a command is out of range | Implied control with no write list | Confirmed per project |
| Alarm and quality flags | How a bad value, a protection event, or a communication timeout is encoded | Plain registers with no fault path | Confirmed per project |
| Document revision | Map revision, date, and the firmware version it applies to | An undated PDF | Confirmed per project |
| Evidence | A dated log, capture or witnessed test against the actual PCS or EMS model and firmware | A statement that “Modbus is supported” | Confirmed per project |
The official introduction to Modbus also warns that 32-bit floating-point word order is not always well documented and may differ between manufacturers. If your EMS expects one packing and the battery uses another, the port will still “come up.” Insist that the packing is written down and then checked in the log.
Do not accept a generic map copied from another brand as evidence for your combination. If the plant already has a house standard, attach that standard to the RFQ and ask the supplier to mark each required point as supported, not supported, or available only through a gateway. A gateway is a new device with its own firmware and map; name it if it is part of the offer.
What to record before you accept the link
The same discipline used for inverter closed-loop acceptance applies here. Before sign-off:
- freeze the battery or cluster controller firmware and the PCS or EMS firmware against the map revision
- read the required points and confirm scale, sign and units
- if write commands are in scope, test only the agreed commands, in the agreed order, within documented limits
- confirm that an alarm or a communication loss produces the documented plant response
- keep the capture file with the acceptance record
High-voltage rack clusters and cabinet systems on this site describe CAN, RS485 or Ethernet (Modbus-type) links to a PCS or EMS as an optional, project-specific configuration — see the high-voltage rack battery cluster page and the communications line in the commercial and industrial RFQ checklist. No fixed register map is published, because the map has to match the controller you actually have.
LJY Energy can help you put these fields into an enquiry or a quotation and can state what has been checked for a named PCS or EMS. Unchecked items remain “confirmed per project.” This page does not publish a LJY register map and does not claim compatibility with any PCS, EMS or SCADA brand.
What to send when you enquire
Include, if you already have them:
- PCS, EMS or plant-controller brand, exact model and firmware
- whether the plant standard is Modbus RTU, Modbus ASCII or Modbus TCP
- the slave address or unit identifier you must use, and the serial or TCP settings
- the list of points the controller must read or write
- any existing register map, cable drawing or capture from a previous attempt
Send those items through the contact page. If the job is still at the product-definition stage rather than a plant interface, the OEM/ODM RFQ checklist and the BMS supply and OEM integration page are the better starting points.
Related reading already on this site: the closed-loop communication guide, the J1939 versus CANopen guide, the BMS selection guide, and the commercial and industrial RFQ checklist.
