This page shows you how to configure an AirLink router so that it will provide location data for display in the Tracker widget. For more information about Tracker itself, see How to Use the Tracker Widget.
Tracker uses GPS data from the AirLink router, so you must:
In AirLink OS, go to Services > Location > General, and 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.
Your router’s AirLink OS Location settings may not include all the settings shown in the AirLink XR60 example below.
To configure communication frequency in ALMS, you can either:
On the Monitor > Systems page:
Configuring a smart reporting rule with an On Change trigger enables the router to record location changes and forward location data to ALMS.
Location data is not forwarded immediately. By default, the router has a minimal 10 seconds delay. The delay can be reduced to 2 seconds using the second template in later section.
Semtech recommends configuring these settings on a single router, and then creating a configuration template that can be applied to a fleet of routers. These routers must be the same model and running the same AirLink OS router software version as the router on which you created the configuration template.
If you are configuring the router in ALMS, first locate the router and view its configuration.
On the System detail page, click Configuration.
The AirLink OS configuration interface opens.
Under the DATASETS table, click CREATE FROM SCRATCH.
AirLink OS enters Dataset mode.
Go to Status/Monitoring > Services > Location.
Select LATITUDE and LONGITUDE.
In the progress bar at bottom, click SAVE.
Save the dataset with a name like Location_data_for_tracker.
Under the REPORTING RULES table, click CREATE RULE.
In the Create rule window, create a rule with the following settings:
Enter a name for the rule, such as “Report location update for Tracker”.
Under “Trigger, click CREATE to create a new “On Data Change” trigger.
The Create on Change window appears.
Enter a Name for the trigger.
Under DATASET, select the dataset created earlier (the “Location_data_for_tracker” for example).
Click CREATE.
In the Create Rule window, do not select any FILTERS.
Under “Action”, click “Create” to create a new “Action”.
The Create Send To ALMS window appears.
Name the Action such as “Store and forward location data for Tracker”.
Under STORAGE POLICY, select Store And Forward.
Under DATASET, select the dataset created earlier (Location_data_for_tracker, for example).
Click CREATE.
In the Create Rule window, click “Create” to finish creating the Smart Reporting Rule.
Confirm that the new new rule is enabled in the REPORTING RULES table.
Click SAVE to save the configuration change on the router.
To apply the new reporting rule to multiple routers, you can create an AirLink OS configuration template containing the new Smart Reporting rule.
See How to create a template for an overview of templates in ALMS.
To create the configuration template in ALMS:
Click EXPORT.
Select “Export to my ALMS account” to save the template, and give it a name such as “Smart_reporting_rule_for_Tracker”.
Click SAVE to finish creating the template.
AirLink OS has a default data report latency of 10 seconds, which is not optimal for reporting Tracker data. Although the latency can be configured to a minimum of 2 seconds, this setting is not currently available in the AirLink OS user interface. Because of this, Semtech has provided templates that will configure latency to 2 seconds.
The latest AirLink OS release (at time of this writing) is 5.0.86. The required JSON templates are created for 5.0.86, and can be downloaded from the Source. You can then import the template to your ALMS account.
SERVER | ROUTER | AIRLINK OS VERSION | TEMPLATE |
---|---|---|---|
EU | RX55 | 5.0.86 | eu_configure_data_report_latency_rx55_5.0.86.json |
EU | XR60 | 5.0.86 | eu_configure_data_report_latency_xr60_5.0.86.json |
EU | XR80 | 5.0.86 | eu_configure_data_report_latency_xr80_5.0.86.json |
EU | XR90 | 5.0.86 | eu_configure_data_report_latency_xr90_5.0.86.json |
NA | RX55 | 5.0.86 | na_configure_data_report_latency_rx55_5.0.86.json |
NA | XR60 | 5.0.86 | na_configure_data_report_latency_xr60_5.0.86.json |
NA | XR80 | 5.0.86 | na_configure_data_report_latency_xr80_5.0.86.json |
NA | XR90 | 5.0.86 | na_configure_data_report_latency_xr90_5.0.86.json |
CAD | RX55 | 5.0.86 | cad_configure_data_report_latency_rx55_5.0.86.json |
CAD | XR60 | 5.0.86 | cad_configure_data_report_latency_xr60_5.0.86.json |
CAD | XR80 | 5.0.86 | cad_configure_data_report_latency_xr80_5.0.86.json |
CAD | XR90 | 5.0.86 |
cad_configure_data_report_latency_xr90_5.0.86.jso |
Do not edit the template. The template contains custom information such as non-visible fields that are not supported in the AirLink OS UI. These values may not display correctly. If you edit an imported template, its non-visible fields will revert to their default values.
In the Import Template window, click + Select a JSON.
Locate your .json file and click Open.
Click Start to import the template.
After the import is complete, the new template will appear in the Templates list.
You can apply the two templates to a fleet of routers using an ALMS Workflow. For an overview see How to configure systems using Apply Workflow(s).
A configuration template is associated with a specific firmware release. Change to device will be rejected if firmware release versions mismatch.
At top right corner of the systems table, click Apply Workflow(s).
In the Apply Workflow(s) window, create two “Apply Template” steps with the required templates. Ensure that the data reporting latency template is the second of the two steps.
Click Launch. The Operation Dependencies window appears.
Cick Setup dependencies and continue to launch the configuration change operations.
You can go to Monitor > Operations to monitor the progress.
To add the Tracker widget:
Auto refresh is disabled by default. When enabled, Tracker auto refreshes every 5 seconds.
Tracker displays devices that have updated their location within the last 15 minutes by default. This default setting is configurable (see Filtering Results and Time Range below).
Tracker gives you the following options for filtering results.
The map displays systems whose last reported location time is within the selected time range. By default the time range is the last 15 minutes, to limit the display to only devices that have been active recently. Set the duration longer to see devices that have not been active recently.
Tracker has various controls for viewing the data you want to see.
When several vehicles are so close together that they can’t be viewed separately, Tracker presents them in a cluster.
Click a cluster to zoom in and view the individual vehicles, or smaller clusters.
When looking at a vehicle on the map, you can view system information. To view system information, click the location icon.
The system name, last recorded position coordinates and the time of the last recorded position are displayed. Click x to close the system information bubble.
The map options include:
You can switch between Google Maps standard Map view and Satellite view. You can also display Google Maps traffic layer.
AirLink OS-based devices stream data to ALMS in a near real-time fashion. In its default configuration, AirLink OS will not stream location data at a high enough resolution for the Tracker widget to provide a near real-time experience. If you follow the configuration instructions provided in Enabling Location in AirLink OS, then you can expect that the device location will update approximately every 5 seconds.