31,703
edits
Changes
Template:Networking rutos manual modbus (view source)
Revision as of 12:07, 25 August 2020
, 12:07, 25 August 2020no edit summary
{{Template:Networking_rutos_manual_fw_disclosure
{{Template:Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.04.1
| fw_version = {{{series}}}_R_00.02.05
| series = {{{series}}}
| series = {{{series}}}
}}
}}
The figure below is an example of the Modbus TCP window section and the table below provides information on the fields contained in that window:
The figure below is an example of the Modbus TCP window section and the table below provides information on the fields contained in that window:
[[File:Networking_rutos_manual_modbus_modbus_tcp_slave_v2.png]]
[[File:Networking_rutos_manual_modbus_modbus_tcp_slave.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Enable</td>
<td>Enable</td>
<td>yes | no; default: <b>none</b></td>
<td>off | on; default: <b>none</b></td>
<td>Turns Modbus TCP on or off.</td>
<td>Turns Modbus TCP on or off.</td>
</tr>
</tr>
<tr>
<tr>
<td>Port</td>
<td>Port</td>
<td>integer [0..65535]; default: '''502'''</td>
<td>integer [0..65535]; default: <b>502</b></td>
<td>TCP port used for Modbus communications.</td>
<td>TCP port used for Modbus communications.</td>
</tr>
</tr>
<tr>
<tr>
<td>Allow Remote Access</td>
<td>Allow Remote Access</td>
<td>yes | no; default: <b>no</b></td>
<td>off | on; default: <b>off</b></td>
<td>Allows remote Modbus connections by adding an exception to the device's firewall on the port specified in the field above.</td>
<td>Allows remote Modbus connections by adding an exception to the device's firewall on the port specified in the field above.</td>
</tr>
</tr>
<tr>
<tr>
<td>Keep persistent connection</td>
<td>Keep persistent connection</td>
<td>yes | no; default: <b>no</b></td>
<td>off | on; default: <b>off</b></td>
<td>Allows keep the connection open after responding a Modbus TCP master request.</td>
<td>Allows keep the connection open after responding a Modbus TCP master request.</td>
</tr>
</tr>
<tr>
<tr>
<td>Enable custom register block</td>
<td>Enable custom register block</td>
<td>yes | no; default: <b>no</b></td>
<td>off | on; default: <b>off</b></td>
<td>Allow custom register block.</td>
<td>Allows the usage of custom register block.</td>
</tr>
</tr>
</table>
</table>
==Modbus TCP Master==
==Modbus TCP Master==
A Modbus <b>master</b> device can request data from Modbus slaves. The Modbus TCP Master section is used to configure Modbus TCP slaves.
A <b>Modbus Master</b> device can request data from Modbus slaves. The Modbus TCP Master section is used to configure Modbus TCP slaves. By default, the slave list is empty. To add a new slave, click the 'Add' button
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_modbus_tcp_slave_devices_add_button.png|border|class=tlt-border]]
After clicking 'Add' you will be redirected to the newly added slave's configuration page.
You can create a maximum of 10 slave configurations.
You can create a maximum of 10 slave configurations.
<tr>
<tr>
<th>Enabled</th>
<th>Enabled</th>
<th>off | on; Default: <b>off</b></th>
<th>off | on; default: <b>off</b></th>
<th>Turns the data sender ON or OFF</th>
<th>Turns the data sender ON or OFF</th>
</tr>
</tr>
<tr>
<tr>
<td>Name</td>
<td>Name</td>
<td>string; Default: <b>none</b></td>
<td>string; default: <b>none</b></td>
<td>Data sender's name. used for easier management purposes</td>
<td>Data sender's name. used for easier management purposes</td>
</tr>
</tr>
<tr>
<tr>
<td>Protocol</td>
<td>Protocol</td>
<td>HTTP; Default: <b>HTTP</b></td>
<td>HTTP; default: <b>HTTP</b></td>
<td>Data sending protocol</td>
<td>Data sending protocol</td>
</tr>
</tr>
<tr>
<tr>
<td>JSON format</td>
<td>JSON format</td>
<td>json string; Default: <b>{"ID":"%i", "TS":"%t","ST":"%s","VR":"%a"}</b></td>
<td>json string; default: <b>{"ID":"%i", "TS":"%t","ST":"%s","VR":"%a"}</b></td>
<td>Provides the possibility to fully customize the JSON segment</td>
<td>Provides the possibility to fully customize the JSON segment</td>
</tr>
</tr>
<tr>
<tr>
<td>Segment count</td>
<td>Segment count</td>
<td>1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10; Default: <b>1</b></td>
<td>1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10; default: <b>1</b></td>
<td>Max segment count in one JSON string sent to server</td>
<td>Max segment count in one JSON string sent to server</td>
</tr>
</tr>
<tr>
<tr>
<td>URL</td>
<td>URL</td>
<td>host | ip; Default: <b>none</b></td>
<td>host | ip; default: <b>none</b></td>
<td>Address of the server to which the data will be sent.</td>
<td>Address of the server to which the data will be sent.</td>
</tr>
</tr>
<tr>
<tr>
<td>Period</td>
<td>Period</td>
<td>integer [1..6400]; Default: <b>60</b></td>
<td>integer [1..6400]; default: <b>60</b></td>
<td>Data sending frequency (in seconds)</td>
<td>Data sending frequency (in seconds)</td>
</tr>
</tr>
<tr>
<tr>
<td>Data filtering</td>
<td>Data filtering</td>
<td>All data | By slave ID | By slave IP; Default: <b>All data</b></td>
<td>All data | By slave ID | By slave IP; default: <b>All data</b></td>
<td>Which data this sender will transfer to the server</td>
<td>Which data this sender will transfer to the server</td>
</tr>
</tr>
<tr>
<tr>
<td>Retry on fail</td>
<td>Retry on fail</td>
<td>off | on; Default: <b>no</b></td>
<td>off | on; default: <b>off</b></td>
<td>Specifies whether the data sender should retry failed attempts (Retry until successful)</td>
<td>Specifies whether the data sender should retry failed attempts (Retry until successful)</td>
</tr>
</tr>
<tr>
<tr>
<td>Custom header</td>
<td>Custom header</td>
<td>string; Default: <b>no</b></td>
<td>string; default: <b>off</b></td>
<td>Adds a custom header(s) to HTTP requests</td>
<td>Adds a custom header(s) to HTTP requests</td>
</tr>
</tr>
</table>
</table>
-->
-->
