Table of Contents
Advertisement
9150-0125-01 R-4
9.1
MESSAGES
The Messages module is used to read and set properties on all over-the-air (OTA) message profiles. OTA message profiles
are consumed by the application and map UAPI module events and sequences of events into OTA messages.
Legacy messages are intended for backwards compatibility with previous Globalstar products. Modular messages allow
for future scalability and payload customization by use of a configuration byte for each modular message profile. For
example, a Device Reset event can send a Modular Turned On Message that includes UTC time from the Modular
Message UTC Time profile and custom raw payload. It could also be configured to send a device turned on message that
includes the Modular Message GPS Position data with speed/heading/accuracy data.
Modular messages may include more than one contained message type, and always includes a status byte for each
contained message to indicate how to parse the payload for each contained message. When decoding the message on
the backoffice, it is necessary to interrogate the status byte of each included message to properly decode the payload
that follows.
The available OTA message profiles include the following:
•
Type 0 Subtype 0-5 Standard Message: Legacy GPS/Input 1 & 2/Vibration info
•
Type 0 Subtype 6 Speed and Heading: Legacy Speed/Heading/Input1 & 2 info
Type 1 Truncated: Legacy GPS + raw message
•
Type 1 Subtype 59 Sensor Truncated No Timestamp: Smart 1 Sensor Message with GPS info
•
Type 1 Subtype 63 Sensor Truncated With Timestamp: Smart 1 Sensor message with GPS info and timestamp
•
•
Type 2 Raw Message: Raw message
•
Type 2 Subtype 59 Sensor Raw No Timestamp: Smart 1 Raw Sensor Message
•
Type 2 Subtype 63 Sensor Raw With Timestamp: Smart 1 Raw Sensor Message With Timestamp
•
Type 3 Subtype 24 Count Accumulate: Legacy count/accumulate info for Input 1/2
Type 3 Subtype 0-20 Modular Messages:
•
o Mod Msg Turned On: Device Turned On Message
o Mod Msg UTC Time: UTC timestamp message
o Mod Msg UTC Time Sensor: Reserved for future use
o Mod Msg GPS Position Track: Used by the track application
o Mod Msg GPS Pos Track Non Maskable: Used by non-maskable track application (ie: SOS mode)
o Mod Msg GPS Pos General: General GPS position profile that can be used by non-track and non-sensor
uses, such as for a device turned-on message, inputs 1-8, and time-of-day/interval messages
o Mod Msg GPS Pos Sensor: Reserved for future use
o Mod Msg Input Config 1-8: Customizable input OTA messages that can be mapped to software inputs 1-8
and include count, accumulate, state, and transition info
•
Type 3 Subtype 31 Health Check: Used to send diagnostics information about the device. Message is required to
send at least once a month, but may be sent more frequently. If only one message is sent per month, no usage
charge is incurred.
9.1.1
Message Priority
Each message type has a configurable priority, 1 (lowest) – 3 (highest), with the exception of raw and truncated
messages. Raw and truncated message priorities are specified on a per-message basis for the message being queued into
the transmit queue (See Transmit Queue)
9.1.2
Burst Count
The burst count specifies how many times a message should attempt transmission. This is required for transmit-only IoT
satellite transmissions since message delivery success cannot be determined by the transmitter.
ST150M User Manual
Confidential & Proprietary Information
55
Advertisement
Table of Contents
