Select Page

RUTX11 Input/Output

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 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.

Networking rutx manual webui basic advanced mode v1.gif

Characteristics #

The router’s input/output pins can be found inside the power socket:

Networking rutx manual input output status pinout v1.png

The electric characteristics for the input and output pins are as follows:

  • Digital non-isolated input:
    • logic low: 0 – 5 V
    • logic high: 8 – 40 V
  • Digital open collector output: 30 V, 300 mA

Status #

The Status page displays the current states of the device input and output:

Networking rutx manual input output status v2.png

You can invert Input pin by clicking on slider 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 RUTX11 devices:

ioman.gpio.din1
ioman.gpio.dout1

Call command ubus call value status :

root@Teltonika-RUTX11:~# 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:

Networking rutx manual input output post get v1.png
FieldValueDescription
Enableoff | on; default: offTurns Post/Get on or off.
Usernamestring; default: noneUsername used for authentication in POST/GET queries.
Passwordstring; default: nonePassword 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:

ActionPOST/GET URL
Turn Output state to highhttp://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 secondshttp://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 – device 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.
  • state – turn Output on or off.
  • 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.

Networking rutx manual input output output scheduler v2.png

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.

Networking rutx manual input output iojuggler general v1.png

Modify Input configuration #

You can find explanation about fields in the table below this illustration.

Networking rutx manual input output iojuggler general modify v1.png
FieldValueDescription
Enabledoff | on; default: offChanges current profile to specified one when action triggers.
Trigger intervalpositive integer; default: noneSpecifies what is the shortest amount of seconds between triggers.
TriggerRising | Falling | Both; default: RisingSpecifies on which trigger state this rule will be activated.
Add actionsactions; default: noneSpecifies actions which have to be met for rule to be executed. Actions are optional.
Add conditionsconditions; default: noneSpecifies 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.

Networking rutx manual input output iojuggler actions v1.png

Modify action #

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 #
FieldValueDescription
TypeProfileChanges current profile to specified one when action triggers.
Execution delaypositive integer; default: noneHow many seconds will pass before the action is excecuted after it’s triggered.
Profileprofile; default: defaultChoose a profile that will be applied when the action triggers.
Add conditionsconditions; default: noneSpecifies conditions which have to be met for action to occur. Conditions are optional.
Email #
FieldValueDescription
TypeEmailSends email when action triggers.
Subjectstring; default: noneSubject of email.
Text messagestring; default: noneText 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 delaypositive integer; default: noneHow many seconds will pass before the action is excecuted after it’s triggered.
Email useremail user; default: noneConfigured email user.
Recipient’s email addressstring; default: noneEmail receiver(s).
Add conditionsconditions; default: noneSpecifies conditions which have to be met for action to occur. Conditions are optional.
SMS #
FieldValueDescription
TypeSMSSends sms when action triggers.
Text messagestring; default: noneText 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.
Execution delaypositive integer; default: noneHow many seconds will pass before the action is excecuted after it’s triggered.
RecipientsSingle number | Group; default: Single numberHow many recipients will get the message.
Single number: Recipient’s phone numbernumber; default: noneSMS receiver.
Group: Phone groupphone group; default: noneSMS receivers.
Add conditionsconditions; default: noneSpecifies conditions which have to be met for action to occur. Conditions are optional.

Note: this table has coloring scheme to indicate which fields can be seen with different configuration.

Output #
FieldValueDescription
TypeOutputChanges Output state when action triggers.
Execution delaypositive integer; default: noneHow many seconds will pass before the action is excecuted after it’s triggered.
Controloutput; default: Output(4)Specifies the output of which the state will be changed.
Revertinteger; default: 0After how many seconds the state will revert. If left 0 or empty the state will not revert.
Maintainoff | on; default: onMaintain this IO state after reboot.
Invertoff | on; default: offOn action inverts pin state.
State copyingoff | on; default: offCopies the state from selected input to selected output.
StateHigh | Low; default: HighSpecifies what state the output pin will be set to.
Add conditionsconditions; default: noneSpecifies conditions which have to be met for action to occur. Conditions are optional.
HTTP #
FieldValueDescription
TypeHTTPSends HTTP request when action triggers.
Execution delaypositive integer; default: noneHow many seconds will pass before the action is excecuted after it’s triggered.
MethodGet | Post; default: GetSpecifies the output of which the state will be changed.
URLstring; default: noneURL to send request to.
Verifyoff | on; default: offVerifies the validity of certificates, only works for https.
Parametersstring; default: noneParameters 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 conditionsconditions; default: noneSpecifies conditions which have to be met for action to occur. Conditions are optional.
Script #
FieldValueDescription
TypeScriptRuns script when action triggers.
Execution delaypositive integer; default: noneHow many seconds will pass before the action is excecuted after it’s triggered.
Specify pathUpload a script | Specify path; default: Upload a criptSelection to upload a script or specify its absolute path in device.
Upload a script: Custom script-(interactive button)Shows file upload window on click.
Specify path: Script filestring; default: noneAbsolute path to script file in device.
Argumentsstring; default: noneOptional arguments which can be provided for the script. You can include device information with values given below this input field.
Add conditionsconditions; default: noneSpecifies conditions which have to be met for action to occur. Conditions are optional.

Note: this table has coloring scheme to indicate which fields can be seen with different configuration.

Reboot #
FieldValueDescription
TypeRebootReboots device when action triggers.
Execution delaypositive integer; default: noneHow many seconds will pass before the action is excecuted after it’s triggered.
Add conditionsconditions; default: noneSpecifies conditions which have to be met for action to occur. Conditions are optional.
Change sim #
FieldValueDescription
TypeChange simChanges active sim card when action triggers.
Execution delaypositive integer; default: noneHow many seconds will pass before the action is excecuted after it’s triggered.
Flipoff | on; default: offSwitches to a different sim card.
Off: TargetSim1 | Sim2; default: Sim1Switches to a selected sim card.
Add conditionsconditions; default: noneSpecifies conditions which have to be met for action to occur. Conditions are optional.

Note: this table has coloring scheme to indicate which fields can be seen with different configuration.

Conditions #

The Conditions section lets you manage your created Conditions for IO Juggler Actions. The figure below is an example of Conditions section.

Networking rutx manual input output iojuggler conditions v1.png

Modify condition #

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 #
FieldValueDescription
Condition typeBoolean groupA type of condition.
Boolean typeAND | NAND | OR | NOR; default: ANDType of boolean condition.
Add conditionsconditions; default: noneSpecifies conditions which have to be met for action to occur. Conditions are optional.
I/O #
FieldValueDescription
Condition typeI/OA type of condition.
I/Oinputs/outputs; default: Output(4)Specifies the I/O to which the condition is listening to.
StateHigh | Low; default: HighSpecifies in what state the pin has to be.
Minute #
FieldValueDescription
Condition typeMinuteA type of condition.
Inverted functionoff | on; default: offInverts the selected condition type. Makes the condition true if the time/date is outside the specified interval.
Intervaloff | on; default: offSwitches between a specific value and a time interval.
Off: Minuteinteger [0..59]; default: noneSpecifies minute at which the action can occur.
On: Start minuteinteger [0..59]; default: noneSpecifies starting minute of the interval at which the action can occur.
On: End minuteinteger [0..59]; default: noneSpecifies ending minute of the interval at which the action can occur.

Note: this table has coloring scheme to indicate which fields can be seen with different configuration.

Hour #
FieldValueDescription
Condition typeHourA type of condition.
Inverted functionoff | on; default: offInverts the selected condition type. Makes the condition true if the time/date is outside the specified interval.
Intervaloff | on; default: offSwitches between a specific value and a time interval.
Off: Hourinteger [0..59]; default: noneSpecifies hour at which the action can occur.
On: Start hourinteger [0..59]; default: noneSpecifies starting hour of the interval at which the action can occur.
On: End hourinteger [0..59]; default: noneSpecifies ending hour of the interval at which the action can occur.

Note: this table has coloring scheme to indicate which fields can be seen with different configuration.

Weekday #
FieldValueDescription
Condition typeWeekdayA type of condition.
Inverted functionoff | on; default: offInverts the selected condition type. Makes the condition true if the time/date is outside the specified interval.
Intervaloff | on; default: offSwitches between a specific value and a time interval.
Off: Weekdayweekday; default: MondaySpecifies weekday at which the action can occur.
On: Start weekdayweekday; default: MondaySpecifies starting weekday of the interval at which the action can occur.
On: End weekdayweekday; default: MondaySpecifies ending weekday of the interval at which the action can occur.

Note: this table has coloring scheme to indicate which fields can be seen with different configuration.

Month day #
FieldValueDescription
Condition typeMonth dayA type of condition.
Month overrideoff | on; default: offIf the option is selected and the specified day is not in the month then the condition uses the last day of the month.
Intervaloff | on; default: offSwitches between a specific value and a time interval.
Off: Day of the monthinteger [1..31]; default: noneSpecifies day of the month at which the action can occur.
On: Start day of the monthinteger [1..31]; default: noneSpecifies starting day of the interval of the month at which the action can occur.
On: End day of the monthinteger [1..31]; default: noneSpecifies ending day of the interval of the month at which the action can occur.

Note: this table has coloring scheme to indicate which fields can be seen with different configuration.

Year #
FieldValueDescription
Condition typeYearA type of condition.
Inverted functionoff | on; default: offInverts the selected condition type. Makes the condition true if the time/date is outside the specified interval.
Intervaloff | on; default: offSwitches between a specific value and a time interval.
Off: Day of the yearinteger [1..366]; default: noneSpecifies day of the year at which the action can occur.
On: Start day of the yearinteger [1..366]; default: noneSpecifies starting day of the interval of the year at which the action can occur.
On: End day of the yearinteger [1..366]; default: noneSpecifies ending day of the interval of the year at which the action can occur.

Submit a Comment

Your email address will not be published. Required fields are marked *