Table of Contents
Advertisement
9150-0126-01 R-2
B. Put the magnetic puck assembly to the stainless-steel sled dedicated circular cutout in the center of the plate, making sure the
magnetic side is facing up.
C. Install the Integrity 150 device to the sled using the four M4x12 screws that are provided with the sled. Hand tighten the screws
with a 3 mm hex Allen key. Please do not overtighten the screws.
ST CONFIGURATION
The Integrity 150 can be configured via the My IoTAccount Portal for general features. The application is primarily used to sync profiles from the
back office into the application so that they can be applied to a unit.
Refer to 9150-0127-01 Globalstar ST Configuration App User Manual for detailed examples of firmware updating and management of your devices.
MESSAGES
The Integrity 150 produces on-air messages conforming to the Globalstar specified format. Refer to 8550-0002-01 Globalstar Unified API
document for detailed examples of various message decoding.
The data being communicated to the end user is contained entirely in the 72-bit (9-byte) field. This section will describe the use of the 9-byte
user information segment for communicating the range of information that the Integrity 150 is able to convey to the user.
NOTE: User information is also referred to as the Message Payload.
GLOBAL MESSAGE TYPE
Bits 0 and 1 in the first byte of the user data defines the Global Message Type; there are four total global types. Types 0 and 3 are applicable
to the function and features of the Integrity 150, Type 1 and 2 are user defined message types.
• Type 0 - Standard Message: All the various message types that contain Latitude and Longitude data that are transmitted
by the Integrity 150 will be of this type.
• Type 1 - Truncated Message: This message type provides for up to 2 bytes plus 6 bits of user data to be appended to the
status byte and GPS location information.
• Type 2 - Raw Message: This message type provides for up to 8 bytes plus 6 bits of user data.
• Type 3 - Non-Standard Message: The Integrity 150 will use this message type for modular messages, as well as health
check message. The modular messages are recommended for new designs. Legacy message sub types include
Accumulate/Count messages, Contact Service Provider messages and Low Battery messages.
Globalstar messages can send up to 144 bytes of data per transmission, broken into 9-byte packets. Transmissions can consist of up to 16 9-byte
packets sent sequentially. The packet is the lowest discreet data element that can be sent. Messages that do not utilize the max possible length will
be automatically interleaved with other messages in the transmit queue, for better through put and lower latency.
Interleaving example: M1 is a 9-byte message queued for dispatch. By default, every message is retried 2 times. M2 is queued for dispatch after
M1 has initially been transmitted. Review below how messages will be transmitted based on defined retry intervals:
At T0, M1 transmitted
At T1, M2 transmitted, M1 first retry
At T2, M2 first retry, M1 second retry
At T3, M2 second retry
At T4, no transmission, queue is empty
Up to ten 9-byte messages can be sent in a transmission.
Integrity 150 User Manual
Confidential & Proprietary Information
11
Advertisement
Table of Contents
