31,703
edits
Changes
Template:Networking rut manual modbus (view source)
Revision as of 12:26, 4 December 2018
, 12:26, 4 December 2018Created page with "==Summary== '''Modbus''' is a serial communications protocol. Simple and robust, it has since become a de facto standard communication protocol and is now a commonly availabl..."
==Summary==
'''Modbus''' is a serial communications protocol. Simple and robust, it has since become a de facto standard communication protocol and is now a commonly available means of connecting industrial electronic devices. This chapter is an overview of the Modbus TCP functionality.
==Modbus TCP==
'''Modbus TCP''' provides users with the possibility to set or get system parameters. The Modbus daemon acts as slave device. That means it accepts connections from a master (client) and sends out a response or sets some system related parameter in accordance with the given query.
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:{{{modbus_tcp_file}}}]]
{{#ifeq: {{lc:{{{series}}}}} | rut2xx
| {{Template: Networking_rut2xx_manual_modbus_modbus_tcp_table}}
| {{Template: Networking_rut9xx_manual_modbus_modbus_tcp_table}}
}}
===Get Parameters===
----
Modbus parameters are held within '''registers'''. Each register contains 2 bytes of information. For simplification, the number of registers for storing numbers is 2 (4 bytes), while the number of registers for storing text information is 16 (32 bytes). The register numbers and corresponding system values are described in the table below:
{{#ifeq: {{lc:{{{series}}}}} | rut2xx
| {{Template: Networking_{lc:{{{series}}}}}_manual_modbus_modbus_tcp_get_parameters_table}}
| {{Template: Networking_{{lc:{{{name}}}}}_manual_modbus_modbus_tcp_get_parameters_table}}
}}
<span class="asterisk">*</span> All received/sent data usage values are returned in '''kibibytes''' ('''KiB'''), which is an ISQ standard accepted by most major standard organizations. <br> 1 kibibyte (KiB) = 2<sup>10</sup> bytes = 1024 bytes <br> 1 mebibyte (MiB) = 2<sup>10</sup> kibibytes (KiB) = 2<sup>20</sup> bytes = 1 048 576 bytes
===Set Parameters===
----
The Modbus daemon can also set some device parameters. These parameters and explanations on how to use them are described in the table below:
{{#ifeq: {{lc:{{{series}}}}} | rut2xx
| {{Template: Networking_{lc:{{{series}}}}}_manual_modbus_modbus_tcp_set_parameters_table}}
| {{Template: Networking_{{lc:{{{name}}}}}_manual_modbus_modbus_tcp_set_parameters_table}}
}}
<span class="asterisk">*</span> All ON/OFF commands only accept '''0''' and '''1''' values, which represent the following:
<ul>
<li>1 - ON</li>
<li>0 - OFF</li>
</ul>
==See also==
{{Template: Networking_device_modbus_see_also}}
'''Modbus''' is a serial communications protocol. Simple and robust, it has since become a de facto standard communication protocol and is now a commonly available means of connecting industrial electronic devices. This chapter is an overview of the Modbus TCP functionality.
==Modbus TCP==
'''Modbus TCP''' provides users with the possibility to set or get system parameters. The Modbus daemon acts as slave device. That means it accepts connections from a master (client) and sends out a response or sets some system related parameter in accordance with the given query.
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:{{{modbus_tcp_file}}}]]
{{#ifeq: {{lc:{{{series}}}}} | rut2xx
| {{Template: Networking_rut2xx_manual_modbus_modbus_tcp_table}}
| {{Template: Networking_rut9xx_manual_modbus_modbus_tcp_table}}
}}
===Get Parameters===
----
Modbus parameters are held within '''registers'''. Each register contains 2 bytes of information. For simplification, the number of registers for storing numbers is 2 (4 bytes), while the number of registers for storing text information is 16 (32 bytes). The register numbers and corresponding system values are described in the table below:
{{#ifeq: {{lc:{{{series}}}}} | rut2xx
| {{Template: Networking_{lc:{{{series}}}}}_manual_modbus_modbus_tcp_get_parameters_table}}
| {{Template: Networking_{{lc:{{{name}}}}}_manual_modbus_modbus_tcp_get_parameters_table}}
}}
<span class="asterisk">*</span> All received/sent data usage values are returned in '''kibibytes''' ('''KiB'''), which is an ISQ standard accepted by most major standard organizations. <br> 1 kibibyte (KiB) = 2<sup>10</sup> bytes = 1024 bytes <br> 1 mebibyte (MiB) = 2<sup>10</sup> kibibytes (KiB) = 2<sup>20</sup> bytes = 1 048 576 bytes
===Set Parameters===
----
The Modbus daemon can also set some device parameters. These parameters and explanations on how to use them are described in the table below:
{{#ifeq: {{lc:{{{series}}}}} | rut2xx
| {{Template: Networking_{lc:{{{series}}}}}_manual_modbus_modbus_tcp_set_parameters_table}}
| {{Template: Networking_{{lc:{{{name}}}}}_manual_modbus_modbus_tcp_set_parameters_table}}
}}
<span class="asterisk">*</span> All ON/OFF commands only accept '''0''' and '''1''' values, which represent the following:
<ul>
<li>1 - ON</li>
<li>0 - OFF</li>
</ul>
==See also==
{{Template: Networking_device_modbus_see_also}}
