Template:Networking rut manual input output: Difference between revisions
No edit summary |
No edit summary |
||
| Line 89: | Line 89: | ||
[[File:{{{file_output_on_off}}}]] | [[File:{{{file_output_on_off}}}]] | ||
<!-- | <!-- | ||
===Post/Get | ===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 an the table below provides information on the fields contained in that section: | |||
[[File: | [[File:{{{file_output_post_get}}}]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>yes | no; | <td>yes | no; default: <b>no</b></td> | ||
<td> | <td>Turns Post/Get on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Username</td> | <td>Username</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>Username used for authentication in POST/GET queries</td> | <td>Username used for authentication in POST/GET queries.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Password</td> | <td>Password</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>Password used for authentication in POST/GET queries</td> | <td>Password used for authentication in POST/GET queries.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
====Post/Get | ====Post/Get examples==== | ||
---- | ---- | ||
{{ | It is possible to turn the {{#ifeq:{{{name}}}|RUT955|outputs|output}} on and off by using a valid HTTP POST/GET syntax. Use a web browser or any other compatible software to submit HTTP POST/GET strings to the device. | ||
<table class="nd- | Below is a table containing syntax examples of this usage: | ||
<table class="nd-othertables_2"> | |||
<tr> | <tr> | ||
<th style="width: 500px">Action</th> | |||
< | <th style="width: 900px">POST/GET URL</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Turn | <td>Turn output on</td> | ||
<td>http://192.168.1.1/cgi-bin/output?username=user1&password=user1&action=on&pin= | <td><nowiki>http://192.168.1.1/cgi-bin/output?username=user1&password=user1&</nowiki><span style="color: #0054a6;><b>action=on</b></span><nowiki>&pin=pin2</nowiki></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Turn output off</td> | |||
<td><nowiki>http://192.168.1.1/cgi-bin/output?username=user1&password=user1&</nowiki><span style="color: #0054a6;><b>action=off</b></span><nowiki>&pin=pin2</nowiki></td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Turn output on after a 10 second delay</td> | |||
<td><nowiki>http://192.168.1.1/cgi-bin/output?username=user1&password=user1&action=on&pin=pin2&</nowiki><span style="color: #0054a6;><b>delay=10</b></span></td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Turn output on for 5 seconds</td> | |||
<td><nowiki>http://192.168.1.1/cgi-bin/output?username=user1&password=user1&action=on&pin=pin2&</nowiki><span style="color: #0054a6;><b>time=5</b></span></td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Turn | <td>Turn output on for 5 seconds after a 10 second delay</td> | ||
<td>http://192.168.1.1/cgi-bin/output?username=user1&password=user1&action=on&pin= | <td><nowiki>http://192.168.1.1/cgi-bin/output?username=user1&password=user1&action=on&pin=pin2&</nowiki><span style="color: #0054a6;><b>delay=10&time=5</b></span></td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
<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>pin2</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=== | ||
---- | ---- | ||
Revision as of 13:36, 29 July 2019
Summary
Inputs and Outputs 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.
The information in this page is updated in accordance with the [[Media:{{{fw_version}}}_WEBUI.bin|{{{fw_version}}}]] firmware version.
Characteristics
{{Template:Networking_{{{name}}}_manual_input_output_characteristics|name={{{name}}}}}
Status
The Status tab displays the current states the router’s input and output:
[[File:{{{file_status}}}]]
Custom Labels
If the default Input/Output labels do not suit your needs, you can always configure custom ones in the Custom Labels 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}}}]]
The figure above is an example of custom label configuration for Digital Input. 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.
Status and control from command line
{{Template: Networking_{{{name}}}_manual_input_output_cli}}
Input
The Input tab is used to configure the router's input pin.
Input Rules
The Input Rules 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}}}]]
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}}}]]
{{Template:Networking_{{{series}}}_manual_input_output_input_rule_table|name={{{name}}}}}
Output
The Output tab is used to configure the router's output {{ifeq:{{{name}}}|RUT955|pins|pin}}.
Output Configuration
The Output Configuration section is used to change the default {{ifeq:{{{name}}}|RUT955|states|state}} of the router's output {{ifeq:{{{name}}}|RUT955|pins|pin}}.
[[File:{{{file_output_config}}}]]
| Field | Value | Description |
|---|---|---|
| Open collector output | Low level | High level; default: High level | Changes the default* state of the open collector (OC) output pin. |
* Changing the default state of an output means that the changes will be written into the input/output config and saved. This means that unless some other related change occurs the state of the output will remain as set in this section.
ON/OFF
The ON/OFF 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}}}]] [[Category:{{{name}}} WebUI]]