Changes

no edit summary
Line 30: Line 30:  
[[Image:Lost universal sensor.png|350px|right]]
 
[[Image:Lost universal sensor.png|350px|right]]
 
<b>Lost Sensor Alarm</b> - When enabled TAT device will generate a record to notify that sensor has been lost. Required to be enabled for Recovery mode trigger "Lost BLE sensor" to work. <br>
 
<b>Lost Sensor Alarm</b> - When enabled TAT device will generate a record to notify that sensor has been lost. Required to be enabled for Recovery mode trigger "Lost BLE sensor" to work. <br>
When universal sensor is lost TAT will send a record with even number that is the first configured IO element. In shown example if sensor is lost device will generate a record with event ID 29 (BLE Battery #1:29). If it was configured for second sensor, record will have event ID 20 (BLE Battery #2:20). Depending on the type of IO element this AVL ID will have one of two values:<br>
+
When universal sensor is lost TAT will send a record with event number that is the first configured IO element. In shown example if sensor is lost device will generate a record with event ID 29 (BLE Battery #1:29). If it was configured for second sensor, record will have event ID 20 (BLE Battery #2:20). Depending on the type of IO element this AVL ID will have one of two values:<br>
 
<code>-4162</code> - if configured data is integer<br>
 
<code>-4162</code> - if configured data is integer<br>
 
<code>BEEF</code> - if configured data is sent as HEX number. <br><br>
 
<code>BEEF</code> - if configured data is sent as HEX number. <br><br>
Line 189: Line 189:  
If <b>no beacons are found</b> during a BLE scan, device will wake up, acquire location based on configuration and send a record to configured server. This record will have <b>event AVL ID 20014 with a value of 3</b>.<br>
 
If <b>no beacons are found</b> during a BLE scan, device will wake up, acquire location based on configuration and send a record to configured server. This record will have <b>event AVL ID 20014 with a value of 3</b>.<br>
 
This functionality can also trigger Recovery mode. Device will send lost beacon event and then go into Recovery mode.  
 
This functionality can also trigger Recovery mode. Device will send lost beacon event and then go into Recovery mode.  
<br><br>
+
<br><br><br><br><br><br>
 +
 
 +
==BLE Feature Backup Tracker==
 +
===Introduction to Backup Tracker functionality===
 +
TAT devices support a feature which allows them to work as a Backup Tracker. <br>
 +
 
 +
1. If main tracker ([[FMB_Compability_table_for_backup_tracker_feature|Compatibility table]]) is turned off, Alarm event from the TAT100 will be received and AVL 236 in the data packet will be sent.<br>
 +
2. Even if Backup tracker is in alarm mode, TAT device will continue to track its position as configured. <br>
 +
 
 +
===Topology scheme===
 +
 
 +
[[File:422705 VEHICLE BACKUP SECURITY SOLUTION TOPOLOGY 02 (1).png|center|900px]]
 +
 
 +
===Backup feature logic===
 +
 
 +
[[File:TAT_Backup_Logic.png]]
 +
{| class="wikitable" style="background: #0054A6; color: black; border: 2px #0054A6; border-bottom: 1px solid #0054A6;border-top: 1px solid #0054A6;border-left: 1px solid #0054A6;border-right: 1px solid #0054A6;""
 +
|+
 +
| style="width: auto; text-align: left; border: 1px solid #0054A6; border-bottom: 1px solid #0054A6; background: #0054A6; color: white;" |<b>NOTE:</b>
 +
| style="width: auto; text-align: left; border: 1px solid #0054A6; border-bottom: 1px solid #0054A6; background: white;" | '''If TAT does not pick up advertised data packets from main tracker, TAT100 generates and sends a record with AVL ID 236 (Value 1). After sending this record, device will wait for the next Update Frequency and will keep generating records with event ID 236 until main tracker is found again. No record is generated if main tracker can be located during a BLE scan.'''
 +
|}
 +
 
 +
{| class="wikitable"
 +
|- style="font-weight:bold;"
 +
! Parameter Name
 +
! Description
 +
! Parameter ID
 +
! Parameter Value
 +
|-
 +
| BLE Feature
 +
| Select which BLE feature is enabled.<br />Backup tracker or Sensors can be selected (not both)
 +
| 189
 +
| 0 - None<br />1 - Backup Tracker <br />2 - Sensors
 +
|-
 +
| IMEI of Central Device
 +
| IMEI of main tracker that TAT is scanning for
 +
| 190
 +
| Valid IMEI number
 +
|-
 +
| Update Frequency
 +
| Time in seconds for scanning intervals
 +
| 1100
 +
| Min 30 sec.<br />Max 65535 sec.<br />Default 120 sec.
 +
|}
 +
 
 +
 
 +
===Instructions===
 +
'''To ENABLE backup feature on TAT device:'''
 +
 
 +
# <code>Bluetooth</code> → select <code>Backup Tracker</code><br>
 +
# Enter main device (FMBxxx/TFT100/TST100/GH5200/TMT250) IMEI<br>
 +
# Set <b>Update frequency</b> – <i>(We recommend to set update frequency to >3600 sec. Frequent BLE scanning will reduce battery life.)</i><br>
 +
 
 +
[[File:TAT Backup Tracker.png|center|400px]]
 +
 
 +
'''To ENABLE backup feature on main tracker:'''
 +
 
 +
#<code>Bluetooth</code> → <code>BT Radio</code> set to <code>Enable (visible)</code><br><br>[[File:Main tracker BT on.png|center|450x]]<br>
 +
#ENABLE backup feature on:
 +
##<b>TFT100 | TST100 | GH5200 | TMT250</b> devices<br><code>Bluetooth 4.0</code> → <code>Backup Tracker</code> set to <code>Enabled</code><br><br>[[File:Main tracker BackT enable mob.png|center|500px]]<br>
 +
##<b>FMBXXX</b> devices<br><code>BLE connection control</code> needs to be set to Prohibit for <code>Backup Tracker</code> feature to become visible.<br><br>[[File:Main tracker BackT enable fmb.png|center|500px]]<br>

Navigation menu