Changes

Template:Networking rut manual gps (view source)

Revision as of 10:24, 23 December 2020

3,045 bytes added , 10:24, 23 December 2020

no edit summary

Line 1: Line 1: +

{{Template: Networking_rutos_manual_fw_disclosure

+

| fw_version = {{{series}}}_R_00.06.07

+

}}

==Summary==

The Global Positioning System (GPS) 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==

Line 13: Line 12:

The figure below is an example of the Map page:

−

[[File:~~{{{file_map}}}~~]]

+

[[File:Networking_rut_manual_gps_map.png]]

==General==

−

The General is used to enable the GPS service and the support for different types satellites. Once you turn on GPS, you can check the [[{{{name}}}_GPS#Map|Map]] page in order to see if the router has obtained a GPS fix. It is very important to attach the GPS antenna on the router and place it outside (not inside of a building). The router will not be likely to obtain a GPS fix otherwise.

+

The General section is used to enable the GPS service and the support for different types satellites. Once you turn on GPS, you can check the [[{{{name}}}_GPS#Map|Map]] page in order to see if the router has obtained a GPS fix. It is very important to attach the GPS antenna on the router and place it outside (not inside of a building). The router will not be likely to obtain a GPS fix otherwise.

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]]

Line 61: Line 60:

The NMEA forwarding 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]]

Line 72: Line 71:

<td>Enabled</td>

<td>yes | no; default: no</td>

−

<td>Turns NMEA forwarding on or off.</td>

+

<td>Turns NMEA forwarding on or off</td>

</tr>

<tr>

<td>Hostname</td>

<td>ip | host; default: 192.168.1.5</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>

<td>integer [0..65535]; default: 8500</td>

−

<td>Port number off the server to which NMEA data will be forwarded.</td>

+

<td>Port number off the server to which NMEA data will be forwarded</td>

</tr>

<tr>

<td>Protocol</td>

<td>TCP | UDP; default: TCP</td>

−

<td>Protocol that will be used to send NMEA data.</td>

+

<td>Protocol that will be used to send NMEA data</td>

+

</tr>

+

<tr>

+

<td>Contain Connection</td>

+

<td>yes | no; default: no</td>

+

<td>Contain active session with a remote server</td>

</tr>

</table>

Line 95: Line 99:

The router caches NMEA forwarding 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]]

Line 124: Line 128:

The NMEA collecting 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]]

Line 148: Line 152:

The NMEA sentence settings 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]]

+

<tr>

Line 180: Line 185:

<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>

Line 237: Line 242:

The HTTPS/HTTP Server Settings 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]]

Line 261: Line 266:

The TAVL Settings 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]]

Line 299: Line 304:

The AVL Server Settings 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]]

Line 326: Line 331:

<td>TCP | UDP; default: TCP</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: no</td>

+

<td>When turned on, closes the TCP/UDP socket each time after transferring data.</td>

</tr>

</table>

Line 333: Line 343:

The Main rule 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]]

Line 391: Line 401:

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]]

Line 401: Line 411:

<tr>

<td>Enable</td>

−

<td>yes | no; default: no</td>

+

<td>yes | no; default: yes</td>

−

<td>Turns the ~~secondary~~ rule on or off.</td>

+

<td>Turns the rule on or off.</td>

</tr>

<tr>

Line 411: Line 421:

<tr>

<td>Digital Isolated Input</td>

−

<td>Low logic level | High logic level | Both; default: ~~Low~~ logic level</td>

+

<td>Low logic level | High logic level | Both; default: High logic level</td>

<td>Selects which input state will trigger the rule.</td>

</tr>

Line 428: Line 438:

<tr>

<td>Collect period</td>

−

<td>integer [1..999999]; default: 25</td>

+

<td>integer [1..999999]; default: 10</td>

<td>How often (in seconds) data will be collected.</td>

</tr>

<tr>

<td>Min distance</td>

−

<td>integer [1..999999]; default: ~~200~~</td>

+

<td>integer [1..999999]; default: 25</td>

<td>Minimum distance change (in meters) before sending records.</td>

</tr>

<tr>

<td>Min angle</td>

−

<td>integer [1..360]; default: 30</td>

+

<td>integer [1..360]; default: 25</td>

<td>Minimum angle change (in degrees) before sending records.</td>

</tr>

<tr>

<td>Min saved records</td>

−

<td>integer [1..32]; default: 20</td>

+

<td>integer [1..32]; default: 10</td>

<td>Minimum amount of gathered records before sending.</td>

</tr>

<tr>

<td>Send period</td>

−

<td>integer [0..999999]; default: 50</td>

+

<td>integer [0..999999]; default: 10</td>

<td>How often (in seconds) gathered data is sent.</td>

</tr>

Line 457: Line 467:

The AVL Configuration 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===

Line 463: Line 473:

The TAVL Settings 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]]

Line 490: Line 500:

<td>yes | no; default: no</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: no</td>

+

<td>Includes digital input #3 state in GPS data package to be sent to server.</td>

+

</tr>

+

</table>

+

==AVL I/O==

+

The AVL I/O tab provides you with the possibility to configure input rules.

+

===Check Analog===

+

----

+

The Check Analog 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:Networking_rut_manual_gps_avl_io_check_analog.png]]

+

===Input Rules===

+

----

+

The Input Rules section displays existing input rules. To create a new input rule look to the section below (AVL Input Configuration), select input type, trigger and click the 'Add' button.

+

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:Networking_rut_manual_gps_avl_io_input_rule_configuration.png]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Enable</td>

+

<td>yes | no; default: no</td>

+

<td>Turns the input rule on or off.</td>

+

</tr>

+

<tr>

+

<td>Input type</td>

+

<td>Digital | Digital isolated | analog; default: Digital</td>

+

<td>Selects to which input the rule will apply.</td>

+

</tr>

+

<tr>

+

<td>Trigger</td>

+

<td>Input open | Input shorted | Both; default: Input open</td>

+

<td>The event that will trigger the rule.</td>

+

</tr>

+

<tr>

+

<td>Priority</td>

+

<td>Low | High | Panic; default: Low</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 router sends data of higher priority first. Priority levels from highest to lowest are as follows:

+

<ol>

+

<li>Panic</li>

+

+

+

</ol>

+

</td>

</tr>

</table>

Line 497: Line 564:

A geofence 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:

−

[[File:~~{{{file_geofencing_details}}}~~]]

+

[[File:Networking_rut_manual_gps_gps_geofencing_details.png]]

Line 544: Line 611:

<ul>

−

<li>[[~~{{{name}}}_Protocols|~~{{{name}}} GPS ~~protocols~~]]</li>

+

<li>[[{{{name}}} GPS Protocols]]</li>

</ul>

−

[[Category:{{{name}}} ~~WebUI~~]]

+

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

Dziugas

Bureaucrats, Interface administrators, Administrators

31,703

edits

Namespaces

Variants

Views

More

Search

Changes

Template:Networking rut manual gps (view source)

Revision as of 10:24, 23 December 2020

Navigation menu

Personal tools

NAVIGATION

Tools

Categories