Select Page

RUTX11 GPS

Summary #

The Global Positioning System (GPS) is a space-based radionavigation system. This page is an overview of the GPS service in RUTX11 devices.

If you’re having trouble finding this page or some of the parameters described here on your device’s WebUI, you should turn on “Advanced WebUI” mode. You can do that by clicking the “Basic” button under “Mode”, which is located at the top-right corner of the WebUI.

Networking rutx manual webui basic advanced mode v1.gif

Map #

The Map page displays the device’s current coordinates and position on the map. To see the device’s location on the map, make sure to attach the GPS antenna on the device and enable GPS in the General page.

The figure below is an example of the Map page:

Networking rutx manual gps map v1.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 Map page in order to see if the device has obtained a GPS fix. It is very important to attach the GPS antenna on the device and place it outside (not inside of a building). The device 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:

Networking rutx manual gps general v2.png
FieldValueDescription
Enabledoff | on; default: offTurns the GPS service on or off.
Galileo NMEA support*off | on; default: offTurns support for Galileo satellites on or off.
Glonass NMEA support*off | on; default: offTurns support for Glonass satellites on or off.
BeiDou NMEA support*off | on; default: offTurns support for BeiDou satellites on or off.

*Changing these options requires a modem reboot. Therefore, if you make changes to these options and save them, the device will lose cellular connectivity for about 30 seconds.

NMEA #

The NMEA page is used to configure settings related to NMEA sentence collecting and forwarding.

NMEA forwarding #

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:

Networking rutx manual gps nmea nmea forwarding v2.png
FieldValueDescription
Enabledoff | on; default: offTurns NMEA forwarding on or off.
Hostnameip | host; default: 192.168.1.5IP address or hostname of the server to which NMEA data will be forwarded.
Portinteger [0..65535]; default: 8500Port number off the server to which NMEA data will be forwarded.
ProtocolTCP | UDP; default: TCPProtocol that will be used to send NMEA data.

NMEA forwarding cache #

The device 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:

Networking rutx manual gps nmea nmea forwarding cache v2.png
FieldValueDescription
Save cache inRAM Memory | FLASH Memory; default: RAM MemorySelects which type of memory will be used for storing NMEA forwarding cache.
Maximum sentencesinteger; default: 5000Maximum amount of NMEA sentences that will be saved in the cache before older entries are deleted and replaced by new ones.
Filefilepath; default: noneLocation of the file where NMEA forwarding cache information will be stored. This field becomes visible only when the selected memory type is “flash”.

NMEA collecting #

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:

Networking rutx manual gps nmea nmea collecting v1.png
FieldValueDescription
Enabledoff | on; default: offTurns NMEA sentence collecting on or off.
Locationfilepath; default: noneLocation of the file where NMEA sentences will be stored. This field becomes visible only when NMEA collecting is enabled.

NMEA sentence settings #

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:

Networking rutx manual gps nmea nmea sentence settings v2.png
FieldValueDescription
Forwarding enabledoff | on; default: offEnables forwarding for the adjacent NMEA sentence.
Forwarding intervalpositive integer; default: 5NMEA sentence forwarding frequency in seconds.
Collecting enabledoff | on; default: offEnables collecting for the adjacent NMEA sentence.
Collecting intervalpositive integer; default: 5NMEA sentence collecting frequency in seconds.


NMEA sentence reference table:

NMEA sentence nameDescription
GPGSVNumber of GPS satellites in view.
GPGGAGPS fix data.
GPVTGTrack made good and speed relative to the ground.
GPRMCRecommended minimum specific GPS/Transit data.
GPGSAGPS DOP and active satellites.
GNGSAGLONASS DOP and active satellites.
GLGSVNumber of GLONASS satellites in view.
GNGNSGNSS position fix from more than one constellation (e.g., GPS + GLONASS).
GAGSVNumber of Galileo satellites in view.
PQGSVDetailed satellite data (used in BeiDou sentences).
PQGSAOverall satellite data (used in BeiDou sentences).

HTTPS #

The HTTPS page can be used to configure data sending to an HTTP(S) server.

HTTPS/HTTP server settings #

The HTTPS/HTTP Server Settings section is used to enable GPS data sending to an HTTP or HTTPS server.

Networking rutx manual gps https server settings v2.png
FieldValueDescription
Enabledoff | on; default: offTurns data sending to HTTP/HTTPS server on or off.
URLstring; default: 192.168.1.5URL of remote server.

TAVL settings #

The TAVL settings section is used to select which data will be sent to the TAVL server:

Networking rutx manual gps avl tavl settings v3.png
FieldValueDescription
Send GSM signaloff | on; default: offIncludes GSM signal strength information in the GPS data sent to server.
Send digital inputoff | on; default: offIncludes digital input state in the GPS data sent to server.

AVL #

The AVL page is used to set up GPS data sending to an AVL server.

AVL server settings #

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:

Networking rutx manual gps avl avl server settings v2.png
FieldValueDescription
Enabledoff | on; default: offTurns data sending to AVL server on or off.
Hostnameip | host; default: 192.168.1.5IP address or hostname of an AVL server.
Portinteger [0..65535]; default: 8501TCP/UDP port number of the AVL server to which the device will be connecting.
ProtocolTCP | UDP; Default: TCPProtocol that will be used for communication with the AVL server.

Main rule #

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.

Networking rutx manual gps avl main rule v1.png
FieldValueDescription
Enableoff | on; default: onTurns the main rule on or off.
Rule priorityLow priority level | High priority level | Panic priority level | Security priority level; default: Low priority levelThe 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:SecurityPanicHighLow
Collect periodinteger [1..999999]; default: 5How often (in seconds) data will be collected.
Min distanceinteger [1..999999]; default: 50Minimum distance change (in meters) before sending records.
Min angleinteger [1..360]; default: 50Minimum angle change (in degrees) before sending records.
Min saved recordsinteger [1..32]; default: 20Minimum amount of gathered records before sending.
Send periodinteger [0..999999]; default: 60How often (in seconds) gathered data is sent.

Secondary rules #

The Secondary rules section provides you with the possibility to create additional data sending rules. The difference from the main rule is that the secondary rules only send data when the device uses a specified type of WAN and when the digital isolated output is in the specified state.

Refer to the figure and table below for information on the configuration fields of the Secondary rules section.

Networking rutx manual gps avl secondary rules v1.png
FieldValueDescription
Enableoff | on; default: offTurns the secondary rule on or off.
WANMobile Both | Mobile Home | Mobile Roaming | Wired; default: Mobile HomeSelects which type of WAN will trigger the rule.
Digital Isolated InputLow logic level | High logic level | Both; default: Low logic levelSelects which input state will trigger the rule.
Rule priorityLow priority level | High priority level | Panic priority level | Security priority level; default: High priority levelThe 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:SecurityPanicHighLow
Collect periodinteger [1..999999]; default: 10How often (in seconds) data will be collected.
Min distanceinteger [1..999999]; default: 25Minimum distance change (in meters) before sending records.
Min angleinteger [1..360]; default: 25Minimum angle change (in degrees) before sending records.
Min saved recordsinteger [1..32]; default: 10Minimum amount of gathered records before sending.
Send periodinteger [0..999999]; default: 10How often (in seconds) gathered data is sent.

TAVL settings #

The TAVL settings section is used to select which data will be sent to the TAVL server:

Networking rutx manual gps avl tavl settings v3.png
FieldValueDescription
Send GSM signaloff | on; default: offIncludes GSM signal strength information in the GPS data sent to server.
Send digital inputoff | on; default: offIncludes digital input state in the GPS data sent to server.

GPS Geofencing #

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.

To create a new geofence area, enter a custom name for it and click the ‘Add’ button. A new geofence area configuration with the given name should appear in the “Geofencing” list. Click the button that looks like a pencil next to it to begin editing.

The figure below is an example of GPS Geofencing configuration and the table below provides information related to that configuration:

Networking rutx manual gps gps geofencing geofencing details v1.png
FieldValueDescription
Enableoff | on; default: offTurns the Geofence rule on or off.
Longitude (X)degrees [-180.000000..180.000000]; default: 0.000000East-west position of a point on the Earth’s surface. Combining this and the Latitude information will produce a point on the world map that will serve as the center of the geofence area.
Latitude (Y)degrees [-90.000000..90.000000]; default: 0.000000North-south position of a point on the Earth’s surface. Combining this and the Longitude information will produce a point on the world map that will serve as the center of the geofence area.
Radiusinteger [1..999999]; default: 200Radius (in meters) of the geofence area.
Generate event onExit | Enter | Enter/exit; default: ExitSpecifies whether the rule should be triggered when the device enters the geofence area, leaves it or on both events.
Get current coordinates– (interactive button)Obtains the device’s current coordinates and places them in the Longitude and Latitude fields.

Submit a Comment

Your email address will not be published. Required fields are marked *