202
edits
Changes
no edit summary
==Introduction to Backup Tracker functionality==
==Introduction to Backup Tracker functionality==
FMB+FMB Backup Tracker is a new feature which allows to transform device's work-mode to work as a backup tracker.<br>
FMB+FMB Backup Tracker is a new feature which allows to transform device's work-mode to work as a backup tracker.<br>
Each backup tracker's scan cycle lasts up to 60 seconds. If during those 60 seconds the Backup tracker is:
Each backup tracker's scan cycle lasts up to 60 seconds. If during those 60 seconds the Backup tracker is:
* Able to catch 15 valid Main tracker packets, the scan will stop and the device will wait for next cycle to start.
* Able to catch 15 valid Main tracker packets, the scan will stop and the device will wait for next cycle to start.
* Unable to catch at least 15 valid Main tracker packets, an alarm record will be generated with AVL ID 1153. After '''delay timeout (s)''' is reached, device will send that generated record to the server and enable other record generation/sending (Periodic and Eventual record).
* Unable to catch at least 15 valid Main tracker packets, an alarm record will be generated with AVL ID 1153. After '''delay timeout (s)''' is reached, device will send that generated record to the server and enable other record generation/sending (Periodic and Eventual record).
<br>
<br>
[[File:Backup feature logic.png|1000px]]
[[File:Backup feature logic.png|1000px]]
<br>
<br><br>
==Limitations==
==Backup functionality logic==
[[File:Backup tracker flowchart.jpg]]
Each time the device is starts up or gets reconfigured, it checks if either main or backup tracker modes are enabled on the current configuration.<br>
Both modes have some common initialization procedures:
* Check if '''Sleep Mode''' (ID: 102) is configured to '''Ultra Sleep''' (4). If it is, set '''Sleep Mode''' to '''Disabled''' (0). This means that both tracker modes overwrite configured '''Ultra Sleep''' mode and it‘s impossible to use Ultra Sleep mode with this functionality enabled;
* '''Non stop scanning''' (ID: 1115) is set '''Disable''' (0);
* '''BLE connection control''' (ID: 1112) is set to '''Prohibit''' (0);
* All '''BLE connectionless functionalities''' are set to '''Disabled''' (0).
Then, both modes have some unique initialization procedures (specific to the tracker mode):
Main tracker mode:
* '''Beacon Detection''' (ID: 134) is set to '''Disabled''' (0);
* BLE packet sending gets initialized and works according to flowchart.
Backup tracker mode:
* '''Beacon Detection''' (ID: 134) is set to '''All''' (1);
* All record generation is disabled. This means that if the device is not detecting the main tracker and starts generating records, it can be reconfigured or hard reset, and it will only start generating records again after the next failed scan (aka after next alarm record).
* Record sending is queued up to stop. Device waits for any currently queued up record sending to finish, so there might be a delay for this full record sending stop to occur.
'''<big>Packet format</big>'''<br>
[[File:Packet format.jpg]]
[[File:Packet format.jpg]]
{| class="wikitable"
{| class="wikitable"
|-
|-
|}
|}
===Limitations===
Since the feature relies on Bluetooth functionality, all of the existing Bluetooth limitations are applied.
One of such limitations is the fact that FMB devices only store up to 100 BLE devices per scan. This means, that if there are more than 100 BLE devices in the surrounding environment, backup tracker being able to catch main tracker packets in time gets reduced.