Changes

no edit summary
Line 1: Line 1:  +
{{Template: Networking_rutos_manual_fw_disclosure
 +
| fw_version = {{{series}}}_R_00.06.07
 +
}}
 
==Summary==
 
==Summary==
    
The <b>Global Positioning System</b> (<b>GPS</b>) is a space-based radionavigation system. This page is an overview of the GPS service in {{{name}}} routers.
 
The <b>Global Positioning System</b> (<b>GPS</b>) is a space-based radionavigation system. This page is an overview of the GPS service in {{{name}}} routers.
  −
{{Template: Networking_rutxxx_manual_fw_disclosure
  −
| fw_version = {{{fw_version}}}
  −
}}
      
==Map==
 
==Map==
Line 13: Line 12:  
The figure below is an example of the Map page:
 
The figure below is an example of the Map page:
   −
[[File:{{{file_map}}}]]
+
[[File:Networking_rut_manual_gps_map.png]]
    
==General==
 
==General==
Line 21: Line 20:  
The figure below is an example of the General page and the table below provides information on the fields contained in that page:
 
The figure below is an example of the General page and the table below provides information on the fields contained in that page:
   −
[[File:{{{file_general}}}]]
+
[[File:Networking_rut_manual_gps_general.png]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 61: Line 60:  
The <b>NMEA forwarding</b> section is used to configure and enable NMEA forwarding. The figure below is an example of the NMEA forwarding section and the table below provides information on the fields contained in that section:
 
The <b>NMEA forwarding</b> section is used to configure and enable NMEA forwarding. The figure below is an example of the NMEA forwarding section and the table below provides information on the fields contained in that section:
   −
[[File:{{{file_nmea_forwarding}}}]]
+
[[File:Networking_rut_manual_gps_nmea_nmea_forwarding.png]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 100: Line 99:  
The router <b>caches NMEA forwarding</b> information if NMEA forwarding is enabled. This section is used to select the memory type where the cache will be stored and the maximum amount of data that will be saved:
 
The router <b>caches NMEA forwarding</b> information if NMEA forwarding is enabled. This section is used to select the memory type where the cache will be stored and the maximum amount of data that will be saved:
   −
[[File:{{{file_nmea_cache}}}]]
+
[[File:Networking_rut_manual_gps_nmea_nmea_forwarding_cache.png]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 129: Line 128:  
The <b>NMEA collecting</b> section is used to enable NMEA sentence gathering and storing. The figure below is an example of the NMEA collecting section and the table below provides information on the fields contained in that section:
 
The <b>NMEA collecting</b> section is used to enable NMEA sentence gathering and storing. The figure below is an example of the NMEA collecting section and the table below provides information on the fields contained in that section:
   −
[[File:{{{file_nmea_collecting}}}]]
+
[[File:Networking_rut_manual_gps_nmea_nmea_collecting.png]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 153: Line 152:  
The <b>NMEA sentence settings</b> section provides the possibility to configure which NMEA sentences will be forwarded or collected and at what frequency. The figure below is an example of the NMEA sentence settings section and the table below provides information on the fields contained in that section:
 
The <b>NMEA sentence settings</b> section provides the possibility to configure which NMEA sentences will be forwarded or collected and at what frequency. The figure below is an example of the NMEA sentence settings section and the table below provides information on the fields contained in that section:
   −
[[File:{{{file_nmea_sentence}}}]]
+
[[File:Networking_rut_manual_gps_nmea_nmea_sentence_settings.png]]
 +
 
 
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
Line 185: Line 185:  
<table class="nd-othertables_3">
 
<table class="nd-othertables_3">
 
     <tr>
 
     <tr>
         <th width=250>NMEA sentence name</th>
+
         <th width="250">NMEA sentence name</th>
         <th width=902>Description</th>
+
         <th width="902">Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 242: Line 242:  
The <b>HTTPS/HTTP Server Settings</b> section is used to enable GPS data sending to an HTTP or HTTPS server:
 
The <b>HTTPS/HTTP Server Settings</b> section is used to enable GPS data sending to an HTTP or HTTPS server:
   −
[[File:{{{file_https_settings}}}]]
+
[[File:Networking_rut_manual_gps_https_https_server_settings.png]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 266: Line 266:  
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:
   −
[[File:{{{file_tavl_settings}}}]]
+
[[File:Networking_rut_manual_gps_https_tavl_settings.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 304: Line 304:  
The <b>AVL Server Settings</b> section is used to configure the main parameters of data sending to an AVL server. The figure below is an example of the AVL Server Settings section and the table below provides information on the fields contained in that section:  
 
The <b>AVL Server Settings</b> section is used to configure the main parameters of data sending to an AVL server. The figure below is an example of the AVL Server Settings section and the table below provides information on the fields contained in that section:  
   −
[[File:{{{file_avl_settings}}}]]
+
[[File:Networking_rut_manual_gps_avl_avl_server_settings.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 331: Line 331:  
         <td>TCP | UDP; default: <b>TCP</b></td>
 
         <td>TCP | UDP; default: <b>TCP</b></td>
 
         <td>Protocol that will be used for communication with the AVL server.</td>
 
         <td>Protocol that will be used for communication with the AVL server.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Don't Contain Connection</td>
 +
        <td>yes | no; default: <b>no</b></td>
 +
        <td>When turned on, closes the TCP/UDP socket each time after transferring data.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 338: Line 343:  
The <b>Main rule</b> section defines how and when GPS data will be collected and sent to a specified AVL server. Refer to the figure and table below for information on the configuration fields of Main Rule.
 
The <b>Main rule</b> section defines how and when GPS data will be collected and sent to a specified AVL server. Refer to the figure and table below for information on the configuration fields of Main Rule.
   −
[[File:{{{file_main_rule}}}]]
+
[[File:Networking_rut_manual_gps_avl_main_rule.png]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 396: Line 401:  
Refer to the figure and table below for information on the configuration fields of the Secondary rules section.
 
Refer to the figure and table below for information on the configuration fields of the Secondary rules section.
   −
[[File:{{{file_secondary_rules}}}]]
+
[[File:Networking_rut_manual_gps_avl_secondary_rules.png]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 406: Line 411:  
     <tr>
 
     <tr>
 
         <td>Enable</td>
 
         <td>Enable</td>
         <td>yes | no; default: <b>no</b></td>
+
         <td>yes | no; default: <b>yes</b></td>
         <td>Turns the secondary rule on or off.</td>
+
         <td>Turns the rule on or off.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 416: Line 421:  
     <tr>
 
     <tr>
 
         <td>Digital Isolated Input</td>
 
         <td>Digital Isolated Input</td>
         <td>Low logic level | High logic level | Both; default: <b>Low logic level</b></td>
+
         <td>Low logic level | High logic level | Both; default: <b>High logic level</b></td>
 
         <td>Selects which input state will trigger the rule.</td>
 
         <td>Selects which input state will trigger the rule.</td>
 
     </tr>
 
     </tr>
Line 433: Line 438:  
     <tr>
 
     <tr>
 
         <td>Collect period</td>
 
         <td>Collect period</td>
         <td>integer [1..999999]; default: <b>25</b></td>
+
         <td>integer [1..999999]; default: <b>10</b></td>
 
         <td>How often (in seconds) data will be collected.</td>
 
         <td>How often (in seconds) data will be collected.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>Min distance</td>
 
         <td>Min distance</td>
         <td>integer [1..999999]; default: <b>200</b></td>
+
         <td>integer [1..999999]; default: <b>25</b></td>
 
         <td>Minimum distance change (in meters) before sending records.</td>
 
         <td>Minimum distance change (in meters) before sending records.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>Min angle</td>
 
         <td>Min angle</td>
         <td>integer [1..360]; default: <b>30</b></td>
+
         <td>integer [1..360]; default: <b>25</b></td>
 
         <td>Minimum angle change (in degrees) before sending records.</td>
 
         <td>Minimum angle change (in degrees) before sending records.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>Min saved records</td>
 
         <td>Min saved records</td>
         <td>integer [1..32]; default: <b>20</b></td>
+
         <td>integer [1..32]; default: <b>10</b></td>
 
         <td>Minimum amount of gathered records before sending.</td>
 
         <td>Minimum amount of gathered records before sending.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>Send period</td>
 
         <td>Send period</td>
         <td>integer [0..999999]; default: <b>50</b></td>
+
         <td>integer [0..999999]; default: <b>10</b></td>
 
         <td>How often (in seconds) gathered data is sent.</td>
 
         <td>How often (in seconds) gathered data is sent.</td>
 
     </tr>
 
     </tr>
Line 462: Line 467:  
The <b>AVL Configuration</b> section is used to add additional secondary GPS data sending rules.
 
The <b>AVL Configuration</b> section is used to add additional secondary GPS data sending rules.
   −
[[File:{{{file_gps_configuration}}}]]
+
[[File:Networking_rut_manual_gps_avl_gps_configuration.png]]
    
===TAVL Settings===
 
===TAVL Settings===
Line 468: Line 473:  
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:
   −
[[File:{{{file_tavl_settings}}}]]
+
[[File:Networking_rut_manual_gps_avl_tavl_settings.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 495: Line 500:  
         <td>yes | no; default: <b>no</b></td>
 
         <td>yes | no; default: <b>no</b></td>
 
         <td>Includes digital input #2 state in GPS data package to be sent to server.</td>
 
         <td>Includes digital input #2 state in GPS data package to be sent to server.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Send digital input (3)</td>
 +
        <td>yes | no; default: <b>no</b></td>
 +
        <td>Includes digital input #3 state in GPS data package to be sent to server.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 506: Line 516:  
The <b>Check Analog</b> section is used to set how often the router checks the value of the analog input. This is relevant to input rules related to the analog input.
 
The <b>Check Analog</b> section is used to set how often the router checks the value of the analog input. This is relevant to input rules related to the analog input.
   −
[[File:{{{file_avl_io_analog}}}]]
+
[[File:Networking_rut_manual_gps_avl_io_check_analog.png]]
    
===Input Rules===
 
===Input Rules===
Line 514: Line 524:  
To configure an input rule click the 'Edit' button located next to it. The figure below represents a newly added rule with default settings. Refer to the table below for information on the fields contained in the input rule configuration section.
 
To configure an input rule click the 'Edit' button located next to it. The figure below represents a newly added rule with default settings. Refer to the table below for information on the fields contained in the input rule configuration section.
   −
[[File:{{{file_avl_io_rules}}}]]
+
[[File:Networking_rut_manual_gps_avl_io_input_rule_configuration.png]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 554: Line 564:  
A <b>geofence</b> is a virtually defined boundary for a real-world geographic area. The GPS Geofencing page provides you with the possibility to set this custom area and apply rules that will inform you when the device leaves or enters the geofence.
 
A <b>geofence</b> is a virtually defined boundary for a real-world geographic area. The GPS Geofencing page provides you with the possibility to set this custom area and apply rules that will inform you when the device leaves or enters the geofence.
   −
[[File:{{{file_geofencing_add}}}]]
+
[[File:Networking_rut_manual_gps_gps_geofencing_add_button.png]]
    
The figure below is an example of GPS Geofencing configuration and the table below provides information related to that configuration:
 
The figure below is an example of GPS Geofencing configuration and the table below provides information related to that configuration:
   −
[[File:{{{file_geofencing_details}}}]]
+
[[File:Networking_rut_manual_gps_gps_geofencing_details.png]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 601: Line 611:     
<ul>
 
<ul>
     <li>[[{{{name}}}_Protocols|{{{name}}} GPS protocols]]</li>
+
     <li>[[{{{name}}} GPS Protocols]]</li>
 
</ul>
 
</ul>
   −
[[Category:{{{name}}} WebUI]]
+
[[Category:{{{name}}} Services section]]

Navigation menu