Confidential & Proprietary Information
9.1.16.2 External Accelerometer
It is possible to use an external accelerometer and set instantaneous motion via the set motion API. This API can be used
if the accelerometer mode is set to the manual state. In this state, the internal accelerometer will be placed in a low
power state.
Reading motion via the get motion API does not return instantaneous motion as the set command does, but rather the
“In-Motion” state of the device. Thus, in order for the get motion command to return a non-zero value, the set motion
API must be called repetitively, once every two seconds at a minimum, until the continuous vibration requirement is met.
Only after that condition is met, will the get motion API return a non-zero value.
9.1.16.3 Accelerometer Sensitivity
The accelerometer can use a 2G, 4G, or 16G scale reference for acceleration detection, in addition to a sensitivity setting,
1-10, which is proportional to that scale. So, a 2G scale with a 1 sensitivity will yield the most sensitive motion detection
possible, whereas a 16G scale with a 10 sensitivity will yield the least sensitive setting.
Changes to accelerometer sensitivity occur in real-time, and events can be used to enable URC messages to quickly test
the results of sensitivity changes.
9.1.16.4 Orientation Detection
6D orientation match detection can be specified such that transitions in or out of configurable orientation states can be
identified.
9.1.16.5 Input and OTA Events
Accelerometer events can be mapped to Software Input functions (See Inputs Module Section). Events that support
active and inactive states can be mapped to count, accumulate, transition, and undesired state functions. Events that do
not support open and closed states, such as a motion event, can be mapped to count and transition functions.
Mod Msg Input Config 1-8 OTA messages make it possible to describe accelerometer events and states through OTA
messages.
9.1.17 Power Management
Power management supports 3 power states as follows:
9.1.17.1 Normal Operation
In Normal Operation, tracking occurs at the at rest and in-motion tracking intervals.
9.1.17.2 Partial Suspended
In the Partial Suspended state, tracking occurs at the low battery update interval, if the low battery update interval is less
than the normal or in-motion interval respective of the current tracking state.
9.1.17.3 Full Suspended
In the full suspended state, the tracker and transmitter are suspended and cannot be used.
9.1.17.4 Power Management State Changes
Power management state changes can be set with the Power Management Set Power State API. Based on the user’s
implementation and power architecture, the ST150M’s power state can be directed to the appropriate state.
9.1.18 Temperature Notifications
Temperature notification events can be configured for high/low temperatures on the ASIC and MCU. URCs for these
events can be enabled for visibility from external interfaces.