Difference between revisions of "Template:Networking rutos manual input output"
(complete for rutx) |
|||
(144 intermediate revisions by 21 users not shown) | |||
Line 1: | Line 1: | ||
− | {{Template: | + | {{Template:Networking_rutos_manual_fw_disclosure |
+ | | fw_version = {{{series}}}_R_00.02.03 | ||
| series = {{{series}}} | | series = {{{series}}} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
}} | }} | ||
− | |||
− | + | __TOC__ | |
− | |||
− | |||
==Summary== | ==Summary== | ||
− | <b>Inputs</b> and <b>outputs</b> are used for monitoring and controlling a connected device or receiving signals from that device in order to trigger certain events. | + | <b>Inputs</b> and <b>outputs</b> are used for monitoring and controlling a connected device or receiving signals from that device in order to trigger certain events. This chapter is an overview of the Input/Output section for {{{name}}} routers. |
+ | {{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer}} | ||
− | + | ==Characteristics== | |
− | {{ | + | {{#switch:{{{series}}} |
− | + | | RUTX = | |
− | + | The router's input/output pins can be found inside the power socket: | |
− | |||
− | |||
− | |||
− | |||
− | + | [[File:Networking_rutx_manual_input_output_status_pinout_v1.png]] | |
− | |||
− | |||
− | |||
− | |||
− | |||
---- | ---- | ||
− | + | The electric characteristics for the input and output pins are as follows: | |
<ul> | <ul> | ||
− | <li> | + | <li>Digital non-isolated input: |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<ul> | <ul> | ||
− | <li>0- | + | <li>logic low: 0 - 5 V</li> |
− | <li> | + | <li>logic high: 8 - 40 V</li> |
</ul> | </ul> | ||
</li> | </li> | ||
− | <li> | + | <li>Digital open collector output: 30 V, 300 mA</li> |
− | |||
− | |||
− | |||
− | |||
</ul> | </ul> | ||
− | | | + | | TRB1 = |
+ | {{#ifeq:{{{name}}}|TRB141 | ||
+ | | | ||
+ | TRB141 has eighteen input/output pins, two of them can be found inside the power socket and the rest sixteen are on the side of the device. A list of Input/Output electric characteristics inherent in TRB141 routers can be found bellow. | ||
+ | |||
+ | ===Power Socket Pins=== | ||
+ | ---- | ||
+ | [[File:Networking_trb141_manual_I-O_power_v1.png|border|class=tlt-border|353x353px]]<br /> | ||
+ | |||
+ | *'''Power''' pin: +9 ... +30 VDC positive power input. | ||
+ | *'''Ground''' pin: negative/ground connection from power supply. | ||
+ | *'''I/0''' pins: programmable Input/Output pins (Open Collector output, max 30V or Digital input where 0-7.3 V is detected as logical "0", 7.3-30 V is detected as logical "1"). | ||
+ | | | ||
+ | This section provides a list Input/Output electric characteristics inherent in {{{name}}} devices: | ||
+ | |||
+ | [[File:Networking_rutx_manual_input_output_status_pinout_v1.png]] | ||
---- | ---- | ||
− | + | The electric characteristics for the input and output pins are as follows: | |
<ul> | <ul> | ||
− | <li> | + | <li>Digital non-isolated input: |
<ul> | <ul> | ||
− | <li>0- | + | <li>logic low: 0 - 5 V</li> |
− | <li> | + | <li>logic high: 8 - 40 V</li> |
</ul> | </ul> | ||
− | + | </li> | |
− | + | <li>Digital open collector output: 30 V, 300 mA</li> | |
− | |||
− | |||
− | |||
− | <li> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</ul> | </ul> | ||
+ | }} | ||
+ | | TRB2 = | ||
− | + | | | |
}} | }} | ||
==Status== | ==Status== | ||
− | The <b>Status</b> page displays the current states of the | + | The <b>Status</b> page displays the current states of the router's input and output: |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | [[File:Networking_rutx_manual_input_output_status_v2.png|border|class=tlt-border]] | |
− | [[File: | ||
− | + | You can invert Input pin by clicking on clider in <b>Inversion</b> column and switch Output pin state by clicking on slider in <b>State</b> column. | |
− | |||
− | |||
− | |||
===Status from command line=== | ===Status from command line=== | ||
---- | ---- | ||
− | You can also obtain the status of input | + | You can also obtain the status of the input or output from the command line. List of ubus possible <b>values</b> in {{{name}}} devices: |
− | + | ioman.gpio.din1 | |
− | + | ioman.gpio.dout1 | |
− | + | ||
− | + | Call command <b>ubus call <u>value</u> status </b>: | |
− | + | root@Teltonika-{{{name}}}:~# ubus call ioman.gpio.dout1 status | |
− | + | { | |
− | + | "value": "0", | |
+ | "direction": "in", | ||
+ | "bi_dir": false, | ||
+ | "invert_input": false | ||
+ | } | ||
− | + | <ul> | |
− | + | <li><b>din1</b> is the input: | |
− | + | <ul> | |
− | + | <li>"value": "<b>0</b>" means low level state.</li> | |
+ | <li>"value": "<b>1</b>" means high level state.</li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | <li><b>dout1</b> is the output: | ||
+ | <ul> | ||
+ | <li>"value": "<b>0</b>" means low level state.</li> | ||
+ | <li>"value": "<b>1</b>" means high level state.</li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | </ul> | ||
==Post/Get== | ==Post/Get== | ||
− | Enabling <b>Post/Get</b> | + | Enabling <b>Post/Get</b> will allow you to send HTTP POST/GET requests to device which controls 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:Networking_rutx_manual_input_output_post_get_v1.png|border|class=tlt-border]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 155: | Line 117: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
− | <td>off | + | <td>off | on; default: <b>off</b></td> |
<td>Turns Post/Get on or off.</td> | <td>Turns Post/Get on or off.</td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 172: | Line 129: | ||
<td>string; default: <b>none</b></td> | <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 examples=== | ===Post/Get examples=== | ||
---- | ---- | ||
− | Use a web browser or any other compatible software to | + | It is possible to turn the 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. |
− | + | Below is a table containing syntax examples of this usage: | |
− | |||
− | |||
<table class="nd-othertables_2"> | <table class="nd-othertables_2"> | ||
Line 195: | Line 143: | ||
<th style="width: 900px">POST/GET URL</th> | <th style="width: 900px">POST/GET URL</th> | ||
</tr> | </tr> | ||
− | |||
<tr> | <tr> | ||
− | <td>Turn Output state to high</td | + | <td>Turn Output state to high</td> |
− | <td><nowiki>http://192.168. | + | <td><nowiki>http://192.168.1.1/cgi-bin/io_state?username=user1&password=user1&pin=dout1</nowiki><span style="color: #0054a6;"><b><nowiki>&state=on</nowiki></b></span></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Turn Output state to low after 5 seconds for 3 seconds</td> | <td>Turn Output state to low after 5 seconds for 3 seconds</td> | ||
− | <td><nowiki>http://192.168. | + | <td><nowiki>http://192.168.1.1/cgi-bin/io_state?username=user1&password=user1&pin=dout1&state=on</nowiki><span style="color: #0054a6;"><b><nowiki>&delay=5</nowiki></b></span><span style="color: #3232ff;"><b><nowiki>&time=3</nowiki></b></span></td> |
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</table> | </table> | ||
<b>Overview</b>: | <b>Overview</b>: | ||
<ul> | <ul> | ||
− | <li>192.168. | + | <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>username - login name from Post/Get configuration.</li> | ||
<li>password- password from Post/Get configuration.</li> | <li>password- password from Post/Get configuration.</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> | ||
</ul> | </ul> | ||
− | Delay and time parameters can be used together. | + | 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. | ||
− | + | ==Scheduler== | |
− | + | With the help of the output <b>Scheduler</b> you can configure a timetable of when the output should be enabled or disabled based on date and time. | |
− | + | By default everything is unset. | |
− | |||
− | |||
− | = | + | [[File:Networking_rutx_manual_input_output_output_scheduler_v2.png|border|class=tlt-border]] |
− | |||
− | |||
− | + | ==Io juggler== | |
− | + | The <b>Io juggler</b> page is used create automated actions based on Input state and conditions. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | == | + | ===General=== |
+ | ---- | ||
− | The | + | The <b>General</b> section allows you to create automated Actions based on selected Inputs and their trigger state. |
+ | The figure below is an example of Conditions section. | ||
− | [[File: | + | [[File:Networking_rutx_manual_input_output_iojuggler_general_v1.png]] |
− | + | ====Modify Input configuration==== | |
− | + | ---- | |
− | |||
− | + | You can find explanation about fields in the table below this illustration. | |
− | [[File: | + | [[File:Networking_rutx_manual_input_output_iojuggler_general_modify_v1.png]] |
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
Line 302: | Line 200: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | + | <td>Enabled</td> | |
− | + | <td>off {{!}} on; default: <b>off</b> </td> | |
− | + | <td>Changes current profile to specified one when action triggers.</td> | |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | + | <td>Trigger interval</td> | |
− | + | <td>positive integer; default: <b>none</b></td> | |
− | + | <td>Specifies what is the shortest amount of seconds between triggers.</td> | |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | + | <td>Trigger</td> | |
− | + | <td>Rising {{!}} Falling {{!}} Both; default: <b>Rising</b> </td> | |
− | + | <td>Specifies on which trigger state this rule will be activated.</td> | |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | + | <td>Add actions</td> | |
− | + | <td>actions; default: <b>none</b> </td> | |
− | + | <td>Specifies actions which have to be met for rule to be executed. Actions are optional.</td> | |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | + | <td>Add conditions</td> | |
− | + | <td>conditions; default: <b>none</b> </td> | |
− | + | <td>Specifies conditions which have to be met for action to occur. Conditions are optional.</td> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | ===Actions=== | |
− | |||
− | |||
− | |||
− | == | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
---- | ---- | ||
− | |||
− | + | The <b>Actions</b> section lets you manage your created Actions for IO Juggler inputs. | |
− | + | The figure below is an example of Actions section. | |
− | |||
− | |||
− | |||
− | + | [[File:Networking_rutx_manual_input_output_iojuggler_actions_v1.png]] | |
− | + | ====Modify action==== | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
---- | ---- | ||
− | |||
− | [[File: | + | [[File:Networking_rutx_manual_input_output_iojuggler_actions_modify_v1.png]] |
− | + | Above is an example of what action configuration window looks like. Below is a table with detailed explanations on | |
− | + | how to configure the action and what each of the fields mean. To avoid redundancy, screenshots for the other actions | |
− | + | will not be provided, since the structures, syntax and the overall look of the configuration windows for each action | |
+ | are very similar. Instead, only tables containing information on how to edit each action will be provided. | ||
− | + | =====Profile===== | |
− | |||
− | |||
− | |||
− | === | ||
---- | ---- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 406: | Line 253: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Type</td> |
− | <td> | + | <td>Profile</td> |
<td>Changes current profile to specified one when action triggers.</td> | <td>Changes current profile to specified one when action triggers.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Execution delay</td> |
− | <td>integer | + | <td>positive integer; default: <b>none</b></td> |
− | <td> | + | <td>How many seconds will pass before the action is excecuted after it's triggered.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Profile</td> |
− | <td> | + | <td>profile; default: <b>default</b> </td> |
− | + | <td>Choose a profile that will be applied when the action triggers.</td> | |
− | |||
− | |||
− | |||
− | |||
− | <td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Add conditions</td> | <td>Add conditions</td> | ||
− | <td> | + | <td>conditions; default: <b>none</b> </td> |
− | <td> | + | <td>Specifies conditions which have to be met for action to occur. Conditions are optional.</td> |
</tr> | </tr> | ||
</table> | </table> | ||
− | === | + | =====Email===== |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
---- | ---- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 465: | Line 281: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Type</td> | ||
+ | <td>Email</td> | ||
+ | <td>Sends email when action triggers.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 474: | Line 295: | ||
<td>Text message</td> | <td>Text message</td> | ||
<td>string; default: <b>none</b> </td> | <td>string; default: <b>none</b> </td> | ||
− | <td> | + | <td>Text message to be sent in email. Below this field you can find device information and |
+ | their codes, which can be included in messages to send device information.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Execution delay</td> | ||
+ | <td>positive integer; default: <b>none</b></td> | ||
+ | <td>How many seconds will pass before the action is excecuted after it's triggered.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Email user</td> | ||
+ | <td>email user; default: <b>none</b></td> | ||
+ | <td>Configured email user.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Recipient's email address</td> | ||
+ | <td>string; default: <b>none</b></td> | ||
+ | <td>Email receiver(s).</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Add conditions</td> | ||
+ | <td>conditions; default: <b>none</b> </td> | ||
+ | <td>Specifies conditions which have to be met for action to occur. Conditions are optional.</td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | {{#ifeq:{{{mobile}}}|1| | ||
+ | =====SMS===== | ||
+ | ---- | ||
+ | <table class="nd-mantable"> | ||
+ | <tr> | ||
+ | <th>Field</th> | ||
+ | <th>Value</th> | ||
+ | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Type</td> | ||
+ | <td>SMS</td> | ||
+ | <td>Sends sms when action triggers.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Text message</td> | ||
+ | <td>string; default: <b>none</b> </td> | ||
+ | <td>Text message to be sent in sms. Below this field you can find device information and | ||
+ | their codes, which can be included in messages to send device information.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Execution delay</td> | <td>Execution delay</td> | ||
<td>positive integer; default: <b>none</b></td> | <td>positive integer; default: <b>none</b></td> | ||
− | <td> | + | <td>How many seconds will pass before the action is excecuted after it's triggered.</td> |
− | </tr> | + | </tr> |
− | + | <tr> | |
+ | <td>Recipients</td> | ||
+ | <td><span style="color:red;">Single number</span> {{!}} <span style="color:blue;">Group</span>; default: <b>Single number</b></td> | ||
+ | <td>How many recipients will get the message.</td> | ||
+ | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:red;">Recipient's phone number</span></td> |
− | <td> | + | <td>number; default: <b>none</b></td> |
− | <td> | + | <td>SMS receiver.</td> |
− | </tr> | + | </tr> |
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:blue;">Phone group</span></td> |
− | <td> | + | <td>phone group; default: <b>none</b></td> |
− | <td> | + | <td>SMS receivers.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Add conditions</td> |
− | <td> | + | <td>conditions; default: <b>none</b> </td> |
− | <td> | + | <td>Specifies conditions which have to be met for action to occur. Conditions are optional.</td> |
</tr> | </tr> | ||
</table> | </table> | ||
− | + | |}} | |
− | ==== | + | =====Output===== |
---- | ---- | ||
− | |||
− | |||
− | |||
− | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 510: | Line 373: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Type</td> | ||
+ | <td>Output</td> | ||
+ | <td>Changes Output state when action triggers.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Execution delay</td> | <td>Execution delay</td> | ||
<td>positive integer; default: <b>none</b></td> | <td>positive integer; default: <b>none</b></td> | ||
− | <td> | + | <td>How many seconds will pass before the action is excecuted after it's triggered.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Control</td> | <td>Control</td> | ||
− | <td>output; default: <b> | + | <td>output/relay; default: <b>Output(4)</b></td> |
− | <td> | + | <td>Specifies the output/relay of which the state will be changed.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Revert</td> | <td>Revert</td> | ||
− | <td>integer; default: <b>0</b></td> | + | <td>integer; default: <b>0</b> </td> |
− | <td>After how many seconds the state will revert. If left | + | <td>After how many seconds the state will revert. If left 0 or empty the state will not revert.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Maintain</td> | <td>Maintain</td> | ||
<td>off | on; default: <b>on</b></td> | <td>off | on; default: <b>on</b></td> | ||
− | <td> | + | <td>Maintain this IO state after reboot.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Invert</td> | <td>Invert</td> | ||
<td>off | on; default: <b>off</b></td> | <td>off | on; default: <b>off</b></td> | ||
− | <td> | + | <td>On action inverts pin state.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>State copying</td> | <td>State copying</td> | ||
<td>off | on; default: <b>off</b></td> | <td>off | on; default: <b>off</b></td> | ||
− | <td>Copies the state from | + | <td>Copies the state from selected input to selected output.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>State</td> | <td>State</td> | ||
<td>High | Low; default: <b>High</b></td> | <td>High | Low; default: <b>High</b></td> | ||
− | <td>Specifies | + | <td>Specifies what state the output pin will be set to.</td> |
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Add conditions</td> | ||
+ | <td>conditions; default: <b>none</b> </td> | ||
+ | <td>Specifies conditions which have to be met for action to occur. Conditions are optional.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | ==== | + | =====HTTP===== |
---- | ---- | ||
− | |||
− | |||
− | |||
− | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 559: | Line 428: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Type</td> | ||
+ | <td>HTTP</td> | ||
+ | <td>Sends HTTP request when action triggers.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Execution delay</td> | ||
+ | <td>positive integer; default: <b>none</b></td> | ||
+ | <td>How many seconds will pass before the action is excecuted after it's triggered.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Method</td> | <td>Method</td> | ||
− | <td>Get | + | <td>Get {{!}} Post; default: <b>Get</b></td> |
− | <td> | + | <td>Specifies the output/relay of which the state will be changed.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>URL</td> | <td>URL</td> | ||
<td>string; default: <b>none</b> </td> | <td>string; default: <b>none</b> </td> | ||
− | <td>URL to send | + | <td>URL to send request to.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Verify</td> | <td>Verify</td> | ||
<td>off | on; default: <b>off</b></td> | <td>off | on; default: <b>off</b></td> | ||
− | <td>Verifies the validity of certificates | + | <td>Verifies the validity of certificates, only works for https.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td | + | <td>Parameters</td> |
− | |||
− | |||
− | |||
− | |||
− | |||
<td>string; default: <b>none</b></td> | <td>string; default: <b>none</b></td> | ||
− | <td>Parameters | + | <td>Parameters and their value from device for usage in Post or Get requests. |
+ | Possible values: Time stamp, UNIX time, WAN MAC, Wired WAN IP, Network info, Product code, LAN MAC address, LAN IP address, Serial number, Current FW version, Monitoring status, Input Name, Input state change trigger, RSCP, ECIO, SIM slot in use, CELLID, RSRQ, SINR, RSRP, SIM State, SIM pin state, Modem model, IMSI, Modem serial number , Network State, Data connection state, Connection type, Mobile IP, Operator name, Signal strenght, IMEI, ICCID, Neighbour cells, Network serving.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Add conditions</td> |
− | + | <td>conditions; default: <b>none</b> </td> | |
− | + | <td>Specifies conditions which have to be met for action to occur. Conditions are optional.</td> | |
− | |||
− | |||
− | |||
− | <td> | ||
− | <td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
− | ==== | + | =====Script===== |
---- | ---- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 617: | Line 474: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Type</td> | ||
+ | <td>Script</td> | ||
+ | <td>Runs script when action triggers.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Execution delay</td> | <td>Execution delay</td> | ||
<td>positive integer; default: <b>none</b></td> | <td>positive integer; default: <b>none</b></td> | ||
− | <td> | + | <td>How many seconds will pass before the action is excecuted after it's triggered.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Specify path</td> | <td>Specify path</td> | ||
− | <td>Upload a script | + | <td><span style="color:red;">Upload a script</span> {{!}} <span style="color:blue;">Specify path</span>; default: <b>Upload a cript</b></td> |
− | <td> | + | <td>Selection to upload a script or specify its absolute path in device.</td> |
+ | </tr> | ||
+ | <tr> | ||
+ | <td><span style="color:red;">Custom script</span></td> | ||
+ | <td>-(interactive button)</td> | ||
+ | <td>Shows file upload window on click.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:blue;">Script file</span></td> |
− | <td> | + | <td>string; default: <b>none</b></td> |
− | <td> | + | <td>Absolute path to script file in device.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Arguments</td> | <td>Arguments</td> | ||
− | <td>string; default: <b>none</b></td> | + | <td>string; default: <b>none</b> </td> |
<td>Optional arguments which can be provided for the script. You can include device information with values given below this input field.</td> | <td>Optional arguments which can be provided for the script. You can include device information with values given below this input field.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Add conditions</td> | ||
+ | <td>conditions; default: <b>none</b> </td> | ||
+ | <td>Specifies conditions which have to be met for action to occur. Conditions are optional.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | ==== | + | =====Reboot===== |
---- | ---- | ||
− | |||
− | |||
− | |||
− | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 651: | Line 519: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Type</td> | ||
+ | <td>Reboot</td> | ||
+ | <td>Reboots device when action triggers.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Execution delay</td> | <td>Execution delay</td> | ||
<td>positive integer; default: <b>none</b></td> | <td>positive integer; default: <b>none</b></td> | ||
− | <td> | + | <td>How many seconds will pass before the action is excecuted after it's triggered.</td> |
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Add conditions</td> | ||
+ | <td>conditions; default: <b>none</b> </td> | ||
+ | <td>Specifies conditions which have to be met for action to occur. Conditions are optional.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | {{#ifeq:{{{mobile}}}|1| | |
− | ==== | + | =====Change sim===== |
---- | ---- | ||
− | |||
− | |||
− | |||
− | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 670: | Line 544: | ||
<th>Value</th> | <th>Value</th> | ||
<th>Description</th> | <th>Description</th> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Type</td> | ||
+ | <td>Change sim</td> | ||
+ | <td>Changes active sim card when action triggers.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Execution delay</td> | <td>Execution delay</td> | ||
<td>positive integer; default: <b>none</b></td> | <td>positive integer; default: <b>none</b></td> | ||
− | <td> | + | <td>How many seconds will pass before the action is excecuted after it's triggered.</td> |
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Flip</td> | ||
+ | <td><span style="color:red;">off</span> {{!}} on; default: <b>off</b></td> | ||
+ | <td>Switches to a different sim card.</td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td><span style="color:red;">Target</span></td> | ||
+ | <td>Sim1 {{!}} Sim2; default: <b>Sim1</b></td> | ||
+ | <td>Switches to a selected sim card.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Add conditions</td> |
− | <td> | + | <td>conditions; default: <b>none</b> </td> |
− | <td> | + | <td>Specifies conditions which have to be met for action to occur. Conditions are optional.</td> |
</tr> | </tr> | ||
</table> | </table> | ||
+ | |}} | ||
+ | ===Conditions=== | ||
+ | ---- | ||
+ | |||
+ | The <b>Conditions</b> section lets you manage your created Conditions for IO Juggler Actions. | ||
+ | The figure below is an example of Conditions section. | ||
+ | |||
+ | [[File:Networking_rutx_manual_input_output_iojuggler_conditions_v1.png]] | ||
− | ==== | + | ====Modify condition==== |
---- | ---- | ||
− | |||
− | [[File: | + | [[File:Networking_rutx_manual_input_output_iojuggler_conditions_modify_v1.png]] |
+ | |||
+ | Above is an example of what condition configuration window looks like. Below is a table with detailed explanations on | ||
+ | how to configure the condition and what each of the fields mean. To avoid redundancy, screenshots for the other conditions | ||
+ | will not be provided, since the structures, syntax and the overall look of the configuration windows for each condition | ||
+ | are very similar. Instead, only tables containing information on how to edit each condition will be provided. | ||
+ | =====Boolean group===== | ||
+ | ---- | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 696: | Line 599: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Condition type</td> |
− | <td> | + | <td>Boolean group</td> |
− | <td> | + | <td>A type of condition.</td> |
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Boolean type</td> | ||
+ | <td>AND {{!}} NAND {{!}} OR {{!}} NOR; default: <b>AND</b></td> | ||
+ | <td>Type of boolean condition.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Add conditions</td> |
− | <td> | + | <td>conditions; default: <b>none</b> </td> |
− | <td>Specifies | + | <td>Specifies conditions which have to be met for action to occur. Conditions are optional.</td> |
</tr> | </tr> | ||
</table> | </table> | ||
− | ==== | + | =====I/O===== |
---- | ---- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 725: | Line 624: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Condition type</td> |
− | <td> | + | <td>I/O</td> |
− | <td> | + | <td>A type of condition.</td> |
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>I/O</td> |
− | <td> | + | <td>inputs/outputs; default: <b>Output(4)</b></td> |
− | <td> | + | <td>Specifies the I/O to which the condition is listening to.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>State</td> |
− | <td> | + | <td>High {{!}} Low; default: <b>High</b> </td> |
− | <td> | + | <td>Specifies in what state the pin has to be.</td> |
</tr> | </tr> | ||
+ | </table> | ||
+ | |||
+ | =====Minute===== | ||
+ | ---- | ||
+ | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
− | < | + | <th>Field</th> |
− | + | <th>Value</th> | |
− | + | <th>Description</th> | |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Condition type</td> |
− | <td> | + | <td>Minute</td> |
− | <td> | + | <td>A type of condition.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Inverted function</td> |
− | <td> | + | <td>off {{!}} on; default: <b>off</b> </td> |
− | <td> | + | <td>Inverts the selected condition type. Makes the condition true if the time/date is outside the specified interval.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Interval</td> |
− | <td> | + | <td><span style="color:red;">off</span> | <span style="color:blue;">on</span>; default: <b>off</b></td> |
− | <td> | + | <td>Switches between a specific value and a time interval.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:red;">Minute</span></td> |
− | <td> | + | <td>integer [0..59]; default: <b>none</b></td> |
− | <td> | + | <td>Specifies minute at which the action can occur.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:blue ;">Start minute</span></td> |
− | <td> | + | <td>integer [0..59]; default: <b>none</b></td> |
− | <td> | + | <td>Specifies starting minute of the interval at which the action can occur.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:blue ;">End minute</span></td> |
− | + | <td>integer [0..59]; default: <b>none</b></td> | |
− | <td> | + | <td>Specifies ending minute of the interval at which the action can occur.</td> |
</tr> | </tr> | ||
+ | </table> | ||
+ | |||
+ | =====Hour===== | ||
+ | ---- | ||
+ | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
− | < | + | <th>Field</th> |
− | + | <th>Value</th> | |
− | + | <th>Description</th> | |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Condition type</td> |
− | <td> | + | <td>Hour</td> |
− | <td> | + | <td>A type of condition.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Inverted function</td> |
− | <td>off {{!}} on; default: <b>off</b></td> | + | <td>off {{!}} on; default: <b>off</b> </td> |
− | <td> | + | <td>Inverts the selected condition type. Makes the condition true if the time/date is outside the specified interval.</td> |
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td><span style="color: | + | <td>Interval</td> |
− | + | <td><span style="color:red;">off</span> | <span style="color:blue;">on</span>; default: <b>off</b></td> | |
− | <td> | + | <td>Switches between a specific value and a time interval.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td><span style="color: | + | <td><span style="color:red;">Hour</span></td> |
− | <td>. | + | <td>integer [0..59]; default: <b>none</b></td> |
− | <td> | + | <td>Specifies hour at which the action can occur.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td><span style="color:blue"> | + | <td><span style="color:blue ;">Start hour</span></td> |
− | <td> | + | <td>integer [0..59]; default: <b>none</b></td> |
− | <td> | + | <td>Specifies starting hour of the interval at which the action can occur.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td><span style="color:blue"> | + | <td><span style="color:blue ;">End hour</span></td> |
− | <td> | + | <td>integer [0..59]; default: <b>none</b></td> |
− | <td> | + | <td>Specifies ending hour of the interval at which the action can occur.</td> |
</tr> | </tr> | ||
</table> | </table> | ||
− | + | =====Weekday===== | |
− | |||
− | ==== | ||
---- | ---- | ||
− | |||
− | |||
− | |||
− | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 832: | Line 729: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Condition type</td> |
− | <td> | + | <td>Weekday</td> |
− | <td>A | + | <td>A type of condition.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Inverted function</td> |
− | <td>off {{!}} on; default: <b>off</b></td> | + | <td>off {{!}} on; default: <b>off</b> </td> |
− | <td> | + | <td>Inverts the selected condition type. Makes the condition true if the time/date is outside the specified interval.</td> |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Interval</td> |
− | <td> | + | <td><span style="color:red;">off</span> | <span style="color:blue;">on</span>; default: <b>off</b></td> |
− | <td> | + | <td>Switches between a specific value and a time interval.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:red;">Weekday</span></td> |
− | <td> | + | <td>weekday; default: <b>Monday</b></td> |
− | <td> | + | <td>Specifies weekday at which the action can occur.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:blue ;">Start weekday</span></td> |
− | <td> | + | <td>weekday; default: <b>Monday</b></td> |
− | <td> | + | <td>Specifies starting weekday of the interval at which the action can occur.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:blue ;">End weekday</span></td> |
− | <td> | + | <td>weekday; default: <b>Monday</b></td> |
− | <td> | + | <td>Specifies ending weekday of the interval at which the action can occur.</td> |
</tr> | </tr> | ||
</table> | </table> | ||
− | + | ||
− | + | =====Month day===== | |
− | ==== | ||
---- | ---- | ||
− | |||
− | |||
− | |||
− | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 902: | Line 769: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Condition type</td> |
− | <td> | + | <td>Month day</td> |
− | <td> | + | <td>A type of condition.</td> |
+ | </tr> | ||
+ | <tr> | ||
+ | <td>Month override</td> | ||
+ | <td>off {{!}} on; default: <b>off</b> </td> | ||
+ | <td>If the option is selected and the specified day is not in the month then the condition uses the last day of the month.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Interval</td> |
− | <td>off | + | <td><span style="color:red;">off</span> | <span style="color:blue;">on</span>; default: <b>off</b></td> |
− | <td> | + | <td>Switches between a specific value and a time interval.</td> |
</tr> | </tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<tr> | <tr> | ||
− | < | + | <td><span style="color:red;">Day of the month</span></td> |
− | + | <td>integer [1..31]; default: <b>none</b></td> | |
− | + | <td>Specifies day of the month at which the action can occur.</td> | |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:blue ;">Start day of the month</span></td> |
− | <td> | + | <td>integer [1..31]; default: <b>none</b></td> |
− | <td>Specifies the | + | <td>Specifies starting day of the interval of the month at which the action can occur.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:blue ;">End day of the month</span></td> |
− | <td> | + | <td>integer [1..31]; default: <b>none</b></td> |
− | <td>Specifies | + | <td>Specifies ending day of the interval of the month at which the action can occur.</td> |
</tr> | </tr> | ||
</table> | </table> | ||
− | + | ||
− | ==== | + | =====Year===== |
---- | ---- | ||
− | |||
− | |||
− | |||
− | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
Line 963: | Line 809: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td>Condition</td> | + | <td>Condition type</td> |
− | <td> | + | <td>Year</td> |
− | <td> | + | <td>A type of condition.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Inverted function</td> |
− | <td> | + | <td>off {{!}} on; default: <b>off</b> </td> |
− | <td> | + | <td>Inverts the selected condition type. Makes the condition true if the time/date is outside the specified interval.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td>Interval</td> |
− | <td> | + | <td><span style="color:red;">off</span> | <span style="color:blue;">on</span>; default: <b>off</b></td> |
− | <td> | + | <td>Switches between a specific value and a time interval.</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:red;">Day of the year</span></td> |
− | <td> | + | <td>integer [1..366]; default: <b>none</b></td> |
− | <td>Specifies | + | <td>Specifies day of the year at which the action can occur.</td> |
</tr> | </tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<tr> | <tr> | ||
− | < | + | <td><span style="color:blue ;">Start day of the year</span></td> |
− | + | <td>integer [1..366]; default: <b>none</b></td> | |
− | + | <td>Specifies starting day of the interval of the year at which the action can occur.</td> | |
− | |||
− | |||
− | |||
− | <td> | ||
− | <td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <td> | + | <td><span style="color:blue ;">End day of the year</span></td> |
− | <td> | + | <td>integer [1..366]; default: <b>none</b></td> |
− | <td>Specifies | + | <td>Specifies ending day of the interval of the year at which the action can occur.</td> |
</tr> | </tr> | ||
</table> | </table> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
[[Category:{{{name}}} Services section]] | [[Category:{{{name}}} Services section]] |
Revision as of 11:05, 7 May 2020
Template:Networking rutos manual fw disclosure
Summary
Inputs and outputs are used for monitoring and controlling a connected device or receiving signals from that device in order to trigger certain events. This chapter is an overview of the Input/Output section for {{{name}}} routers. If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Advanced" button, located at the top of the WebUI.
Characteristics
Status
The Status page displays the current states of the router's input and output:
File:Networking rutx manual input output status v2.png
You can invert Input pin by clicking on clider in Inversion column and switch Output pin state by clicking on slider in State column.
Status from command line
You can also obtain the status of the input or output from the command line. List of ubus possible values in {{{name}}} devices:
ioman.gpio.din1 ioman.gpio.dout1
Call command ubus call value status :
root@Teltonika-{{{name}}}:~# ubus call ioman.gpio.dout1 status { "value": "0", "direction": "in", "bi_dir": false, "invert_input": false }
- din1 is the input:
- "value": "0" means low level state.
- "value": "1" means high level state.
- dout1 is the output:
- "value": "0" means low level state.
- "value": "1" means high level state.
Post/Get
Enabling Post/Get will allow you to send HTTP POST/GET requests to device which controls 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:
Field | Value | Description |
---|---|---|
Enable | off | on; default: off | Turns Post/Get on or off. |
Username | string; default: none | Username used for authentication in POST/GET queries. |
Password | string; default: none | Password used for authentication in POST/GET queries. |
Post/Get examples
It is possible to turn the 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.
Below is a table containing syntax examples of this usage:
Action | POST/GET URL |
---|---|
Turn Output state to high | http://192.168.1.1/cgi-bin/io_state?username=user1&password=user1&pin=dout1&state=on |
Turn Output state to low after 5 seconds for 3 seconds | http://192.168.1.1/cgi-bin/io_state?username=user1&password=user1&pin=dout1&state=on&delay=5&time=3 |
Overview:
- 192.168.1.1 - router's default LAN IP address; replace it in accordance with your own configuration.
- username - login name from Post/Get configuration.
- password- password from Post/Get configuration.
- delay - defines a delay (in seconds) after which the specified action will be performed.
- time - defines a window of time during which the action will take place. For instance, if you post an on action while specifying time=5, the output will turn on and stay on for 5 seconds before turning off.
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 on (or stay in on state if it was already that way), then after 5 more seconds it will switch to off state. In this case the overall command execution time is 15 seconds.
Scheduler
With the help of the output Scheduler you can configure a timetable of when the output should be enabled or disabled based on date and time. By default everything is unset.
Io juggler
The Io juggler page is used create automated actions based on Input state and conditions.
General
The General section allows you to create automated Actions based on selected Inputs and their trigger state. The figure below is an example of Conditions section.
Modify Input configuration
You can find explanation about fields in the table below this illustration.
Field | Value | Description |
---|---|---|
Enabled | off | on; default: off | Changes current profile to specified one when action triggers. |
Trigger interval | positive integer; default: none | Specifies what is the shortest amount of seconds between triggers. |
Trigger | Rising | Falling | Both; default: Rising | Specifies on which trigger state this rule will be activated. |
Add actions | actions; default: none | Specifies actions which have to be met for rule to be executed. Actions are optional. |
Add conditions | conditions; default: none | Specifies conditions which have to be met for action to occur. Conditions are optional. |
Actions
The Actions section lets you manage your created Actions for IO Juggler inputs. The figure below is an example of Actions section.
Modify action
Above is an example of what action configuration window looks like. Below is a table with detailed explanations on how to configure the action and what each of the fields mean. To avoid redundancy, screenshots for the other actions will not be provided, since the structures, syntax and the overall look of the configuration windows for each action are very similar. Instead, only tables containing information on how to edit each action will be provided.
Profile
Field | Value | Description |
---|---|---|
Type | Profile | Changes current profile to specified one when action triggers. |
Execution delay | positive integer; default: none | How many seconds will pass before the action is excecuted after it's triggered. |
Profile | profile; default: default | Choose a profile that will be applied when the action triggers. |
Add conditions | conditions; default: none | Specifies conditions which have to be met for action to occur. Conditions are optional. |
Field | Value | Description |
---|---|---|
Type | Sends email when action triggers. | |
Subject | string; default: none | Subject of email. |
Text message | string; default: none | Text message to be sent in email. Below this field you can find device information and their codes, which can be included in messages to send device information. |
Execution delay | positive integer; default: none | How many seconds will pass before the action is excecuted after it's triggered. |
Email user | email user; default: none | Configured email user. |
Recipient's email address | string; default: none | Email receiver(s). |
Add conditions | conditions; default: none | Specifies conditions which have to be met for action to occur. Conditions are optional. |
Output
Field | Value | Description |
---|---|---|
Type | Output | Changes Output state when action triggers. |
Execution delay | positive integer; default: none | How many seconds will pass before the action is excecuted after it's triggered. |
Control | output/relay; default: Output(4) | Specifies the output/relay of which the state will be changed. |
Revert | integer; default: 0 | After how many seconds the state will revert. If left 0 or empty the state will not revert. |
Maintain | off | on; default: on | Maintain this IO state after reboot. |
Invert | off | on; default: off | On action inverts pin state. |
State copying | off | on; default: off | Copies the state from selected input to selected output. |
State | High | Low; default: High | Specifies what state the output pin will be set to. |
Add conditions | conditions; default: none | Specifies conditions which have to be met for action to occur. Conditions are optional. |
HTTP
Field | Value | Description |
---|---|---|
Type | HTTP | Sends HTTP request when action triggers. |
Execution delay | positive integer; default: none | How many seconds will pass before the action is excecuted after it's triggered. |
Method | Get | Post; default: Get | Specifies the output/relay of which the state will be changed. |
URL | string; default: none | URL to send request to. |
Verify | off | on; default: off | Verifies the validity of certificates, only works for https. |
Parameters | string; default: none | Parameters and their value from device for usage in Post or Get requests. Possible values: Time stamp, UNIX time, WAN MAC, Wired WAN IP, Network info, Product code, LAN MAC address, LAN IP address, Serial number, Current FW version, Monitoring status, Input Name, Input state change trigger, RSCP, ECIO, SIM slot in use, CELLID, RSRQ, SINR, RSRP, SIM State, SIM pin state, Modem model, IMSI, Modem serial number , Network State, Data connection state, Connection type, Mobile IP, Operator name, Signal strenght, IMEI, ICCID, Neighbour cells, Network serving. |
Add conditions | conditions; default: none | Specifies conditions which have to be met for action to occur. Conditions are optional. |
Script
Field | Value | Description |
---|---|---|
Type | Script | Runs script when action triggers. |
Execution delay | positive integer; default: none | How many seconds will pass before the action is excecuted after it's triggered. |
Specify path | Upload a script | Specify path; default: Upload a cript | Selection to upload a script or specify its absolute path in device. |
Custom script | -(interactive button) | Shows file upload window on click. |
Script file | string; default: none | Absolute path to script file in device. |
Arguments | string; default: none | Optional arguments which can be provided for the script. You can include device information with values given below this input field. |
Add conditions | conditions; default: none | Specifies conditions which have to be met for action to occur. Conditions are optional. |
Reboot
Field | Value | Description |
---|---|---|
Type | Reboot | Reboots device when action triggers. |
Execution delay | positive integer; default: none | How many seconds will pass before the action is excecuted after it's triggered. |
Add conditions | conditions; default: none | Specifies conditions which have to be met for action to occur. Conditions are optional. |
Conditions
The Conditions section lets you manage your created Conditions for IO Juggler Actions. The figure below is an example of Conditions section.
Modify condition
Above is an example of what condition configuration window looks like. Below is a table with detailed explanations on how to configure the condition and what each of the fields mean. To avoid redundancy, screenshots for the other conditions will not be provided, since the structures, syntax and the overall look of the configuration windows for each condition are very similar. Instead, only tables containing information on how to edit each condition will be provided.
Boolean group
Field | Value | Description |
---|---|---|
Condition type | Boolean group | A type of condition. |
Boolean type | AND | NAND | OR | NOR; default: AND | Type of boolean condition. |
Add conditions | conditions; default: none | Specifies conditions which have to be met for action to occur. Conditions are optional. |
I/O
Field | Value | Description |
---|---|---|
Condition type | I/O | A type of condition. |
I/O | inputs/outputs; default: Output(4) | Specifies the I/O to which the condition is listening to. |
State | High | Low; default: High | Specifies in what state the pin has to be. |
Minute
Field | Value | Description |
---|---|---|
Condition type | Minute | A type of condition. |
Inverted function | off | on; default: off | Inverts the selected condition type. Makes the condition true if the time/date is outside the specified interval. |
Interval | off | on; default: off | Switches between a specific value and a time interval. |
Minute | integer [0..59]; default: none | Specifies minute at which the action can occur. |
Start minute | integer [0..59]; default: none | Specifies starting minute of the interval at which the action can occur. |
End minute | integer [0..59]; default: none | Specifies ending minute of the interval at which the action can occur. |
Hour
Field | Value | Description |
---|---|---|
Condition type | Hour | A type of condition. |
Inverted function | off | on; default: off | Inverts the selected condition type. Makes the condition true if the time/date is outside the specified interval. |
Interval | off | on; default: off | Switches between a specific value and a time interval. |
Hour | integer [0..59]; default: none | Specifies hour at which the action can occur. |
Start hour | integer [0..59]; default: none | Specifies starting hour of the interval at which the action can occur. |
End hour | integer [0..59]; default: none | Specifies ending hour of the interval at which the action can occur. |
Weekday
Field | Value | Description |
---|---|---|
Condition type | Weekday | A type of condition. |
Inverted function | off | on; default: off | Inverts the selected condition type. Makes the condition true if the time/date is outside the specified interval. |
Interval | off | on; default: off | Switches between a specific value and a time interval. |
Weekday | weekday; default: Monday | Specifies weekday at which the action can occur. |
Start weekday | weekday; default: Monday | Specifies starting weekday of the interval at which the action can occur. |
End weekday | weekday; default: Monday | Specifies ending weekday of the interval at which the action can occur. |
Month day
Field | Value | Description |
---|---|---|
Condition type | Month day | A type of condition. |
Month override | off | on; default: off | If the option is selected and the specified day is not in the month then the condition uses the last day of the month. |
Interval | off | on; default: off | Switches between a specific value and a time interval. |
Day of the month | integer [1..31]; default: none | Specifies day of the month at which the action can occur. |
Start day of the month | integer [1..31]; default: none | Specifies starting day of the interval of the month at which the action can occur. |
End day of the month | integer [1..31]; default: none | Specifies ending day of the interval of the month at which the action can occur. |
Year
Field | Value | Description |
---|---|---|
Condition type | Year | A type of condition. |
Inverted function | off | on; default: off | Inverts the selected condition type. Makes the condition true if the time/date is outside the specified interval. |
Interval | off | on; default: off | Switches between a specific value and a time interval. |
Day of the year | integer [1..366]; default: none | Specifies day of the year at which the action can occur. |
Start day of the year | integer [1..366]; default: none | Specifies starting day of the interval of the year at which the action can occur. |
End day of the year | integer [1..366]; default: none | Specifies ending day of the interval of the year at which the action can occur. |
[[Category:{{{name}}} Services section]]