Line 438: |
Line 438: |
| </ol> | | </ol> |
| ---- | | ---- |
− | Selecting conditions is optional. If there are set or configured I/O Juggler conditions, the operating sequence is as such: | + | You can specify multiple actions and multiple conditions for any I/O Juggler rule. Selecting conditions is optional. If there are no set or configured I/O Juggler conditions, the operating sequence is as such: |
| | | |
| [[File:Networking_rutos_manual_input_output_io_juggler_scheme_mobile_{{{mobile}}}.png]] | | [[File:Networking_rutos_manual_input_output_io_juggler_scheme_mobile_{{{mobile}}}.png]] |
Line 452: |
Line 452: |
| ====Input==== | | ====Input==== |
| ---- | | ---- |
− | You can find explanation about fields in the table below this illustration.
| + | The <b>Input</b> is used to create Input Rules. An Input Rule is triggered by a user-specified input state change. When this trigger occurs, the device executes a specified command if certain specified conditions are met (conditions are optional). |
| | | |
− | [[File:Networking_rutx_manual_input_output_iojuggler_general_modify_v1.png]] | + | The Input list is empty by default. To create a new Input Rule, look to the Add Input section at the bottom of the page; select an input and click the 'Add' button: |
| + | |
| + | [[File:Networking_rutos_manual_input_output_io_juggler_general_input_add_button_juggler_input_{{{juggler_input}}}.png|border|class=tlt-border]] |
| + | |
| + | After this you will be redirected to the configuration page for the newly added Rule, which should look similar to this: |
| + | |
| + | [[File:Networking_rutos_manual_input_output_io_juggler_general_input_configuration_juggler_input_{{{juggler_input}}}.png|border|class=tlt-border]] |
| | | |
| <table class="nd-mantable"> | | <table class="nd-mantable"> |
Line 464: |
Line 470: |
| <tr> | | <tr> |
| <td>Enabled</td> | | <td>Enabled</td> |
− | <td>off {{!}} on; default: <b>off</b> </td> | + | <td>off | on; default: <b>off</b> </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>Trigger interval</td> | | <td>Trigger interval</td> |
− | <td>positive integer; default: <b>none</b></td> | + | <td>integer [0..99999999]; default: <b>1</b></td> |
− | <td>Specifies what is the shortest amount of seconds between triggers.</td> | + | <td>The shortest amount of time (in seconds) between two triggers. If the input is triggered more than once in a time period shorter than the value specified in this field, the device will react to the first trigger.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>Trigger</td> | | <td>Trigger</td> |
− | <td>Rising {{!}} Falling {{!}} Both; default: <b>Rising</b> </td> | + | <td>Rising | Falling | Both; default: <b>Rising</b> </td> |
− | <td>Specifies on which trigger state this rule will be activated.</td> | + | <td>Input state change that will trigger this rule.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>Add actions</td> | | <td>Add actions</td> |
− | <td>actions; default: <b>none</b> </td> | + | <td>i/o juggler action(s); default: <b>none</b> </td> |
− | <td>Specifies actions which have to be met for rule to be executed. Actions are optional.</td> | + | <td>Actions that will be executed by this rule when the specified trigger and conditions (optional) occur.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>Add conditions</td> | | <td>Add conditions</td> |
− | <td>conditions; default: <b>none</b> </td> | + | <td>i/o juggler conditions; default: <b>none</b> </td> |
− | <td>Specifies conditions which have to be met for action to occur. Conditions are optional.</td> | + | <td>Conditions that have to be met for the rule to take action. Conditions are optional.</td> |
| </tr> | | </tr> |
| </table> | | </table> |
Line 491: |
Line 497: |
| ===Actions=== | | ===Actions=== |
| ---- | | ---- |
| + | The <b>Actions</b> section is used to manage existing and create new Actions that be executed by the I/O Juggler Rules. The figure below is an example of the Actions section, which is empty by default. |
| + | |
| + | [[File:Networking_rutos_manual_input_output_io_juggler_actions_actions.png|border|class=tlt-border]] |
| + | |
| + | To create a new Action, look to the Add an Action section at the bottom of the page; enter a custom name, select an action type and click the 'Add' button: |
| + | |
| + | [[File:Networking_rutos_manual_input_output_io_juggler_actions_add_button.png|border|class=tlt-border]] |
| | | |
− | The <b>Actions</b> section lets you manage your created Actions for I/O Juggler inputs.
| + | After this you will be redirected to the configuration page for the newly added Action, which should look similar to this (example for the 'Reboot' action only): |
− | The figure below is an example of Actions section.
| |
| | | |
− | [[File:Networking_rutx_manual_input_output_iojuggler_actions_v1.png]] | + | [[File:Networking_rutos_manual_input_output_io_juggler_actions_configuration_reboot.png|border|class=tlt-border]] |
| | | |
| ====Modify action==== | | ====Modify action==== |