Changes

no edit summary
Line 21: Line 21:  
{{#ifeq:{{{name}}}|RUT955
 
{{#ifeq:{{{name}}}|RUT955
 
|[[File:{{{file_status}}}|border|class=tlt-border]]
 
|[[File:{{{file_status}}}|border|class=tlt-border]]
|[[File:{{{file_status}}}]]}}
+
|[[File:{{{file_status}}}|border|class=tlt-border]]}}
    
===Custom Labels===
 
===Custom Labels===
Line 27: Line 27:  
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 and the names of their states. The changes are purely cosmetic and used for easier management purposes.
Line 99: Line 99:     
[[File:{{{file_output_on_off}}}]]
 
[[File:{{{file_output_on_off}}}]]
  −
===Post/Get configuration===
  −
----
  −
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 and the table below provides information on the fields contained in that section:
  −
  −
[[File:{{{file_output_post_get}}}]]
  −
  −
<table class="nd-mantable">
  −
    <tr>
  −
        <th>Field</th>
  −
      <th>Value</th>
  −
      <th>Description</th>
  −
    </tr>
  −
    <tr>
  −
      <td>Enable</td>
  −
      <td>yes | no; default: <b>no</b></td>
  −
      <td>Turns Post/Get on or off.</td>
  −
    </tr>
  −
    <tr>
  −
      <td>Username</td>
  −
      <td>string; default: <b>none</b></td>
  −
      <td>Username used for authentication in POST/GET queries.</td>
  −
    </tr>
  −
    <tr>
  −
    <td>Password</td>
  −
        <td>string; default: <b>none</b></td>
  −
        <td>Password used for authentication in POST/GET queries.</td>
  −
    </tr>
  −
</table>
  −
  −
====Post/Get examples====
  −
----
  −
It is possible to turn the {{#ifeq:{{{name}}}|RUT955|outputs|output}} on and off by using a HTTP POST/GET requests. Use a web browser or any other compatible software to send HTTP POST/GET requests to the device.
  −
  −
Below is a table containing syntax examples of this usage:
  −
  −
{{Template:Networking_{{#ifeq:{{{name}}}|RUT955|{{lc:{{{name}}}}}|{{lc:{{{series}}}}}}}_manual_input_output_post_get_examples_table|name={{{name}}}}}
  −
  −
<b>Overview</b>:
  −
<ul>
  −
    <li>192.168.1.1 - router's default LAN IP address; replace it in accordance with your own configuration.</li>
  −
    <li>username - login name 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>pin - specifies the output (use <i>oc</i>{{#ifeq:{{{name}}}|RUT955| or <i>relay</i>|}}).</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>
  −
</ul>
  −
  −
Delay and time parameters can be used together. For example, if delay is 10, time is 5, action is on, then 10 seconds after the execution of the command, the output will switch to <i>on</i> (or stay in <i>on</i> state if it was already that way), then after 5 more seconds it will switch to <i>off</i> state. In this case the overall command execution time is 15 seconds.
      
===Periodic control===
 
===Periodic control===
Line 198: Line 148:  
With the help of the output <b>Scheduler</b> you can configure a timetable of when the {{#ifeq:{{{name}}}|RUT955|outputs|output}} should be enabled or disabled based on time.  
 
With the help of the output <b>Scheduler</b> you can configure a timetable of when the {{#ifeq:{{{name}}}|RUT955|outputs|output}} should be enabled or disabled based on time.  
   −
[[File:{{{file_output_scheduler}}}]]
+
[[File:{{{file_output_scheduler}}}|border|class=tlt-border]]
 +
 
 +
==Post/Get==
 +
----
 +
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 and the table below provides information on the fields contained in that section:
 +
 
 +
[[File:{{{file_output_post_get}}}|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable</td>
 +
      <td>yes | no; default: <b>no</b></td>
 +
      <td>Turns Post/Get on or off.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Username</td>
 +
      <td>string; default: <b>none</b></td>
 +
      <td>Username used for authentication in POST/GET queries.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Password</td>
 +
        <td>string; default: <b>none</b></td>
 +
        <td>Password used for authentication in POST/GET queries.</td>
 +
    </tr>
 +
</table>
 +
 
 +
===Post/Get examples===
 +
----
 +
It is possible to turn the {{#ifeq:{{{name}}}|RUT955|outputs|output}} on and off by using a HTTP POST/GET requests. Use a web browser or any other compatible software to send HTTP POST/GET requests to the device.
 +
 
 +
Below is a table containing syntax examples of this usage:
 +
 
 +
{{Template:Networking_{{#ifeq:{{{name}}}|RUT955|{{lc:{{{name}}}}}|{{lc:{{{series}}}}}}}_manual_input_output_post_get_examples_table|name={{{name}}}}}
 +
 
 +
<b>Overview</b>:
 +
<ul>
 +
    <li>192.168.1.1 - router's default LAN IP address; replace it in accordance with your own configuration.</li>
 +
    <li>username - login name 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>pin - specifies the output (use <i>oc</i>{{#ifeq:{{{name}}}|RUT955| or <i>relay</i>|}}).</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>
 +
</ul>
 +
 
 +
Delay and time parameters can be used together. For example, if delay is 10, time is 5, action is on, then 10 seconds after the execution of the command, the output will switch to <i>on</i> (or stay in <i>on</i> state if it was already that way), then after 5 more seconds it will switch to <i>off</i> state. In this case the overall command execution time is 15 seconds.
 +
 
 
{{#ifeq: {{{series}}} | RUT9XX ||
 
{{#ifeq: {{{series}}} | RUT9XX ||
 
==Additional Information==
 
==Additional Information==