Modbus TCP Client Device Edit

From Control Solutions IoTServer Documentation
Jump to navigation Jump to search

The Modbus TCP Devices page is where you set up the list of Modbus TCP servers (slaves) that this IoTServer will read from and write to while acting as a Modbus TCP client (master). The full set of parameters required for each device is set up once here, and then referenced by device number in any number of read or write maps.

Modbus TCP client device edit 1.jpg

Number – Device number that will be reference in read and write maps.

Modbus TCP client device edit 2.jpg

Name – Arbitrary name for this device, used only as a reference in the web UI.

Modbus TCP client device edit 3.jpg

RemoteIP – The IP address in “a.b.c.d” form that the TCP client will attempt to connect to for read and write maps referencing this device number.

Port – The port number that should be opened at the remote IP address given. Port number will default to 502 if not given or set to zero.

Modbus TCP client device edit 4.jpg

Unit – An optional unit number that will be used when connecting to this remote TCP device. If none is given or is set to zero, then unit 1 will be used.

Modbus TCP client device edit 5.jpg

Poll Time – The default poll time that will be used if none is given explicitly in individual read and write maps.

Modbus TCP client device edit 6.jpg

Timeout – The amount of time that the client should wait before flagging the attempted read or write with a “no response” error.