The process outlined below is designed for customers that need to configure a device (or a fleet of gateways) for ALMS ARA. ALMS ARA (Advanced Reporting and Analytics) provides a series of pre-defined reports that deliver deeper insight into the range of telemetry data via ALMS by the MP70/LX60 of gateways.
Step-by-step guide
Register your MP70/LX60 in ALMS:
Enter your device's Serial Number and IMEI/ESN.
Select "Pre-configure system". Once complete, select Register.
Fill in an optional Name for the device.
Pre-configured System(s) window:
In the Configure Communication workflow, adjust the Heartbeat, Status report, and add an Additional dataset as needed.
In the Apply Template workflow, choose a device template. The device template must already be created under Configure > Templates. The device template must also have ALEOS Application Framework (AAF) enabled as part of the configuration.
Note
The ALMS ARA Device Template below shows the user-created device template with ALEOS Application Framework (AAF) enabled.
3. Select Pre-configure in the Pre-configured Systems window.
4. The Operation Dependencies window will show up. Accept the changes by selecting Setup Dependencies and continue.
5. The next time your device checks in with ALMS, it will pick up the workflows applied to the newly registered device.
Before check-in.
After check-in.
Important
Please ensure the Systems Operations have successfully completed before proceeding further.
6. Create another Workflow by navigating to Monitor > Systems and selecting the gateways you wish to apply the Workflow to. Currently, Workflows can only be applied up to 50 units at a time. The Workflow button will grey out if you select all gateways (assuming there is more than 50 in your fleet).
7. In Apply Workflow(s):
a. Remove the Basic Workflow and Apply Template workflow.
b. Drag and drop the Configure ALMS ARA workflow.
Important
Please ensure that you select the correct setting under Direct Vehicle Bus (CAN) Data Collection. By default, this is Enabled: Connected to Ignition. If you do not have the ignition sense properly wired to your vehicle's ignition or an external switch, the MP70 may not be able to communicate with your vehicle's diagnostics port. Please refer to the Telemetry Guide for more detail: https://source.sierrawireless.com/devices/telemetry/telemetry/#sthash.LPlc2Cc5.dpbs.
Create an AAF Password.
Under Install Application (1), ensure the latest AVTA version is selected.
Under Install Application (2), ensure the latest AVTC version is selected.
Under Start Application, ensure the latest AVTA version is selected.
Create an AVTA Password.
Click Launch when you're finished.
Note
If the "Install application" operation is pending longer than 24 hours of the device being online, please see the Troubleshooting steps guided near the end of this article.
8. The ALMS ARA workflow should eventually complete:
9. (Optional) If required, you can also enable the AVTC application in the device view of a particular gateway by selecting the Play button beside AVTC. AVTA is already started as part of the ALMS ARA workflow.
10. All that is left to do is configure the AVTA settings. By default, only a specific set of telemetry data is sent via MQTT by default. You will need to toggle each parameter that you want ALMS ARA to report on. You can do this by one of two methods:
Creating a new Application template for AVTA under Configure Templates.
Manually configuring the AVTA settings for a specific device. This can be found in the device view under the System Applications widget.
Click on AVTA.
2. Select Telemetry_config.
3. Configure your parameters.
Note
Once you apply the changes, you will need to reboot the gateway as well. An option will be presented to do so once you hit Apply.
Please refer to the Sierra Wireless Source page for the AVTA User Guide on specific configuration parameters.
11. All that is left is configuring the reports for the ALMS ARA solution. Under Reporting tab, you can create a new report that will include a handful of pre-defined reporting shown below:
Please refer to the AirVantage Documentation for specific information about each pre-defined report type.
Troubleshooting - Gateway is stuck on Installing AVTA or AVTC
Important
It is possible for an AAF application (such as AVTA or AVTC) to be stuck in the "Install application" state. If the gateway is not taking the operation after 24 hours, do not worry. You may simply follow the steps below for a resolution. Please keep in mind that the AAF applications communicate to ALMS over M3DA, not LWM2M or MSCI. This serves some importance as the check-in time configured for the device (ie, 15-minute intervals) is very different for applications. AAF applications abide by a different check-in time which is hardcoded into the ALEOS code and therefore, cannot be changed by users.
Login to AceManager and force the AAF service to connect to ALMS by navigating to Services > ALMS > AAF, and click on the red "Connect" button.
If you do not have remote access to the gateway's UI (AceManager), you can cancel the operation by clicking on the checkbox beside the "Install application" job, and selecting the Abort button at the top-right of the screen.
Once canceled, issue a new operation to reboot the gateway under Monitor > Systems.
After the gateway has been rebooted, create another ALMS ARA workflow (see step 5 in the Step-by-step guide above).
The operation should be successful the next time the gateway checks in via M3DA protocol.
To see Telemetry data (MQTT), click on the Timeline button in the device view to see the data set arrive on ALMS in real-time. This information is used by ALMS ARA to compile a report.
Important
Please note, that if the applications still stuck installing and the device in question is connected to a private network, it is possible that TCP/80 outbound is being blocked on the customer's firewall. Please see below for ALMS firewall rules:
โhttps://source.sierrawireless.com/airvantage/av/reference/register/howtos/configureInfrastructureForPrivateAPN/
Troubleshooting - Vehicle-specific telemetry data not being seen in the ALMS ARA Reports
Important
ALMS ARA compiles reports based on the telemetry data received from your devices. If you are not seeing any information in the reports, there is more than likely a problem between the vehicle and gateway that needs looking into (more specifically, the physical connection).
Please re-check the connection between the vehicle's diagnostic port and MP70's Aux I/O port.
Important
Please ensure that you select the correct setting under Direct Vehicle Bus (CAN) Data Collection. By default, this is Enabled: Connected to Ignition. If you do not have the ignition sense properly wired to your vehicle's ignition or an external switch, the MP70 may not be able to communicate with your vehicle's diagnostics port. Please refer to the Telemetry Guide for more detail: https://source.sierrawireless.com/devices/telemetry/telemetry/#sthash.LPlc2Cc5.dpbs.Change the MQTT password in ALMS to the default. You can change the ALMS MQTT password by selecting More > Edit in the device view. There is a small lock symbol to the right of Firmware & Applications. The default password is "Sierra-123". Save the configuration.
Remove all user-configured AVTA settings in the AVTA configuration, including the MQTT Password Setting. When it asks you to reboot the device, please proceed.
Upgrade the AVTA application. At the time of writing, the latest AVTA version is 1.4.1.001. If your device is already running 1.4.1.001 or a newer version, please skip this step. To upgrade the application, select the upgrade button within the Systems Applications widget for the device in question. Click Upgrade Application once you have selected the latest AVTA version:
Reboot the gateway and start the application.
Check to see if telemetry data is being received on ALMS by clicking on the AVTA application in the System Applications widget of ALMS, and selecting Telemetry data. You should see some fields pre-populated such as the Engine Speed and Fluid level, indicating that the MP70 is communicating with the vehicle bus and sending the information via MQTT.