AERL technical documentation

CoolMax SRX – Modbus RTU Protocol Rev 2.0.5

8 pages

Download PDF Print
CoolMax SRX
Modbus RTU Protocol Rev 2.0.5 16 Nov 2026
Download PDF· Rev 2.0.5
RS485 / Modbus Communications

CoolMax SRX

Modbus RTU Communications Protocol
Doc · SRX-MODBUS-RTU
StandardModbus RTU
PhysicalRS485 · RJ45
Default baud9600 bps
Frame8·N·1
Default address20
Function codes0x02 · 0x04 · 0x0B
CRCCRC-16 (LSB first)
DocumentSRX-MODBUS-RTU
Revision2.0.5
Effective11 / 2026
ProductCoolMax SRX / SRX-R
AudienceIntegrators
Firmware2.0.1 and later
FormatA4 · 8 pages

Contents

01Bus, Connection and SettingsCommunication parameters, frame timing, RJ45 pinout, topology02
02Supported Function Codes0x02 / 0x04 / 0x0B request and response formats, examples04
03Exception CodesStandard Modbus exception responses05
04Modbus Register MapAddressing, input registers 30001–3005805
05Data MappingsDiscrete inputs and Status Flags bit field, Active Event code07
06Data EncodingByte order, signed values, milliunit scaling, worked CRC-1608
07Revision HistoryDocument revision log08
Firmware

Applies to CoolMax SRX and SRX-R firmware 2.0.1 and later. The Min FW column gives the first release with each item.

2.6.9 and 2.8.4 were SRX-R releases only, so an item first released in 2.8.4 reaches the SRX in 2.9.4. 2.6.6 to 2.8.4 have been withdrawn; update units on them to 2.17.9.

CoolMax SRX · Modbus RTU Protocol · Rev 2.0.5 Page 1 / 8 © 2026 AERL Pty Ltd
CoolMax SRX
Modbus RTU Protocol Rev 2.0.5 16 Nov 2026
Chapter 01

Bus, Connection and Settings

The CoolMax SRX and SRX-R (firmware 2.0.1 and later) provide read-only access to real-time measurements, fault flags and device information via the standard Modbus RTU protocol over RS485.

Communication Parameters

ParameterValueMin FW
Baud rate9600, fixed2.0.1
Configurable baud rate9600 (default) / 19200 / 38400 / 57600 / 115200; set by AERL, as AERL Link cannot change it on 2.17.9 and earlier2.8.4 (SRX-R) / 2.9.4 (SRX)
Data bits82.0.1
Stop bits12.0.1
ParityNone2.0.1
Device address20 (default); configurable 1–90 with AERL Link; a setting outside 1–90 is used as 202.0.1
CRCModbus CRC-16 (transmitted LSB first)2.0.1

The broadcast address 0 is not supported; every request is addressed to one unit. Only the function codes in Chapter 02 are supported.

Frame Timing

Modbus RTU frames are delimited by idle time on the bus: a frame is treated as complete once the bus has been silent for the inter-frame gap period.

Firmware before 2.19.6 uses an inter-frame gap of about 8 ms at every baud rate. From 2.19.6 the gap follows the rate: 8 ms at 9600 baud, 4 ms at 19200 and 3 ms at 38400 baud and above. Allow for that gap, a short processing delay, and the transmission time of the response, which at 9600 baud is 126 ms for a full 58-register read.

Set the response timeout to at least 250 ms at 9600 baud, and wait for the response, or for the timeout to expire, before sending the next request. Requests must not be overlapped: a second request that arrives before the first has been answered is discarded along with it.

CoolMax SRX · Modbus RTU Protocol · Rev 2.0.5 Page 2 / 8 © 2026 AERL Pty Ltd
CoolMax SRX
Modbus RTU Protocol Rev 2.0.5 16 Nov 2026
Chapter 01 · continued

Physical Connection

RS485 uses the two paralleled RJ45 sockets labelled MODBUS, separate from the two CAN sockets. The pin-out differs: pin 6 is RS485-B here and GND on a CAN socket, so do not plug a CAN cable into a MODBUS socket.

RJ45 connector viewed from the front, with the eight contacts numbered 1 through 8 from left to right
RJ45 connector viewed from the front: contacts numbered 1 to 8, left to right.
PinSignal
3RS485-A (non-inverting)
6RS485-B (inverting)
8GND

All other pins are unused.

Network Topology

The Modbus network is a linear bus, with short stubs branching from ‘T’ connectors on the main backbone to each device. Terminate the bus at both ends with a 120 Ω resistor between the RS485-A and RS485-B signals: at the master (many masters have a built-in or switchable terminator) and at the far end of the backbone.

Modbus RS485 network topology: a master is daisy-chained to SRX 1, SRX 2 and SRX n on a two-wire bus plus GND, each unit exposing A, B and G terminals, with a 120 ohm termination resistor R2 fitted across A and B at the far end of the backbone
Linear two-wire RS485 bus plus GND: master daisy-chained to SRX units (A / B / G), with 120 Ω termination across A and B at the far end of the backbone.

Each CoolMax SRX is pre-fitted with a switchable 120 Ω termination, enabled by the slide switch next to the MODBUS sockets. Enable it on the SRX at the far end of the backbone only, and leave it off on every other SRX.

CoolMax SRX · Modbus RTU Protocol · Rev 2.0.5 Page 3 / 8 © 2026 AERL Pty Ltd
CoolMax SRX
Modbus RTU Protocol Rev 2.0.5 16 Nov 2026
Chapter 02

Supported Function Codes

0x02 Read Discrete Inputs Min FW 2.0.1

Read one or more fault flags as single bits. On firmware before 2.19.5 the quantity is 1–26 and start address + quantity must not exceed 26: inputs 10027–10032 cannot be read with 0x02, so read bit 26 from the Status Flags register (30027). From 2.19.5 the limit is 32. Inputs are packed eight per byte, first requested input in the LSB; a final partial byte is padded with zeros.

Request[Device ID] [0x02] [Start Address High] [Start Address Low] [Quantity High] [Quantity Low] [CRC Low] [CRC High] Response[Device ID] [0x02] [Byte Count] [Input Bytes…] [CRC Low] [CRC High]
FrameBytesNotes
Request14 02 00 00 00 1A FB 04Device 20 (0x14): read 26 inputs, start 0, quantity 26 (0x1A)
Response14 02 04 40 00 00 00 AA E3Byte count = 4 (last byte padded); 0x40 in the first byte = input 6 (Vin Low Fault) set
0x04 Read Input Registers Min FW 2.0.1

Read one or more input registers containing measurements or device information. Quantity 1–58; start address + quantity must not exceed 58.

Request[Device ID] [0x04] [Start Address High] [Start Address Low] [Quantity High] [Quantity Low] [CRC Low] [CRC High] Response[Device ID] [0x04] [Byte Count] [Data…] [CRC Low] [CRC High]
FrameBytesNotes
Request14 04 00 08 00 02 F2 CCRead 2 registers starting at offset 8 (PV Voltage, 30009–30010)
Response14 04 04 00 06 2E 83 03 45Byte count = 4, value = 0x00062E83 = 405 123 mV = 405.123 V
0x0B Get Comm Event Counter Min FW 2.19.5

Read the count of successful 0x02 / 0x04 responses since power-up. Firmware before 2.19.5 answers 0x0B, but its response leaves out the function-code byte; the standard response below needs 2.19.5.

Request[Device ID] [0x0B] [CRC Low] [CRC High] Response[Device ID] [0x0B] [Status High] [Status Low] [Count High] [Count Low] [CRC Low] [CRC High] Response, before 2.19.5[Device ID] [Status High] [Status Low] [Count High] [Count Low] [CRC Low] [CRC High]

Status is always 0. The counter is 16-bit and wraps.

All other function codes return an Illegal Function (01) exception. In particular 0x03 Read Holding Registers, the default in many Modbus tools, is not supported: configure the client for input registers (0x04).

CoolMax SRX · Modbus RTU Protocol · Rev 2.0.5 Page 4 / 8 © 2026 AERL Pty Ltd
CoolMax SRX
Modbus RTU Protocol Rev 2.0.5 16 Nov 2026
Chapter 03

Exception Codes

Standard Modbus exception responses:

CodeNameDescriptionMin FW
0x01Illegal FunctionFunction code other than 0x02, 0x04, 0x0B2.0.1
0x02Illegal Data AddressStart address + quantity exceeds 26 inputs (32 from 2.19.5) / 58 registers2.0.1
0x03Illegal Data ValueQuantity is 0, or greater than 26 inputs (32 from 2.19.5) / 58 registers2.0.1
Exception response[Device ID] [Function Code + 0x80] [Exception Code] [CRC Low] [CRC High]

Example: 14 83 01 91 34 answers an unsupported 0x03 request. A request whose CRC fails is discarded without a response.

Chapter 04

Modbus Register Map

Addressing

Register reference numbers (1xxxx for discrete inputs, 3xxxx for input registers) are a documentation convention only. The value placed on the wire is the zero-based offset: input 10001 is addressed as 0x0000 under function 0x02, and register 30001 is addressed as 0x0000 under function 0x04.

CoolMax SRX · Modbus RTU Protocol · Rev 2.0.5 Page 5 / 8 © 2026 AERL Pty Ltd
CoolMax SRX
Modbus RTU Protocol Rev 2.0.5 16 Nov 2026
Chapter 04 · continued

Input Registers (FC 0x04)

All registers are read-only 16-bit words. Multi-register values are big-endian: the register at the lowest address holds the most significant word.

AddressOffsetRegs DescriptionTypeUnit / notesMin FW
30001–300040–34Product IDUInt64Device type code, zero-extended2.0.1
30005–300084–74Serial NumberUInt64Allocated at manufacture2.0.1
30009–300108–92PV VoltageInt32mV2.0.1
30011–3001210–112PV CurrentInt32mA2.0.1
30013–3001412–132Output VoltageInt32mV2.0.1
30015–3001614–152Output CurrentInt32mA2.0.1
30017–3002016–194ReservedUInt64Always 02.0.1
30021–3002220–212Power (see below)Int32mW; output power before 2.19.6, see below2.0.1
30023–3002422–232Case TemperatureInt32m°C (25 000 = 25.0 °C), see below2.0.1
30025–3002624–252Active EventInt32Signed event code, see page 82.0.1
30027–3003026–294Status FlagsUInt64Bit field, bits 0–31 used, see page 72.0.1
30031–3003430–334ReservedUInt64Ignore: reads 0x1234567890ABCDEF before 2.19.5, 0 from 2.19.52.0.1
30035–3003834–374ReservedUInt64Always 02.0.1
30039–3004038–392Battery TemperatureInt32m°C; 0 until a value is received, see below2.0.1
30041–3004440–434Hardware Version8 × ASCIIReads AER09SRX2.0.1
30045–3004844–474Firmware Version8 × ASCIIFirst 8 characters of the version string: V2.17.9.0 reads V2.17.9.2.0.1
30049–3005048–492Model TypeUInt32Device type code2.0.1
30051–3005450–534Product ID (mirror)UInt64Mirror of 30001–300042.0.1
30055–3005854–574Serial Number (mirror)UInt64Mirror of 30005–300082.0.1

The four telemetry values (PV and output voltage and current) are positive in normal operation; a small negative reading can appear at zero current or voltage from sensor offset.

CoolMax SRX · Modbus RTU Protocol · Rev 2.0.5 Page 6 / 8 © 2026 AERL Pty Ltd
CoolMax SRX
Modbus RTU Protocol Rev 2.0.5 16 Nov 2026
Chapter 05

Data Mappings

Discrete Inputs and Status Flags

The 32 discrete inputs (FC 0x02, 10001–10032) and bits 0–31 of the Status Flags (30027–30030) are the same fault flags; bits 32–63 are always 0, and the numbering matches the CAN Active Flags broadcast. A flag reads 1 when its condition is active. On 2.17.9 and earlier the Status Flags are a latched snapshot, updated when a fault is raised or cleared, not a live view of each condition. Min FW is the first firmware with the flag.

BitInputFlagDescriptionMin FW
010001Hardware Fault (Generic)Generic hardware fault; also a battery BMS alarm2.0.1
110002No Config DataNo configuration data set2.0.1
210003Config Data Out of RangeConfiguration out of range; from 2.19.5, also a charge target outside the BMS limits2.0.1
310004Battery Sense LostBattery Sense no longer responding2.0.1
410005CAN Master LostCAN master lost2.0.1
510006Internal Over TempInternal temperature fault2.0.1
610007Vin Low FaultInput voltage too low2.0.1
710008Vout Low FaultOutput voltage too low2.0.1
810009Vout High FaultOutput voltage too high2.0.1
910010Vin High FaultInput voltage too high2.0.1
1010011High PV CurrentPV input current too high2.0.1
1110012Over Temp FaultDevice temperature exceeds maximum2.0.1
1210013Low Battery TempLow battery temperature (separate from cut-off)2.0.1
1310014Earth Fault PositiveEarth fault on the positive conductor2.0.1
1410015Earth Fault NegativeEarth fault on the negative conductor2.0.1
1510016Active Cooling FaultFan fault2.0.1
1610017Output Over-CurrentOutput current too high; on bit 24 from 2.19.52.0.1
1710018Iin High FaultInput current too high2.0.1
1810019Cross Check FaultCross-check failed2.0.1
1910020Temp Sensor TimeoutTemperature sensor unresponsive2.0.1
2010021Earth FaultLow isolation resistance; clears after about 30 min from 2.6.6, held until reset from 2.19.62.0.1
2110022No Output FaultNo output detected2.0.1
2210023Low Bat Temp Cut-offLow battery temperature cut-off active2.0.1
2310024High Bat Temp Cut-offHigh battery temperature cut-off active2.0.1
2410025Current Flow DisruptedCharging interrupted (incl. output over-current)2.0.1
2510026Pre-charge FailurePre-charge failure2.0.1
2610027PV Pre-charge FailurePV input pre-charge failure2.8.4 (SRX-R) / 2.9.4 (SRX)
2710028PWM Regulation FailureCurrent flowing while PWM disabled2.19.5
2810029PWM CorruptionPWM state corruption detected2.19.5
2910030Stack OverflowInternal stack overflow detected2.19.5
3010031Clock FailureClock failure (CSS / drift) detected2.19.5
3110032BrownoutBrown-out detected2.19.5
CoolMax SRX · Modbus RTU Protocol · Rev 2.0.5 Page 7 / 8 © 2026 AERL Pty Ltd
CoolMax SRX
Modbus RTU Protocol Rev 2.0.5 16 Nov 2026
Chapter 05 · continued

Active Event (Registers 30025–30026)

A single signed Int32 event code, not a bit field. 0 = no event (cleared once all flags clear and the converter re-enables). Negative values are fault codes, for example −1100 = temperature exceeds maximum; positive values are informational events, for example 101 = fault recovered. The register holds the most recent code raised. A battery BMS alarm shows here as −1305. Decode as two’s complement. The SRX user manual’s troubleshooting chapter lists the codes an installer sees; the full list is available from AERL on request.

Chapter 06

Data Encoding

All values are transmitted as integers; no floating-point encoding is used.

CRC-16

Every frame ends with a 16-bit CRC computed over all preceding bytes using polynomial 0xA001 (0x8005 reflected) with an initial value of 0xFFFF, and transmitted low byte first.

Frame (without CRC)CRC-16On the wire (CRC appended, low byte first)
14 04 00 08 00 020xCCF214 04 00 08 00 02 F2 CC
14 04 04 00 06 2E 830x450314 04 04 00 06 2E 83 03 45 (response)
Chapter 07

Revision History

Rev.DateChange
––Earlier revisions: see previous editions.
2.0.210/09/26Reorganised for integrators.
2.0.308/11/26Updated for firmware 2.19.6: register 30021 is PV power; inter-frame gap per baud rate; flag notes; MODBUS sockets have their own pin-out; bus termination clarified.
2.0.409/11/26Minimum firmware marked on items that need firmware later than 2.17.9.
2.0.516/11/26Minimum firmware for every register, function and flag, from 2.0.1; corrections for firmware 2.17.9 and earlier.