TEMPERATURE TRACKING WITH BLE SENSORS - Revision history

Arnas.Zeb: Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

2023-12-28T13:28:06Z

Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

← Older revision		Revision as of 16:28, 28 December 2023
Line 1:		Line 1:
	==''INTRO''==		==''INTRO''==
	The temperature tracking and monitoring industry has a multi-billion-dollar economic and environmental impact worldwide. It is constantly changing and adapting to growing consumer demands. But to remain competitive and profitable, cold chain logistics fleets have to look for innovative and efficient solutions. ~~Bluetooth~~ technology, combined with vehicle GPS trackers and sensors, opens up new possibilities for fleet and cargo monitoring.		The temperature tracking and monitoring industry has a multi-billion-dollar economic and environmental impact worldwide. It is constantly changing and adapting to growing consumer demands. But to remain competitive and profitable, cold chain logistics fleets have to look for innovative and efficient solutions. Bluetooth® technology, combined with vehicle GPS trackers and sensors, opens up new possibilities for fleet and cargo monitoring.

	== Solution description ==		== Solution description ==
	To solve the challenges mentioned above, we use the SPECIAL category GPS tracker FMB140 or other FMB EYE Sensor - the brand-new BLE based Teltonika accessory with smart features and extensive functionality set including ID signal transmission, temperature, humidity, and internal battery level tracking.		To solve the challenges mentioned above, we use the SPECIAL category GPS tracker FMB140 or other FMB EYE Sensor - the brand-new BLE based Teltonika accessory with smart features and extensive functionality set including ID signal transmission, temperature, humidity, and internal battery level tracking.

	'''How it works''' - the FMB models is based on the FMB platform and supports wireless ~~Bluetooth~~ LE connectivity, so it can effectively communicate with ~~Bluetooth~~ devices such as sensors. To ensure the best results, the tracker should be installed in a cold chain vehicle and configured the usual way in the spot where its ~~Bluetooth~~ antenna is not covered by bulky metal parts nearby.		'''How it works''' - the FMB models is based on the FMB platform and supports wireless Bluetooth® LE connectivity, so it can effectively communicate with Bluetooth® devices such as sensors. To ensure the best results, the tracker should be installed in a cold chain vehicle and configured the usual way in the spot where its Bluetooth® antenna is not covered by bulky metal parts nearby.

	The compact and lightweight EYE Sensor has to be attached to temperature-sensitive cargo items to be tracked and monitored - the protective bag, outer corrugated carton, container, barrel, pallet, etc. Vehicle GPS tracker receives readings from each sensor over the air at configurable intervals and sends this data as iBeacon or Eddystone profile to a server for analysis combined with the actual temperature, humidity, and its GNSS location details.		The compact and lightweight EYE Sensor has to be attached to temperature-sensitive cargo items to be tracked and monitored - the protective bag, outer corrugated carton, container, barrel, pallet, etc. Vehicle GPS tracker receives readings from each sensor over the air at configurable intervals and sends this data as iBeacon or Eddystone profile to a server for analysis combined with the actual temperature, humidity, and its GNSS location details.
Line 70:		Line 70:
	'''Step 2:''' Configure FM device using Teltonika configurator:		'''Step 2:''' Configure FM device using Teltonika configurator:

	#In [[FMB120 ~~Bluetooth~~ settings\|~~Bluetooth~~]] settings Enable ~~Bluetooth~~, set this setting as either "Enable (hidden)" or "Enable (visible)", otherwise ~~Bluetooth~~ will be disabled;		#In [[FMB120 Bluetooth® settings\|Bluetooth®]] settings Enable Bluetooth®, set this setting as either "Enable (hidden)" or "Enable (visible)", otherwise Bluetooth® will be disabled;
	#In [[FMB120 ~~Bluetooth~~ 4.0 settings\|~~Bluetooth~~ 4.0]] settings:		#In [[FMB120 Bluetooth® 4.0 settings\|Bluetooth® 4.0]] settings:
	##set Non Stop Scan to "Disable", configure "Update Frequency" and "Scan duration" as 30 seconds. These settings will bring the best results for BLE scanning with our device;		##set Non Stop Scan to "Disable", configure "Update Frequency" and "Scan duration" as 30 seconds. These settings will bring the best results for BLE scanning with our device;
	##In [[FMB120 ~~Bluetooth~~ 4.0 settings#Advanced%20Mode\|~~Bluetooth~~ 4.0 settings Advanced Mode Settings]] Load EYE Sensor preset according to packet settings in EYE app(if you do not have preset you can download them from below table)		##In [[FMB120 Bluetooth® 4.0 settings#Advanced%20Mode\|Bluetooth® 4.0 settings Advanced Mode Settings]] Load EYE Sensor preset according to packet settings in EYE app(if you do not have preset you can download them from below table)

Kirilbelinsky at 07:44, 18 July 2023

2023-07-18T07:44:27Z

← Older revision		Revision as of 10:44, 18 July 2023
Line 59:		Line 59:
	<br />		<br />
	<br />		<br />

Kirilbelinsky at 15:25, 2 December 2022

2022-12-02T15:25:40Z

Show changes

Kirilbelinsky at 15:24, 2 December 2022

2022-12-02T15:24:16Z

← Older revision		Revision as of 18:24, 2 December 2022
Line 56:		Line 56:
	*<span style="background-color:#d4b991;">2006</span> – Data sending protocol (0 – TCP, 1 – UDP)		*<span style="background-color:#d4b991;">2006</span> – Data sending protocol (0 – TCP, 1 – UDP)
	<br />		<br />



	==== '''2.1 Configuring BLE Sensors''' ====		==== '''2.1 Configuring BLE Sensors''' ====

Kirilbelinsky at 15:23, 2 December 2022

2022-12-02T15:23:28Z

← Older revision		Revision as of 18:23, 2 December 2022
Line 56:		Line 56:
	*<span style="background-color:#d4b991;">2006</span> – Data sending protocol (0 – TCP, 1 – UDP)		*<span style="background-color:#d4b991;">2006</span> – Data sending protocol (0 – TCP, 1 – UDP)
	<br />		<br />

			==== '''2.1 Configuring BLE Sensors''' ====
			'''Step 1:''' Check EYE App Settings:

			# Make sure that name of the sensor is default length (10 symbols) in [[EYE SENSOR / BTSMP1#Configure%20window\|EYE App Basic Configuration window]]
			# Note what Packet settings you have set in [[EYE SENSOR / BTSMP1#Configure%20window\|EYE App Basic Configuration window]]

			'''Step 2:''' Configure FM device using Teltonika configurator:

			# In [[FMB120 Bluetooth settings\|Bluetooth]] settings Enable Bluetooth, set this setting as either "Enable (hidden)" or "Enable (visible)", otherwise Bluetooth will be disabled;
			# In [[FMB120 Bluetooth 4.0 settings\|Bluetooth 4.0]] settings:
			## set Non Stop Scan to "Disable", configure "Update Frequency" and "Scan duration" as 30 seconds. These settings will bring the best results for BLE scanning with our device;
			## In [[FMB120 Bluetooth 4.0 settings#Advanced%20Mode\|Bluetooth 4.0 settings Advanced Mode Settings]] Load EYE Sensor preset according to packet settings in EYE app(if you do not have preset you can download them from below table)

Kirilbelinsky at 14:42, 2 December 2022

2022-12-02T14:42:55Z

← Older revision		Revision as of 17:42, 2 December 2022
Line 56:		Line 56:
	*<span style="background-color:#d4b991;">2006</span> – Data sending protocol (0 – TCP, 1 – UDP)		*<span style="background-color:#d4b991;">2006</span> – Data sending protocol (0 – TCP, 1 – UDP)
	<br />		<br />

Kirilbelinsky: /* Parsing information */

2022-12-02T14:42:02Z

Parsing information

← Older revision		Revision as of 17:42, 2 December 2022
Line 56:		Line 56:
	*<span style="background-color:#d4b991;">2006</span> – Data sending protocol (0 – TCP, 1 – UDP)		*<span style="background-color:#d4b991;">2006</span> – Data sending protocol (0 – TCP, 1 – UDP)
	<br />		<br />

Kirilbelinsky at 14:41, 2 December 2022

2022-12-02T14:41:38Z

← Older revision		Revision as of 17:41, 2 December 2022
Line 57:		Line 57:
	<br />		<br />

	== Parsing information ==
			==Parsing information==

	==='''1.Prerequisites:'''===		==='''1.Prerequisites:'''===
Line 118:		Line 119:
	\| style="vertical-align: middle; text-align: center;" \|00		\| style="vertical-align: middle; text-align: center;" \|00
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|N of Total ID		\| style="vertical-align: middle; text-align: center;" \| N of Total ID
	\| style="vertical-align: middle; text-align: center;" \|1F		\| style="vertical-align: middle; text-align: center;" \|1F
	\|-		\|-

Kirilbelinsky at 14:39, 2 December 2022

2022-12-02T14:39:49Z

Kirilbelinsky at 14:37, 2 December 2022

2022-12-02T14:37:59Z

Show changes

← Older revision		Revision as of 17:39, 2 December 2022
Line 57:		Line 57:
	<br />		<br />

	==Parsing information==		== Parsing information ==

	==='''1.Prerequisites:'''===		==='''1.Prerequisites:'''===

	==== 1.1. Open [https://wiki.teltonika-gps.com/view/Opening_TCP/UDP_port TCP/UDP port]====		====1.1. Open [https://wiki.teltonika-gps.com/view/Opening_TCP/UDP_port TCP/UDP port]====

	==== 1.2. Read Java parser [https://wiki.teltonika-gps.com/view/Java_Parser_First_Start_Guide first start guide]====		====1.2. Read Java parser [https://wiki.teltonika-gps.com/view/Java_Parser_First_Start_Guide first start guide]====

	=== '''2. Parsing example:''' ===		==='''2. Parsing example:'''===
	{\| class="nd-othertables_2" style="width:100%;"		{\| class="nd-othertables_2" style="width:100%;"
	! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" \|Unparsed received data in hexadecimal stream		! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" \|Unparsed received data in hexadecimal stream
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \| 000000000000008F080100000177B0A5F838000000000000000000004400280D0000001F09EF00F0001504B301B40051005200590098000B42307443		\| style="vertical-align: middle; text-align: center;" \|000000000000008F080100000177B0A5F838000000000000000000004400280D0000001F09EF00F0001504B301B40051005200590098000B42307443
	0F8244000011001812002D13FFE85400BE5500005A0000970000A800000AF10000601A53000000005703CB6B986400002E		0F8244000011001812002D13FFE85400BE5500005A0000970000A800000AF10000601A53000000005703CB6B986400002E
	97660000000069023B33856B000065B27B000000007D00000000BD000000000184<span style="background:#0b9768">0080000030000005</span>0100005C92		97660000000069023B33856B000065B27B000000007D00000000BD000000000184<span style="background:#0b9768">0080000030000005</span>0100005C92
Line 79:		Line 79:
	! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" \|HEX Code Part		! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" \|HEX Code Part
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \| Zero Bytes		\| style="vertical-align: middle; text-align: center;" \|Zero Bytes
	\| style="vertical-align: middle; text-align: center;" \|00 00 00 00		\| style="vertical-align: middle; text-align: center;" \|00 00 00 00
	\|-		\|-
Line 94:		Line 94:
	\| style="vertical-align: middle; text-align: center;" \|00 00 01 77 B0 A5 F8 38 (Thursday, February 18, 2021 3:43:00 PM GMT+02:00)		\| style="vertical-align: middle; text-align: center;" \|00 00 01 77 B0 A5 F8 38 (Thursday, February 18, 2021 3:43:00 PM GMT+02:00)
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \| Priority		\| style="vertical-align: middle; text-align: center;" \|Priority
	\| style="vertical-align: middle; text-align: center;" \|00		\| style="vertical-align: middle; text-align: center;" \|00
	\|-		\|-
Line 136:		Line 136:
	\| style="vertical-align: middle; text-align: center;" \|00		\| style="vertical-align: middle; text-align: center;" \|00
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \| 3’rd IO ID		\| style="vertical-align: middle; text-align: center;" \|3’rd IO ID
	\| style="vertical-align: middle; text-align: center;" \|15 (AVL ID: 21, Name: GSM Signal)		\| style="vertical-align: middle; text-align: center;" \|15 (AVL ID: 21, Name: GSM Signal)
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \| 3’rd IO Value		\| style="vertical-align: middle; text-align: center;" \|3’rd IO Value
	\| style="vertical-align: middle; text-align: center;" \|04		\| style="vertical-align: middle; text-align: center;" \|04
	\|-		\|-
Line 152:		Line 152:
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|5'th IO Value		\| style="vertical-align: middle; text-align: center;" \|5'th IO Value
	\| style="vertical-align: middle; text-align: center;" \| 00		\| style="vertical-align: middle; text-align: center;" \|00
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|6'th IO ID		\| style="vertical-align: middle; text-align: center;" \|6'th IO ID
Line 158:		Line 158:
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|6'th IO Value		\| style="vertical-align: middle; text-align: center;" \|6'th IO Value
	\| style="vertical-align: middle; text-align: center;" \| 00		\| style="vertical-align: middle; text-align: center;" \|00
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|7'th IO ID		\| style="vertical-align: middle; text-align: center;" \|7'th IO ID
Line 178:		Line 178:
	\| style="vertical-align: middle; text-align: center;" \|00		\| style="vertical-align: middle; text-align: center;" \|00
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \| N2 of Two Byte IO		\| style="vertical-align: middle; text-align: center;" \|N2 of Two Byte IO
	\| style="vertical-align: middle; text-align: center;" \|0B		\| style="vertical-align: middle; text-align: center;" \|0B
	\|-		\|-
Line 211:		Line 211:
	\| style="vertical-align: middle; text-align: center;" \|0F 8A		\| style="vertical-align: middle; text-align: center;" \|0F 8A
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \| 6'th IO ID		\| style="vertical-align: middle; text-align: center;" \|6'th IO ID
	\| style="vertical-align: middle; text-align: center;" \|13 (AVL ID: 19, Name: Axis Z)		\| style="vertical-align: middle; text-align: center;" \|13 (AVL ID: 19, Name: Axis Z)
	\|-		\|-
Line 254:		Line 254:
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|1’st IO Value		\| style="vertical-align: middle; text-align: center;" \|1’st IO Value
	\| style="vertical-align: middle; text-align: center;" \| 00 00 60 1A		\| style="vertical-align: middle; text-align: center;" \|00 00 60 1A
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|2’nd IO ID		\| style="vertical-align: middle; text-align: center;" \|2’nd IO ID
Line 335:		Line 335:
	*1) 100000000000000000000000001<span style="background:#0b9768">1</span>0000000000000000000000000101		*1) 100000000000000000000000001<span style="background:#0b9768">1</span>0000000000000000000000000101
	*2) 100000000000000000000000000<span style="background:#d4f991">0</span>0000000000000000000000000101		*2) 100000000000000000000000000<span style="background:#d4f991">0</span>0000000000000000000000000101
	If car is locked value is <span style="background:#0b9768>1</span> and if car is unlocked value is <span style="background:#d4f991">0</span>		If car is locked value is <span style="background:#0b9768">1</span> and if car is unlocked value is <span style="background:#d4f991">0</span>

	To test the car unlocking and locking use these GPRS commands		To test the car unlocking and locking use these GPRS commands