Every device. One tool. Pay once. Modbus · BACnet · Siemens S7 · one-time licence · also from us: BACManager ↗

CoolMasterNet VRF Modbus: Virtual Addresses, Unit ID 80 and the 16-Address Block

A CoolAutomation CoolMasterNet sits on the VRF bus of a Daikin, Mitsubishi Electric, Samsung, LG, Toshiba or other system and gives every indoor unit the same Modbus block: on/off, mode, fan speed, setpoint, room temperature and the malfunction code. One map for every brand — once you know how the Virtual Address turns into a register number, which is where most integrations go wrong by one.

ModbusManager Pro dashboard for four VRF indoor units behind a CoolMasterNet: Office 1 cooling at 25.3 °C room with setpoint 24.0 and fan Med, Office 2 stopped, the meeting room on fan only, Reception offline with malfunction 65535, and a room temperature trend
The free workspace below on a simulated CoolMasterNet — four Virtual Addresses, one of them not answering the gateway.

Before Modbus Answers

Several RTU and TCP masters can be connected at the same time.

Virtual Address to Register

CoolAutomation gives the base of each indoor unit as VA × 16 + 1: VA1 = 17, VA2 = 33. Each unit has a 16-address block, and the same base applies to the holding, input, coil and discrete-input tables.

17 or 16? “17” reads as a 1-based register number. The Loxone integration guide that CoolAutomation hosts addresses the same register as 16 (“IO addresses will start at 16 for VA1”), and the workspace on this page uses 16 × VA on the wire. CoolAutomation's guidelines do not say which, so check on your gateway: read holding 16 and 17 for VA1 — the mode register holds 0–6, the fan register 0–5, and the setpoint two registers on is a number like 240.

The Indoor-Unit Block

OffsetTableValue
+0holding (FC03/06)Mode: 0 Cool, 1 Heat, 2 Auto, 3 Dry, 4 HAUX, 5 Fan, 6 HH
+1holdingFan speed: 0 Low, 1 Med, 2 High, 3 Auto, 4 Top, 5 Very low
+2holdingSetpoint × 10 °C
+3holdingOn / off (0 / 1)
+4holdingFilter sign
+5holdingSwing: 0 vertical … 4 horizontal, 5 auto, 6 off
+6holding (read)Room temperature × 10 °C
+7holding (read)Malfunction code: 0 none, 65535 (0xFFFF) = indoor unit lost
+8holdingWall-controller lock bits: b0 on/off, b1 mode, b2 setpoint, b7 all
+9holdingSetpoint limits: high byte = high × 2, low byte = low × 2 (0x4020 = 32 / 16 °C)
+1 / +4input (FC04)Room temperature / setpoint × 10
+2, +3inputMalfunction as four ASCII characters (“OK  ” = 0x4F4B 0x2020)
+0 / +3coil (FC01/05)On / off; Inhibit (a window contact: forces the unit off after about 8 s)
+0 / +1discrete input (FC02)Thermo-on (demand); indoor communication failure

The same quantity is in more than one table — on/off is holding +3 and coil +0, room temperature holding +6 and input +1. Pick one and stay with it.

Malfunction Codes

Holding +7 is 0 with no fault and 0xFFFF when the gateway has lost the indoor unit (discrete input +1 says the same). Any other value is the brand's own code, as a number to translate: on Daikin 0x11 = A1, 0x30 = E0, 0x40 = H0; Mitsubishi Electric codes read as four decimal digits; LG as two. For a display, the two ASCII input registers give the code as text.

Common Mistakes

Step-by-Step: Reading a CoolMasterNet with ModbusManager

  1. Assign VAs (va), enable Modbus IP and reboot.
  2. In ModbusManager choose TCP, the gateway's address, port 502, slave ID 80.
  3. Read FC03 from 16 × VA, 12 registers: mode, fan, setpoint × 10, on/off … room × 10, malfunction.
  4. Open the workspace below and change the VAs or add units by copying a poll window.

Download a Ready-Made Workspace

Read-only. Nothing is written — no on/off, no setpoint. Set your gateway's IP address and your VAs; if VA1's mode reads at 17 on your gateway, add 1 to every poll address. Tags, script and dashboard are ModbusManager Pro features; Standard opens the poll windows only.

CoolMasterNet_VRF.json

CoolMasterNet workspace, four VRF indoor units (Modbus TCP, unit 80). Open via Workspace › Open in ModbusManager Pro, or from the in-app Device library.

Download Workspace

Try it with ModbusManager Pro

VRF and indoor-unit faceplates, alarms on malfunction codes, historian, and MQTT to Home Assistant. Free 14-day trial. No credit card. Windows 10/11.

Download Pro Trial

The same VRF over BACnet: Mitsubishi AE-200 and Daikin iTM on bacmanager.com. A heat pump for the hot water: NIBE S-series.

Frequently Asked Questions

What is the default Modbus address of a CoolMasterNet?

Slave address 80 (0x50) on RS-485, 9600 8N1. It is changed with line myid, and the value is given in hex. Modbus TCP uses port 502 and is off until you enable it and reboot.

How do I find the Modbus register of a VRF indoor unit on a CoolMasterNet?

Give the unit a Virtual Address (va command). Its 16-address block starts at VA × 16 + 1 in CoolAutomation's numbering, which is VA × 16 on the wire: VA1 mode is holding 16 (17 in 1-based tools). Check on your gateway which one yours answers.

What does malfunction code 65535 mean on a CoolMasterNet?

The gateway has lost communication with that indoor unit. 0 means no fault; any other value is the brand's own code (Daikin numbers translate to A1, E0, H0 and so on).

Why does the setpoint read 240?

Setpoint and room temperature are multiplied by 10: 240 is 24.0 °C.

Can I use an Intesis template on a CoolMasterNet?

No. The mode numbers differ (CoolMaster 0 = Cool, Intesis 0 = Auto and 4 = Cool), and so do the addresses. Each gateway has its own map.

Sources

CoolAutomation, Modbus Integration Guidelines — CoolMaster, CooLinkBridge, CooLinkHub, CooLinkNet, revision 1.3 (2025-07-17), and CoolMaster Product Line PRM, revision 0.10 (2024-11-01), support.coolautomation.com; the Loxone integration guide hosted there for the wire address of VA1. Tested against a simulator built from these documents, not against a physical gateway.

// beyond the indoor units

The VRF plus the rest of the building

ModbusManager Pro reads the VRF gateway next to meters, heat pumps and PLCs, and republishes the values as one Modbus TCP map or as MQTT topics with Home Assistant discovery.

Modbus gateway software →