Searching...

Matching results

    ALEOS Data Streaming: Heartbeat, GPS, Telemetry

    The ALEOS device can be configured to send some basic operational data to the server in a continuous stream, to maintain optimum status information and optional vehicle telemetry data. It uses an AAF application called Airlink Mobility Manager Event Reporting (AMMER) to do this. This connection is required to support Telemetry data but can be configured for Heartbeat and GPS if desired. The same application (AMMER) is used to configure the AMM Management Tunnel, but does require a higher version of the application and AMM server.

    The data streaming supports a more granular level of reporting detail in AMM deployments when GPS is streamed to the server.

    Additional Information:

    • Device Limitations and Server Requirements for Data Streaming
      • ALEOS devices must be running ALEOS version 4.8.0 or higher with AAF application support. This feature is not supported on systems for which the minimum required ALEOS version is not available.
      • The AMM server version must be a minimum of 2.16.0.1 or higher to support the data streaming feature (the AAF application is not distributed with earlier server images).
    • Configuration Steps for Data Streaming

      To set up data streaming from the ALEOS device:

      1. Ensure that AAF is enabled (MSCIID 10250=1; this change does not require reboot to take effect).
      2. On the AirLink Manager server, navigate to Admin -> Software -> Distribution, select the desired devices, and click the Install/Upgrade Application(s) button. Select the AMMER application and the latest version.
        • This procedure will perform a first-time installation as well as application upgrade.
        • Only one application can be installed at a time, and the device must be rebooted in order for the application to be initialized. More than one application may be installed prior to rebooting the device to make them active.
      3. Schedule the installation if desired; otherwise it will download and install immediately when the device checks in.
      4. Once the desired application(s) are installed, right-click on the device in the navigation tree and select Request reboot.
      5. After the reboot, on the AMM server, navigate to Configuration -> Deployment -> Configuration Control, and select the affected devices. Click on the Revert button. This will update the server’s collection of those devices’ configuration files. Once the check-in is completed, the ammerconfig file will appear as part of the collection of configuration files.
      6. If you want to modify the default settings, it is recommended that you make the changes to the configuration file on one unit and then copy that configuration file to the rest of the fleet using the AirLink Manager’s Copy Configuration feature. To edit the configuration file, click on the Click to display files… link in the Files column.

      Note: If you do not see the Click to display files link, contact your server administrator for the *Configuration/Deployment/Configuration Control/Files access privilege. It must follow the Configuration/Deployment/Configuration Control access privilege.

       Double click on the ammerconfig file and make the desired edits in the editor pane. For more information see: AMMER Support and Configuration.

    • For a list of related ports and protocols for this functionality see: ALEOS Gateways Firewall Port Summary.
    TOP