9,567
edits
Changes
Template:Networking rut manual modbus legacy (view source)
Revision as of 12:24, 24 October 2023
, 12:24, 24 October 2023Text replacement - "\{\{Template: Networking_rutos_manual_fw_disclosure (.*) (.*) (.*) \}\}" to "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }}"
{{Template: Networking_rutos_manual_fw_disclosure
{{Template: Networking_device_manual_fw_disclosure
| fw_version = {{#switch: {{{series}}}
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| series = {{{series}}}
| name = {{{name}}}
}}
}}
}}
----
----
A Modbus <b>request</b> is a way of obtaining data from Modbus slaves. The master sends a request to a slave specifying the function code to be performed. The slave then sends the requested data back to the Modbus master. You can create a maximum of 64 request configurations for each slave device.
A Modbus <b>request</b> is a way of obtaining data from Modbus slaves. The master sends a request to a slave specifying the function code to be performed. The slave then sends the requested data back to the Modbus master. You can create a maximum of 64 request configurations for each slave device.
<span style="color:red"> <b>Note: </b></span>Modbus TCP Master uses <i>Register Number</i> instead of <i>Register Address</i> for pointing to a register. For example, to request the <i>Uptime</i> of a device, you must use <b>2</b> in the <i>First Register</i> field.
The figure below is an example of the Requests configuration section and the table below provides information contained in the fields of that section:
The figure below is an example of the Requests configuration section and the table below provides information contained in the fields of that section:
----
----
A Modbus <b>request</b> is a way of obtaining data from Modbus slaves. The master sends a request to a slave specifying the function code to be performed. The slave then sends the requested data back to the Modbus master.
A Modbus <b>request</b> is a way of obtaining data from Modbus slaves. The master sends a request to a slave specifying the function code to be performed. The slave then sends the requested data back to the Modbus master.
<span style="color:red"> <b>Note: </b></span>Modbus Serial Master uses <i>Register Number</i> instead of <i>Register Address</i> for pointing to a register. For example, to request the <i>Uptime</i> of a device, you must use <b>2</b> in the <i>First Register</i> field.
The figure below is an example of the Requests configuration section and the table below provides information contained in the fields of that section:
The figure below is an example of the Requests configuration section and the table below provides information contained in the fields of that section:
Below is an example of the MQTT Gateway page. Refer to the table for information on MQTT Gateway configuration fields.
Below is an example of the MQTT Gateway page. Refer to the table for information on MQTT Gateway configuration fields.
[[File:Networking_rut_manual_modbus_mqtt_gateway.png|border|class=tlt-border]]
{{#ifeq: {{{series}}} | RUT9XX |
[[File:Networking_rut_manual_modbus_mqtt_gateway.png|border|class=tlt-border]]|
[[File:Networking_rut_manual_modbus_mqtt_gateway_v2.png|border|class=tlt-border]]}}
<table class="nd-mantable">
<table class="nd-mantable">
<td>string; default: <b>none</b></td>
<td>string; default: <b>none</b></td>
<td>Password for authentication to the MQTT broker. Leave empty if you do not use client authentication.</td>
<td>Password for authentication to the MQTT broker. Leave empty if you do not use client authentication.</td>
</tr>
</tr>{{#ifeq:{{{series}}}|RUT2XX|
<tr>
<td>Keep alive</td>
<td>integer [0..86400]; default: <b>10</b></td>
<td>Specifies the number of seconds after which the broker should send a PING message to the client if no other messages have been exchanged in that time.</td>
</tr>|}}
</table>
</table>
===Request messages===
===Request messages===
----
----
<span style="color:red"> <b>Note: </b></span>MQTT Gateway uses <i>Register Number</i> instead of <i>Register Address</i> for pointing to a register. For example, to request the <i>Uptime</i> of a device, you must use <b>2</b> in the <i>Register Number</i> field.
Modbus request data sent in the MQTT payload should be generated in accordance with the following format:
Modbus request data sent in the MQTT payload should be generated in accordance with the following format:
