Spireon Flex2-L, Руководство пользователя

Страница: 6 / 9

6
FLEX2-L is programmed and configured either via the serial UART connection or via
anOver the Air (OTA) process on the cellular data network.
A Device Manager Server on the Positioning Universal infrastructure automatically
updates Applications and Settings files for groups of devices. When an updateof the
application or new settingsare released, they are loaded into the DMAN server and assigned
to the Groups of devices that are to receive the update. The DMAN server automatically
updates devices to the latest assigned versions. In normal operation, devices “check in” to
the DMAN server regularly to report their health, and to check whether they are due to get
updates.
2) Applications
The application provides standard tracking functionality to the FLEX2-L. The specific
operation and variations in behavior are provided via parameters included in a Settings file.
These parameter values may vary depending on the nature of the specific tracking
application that the device is employed in.
The Tracking Application is software developed to run on the VSM550 device family
and provide functions that are typically used in vehicle and asset tracking. Updates to the
application are provided by Positioning Universal to provide improvements, corrections,
and add new functionality when it is ready for release.
7 Tracking Behavior Summary
FLEX2-L applications address the needs of typical vehicle and asset tracking. Variations
in functional behavior for specific applications is controlled via parameters in the settings
file.
1) Power State Reporting
The FLEX2-L can be configured to report power up and rebooting behavior in a variety
of ways depending on what is desired. Cold Boot, Warm Boot, and first GPS Acquisition are
reported if so configured following Power Up events, power cycling, commanded reboots,
and configured periodic reboots. In addition, there is an option to report a Stop event
following a reboot of a non-moving device to address some customer needs to ensure that
the corner case of a reboot occurring at the end of a trip doesn’t result in an error in trip or
idle reporting by the server.