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 RUTX11 devices.
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 “Basic” button under “Mode”, which is located at the top-right corner of the WebUI.
The router’s input/output pins can be found inside the power socket:
The electric characteristics for the input and output pins are as follows:
The Status page displays the current states of the device input and output:
You can invert Input pin by clicking on slider in Inversion column and switch Output pin state by clicking on slider in State column.
You can also obtain the status of the input or output from the command line. List of ubus possible values in RUTX11 devices:
Call command ubus call value status :
root@Teltonika-RUTX11:~# ubus call ioman.gpio.dout1 status
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:
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:
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.
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.
The Io juggler page is used create automated actions based on Input state and conditions.
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.
You can find explanation about fields in the table below this illustration.
The Actions section lets you manage your created Actions for IO Juggler inputs. The figure below is an example of Actions section.
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.
Note: this table has coloring scheme to indicate which fields can be seen with different configuration.
The Conditions section lets you manage your created Conditions for IO Juggler Actions. The figure below is an example of Conditions section.
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.
Your email address will not be published. Required fields are marked *
Save my name, email, and website in this browser for the next time I comment.