Difference between revisions of "Template:Networking rut manual modbus"

From Teltonika Networks Wiki
Line 44: Line 44:
 
{{#ifeq: {{{series}}} | RUT2xx
 
{{#ifeq: {{{series}}} | RUT2xx
 
| <!--
 
| <!--
|  
+
| ----
 
}}
 
}}
 
==Modbus TCP Master==
 
==Modbus TCP Master==

Revision as of 16:35, 3 May 2019

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}}}]]

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:

{{Template: Networking_{{{name}}}_manual_modbus_modbus_tcp_get_parameters_table}}

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:

{{Template: Networking_{{{name}}}_manual_modbus_modbus_tcp_set_parameters_table}}

* All ON/OFF commands only accept 0 and 1 values, which represent the following:

  • 1 - ON
  • 0 - OFF

See also

Template:Networking device modbus see also

[[Category:{{{name}}} WebUI]]