Data Communication and Usage

Data Communicated on a Device’s ‘Heartbeat’

This section lists the data that is communicated on the “heartbeat” between an AMM and both non-AMMER and AMMER-based ALEOS devices. For more information about AMMER see: ALEOS and MG Support .

AMMER Devices and Non-AMMER Devices

ALEOS devices with or without AMMER perform regular check-ins for which the AMM asks for three types of values: stats, configuration settings, and device states, as listed in the following three tables:

Stats Sent During Regular Checkins

Configuration Settings Sent During Regular Checkins

Device State and Other Information Sent During Regular Checkins

AMMER Devices

AMMER devices send events to the AMM as those events occur. Events can include telemetry data, GPS coordinates, WAN interface bounces, etc. For a complete list of events see: AMMER Configurable-Parameters Interface .

Note however, that even if a gateway is not moving and all network links are solid, an AMMER-based device will still send some events at regular intervals, unless those events have been disabled. For example, an AMMER-based device will send:

• GPS location, default every five minutes, even if a GPS antenna is not connected.
• GPS speed, default every one minute.
• Heartbeat, default every one minute.

Typical Data Usage

This section provides common data usage consumption values. The table below lists data usage for an RV50X running ALEOS 4.8.1.006 for 24 hours. This can be used as a guidance as to the typical data consumption that occurs when communicating with an AM/AMM server.

Note: the gateway used to collect the cellular data usage was using default settings (apart from those values altered as in the table below).

Typical Data Usage Values for an RV50X running ALEOS 4.11.1.007 for 24 hours.