Changes

m
Text replacement - "\{\{Template: Networking_rutos_manual_fw_disclosure (.*) (.*) (.*) (.*) \}\}" to "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }}"
Line 1: Line 1: −
{{Template: Networking_rutos_manual_fw_disclosure
+
{{Template: Networking_device_manual_fw_disclosure
| fw_version = {{#switch: {{{series}}}
+
| series = {{{series}}}
   | RUT2XX = {{{series}}}_R_00.01.13
+
| name   = {{{name}}}
  | RUT9XX = {{{series}}}_R_00.06.07}}
+
| fw_version ={{Template: Networking_device_manual_latest_fw
| series    = {{{series}}}
+
| series = {{{series}}}
 +
| name  = {{{name}}}
 +
}}
 
}}
 
}}
 
==Summary==
 
==Summary==
Line 219: Line 221:  
<b>Alarms</b> are a way of setting up automated actions when some Modbus values meet user specified conditions. The figure below is an example of the Alarm configuration page and the table below provides information on fields that it contains:
 
<b>Alarms</b> are a way of setting up automated actions when some Modbus values meet user specified conditions. The figure below is an example of the Alarm configuration page and the table below provides information on fields that it contains:
   −
[[File:Networking_rut_manual_modbus_modbus_tcp_master_alarm_configuration.png|border|class=tlt-border]]
+
{{#ifeq:{{{series}}}|RUT2XX|[[File:Networking_rut2xx_manual_modbus_modbus_tcp_master_alarm_configuration.png|border|class=tlt-border]]
 +
|[[File:Networking_rut_manual_modbus_modbus_tcp_master_alarm_configuration.png|border|class=tlt-border]]
 +
}}
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 274: Line 278:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td><span style="color: red;">Trigger output:</span> Output</td>
+
         <td><span style="color: red;">Trigger output:</span> Output</td>{{#ifeq:{{{name}}}|RUT955|
         <td>Open collector output | Relay output | Both; default: <b>Open collector output</b></td>
+
         <td>Open collector output {{!}} Relay output {{!}} Both; default: <b>Open collector output</b></td>|
 +
        <td>4PIN output; default: <b>4PIN output</b></td>}}
 
         <td>Which output(s) will be triggered.</td>
 
         <td>Which output(s) will be triggered.</td>
 
     </tr>
 
     </tr>
Line 330: Line 335:  
This section is used to configure the Modbus RTU master's RS232 serial interface settings. Refer to the figure and table below for information on RS232 configuration.
 
This section is used to configure the Modbus RTU master's RS232 serial interface settings. Refer to the figure and table below for information on RS232 configuration.
   −
[[File:Networking_rut_manual_modbus_modbus_serial_master_rs232.png|borer|class=tlt-border]]
+
[[File:Networking_rut_manual_modbus_modbus_serial_master_rs232.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 465: Line 470:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td>Period</td>
+
        <td>Frequency settings period</td>
         <td>integer [1..9999]; default: <b>10</b></td>
+
        <td>Period {{!}} Schedule; default: <b>Period</b></td>
         <td>Interval (in minutes) at which requests are sent to the slave device.</td>
+
        <td>Specifies whether request frequency should happen every x amount of seconds (<i>Period</i>) or on a set schedule (<i>Schedule</i>).</td>
 +
    </tr>
 +
    <tr>
 +
         <td>Period/Schedule</td>
 +
         <td>integer [1..9999]/; default: <b>10</b></td>
 +
         <td>Interval (in minutes) at which requests are sent to the slave device. Or Shedule (crontab-like, three fields (HH MM SS); e.g.. <i>0,12 * *</i>).</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>

Navigation menu