# ModbusMasterTCP

## `ModbusMasterTCP` (FB)

FUNCTION\_BLOCK ModbusMasterTCP IMPLEMENTS IModbusConnector

InOut:

| Scope       | Name                       | Type             | Initial         | Comment                                                                                                                                                                         |
| ----------- | -------------------------- | ---------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Input       | `xEnable`                  | `BOOL`           | TRUE            |                                                                                                                                                                                 |
| Input       | `xResetAuto`               | `BOOL`           |                 | <p>Reset manual override of the connected<br>slaves.</p>                                                                                                                        |
| Input       | `sIPAddress`               | `STRING(15)`     | ‘192.168.60.10’ |                                                                                                                                                                                 |
| Input Const | `uiPort`                   | `UINT`           | 502             | Network port for ModbusTCP                                                                                                                                                      |
| Input Const | `tConnectTimeout`          | `TIME`           | TIME#5s0ms      | <p>Timeout time for establishing the connection. When the time<br>has elapsed, a repeating reconnect occurs after the time<br>has elapsed <code>tWatchdogDisconnect</code>.</p> |
| Input Const | `tReplyTimeout`            | `TIME`           | TIME#1s0ms      | <p>Reply timeout for Modbus requests; this applies to all<br>connected slaves.1</p>                                                                                             |
| Input Const | `tWatchdogDisconnect`      | `TIME`           | TIME#25s0ms     | <p>Watchdog that monitors an active connection and performs a<br>reconnect after the time has elapsed.</p>                                                                      |
| Output      | `xConnected`               | `BOOL`           |                 | `TRUE` = connection to Modbus TCP participant established                                                                                                                       |
| Output      | `itfModbusConnector`       | IModbusConnector | THIS^           |                                                                                                                                                                                 |
| Output      | `udiConnectedSlaves`       | `UDINT`          |                 | Number of connected Modbus participants                                                                                                                                         |
| Output      | `udiLastModbusRequestTime` | `UDINT`          |                 | Modbus request transaction time in milliseconds                                                                                                                                 |
| Output      | `udiNumberOfMsgSent`       | `UDINT`          |                 | Number of sent Modbus requests                                                                                                                                                  |
| Output      | `udiNumberOfMsgReply`      | `UDINT`          |                 | Number of received Modbus requests                                                                                                                                              |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.powerio.com/hub/codesys-hvac/en/hvac-modbusio2-lib/funktionsbausteine/modbusmastertcp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.