Changes

1,772 bytes added , 15:07, 6 December 2023

m

Text replacement - "Bluetooth" to "Bluetooth®"

Line 10: Line 10:

The basic firmware functionality supports such generic features like sleep modes, trip detection, and different data acquisition modes that depend on ignition/movement source or even the connected GSM operator. The device supports different ignition detection modes, depending on the installation variant. Moreover, it supports such advanced functions like auto geofence, towing detection, green driving, crash event detection, virtual odometer, unplug detection, GPRS/SMS notifications and many more. The user can easily enable the function he needs using the configurator or FOTA WEB and change the configuration in accordance with the changing needs of the client.

−

Teltonika trackers also support '''BLE technology''' that significantly expands their functionality. For example, if a client wants to get more telemetric vehicle data, it is possible to connect via ~~Bluetooth~~ OBDII dongle and read such data like millage, engine hours, engine faults, fuel level, etc. Advanced BLE mode lets to configure BLE beacons and various BLE sensors (temperature, humidity, movement, etc.). BLE beacons can be used as an immobilizer or for the authentication of drivers and passengers. Another possible way of using them is to monitor assets during transportation, even for indoor tracking. By the way, it also is possible to configure a device via ~~Bluetooth~~. Teltonika provides ~~Bluetooth~~ communication protocols so that users could develop their own mobile application to read notifications in real time and do many other useful functions with their trackers.

+

Teltonika trackers also support '''BLE technology''' that significantly expands their functionality. For example, if a client wants to get more telemetric vehicle data, it is possible to connect via Bluetooth® OBDII dongle and read such data like millage, engine hours, engine faults, fuel level, etc. Advanced BLE mode lets to configure BLE beacons and various BLE sensors (temperature, humidity, movement, etc.). BLE beacons can be used as an immobilizer or for the authentication of drivers and passengers. Another possible way of using them is to monitor assets during transportation, even for indoor tracking. By the way, it also is possible to configure a device via Bluetooth®. Teltonika provides Bluetooth® communication protocols so that users could develop their own mobile application to read notifications in real time and do many other useful functions with their trackers.

==What you need for a solution?==

Line 23: Line 23:

*The [https://wiki.teltonika-gps.com/view/FMB920_First_Start#How_to_insert_Micro-SIM_card '''SIM card'''] in order to get data to your server

*[https://wiki.teltonika-gps.com/view/EYE_FAQ '''EYE BEACON/SENSOR'''] BLE sensors that can be additionally connected if necessary

−

*[https://wiki.teltonika-gps.com/view/~~How_to_connect_OBD_II_Bluetooth_Dongle_to_FMB_device~~#~~Supported_Bluetooth_OBD_II_dongles~~ '''~~Bluetooth~~ OBD II dongles'''] ~~Bluetooth~~ OBD II dongles from other manufacturers can be connected if necessary to receive data from the OBD connector

+

*[https://wiki.teltonika-gps.com/view/How_to_connect_OBD_II_Bluetooth®_Dongle_to_FMB_device#Supported_Bluetooth®_OBD_II_dongles '''Bluetooth® OBD II dongles'''] Bluetooth® OBD II dongles from other manufacturers can be connected if necessary to receive data from the OBD connector

*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device

Line 54: Line 54: −

You can also use third-party '''OBD BT dongles''' for this solution (if there is a need to get data from the vehicle's OBDII interface. You can read more about selecting the appropriate OBD BT dongle models [https://wiki.teltonika-gps.com/view/~~How_to_connect_OBD_II_Bluetooth_Dongle_to_FMB_device~~#~~Supported_Bluetooth_OBD_II_dongles~~ here].

+

You can also use third-party '''OBD BT dongles''' for this solution (if there is a need to get data from the vehicle's OBDII interface. You can read more about selecting the appropriate OBD BT dongle models [https://wiki.teltonika-gps.com/view/How_to_connect_OBD_II_Bluetooth®_Dongle_to_FMB_device#Supported_Bluetooth®_OBD_II_dongles here].

Line 190: Line 190:

[[File:Sensor settings.png|alt=|left|452x452px|thumb]]

−

*In the ~~Bluetooth~~ 4.0 section, set the operating mode for one of the 4 sensors as Advanced

+

*In the Bluetooth® 4.0 section, set the operating mode for one of the 4 sensors as Advanced

Line 224: Line 224:

! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" |Unparsed received data in hexadecimal stream

|-

−

| style="vertical-align: middle; text-align: center;" | ~~00000000000000328E010000017E065DE1B80000000000000000000000000000000000000003000300EF0000F000~~~~0187~~01~~0000000000000000010000793F~~

+

| style="vertical-align: middle; text-align: center;" | 00 00 00 00 00 00 00 32 8E 01 00 00 01 7E 06 5D E1 B8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C0 00 06 00 EF 00 00 F0 00 00 01 01 00 B3 01 00 1E 00 00 25 00 00 03 00 19 00 7D 00 56 03 25 00 24 03 84 00 00 00 03 01 4B 00 00 00 00 00 00 00 H7 01 CF 00 00 00 00 00 00 0C CB 01 D0 00 00 00 00 00 0B FF C7 00 00 01 00 00 79 3F

|}

Line 278: Line 278:

|-

| style="vertical-align: middle; text-align: center;" |1’st IO ID

−

| style="vertical-align: middle; text-align: center;" |00 EF (AVL ID 239, Name: Ignition)

+

| style="vertical-align: middle; text-align: center;" |00 EF (AVL ID 239, Name: Ignition)

|-

| style="vertical-align: middle; text-align: center;" |1’st 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;" |2’nd IO ID

−

| style="vertical-align: middle; text-align: center;" |00 F0 (AVL ID 240, Name: Movement)

+

| style="vertical-align: middle; text-align: center;" |00 F0 (AVL ID 240, Name: Movement)

|-

| style="vertical-align: middle; text-align: center;" |2’nd 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;" |3’rd IO ID

Line 317: Line 317:

|-

| style="vertical-align: middle; text-align: center;" |1’st IO ID

−

| style="vertical-align: middle; text-align: center;" |00 19 (AVL ID 25, Name: BLE Temperature #1)

+

| style="vertical-align: middle; text-align: center;" |00 19 (AVL ID 25, Name: BLE Temperature #1)

|-

| style="vertical-align: middle; text-align: center;" |1’st IO Value

−

| style="vertical-align: middle; text-align: center;" |00 7D (Temperature value 1.25 degrees Celsius)

+

| style="vertical-align: middle; text-align: center;" |00 7D (Temperature value 1.25 degrees Celsius)

|-

| style="vertical-align: middle; text-align: center;" |2’nd IO ID

−

| style="vertical-align: middle; text-align: center;" |00 56 (AVL ID 86, Name: BLE Humidity #1)

+

| style="vertical-align: middle; text-align: center;" |00 56 (AVL ID 86, Name: BLE Humidity #1)

|-

| style="vertical-align: middle; text-align: center;" |2’nd IO Value

−

| style="vertical-align: middle; text-align: center;" |03 25 (Humidity 80.5%)

+

| style="vertical-align: middle; text-align: center;" |03 25 (Humidity 80.5%)

|-

| style="vertical-align: middle; text-align: center;" |3’rd IO ID

Line 341: Line 341:

|-

| style="vertical-align: middle; text-align: center;" |1’st IO ID

−

| style="vertical-align: middle; text-align: center;" |~~00 19~~ (AVL ID 25, Name: BLE ~~Temperature~~ #1)

+

| style="vertical-align: middle; text-align: center;" |01 4B (AVL ID 331, Name: BLE 1 Custom #1)

|-

| style="vertical-align: middle; text-align: center;" |1’st IO Value

−

| style="vertical-align: middle; text-align: center;" |00 7D (~~Temperature~~ value 1.~~25 degrees Celsius~~)

+

| style="vertical-align: middle; text-align: center;" |00 00 00 00 00 00 00 H7 (Flags. Each set bit (0-7) means the presence of value (0-7).)

|-

| style="vertical-align: middle; text-align: center;" |2’nd IO ID

−

| style="vertical-align: middle; text-align: center;" |~~00 56~~ (AVL ID 86, Name: BLE ~~Humidity~~ #1)

+

| style="vertical-align: middle; text-align: center;" |01 CF (AVL ID 463, Name: BLE 1 Custom #2)

|-

| style="vertical-align: middle; text-align: center;" |2’nd IO Value

−

| style="vertical-align: middle; text-align: center;" |~~03 25~~ (~~Humidity 80.5%~~)

+

| style="vertical-align: middle; text-align: center;" |00 00 00 00 00 00 0C CB (Movement status)

|-

| style="vertical-align: middle; text-align: center;" |3’rd IO ID

−

| style="vertical-align: middle; text-align: center;" |~~00 24~~ (AVL ID 36, Name: ~~Engine RPM~~)

+

| style="vertical-align: middle; text-align: center;" |01 D0 (AVL ID 464, Name: BLE 1 Custom #3)

|-

| style="vertical-align: middle; text-align: center;" |3’rd IO Value

−

| style="vertical-align: middle; text-align: center;" |~~03 84~~ (~~Engine RPM state 900 RPM~~)

+

| style="vertical-align: middle; text-align: center;" |00 00 00 00 00 0B FF C7 (Angle. 0B – Most significant byte represents device pitch. FFC7– Two least significant bytes represent device roll.)

|-

| style="vertical-align: middle; text-align: center;" |NX of X Byte IO

Arnas.Zeb

Administrators

4,670

edits

Changes

BASIC TRACK & TRACE (view source)

Revision as of 15:07, 6 December 2023