|
<< Click to Display Table of Contents >> Modbus TCP |
  
|
|
<< Click to Display Table of Contents >> Modbus TCP |
|
To create a new Modbus TCP(UDP) server select the menu item Modbus TCP(UDP). You’ll see the following window:
List or properties:
Property |
ST script field* |
Description |
|---|---|---|
Name |
|
Name of the Modbus TCP server. |
IP or DNS |
ipaddress |
IP address or DNS of the Modbus TCP server. |
Port |
port |
Port of the Modbus TCP server. |
Poll interval |
interval |
Polling interval (period) of the server's requests. |
Type |
type |
Communication protocol of Modbus server - TCP or UDP. |
Request type |
requesttype |
Choose request type: - Maximum registers - if you choose this type the application during polling will send maximum modbus pointers in 1 polling request. - Consecutive registers - if you choose this type the application during polling will send only consecutive modbus pointers in 1 polling request. - 1 pointer registers - if you choose this type the application during polling will send only registers used by 1 pointer in 1 polling request. |
RTU via TCP(UDP) |
rtuviatcp |
Check if you use Modbus converter from serial into TCP(UDP) protocol. |
Without function 6 |
withoutfun |
Check if your controller doesn’t support Modbus writing function 6. |
Read delay |
readdelay |
This value tells the client how long to wait data from the server. Setting this to very small values (as low as 1ms) can result in high processor consumption, but better responsiveness when data arrives. Very high values have the opposite effect. |
* This field is used in ST scripts. For example: Servers.Server1.requesttype = 0. In this script command request type of the Server1 become Maximum registers. Also for all servers you can use fields:
▪connect - connect to the server.
▪connected - check connection.
▪lostconnection - check lost or not connection.