BASIC TRACK & TRACE - Revision history

Arnas.Zeb: Text replacement - "Bluetooth" to "Bluetooth®"

2023-12-06T12:07:29Z

Text replacement - "Bluetooth" to "Bluetooth®"

← Older revision		Revision as of 15:07, 6 December 2023
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.		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?==		==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		*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/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<br />		*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device<br />

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].

	<br>		<br>
Line 190:		Line 190:
	[[File:Sensor settings.png\|alt=\|left\|452x452px\|thumb]]		[[File:Sensor settings.png\|alt=\|left\|452x452px\|thumb]]
	<br />		<br />
	*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
	<br />		<br />
	<br />		<br />

Jonas.sterbavicius: Text replacement - "Bluetooth®" to "Bluetooth"

2023-10-27T13:44:53Z

Text replacement - "Bluetooth®" to "Bluetooth"

← Older revision		Revision as of 16:44, 27 October 2023
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.		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?==		==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		*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/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<br />		*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device<br />

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].

	<br>		<br>
Line 190:		Line 190:
	[[File:Sensor settings.png\|alt=\|left\|452x452px\|thumb]]		[[File:Sensor settings.png\|alt=\|left\|452x452px\|thumb]]
	<br />		<br />
	*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
	<br />		<br />
	<br />		<br />

Jonas.sterbavicius: Text replacement - "Bluetooth" to "Bluetooth®"

2023-10-27T13:07:14Z

Text replacement - "Bluetooth" to "Bluetooth®"

← Older revision		Revision as of 16:07, 27 October 2023
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.		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?==		==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		*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/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<br />		*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device<br />

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].

	<br>		<br>
Line 190:		Line 190:
	[[File:Sensor settings.png\|alt=\|left\|452x452px\|thumb]]		[[File:Sensor settings.png\|alt=\|left\|452x452px\|thumb]]
	<br />		<br />
	*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
	<br />		<br />
	<br />		<br />

Jonas.sterbavicius: Text replacement - "Bluetooth®" to "Bluetooth"

2023-10-27T12:58:45Z

Text replacement - "Bluetooth®" to "Bluetooth"

← Older revision		Revision as of 15:58, 27 October 2023
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.		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?==		==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		*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/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<br />		*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device<br />

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].

	<br>		<br>
Line 190:		Line 190:
	[[File:Sensor settings.png\|alt=\|left\|452x452px\|thumb]]		[[File:Sensor settings.png\|alt=\|left\|452x452px\|thumb]]
	<br />		<br />
	*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
	<br />		<br />
	<br />		<br />

Jonas.sterbavicius: Text replacement - "Bluetooth" to "Bluetooth®"

2023-10-27T12:45:50Z

Text replacement - "Bluetooth" to "Bluetooth®"

← Older revision		Revision as of 15:45, 27 October 2023
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.		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?==		==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		*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/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<br />		*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device<br />

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].

	<br>		<br>
Line 190:		Line 190:
	[[File:Sensor settings.png\|alt=\|left\|452x452px\|thumb]]		[[File:Sensor settings.png\|alt=\|left\|452x452px\|thumb]]
	<br />		<br />
	*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
	<br />		<br />
	<br />		<br />

AndrewBakalov at 08:59, 4 November 2022

2022-11-04T08:59:44Z

AndrewBakalov at 08:57, 4 November 2022

2022-11-04T08:57:39Z

← Older revision		Revision as of 11:57, 4 November 2022
Line 224:		Line 224:
	! 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;" \| 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 <span style="background:#0b9768">00 EF</span> <span style="background:#~~0b9768~~">00</span> <span style="background:#0b9768">00 F0</span> <span style="background:#~~0b9768~~">00</span> <span style="background:#0b9768">00 01</span> <span style="background:#~~0b9768~~">01</span> <span style="background:#0b9768">00 B3</span> <span style="background:#~~0b9768~~">01</span> <span style="background:#0b9768">00 1E</span> <span style="background:#~~0b9768~~">00</span> <span style="background:#0b9768">00 25</span> <span style="background:#~~0b9768~~">00</span> 00 03 <span style="background:#0b9768">00 19</span> <span style="background:#~~0b9768~~">00 7D</span> <span style="background:#0b9768">00 56</span> <span style="background:#~~0b9768~~">03 25</span> <span style="background:#0b9768">00 24</span><span style="background:#d4f991"> 03 84 </span> 00 00 00 03 <span style="background:#~~d4f991~~">01 4B</span> <span style="background:#d4f991">00 00 00 00 00 00 00 H7</span> <span style="background:#~~d4f991~~">01 CF</span> <span style="background:#d4f991">00 00 00 00 00 00 0C CB</span> <span style="background:#0b9768">01 D0</span> <span style="background:#d4f991">00 00 00 00 00 0B FF C7</span> 00 00 01 00 00 79 3F		\| 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 <span style="background:#0b9768">00 EF</span> <span style="background:#d4f991">00</span> <span style="background:#0b9768">00 F0</span> <span style="background:#d4f991">00</span> <span style="background:#0b9768">00 01</span> <span style="background:#d4f991">01</span> <span style="background:#0b9768">00 B3</span> <span style="background:#d4f991">01</span> <span style="background:#0b9768">00 1E</span> <span style="background:#d4f991">00</span> <span style="background:#0b9768">00 25</span> <span style="background:#d4f991">00</span> 00 03 <span style="background:#0b9768">00 19</span> <span style="background:#d4f991">00 7D</span> <span style="background:#0b9768">00 56</span> <span style="background:#d4f991">03 25</span> <span style="background:#0b9768">00 24</span><span style="background:#d4f991"> 03 84 </span> 00 00 00 03 <span style="background:#0b9768">01 4B</span> <span style="background:#d4f991">00 00 00 00 00 00 00 H7</span> <span style="background:#0b9768">01 CF</span> <span style="background:#d4f991">00 00 00 00 00 00 0C CB</span> <span style="background:#0b9768">01 D0</span> <span style="background:#d4f991">00 00 00 00 00 0B FF C7</span> 00 00 01 00 00 79 3F

	\|}		\|}

AndrewBakalov at 08:52, 4 November 2022

2022-11-04T08:52:47Z

← Older revision		Revision as of 11:52, 4 November 2022
Line 224:		Line 224:
	! 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;" \| 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 <span style="background:#0b9768">00 EF</span> <span style="background:#0b9768">00</span> <span style="background:#0b9768">00 F0</span> <span style="background:#0b9768">00</span> <span style="background:#0b9768">00 01</span> <span style="background:#0b9768">01</span> <span style="background:#0b9768">00 B3</span> <span style="background:#0b9768">01</span> <span style="background:#0b9768">00 1E</span> <span style="background:#0b9768">00</span> <span style="background:#0b9768">00 25</span> <span style="background:#0b9768">00</span> 00 03 <span style="background:#0b9768">00 19</span> <span style="background:#0b9768">00 7D</span> <span style="background:#0b9768">00 56</span> <span style="background:#0b9768">03 25</span> <span style="background:#0b9768">00 24</span><span style="background:#d4f991"> 03 84 </span> 00 00 00 03 01 4B 00 00 00 00 00 00 00 H7 01 CF 00 00 00 00 00 00 0C CB <span style="background:#0b9768">01 D0</span> <span style="background:#d4f991">00 00 00 00 00 0B FF C7</span> 00 00 01 00 00 79 3F		\| 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 <span style="background:#0b9768">00 EF</span> <span style="background:#0b9768">00</span> <span style="background:#0b9768">00 F0</span> <span style="background:#0b9768">00</span> <span style="background:#0b9768">00 01</span> <span style="background:#0b9768">01</span> <span style="background:#0b9768">00 B3</span> <span style="background:#0b9768">01</span> <span style="background:#0b9768">00 1E</span> <span style="background:#0b9768">00</span> <span style="background:#0b9768">00 25</span> <span style="background:#0b9768">00</span> 00 03 <span style="background:#0b9768">00 19</span> <span style="background:#0b9768">00 7D</span> <span style="background:#0b9768">00 56</span> <span style="background:#0b9768">03 25</span> <span style="background:#0b9768">00 24</span><span style="background:#d4f991"> 03 84 </span> 00 00 00 03 <span style="background:#d4f991">01 4B</span> <span style="background:#d4f991">00 00 00 00 00 00 00 H7</span> <span style="background:#d4f991">01 CF</span> <span style="background:#d4f991">00 00 00 00 00 00 0C CB</span> <span style="background:#0b9768">01 D0</span> <span style="background:#d4f991">00 00 00 00 00 0B FF C7</span> 00 00 01 00 00 79 3F

	\|}		\|}

AndrewBakalov at 08:50, 4 November 2022

2022-11-04T08:50:51Z

← Older revision		Revision as of 11:50, 4 November 2022
Line 224:		Line 224:
	! 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;" \| 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 <span style="background:#0b9768">00 24</span><span style="background:#d4f991"> 03 84 </span> 00 00 00 03 01 4B 00 00 00 00 00 00 00 H7 01 CF 00 00 00 00 00 00 0C CB <span style="background:#0b9768">01 D0</span> <span style="background:#d4f991">00 00 00 00 00 0B FF C7</span> 00 00 01 00 00 79 3F		\| 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 <span style="background:#0b9768">00 EF</span> <span style="background:#0b9768">00</span> <span style="background:#0b9768">00 F0</span> <span style="background:#0b9768">00</span> <span style="background:#0b9768">00 01</span> <span style="background:#0b9768">01</span> <span style="background:#0b9768">00 B3</span> <span style="background:#0b9768">01</span> <span style="background:#0b9768">00 1E</span> <span style="background:#0b9768">00</span> <span style="background:#0b9768">00 25</span> <span style="background:#0b9768">00</span> 00 03 <span style="background:#0b9768">00 19</span> <span style="background:#0b9768">00 7D</span> <span style="background:#0b9768">00 56</span> <span style="background:#0b9768">03 25</span> <span style="background:#0b9768">00 24</span><span style="background:#d4f991"> 03 84 </span> 00 00 00 03 01 4B 00 00 00 00 00 00 00 H7 01 CF 00 00 00 00 00 00 0C CB <span style="background:#0b9768">01 D0</span> <span style="background:#d4f991">00 00 00 00 00 0B FF C7</span> 00 00 01 00 00 79 3F

	\|}		\|}

AndrewBakalov at 07:55, 4 November 2022

2022-11-04T07:55:48Z

← Older revision		Revision as of 11:59, 4 November 2022
Line 281:		Line 281:
	\|-		\|-
	\| 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;" \|<span style="background:#~~0b9768~~">00</span>		\| style="vertical-align: middle; text-align: center;" \|<span style="background:#d4f991">00</span>
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|2’nd IO ID		\| style="vertical-align: middle; text-align: center;" \|2’nd IO ID
Line 287:		Line 287:
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|2’nd IO Value		\| style="vertical-align: middle; text-align: center;" \|2’nd IO Value
	\| style="vertical-align: middle; text-align: center;" \|<span style="background:#~~0b9768~~">00</span>		\| style="vertical-align: middle; text-align: center;" \|<span style="background:#d4f991">00</span>
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|3’rd IO ID		\| style="vertical-align: middle; text-align: center;" \|3’rd IO ID
Line 320:		Line 320:
	\|-		\|-
	\| 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;" \|<span style="background:#~~0b9768~~">00 7D</span> (Temperature value 1.25 degrees Celsius)		\| style="vertical-align: middle; text-align: center;" \|<span style="background:#d4f991">00 7D</span> (Temperature value 1.25 degrees Celsius)
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|2’nd IO ID		\| style="vertical-align: middle; text-align: center;" \|2’nd IO ID
Line 326:		Line 326:
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|2’nd IO Value		\| style="vertical-align: middle; text-align: center;" \|2’nd IO Value
	\| style="vertical-align: middle; text-align: center;" \|<span style="background:#~~0b9768~~">03 25</span> (Humidity 80.5%)		\| style="vertical-align: middle; text-align: center;" \|<span style="background:#d4f991">03 25</span> (Humidity 80.5%)
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|3’rd IO ID		\| style="vertical-align: middle; text-align: center;" \|3’rd IO ID
Line 344:		Line 344:
	\|-		\|-
	\| 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;" \|<span style="background:#~~0b9768~~">00 00 00 00 00 00 00 H7</span> (Flags. Each set bit (0-7) means the presence of value (0-7).)		\| style="vertical-align: middle; text-align: center;" \|<span style="background:#d4f991">00 00 00 00 00 00 00 H7</span> (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;" \|2’nd IO ID
Line 350:		Line 350:
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|2’nd IO Value		\| style="vertical-align: middle; text-align: center;" \|2’nd IO Value
	\| style="vertical-align: middle; text-align: center;" \|<span style="background:#~~0b9768~~">00 00 00 00 00 00 0C CB</span> (Movement status)		\| style="vertical-align: middle; text-align: center;" \|<span style="background:#d4f991">00 00 00 00 00 00 0C CB</span> (Movement status)
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|3’rd IO ID		\| style="vertical-align: middle; text-align: center;" \|3’rd IO ID

← Older revision		Revision as of 10:55, 4 November 2022
Line 278:		Line 278:
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|1’st IO ID		\| 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;" \|<span style="background:#0b9768">00 EF</span> (AVL ID 239, Name: Ignition)
	\|-		\|-
	\| 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		\| style="vertical-align: middle; text-align: center;" \|<span style="background:#0b9768">00</span>
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|2’nd IO ID		\| 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;" \|<span style="background:#0b9768">00 F0</span> (AVL ID 240, Name: Movement)
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|2’nd IO Value		\| 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;" \|<span style="background:#0b9768">00</span>
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|3’rd IO ID		\| 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;" \|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;" \|<span style="background:#0b9768">00 19</span> (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;" \|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;" \|<span style="background:#0b9768">00 7D</span> (Temperature value 1.25 degrees Celsius)
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|2’nd IO ID		\| 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;" \|<span style="background:#0b9768">00 56</span> (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;" \|2’nd IO Value
	\| style="vertical-align: middle; text-align: center;" \|03 25 (Humidity 80.5%)		\| style="vertical-align: middle; text-align: center;" \|<span style="background:#0b9768">03 25</span> (Humidity 80.5%)
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|3’rd IO ID		\| 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;" \|1’st IO ID
	\| style="vertical-align: middle; text-align: center;" \|01 4B (AVL ID 331, Name: BLE 1 Custom #1)		\| style="vertical-align: middle; text-align: center;" \|<span style="background:#0b9768">01 4B</span> (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;" \|1’st IO Value
	\| 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;" \|<span style="background:#0b9768">00 00 00 00 00 00 00 H7</span> (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;" \|2’nd IO ID
	\| style="vertical-align: middle; text-align: center;" \|01 CF (AVL ID 463, Name: BLE 1 Custom #2)		\| style="vertical-align: middle; text-align: center;" \|<span style="background:#0b9768">01 CF</span> (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;" \|2’nd IO Value
	\| style="vertical-align: middle; text-align: center;" \|00 00 00 00 00 00 0C CB (Movement status)		\| style="vertical-align: middle; text-align: center;" \|<span style="background:#0b9768">00 00 00 00 00 00 0C CB</span> (Movement status)
	\|-		\|-
	\| style="vertical-align: middle; text-align: center;" \|3’rd IO ID		\| style="vertical-align: middle; text-align: center;" \|3’rd IO ID