Modbus TCP
Modbus TCP is a version of the Modbus protocol based on Ethernet, which uses TCP/IP for communication. Unlike the traditional Modbus RTU protocol, Modbus TCP allows devices to be interconnected directly through Ethernet without any special hardware or communication interface. Therefore, Modbus TCP has higher communication speed and wider application range.
In addition to supporting data acquisition and processing via TCP client mode, the Neuron Modbus TCP plugin also supports TCP server mode, which allows devices to connect to Neuron actively. This feature is mainly used for 4G DTU because the IP address of 4G network is a private IP. In this case, the DTU device can only connect to Neuron actively.
Plugins
Plugin | Description |
---|---|
Modbus TCP | Standard Modbus TCP protocol implementation supports both TCP client and server modes, providing better compatibility with devices. |
Modbus TCP community | The open-source version of the standard Modbus TCP protocol only supports TCP client mode. |
Modbus TCP QH | Customized Modbus TCP protocol implementation supports a maximum of 65530 bytes for one read operation, while the standard protocol only allows a maximum of 250 bytes to be read at a time. |
Parameters
Parameter | Description |
---|---|
Connection Mode | When selecting Ethernet TCP connection, you can choose Neuron as the TCP client or server. |
Send Interval | The waiting time between sending each read/write command. Some serial devices may discard certain commands if they receive consecutive commands in a short period of time. |
IP Address | The IP address of the device when using TCP connection with Neuron as the client, or the IP address of Neuron when using TCP connection with Neuron as the server. The default value is 0.0.0.0. |
Port | The port number of the device when using TCP connection with Neuron as the client, or the port number of Neuron when using TCP connection with Neuron as the server. |
Connection Timeout | The time the system waits for a device to respond to a command. |
Data types
- INT16
- UINT16
- INT32
- UINT32
- INT64
- UINT64
- FLOAT
- DOUBLE
- BIT
- STRING
Address format
SLAVE!ADDRESS[.BIT][#ENDIAN][.LEN[H][L][D][E]]
SLAVE
Required, Slave is the slave address or site number.
ADDRESS
Required, Address is the register address.The Modbus protocol has four areas, each area has a maximum of 65536 registers, and the address range of each area is shown in the table below. It should be noted that the storage area as large as 65536 is generally not required in practical applications. Generally, PLC manufacturers generally use an address range within 10000. Please pay attention to fill in the correct point address according to the area and function code of the device.
Area | Address Range | Attribute | Register Size | Function Code | Data Type |
---|---|---|---|---|---|
Coil | 000001 ~ 065536 | Read/Write | 1Bit | 0x01,0x05,0x0f | BIT |
Input | 100001 ~ 165536 | Read/Write | 1Bit | 0x02 | BIT |
Input Register | 300001 ~ 365536 | Read/Write | 16Bit,2Byte | 0x04 | BIT,INT16,UINT16,INT32,UINT32,INT64,UINT64,FLOAT,DOUBLE,STRING |
Hold Register | 400001 ~ 465536 | Read/Write | 16Bit,2Byte | 0x03,0x06,0x10 | BIT,INT16,UINT16,INT32,UINT32,INT64,UINT64,FLOAT,DOUBLE,STRING |
tip Some device specification documents may use function codes and register addresses to describe commands. Since register address numbers start at 0, the register address range for each area is 0 to 65535. Neuron uses a PLC configuration address specification, so the addresses configured in Neuron start from 1.
The conversion rule for the configuration address specification is as follows: determine the highest digit of the address based on the function code, and add 1 to the register address to obtain the address used in Neuron.
For example, if the function code is 0x03 and the register address is 0, the address used in Neuron is 400001. If the function code is 0x02 and the register address is 5, the address used in Neuron is 100006.
.BIT
Optional, specify a specific bit in a registe
Address | Data Type | Description |
---|---|---|
1!300004.0 | bit | Refers to station 1, input area, address 300004, bit 0 |
1!400010.4 | bit | Refers to station 1, hold register area, address 400010, bit 4 |
2!400001.15 | bit | Refers to station 2, hold register area, address 400001, bit 15 |
#ENDIAN
Optional, byte order, applicable to data types int16/uint16/int32/uint32/float, see the table below for details. | Symbol | Byte Order | Supported Data Types | Note | | —- | ———- | ————————— | ——- | | #B | 2,1 | int16/uint16 | | | #L | 1,2 | int16/uint16 | Default byte order if not specified | | #LL | 1,2,3,4 | int32/uint32/float | Default byte order if not specified | | #LB | 2,1,4,3 | int32/uint32/float | | | #BB | 3,4,1,2 | int32/uint32/float | | | #BL | 4,3,2,1 | int32/uint32/float | |
.LEN[H][L][D][E]
When the data type is STRING, .LEN is a required field, indicating the number of bytes the string occupies. Each register contains four storage methods: H, L, D, and E, as shown in the table below. | Symbol | Description | | —- | ——————————————————- | | H | One register stores two bytes, with the high byte first | | L | One register stores two bytes, with the low byte first | | D | One register stores one byte, and it is stored in the low byte | | E | One register stores one byte, and it is stored in the high byte|
Examples
Address | Data Type | Description |
---|---|---|
1!300004 | int16 | Refers to station 1, input area, address 300004, byte order #L |
1!300004#B | int16 | Refers to station 1, input area, address 300004, byte order #B |
1!300004#L | uint16 | Refers to station 1, input area, address 300004, byte order #L |
1!400004 | int16 | Refers to station 1, hold register area, address 400004, byte order #L |
1!400004#L | int16 | Refers to station 1, hold register area, address 400004, byte order #L |
1!400004#B | uint16 | Refers to station 1, hold register area, address 400004, byte order #B |
1!300004 | int32 | Refers to station 1, input area, address 300004, byte order #LL |
1!300004#BB | uint32 | Refers to station 1, input area, address 300004, byte order #BB |
1!300004#LB | uint32 | Refers to station 1, input area, address 300004, byte order #LB |
1!300004#BL | float | Refers to station 1, input area, address 300004, byte order #BL |
1!300004#LL | int32 | Refers to station 1, input area, address 300004, byte order #LL |
1!400004 | int32 | Refers to station 1, hold register area, address 400004, byte order #LL |
1!400004#LB | uint32 | Refers to station 1, hold register area, address 400004, byte order #LB |
1!400004#BB | uint32 | Refers to station 1, hold register area, address 400004, byte order #BB |
1!400004#LL | int32 | Refers to station 1, hold register area, address 400004, byte order #LL |
1!400004#BL | float | Refers to station 1, hold register area, address 400004, byte order #BL |
1!300001.10 | String | Refers to station 1, input area, address 300001, character length 10, byte order L, which occupies addresses 300001 to 300005 |
1!300001.10H | String | Refers to station 1, input area, address 300001, character length 10, byte order H, which occupies addresses 300001 to 300005 |
1!300001.10L | String | Refers to station 1, input area, address 300001, character length 10, byte order L, which occupies addresses 300001 to 300005 |
1!400001.10 | String | Refers to station 1, hold register area, address 400001, character length 10, byte order L, which occupies addresses 400001 to 400005 |
1!400001.10H | String | Refers to station 1, hold register area, address 400001, character length 10, byte order H, which occupies addresses 400001 to 400005 |
1!400001.10L | String | Refers to station 1, hold register area, address 400001, character length 10, byte order L, which occupies addresses 400001 to 400005 |
1!400001.10D | String | Refers to station 1, hold register area, address 300001, character length 10, byte order D, which occupies addresses 400001 to 400005 |
1!400001.10E | String | Refers to station 1, hold register area, address 300001, character length 10, byte order E, which occupies addresses 400001 to 400005 |