aqotec RM360 via Modbus RTU Modbus Extension RS485

Use cases

• Monitor outdoor, flow, and return temperatures on a live dashboard to verify district heating supply conditions.
• Track heat meter energy consumption and flow rates over time to validate billing data for building operators.
• Create alerts when error bytes indicate a fault condition on any of the four heating circuits.
• Adjust HC1 to HC4 room temperature setpoints remotely during seasonal commissioning without a site visit.
• Switch TC1 and TC2 hot water tank modes from the cloud to respond to occupancy changes or maintenance schedules.
• Log primary valve position data to diagnose control stability and detect hunting or stuck valve issues.

Installation

1. 1Connect the RS485 A and B terminals of the ModbusCloud gateway (MCG or MLP series) to the corresponding RS485 terminals on the Aqotec RM360 controller.
2. 2Set the Modbus baud rate on the gateway to 19200 to match the RM360 default communication settings.
3. 3Configure a unique Modbus slave address on the RM360 and enter the same address in the ModbusCloud template settings.
4. 4Import the Aqotec RM360 Modbus RTU template into your ModbusCloud project from the template library.
5. 5Verify communication by checking that outdoor temperature and heat meter readings appear correctly on the cloud dashboard.
6. 6Confirm that float32 registers are read as two consecutive addresses and that the byte order matches the RM360 register map.

Things to watch for

01

Why are some temperature or energy readings showing incorrect or extremely large values?

The RM360 register map uses mixed data types including float32 values that span two consecutive addresses. Ensure the template is configured with the correct data type and byte order (typically big-endian) for each register. A mismatch will produce nonsensical values.

02

What baud rate should I use for the RS485 connection?

The RM360 communicates at 19200 baud by default. Make sure both the ModbusCloud gateway and the controller are set to the same baud rate, parity, and stop bit configuration.

03

Can I control all four heating circuits even if my installation uses fewer?

Yes. The template exposes HC1 through HC4, but unused circuits will simply return default or zero values. You can ignore or hide unused registers in the ModbusCloud dashboard.

04

How do I identify which fault has occurred using the error bytes?

The template reads error bytes 1 through 4 from the RM360. Refer to the official Aqotec RM360 controller documentation for the specific bit definitions and fault codes associated with each error byte.

Registers (98)

98 read / 29 write

More Aqotec templates

aqotec RM360 via Modbus TCP

Aqotec

Modbus TCP

Monitors and controls an aqotec RM360 district heating substation controller via Modbus TCP

98 registers

More RTU templates

Alnor HRU-P

Alnor Systemy Wentylacji Sp. z o. o.

Modbus RTU

Controls Alnor HRU-P heat recovery ventilation units via Modbus RTU.

49 registers7

Alnor HRU

Alnor Systemy Wentylacji Sp. z o. o.

Modbus RTU

Controls and monitors Alnor heat recovery ventilation units via Modbus RTU.

29 registers13

Wattsonic - Schmachtl Sun Energy Box

Wattsonic

Modbus RTU

Monitors Schmachtl Wattsonic hybrid inverter via Modbus RTU

92 registers72

Heidelberg Wallbox Energy Control

AMPERFIED GmbH

Modbus RTU

Controls and monitors Heidelberg Wallbox Energy Control EV charger via Modbus RTU.

22 registers67

connecdoor.controller

connecdoor

Modbus RTU

Controls and monitors smart door access points via RS485

0 registers53

Belimo Air-Water Actuator Modbus RTU

Belimo

Modbus RTU

Controls communicative damper and valve actuators via Modbus RTU.

20 registers46