Changes

m
Reverted edits by Tomas (talk) to last revision by Lukasmar
Line 1: Line 1:  
<!-- Template uses {{{name}}}, {{{series}}}  -->
 
<!-- Template uses {{{name}}}, {{{series}}}  -->
{{Template:Networking_rutos_manual_fw_disclosure
+
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.05
+
| fw_version = {{{series}}}_R_00.07.00
 
| series    = {{{series}}}
 
| series    = {{{series}}}
 
}}
 
}}
 
+
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} GPS (legacy WebUI)|click here]]</b> for the old style WebUI (FW version RUT9XX_R_00.06.08.3 and earlier) user manual page.</i>|}}
 
==Summary==
 
==Summary==
   Line 82: Line 82:  
     <tr>
 
     <tr>
 
         <td>Hostname</td>
 
         <td>Hostname</td>
         <td>ip | host; default: '''192.168.1.5'''</td>
+
         <td>ip | host; default: '''none'''</td>
 
         <td>IP address or hostname of the server to which NMEA data will be forwarded.</td>
 
         <td>IP address or hostname of the server to which NMEA data will be forwarded.</td>
 
     </tr>
 
     </tr>
Line 260: Line 260:  
     <tr>
 
     <tr>
 
         <td>URL</td>
 
         <td>URL</td>
         <td>string; default: '''192.168.1.5'''</td>
+
         <td>url string; default: <b>192.168.1.5</b></td>
 
         <td>URL of remote server.</td>
 
         <td>URL of remote server.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Delay</td>
 +
        <td>integer; default: <b>5</b></td>
 +
        <td>Time interval in seconds between sending packages.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 268: Line 273:  
----
 
----
 
The <b>TAVL settings</b> section is used to select which data will be sent to the TAVL server:
 
The <b>TAVL settings</b> section is used to select which data will be sent to the TAVL server:
 
+
{{#ifeq:{{{series}}}| RUT9|
 +
[[File:Networking_rut9_manual_gps_https_tavl_settings.png|border|class=tlt-border]]
 +
|
 
[[File:Networking_rutos_manual_gps_https_tavl_settings.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_gps_https_tavl_settings.png|border|class=tlt-border]]
 +
}}
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 472: Line 480:  
         <td>off | on; default: <b>off</b></td>
 
         <td>off | on; default: <b>off</b></td>
 
         <td>Includes digital input state in the GPS data sent to server.</td>
 
         <td>Includes digital input state in the GPS data sent to server.</td>
 +
    </tr>
 +
</table>
 +
 +
==AVL I/O==
 +
 +
The <b>AVL I/O</b> tab provides you with the possibility to configure input rules.
 +
{{#ifeq: {{{analog}}} | 1 |
 +
===Check Analog===
 +
----
 +
The <b>Check Analog</b> section is used to set how often the device checks the value of the analog input. This is relevant to input rules related to the analog input.
 +
 +
[[File:Networking_rutos_manual_gps_avl_io_check_analog.png|border|class=tlt-border]]
 +
|}}
 +
===Input Rules===
 +
----
 +
The <b>Input Rules</b> section displays existing input rules. To create a new input rule look to the section below (<i>AVL Input Configuration</i>), select input type, trigger and click the 'Add' button.
 +
 +
[[File:Networking_rutos_manual_gps_avl_io_input_rules_add_button_config_io_{{{config_io}}}.png|border|class=tlt-border]]
 +
 +
After this you should be redirected to configuration page of the newly added rule, which should look similar to this:
 +
 +
[[File:Networking_rutos_manual_gps_avl_io_input_rules_avl_input_rule_data_configuration_config_io_{{{config_io}}}.png|border|class=tlt-border]]
 +
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Enable</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Turns the input rule on or off.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Input type</td>
 +
        <td>{{{input_types}}}; default: <b>{{#ifeq:{{{config_io}}}|1|Configurable Input/Output (3)|Input (3)}}</b></td>
 +
        <td>Selects to which input the rule will apply.</td>
 +
    </tr>{{#ifeq: {{{analog}}} | 1 |
 +
    <tr>
 +
        <td><span style="color: red;">Min voltage</span></td>
 +
        <td>float [0..40]; default: <b>none</b></td>
 +
        <td>Minimum analog input voltage range value that will trigger the rule.<br><b>Note:</b> this field is visible only when the selected 'Input type' is <i>Analog Input (11)</i>.</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: red;">Max voltage</span></td>
 +
        <td>float [0..40]; default: <b>none</b></td>
 +
        <td>Maximum analog input voltage range value that will trigger the rule.<br><b>Note:</b> this field is visible only when the selected 'Input type' is <i>Analog Input (11)</i>.</td>
 +
    </tr>|}}
 +
    <tr>
 +
        <td>Trigger</td>
 +
        <td>{{#ifeq:{{{analog}}}|1|<span style="color: blue;">Configurable I/O:</span>|}} Input active | Input low | Both{{#ifeq:{{{analog}}}|1|<br><span style="color: red;">Analog Input:</span> Inside range {{!}} Outside range|}}; default: <b>Input active</b></td>
 +
        <td>The event that will trigger the rule.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Priority</td>
 +
        <td>Low | High; default: <b>Low</b></td>
 +
        <td>The rule's priority. Different priority settings add different flags to event packets, so they can be displayed differently in the receiving system. The device sends data of higher priority first. Priority levels from highest to lowest are as follows:
 +
            <ol>
 +
                <!--<li>Panic</li>-->
 +
                <li>High</li>
 +
                <li>Low</li>
 +
            </ol>
 +
        </td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>

Navigation menu