Template:TATXYZ Bluetooth® settings - Revision history

Karolis.C at 08:03, 27 August 2024

2024-08-27T08:03:42Z

← Older revision		Revision as of 11:03, 27 August 2024
Line 45:		Line 45:
	<code>AVL ID 471, value BEEF</code> - Lost BLE3 EYE Sensor.<br>		<code>AVL ID 471, value BEEF</code> - Lost BLE3 EYE Sensor.<br>
	<code>AVL ID 475, value BEEF</code> - Lost BLE4 EYE Sensor.<br>		<code>AVL ID 475, value BEEF</code> - Lost BLE4 EYE Sensor.<br>
			<br>
			{\| class="main-table" style="background: #E7F1FE; color: black;"
			{\| style="width: 800px;height: 60px; text-align: left; border: 1 px solid #0054A6; border-bottom: 1px solid #0054A6; border-left: 1px solid #0054A6;border-top: 1px solid #0054A6;border-right: 1px solid #0054A6;background: #E7F1FE; color: black; text-align: left; padding: 10px;"
			\| style="width: 40px;height: 20px;padding: 10px;" \| [[File:Note_icon.png\|30 px\|link=]]
			\|\| '''Please note:'''<br>
			If Lost Sensor Alarm is <b>disabled</b> and sensor is <b>not found during a scan</b> IO element will contain value:<br>
			* <b>32767</b> - temperature IO<br>
			* <b>65535</b> - humidity IO
			\|}
	<br>		<br>
	When EYE Sensor is configured, TAT device will automatically map data to below IO elements -<br>		When EYE Sensor is configured, TAT device will automatically map data to below IO elements -<br>

Karolis.C at 05:44, 4 April 2024

2024-04-04T05:44:24Z

← Older revision		Revision as of 08:44, 4 April 2024
Line 208:		Line 208:
	\|+		\|+
	\| 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: #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 0). 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.'''		\| 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.'''
	\|}		\|}

Karolis.C at 05:18, 4 April 2024

2024-04-04T05:18:38Z

← Older revision		Revision as of 08:18, 4 April 2024
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>

Karolis.C at 06:44, 2 April 2024

2024-04-02T06:44:00Z

← Older revision		Revision as of 09:44, 2 April 2024
Line 204:		Line 204:
	===Backup feature logic===		===Backup feature logic===

	[[File:~~TAT100_Backup_feature~~.png]]		[[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;""		{\| 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;""
	\|+		\|+

Karolis.C at 06:11, 2 April 2024

2024-04-02T06:11:58Z

@@ 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>
 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>

Karolis.C at 12:47, 26 March 2024

2024-03-26T12:47:04Z

← Older revision		Revision as of 15:47, 26 March 2024
Line 28:		Line 28:
	<br>		<br>
	<b>MAC</b> - MAC address of the universal sensor.<br>		<b>MAC</b> - MAC address of the universal sensor.<br>
	~~<br>~~		[[Image:Lost universal sensor.png\|350px\|right]]
	[[Image:Lost universal sensor.png\|~~200px~~\|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 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>
	<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.		<code>BEEF</code> - if configured data is sent as HEX number. <br><br>
	<br />		<br />

	===EYE Sensor===		===EYE Sensor===
	When EYE Sensors mode is selected MAC address of the sensor will need to be entered. ~~[[Image:TAT EYE Sensor window2.png\|200px\|none]]~~<br />		[[Image:TAT EYE Sensor window2.png\|200px\|right]]
			When EYE Sensors mode is selected MAC address of the sensor will need to be entered. <br />
	<b>MAC</b> - MAC address of the EYE Sensor.<br>		<b>MAC</b> - MAC address of the EYE Sensor.<br>
	<br>		<br>
Line 168:		Line 168:
	\|-		\|-
	\|}		\|}
			<br><br>

	===Eddystone===		===Eddystone===
			[[Image:TAT Eddystone window.png\|250px\|right]]
			When Eddysone mode is selected Namesspace and Instance IDs will be configurable. <br />
			Configuring both parameters is not mandatory. If one of the parameters is is left empty TAT will find beacons matching other provided parameter. It is also possible to configure only part of a parameter (for example only 10 Namespace ID symbols instead of 20). During BLE scan device needs to <b>find at least one beacon (even if 4 different connections are configured</b>.
			Scanning for BLE beacons is initiated every Update Frequency. Scan will take up to 60 seconds and will end early if at least one beacon is found. <br>
			<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.
			<br><br>


	===iBeacon===		===iBeacon===
			[[Image:TAT iBeacon window.png\|250px\|right]]
			When iBeacon mode is selected UUID, Major ID and Minor IDs will be configurable. <br />
			Configuring all parameters is not mandatory. If one of the parameters is is left empty TAT will find beacons matching other provided parameter. It is also possible to configure only part of a parameter (for example only 20 UUID symbols instead of 32). During BLE scan device needs to <b>find at least one beacon (even if 4 different connections are configured</b>.
			Scanning for BLE beacons is initiated every Update Frequency. Scan will take up to 60 seconds and will end early if at least one beacon is found. <br>
			<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.
			<br><br>

Karolis.C at 12:19, 26 March 2024

2024-03-26T12:19:20Z

Show changes

Karolis.C: Created page with "TOC ==BLE Feature Sensors== Allows to configure universal or EYE sensors for data reading or BLE beacons for use with Recovery mode.
Image:TAT BLE Sensor configurat..."

2024-03-26T11:40:23Z

Created page with "__TOC__ ==BLE Feature Sensors== Allows to configure universal or EYE sensors for data reading or BLE beacons for use with Recovery mode. Image:TAT BLE Sensor configurat..."

New page

__TOC__

==BLE Feature Sensors==
Allows to configure universal or EYE sensors for data reading or BLE beacons for use with Recovery mode. 
[[Image:TAT BLE Sensor configuration v4.png|250px|{{{general|size}}}|right]]
 '''BLE Feature:''' 
 <code>None</code> – Bluetooth functionality will be disabled. 
<code>Sensors</code> – Enables Bluetooth functionality for universal sensors, EYE Sensors and beacons. 
<code>Backup Tracker</code> - Enables Backup Tracker 
 
Update frequency - Sets BLE update frequency if Backup Tracker or BLE beacon is configured. Scan for universal sensors or EYE Sensors is only performed with periodic or scheduled records. To increase BLE scan frequency when using universal sensors or EYE Sensors, Operand in IO elements needs to be configured. 
 
AAS scenario - When enabled TAT device will only perform BLE scan while it is in "On Move" tracking scenario. While device is stationary BLE scan does not initiate.

===Sensor===
When Sensors mode is selected a table with configurable parameters will appear:[[Image:TAT sensors window.png|1000px|none]] 

*The table has 9 types of parameters:
*#Type – EIR data type. This parameter will indicate which type to look for and work with.
*#Data Offset – start index of data we are interested in.
*#Data Size – size of the data we are interested in. Limited to 2 bytes of data.
*#Action – two actions are possible: Match and Save. Match means that we want to perform a validation of certain data. Save means that we want to get certain data and later save it to an AVL record.
*#IO – tells which IO element's data will be saved to. '''Used only with Save action.'''
*#Match – hex string to be matched with BLE sensor data. '''Used only with Match action.'''
*#Endianness – endianness of data: little endian (ex. 0x1122) or big endian (ex. 0x2211). '''Used only with Save action.'''
*#Multiplier – value to be used to multiply output data. '''Used only with Save action.'''
*#Offset – value to be added to output data. '''Used only with Save action.''' 
 
 
MAC - MAC address of the universal sensor. 
Lost Sensor Alarm - 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. 
When universal sensor is lost TAT will send a record with even number that is the first configured IO element. In below 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). 
[[Image:Lost universal sensor.png|200px|none]] 

===EYE Sensor===
When EYE Sensors mode is selected MAC address of the sensor will need to be entered. [[Image:TAT EYE Sensor window.png|500px|none]] 
MAC - MAC address of the EYE Sensor. 
Lost Sensor Alarm - When enabled TAT device will generate a record to notify that EYE Sensor has been lost. Required to be enabled for Recovery mode trigger "Lost BLE sensor" to work. 
<code>AVL ID 463, value BEEF</code> - Lost BLE1 EYE Sensor. 
<code>AVL ID 467, value BEEF</code> - Lost BLE2 EYE Sensor. 
<code>AVL ID 471, value BEEF</code> - Lost BLE3 EYE Sensor. 
<code>AVL ID 475, value BEEF</code> - Lost BLE4 EYE Sensor. 

===Eddystone===

===iBeacon===