Jump to content

Template:Networking rutx manual input output: Difference between revisions

no edit summary
No edit summary
No edit summary
 
(14 intermediate revisions by the same user not shown)
Line 20: Line 20:
         <ul>
         <ul>
             <li>logic low: 0 - 5 V</li>
             <li>logic low: 0 - 5 V</li>
             <li>logic high: 8 - 40 V></li>
             <li>logic high: 8 - 40 V</li>
         </ul>
         </ul>
     </li>
     </li>
Line 28: Line 28:
==Status==
==Status==


The <b>Status</b> page displays the current states of the input and the output:
The <b>Status</b> page displays the current states of the router's input and output:


[[File:{{{file_status}}}]]
[[File:{{{file_status}}}]]
Line 75: Line 75:
  }
  }


Set the number following after "value": to indicate the new state of the output (possible values are 0 and 1).
Set the number following after <i>"value":</i> to indicate the new state of the output (possible values are 0 and 1).


==Input==
==Input==
Line 107: Line 107:
         <td>Trigger</td>
         <td>Trigger</td>
         <td>Input open | Input shorted | Both; default: <b>Input open</b></td>
         <td>Input open | Input shorted | Both; default: <b>Input open</b></td>
         <td>Selects which input state triggers the rule.</td>
         <td>Selects which input state will trigger the rule.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Action</td>
         <td>Action</td>
         <td>Send SMS | Change profile | Reboot | Activate output; default: <b>Send SMS</b></td>
         <td>{{#ifeq:{{{modem}}}|1|Send SMS {{!}} |}} Change profile | Reboot | Activate output; default: <b>Send SMS</b></td>
         <td>The action that will be taken when the rule is triggered:
         <td>The action that will be taken when the rule is triggered.
             <ul>
             <ul>
                <li><b>Send SMS</b> - sends an SMS message with user specified text to the specified recipient(s).</li>
{{#ifeq:{{{modem}}}|1|{{Template:Networking_rutx_manual_input_output_input_input_rules_modem}}|}}
                 <li><b>Change profile</b> - switches to another configuration profile. At least one configuration profile has to be created before this can be used. You can create configuration profiles from the <b>System → [[{{{name}}} Profiles|Profiles]]</b> page.</li>
                 <li><b>Change profile</b> - switches to another configuration profile. At least one configuration profile has to be created before this can be used. You can create configuration profiles from the <b>System → [[{{{name}}} Profiles|Profiles]]</b> page.</li>
                 <li><b>Reboot</b> - reboots the device when a specified amount of time passes after the trigger.</li>
                 <li><b>Reboot</b> - reboots the device when a specified amount of time passes after the trigger.</li>
Line 133: Line 133:
===On/Off===
===On/Off===
----
----
The ON/OFF section is used to turn the output on or off, but it doesn't save the state permanently, meaning that after a reboot the state will revert back to its default value.
The On/Off section is used to turn the output on or off, but it doesn't save the state permanently, meaning that after a reboot the state will revert back to its default value.


[[File:{{{file_output_on_off}}}]]
[[File:{{{file_output_on_off}}}]]
Line 139: Line 139:
===Post/Get configuration===
===Post/Get configuration===
----
----
Enabling <b>Post/Get</b> will allow you to send HTTP POST/GET requests to the router that control the state of the output.
Enabling <b>Post/Get</b> will allow you to send HTTP POST/GET requests to the router that control the state of the output. The figure below is an example of the Post/Get configuration section an the table below provides information on the fields contained in that section:


[[File:{{{file_output_post_get}}}]]
[[File:{{{file_output_post_get}}}]]
Line 170: Line 170:
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.
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 table containing syntax examples of this usage:  
Below is a table containing syntax examples of this usage:  


<table class="nd-othertables_2">
<table class="nd-othertables_2">
     <tr>
     <tr>
         <th style="width: 500px">ACTION</th>
         <th style="width: 500px">Action</th>
       <th style="width: 900px">POST/GET URL EXAMPLE</th>
       <th style="width: 900px">POST/GET URL</th>
     </tr>
     </tr>
     <tr>
     <tr>
Line 236: Line 236:
       <td>Output</td>
       <td>Output</td>
       <td>Digital output (pin2); default: <b>Digital output (pin2)</b></td>
       <td>Digital output (pin2); default: <b>Digital output (pin2)</b></td>
       <td>Output that will be affected by the rule.</td>
       <td>The output pin that will be be effected by the rule.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 251: Line 251:
     <td>Mode</td>
     <td>Mode</td>
         <td>Fixed | Interval; default: <b>Fixed</b></td>
         <td>Fixed | Interval; default: <b>Fixed</b></td>
         <td>
         <td>When the rule will be triggered.
             <ul>
             <ul>
                 <li><b>Fixed</b> - triggers the specified action on the specified day(s), hour and minute. For example, every Sunday at 8:30 AM.</li>
                 <li><b>Fixed</b> - triggers the specified action on the specified day(s), hour and minute. For example, every Sunday at 8:30 AM.</li>
                 <li><b>Interval</b> - performs the action periodically. For example, every 1 hour.</li>
                 <li><b>Interval</b> - performs the action at an interval. For example, every 1 hour during Mondays.</li>
             </ul>
             </ul>
         </td>
         </td>
Line 262: Line 262:
===Scheduler===
===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.
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.


[[File:{{{file_output_scheduler}}}]]
[[File:{{{file_output_scheduler}}}]]


[[Category:{{{name}}} WebUI]]
[[Category:{{{name}}} Services section]]