Changes

no edit summary
Line 1: Line 1:  
{{Template:Networking_rutos_manual_fw_disclosure
 
{{Template:Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.05.1
+
| fw_version = {{{series}}}{{#ifeq:{{{name}}}|RUT241|M|}}_R_00.07.01{{#ifeq:{{{series}}}|RUT9|.1|}}
 
| series    = {{{series}}}
 
| series    = {{{series}}}
 
}}
 
}}
 +
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Input/Output (legacy WebUI)|click here]]</b> for the old style WebUI (FW version RUT9XX_R_00.06.08.5 and earlier) user manual page.</i>
 +
<p style="color:red">Warning: From 7.0 version I/O parameters and controls have changed compared to RUT9XX_R_00.06.08.3 and earlier legacy versions.</p>|}}
 +
{{#ifeq: {{{series}}} | RUT2 |
 +
{{#switch: {{{name}}}
 +
  | RUT241 =
 +
  | #default =
 +
<br><i><b>Note</b>: <b>[[{{{name}}} System (legacy WebUI)|click here]]</b> for the old style WebUI (FW version RUT2XX_R_00.01.14.4 and earlier) user manual page.</i>}}
 +
<p style="color:red">Warning: From 7.1 version I/O parameters and controls have changed compared to RUT2XX_R_00.01.14.1 and earlier legacy versions.</p>|}}
 
==Summary==
 
==Summary==
   Line 14: Line 22:  
==Physical characteristics and I/O pin mapping==
 
==Physical characteristics and I/O pin mapping==
   −
Electrical characteristics and I/O pin mapping information is presented below.
+
Electrical characteristics and I/O pin mapping information are presented below.
    
{{Template:Networking_rutos_manual_input_output_pinout
 
{{Template:Networking_rutos_manual_input_output_pinout
Line 21: Line 29:  
| input_volts    = {{{input_volts}}}
 
| input_volts    = {{{input_volts}}}
 
}}{{#ifeq: {{{name}}} | TRB141 |
 
}}{{#ifeq: {{{name}}} | TRB141 |
===Input/Output Connector Pinout===
+
<h3>Input/Output Connector Pinout</h3>
 
----
 
----
 
[[File:Networking_trb141_manual_input_output_input_output_connector_pinout.png]]
 
[[File:Networking_trb141_manual_input_output_input_output_connector_pinout.png]]
Line 33: Line 41:  
     </li>
 
     </li>
 
     <li><b>NC<sub>1</sub></b>, <b>C<sub>1</sub></b> & <b>NO<sub>1</sub></b> - Normally Closed, Common and Normally Open contacts of the internal Non-Latching Relay respectively.<br>Maximum relay ratings: 0.5 A at 60 VDC/70 VAC, 1 A at 30 VDC/VAC.</li>
 
     <li><b>NC<sub>1</sub></b>, <b>C<sub>1</sub></b> & <b>NO<sub>1</sub></b> - Normally Closed, Common and Normally Open contacts of the internal Non-Latching Relay respectively.<br>Maximum relay ratings: 0.5 A at 60 VDC/70 VAC, 1 A at 30 VDC/VAC.</li>
     <li><b>NC<sub>2</sub></b>, <b>C<sub>2</sub></b> & <b>NO<sub>2</sub></b> - Normally Closed, Common and Normally Open contacts of the internal Latching Relay respectively.<b>Maximum relay ratings: 0.8 A at 70 VDC, 0.9 A at 70 VAC, 2 A at 30 VDC/VAC.</li>
+
     <li><b>NC<sub>2</sub></b>, <b>C<sub>2</sub></b> & <b>NO<sub>2</sub></b> - Normally Closed, Common and Normally Open contacts of the internal Latching Relay respectively.<br>Maximum relay ratings: 0.8 A at 70 VDC, 0.9 A at 70 VAC, 2 A at 30 VDC/VAC.</li>
     <li><b>A</b> - ADC input. Analog voltage range: 0-30 V. The input can be configured for 4-20 mA sensor protocol as current measurement of 0-30 mA.</li>
+
     <li><b>A</b> - ADC input. Analog voltage range: 0-30 V. The input can be configured for 4-20 mA sensor protocol as current measurement (ACL) of 0-30 mA.</li>
 
     <li><b>l</b> and <b>⏚</b> - isolated input contacts.
 
     <li><b>l</b> and <b>⏚</b> - isolated input contacts.
 
         <ul>
 
         <ul>
Line 46: Line 54:  
     <li><b>⏚</b> - GND contact.</li>
 
     <li><b>⏚</b> - GND contact.</li>
 
</ul>|}}
 
</ul>|}}
 +
 
==Status==
 
==Status==
    
The <b>Status</b> page displays the current states of the device's input and output pins:
 
The <b>Status</b> page displays the current states of the device's input and output pins:
   −
{{#ifeq: {{{name}}} | TRB141  
+
{{#switch: {{{name}}}  
  | [[File:Networking_trb141_manual_input_output_status.png|border|class=tlt-border]]
+
| TRB141 = [[File:Networking_trb141_manual_input_output_status.png|border|class=tlt-border]]
  | [[File:Networking_{{lc:{{{series}}}}}_manual_input_output_status.png|border|class=tlt-border]]
+
| RUT950 = [[File:Networking_RUT950_manual_input_output_status.png|border|class=tlt-border]]
 +
| RUT955 = [[File:Networking_RUT955_manual_input_output_status.png|border|class=tlt-border]]
 +
| [[File:Networking_{{lc:{{{series}}}}}_manual_input_output_status.png|border|class=tlt-border]]
 
}}
 
}}
   Line 61: Line 72:  
You can also obtain the status of input and output pins via the command line (CLI or SSH). List of possible ubus values in {{{name}}} devices:
 
You can also obtain the status of input and output pins via the command line (CLI or SSH). List of possible ubus values in {{{name}}} devices:
   −
{{#ifeq: {{{name}}} | TRB141  
+
{{#switch: {{{series}}}
  | {{Template:Networking_trb141_manual_input_output_status}}
+
| TRB1 ={{#ifeq:{{{name}}}
  | {{Template:Networking_{{lc:{{{series}}}}}_manual_input_output_status|name={{{name}}}}}
+
  | TRB141 | {{Template:Networking_trb141_manual_input_output_status}}
 +
  | {{Template:Networking_{{lc:{{{series}}}}}_manual_input_output_status|name={{{name}}}}}
 +
  }}
 +
| #default = {{Template:Networking_{{lc:{{{series}}}}}_manual_input_output_status|name={{{name}}}}}
 
}}
 
}}
    
==Post/Get==
 
==Post/Get==
   −
Enabling <b>Post/Get</b> provides the possibility to control the state of an output via HTTP POST/GET requests. The figure below is an example of the Auth Settings section of the Post/Get page. It is used to turn Post/Get on or off and to set authentication parameters.
+
Enabling <b>Post/Get</b> provides the possibility to control the state of an output via HTTP POST/GET requests. The figure below is an example of the Auth Settings section of the Post/Get page. It is used to turn Post/Get requests on or off and to set authentication parameters.
    
[[File:Networking_rutos_manual_input_output_post_get_auth_settings.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_input_output_post_get_auth_settings.png|border|class=tlt-border]]
Line 102: Line 116:  
===Post/Get examples===
 
===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.
+
Use a web browser or any other compatible software to send HTTP POST/GET requests to the device.
    
Below is a table containing syntax examples of this usage:  
 
Below is a table containing syntax examples of this usage:  
Line 122: Line 136:  
     <tr>
 
     <tr>
 
         <td>Change Configurable Input/Output with pin3 to Output</td>
 
         <td>Change Configurable Input/Output with pin3 to Output</td>
         <td><nowiki>http://192.168.</nowiki>{{#ifeq:{{{series}}}|TRB1|2|1}}.1/cgi-bin/<span style="color: #0054a6;"><b>io_type</b></span><nowiki>?username=user1&password=user1&</nowiki><span style="color: #0054a6;"><b>pin=dio1</b></span><span style="color: #3232ff;"><b><nowiki>&type=out</nowiki></b></span></td>
+
         <td><nowiki>http://192.168.</nowiki>{{#ifeq:{{{series}}}|TRB1|2|1}}.1/cgi-bin/<span style="color: #0054a6;"><b>io_type</b></span><nowiki>?username=user1&password=user1&</nowiki><span style="color: #0054a6;"><b>pin=dio0</b></span><span style="color: #3232ff;"><b><nowiki>&type=out</nowiki></b></span></td>
 
     </tr>
 
     </tr>
 
|
 
|
Line 162: Line 176:  
==Scheduler==
 
==Scheduler==
   −
The output <b>Scheduler</b> can be used to configure a timetable of when an output should be turned on or off, based on days of the week and hours of the day. Below is an example of the Scheduler section.
+
The output <b>Scheduler</b> can be used to configure a timetable of when an output should be turned on or off, based on days of the week or month and hours of the day. The General Configuration section is used to turn the Output Scheduler on or off.
 +
 
 +
[[File:Networking_rutos_manual_input_output_scheduler_general_configuration.png|border|class=tlt-border]]
 +
 
 +
The Scheduler is configured in the form of <b>Instances</b>. A Scheduler Instance defines a time interval during which the state of an output associated with the instance will be set to "High". The Output Scheduler Instances list is empty by default. Click the 'Add' button in order to create a new Scheduler Instance:
 +
 
 +
[[File:Networking_rutos_manual_input_output_scheduler_add_button.png|border|class=tlt-border]]
 +
 
 +
After this you should be redirected to the configuration page for the newly added Instance which should look similar to this:
   −
[[File:Networking_rutos_manual_input_output_scheduler_configure_scheduler_configurableio_{{{configurableio}}}.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_input_output_scheduler_instance_configuration_configurableio_{{{configurableio}}}.png|border|class=tlt-border]]
   −
Each field represents a day of the week and an hour of the day. The Scheduler table itself is interactive; click on different fields to set the state of an output for a specific window of time. For example:
+
<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 the Scheduler Instance on or off.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Pin</td>
 +
      <td>output pin; default: <b>{{#ifeq:{{{configurableio}}}|1|Configurable Input/Output (2)|Output (4)}}</b></td>
 +
      <td>Output pin. The state of the selected output will be set to "High" during the time interval defined in the fields below.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Interval Type</td>
 +
      <td>Weekdays | <span style="color: red;">Month Days</span>; default: <b>Weekdays</b></td>
 +
      <td>Selects the interval type for scheduler to use.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Start Day</td>
 +
      <td>[Monday..Sunday] | [1..31]; default: <b>Monday | 1</b></td>
 +
      <td>The day that marks the start of the time interval.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Start Time</td>
 +
      <td>hh:mm ([00..23]:[00..59]); default: <b>12:00</b></td>
 +
      <td>The hour and minute that mark the start of the time interval.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>End Day</td>
 +
      <td>[Monday..Sunday] | [1..31]; default: <b>Tuesday | 1</b></td>
 +
      <td>The day that marks the end of the time interval.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>End Time</td>
 +
      <td>hh:mm ([00..23]:[00..59]); default: <b>12:00</b></td>
 +
      <td>The hour and minute that mark the end of the time interval.</td>
 +
    </tr>
 +
    <tr>
 +
      <td><span style="color: red;">Force Last Day</span></td>
 +
      <td>off | on; default: <b>off</b></td>
 +
      <td>Forces intervals to accept last day of month as a valid option if selected day does not exist during ongoing month. This field becomes visible only when 'Interval Type' is set to <i>Month Days</i>.</td>
 +
    </tr>
 +
</table>
   −
[[File:Networking_rutos_manual_input_output_scheduler_configure_scheduler_example_configurableio_{{{configurableio}}}.png|border|class=tlt-border]]
+
A Scheduler Instance will not work unless you turn both the the Scheduler service and the individual instance on:
   −
The Scheduler is turned off by default. To turn it on set the 'Enable' slider to "on".
+
[[File:Networking_rutos_manual_input_output_scheduler_on_off_slider_configurableio_{{{configurableio}}}.png|border|class=tlt-border]]
    
==I/O Juggler==
 
==I/O Juggler==
Line 399: Line 467:  
====HTTP====
 
====HTTP====
 
----
 
----
Executes at HTTP Post/Get action.
+
Executes a HTTP POST/GET request.
    
[[File:Networking_rutos_manual_input_output_io_juggler_actions_http.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_input_output_io_juggler_actions_http.png|border|class=tlt-border]]

Navigation menu