Changes

no edit summary
Line 1: Line 1:  +
{{Template: Networking_rutxxx_manual_fw_disclosure
 +
| fw_version = {{{series}}}_R_00.06.07
 +
}}
 
==Summary==
 
==Summary==
    
<b>Inputs and Outputs</b> are used for the monitoring and controlling of a connected device or receiving signals from that device in order to trigger certain events. This chapter is overview on the Input/Output section for {{{name}}} routers.
 
<b>Inputs and Outputs</b> are used for the monitoring and controlling of a connected device or receiving signals from that device in order to trigger certain events. This chapter is overview on the Input/Output section for {{{name}}} routers.
  −
{{Template: Networking_rutxxx_manual_fw_disclosure
  −
| fw_version = {{{fw_version}}}
  −
}}
      
==Characteristics==
 
==Characteristics==
   −
{{Template:Networking_rut2xx_manual_input_output_characteristics|name={{{name}}}}}
+
{{Template:Networking_rut9xx_manual_input_output_characteristics|name={{{name}}}}}
    
==Status==
 
==Status==
Line 15: Line 14:  
The <b>Status</b> tab displays the current states the router’s input and output:
 
The <b>Status</b> tab displays the current states the router’s input and output:
   −
[[File:{{{file_status}}}]]
+
[[File:{{{file_status}}}|border|class=tlt-border]]
    
===Custom Labels===
 
===Custom Labels===
Line 21: Line 20:  
If the default Input/Output labels do not suit your needs, you can always configure custom ones in the <b>Custom Labels</b> section. Click the 'Edit' button next to the desired Input or Output and you will be redirected to a window such as this:
 
If the default Input/Output labels do not suit your needs, you can always configure custom ones in the <b>Custom Labels</b> section. Click the 'Edit' button next to the desired Input or Output and you will be redirected to a window such as this:
   −
[[File:{{{file_status_digital}}}]]
+
[[File:{{{file_status_digital}}}|border|class=tlt-border]]
   −
The figure above is an example of custom label configuration for <i>Digital Input</i>. You can change an input's/output's name and the names of their states. The changes are purely cosmetic and used for easier management purposes.
+
The figure above is an example of custom label configuration for <i>Digital Input</i>. You can change an input's/output's name, the names of their states and which state is considered as "Active". The changes are purely cosmetic and used for easier management purposes.
    
===Status and control from command line===
 
===Status and control from command line===
 
----
 
----
{{Template: Networking_rut2xx_manual_input_output_cli}}
+
{{Template: Networking_rut9xx_manual_input_output_cli|name={{{name}}}}}
    
==Input==
 
==Input==
Line 37: Line 36:  
The <b>Input Rules</b> section provides you with the possibility to set up rules that execute user specified actions after a certain trigger occurs. To add a new rule, look to the Input Configuration section that is just below. Select the input, the trigger and the action for the rule and click the 'Add' button. A new rule will appear in the Input Rules list:  
 
The <b>Input Rules</b> section provides you with the possibility to set up rules that execute user specified actions after a certain trigger occurs. To add a new rule, look to the Input Configuration section that is just below. Select the input, the trigger and the action for the rule and click the 'Add' button. A new rule will appear in the Input Rules list:  
   −
[[File:{{{file_input_add}}}]]
+
[[File:{{{file_input_add}}}|border|class=tlt-border]]
 
----
 
----
 
To begin editing an input rule, click the 'Edit' button located next to it. Refer to the figure and table below for information on input rule configuration.
 
To begin editing an input rule, click the 'Edit' button located next to it. Refer to the figure and table below for information on input rule configuration.
   −
[[File:{{{file_input_config}}}]]
+
[[File:{{{file_input_config}}}|border|class=tlt-border]]
   −
{{Template:Networking_rut2xx_manual_input_output_input_rule_table|name={{{name}}}}}
+
{{Template:Networking_rut9xx_manual_input_output_input_rule_table|name={{{name}}}}}
    
==Output==
 
==Output==
Line 62: Line 61:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
       <td>Open collector output</td>
+
       <td>Digital output 4PIN</td>
 
       <td>Low level | High level; default: <b>Low level</b></td>
 
       <td>Low level | High level; default: <b>Low level</b></td>
       <td>Changes the default<span class="asterisk">*</span> state of the open collector (OC) output pin.</td>
+
       <td>Changes the default<span class="asterisk">*</span> state of the digital output pin.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 74: Line 73:  
The <b>ON/OFF</b> section is used to turn the router's output on or off. This action does not save the state permanently, meaning that after a reboot the state will revert back to their default values.
 
The <b>ON/OFF</b> section is used to turn the router's output on or off. This action does not save the state permanently, meaning that after a reboot the state will revert back to their default values.
   −
[[File:{{{file_output_on_off}}}]]
+
[[File:{{{file_output_on_off}}}|border|class=tlt-border]]
    
===Post/Get configuration===
 
===Post/Get configuration===
Line 80: Line 79:  
Enabling <b>Post/Get</b> will allow you to send HTTP POST/GET requests to the router that control the state of the output. The figure below is an example of the Post/Get configuration section an the table below provides information on the fields contained in that section:
 
Enabling <b>Post/Get</b> will allow you to send HTTP POST/GET requests to the router that control the state of the output. The figure below is an example of the Post/Get configuration section an the table below provides information on the fields contained in that section:
   −
[[File:{{{file_output_post_get}}}]]
+
[[File:{{{file_output_post_get}}}|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 95: Line 94:  
     <tr>
 
     <tr>
 
       <td>Username</td>
 
       <td>Username</td>
       <td>string; default: <b>none</b></td>
+
       <td>string; default: <b>user1</b></td>
 
       <td>Username used for authentication in POST/GET queries.</td>
 
       <td>Username used for authentication in POST/GET queries.</td>
 
     </tr>
 
     </tr>
Line 111: Line 110:  
Below is a table containing syntax examples of this usage:  
 
Below is a table containing syntax examples of this usage:  
   −
{{Template:Networking_rut2xx_manual_input_output_post_get_examples_table|name={{{name}}}}}
+
{{Template:Networking_rut9xx_manual_input_output_post_get_examples_table|name={{{name}}}}}
    
<b>Overview</b>:
 
<b>Overview</b>:
Line 119: Line 118:  
     <li>password- password from Post/Get configuration.</li>
 
     <li>password- password from Post/Get configuration.</li>
 
     <li>action- the action that will be performed on the output (can be <i>on</i> or <i>off</i>).</li>
 
     <li>action- the action that will be performed on the output (can be <i>on</i> or <i>off</i>).</li>
     <li>pin - specifies the output (use <i>oc</i>).</li>
+
     <li>pin - specifies the output (use <i>4pin</i>).</li>
 
     <li>delay - defines a delay (in seconds) after which the specified action will be performed.</li>
 
     <li>delay - defines a delay (in seconds) after which the specified action will be performed.</li>
 
     <li>time - defines a window of time during which the action will take place. For instance, if you post an <i>on</i> action while specifying <i>time=5</i>, the output will turn on and stay on for 5 seconds before turning off.</li>
 
     <li>time - defines a window of time during which the action will take place. For instance, if you post an <i>on</i> action while specifying <i>time=5</i>, the output will turn on and stay on for 5 seconds before turning off.</li>
Line 128: Line 127:  
===Periodic control===
 
===Periodic control===
 
----
 
----
The <b>Periodic control</b> section allows you to set up automatic output control rules that trigger output state changes at the specified period or interval. Refer to the figure and table below for information on configuration fields contained in that section.
+
The <b>Periodic control</b> section allows you to set up automatic output control rules that trigger output state changes at the specified period or interval.
 +
 
 +
Click the 'Add' button to add a new periodic control rule and click the 'Edit' button next to it to begin configuration:
 +
 
 +
[[File:{{{file_output_periodic_add}}}|border|class=tlt-border]]
 +
 
 +
Refer to the figure and table below for information on configuration fields contained in that section.
   −
[[File:{{{file_output_periodic}}}]]
+
[[File:{{{file_output_periodic}}}|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 145: Line 150:  
     <tr>
 
     <tr>
 
       <td>Output</td>
 
       <td>Output</td>
       <td>Digital OC Output | Digital 4PIN | Digital relay output; default: <b>Digital OC Output</b> </td>
+
       <td>Digital 4PIN output; default: <b>Digital 4PIN output</b> </td>
 
       <td>The output pin that will be be affected by the rule.</td>
 
       <td>The output pin that will be be affected by the rule.</td>
 
     </tr>
 
     </tr>
Line 176: Line 181:  
[[File:{{{file_output_scheduler}}}|border|class=tlt-border]]
 
[[File:{{{file_output_scheduler}}}|border|class=tlt-border]]
   −
[[Category:{{{name}}} WebUI]]
+
[[Category:{{{name}}} Services section]]

Navigation menu