Events Protocol Reports - Sierra Wireless AirLink RV50 Series User Manual

Rev 1 Dec. 17
Note: The Reliable, Simple Reliable, and UDP Sequence SNF modes apply only to RAP
reports. For more information on SNF, see
5. Optional (location RAP Report 13 only)—Enable Report Odometer and/or
Report Digital Inputs.
6. Click Apply.
The name you assigned to the Action appears under Actions. You can click on
this at any time to modify the settings.
7. Click Events on the menu on the left and follow the instructions on
Types on page 260 to configure the Event you want associated with this
Action and to link the Action to the Event.

Events Protocol Reports

Sierra Wireless' Events Reporting protocol allows for messages to be sent to the
report server in four formats:
• 1 — Type, Length, Value (TLV)—The TLV message consists of the MSCI
ID as the type, the length of the data, and the actual data.
• 2 — Binary—A binary condensed form of the TLV message
• 3 — CSV-ASCII—An ASCII condensed and comma-delimited form of the
TLV message
• 4 — XML—An XML form of the data
Tip: Because of its flexibility and robustness, the TLV message type is recommended for
most reports using the Events Protocol. The Binary and ASCII forms do not contain a "type
field" which can result in misinterpretation of data. Since the TLV and XML forms always
include the type as well as the data, an unintentional type can be identified much easier.
To configure an Events protocol report:
1. On the Events Reporting tab, select Actions from the menu on the left.
2. Enter the desired Action Name.
3. From the drop-down menu in the Action Type field, select the desired Events
protocol report format.
255
Events Reporting Configuration
page 237.
Event
41111088