Searching...

Matching results

    Tracker Latency Templates (AirLink OS 5.0 and 5.1)

    Configuring Data Report Latency

    When configuring an AirLink OS router to use Tracker, the ALMS Smart Reporting LATENCY LIMIT is an important setting to consider. The default report latency of 10 seconds is not optimal for reporting Tracker data. Although the latency can be configured in AirLink OS 5.2 and later, this setting was not user-configurable in AirLink OS 5.0.86 and 5.1.78.

    Because of this, Semtech has provided templates that will configure latency to 2 seconds for routers running AirLink OS 5.0.86 or 5.1.78.

    The JSON templates available for download below are created for AirLink OS 5.0.86 and 5.1.78. After downloading, you can import these templates to your ALMS account. Templates can be applied to routers running AirLink OS 5.0.86 or 5.1.78 in order to set Tracker data report latency to 2 seconds.

    SERVER ROUTER AIRLINK OS 5.0.86 AIRLINK OS 5.1.78
    EU RX55 eu_configure_data_report_latency_rx55_5.0.86.json eu_configure_data_report_latency_rx55_5.1.78.json
    EU XR60 eu_configure_data_report_latency_xr60_5.0.86.json eu_configure_data_report_latency_xr60_5.1.78.json
    EU XR80 eu_configure_data_report_latency_xr80_5.0.86.json eu_configure_data_report_latency_xr80_5.1.78.json
    EU XR90 eu_configure_data_report_latency_xr90_5.0.86.json eu_configure_data_report_latency_xr90_5.1.78.json
    NA RX55 na_configure_data_report_latency_rx55_5.0.86.json na_configure_data_report_latency_rx55_5.1.78.json
    NA XR60 na_configure_data_report_latency_xr60_5.0.86.json na_configure_data_report_latency_xr60_5.1.78.json
    NA XR80 na_configure_data_report_latency_xr80_5.0.86.json na_configure_data_report_latency_xr80_5.1.78.json
    NA XR90 na_configure_data_report_latency_xr90_5.0.86.json na_configure_data_report_latency_xr90_5.1.78.json
    CAD RX55 cad_configure_data_report_latency_rx55_5.0.86.json cad_configure_data_report_latency_rx55_5.1.78.json
    CAD XR60 cad_configure_data_report_latency_xr60_5.0.86.json cad_configure_data_report_latency_xr60_5.1.78.json
    CAD XR80 cad_configure_data_report_latency_xr80_5.0.86.json cad_configure_data_report_latency_xr80_5.1.78.json
    CAD XR90 cad_configure_data_report_latency_xr90_5.0.86.json cad_configure_data_report_latency_xr90_5.1.78.json

    Import the Configuration Template

    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.

    1. In ALMS, go to Configure > Templates.
    2. Click the Import button at the top right corner.

    3. In the Import Template window, click + Select a JSON.

    4. Locate your .json file and click Open.

    5. Click Start to import the template.

      After the import is complete, the new template will appear in the Templates list.

    Apply the Configuration Template

    You can apply templates to a fleet of routers using an ALMS Workflow. For an overview see How to configure systems using Apply Workflow(s).

    This example shows you how to apply two templates:

    A configuration template is associated with a specific router model and its firmware release. Applying a template will fail if the router models and/or the firmware release versions do not match.

    1. Go to Monitor > Systems.
    2. Select the target system(s) to receive configuration changes.

    3. At top right corner of the systems table, click Apply Workflow(s).

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

    5. Click Launch. The Operation Dependencies window appears.

    6. Click Setup dependencies and continue to launch the configuration change operations.

      You can go to Monitor > Operations to monitor the progress.

    TOP