Modbus TCP
Last updated
Last updated
Skysens AgPM can be connected any Modbus TCP devices. User can configure and start to monitor their data from a Modbus TCP data source.
Modbus TCP adapts the Modbus industrial communication protocol for use over TCP/IP networks like Ethernet, enabling data exchange between devices in industrial automation settings via standard network infrastructure.
Adding a Modbus TCP source is three-step process: Source Information, Slave Information and Register Information.
Source Information
Services: A list of pre-configured services that can be helpful for load balancing
Name: Descriptive name for your Modbus TCP device
Self Connect (Optional) : Select If your Modbus tcp device supports slave mod that can be automatically connected
Addresses (Optional) : Select a configured IP, Port connection if you add some connections before
IP: Modbus TCP device IP address
Port: Modbus TCP device Port number
TCP-Timeout: TCP connection time out. For Ethernet connection it will be recommended 1s, for GPS connections it will be recommended 10s
Slave Information
A Modbus TCP connection need to be have a slave ID in order to read data.
Slave ID: Slave identifier is used established Modbus Communication.
Interval: Data reading frequency (in seconds)
Register Information
Modbus TCP registers are memory locations within a Modbus device used to store and exchange data; they are addressed for reading or writing various data types, enabling communication between a master and slave devices. You can read multiple registers on a single connection.
Field Name: An identifier for register
Address: Modbus Register Addresses Such as: 0001,0002
Quantity: Number of reading registers
Unit: Reading data's unit
Format: Data format. Such as: int32, float
