0
edits
Changes
Template:Networking rutos manual input output (view source)
Revision as of 16:57, 6 May 2020
, 16:57, 6 May 2020change template
{{Template:Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.03
| series = {{{series}}}
}}
__TOC__
==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. 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>
<li>Digital non-isolated input:
<ul>
<li>logic low: 0 - 5 V</li>
<li>logic high: 8 - 40 V</li>
</ul>
</li>
<li>Digital open collector output: 30 V, 300 mA</li>
</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>
<li>Digital non-isolated input:
<ul>
<li>logic low: 0 - 5 V</li>
<li>logic high: 8 - 40 V</li>
</ul>
</li>
<li>Digital open collector output: 30 V, 300 mA</li>
</ul>
}}
| TRB2 =
|
}}
==Status==
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]]
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===
----
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==
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:Networking_rutx_manual_input_output_post_get_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</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 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">
<tr>
<th style="width: 500px">Action</th>
<th style="width: 900px">POST/GET URL</th>
</tr>
<tr>
<td>Turn Output state to high</td>
<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>
<td>Turn Output state to low after 5 seconds for 3 seconds</td>
<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>
</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>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.
==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===
----
[[File:Networking_rutx_manual_input_output_iojuggler_general_v1.png]]
====Modify Input configuration====
----
[[File:Networking_rutx_manual_input_output_iojuggler_general_modify_v1.png]]
===Actions===
----
[[File:Networking_rutx_manual_input_output_iojuggler_actions_v1.png]]
====Modify action====
----
[[File:Networking_rutx_manual_input_output_iojuggler_actions_modify_v1.png]]
===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====
----
Table below provides information on the fields contained in this section:
[[File:Networking_rutx_manual_input_output_iojuggler_conditions_modify_v1.png]]
[[Category:{{{name}}} Services section]]
| fw_version = {{{series}}}_R_00.02.03
| series = {{{series}}}
}}
__TOC__
==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. 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>
<li>Digital non-isolated input:
<ul>
<li>logic low: 0 - 5 V</li>
<li>logic high: 8 - 40 V</li>
</ul>
</li>
<li>Digital open collector output: 30 V, 300 mA</li>
</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>
<li>Digital non-isolated input:
<ul>
<li>logic low: 0 - 5 V</li>
<li>logic high: 8 - 40 V</li>
</ul>
</li>
<li>Digital open collector output: 30 V, 300 mA</li>
</ul>
}}
| TRB2 =
|
}}
==Status==
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]]
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===
----
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==
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:Networking_rutx_manual_input_output_post_get_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</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 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">
<tr>
<th style="width: 500px">Action</th>
<th style="width: 900px">POST/GET URL</th>
</tr>
<tr>
<td>Turn Output state to high</td>
<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>
<td>Turn Output state to low after 5 seconds for 3 seconds</td>
<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>
</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>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.
==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===
----
[[File:Networking_rutx_manual_input_output_iojuggler_general_v1.png]]
====Modify Input configuration====
----
[[File:Networking_rutx_manual_input_output_iojuggler_general_modify_v1.png]]
===Actions===
----
[[File:Networking_rutx_manual_input_output_iojuggler_actions_v1.png]]
====Modify action====
----
[[File:Networking_rutx_manual_input_output_iojuggler_actions_modify_v1.png]]
===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====
----
Table below provides information on the fields contained in this section:
[[File:Networking_rutx_manual_input_output_iojuggler_conditions_modify_v1.png]]
[[Category:{{{name}}} Services section]]
