Changes

You can create a maximum of 10 slave configurations.

You can create a maximum of 10 slave configurations.

===Slave device configuration===

===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:

The <b>Slave Device Configuration</b> section is used to configure the parameters or Modbus TCP slaves that the Master (this {{{name}}} device) will querying with requests. The figure below is an example of the Slave Device Configuration and the table below provides information on the fields contained in that section:

[[File:Networking_rutos_manual_modbus_modbus_tcp_master_slave_configuration_v1.png|border|class=tlt-border]]

[[File:Networking_rutos_manual_modbus_modbus_tcp_master_slave_device_configuration.png|border|class=tlt-border]]

<table class="nd-mantable">

<table class="nd-mantable">

</table>

</table>

===Requests configuration===

===Requests Configuration===

----

----

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.

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 Request Configuration list is empty by default. To add a new Request Configuration loon to the Add New Instance section. Enter a custom name into the 'Name' field and click the 'Add' button:

[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_v1.png|border|class=tlt-border]]

[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_add_new_instance.png|border|class=tlt-border]]

 

 

[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration.png|border|class=tlt-border]]

<table class="nd-mantable">

<table class="nd-mantable">

         <td>Name</td>

         <td>Name</td>

         <td>string; default: <b>Unnamed</b></td>

         <td>string; default: <b>Unnamed</b></td>

         <td>Request name. Used for easier management purposes.</td>

         <td>Name of this Request Configuration. Used for easier management purposes.</td>

     </tr>

     </tr>

     <tr>

     <tr>

         <td>Data type</td>

         <td>Data type</td>

         <td>8bit INT | 8bit UINT | 16bit INT, high byte first | 16bit INT, low byte first | 16bit UINT, high byte first | 16bit UINT, low byte first | 32bit float, Byte order 1,2,3,4 | 32bit float, Byte order 4,3,2,1 | 32bit float, Byte order 2,1,4,3 | 32bit float, Byte order 3,4,1,2; default: <b>16bit INT, high byte first</b></td>

         <td>8bit INT | 8bit UINT | 16bit INT, high byte first | 16bit INT, low byte first | 16bit UINT, high byte first | 16bit UINT, low byte first | 32bit float, Byte order 1,2,3,4 | 32bit float, Byte order 4,3,2,1 | 32bit float, Byte order 2,1,4,3 | 32bit float, Byte order 3,4,1,2; default: <b>16bit INT, high byte first</b></td>

         <td>How read data will be stored.</td>

         <td>Defines how read data will be stored.</td>

     </tr>

     </tr>

     <tr>

     <tr>

</table>

</table>

After having configured a request, you should see a new 'Testing' section appear. It is used to check whether the configuration works correctly. Simply press the 'Test' button and a response should appear in the box below.

 

After having configured a request, you should see a new 'Request Configuration Testing' section appear. It is used to check whether the configuration works correctly. Simply click the 'Test' button and a response should appear in the box below. A successful response to a test may look something like this:

[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_testing_v1.png|border|class=tlt-border]]

[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_testing.png|border|class=tlt-border]]

===Alarms Configuration===

===Alarms Configuration===