Template:Networking rut manual modbus: Difference between revisions

From Teltonika Networks Wiki
No edit summary
No edit summary
Line 43: Line 43:
</ul>
</ul>


==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. To add a new slave, enter a custom name, slave's ID, IP address and port and click the "Add" button:
[[File:{{{file_add_new_slave}}}]]
===Slave device configuration===
----
The figure below is an example of the <b>Slave device configuration</b> and the table below provides information on the fields contained in that section:
[[File:{{{file_slave_configuration}}}]]
<table class="nd-mantable">
    <tr>
        <th>Field name</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Enabled</td>
        <td>yes | no; Default: <b>no</b></td>
        <td>Turns communication with the slave device ON or OFF</th>
    </tr>
    <tr>
        <td>Name</td>
        <td>string; Default: <b>none</b></td>
        <td>Slave device custom name, used for easier management purposes</th>
    </tr>
    <tr>
        <td>Slave ID</td>
        <td>integer [1..247]; Default: <b>none</b></td>
        <td>Slave ID. Each slave in a network is assigned a unique identifier randging from 1 to 247. When the master requests data from a slave, the first byte it sends is the Slave ID</th>
    </tr>
    <tr>
        <td>IP address</td>
        <td>ip; Default: <b>none</b></td>
        <td>Slave device IP address</th>
    </tr>
    <tr>
        <td>Port</td>
        <td>integer [0..65535]; Default: <b>none</b></td>
        <td>Slave device Modbus TCP port</th>
    </tr>
    <tr>
        <td>Period</td>
        <td>integer [1..6400]; Default: <b>none</b></td>
        <td>Interval at which requests are sent to the slave device</th>
    </tr>
    <tr>
        <td>Timeout</td>
        <td>integer [1..30]; Default: <b>nome</b></td>
        <td>Maximum response wait time</th>
    </tr>
</table>
==Modbus Data to Server==
[[File:{{{file_add_new_sender}}}]]
[[File:{{{file_sender_configuration}}}]]


==See also==
==See also==

Revision as of 06:48, 2 April 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]]