OCHSNER OTS Heat Pump

Use cases

• Monitor heat pump flow and return temperatures on a live dashboard to verify system performance.
• Set target heating and DHW temperatures remotely without visiting the installation site.
• Create an alert when the outdoor temperature drops below a threshold and the auxiliary heater activates unexpectedly.
• Track compressor runtime hours and energy consumption over time to plan preventive maintenance.
• Feed external room sensor data into each heating circuit by writing room temperature and humidity values via Modbus TCP.
• Compare heat pump energy counters with auxiliary heater counters to evaluate system efficiency.

Installation

1. 1Verify that the OCHSNER OTS Controller software is at version V03.00.000 or higher, and that the APP version meets the minimum requirements (Android >= V2.22.6, iOS >= V3.3.3).
2. 2Connect the ModbusCloud gateway (MCG or MLP series) to the same local network as the OCHSNER OTS controller via Ethernet.
3. 3Configure the Modbus TCP connection on the OTS controller and note the IP address and port number assigned to the Modbus TCP server.
4. 4In the ModbusCloud platform, add a new device and import the OCHSNER OTS Heat Pump template from the template library.
5. 5Enter the IP address and port of the OTS controller in the gateway configuration and verify that data appears on the dashboard.
6. 6Test a write command, such as changing the target DHW temperature, to confirm bidirectional communication is working.

Things to watch for

01

Why do energy counters or compressor hours show incorrect values?

These registers use uint32 values that span two consecutive Modbus addresses. Make sure the template is correctly configured to read both addresses as a single 32-bit value. The template handles this by default, but custom register configurations may break the mapping.

02

Why does writing the target operating mode not work?

Read and write addresses differ for some registers. The target operating mode is read from address 11 but must be written to address 1. The template maps these separately. If you created a custom register, verify you are using the correct write address.

03

What firmware version is required on the OCHSNER controller?

The OTS Controller software must be at least V03.00.000. The APP version must also be V03.00.000 or higher. The Android APP requires V2.22.6 and the iOS APP requires V3.3.3. Older versions do not support Modbus TCP communication.

04

The gateway cannot reach the OTS controller over Modbus TCP. What should I check?

Confirm that the gateway and the OTS controller are on the same network or VLAN. Verify the IP address and TCP port configured on the controller. Check that no firewall rules are blocking traffic on the Modbus TCP port (typically 502).

Registers (47)

42 read / 13 write

More Ochsner templates

Ochsner BWWP Genius 333

Ochsner

Modbus RTU

4 registers

More TCP templates

Domekt R 400 V

Komfovent

Modbus TCP

Controls Komfovent Domekt recuperator ventilation via Modbus TCP

25 registers118

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597

NIBE Nibe S-Series (SG Ready)

NIBE

Modbus TCP

5 registers1

SunSpec Model 139 — LVRTX

SunSpec

Modbus TCP

12 registers

Atmoce MG100 M-gateway (battery)

Atmoce

Modbus TCP

6 registers

Victron Meter AcOut

Victron

Modbus TCP

16 registers