XR Series routers are equipped with location tracking, enabling you to track the movements of a vehicle or other devices that move. The router relays the information of its location as well as other data for use with tracking applications.
Common uses for location reporting include:
For instructions on configuring the router for Advanced Mobility Reporting (AMR) (available in ALMS), see this page.
National Marine Electronics Association (NMEA®): NMEA is an ASCII protocol used by many location tracking applications.
Trimble® ASCII Interface Protocol (TAIP): TAIP is a digital communication interface based on printable ASCII characters over a serial data link. TAIP was designed specifically for vehicle tracking applications but has become common in a number of other applications, such as data terminals and portable computers, because of its ease of use.
Ensure that a GNSS antenna is connected to the dark blue FAKRA connector on the router. See the XR Series Hardware Guide for installation and antenna connection instructions. For compatible antennas sold by Sierra Wireless, see our website.
After starting up the router, check the GNSS LED to confirm GNSS operation. The GNSS LED will be red while searching for a fix. After getting a fix, it is yellow (Dead Reckoning is enabled but not calibrated) or green (Dead Reckoning is calibrated or disabled). Dead Reckoning enhances vehicle tracking when satellite GNSS service is impeded or unreliable.
See this page for full LED information.
GNSS is the evolution of GPS. GPS uses only a single constellation of satellites, while GNSS uses signalling from up to 4 constellations to provide a more reliable and accurate location fix. For legacy applications that may require GPS-only, you can limit the location service by selecting the “GPS Only” option. See LOCATION CONSTELLATION below.
Under Services > Location > General, ensure that GNSS ENABLE is On.
GNSS is enabled by default, and begins working when the router is powered on with a GNSS antenna connected. GNSS status is reported under GNSS STATE, and can include the following status messages:
Status messages related to Firmware are shown after you manually select new GNSS Firmware for the router to use. See GNSS FIRMWARE SELECTION MODE below.
For fine tuning GNSS, you can configure the settings listed below:
SETTING | DESCRIPTION | RANGE | DEFAULT |
---|---|---|---|
GNSS FIRMWARE SELECTION MODE |
When switched to Manual, you can select firmware from the SELECT GNSS FIRMWARE list.
|
Manual, Automatic | Automatic |
GNSS CURRENT FIRMWARE | Current version of firmware on the router’s GNSS (Global Navigation Satellite System) module | N/A | N/A |
LOCATION CONSTELLATION | Location constellation you want the router to use |
|
GNSS (GPS, Galileo, QZSS, GLONASS) |
GNSS ANTENNA BIAS | Optimize the router for the type of connected GNSS antenna |
On (required for active GNSS antenna) Off (compatible only for passive GNSS antenna) |
On |
FAST FIRST FIX | Leave Off. This setting will be removed in a future release | Off/On | Off |
GNSS ANTENNA DETECTION | Enable/Disable the reporting of GNSS Antenna State under Status/Monitoring > Status > Location. When disabled, GNSS Antenna State is reported as Not available. | Off/On | Off |
Under Location > Reporting, enter the TAIP ID (used for TAIP reports; not required for NMEA). This can be any four-character alphanumeric string as per the TAIP standard.
Local reports are sent via UDP to an IP address on the LAN. For Local Reporting, configure the following:
Report Type: Select the report type (or protocol, as described above).
Sentences: If the report type is NMEA, you can select the desired combination of GGA, GSA, RMC, VTG, and GSV sentences. Some typical sentences are below.
For Remote Reporting, configure the following REMOTE REPORTING SERVER settings, as applicable:
AirLink gateways and routers running ALEOS could embed a unique identifier into the NMEA sentence to identify the vehicle or host device sending the location data. This functionality will be added to a future AirLink OS release.
It is possible to send reports via the RJ45 Serial port on the router using the loopback address (127.0.0.1) and then setting the Serial port in PAD mode to listen and forward to the serial port. This configuration is useful in cases where local serial forwarding is used for sending reports to laptops in docking stations in a service vehicle.
To configure sending local reports to the Serial Port:
Under Location > Reporting > LOCAL REPORTING, configure Local Reporting for UDP Multicast using the loopback address (127.0.0.1).
Go to Hardware Interfaces.
Under Serial Interfaces > Configuration, set the MODE for Port 1 to PAD.
Under PAD Settings, configure Port 1 as follows:
The receiving application may have additional requirements for reducing the BAUD rate or configuring other flow control parameters. Consult the documentation from the application vendor for details.
Click SAVE.
To confirm operation, open the CAD/AVL listening application on your computer and confirm that messages are being received and understood.
You can send GPIO status along with device location to an MQTT server using the Telemetry reporting feature.
The Report Title General Purpose Inputs exists by default, and is reported at each GPIO state change by default. This report sends the report GPIO ARA, which consists of the following data points:
Example:
GPIO Input 5: false
GPIOCumulativeBits: 01011 (= hexadecimal 0x0B) (= decimal 11)
To send GPIO and location information to an MQTT server:
Go to Telemetry > General, turn on SERVICE.
Go to Telemetry > Reporting, under REPORT MODE, select one of the MQTT options: MQTT or AirVantage and MQTT.
Under Telemetry > MQTT, configure the connection to your MQTT server.