Changes

no edit summary
Line 199: Line 199:  
</table>
 
</table>
   −
<b>Additional note:</b>By default the newly added Request Configurations are turned off. You can use the on/off slider to the right of the Request Configuration to turn it on:
+
<b>Additional note:</b> by default the newly added Request Configurations are turned off. You can use the on/off slider to the right of the Request Configuration to turn it on:
    
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_on_off_slider.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_on_off_slider.png|border|class=tlt-border]]
Line 497: Line 497:  
</table>
 
</table>
   −
<b>Additional note:</b>By default the newly added Request Configurations are turned off. You can use the on/off slider to the right of the Request Configuration to turn it on:
+
<b>Additional note:</b> by default the newly added Request Configurations are turned off. You can use the on/off slider to the right of the Request Configuration to turn it on:
    
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_on_off_slider.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_on_off_slider.png|border|class=tlt-border]]
Line 505: Line 505:  
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_testing.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_testing.png|border|class=tlt-border]]
   −
====Alarms Configuration====
+
====Modbus Master Alarms====
 
----
 
----
<b>Alarms</b> are a way of setting up automated actions when some Modbus values meet user-defined conditions. When the Modbus TCP Master (this {{{name}}} device) requests some information from a slave device it compares that data to with the parameters set in an Alarm Configuration. If the comparison meets the specified condition (more than, less than, equal to, not equal to), the Master performs a user-specified action, for example, a Modbus write request or switching the state of an output.
+
<b>Alarms</b> are a way of setting up automated actions when some Modbus values meet user-defined conditions. When the Modbus Serial Master (this {{{name}}} device) requests some information from a slave device it compares that data to with the parameters set in an Alarm Configuration. If the comparison meets the specified condition (more than, less than, equal to, not equal to), the Master performs a user-specified action, for example, a Modbus write request or switching the state of an output.
 +
 
 +
The figure below is an example of the Modbus Master Alarms list. To create a new Alarm, click the 'Add' button.
 +
 
 +
[[File:Networking_rutos_manual_modbus_modbus_serial_master_modbus_master_alarms_add_button.png|border|class=tlt-border]]
   −
The figure below is an example of the Alarms Configuration list. To create a new Alarm, click the 'Add' button.
+
Then click the 'Edit' button next to the newly created Alarm to configuration.
   −
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_alarms_configuration_add_button.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_modbus_modbus_serial_master_modbus_master_alarms_edit_button.png|border|class=tlt-border]]
   −
After adding the Alarm you should be redirected to its configuration page which should look similar to this:
+
After this you should be redirected to that Alarm's configuration page which should look similar to this:
   −
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_alarms_configuration.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_modbus_modbus_serial_master_modbus_master_alarms_alarm_configuration.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 531: Line 535:  
         <td>Function code</td>
 
         <td>Function code</td>
 
         <td>Read Coil Status (1) <nowiki>|</nowiki> Read Input Status (2) <nowiki>|</nowiki> Read Holding Registers (3) <nowiki>|</nowiki> Read Input Registers (4); default: <b>Read Coil Status (1)</b></td>
 
         <td>Read Coil Status (1) <nowiki>|</nowiki> Read Input Status (2) <nowiki>|</nowiki> Read Holding Registers (3) <nowiki>|</nowiki> Read Input Registers (4); default: <b>Read Coil Status (1)</b></td>
         <td>Modbus function used for this alarm's Modbus request. The Modbus TCP Master (this {{{name}}} device) perform this request as often as specified in the 'Period' field in [[#RS232_Slave_Device_Configuration|RS232 Slave Device Configuration]].</td>
+
         <td>Modbus function used for this alarm's Modbus request. The Modbus TCP Master (this {{{name}}} device) perform this request as often as specified in the 'Period' field in [[#RS485_Slave_Device_Configuration|RS485 Slave Device Configuration]].</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 587: Line 591:  
         <td>phone number; default: <b>none</b></td>
 
         <td>phone number; default: <b>none</b></td>
 
         <td>Recipient's phone number.</td>
 
         <td>Recipient's phone number.</td>
    </tr>
  −
    <tr>
  −
        <td><span style="color: purple;">MODBUS Write Request: IP address</span></td>
  −
        <td>ip <nowiki>|</nowiki> host; default: <b>none</b></td>
  −
        <td>Modbus slave's IP address.</td>
  −
    </tr>
  −
    <tr>
  −
        <td><span style="color: purple;">MODBUS Write Request: Port</span></td>
  −
        <td>integer [0..65535]; default: <b>none</b></td>
  −
        <td>Modbus slave's port.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 625: Line 619:  
</table>
 
</table>
 
|}}|}}{{#ifeq: {{{rs485}}} | 1 |
 
|}}|}}{{#ifeq: {{{rs485}}} | 1 |
<h3>RS485</h3>
+
===RS485===
 
----
 
----
 
This section is used to configure the Modbus Serial Master's <b>RS485</b> serial interface settings. Refer to the figure and table below for information on RS485 configuration.
 
This section is used to configure the Modbus Serial Master's <b>RS485</b> serial interface settings. Refer to the figure and table below for information on RS485 configuration.
Line 791: Line 785:  
</table>
 
</table>
   −
<b>Additional note:</b>By default the newly added Request Configurations are turned off. You can use the on/off slider to the right of the Request Configuration to turn it on:
+
<b>Additional note:</b> by default the newly added Request Configurations are turned off. You can use the on/off slider to the right of the Request Configuration to turn it on:
    
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_on_off_slider.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_on_off_slider.png|border|class=tlt-border]]
Line 799: Line 793:  
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_testing.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_requests_configuration_testing.png|border|class=tlt-border]]
   −
====Alarms Configuration====
+
====Modbus Master Alarms====
 
----
 
----
<b>Alarms</b> are a way of setting up automated actions when some Modbus values meet user-defined conditions. When the Modbus TCP Master (this {{{name}}} device) requests some information from a slave device it compares that data to with the parameters set in an Alarm Configuration. If the comparison meets the specified condition (more than, less than, equal to, not equal to), the Master performs a user-specified action, for example, a Modbus write request or switching the state of an output.
+
<b>Alarms</b> are a way of setting up automated actions when some Modbus values meet user-defined conditions. When the Modbus Serial Master (this {{{name}}} device) requests some information from a slave device it compares that data to with the parameters set in an Alarm Configuration. If the comparison meets the specified condition (more than, less than, equal to, not equal to), the Master performs a user-specified action, for example, a Modbus write request or switching the state of an output.
 +
 
 +
The figure below is an example of the Modbus Master Alarms list. To create a new Alarm, click the 'Add' button.
 +
 
 +
[[File:Networking_rutos_manual_modbus_modbus_serial_master_modbus_master_alarms_add_button.png|border|class=tlt-border]]
   −
The figure below is an example of the Alarms Configuration list. To create a new Alarm, click the 'Add' button.
+
Then click the 'Edit' button next to the newly created Alarm to configuration.
   −
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_alarms_configuration_add_button.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_modbus_modbus_serial_master_modbus_master_alarms_edit_button.png|border|class=tlt-border]]
   −
After adding the Alarm you should be redirected to its configuration page which should look similar to this:
+
After this you should be redirected to that Alarm's configuration page which should look similar to this:
   −
[[File:Networking_rutos_manual_modbus_modbus_tcp_master_alarms_configuration.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_modbus_modbus_serial_master_modbus_master_alarms_alarm_configuration.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 881: Line 879:  
         <td>phone number; default: <b>none</b></td>
 
         <td>phone number; default: <b>none</b></td>
 
         <td>Recipient's phone number.</td>
 
         <td>Recipient's phone number.</td>
    </tr>
  −
    <tr>
  −
        <td><span style="color: purple;">MODBUS Write Request: IP address</span></td>
  −
        <td>ip <nowiki>|</nowiki> host; default: <b>none</b></td>
  −
        <td>Modbus slave's IP address.</td>
  −
    </tr>
  −
    <tr>
  −
        <td><span style="color: purple;">MODBUS Write Request: Port</span></td>
  −
        <td>integer [0..65535]; default: <b>none</b></td>
  −
        <td>Modbus slave's port.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>

Navigation menu