Modbus TCP Client Task

From Control Solutions IoTServer Documentation
Revision as of 17:14, 3 May 2019 by Jimhogenson (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Task manager config modbus tcp client.jpg

The maximum table sizes for the Modbus TCP Client are defined here. Keeping the tables set to a range that you will actually use will improve efficiency.

The default XML configuration file is entered here. This is the file that the Modbus TCP Client will attempt to automatically load upon first time startup. After that, settings are retained in the database, and further file activity can be managed on the Config File page for the Modbus TCP Client.

Activity timeout is a form of watchdog. If the task manager does not see the Modbus TCP Client task update its activity indicator within this amount of time, the task manager will restart the Modbus TCP Client. If set to zero, the watchdog is disabled. The task manager itself is restarted by the Linux cron if it stops responding.