CalAmp FOB10-BL, Руководство по аппаратному обеспечению и установке, Страница: 24 / 28

LMU->Server: Fob OTA ID Report
note right of Server: Checks fob's version against any queued\nupdates and determines if one is
available
Server->LMU: OTA Download available (App 107)
note right of LMU: Check if have file already in OTA\n flash storage.
LMU<->Server: HTTP download of A&B image (if required)
note right of Fob: FOB new version is captured
LMU<->Fob: OAD update of A/B image
note left of Fob: Validate image, reset and run
Fob->LMU: Advertisement Packet with new Fob version
note right of LMU: Connection algorithm determines\nthat it should connect to this Fob
LMU->Fob: Connect
LMU->Server: Fob OTA ID Report
note right of Server: If this is the same fob then confirms version\nis updated and marks OTA as
complete
note right of Server: Checks fob's version against any queued\nupdates and determines if one is
available
Format of Fob OTA ID report
This is the LM Direct ID report for the Bluetooth fob that is sent from the LMU to PULS.
The PULS ID report for the Bluetooth fob will use LM Direct Message type 13 which is a Device
Version Report Message. This message type was created for the Android MDT but can be reused by
changing the device type in the message body.
7 0
Options Header (optional)
…
Message Header
…
JSON Object
…
Device Version Report Message Format
The message body (following the Message Header) consists of a single JavaScript Object Notation
(JSON) object, which for the fob will contain three JSON structures. The names and contents of each
structure are summarized in the table below:
Name JSON
type
Contents
“ids” array Device type for Bluetooth fob (13),
Hardware version (key fob app id = 1),
MAC ID,
Firmware file type (0),
Firmware version