NanoDetect PRO Modbus TCP/IP Connectivity

Modbus TCP/IP Communication Guide

The NanoDetect PRO sensor supports Modbus TCP/IP communication over an Ethernet interface. Configuration is performed using the mobile application.

Step 1 Open the mobile application and select “Settings” (bottom right of the screen).

Step 2 Select “Direct Configuration.”

Step 3 Select the sensor type “NanoDetect PRO.”

Step 4 Follow the on-screen instructions to place the device in configuration mode. This is achieved either by power cycling the sensor (disconnect and reconnect the power supply) or by pressing the sensor button twice.

Step 5 Select “Next Step” to continue.

A list of available devices will be displayed. Devices are identified by MAC address and device name.

Step 6 Select the appropriate NanoDetect PRO from the list.

Step 7 From the communication options, select “Modbus IP.”

Step 8 Enter the required Modbus TCP/IP parameters:

• TCP Port
• Device ID (Unit Identifier)

Step 9 Select “Save” to apply the settings. A long audible beep confirms successful configuration.

Communication Parameters

Modbus TCP/IP uses standard Ethernet and TCP transport. Serial communication parameters such as baud rate, parity, and stop bits do not apply.

Default Modbus TCP port: 502
If a different port is configured, the Modbus client (PLC, SCADA, BMS, etc.) must use the same port number.

The Unit Identifier (Device ID) corresponds to the Unit ID field in the Modbus Application Protocol (MBAP) header. In native Modbus TCP networks, this value is typically used for logical device identification. When communicating through a Modbus TCP-to-RTU gateway, the Unit Identifier must match the target RTU slave address.

Ethernet Connection

The NanoDetect PRO provides a 10/100Base-T Ethernet interface with an RJ45 connector located on the rear of the device. Connect the device to the local area network using a standard Ethernet cable.

Network Configuration

The device must be assigned valid network parameters to communicate on the network. The device operate using DHCP (automatic IP address assignment).

Ensure the Modbus client is configured to communicate with the correct IP address and TCP port.

Protocol Notes

The Modbus register map used for Modbus TCP/IP communication is identical to the register map defined for Modbus RTU. All register addresses, scaling factors, and data formats remain the same.

Modbus Protocol

Commands

Read holding register

Read input register

Write single register

• Read Input Register (0x04) command 01 04 0038 0022 F1DEto read all input register
• Write single Register (0x06) command 01 06 0004 07E8 CA75 to set the Modbus holding register address to 0x06 (set device data 2024 year)
• Read holding Register (0x03) command 01 03 0002 0007 A5C8 to read all holding register.

Input Register Address

**Note: When the value is 65535, it indicates that the value is invalid**

Example
Read Temperature:
Send:
01 04 00 03 00 02 34 0B
Receive:
01 04 04 41 B7 85 1F 7C C6

'Temperature is: 22.94^oC'

Holding Register Address

BACK TO SUPPORT CENTER