Modbus RTU Intelligent Wireless Sensor Gateway Protocol Manual - Register Mapping Table and Communication Frame Format - Modbus Product Center

freeFree Technical Resource

This content is free to read, suitable for basic learning and search traffic.

Modbus RTU Intelligent Wireless Sensor Gateway Protocol Manual - Register Mapping Table and Communication Frame Format - Modbus Product Center缩略图
Modbus RTU Intelligent Wireless Sensor Gateway Protocol Manual

I. Product Overview

This product is a smart wireless sensor gateway device that supports the standardModbus RTU protocolof AndIntelligent wireless sensor gateway deviceand hasmulti node sensor data acquisition, communication parameter configurationSecondlydevice management function. Communication with upper computer (PLC, touch screen, SCADA system, etc.) through RS485 interface, supporting complete register read and write operations, can be widely used inindustrial automation, environmental monitoring, Smart Agriculture, Livestock Farming, Building Securityand other fields. As the core hub of wireless sensor networks, this gateway can manage up to 64 wireless sensor nodes simultaneously, converting the data from each sensor into the standard Modbus RTU protocol format for easy integration with the upper computer system.

As the core hub of wireless sensor networks, this gateway can manage up to64 wireless sensor nodesConvert the data from each sensor into a standard Modbus RTU protocol format for easy integration into the upper computer system.

II. Overview of Core Functional System (Calculated from Protocol)

Based on the register definitions, operation cases, and data structures in this protocol document, the following functional modules of the product can be fully calculated:

Serial NumberFunctional ModuleFunctional DescriptionCorresponding register/basis
1Modbus RTU slave communicationStandard Modbus RTU slave mode, RS485 physical interface, supports function codes 03/06/10Chapter 2 and Chapter 3
2Multi node sensor managementSupports up to 64 wireless sensor nodes online simultaneously, with each node addressing independently0002H Register (Range 0~63), Sensor Data Area Allocation Rules
37 types of sensors supportedTemperature and humidity, ear tags (livestock), smoke detector, radar, infrared, remote control, universal 1527 equipmentIndex Register Low 8-bit Type Encoding Definition
4Dual data reporting modeActive reporting mode (sensor automatic push)+Query reporting mode (host polling read)0005H register
5Sensor binding and pairing systemSoftware instruction binding+hardware button binding (long press for 5 seconds), LED indicator status feedback0006H Register, Chapter 6 Binding Management Instructions
6Full parameter register configurationThe slave address (1-247), baud rate (5 levels), and reporting mode can all be modified through registers0003H~0005H registers
7Sensor Lifecycle ManagementAdd nodes, read data, delete individual nodes, and clear all bindings with one clickWrite multiple registers (0x10) operation+0007H register
8Multi dimensional data acquisitionTemperature/humidity/vibration/smoke concentration/human presence detection/electricity/sub device type and other types of dataData1/Data2/Battery field definitions
9Battery level monitoringReal time battery capacity monitoring of each wireless sensor node (0%~100%)Battery register (+5 offset)
10Firmware version queryRead the firmware version number of the device for easy version management and maintenance confirmation0001H Read Only Register
11Broadcast address supportSupports Modbus broadcast address 0xFF (255) and can issue commands to all slave stationsAddress Range Description
12CRC16 verification mechanismUsing CRC-16/MODBUS polynomial 0xA001 verification to ensure data transmission integrityChapter 2 Verification Methods+Appendix C Language Algorithm

III. Detailed Explanation of Supported Sensor Types

According to the encoding definition of the low 8 bits (sensor type field) of the Index register in the protocol, the gateway supports the following7 sensor types, and can be extended more:

3.1 Sensor Type Encoding Table

Type EncodingSensor NameMain Data FieldsData1 MeaningData2 MeaningTypical Application Scenarios
00HUniversal 1527 Encoding DeviceSub device Type+Status DataIdleSub device Type EncodingUniversal Wireless Remote Control/Door Magnet/Door and Window Sensor
01HTemperature and Humidity SensorTemperature+Humidity+ElectricityTemperature Value (0.1 ° C)Humidity Value (0.1%)Greenhouse, Warehouse, Computer Room, Laboratory
02HEar tag sensor (livestock specific)Temperature+vibration counting+electricityTemperature value (0.1 ° C)Vibration frequency (times)Livestock temperature monitoring, estrus/health warning
03HSmoke detector/smoke sensorSmoke concentration+electricityIdleSmoke concentration (ppm)Warehouse fire prevention, kitchen security, factory fire protection
04HRadar Human Presence SensorPresence Status+BatteryIdlePresence Status (0=unmanned/1=manned)Intelligent Lighting, Conference Room, Toilet Linkage
05HInfrared PIR SensorPresence Status+BatteryIdlePresence Status (0=unmanned/1=manned)Intrusion Alarm, Corridor Sensing, Security Monitoring
06HWireless remote controlButton status+sub device typeIdleButton status dataRemote control, light control, device switch
07H+Reserved extensionTo be defined (XXXX)To be definedTo be definedExpansion bits for future new sensor types

3.2 Detailed Description of Data Formats for Each Sensor

① Temperature and Humidity Sensor (Type=01H)

Byte PositionField NameData TypeUnitValue RangeExample
+0~+1 (Byte0~1)IndexUINT16-High 8 bits=Number (0~63), Low 8 bits=Type (0x01)0x0001 represents Temperature and Humidity Sensor No.1
+2~+5 (Byte2~5)Device Address AddrUINT32-32-bit Unique Identifier0x12345678
+6~+7 (Byte6~7)Temperature Data1INT160.1 ° C-3276.8~3276.7 ° C0x00FB=25.1 ° C; 0xFEC=-2.0 ° C
+8~+9 (Byte8~9)Humidity Data2UINT160.1%0~100%0x028B=65.1%; 0x01F4=50.0%
+10~+11 (Byte10-11)BatteryUINT161%0%~100%0x0064=100%; 0x0032=50%

② Ear Tag Sensor - Livestock Breeding Specific (Type=02H)

A wireless ear tag sensor designed specifically for livestock such as cattle, sheep, and pigs, which is a major feature of this product.

Byte PositionField NameData TypeUnitValue RangeBusiness Meaning
+0~+1IndexUINT16-Low 8 Bits=0x02Identified as Ear Tag Type
+2~+5Device Address AddrUINT32-Unique identifierUnique ID for each livestock
+6~+7Temperature Data1INT160.1 ° CBody temperature rangeLivestock body temperature (e.g. 38.5 ° C=normal cow body temperature)
+8~+9Vibration Data2UINT16or0~65535Activity level/vibration frequency, used to determine the activity level or abnormal behavior of livestock
+10~+11BatteryUINT161%0%~100%Ear tag battery remaining power
Typical application scenarios: Large scale pig/cattle farms, by monitoring the body temperature and activity level of each animal, achieve early disease warning (fever recognition), estrus detection (sudden increase in activity level), loss alarm and other functions.

③ Smoke/Smoke Sensor (Type=03H)

Byte PositionField NameData TypeUnitValue RangeRemarks
+6~+7Data1IdleReserved Unused
+8~+9Smoke Concentration Data2UINT16ppm0~5000 ppm0x1388=5000 ppm (high concentration alarm threshold)
+10~+11BatteryUINT161%0% ~ 100%Sensor battery level

④ Radar human presence sensor (Type=04H)&infrared PIR sensor (Type=05H)

Both types of sensors are used for human presence detection, but their technical principles are different:

Comparison itemRadar sensor (Type=04H)Infrared PIR sensor (Type=05H)
Detection PrincipleMillimeter wave radar Doppler effectPyroelectric infrared detection
Data2 value0x0000=No one present; 0x0001=Someone0x0000=No one present; 0x0001=Someone
AdvantagesPenetrating plastic/glass, not affected by temperature, capable of detecting small movements (such as breathing), suitable for "lighting up when people are around"Low cost, extremely low power consumption, suitable for mobile detection
shortcomingrelatively high costUnable to detect stationary human body, affected by environmental temperature
Applicable scenariosIntelligent office/conference room/bathroom (precise presence detection)Corridor/aisle/entrance (motion detection)

⑤ Wireless Remote Control (Type=06H)&Universal 1527 Encoding Device (Type=00H)

fieldWireless Remote Control (06H)Universal 1527 device (00H)
Data1freefree
Data2Key status data (specific encoding depends on remote control model)Sub device type encoding (updated by the host after binding)
RemarkUsed to receive 433MHz remote control button signalsCompatible with most EV1527 encoded wireless transmission devices on the market (door magnets, water immersion, vibration, etc.)

4, Communication Parameters and Frame Format Specification

4.1 Basic Communication Parameters

parameter itemdefault valueOptional values/rangesconfiguration method
communication protocolModbus RTUfixed
physical interfaceRS485fixed
Data Format8N1 (8 data bits, no checksum, 1 stop bit)ConfigurableDefault 8N1
Slave Address11~247Write to 0003H Register
Broadcast Address255 (0xFF)Only 255Send commands to all slave stations
Baud Rate9600 bps9600/19200/38400/57600/115200Write to 0004H register
Verification methodCRC16Polynomial 0xA001 (MODBUS standard)Fixed
Maximum number of sensors64Hardware limitation
Frame interval time≥ 3.5 character time@9600bps ≈ 3.6ms; @115200bps ≈ 0.3msRTU protocol requirements

4.2 Baud Rate Configuration Comparison Table (0004H Register)

write valueActual baud rateSingle character time3.5 character intervalApplicable scenarios
09600 bps≈ 1.04 ms≈ 3.6 msDefault recommendation, stable and reliable
119200 bps≈ 0.52 ms≈ 1.8 msMedium speed demand
238400 bps≈ 0.26 ms≈ 0.9 msFaster speed
357600 bps≈ 0.17 ms≈ 0.6 mshigh-speed transmission
4115200 bps≈ 0.087 ms≈ 0.3 msmaximum speed, ensuring line quality

4.3 supported function code

function codenamedirectionpurpose
0x03read and hold registermaster station → slave stationRead version number, number of nodes, sensor data, etc
0x06Write a single registerMaster Station → Slave StationSet address, baud rate, mode, startup binding, etc
0x10Write multiple registersMaster Station → Slave StationAdd sensors, delete nodes, batch write data, etc

5, Complete Register Mapping Table

5.1 System Control Register Area (0001H~000FH)

register addressRegister NameRead/Write PermissionsData FormatValue Range/Description
0001HVersion NumberRead OnlyUIT16Device Firmware Version Number, such as 0x0102 for V1.2
0002HCurrent Number of Online NodesRead OnlyUINT16The current number of registered and bound sensor nodes (0~63)
0003HRS485 addressread and writeUINT16Modbus slave address, default 1, range 1~247
0004HSerial port baud rateread and writeUINT160=9600, 1=19200, 2=38400, 3=57600, 4=115200
0005HActive reporting mode settingread and writeUINT160=Active reporting enabled (default); 1=Enable query reporting
0006HActivate binding pairing functionJust writeUINT16Write 1 to start binding (indicator light flashing, automatic exit after 20 seconds timeout)
0007HClear all bound dataJust writeUINT16Clear all bound sensor data, rebind required
0008H ~ 000FHReserveReserve for future expansion use

5.2 Sensor Data Register Area (Starting from 0010H)

Each sensor occupies6 consecutive registers (12 bytes)Supports up to 64 sensors:

Sensor NumberRegister address range+0 Index+1 Addr_H+2 Addr_L+3 Data1+4 Data2+5 Battery
Sensor 10010H ~ 0015HNumber+TypeAddress 16 digits highAddress low 16 digitsData 1Data 2battery level
Sensor 20016H ~ 001BHDitto.Ditto.Ditto.Ditto.Ditto.Ditto.
Sensor 3001CH ~ 0021HDitto.Ditto.Ditto.Ditto.Ditto.Ditto.
Sensor 40022H ~ 0027HDitto.Ditto.Ditto.Ditto.Same asSame as
...Increasing by+6..................
Sensor N0010H+(N-1) * 6~0015H+(N-1) * 6Same asSame asSame asSame asSame asSame as
Sensor 64012AH~012FHSame asSame asSame asSame asSame asSame as
Address calculation formula:The starting register address of sensor N=0010H+(N-1) × 6

VI. Detailed explanation of working mode

6.1 Dual data reporting mode

The gateway supports two data reporting modes, which can be switched through the 0005H register:

Mode 0: Active reporting mode (default)

  • After wireless sensors detect data changes,automatically uploads the data to the gateway
  • . The gateway updates the internal register cache immediately after receiving it
  • . The upper computer can read the latest data at any time through the 0x03 function code.
  • Advantages:Good real-time performance, sensor side actively pushes, data updates in a timely manner
  • Applicable scenarios: scenarios that requirereal-time monitoring(such as temperature limit alarm, personnel intrusion detection, etc.)

Mode 1: Query Reporting Mode

  • Wireless sensors are only available inWhen receiving a gateway query commandOnly returned data
  • The upper computer initiates a read request → the gateway queries the sensor → returns data
  • Advantages:power savingThe sensor is mostly in a dormant state for most of the time
  • Applicable scenarios:battery poweredSensors, low-power priority scenarios (such as remote monitoring in agriculture)

6.2 Binding and pairing process

Before adding wireless sensors to the gateway, the binding and pairing operation must be completed first. SupportTwo triggering methods:

Method 1: Software instruction binding (written to 0006H via Modbus)

  1. The upper computer writes values to the 0006H register1Send 01 06 00 06 00 01 A8 0B
  2. The gateway enters binding mode,The indicator light starts flashing
  3. Enable wireless sensors for the targetSend data once(or trigger its emission signal)
  4. The gateway receives and recognizes sensor signals,Automatically allocate a free storage slotRecord the sensor address
  5. Binding successful: The indicator light stops flashing, and the gateway returns a response of 01 06 00 06 00 01 A8 0B (success code 1)
  6. If no sensor signal is received within 20 seconds, return timeout response 01 06 00 06 00 02 E8 0A (timeout code 2), exit binding mode

Method 2: Hardware key binding

  1. Long press the pairing button on the gateway panel for 5 seconds
  2. Enter binding mode (with exactly the same effect as software instructions)
  3. The subsequent steps are the same as Method 1
Tip: Regardless of the method, each binding operation can only add1 pieceSensors. If multiple sensors need to be added, the binding process needs to be repeated.

7, Complete operation case (10 instances including byte by byte parsing)

The following provides a complete operation example covering all functions, including hexadecimal request/response frames and field by field parsing.

7.1 System Register Operations (6 Examples)

Case 1: Read Device Firmware Version Number (Read 0001H)

ProjectContent
Operation TypeRead and Hold Register (Function Code 0x03)
Request Frame (Hexadecimal)01 00 01 00 01 D5 CA
Request Resolution[Address=01] [Function code=03] [Starting address=0001H] [Number of registers=1] [CRC=D5CA]
Response Frame (Hexadecimal)01 03 02 01 02 B8 44
Response analysis[Address=01] [Function code=03] [Byte count=2] [Data=0102] →Version 1.2[CRC=B844]

Case 2: Read the current number of online sensor nodes (read 0002H)

projectContent
Request frame01 03 00 02 00 01 25 CA
Response frame01 03 02 00 08 B9 82
Interpretation of resultsCurrently, there are8sensor nodes online

Case 3: Modify the RS485 slave address of the device (write 0003H → new address=2)

ProjectContent
Operation TypeWrite a single register (function code 0x06)
Request Frame01 06 00 03 00 02 F8 0B
Request Resolution[Address=01] [Function code=06] [Register=0003H] [Data=0002 → Address changed to 2] [CRC=F80A]
Response frame01 06 00 03 00 02 F8 0B (echo request frame, indicating successful writing)
AttentionAfter modification, the new address (0x02) needs to be used for subsequent communication

Case 4: Modify the serial port baud rate to 19200 (write 0004H → value=1)

ProjectContent
Request frame01 06 00 04 00 01 09 CB
Request parsing[Address=01] [Function code=06] [Register=0004H] [Data=0001 → Baud rate option 1] [CRC=09CB]
Response frame01 06 00 04 00 01 09 CB (successful)
Note thatAfter modification, the baud rate of the upper computer serial port needs to be switched to 19200 to continue communication

Case 5: Switch to query reporting mode (write 0005H → value=1)

ProjectContent
Request frame01 06 00 05 00 01 58 0B
Request parsing[Address=01] [Function Code=06] [Register=0005H] [Data=0001 → Query Mode] [CRC=580B]
Response frame01 06 00 05 00 01 58 0B (successfully switched to query reporting mode)

Case 6: Start sensor binding pairing (write 0006H → value=1)

projectContent
Request frame01 06 00 06 00 01 A8 0B
Request parsing[Address=01] [Function Code=06] [Register=0006H] [Data=0001 → Startup Binding] [CRC=A80B]
Response frame (successful)01 06 00 06 00 01 A8 0B (Code 1=Command execution successful, waiting for sensor network access)
Response frame (timeout)01 06 00 06 00 02 E8 0A (Code 2=No sensor connected to the network within 20 seconds, timeout exit)

7.2 Sensor data register operation (4 examples)

Case 7: Manually adding sensor 1 to the system (write address 0x12345678)

When the 32-bit address of the sensor device is known, it can be directly added to the system through register writing:

projectContent
Operation TypeWrite multiple registers (function code 0x10)
destination addressThe starting address 0010H of sensor 1 data area is continuously written into three registers (Index+Addr_H+Addr_L)
Request frame01 10 00 10 00 03 06 00 01 12 34 56 78 A1 E1
Byte by byte parsing[01=Address] [10=Function Code] [00 10=Starting Address 0010H] [00 03=Writing 3 registers]
[06=6 bytes of data in total] [00 01=1+temperature and humidity type] [12 34=address high 16 bits] [56 78=address low 16 bits] [A1 E1=CRC]
Response frame01 10 00 10 00 03 81 CD (confirm to write 3 registers starting from 0010H)

Case 8: Read all data from sensor 1 (6 registers=12 bytes)

projectContent
Request frame01 03 00 10 00 06 C4 0D
Request parsing[01=Address] [03=Function Code] [00 10=Starting Address 0010H] [00 06=Read 6 registers] [CRC=C40D]
Response frame01 03 0C 00 01 12 34 56 78 00 FA 01 F4 00 64 B5 F2
Byte by byte parsing[01=Address] [03=Function Code] [0C=12 bytes of data]
[00 01 → Sensor 1+Temperature and Humidity Type (01H)]
[12 34 56 78 → 32-bit device address 0x12345678]
[00 FA → Temperature 25.0 ° C (250 × 0.1)]
[01 F4 → Humidity 50.0% (500 × 0.1)]
[00 64 → Battery 100%]
[B5 F2 = CRC]

Case 9: Delete Sensor 1 (Clear Address Register)

The method to delete sensors is to reset all corresponding address registers to zero:

projectContent
Request frame01 10 00 10 00 03 06 00 00 00 00 00 00 E7 15
Request parsing[01=Address] [10=Function Code] [00 10=Starting Address] [00 03=3 registers]
[06=6 bytes of data] [00 00 00 00 00=all reset] [E7 15=CRC]
Response frame01 10 00 10 00 03 81 CD (deleted successfully)
EffectThe address of sensor 1 has been reset, the system no longer receives data from that sensor, and the storage slot has been released

Case 10: Directly writing temperature and humidity data from sensor 1

projectContent
Request frame01 10 00 13 00 02 01 2C 02 58 72 19
Request parsing[01=Address] [10=Function Code] [00 13=Starting Address 0013H (Data1)] [00 02=Write 2 registers]
[04=4-byte data] [01 2C → Temperature 30.0 ° C (300 × 0.1)] [02 58 → Humidity 60.0% (600 × 0.1)] [72 19=CRC]
Response frame01 10 00 13 00 02 B0 0D (write successful)

8. Exception handling When the slave station detects an illegal operation, it returns an abnormal response:

8.1 Modbus Exception Response Format

When an illegal operation is detected by the slave station, an abnormal response is returned:

  • The highest bit of the normal function code becomes 1 (such as 0x03 → 0x83, 0x06 → 0x86, 0x10 → 0x90)
  • followed by a 1-byte exception code
Exception CodeMeaningCommon CausesSolution
01Illegal Function CodeUnsupported Function Code UsedOnly 0x03/0x06/0x10
02Illegal Data AddressRegister Address Exceeded Valid RangeCheck if Address is within the range of 0001H~012FH
03Illegal Data ValueThe written data value exceeds the allowed rangeCheck the value range (such as address should be between 1-247)

8.2 Binding function return code (0006H register)

Return codeMeaningindicates that
1command execution was successfulBinding instruction has been received, gateway enters pairing mode and waits for sensor network access
2Binding timeoutNo sensor signal received within 20 seconds, automatically exits binding mode

8.3 Fault diagnosis checklist

Problem phenomenonPossible causesSolution
Communication timeout, no responseRS485 address mismatch or baud rate inconsistencyCheck configuration of 0003H address register and 0004H baud rate register
Sensor data read all zeroSensor node unregistered/bound, or address write errorCheck if the address register starting from 0010H is correctly written to non-zero values
Unable to write to registerFunction code usage error or insufficient permissionsConfirm correct function code: 0x06 for single write, 0x10 for multiple writes; Note that 0001H/0002H is read-only
CRC check error. Error occurred during data transmissionCheck the RS485 line connection (whether A+/B - is reversed, whether the terminal resistance is missing), recalculate CRC
Binding failure (repeated timeout)Sensor is not within communication range or battery is exhaustedShorten the distance between the sensor and the gateway, replace the sensor battery
Partial sensor data is not updatedThe sensor exceeds the wireless signal coverage rangeAdjust the gateway antenna direction, or add a repeater

9. Precautions and best practices

9.1 Key precautions

  1. Frame interval timemust be maintained between adjacent frames. BI_659] 3.5 character time3.5 character timeThe silence interval. Shortest frame interval at different baud rates:
    • 9600 bps: approximately 3.6 ms
    • 115200 bps: approximately 0.3 ms
  2. Big-endian byte orderWhen using function code 0x10 to write multiple registers, data must be written according toBig End ModeOrganization, high bytes come first and low bytes come last.
  3. Broadcast operation no response: When sending a command to the broadcast address 0xFF, all slave stations perform the operation butdoes not return a response frame.
  4. Sensor addition rule: When adding a sensor, the address register (Addr_H+Addr_L) must be writtenNon zero value; Writing all zeros is equivalent to deleting the node.
  5. Operation Interval: After updating sensor data, wait for at least100msbefore performing the next register operation.
  6. Risk of clearing binding: Writing to the 0007H register willclear all bound sensor data at once. Before operation, please confirm that there is no need to retain the existing configuration. After clearing, you need to rebind one by one.

9.2 Recommended Operating Procedure

  1. First Power On: Read 0001H to confirm firmware version, read 0002H to confirm initial state
  2. Configure communication parameters: Modify 0003H (address), 0004H (baud rate), 0005H (reporting mode) as needed
  3. Bind sensors: Add sensors one by one by pressing 0006H or physically
  4. Verify binding: Read 0002H to confirm node number, read corresponding sensor data area to confirm data is normal
  5. Daily operation and maintenance: Regularly read sensor Battery field to monitor battery level and replace low battery sensor batteries in a timely manner

Implement CRC16 algorithm

This protocol adoptsMODBUS standard CRC16verification algorithm, polynomial0xA001(i.e. bit reversed form of 0x8005). The following is a complete C language reference implementation:

#include <stdint.h>

/**
 * MODBUS CRC16 计算
 * @param data  待计算的数据缓冲区指针
 * @param len   数据长度(字节)
 * @return      16 位 CRC 校验值(低字节在前)
 *
 * 多项式:0xA001(MODBUS 标准)
 * 初始值:0xFFFF
 */
uint16_t calc_crc(uint8_t *data, uint16_t len)
{
    uint16_t crc = 0xFFFF;          // 初始值
    for (uint16_t i = 0; i < len; i++)
    {
        crc ^= data[i];              // 与当前字节异或
        for (uint8_t j = 0; j < 8; j++)  // 逐位处理
        {
            if (crc & 0x0001)       // 最低位为 1
            {
                crc >>= 1;           // 右移一位
                crc ^= 0xA001;       // 与多项式异或
            }
            else
            {
                crc >>= 1;           // 仅右移
            }
        }
    }
    return crc;
}

/* 使用示例:
 * uint8_t frame[] = {0x01, 0x03, 0x00, 0x01, 0x00, 0x01};
 * uint16_t crc = calc_crc(frame, 6);
 * 结果:crc = 0xCAD5(低字节 0xD5 在前,高字节 0xCA 在后)
 */

11. Data Download and Technical Support

  • This document version:V1.3(Updated on October 3, 2025)
  • Protocol follows standards:Modbus Industrial Standard Protocol Specification
  • The specific register definition shall be based on the actual firmware of the device
  • If you need technical support, please contact the manufacturer for the latest register mapping table and protocol documentation

Version iteration history

Version numberRelease dateMain changes
V1.12025-09-01Basic version, using standard Modbus RTU protocol as the main node communication protocol
V1.22025-09-21Added software instruction start binding function; Added hardware button start binding function
V1.3 (current)2025-10-03Revised the maximum supported number of sensors to 64; Add sensor type data fields; Provide detailed instructions on the format of sensor data segments; Fixed the binding timeout to 20 seconds; Add 0007H register (one click clear all bindings)

12, Typical application scenarios

Scenario 1: Smart Agriculture - Greenhouse Environment Monitoring System

Deploy inside the greenhouseTemperature and humidity sensor (Type=01H)aggregates data through this gateway and uploads it to the PLC or touch screen control system via Modbus RTU. It can be linked with ventilation fans, sprinkler systems, sunshades and other equipment to achieve automatic temperature and humidity control. Supports up to 64 sensor points64 sensor pointsMeet the multi-point monitoring needs of large connected greenhouses.

Scenario 2: Smart Livestock - Livestock Health Management

Wear for each cow/sheepWireless Ear Tag Sensor (Type=02H)The gateway collects temperature and activity data of livestock in a centralized manner. When the body temperature of a certain livestock exceeds the set threshold, an automatic alarm (disease warning) will be triggered, or when there is an abnormal change in activity, the estrus/health status will be determined.64 node capacityCapable of covering the livestock management needs of small and medium-sized farms.

Scenario 3: Fire Safety - Warehouse/Computer Room Fireworks Monitoring

DeploymentSmoke sensor (Type=03H)Real time monitoring of smoke concentration in key areas such as warehouses and computer rooms. When the concentration exceeds the threshold, the Modbus upper computer triggers the sound and light alarm, exhaust system, or notifies the fire linkage platform. Combined with temperature and humidity sensors, comprehensive environmental safety monitoring can also be achieved.

Scenario 4: Intelligent Building - Human Presence Perception and Lighting Linkage

Install in offices, conference rooms, and bathroomsRadar sensor (Type=04H)orInfrared PIR sensor (Type=05H)To achieve precise personnel presence detection. The radar scheme can detect micro movements (even breathing), achieving true“People are about to light upIntelligent lighting control greatly saves energy. Sensor data is connected to the Building Automation System (BAS) or KNX/Modbus bus through a gateway.

Scenario 5: Security Alarm - Intrusion Detection and Wireless Remote Control

CombineInfrared sensor (Type=05H)Implement perimeter intrusion detection, combined withWireless remote control (Type=06H)Used for arming/disarming operations.Universal 1527 device (Type=00H)Compatible with various wireless detectors such as door magnets, glass breakage, and water immersion, a complete wireless security system is built, and all data is uniformly connected to the alarm host or SCADA platform through Modbus RTU.

Put this resource to use in a real project?

Go to the Tool Center for message parsing, CRC verification and device debugging, or submit your requirements for selection and integration advice.

Engineer Membership

Turn this article into actionable debugging resources

After activation, you can use advanced message parsing, resource pack downloads, code examples, engineering cases and priority technical support, suitable for real project delivery.

Unlimited Advanced Tools
Resource & Code Packs
Complete Engineering Case Library
Priority Technical Support

Leave a Reply

Your email address will not be published. Required fields are marked *.