> For the complete documentation index, see [llms.txt](https://docs.skysens.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skysens.io/sources/connection-types/modbus-tcp.md).

# Modbus TCP

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. 

<figure><img src="https://803875272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUGOLnOOPZHTcQBNC5GI%2Fuploads%2FoBr7kNCvQeyPtlHniGcb%2Fimage.png?alt=media&amp;token=ff144704-4e7b-41c0-9a7b-3d3ead04be37" alt=""><figcaption><p>Select Modbus TCP option</p></figcaption></figure>

Adding a Modbus TCP source is three-step process: Source Information, Slave Information and Register Information.&#x20;

<figure><img src="https://803875272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUGOLnOOPZHTcQBNC5GI%2Fuploads%2FnBxPOyFTca0qAIBTEtqE%2Fimage.png?alt=media&amp;token=560e18e7-76c9-4d41-bc5f-6493a71ceeca" alt=""><figcaption><p>Modbus TCP - 1</p></figcaption></figure>

**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&#x20;
* 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

<figure><img src="https://803875272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUGOLnOOPZHTcQBNC5GI%2Fuploads%2FVbKbP5zgzKb2S3TWW136%2Fimage.png?alt=media&amp;token=84db32c4-c389-42e5-bf6d-6c3016c1232b" alt=""><figcaption><p>Modbus TCP - 2</p></figcaption></figure>

**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)

<figure><img src="https://803875272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUGOLnOOPZHTcQBNC5GI%2Fuploads%2F1LDNm7F5JeWEq0Lzm13M%2Fimage.png?alt=media&amp;token=3f0eff60-0b51-46a9-b138-969ba3dc9ede" alt=""><figcaption><p>Modbus TCP - 3</p></figcaption></figure>

**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&#x20;

Format: Data format. Such as: int32, float&#x20;