Teltonika Telematics Wiki - User contributions [en]

File:RFID connection2.png

2024-02-09T05:22:19Z

Tomas.Gudonis: Tomas.Gudonis uploaded a new version of File:RFID connection2.png

EYE FAQ

2023-10-27T05:50:20Z

Tomas.Gudonis: /* How to identify pitch/roll directions? */

=== <big>Questions about Power and Electrical characteristics</big> ===

==== How to change the battery / is the battery changeable? ====
It is not possible to change the battery with the current device models.

==== How to turn ON the device / does the device need to be turned on? ====
Devices are turned ON from the factory by default.

==== What is the battery life for different advertising intervals? ====
{| class="wikitable"
|EYE Beacon / BTSID1
|EYE Sensor / BTSMP1
|-
|2+ years

(Tx=2 dBm; interval: 1 s)
|1+ year

(Tx=2 dBm; interval: 1 s)
|-
|5+ years

(Tx=2 dBm; interval: 3 s)
|2.5+ years

(Tx=2 dBm; interval: 3 s)
|-
|8+ years

(Tx=2 dBm; interval: 5 s)
|4+ years

(Tx=2 dBm; interval: 5 s)
|-
|10+ years

(Tx=2 dBm; interval: 10s)
|5+ years

(Tx=2 dBm; interval: 10s)
|}

==== Can I disable not-used sensors to conserve the battery? ====
You can only disable only data sending of all sensors the sensors by configuring device protocol to send as a beacon, the sensors will be still active. It's also not possible to disable only one or part of the sensors.
However, there are options to create special order codes with assembly modifications with only one or selected sensors to be soldered and produced.
If you don't want to receive particular sensor data, but have no need for saving battery life, you can can disable the related sensor IO element in Teltonika Configurator. EYE Sensor will be still sending data, but FM will filter it according to your choice.

==== Can you provide battery life graphs according to environment temperature? ====

The graphs below are calculated with 10% safety margin to account for self discharge and variations in nominal capacity of the battery.

[[File:Btsx bat life graph.png|alt=|frameless|1130x1130px]] More information: [[File:BTSXXX CR2450 battery lifetime v1.2 for clients.xlsx|left|link=Special:FilePath/BTSXXX_CR2450_battery_lifetime_v1.2_for_clients.xlsx]]

==== Is there any graph to estimate device lifespan with different advertising settings? ====
Yes, please see attached document. [[File:Power consumption calculator.png | frameless]]

[[File:CLIENT VERSION BTSXX1 power consumption calculator-1.xlsx|thumb]]

==== What is battery voltage when the battery is considered empty? ====
Around 2.2V is when the device's battery is low and around 2.0V battery can be considered depleted.

==== How does the battery voltage translate into the percentage of the battery? ====
At the moment voltage is not directly translated into percentage as the voltage varies depending on the temperature sensor is in. We are working on battery life tests depending on temperature and various advertising frequencies and signal strength and we will be evaluating the possibility to send battery percentage in the future once those tests are done. For now, you can refer to the graph from the battery datasheet for a rough estimation of the remaining battery life.
[[File:Battery lifetime datasheet.png|frameless|454x454px]]
==== What is the battery chemistry used in beacons/sensors and what is the self-discharge rate of these batteries? ====
CR2450 Lithium, Manganese Dioxide(MnO2), Self-discharge 1% per 1 year
==== What is the direction of EYE Senor's or Beacon's antenna? ====
BTS Beacon/Sensor antenna is identical and its signal strength is very similar in all directions.

==== What is the BLE transmission range of BTS devices? ====
According to the tests done by us using FMB1YX trackers: the detection range in an open field in real conditions for the EYE Beacon/Sensor was 80 to 100m. Take note that the maximum range will also depend on the quality of the receiving device antenna.

===<big>Questions about EYE Accessory configuration (EYE APP)</big>===

==== Whats the default pin? ====
123456

==== Can you save configuration a template of a Sensor or Beacon and use it with another sensor/beacon when using the EYE app? ====
You can save the configuration - this is available with EYE APP 1.2.0-60
Uploading the configuration according to saved template will come in the near future.
You can follow EYE APP updates here:
[[EYE APP errata]]

==== Can you change configuration of EYE devices remotely? ====
No, the devices only have bluetooth chip, so you have to be relatively close to the device to update configuration. No implementation of updating EYE devices via services other than EYE APP is planned in near future.

==== Can you update firmware or configuration on a few sensors at the time via the EYE app? ====
Group updates are not available and are not planned to be available in the near future.

==== Why EYE APP does not show MAC on iOS (iPhone)? ====
The iOS operating system does not show MAC addreses on iBeacon or Eddystone protocols because of Apple introduced privacy policy. On iOS EYE app can request and display MAC address only when the device is connected in configuration mode.

==== Why EYE app does not display devices with iBeacon protocol on iOS (iPhone)? ====
Because of Apple introduced privacy policy iOS operating system does not return required data to identify Eye Beacons and EYE sensors configured with iBeacon protocol. Therefore we cannot identify our device and display it in the app.

==== Is it possible to configure the movement sensor to advertise only when movement is detected and if no movement is detected - no information is sent from the sensor? ====
It is not possible at the moment, and such a feature is not planned to be available in the near future. Movement status is advertising with every periodic data packet.

==== Do I need to configure UUID / Instance ID, how is UUID / MAC generated? ====
UUID/MAJOR/MINOR/Namespace/Instance IDs are automatically generated in the factory all are unique. MAC printed on the casing is assigned separately according to the list of available MACs and is not related to UUID/MAJOR/MINOR in any way.

Generally EYE Beacons are following format:
BTSID1 7CD9F4000001-7CD9F40FFFFF
BTSMP1 7CD9F4100000-7CD9F41FFFFF
===<big>Questions about FMBxxx compatibility with EYE Accessories</big>===

==== How many sensors can you use with FM device? ====
At the moment 4 sensors (Base firmware / advance mode), this is expanded up to 100 in evaluation firmware release which includes new EYE features. It will be available with 03.29.XX base firmware. You do not need to configure the MAC address but instead enter the name(or part of name) of the sensor and all sensors with that name(or part of name) will be scanned in case there are more than 100 then the ones with the strongest RSSI will be scanned and put into the packet

==== How to configure FM device for reading data from EYE sensor with standard Teltonika configurator(advanced mode)? ====
Please follow the steps in EYE Sensor wiki page: https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Teltonika_configurator_.28standard_functionality_.2F_advanced_mode.29

===<big>Questions about Protocols</big>===

==== Are EYE Beacons and Sensors supported by other IoT devices? ====
EYE Beacons or EYE Sensor configured as Beacon should be supported by any device that supports iBeacon or Eddystone protocols.
EYE Sensors have Teltonika protocol and custom GATT characteristics, so most likely support has to be developed.
Please check with the manufacturer of the device in question if they support iBeacon, Eddystone, or Teltonika EYE Sensor's protocol.
EYE Sensors protocol link:https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Protocol_description

==== Is magnet information broadcasted as true/false flag or with a counter? ====
At the moment only presence is sent(1 or 0).
A counter is only included in movement sensor's data.
It's possible to get evaluation firmware version with magnet counter functionality.
It's planned that it will be available in base firmware starting with EYE device firmware 1.2.10, you can follow changes here [[BTS firmware errata]]
Source:https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Protocol_description

==== Is it possible to receive the RSSI value from the sensor/ID? ====
Yes, both send RSSI voltage in the Eddystone/iBeacon protocol part.
Source: https://wiki.teltonika-gps.com/view/EYE_BEACON_/_BTSID1#EYE_Beacon_Protocol_overview

==== What data can be read from the accelerometer? ====
Only angle at the moment, with special development it's possible to receive accelerometer data.
Angle consists of 3 Bytes, i.e.: Angle is received as 0BFFC7 in frame advertised by the sensor, it parses to:
C1 – Most significant byte represents device pitch. Device pitch can be from -90 to 90 degrees.
In this example device's pitch is 0000 1011 (2's complement) = 11° degrees.
FFC7– Two least significant bytes represent device's roll. Device's roll can be from -180 to 180 degrees.
In this example device Roll is 1111 1111 1100 0111 (2's complement) = -57° degrees
Source:https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Protocol_description

==== What is TX / RFU / Calibrated Power? ====
The TX power value - value of processors power output to antenna.

Calibrated Power - in the Beacon protocol is a critical parameter that helps estimate the distance between a beacon and a receiving device. For example, this value is sent in Byte 29 of the iBeacon packet and is typically set to a predefined value in the sensor's configuration. It indicates the transmitting power of the beacon at a reference distance of 1 meter and is measured in decibels referenced to 1 milliwatt (dBm).

RFU - Similarly to Calibarated Power, RFU is set for Eddystone protocols. The difference is iBeacon, the calibrated power is reference RSSI value that is the expected RSSI value at 1 meter from the beacon, while for Eddystone, it's the expected RSSI value at 0 meters.

Currently Teltonika is providing beacons with pre-calibrated RSSI at 1m for iBeacon and RSSI at 0m for Eddystone that should be suitable for most use cases, however we plan to introduce user calibration in the future.

===<big>Other questions (Questions without category)</big>===

==== What is the purpose of LED on the devices? ====
It does not have any functions currently that would be apparent for users. It's used internally for doublechecking device visually that it's powered correctly. It's left on PCB for future development options.

==== Can you calibrate the sensors? ====
Temperature / Humidity sensors are pre-calibrated from factory.
For example, temperature long term drift is 0.03 Celsius/year, so the sensor should remain accurate within expected service-life time.
It would be cheaper to purchase new sensor then to re-calibrate it.
Therefore there is no manual calibration option available/planned at the moment.
If there are any specific requirements why the sensor be must be recalibrated earlier or periodically, please contact your sales manager with detailed description of your use case.

==== Can EYE sensors detect temperature less than -20°C? ====
It can detect less than -20°C we have been testing it in -40°C to +80°C, however, it's not recommended to use the device in temperature outside the compatible range for longer than a few hours. Temperature beyond recommended ranges will drain the battery faster than expected.

==== Can the EYE Sensor store data in memory and send it later in case of BT connection issues? ====
Not possible with current HW assembly, in the future, we plan to have modifications with additional flash memory and functionality to save records in memory with an option to download data later.

==== Do you need an additional magnet accessory to detect a magnet with the EYE Sensor? What is magnet detection range? ====
Yes, we offer the needed accessory order code on our [https://teltonika-gps.com/eye/ landing page] The maximum range for magnet detection is 4cm. Please refer to the below image for mounting recommendation.

[[File:MAGNET TRAILER MOUNTING.png|frameless|676x676px]]

==== How to identify pitch/roll directions? ====
Please see attached videos:

{| class="wikitable"
|-
! Roll Axis !! Pitch axis
|-
| [[File:Eye beacon Roll axis v4.mp4|400x400px]]|| [[File:Eye beacon Pitch axis v2.mp4|400x400px]]
|}

[[Category:Sensors]]

EYE FAQ

2023-10-27T04:14:38Z

Tomas.Gudonis:

=== <big>Questions about Power and Electrical characteristics</big> ===

==== How to change the battery / is the battery changeable? ====
It is not possible to change the battery with the current device models.

==== How to turn ON the device / does the device need to be turned on? ====
Devices are turned ON from the factory by default.

==== What is the battery life for different advertising intervals? ====
{| class="wikitable"
|EYE Beacon / BTSID1
|EYE Sensor / BTSMP1
|-
|2+ years

(Tx=2 dBm; interval: 1 s)
|1+ year

(Tx=2 dBm; interval: 1 s)
|-
|5+ years

(Tx=2 dBm; interval: 3 s)
|2.5+ years

(Tx=2 dBm; interval: 3 s)
|-
|8+ years

(Tx=2 dBm; interval: 5 s)
|4+ years

(Tx=2 dBm; interval: 5 s)
|-
|10+ years

(Tx=2 dBm; interval: 10s)
|5+ years

(Tx=2 dBm; interval: 10s)
|}

==== Can I disable not-used sensors to conserve the battery? ====
You can only disable only data sending of all sensors the sensors by configuring device protocol to send as a beacon, the sensors will be still active. It's also not possible to disable only one or part of the sensors.
However, there are options to create special order codes with assembly modifications with only one or selected sensors to be soldered and produced.
If you don't want to receive particular sensor data, but have no need for saving battery life, you can can disable the related sensor IO element in Teltonika Configurator. EYE Sensor will be still sending data, but FM will filter it according to your choice.

==== Can you provide battery life graphs according to environment temperature? ====

The graphs below are calculated with 10% safety margin to account for self discharge and variations in nominal capacity of the battery.

[[File:Btsx bat life graph.png|alt=|frameless|1130x1130px]] More information: [[File:BTSXXX CR2450 battery lifetime v1.2 for clients.xlsx|left|link=Special:FilePath/BTSXXX_CR2450_battery_lifetime_v1.2_for_clients.xlsx]]

==== Is there any graph to estimate device lifespan with different advertising settings? ====
Yes, please see attached document. [[File:Power consumption calculator.png | frameless]]

[[File:CLIENT VERSION BTSXX1 power consumption calculator-1.xlsx|thumb]]

==== What is battery voltage when the battery is considered empty? ====
Around 2.2V is when the device's battery is low and around 2.0V battery can be considered depleted.

==== How does the battery voltage translate into the percentage of the battery? ====
At the moment voltage is not directly translated into percentage as the voltage varies depending on the temperature sensor is in. We are working on battery life tests depending on temperature and various advertising frequencies and signal strength and we will be evaluating the possibility to send battery percentage in the future once those tests are done. For now, you can refer to the graph from the battery datasheet for a rough estimation of the remaining battery life.
[[File:Battery lifetime datasheet.png|frameless|454x454px]]
==== What is the battery chemistry used in beacons/sensors and what is the self-discharge rate of these batteries? ====
CR2450 Lithium, Manganese Dioxide(MnO2), Self-discharge 1% per 1 year
==== What is the direction of EYE Senor's or Beacon's antenna? ====
BTS Beacon/Sensor antenna is identical and its signal strength is very similar in all directions.

==== What is the BLE transmission range of BTS devices? ====
According to the tests done by us using FMB1YX trackers: the detection range in an open field in real conditions for the EYE Beacon/Sensor was 80 to 100m. Take note that the maximum range will also depend on the quality of the receiving device antenna.

===<big>Questions about EYE Accessory configuration (EYE APP)</big>===

==== Whats the default pin? ====
123456

==== Can you save configuration a template of a Sensor or Beacon and use it with another sensor/beacon when using the EYE app? ====
You can save the configuration - this is available with EYE APP 1.2.0-60
Uploading the configuration according to saved template will come in the near future.
You can follow EYE APP updates here:
[[EYE APP errata]]

==== Can you change configuration of EYE devices remotely? ====
No, the devices only have bluetooth chip, so you have to be relatively close to the device to update configuration. No implementation of updating EYE devices via services other than EYE APP is planned in near future.

==== Can you update firmware or configuration on a few sensors at the time via the EYE app? ====
Group updates are not available and are not planned to be available in the near future.

==== Why EYE APP does not show MAC on iOS (iPhone)? ====
The iOS operating system does not show MAC addreses on iBeacon or Eddystone protocols because of Apple introduced privacy policy. On iOS EYE app can request and display MAC address only when the device is connected in configuration mode.

==== Why EYE app does not display devices with iBeacon protocol on iOS (iPhone)? ====
Because of Apple introduced privacy policy iOS operating system does not return required data to identify Eye Beacons and EYE sensors configured with iBeacon protocol. Therefore we cannot identify our device and display it in the app.

==== Is it possible to configure the movement sensor to advertise only when movement is detected and if no movement is detected - no information is sent from the sensor? ====
It is not possible at the moment, and such a feature is not planned to be available in the near future. Movement status is advertising with every periodic data packet.

==== Do I need to configure UUID / Instance ID, how is UUID / MAC generated? ====
UUID/MAJOR/MINOR/Namespace/Instance IDs are automatically generated in the factory all are unique. MAC printed on the casing is assigned separately according to the list of available MACs and is not related to UUID/MAJOR/MINOR in any way.

Generally EYE Beacons are following format:
BTSID1 7CD9F4000001-7CD9F40FFFFF
BTSMP1 7CD9F4100000-7CD9F41FFFFF
===<big>Questions about FMBxxx compatibility with EYE Accessories</big>===

==== How many sensors can you use with FM device? ====
At the moment 4 sensors (Base firmware / advance mode), this is expanded up to 100 in evaluation firmware release which includes new EYE features. It will be available with 03.29.XX base firmware. You do not need to configure the MAC address but instead enter the name(or part of name) of the sensor and all sensors with that name(or part of name) will be scanned in case there are more than 100 then the ones with the strongest RSSI will be scanned and put into the packet

==== How to configure FM device for reading data from EYE sensor with standard Teltonika configurator(advanced mode)? ====
Please follow the steps in EYE Sensor wiki page: https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Teltonika_configurator_.28standard_functionality_.2F_advanced_mode.29

===<big>Questions about Protocols</big>===

==== Are EYE Beacons and Sensors supported by other IoT devices? ====
EYE Beacons or EYE Sensor configured as Beacon should be supported by any device that supports iBeacon or Eddystone protocols.
EYE Sensors have Teltonika protocol and custom GATT characteristics, so most likely support has to be developed.
Please check with the manufacturer of the device in question if they support iBeacon, Eddystone, or Teltonika EYE Sensor's protocol.
EYE Sensors protocol link:https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Protocol_description

==== Is magnet information broadcasted as true/false flag or with a counter? ====
At the moment only presence is sent(1 or 0).
A counter is only included in movement sensor's data.
It's possible to get evaluation firmware version with magnet counter functionality.
It's planned that it will be available in base firmware starting with EYE device firmware 1.2.10, you can follow changes here [[BTS firmware errata]]
Source:https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Protocol_description

==== Is it possible to receive the RSSI value from the sensor/ID? ====
Yes, both send RSSI voltage in the Eddystone/iBeacon protocol part.
Source: https://wiki.teltonika-gps.com/view/EYE_BEACON_/_BTSID1#EYE_Beacon_Protocol_overview

==== What data can be read from the accelerometer? ====
Only angle at the moment, with special development it's possible to receive accelerometer data.
Angle consists of 3 Bytes, i.e.: Angle is received as 0BFFC7 in frame advertised by the sensor, it parses to:
C1 – Most significant byte represents device pitch. Device pitch can be from -90 to 90 degrees.
In this example device's pitch is 0000 1011 (2's complement) = 11° degrees.
FFC7– Two least significant bytes represent device's roll. Device's roll can be from -180 to 180 degrees.
In this example device Roll is 1111 1111 1100 0111 (2's complement) = -57° degrees
Source:https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Protocol_description

==== What is TX / RFU / Calibrated Power? ====
The TX power value - value of processors power output to antenna.

Calibrated Power - in the Beacon protocol is a critical parameter that helps estimate the distance between a beacon and a receiving device. For example, this value is sent in Byte 29 of the iBeacon packet and is typically set to a predefined value in the sensor's configuration. It indicates the transmitting power of the beacon at a reference distance of 1 meter and is measured in decibels referenced to 1 milliwatt (dBm).

RFU - Similarly to Calibarated Power, RFU is set for Eddystone protocols. The difference is iBeacon, the calibrated power is reference RSSI value that is the expected RSSI value at 1 meter from the beacon, while for Eddystone, it's the expected RSSI value at 0 meters.

Currently Teltonika is providing beacons with pre-calibrated RSSI at 1m for iBeacon and RSSI at 0m for Eddystone that should be suitable for most use cases, however we plan to introduce user calibration in the future.

===<big>Other questions (Questions without category)</big>===

==== What is the purpose of LED on the devices? ====
It does not have any functions currently that would be apparent for users. It's used internally for doublechecking device visually that it's powered correctly. It's left on PCB for future development options.

==== Can you calibrate the sensors? ====
Temperature / Humidity sensors are pre-calibrated from factory.
For example, temperature long term drift is 0.03 Celsius/year, so the sensor should remain accurate within expected service-life time.
It would be cheaper to purchase new sensor then to re-calibrate it.
Therefore there is no manual calibration option available/planned at the moment.
If there are any specific requirements why the sensor be must be recalibrated earlier or periodically, please contact your sales manager with detailed description of your use case.

==== Can EYE sensors detect temperature less than -20°C? ====
It can detect less than -20°C we have been testing it in -40°C to +80°C, however, it's not recommended to use the device in temperature outside the compatible range for longer than a few hours. Temperature beyond recommended ranges will drain the battery faster than expected.

==== Can the EYE Sensor store data in memory and send it later in case of BT connection issues? ====
Not possible with current HW assembly, in the future, we plan to have modifications with additional flash memory and functionality to save records in memory with an option to download data later.

==== Do you need an additional magnet accessory to detect a magnet with the EYE Sensor? What is magnet detection range? ====
Yes, we offer the needed accessory order code on our [https://teltonika-gps.com/eye/ landing page] The maximum range for magnet detection is 4cm. Please refer to the below image for mounting recommendation.

[[File:MAGNET TRAILER MOUNTING.png|frameless|676x676px]]

==== How to identify pitch/roll directions? ====
Please see attached videos:

{| class="wikitable"
|-
! Roll Axis !! Pitch axis
|-
| [[File:Eye beacon Roll axis v4.mp4|400x400px]]]|| [[File:Eye beacon Pitch axis v2.mp4|400x400px]]]
|}

[[Category:Sensors]]

FTC881 Features

2023-09-07T06:55:08Z

Tomas.Gudonis:

== Overspeeding ==
[[File:Overspeedinggif2.gif|alt=|right|374x374px]]
When vehicle speed exceeds configured maximum speed value the scenario is activated, and an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}. Detected speed has to be greater than configured max speed +3% of configured max speed for the overspeeding event to start. To stop overspeeding event detected speed has to be lower than configured max speed -3% of configured max speed.
Configurable parameters:

 
*Priority – defines the priority of overspeeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
*Max speed – it is the maximum allowed speed that can be reached. If the speed exceeded configured value, then the event will occur.

==Trip==
[[File:Tripgif.gif|alt=|right]]
''Trip''' section offers user to configure the ''Trip'' feature. ''Trip'' starts when Ignition according ''Ignition source'' is ON and Movement according ''Movement source'' is ON and also 'Start Speed' is exceeded. ''Start Speed'' defines the minimum GPS speed in order to detect ''Trip'' start. ''Ignition OFF Timeout'' is the timeout value to detect ''Trip'' end once the Ignition (configured ignition source) is off. I/O Trip Odometer must be enabled to use ''Distance counting mode'' feature. When it is set to Continuous, ''Trip'' distance is going to be counted continuously (from ''Trip'' start to ''Trip'' end) and written to I/O ''Trip Odometer'' value field. When ''Trip'' is over and the next ''Trip'' begins, ''Trip Odometer'' value is reset to zero. When ''Mode'' is set to Between Records, the distance is going to be counted between every record made. This value is written to I/O ''Trip Odometer'' value field and is reset to zero every new record until the ''Trip'' ends. If later all Odometer values are summed up manually, the distance driven during the whole duration of the ''Trip'' can be obtained. 

== Odometer settings==
[[File:Odometergif.gif|alt=|right]]
{{{par_src|''Calculation Source'' allows to choose Odometer calculation source between GNSS, OBD. }}}''Odometer Value'' sets the starting total odometer value.

==Unplug detection==
[[File:Unplug2.gif|alt=|right]]
An event will be generated when {{{model|FMB1YX}}} is unplugged from {{{txt_src|external power}}} or plugged back in again.
'''Priority'''
*'''Disable''' - disable scenario.
*'''Low Priority''' - when low priority event is triggered, device '''makes additional record''' with indication of event cause.
*'''High Priority''' - module makes additional record with High priority flag and '''sends event packet immediately''' to the server by
'''GPRS'''.

==Static navigation==
[[File:Staticnav.gif|alt=|right|364x364px]]
''Static Navigation Mode'' is a filter, which filters out track jumps when the object is stationary. 
If the Static navigation filter is disabled, it will apply no changes to GPS data. If the Static navigation filter is enabled, it will filter changes in GPS position if no movement (configured movement source) or ignition (configured ignition source) is detected (depends on what static navigation settings are selected: movement, ignition or both sources). It allows filtering GPS jumps when an object is parked (is not moving) and GPS position is still traced. 

[[Category:FTC881 Configuration]]

FTC881 Features

2023-09-07T06:53:23Z

Tomas.Gudonis: /* Odometer settings */

EYE SENSOR / BTSMP1

2023-08-11T06:42:38Z

Tomas.Gudonis:

__TOC__
==Introduction==
Wireless solutions open up new horizons for your business and help to keep an eye on your assets. Discover our brand-new and certified Bluetooth Low Energy ID sensor model from Teltonika with robust waterproof casing and a long-lifetime battery. The model is designed for a low-cost fast and easy configuration and integration to save precious time, resources, and ensure accountability.
[[File:BTSMP1.png|center|frameless|1157x1157px]]

==About BTSMP1==
Perfect for traceability use cases, delivery tracking, monitoring of various movable objects in logistics (trailers, containers), agriculture (tractor attachments), and constructions (tools and inventory). Sensors data makes it especially suitable for cold chain refrigerator use cases. The built-in accelerometer can detect item movement, pitch and roll of the device. Magnet detection can be used for wireless open/close detection and notifications such as trailer door events, etc. EYE sensor supports iBeacon and Eddystone protocols. The device is fully compatible with the Teltonika firmware platform which provides extended functionality. Configure, scan, and update anytime anywhere with a dedicated Teltonika mobile app
==Product Specification==

===Features===
{| class="wikitable"
|+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Functionalities
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Beacon ID, LED, Temperature, Humidity, Accelerometer, Magnet detection
|}
{| class="wikitable"
|+
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Dimensions and weight
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Dimensions
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |56,6 mm x 38 mm x 13 mm
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Weight
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |18g
|-
|}
{| class="wikitable"
|+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Battery and power
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Model
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |CR2450
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Type
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Type Lithium, Manganese Dioxide
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Total Capacity
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |600 mAh
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Replaceable
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |No
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Battery life (Tx=2 dBm; interval: 3 s)
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |2.5+ years
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Battery life (Tx=2 dBm; interval: 5 s), default
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4+ years
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Battery life (Tx=2 dBm; interval: 10 s)
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |5+ years
|}
{| class="wikitable"
|+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Connectivity
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Bluetooth
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Bluetooth 4.2 compliant,
Bluetooth 5.2 certified
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Range
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |80 m
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Available transmission power levels
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Up to 8 dBm
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Sensitivity
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | -88 dBm
|}
{| class="wikitable"
|+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Casing
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Protection
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |IP67
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Mounting
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Two holes to screw/leash/strip, tape
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Customization
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Custom logo upon request (Special conditions)
|}
{| class="wikitable"
|+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Environmental Requirements
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Humidity (non-condensing)
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |From 0% to 100%
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Operational temperature
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | -20°C / +60°C (-4°F / +140°F)
|}
{| class="wikitable"
|+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Protocols compatibility
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |iBeacon
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Yes
<nowiki>*</nowiki>iOS doesn't show devices with iBeacon protocol
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Eddystone
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Yes
|-
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |EYE Sensor
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Yes
|}

===Dimensions===
[[File:Eye dimensions.png]]

==Value-adding Features==

===What is hibernated mode?===

Hibernated mode means that the EYE device is OFF when shipping from the factory, preserving battery life.
PLEASE NOTE that EYE devices are available in two modes: factory-activated (ON) or Hibernated (OFF). You may order the device version which better suits your needs.

===How to activate hibernated eye device?===

Attach any magnet to sleeping device and wait for LED to blink.
 '''NOTE: ANY MAGNET CAN BE USED'''
 [[File:520746 Magnet EYE gif v1.6-min.gif|frameless|684x684px]]
 Now device is discoverable, scannable, connectable via BLE.

===How to put the device back to sleep (Hibernation)?===

If you want to put the EYE device back to sleep after accidental activation or simply pause its use, you may do that.
 Step 1. While connected and in overview tap "Send device to sleep":
 Step 2. Confirm your selection:
 Step 3. Wait for EYE App to disconnect:
 [[File:Send To Sleep.png|frameless|300x300px]]
[[File:Send To Sleep Confirm.png|frameless|300x300px]]
[[File:Send To Sleep Disconnect.png|frameless|300x300px]]

===Which eye devices can I put back to sleep (Hibernation)?===

You may put back to sleep:
 1. All EYE Sensors with firmware version starting from 1.2.9.R.8.

2. New EYE Beacons WITH ‘Hibernate’ feature. It is not available for non-Hibernate edition Beacons due to hardware limitations.

===What's the value of hibernation?===

Hibernated versions of EYE devices simplify stock management for our partners while maximizing battery life. For example, it helps in such situations:
 1. Our partners want to have EYE devices ready and available to deploy at any moment with full battery capacity, delivering the fastest possible service and this way increasing their competitive advantage;

2. Our partners order a little too many devices for a specific project, and then it may take a month or a few to deploy them for different projects. That way they may deploy EYE devices with full battery capacity for further projects as well.

==Mounting recomendations==
[[File:Neweyemouning.png|858x858px]]
 [[File:New mounting recomendations 1.png|848x848px]]

==EYE App Configuration==
Devices work constantly and are ready to perform out of the box. Default basic Sensor settings are set to:
 • Transmitting at 2 dBm power.
 • Data advertising at 1 second intervals.
 • Eddystone and Sensors protocol
 
 If you would like to change these settings you will need to:
 1) Download and install EYE APP - Teltonika application to change sensor settings.
 [[File:QR.jpg]]

===Eye App Overview===
'''With the application you will be able to scan for visible Teltonika EYE devices, check their statuses or connect for configuration or firmware update.'''
 
{|
|- align="TOP"
|
|[[File:Detailed_list_-_collapsed.png|border|360x640px|none]]
|
|[[File:Overview - without update (sensor).png|border|360x640px|none]]
|
|[[File:Basic settings.png|right|border|360x640px]]
|
|[[File:Advanced settings.png|right|border|360x640px]]
|}

==== [[File:Frame 115.png|bottom|frameless|upright=0.2|link=|alt=]] Devices in view ====
In this window you will see all visible devices. You have options to see devices in Short list [[File:Shortlist.jpg|30px]] or in default list. When looking at devices in default list you will be able to open Detailed view [[File:Detailed.jpg]] of devices and check transmitted data statuses. Additionaly if you are looking for specific devices you will be able to use Search [[File:Search button eye app.jpg|30px]] function to filter search options. When in this window select a device of your choice to connect and after passing pin code (default pin code is 123456) you will go to device overview window.

==== [[File:Group 125.png|baseline|frameless|upright=0.2|link=|alt=]]Overview window ====
In overview window you can see device details, check firmware version and update if available , go to device configuration settings. If you select to Configure device new window will open with Basic and Advanced settings.
 

==== [[File:Group 116.png|sub|frameless|upright=0.2|link=|alt=]]Configure window ====
In this window you can check and change device configuration settings. In main tab Basic Settings you can change main settings. Change Device name, Power signal strength, Advertising interval and Packet transmission type*. For more settings go to Advanced settings tab to enable various events.

==== [[File:Group 117.png|sub|frameless|upright=0.2|link=|alt=]]Advanced configuration window ====

=====Advanced configuration: Beacon Settings=====
{|
|-style="vertical-align: top;"
|[[File:IBeacon ID settings.png|frameless]]
|[[File:Eddystone ID settings.png|frameless]]
|}
In Advanced settings tab you can can configure EYE beacon sensor parameters: Beacon information (iBeacon ID*, Eddystone ID). UUID/MINOR/MAJOR parameter can be changed for iBeacon ID*. Namespace ID/Instance ID can be changed for Eddystone ID. If you scroll down you will be able to adjust Sensor reading interval and event settings of the EYE Sensor '''Note:''' iOS doesn't show devices with iBeacon protocol

=====Advanced configuration: Sensor reading and events=====
'''!NOTE:''' These settings are no longer available after EYE APP 1.2.0-60 update.
{|
|- style="vertical-align: top;"
|[[File:Magnetic field event.png]]
|[[File:Humidity event.png]]
|[[File:Temperature event.png]]
|[[File:Movement event2.png]]
|-
|'''Magnetic field event''' - adjust if the device generates events based on detection or exit (loss) of the magnet.
|'''Humidity event''' - adjust if the device generates events based on entrance or exit to selected humidity range
|'''Temperature event''' - adjust if the device generates events based on entrance or exit to selected temperature range
|'''Movement event''' - adjust movement/stop detection and timeouts it takes to register movement / stopping
|-
|[[File:Maximum event duration.png|frameless]]
|[[File:Event Advertising settings.png|frameless]]
|[[File:Sensor reading interval.png|frameless]]
|-
|'''Maximum event duration''' - how long will one event be advertised
|'''Event advertising settings''' - advertising period after event detection
|'''Sensor reading interval''' - how often values are updated by the device
|}
 

==FM Tracker Configuration==

===Teltonika configurator (Base firmware / advanced mode)===
If you have firmware / configurator which does not support EYE sensor tab in Bluetooth 4.0 section, then you can still use Avanced BLE configuration to connect with EYE Sensors.

To configure FM with BTSMP1 EYE Sensor:

'''Requirements:'''

Firmware/configurator version with multiple custom IO fields per sensor, we recommend:

FMBXXX: 03.27.07.Rev.00/1.7.22_B.3.27_R.21 or newer

FMX640: 01.02.03/1.7.24_B.FM64_R.34 or newer (FMB640 does not support for BLE functionality)

'''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 System settings|System settings]] Enable [[Codec#Codec%208%20Extended|Codec8 Extended]];
# In [[FMB120 GPRS settings|GPRS settings]] Configure [[FMB120 GPRS settings#GPRS%20Settings%20and%20Server%20Settings|GPRS Settings and Server Settings]]
# 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)
## Configure MAC address of the sensor
# To receive data to server enable corresponding IO elements in [[FMB120 I/O settings#Priority|FMB120 I/O settings]]

 '''Advanced mode configuration:'''
{|
|EYE Sensor Packet Setting:
|[[File:Eye Sensors.png|alt=|771x771px]]
|[[File:IBeacon and EYE Sensors.png|alt=|771x771px]]
|[[File:Eddystone and EYE Sensors.png|alt=|771x771px]]
|-
|Preset you should use:
|EYE Sensors
|EYE iBeacon
|EYE Eddystone
|-
|FMBXXX Preset download link:
|[[File:Download_zip.png|x30px|link=Special:Redirect/file/EYE_Sensors.zip]]
|[[File:Download_zip.png|x30px|link=Special:Redirect/file/EYE_iBeacon.zip]]
|[[File:Download_zip.png|x30px|link=Special:Redirect/file/EYE_Eddystone.zip]]
|-
|FMBXXX Configuration example download link:
|[[File:Download_zip.png|x30px|link=Special:Redirect/file/EYE_SensorsConfig.zip]]
|[[File:Download_zip.png|x30px|link=Special:Redirect/file/EYE_iBeaconConfig.zip]]
|[[File:Download_zip.png|x30px|link=Special:Redirect/file/EYE_EddystoneConfig.zip]]
|-
|FMX640 Preset download link:
|[[File:Download_zip.png|x30px|link=Special:Redirect/file/FMX640_EYE_Sensors.zip]]
|[[File:Download_zip.png|x30px|link=Special:Redirect/file/FMX640_EYE_iBeacon.zip]]
|[[File:Download_zip.png|x30px|link=Special:Redirect/file/FMX640_EYE_Eddystone.zip]]
|-
| colspan="4" |Instructions how you can manually add a preset: [[How_to_add_a_BLE_preset_to_the_configurator|link]]
|}
 

 
'''Preset Configuration:'''

If EYE Sensor Packet Settings is EYE Sensors or Eddystone and EYE Sensors: [[File:Preset2EYE.png|frameless|1152x1152px]]

 If EYE Sensor Packet Settings is EYE Sensors or iBeacon and EYE Sensors:

[[File:Preset1EYE.png|frameless|1152x1152px]]

'''IO element value descriptions:'''
{| class="wikitable"
|+
! style="width:30%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |NAME
! style="border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |DESCRIPTION
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Custom1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Flags(not supported with curent FMX640 preset)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Temperature
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ambient temperature in Celsius
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Humidity
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ambient humidity in percent
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Custom2
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Movement and movement events count
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Custom3
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Angle
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Custom4
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Battery voltage (2000 + (VALUE * 10)) in mV
|-
|}

<table class="nd-othertables_2" style="width: 100%;">
<tr>
<th style="width: 10%; text-align:center; vertical-align:middle;">Property ID in AVL packet</th>
<th style="width: 20%; text-align:center; vertical-align:middle;">Property name</th>
<th style="width: 5%; text-align:center; vertical-align:middle;">Bytes</th>
<th style="width: 10%; text-align:center; vertical-align:middle;">Type</th>
<th style="width: 10%; text-align:center; vertical-align:middle;">Min</th>
<th style="width: 10%; text-align:center; vertical-align:middle;">Max</th>
<th style="width: 5%; text-align:center; vertical-align:middle;">Multiplier</th>
<th style="width: 5%; text-align:center; vertical-align:middle;">Units</th>
<th style="width: 25%; text-align:center; vertical-align:middle;">Description</th>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">25</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE Temperature #1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-4000</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">12500</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0.01*</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">°C</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Degrees ( °C ), -40 - +125;

Error codes:

4000 - abnormal sensor state

3000 - sensor not found

2000 - failed sensor data parsing
</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">26</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE Temperature #2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-4000</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">12500</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0.01*</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">°C</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Degrees ( °C ), -40 - +125;

Error codes:

4000 - abnormal sensor state

3000 - sensor not found

2000 - failed sensor data parsing
</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">27</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE Temperature #3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-4000</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">12500</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0.01*</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">°C</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Degrees ( °C ), -40 - +125;

Error codes:

4000 - abnormal sensor state

3000 - sensor not found

2000 - failed sensor data parsing
</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">28</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE Temperature #4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-4000</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">12500</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0.01*</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">°C</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Degrees ( °C ), -40 - +125;

Error codes:

4000 - abnormal sensor state

3000 - sensor not found

2000 - failed sensor data parsing
</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">86</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE Humidity #1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1000</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0.1*</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">%RH</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Humidity</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">104</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE Humidity #2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1000</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0.1*</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">%RH</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Humidity</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">106</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE Humidity #3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1000</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0.1*</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">%RH</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Humidity</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">108</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE Humidity #4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1000</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0.1*</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">%RH</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Humidity</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">331</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 1 Custom #1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">Variable</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">HEX</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">463</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 1 Custom #2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">464</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 1 Custom #3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">465</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 1 Custom #4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">466</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 1 Custom #5</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">332</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 2 Custom #1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">Variable</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">HEX</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">467</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 2 Custom #2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">468</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 2 Custom #3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">469</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 2 Custom #4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">470</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 2 Custom #5</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">333</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 3 Custom #1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">Variable</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">HEX</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">471</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 3 Custom #2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">472</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 3 Custom #3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">473</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 3 Custom #4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">474</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 3 Custom #5</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">334</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 4 Custom #1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">Variable</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">HEX</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">475</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 4 Custom #2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">476</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 4 Custom #3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">477</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 4 Custom #4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">478</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">BLE 4 Custom #5</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">8</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">UNSIGNED LONG INT</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">4294967295</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Custom IO element for BLE sensor</td>
</tr></table>

===Teltonika configurator new functionalities (Evaluation firmware / EYE Sensor filtering by name)===
Starting with firmware 03.28.04.Rev.207 there is additional tabs available in Bluetooth 4.0 section that allow for easier configuration to connect FM and EYE sensor or beacon.

'''It's now possible to connect up to 100 sensors at once just by entering one name in the configurator name list.''' It's required to enter at least 3 characters(case sensitive) in the name for FM to scan the sensors. Super easy to set up!

For example, the you may order Sensors with special configuration from factory where the EYE Sensor names would be TRAILER_1,TRAILER_2,...,TRAILER_99 and so on.

If you would enter TRAILERS in the EYE Fimrware FM configurator then sensors who meet this name condition, for example TRAILER_1, TRAILER_21 , TRAILER_17, would be scanned, while other sensors named Tools, MP1_123546, etc. will not be scanned.
With this option, you can upload one configuration to FOTA web and it doesn’t matter which sensor from the list end user will mount, it will be scanned and sent to the server as long as it meets the name criteria.

'''Bluetooth 4.0'''
 
Functionalities were reorganized and transferred to Bluetooth 4.0 configuration tab with additional horizontal tabs selection for specific settings:
 
*'''Global''' - Parameters responsible for device scanning ability like power and duratations.
*'''EYE''' - Parameters to configure data reading from EYE sensors.
 
'''Common settings'''
 
*'''Non Stop Scan''' - Enable Non Stop Scan feature, the device will try to scan for the sensors all the time if any of them are configured.
*'''Sensors and Beacons Update frequency''' - changes sensors temperature/humidity/battery voltage data update frequency. Minimum value: 30s, maximum value: 65535s. Recommended value 30.
*'''BLE Scan Duration''' - Sensors data reading time. Recommended value 30.
*'''Scan retries until error''' - Scan retries count, till start to show the value as Error '3000' - sensor disconnected. Recommended value 30.
*'''BT Power Level''' - Telematics device Bluetooth power level setting.
*'''BLE Broadcasting service ID''' - Telematics device can broadcast configured ID.
*''' BLE connection control''' - Connection mode settings. If broadcasting ID is configured, parameter should be set to Prohibit.

 
[[File:BLE 4,0 Common settings.png]]
 
 
'''Sensors'''
 
Sensor Configuration can be set to Custom Sensors, Eye Sensors or both.
With the Custom Sensors setting enabled, [https://wiki.teltonika-gps.com/view/FMB130_Bluetooth_4.0_settings#Advanced_Mode| any BLE sensor can be configured.] 
When '''EYE Sensors''' is selected, Eye Sensor connectionless functionalities or EYE list search window will appear, depending on the selected EYE Sensor filter.
 
[[File:EYE Sensors NAME.png]]
 '''Name''' 
When EYE Sensors Filter is set to '''Name''', the Eye List search window will appear on the configurator. With this setting, separate EYE Sensor records (AVL ID: 11317) will be generated according to the configured parameters, which are described below:
 
*'''Data Clear period'''- defines how long the FM tracker waits when the Eye sensor is not detected before removing it from the Eye Sensor list and not sending the sensor values. If Data Clear Period is set to 0, then the EYE Sensor will not be removed from the EYE Sensor list and it will always be included in the periodic records. 

*'''RSSI'''- Parameter defines the dBm threshold value of when the EYE sensor will be added to the sensor list. If the FM tracker detects the RSSI lower than the configured value, it will not be added to the EYE Sensor list. 

*'''Record period''' - Defines how often the EYE Sensor record (AVL ID: 11317) will be generated when the FM tracker is operating On Stop or On Move modes, according to the configured [https://wiki.teltonika-gps.com/view/FMB140_System_settings#Movement_Source| movement source.]. 

*'''EYE Sensor Settings''' - Define what sensor readings data is included in to the EYE Sensor Records. Sensor readings which are not needed can be disabled, to reduce data consumption. 
*'''EYE Name list''' - Defines what EYE sensors will be added to EYE Sensor list. For EYE Sensors to be added to the list, only the beginning part of the EYE Sensor local name has to match. For example, if in the EYE name list “EYE_SENSOR” is added and the FM tracker detects EYE_SENSOR1, EYE_SENSOR2, EYE_SENSORXYZ, all these EYE Sensors will be added to EYE Sensor list. If the EYE name list is left empty, all the detected EYE Sensors will be included in the EYE Sensor list. '''NOTE:''' If EYE Sensor has a name that matches configured one in EYE Name List and if it has a MAC address, that matches configured one in EYE Sensors filtered by MAC address, then such sensor will not be added to EYE Sensor list, but it’s data will be added according EYE Sensor filtered by MAC IO elements. 
[[File:EYE List name search.png]]
 
 
Once Eye Sensor filtering by name list is selected, EYE Sensor records containing the AVL ID:11317 will start being generated. Below is an example of how EYE Sensor data is packed into AVL ID 11317 
'''AVL ID 11317 structure'''
{| class="wikitable"
|+
! colspan="2" |Eye Sensor #1
|-
|EYE Sensor #1 Data length
|1 byte
|-
|1st Parameter ID
|1 byte
|-
|1st Parameter Data Length
|1 byte
|-
|1st Parameter Data
|variable
|-
|2nd Parameter ID
|1 byte
|-
|2nd Parameter Data Length
|1 byte
|-
|2nd Parameter Data
|variable
|-
| colspan="2" |<...>
|-
|Nth Parameter ID
|1 byte
|-
|Nth Parameter Data Length
|1 byte
|-
|Nth Parameter Data
|variable
|-
! colspan="2" |Eye Sensor #2
|-
|Eye Sensor #2 Data length
|1 byte
|-
|1st Parameter ID
|1 byte
|-
|1st Parameter Data Length
|1 byte
|-
|1st Parameter Data
|variable
|-
|2nd Parameter ID
|1 byte
|-
|2nd Parameter Data Length
|1 byte
|-
|2nd Parameter Data
|variable
|-
| colspan="2" |<...>
|-
|Nth Parameter ID
|1 byte
|-
|Nth Parameter Data Length
|1 byte
|-
|Nth Parameter Data
|variable
|-
! colspan="2" |Eye Sensor #N
|-
!...
!...
|}

Parameter IDs are used to identify what type of EYE Sensor information is included in the packet. Below is the table describing the possible EYE Sensor parameter IDs, along with their data type and data length. 
{| class="wikitable nd-othertables_2" style="width:125%;" ;
|+'''Table 1. EYE Sensor Parameter IDs'''
|-
!Parameter ID!!Name
!Data type!!Description!!
|-
|5||Eye Sensor Device Name
|Array||Device’s name from Device Name List tab
|-
|6
|EYE Sensor Temperature
|2 byte signed integer
|Temperature value measured by EYE Sensor from List Values from -32768 to +32768 with 0.01 C delta
|-
|7
|EYE Sensor Humidity
|1 byte unsigned integer
|Humidity measured by EYE Sensor from List Values from 0 to 100%
|-
|8
|EYE Sensor Magnet presence
|1 byte unsigned integer
|Magnet measured by EYE Sensor from List Values from 0 to1
|-
|9
|EYE Sensor Movement presence
|1 byte unsigned integer
|Movement measured by Eye Sensor from List Values
|-
|10
|EYE Sensor Movement count
|2 byte unsigned integer
|Movement counts measured by EYE Sensor from List Values
|-
|11
|EYE Sensor Pitch
|1 byte signed integer
|Pitch angle measured by Eye Sensor from list Values
|-
|12
|EYE Sensor Angle Roll
|2 byte signed integer
|Roll Angle measured by EYE Sensor from List Values
|-
|13
|EYE Sensor Low battery indicator
|1 byte unsigned integer
|Low battery state measured by EYE Sensor from List Values from 0 to1
|-
|14
|EYE Sensor Battery voltage
|2 byte unsigned integer
|Low battery state measured by EYE Sensor from List Values from 0 to1
|-
|16
|EYE Sensor Magnet trigger count
|2 byte unsigned integer
|Magnet trigger counts measured by EYE Sensor from List Values
|-
|}

 
 
[[File:EYE Sensors MAC.png]]
 
'''MAC''' 
IF EYE Sensors are selected to be filtered by '''MAC address''', separate EYE sensor records will not be generated; EYE sensor values will be included into regular records with their corresponding IO elements. Up to 4 EYE Sensors can be configured with different MAC Addresses.
In the case of filtering by MAC Address, more advanced configuration is possible, as EYE Sensors’ IOs’ Low, High level, Event Only and Operand parameters can also be configured separately for each IO. 
*'''Working Mode''' - parameter has 2 options – Disabled and EYE Sensor. When it is disabled, EYE Sensor IO values will not be included into the records. When EYE Sensor is selected, EYE Sensor IO values will be included into records. 
*'''MAC Settings''' - parameter specifies the MAC address of the EYE Sensor for the FM tracker to read, parse its data and put to corresponding IO elements. If the sensor is not found for set amount of scan retries, error values will be stored into IO elements. 
*'''I/O elements''' - allows for advanced EYE sensor [https://wiki.teltonika-gps.com/view/FMB130_I/O_settings I/O elements configuration].
[[File:Eye Sensor Connectionless Functionalities.png]]
 
'''EYE Sensor AVL IDs''' 
Table below describes I/O elements which were added for EYE sensor with the new functionalities release. <table class="nd-othertables_2" style="width: 100%;">
<tr>
<th style="width: 10%; text-align:center; vertical-align:middle;">Property ID in AVL packet</th>
<th style="width: 20%; text-align:center; vertical-align:middle;">Property name</th>
<th style="width: 5%; text-align:center; vertical-align:middle;">Bytes</th>
<th style="width: 10%; text-align:center; vertical-align:middle;">Type</th>
<th style="width: 10%; text-align:center; vertical-align:middle;">Min</th>
<th style="width: 10%; text-align:center; vertical-align:middle;">Max</th>
<th style="width: 5%; text-align:center; vertical-align:middle;">Multiplier</th>
<th style="width: 5%; text-align:center; vertical-align:middle;">Units</th>
<th style="width: 25%; text-align:center; vertical-align:middle;">Description</th>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">11317</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Sensor List</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">variable length</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">HEX</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0 bytes</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1024 bytes</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">EYE Sensor List</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10800</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Temperature 1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-32768</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">32768</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0,01</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">°C</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Temperature measured by EYE sensor 1</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10801</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Temperature 2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-32768</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">32768</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0,01</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">°C</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Temperature measured by EYE sensor 2</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10802</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Temperature 3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-32768</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">32768</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0,01</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">°C</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Temperature measured by EYE sensor 3</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10803</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Temperature 4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-32768</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">32768</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">0,01</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">°C</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Temperature measured by EYE sensor 4</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10804</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Humidity 1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">100</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">%</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Humidity measured by EYE sensor 1</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10805</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Humidity 2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">100</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">%</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Humidity measured by EYE sensor 2</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10806</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Humidity 3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">100</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">%</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Humidity measured by EYE sensor 3</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10807</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Humidity 4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">100</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">%</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Humidity measured by EYE sensor 4</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10808</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Magnet 1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Magnet measured by EYE sensor 1</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10809</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Magnet 2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Magnet measured by EYE sensor 2</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10810</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Magnet 3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Magnet measured by EYE sensor 3</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10811</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Magnet 4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Magnet measured by EYE sensor 4</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10812</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Movement 1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Movement state and count measured by EYE sensor 1</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10813</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Movement 2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Movement state and count measured by EYE sensor 2</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10814</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Movement 3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Movement state and count measured by EYE sensor 3</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10815</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Movement 4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Movement state and count measured by EYE sensor 4</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10816</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Pitch 1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-90</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">90</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Pitch and Roll angles measured by EYE sensor 1</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10817</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Pitch 2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-90</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">90</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Pitch and Roll angles measured by EYE sensor 2</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10818</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Pitch 3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-90</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">90</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Pitch and Roll angles measured by EYE sensor 3</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10819</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Pitch 4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-90</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">90</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Pitch and Roll angles measured by EYE sensor 4</td>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10820</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Low Battery 1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Low Battery indication EYE sensor 1</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10821</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Low Battery 2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Low Battery indication EYE sensor 2</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10822</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Low Battery 3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Low Battery indication EYE sensor 3</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10823</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Low Battery 4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Low Battery indication EYE sensor 4</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10824</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Battery Voltage 1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">65535</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Battery Voltage of EYE sensor 1</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10825</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Battery Voltage 2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">65535</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Battery Voltage of EYE sensor 2</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10826</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Battery Voltage 3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">65535</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Battery Voltage of EYE sensor 3</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10827</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Battery Voltage 4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">Unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">65535</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Battery Voltage of EYE sensor 4</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10832</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Roll 1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-180</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">180</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Roll value of EYE Sensor 1</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10833</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Roll 2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-180</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">180</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Roll value of EYE Sensor 2</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10834</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Roll 3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-180</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">180</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Roll value of EYE Sensor 3</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10835</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Roll 4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">signed</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">-180</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">180</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Roll value of EYE Sensor 4</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10836</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Movement Count 1</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">65535</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Movement count value of EYE Sensor 1</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10837</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Movement Count 2</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">65535</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Movement count value of EYE Sensor 2</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10838</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Movement Count 3</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">65535</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Movement count value of EYE Sensor 3</td>
</tr>
<tr>
<td style="width: 10%; text-align:center; vertical-align:middle;">10839</td>
<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Movement Count 4</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">2</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">unsigned</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">0</td>
<td style="width: 10%; text-align:center; vertical-align:middle;">65535</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 5%; text-align:center; vertical-align:middle;">-</td>
<td style="width: 25%; text-align:center; vertical-align:middle;">Movement count value of EYE Sensor 4</td>
</tr>

</table>

Eye sensor parameters have error code values, which will written to the I/O value if parameter data is not received. From the error code value, it is possible to distinguish whether the issue is on the FM tracker side or the EYE Sensor. Below is a table describing these values.
{| class="wikitable"
|+Eye Sensor Error Values
! rowspan="2" |Parameter
! rowspan="2" |Data length
(bytes)
! rowspan="2" |Data type
! colspan="2" |Error codes
|-
!Data Not Received by FM tracker
!EYE Sensor indicates error
|-
|Temperature
|2
|signed
|25000
|25001
|-
|Humidity
|1
|unsigned
|250
|251
|-
|Magnet
|1
|unsigned
|250
|251
|-
|Magnet trigger count
|2
|unsigned
|65000
|65001
|-
|Movement
|1
|unsigned
|250
|251
|-
|Movement counter
|2
|unsigned
|65000
|65001
|-
|Pitch
|1
|signed
|120
|121
|-
|Roll
|2
|signed
|250
|251
|-
|Low battery status
|1
|unsigned
|250
|251
|-
|Battery voltage
|1
|unsigned
|250
|251
|}

'''Note:''' If you are using presets(firmware/configurator without EYE product support), then refer to [[FMB130 Teltonika Data Sending Parameters ID#BLE%20Sensors%20I.2FO%20elements|BLE Sensors I/O elements]] table instead.EYE Sensor Protocol overview

==Sensor advertising==
 
[[File:Sensors data.png|center]]
 
===Beacon and sensors data===
[[File:Beacon and sensors data.png|center|1000x1000px|alt=|frameless]]
 
 

===Protocol description===
At the highest-level Bluetooth LE advertising packet consists of Advertising Indication and Scan Response. Both packets can be maximum of 31 bytes in size. Advertising Indication packet is always broadcasted when Scan Response is broadcasted only if Observer device requests it by using Active Scan.
 
BTSMP1 uses Advertising Indication to send beacon data which can be configured to select between iBeacon and Eddystone protocols or to be disabled at all. In that case, data which is shown as Scan Response in protocol overview will be sent as Advertising Indication without Scan Response following it.
 
Scan Response is used to send device name and manufacturer specific data. Manufacturer specific data includes Teltonika Company ID (0x089A) and protocol version (0x01). It is followed by Flag Encoded Data (Table 1) and Extended Data (Table 2). Later on, protocol will be highly configurable in and will allow to disable/enable sending of device name or any sensor value allowing to reduce size of the packet being sent.
 

Teltonika BTSX devices are transmitting one or two packets depending on the selected protocol. Broadcast packet + Scan response packet.

A scan response packet is sent when an active scan is used, within the BLE layer of communication.
The default for our FM devices and many other applications for example our EYE Appication or nRF connect Application is an active scan.

There are three protocols, with the following packets:

'''1.iBeacon + EYE Sensors'''

'''2.Eddystone + EYE Sensors'''

For '''iBeacon + EYE Sensors''' and '''Eddystone + EYE Sensors''' protocols only iBeacon/Eddystone packet is broadcasted and will be seen by both active and passive scans, to see the EYE Sensors packet you need to use an active scan.
In other words in an environment where no BLE devices are scanning with an active scan or in case when there are no scanning devices at all, only the iBeacon/Eddystone packet will be sent by the BTS device to conserve energy.

'''3. EYE Sensors'''

With '''EYE Sensors''' protocol, the EYE Sensor packet becomes broadcast.
In other words, in an environment where no BLE devices are scanning with an active scan or in case when there are no scanning devices at all EYE Sensors packet will be sent by the BTS device.

More Information on
[https://support.digitalmatter.com/support/solutions/articles/16000100684-active-vs-passive-bluetooth-scanning| Active vs passive scans]
 
 
Device Name has the following default value for Beacon – ID1_XXXXXXX
 
<div style="display:inline-table">
{| class="nd-othertables_2" style="width:125%;" ;
|+'''Table 1. Flag Encoded Date'''
|-
!Data!! Size (Bytes)!!Description
|-
|Flags||1||Each set bit (0-7) means the presence of value (0-7). Bits:
 0 – Temperature value presence
 1 – Humidity value presence
 2 – Magnetic sensor presence
 3 – Magnetic sensor state (1 magnetic field is detected/0 magnetic field is not detected) Valid value is present only if bit 2 flag is set.
 4 – Movement sensor counter
 5 – Movement sensor angle
 6 – Low Battery indication (if set to 1 low battery voltage detected)
 7 – Battery voltage value presence
|-
|Value 0||2||Temperature
 Value in Celsius * 100
 NOTE: present only if bit 0 is set, otherwise is not being sent
|-
|Value 1 ||1||Humidity
 Value in percent
 NOTE: present only if bit 1 is set, otherwise is not being sent
|-
|Value 2||2||Movement Sensor counter
 Most significant bit indicates movement state and 15 least significant bits represent count of movement events.
 NOTE: present only if bit 4 is set, otherwise is not being sent
|-
|Value 3 ||3||Movement sensor angle
 Most significant byte – pitch (-90/+90)
 Two least significant bytes – roll (-180/+180)
 NOTE: present only if bit 5 is set, otherwise is not being sent
|-
|Value 4||1|| Battery Voltage
 Battery voltage in mV = 2000 + VALUE * 10
 NOTE: present only if bit 7 is set, otherwise is not being sent
|}
</div>

===GATT Characteristics===

{| class="wikitable" style="width: 100%; background-color: white; border-bottom: 2px solid #0054A6;"

|-

! style="color: #0054A6; background-color: white; border-bottom: 2px solid #0054A6; width: 20px;" | Name

! style="color: #0054A6; background-color: white; border-bottom: 2px solid #0054A6; width: 280px;" | Service UUID

! style="color: #0054A6; background-color: white; border-bottom: 2px solid #0054A6; width: 280px;" | Characteristic UUID

! style="color: #0054A6; background-color: white; border-bottom: 2px solid #0054A6;" | Data Type

! style="color: #0054A6; background-color: white; border-bottom: 2px solid #0054A6;" | Min

! style="color: #0054A6; background-color: white; border-bottom: 2px solid #0054A6;" | Max

! style="color: #0054A6; background-color: white; border-bottom: 2px solid #0054A6; width: 120px" | Default Value

! style="color: #0054A6; background-color: white; border-bottom: 2px solid #0054A6;" | Notes

|-

| Device Name || e61c0000-7df2-4d4e-8e6d-c611745b92e9 || e61c0016-7df2-4d4e-8e6d-c611745b92e9 || ASCII || 0 || 11 || Unique for each device || -

|-

| Tx Power Lever || 1804 || 2a07 || SINT8 || -14 || 8 || 2 || Possible values: -14, -11, -8, -5, -2, 2, 4, 8

|-

| Protocol Type|| e61c0000-7df2-4d4e-8e6d-c611745b92e9 || e61c0001-7df2-4d4e-8e6d-c611745b92e9 || UINT8 || 0 || 4 || 1 for EYE_Beacon, 4 for EYE_Sensor || 0 - iBeacon 1 - Eddystone 2 - EYE Sensor 3 - iBeacon + EYE Sensor 4 - Eddystone + EYE Sensor

|-

| Advertising Interval|| e61c0000-7df2-4d4e-8e6d-c611745b92e9 || e61c0002-7df2-4d4e-8e6d-c611745b92e9 || UINT16 || 20 || 10000 || 1000 || miliseconds

|-

| Sub Advertising Interval || e61c0000-7df2-4d4e-8e6d-c611745b92e9 || e61c0003-7df2-4d4e-8e6d-c611745b92e9 || UINT16 || 20 || 1000 || 100 || Used by repeats, miliseconds

|-

| Advertising Repeats || e61c0000-7df2-4d4e-8e6d-c611745b92e9 || e61c0004-7df2-4d4e-8e6d-c611745b92e9 || UINT16 || 1 || 10 || 1 || Repeats work only if Advertising Interval is more than 2000 ms and Repeats set to more than 1

|-

| iBeacon ID || e61c0000-7df2-4d4e-8e6d-c611745b92e9 || e61c0005-7df2-4d4e-8e6d-c611745b92e9 || BYTE ARRAY || 20 bytes || 20 bytes || Unique for each device || 16 B - UUID 2 B - major 2 B - minor

|-

| Eddystone ID || e61c0000-7df2-4d4e-8e6d-c611745b92e9 || e61c0006-7df2-4d4e-8e6d-c611745b92e9 || BYTE ARRAY || 16 bytes || 16 bytes || Unique for each device || 10 B - Namespace 6 B - Instance
|-
|Command
|e61c0000-7df2-4d4e-8e6d-c611745b92e9
|e61c0007-7df2-4d4e-8e6d-c611745b92e9
| colspan="5" |[[EYE SENSOR / BTSMP1#Command characteristic|Command characteristic]]
|-

|Password||e61c0000-7df2-4d4e-8e6d-c611745b92e9|| e61c0008-7df2-4d4e-8e6d-c611745b92e9 ||BYTE ARRAY|| 4 bytes||4 bytes||123456||Always 6 Digits

|-

|Sensor Interval||e61c0000-7df2-4d4e-8e6d-c611745b92e9|| e61c0009-7df2-4d4e-8e6d-c611745b92e9||UINT16||0||10000||1000||miliseconds

|-

|Event Interval||e61c0000-7df2-4d4e-8e6d-c611745b92e9|| e61c000a-7df2-4d4e-8e6d-c611745b92e9||UINT16||0||10000||1000 || miliseconds

|-

|Event Duration||e61c0000-7df2-4d4e-8e6d-c611745b92e9||e61c000b-7df2-4d4e-8e6d-c611745b92e9||UINT8||0||30 ||30||seconds

|-

| Temperature Event||e61c0000-7df2-4d4e-8e6d-c611745b92e9||e61c000c-7df2-4d4e-8e6d-c611745b92e9||UINT8 ||0||2|| 2||0 - on entrance 1 - on exit 2 - no event

|-

|Temperature Low||e61c0000-7df2-4d4e-8e6d-c611745b92e9 ||e61c000d-7df2-4d4e-8e6d-c611745b92e9||INT8||-40|| 85||-20||celsius

|-

|Temperature High|| e61c0000-7df2-4d4e-8e6d-c611745b92e9||e61c000e-7df2-4d4e-8e6d-c611745b92e9||INT8||-40||85 ||50||celsius

|-

| Humidity Event||e61c0000-7df2-4d4e-8e6d-c611745b92e9||e61c000f-7df2-4d4e-8e6d-c611745b92e9||UINT8||0||2||2||0 - on entrance 1 - on exit 2 - no event

|-

|Humidity Low||e61c0000-7df2-4d4e-8e6d-c611745b92e9||e61c0010-7df2-4d4e-8e6d-c611745b92e9 || UINT8||0||100||15||%

|-

|Humidity High ||e61c0000-7df2-4d4e-8e6d-c611745b92e9||e61c0011-7df2-4d4e-8e6d-c611745b92e9||UINT8||0||100||50||%

|-

|Movement Event||e61c0000-7df2-4d4e-8e6d-c611745b92e9 || e61c0012-7df2-4d4e-8e6d-c611745b92e9||UINT8||0||2||2||0 - on entrance 1 - on exit 2 - no event

|-

|Movement Start ||e61c0000-7df2-4d4e-8e6d-c611745b92e9||e61c0013-7df2-4d4e-8e6d-c611745b92e9|| UINT16||0||300||5||seconds

|-

|Movement Stop||e61c0000-7df2-4d4e-8e6d-c611745b92e9||e61c0014-7df2-4d4e-8e6d-c611745b92e9|| UINT16||0||300||5 ||seconds

|-

|Magnetic Event||e61c0000-7df2-4d4e-8e6d-c611745b92e9||e61c0015-7df2-4d4e-8e6d-c611745b92e9||UINT8||0||2|| 2||0 - on entrance 1 - on exit 2 - no event
|-
| Password Counter
|e61c0000-7df2-4d4e-8e6d-c611745b92e9
| e61c0019-7df2-4d4e-8e6d-c611745b92e9
|UINT8
|0 (counter)
|10 (counter)
| 0
|Byte 0 – counter,

Byte 1 and 2 - timeout
|-
|Master Password (PUK)
|e61c0000-7df2-4d4e-8e6d-c611745b92e9
|e61c0020-7df2-4d4e-8e6d-c611745b92e9
| UINT8
|8 bytes
|8 bytes
|MAC address dependency
|Byte array
|-
|Manufacturer sleep (Hibernate mode)
|e61c0000-7df2-4d4e-8e6d-c611745b92e9
|e61c0018-7df2-4d4e-8e6d-c611745b92e9
|UINT8
|0
|1
|1
|0 – sleep disabled,

1 – sleep enabled
|-
|Activate / Deactivate Sensors
|e61c0000-7df2-4d4e-8e6d-c611745b92e9
|e61c0021-7df2-4d4e-8e6d-c611745b92e9
|UINT8
|0
|15

(0b1111)
|15

(0b1111)
|(LSb) bit 0 – Temperature

Bit 1 – Humidity

Bit 2 – Magnetic

Bit 3 - Movement
|-
|User ADV Spam Duration
|e61c0000-7df2-4d4e-8e6d-c611745b92e9
|e61c0022-7df2-4d4e-8e6d-c611745b92e9
|UINT16
|1
|300
|30
|WakeUp Advertising

Spam Duration in seconds
|-
|RSSI Calibration Value
|e61c0000-7df2-4d4e-8e6d-c611745b92e9
|e61c0023-7df2-4d4e-8e6d-c611745b92e9
|INT8
|<nowiki>-100</nowiki>
|127
| 127
|RSSI value in dBm

127 – Use default calib. table
|-

|Manufacturer||180A||2A29||BYTE ARRAY||-||-||Not Configurable ||Read Only. Ex. "Teltonika"

|-

| Model|| 180A||2A24|| BYTE ARRAY|| -||-|| Not Configurable||Read Only. Ex. "BTSID1"

|-

|Serial||180A||2A25 ||BYTE ARRAY||-||-||Not Configurable ||Not used

|-

| Hardware||180A|| 2A27 ||BYTE ARRAY||-||-||Not Configurable||Read Only. Ex. "Table:1 Volt:325

|-

|Firmware|| 180A ||2A26||BYTE ARRAY||-||-||Not Configurable||Read Only. Ex. "1.1.0-beta"

|-

| System ID ||180A||2A23||BYTE ARRAY||-||-|| Not Configurable||Not used

|-

|MAC||180A||652143dc-dec6-4fb1-bd46-3e919d2410a6 || BYTE ARRAY||6||6||Not Configurable||Read Only. ex. 112233445566 -> 11:22:33:44:55:66

|-

|Scan Response Data ||e61c0000-7df3-4d4e-8e6d-c611745b92e9|| e61c0001-7df3-4d4e-8e6d-c611745b92e9||BYTE ARRAY||17 || 17||Not Configurable ||Scan Response Data, see picture for detail view of data structure

|}

[[File:Lentele0603.png|800px|frameless|center]]
===Command characteristic===
{| class="wikitable" style="width: 100%; background-color: white; border-bottom: 2px solid #0054A6;"
|-
! style="color: #0054A6; background-color: white; border-bottom: 2px solid #0054A6; width: 20px;" |Command's name
! style="color: #0054A6; background-color: white; border-bottom: 2px solid #0054A6; width: 280px;" |Data to send
! style="color: #0054A6; background-color: white; border-bottom: 2px solid #0054A6; width: 280px;" |Description
|-
|Write to flash||0x0010|| Writes set parameters to flash
|-
|General boot||0x0011||Enter boot mode
|-
|Instant reset||0x0012||Software reset
|-
|Reset after connection||0x0013||Reset after disconnect
|-
|Get hw voltage||0x0014||Sets detected hw voltage in response data
|-
|Keep connection alive||0x0015|| Resets disconnect timer
|-
|Restore defaults||0x0016||Sets all configurable parameters to default values
|}

===EYE Sensor Bluetooth frame parsing example===

{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Unparsed data
|-
| style="vertical-align: middle; text-align: center;" |0201061AFF4C000215FFFFFFFF0B8C404510C655AAB636EBEFBB700055020C094D50315F313233343536370EFF9A0801B708B4120CCB0BFFC767
|}
 
{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="4" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Parsed data
|-
! colspan="2" rowspan="1" style="width:33%; vertical-align: middle; text-align: center;" |Parameter
! rowspan="1" style="width:33%; vertical-align: middle; text-align: center;" |HEX Code Part
! rowspan="1" style="width:33%; vertical-align: middle; text-align: center;" |Actual Value
|-
| rowspan="50" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Length
| style="vertical-align: middle; text-align: center;" |02
|
|-

| style="vertical-align: middle; text-align: center;" |Type
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" | Flags
| style="vertical-align: middle; text-align: center;" |06
|-
| style="vertical-align: middle; text-align: center;" | Length
| style="vertical-align: middle; text-align: center;" |1A
|-
| style="vertical-align: middle; text-align: center;" |Type
| style="vertical-align: middle; text-align: center;" |FF
|-
| style="vertical-align: middle; text-align: center;" |Apple company identifier (big endian)
| style="vertical-align: middle; text-align: center;" |4C00
|-
| style="vertical-align: middle; text-align: center;" |Beacon type
| style="vertical-align: middle; text-align: center;" |0215
|-
| style="vertical-align: middle; text-align: center;" |UUID
| style="vertical-align: middle; text-align: center;" |FFFFFFFF0B8C404510C655AAB636EBEF
|-
| style="vertical-align: middle; text-align: center;" | Major
| style="vertical-align: middle; text-align: center;" |BB70
|-
| style="vertical-align: middle; text-align: center;" |Minor
| style="vertical-align: middle; text-align: center;" |0055
|-
| style="vertical-align: middle; text-align: center;" |Power
| style="vertical-align: middle; text-align: center;" |02
|-
| style="vertical-align: middle; text-align: center;" |Length
| style="vertical-align: middle; text-align: center;" |0C
|-
| style="vertical-align: middle; text-align: center;" |Type
| style="vertical-align: middle; text-align: center;" |09
|-
| style="vertical-align: middle; text-align: center;" |Device name
| style="vertical-align: middle; text-align: center;" |4D50315F31323334353637
|-
| style="vertical-align: middle; text-align: center;" |Length
| style="vertical-align: middle; text-align: center;" |0E
|-
| style="vertical-align: middle; text-align: center;" |Type
| style="vertical-align: middle; text-align: center;" |FF
|-
| style="vertical-align: middle; text-align: center;" |Teltonika company ID (big endian)
| style="vertical-align: middle; text-align: center;" |9A08
|-
| style="vertical-align: middle; text-align: center;" |Protocol version
| style="vertical-align: middle; text-align: center;" |01
|
|-
| style="vertical-align: middle; text-align: center;" |Flags
| style="vertical-align: middle; text-align: center;" |B7
|Raw value example 0xB7. Data has to be interpretated as binary value.
In this example would be (MSB)1011 0111(LSB) and is parsed from least significant byte(LSB).

0 – Temperature value presence. 1 Means device is reading and transmitting temperature value.

1 – Humidity value presence. 1 Means device is reading and transmitting humidity value.

2 – Magnetic sensor presence. 1 Means device is reading and transmitting Magnetic sensor value.

3 – Magnetic sensor state (1 magnetic field is detected/0 magnetic field is not detected) Valid value is present only if bit 2 flag is set.

4 – Movement sensor counter. 1 Means device is reading and transmitting movement state and count values.

5 – Movement sensor angle. 1 Means device is reading and transmitting angle roll and pitch values.

6 – Low Battery indication. 0 – Means device battery is from 100 to 15 % (When value changes to 1 Battery level is lower than 15 %.

7 – Battery voltage value presence. 1 Means device is reading and transmitting battery voltage value.
|-
| style="vertical-align: middle; text-align: center;" |Temperature
| style="vertical-align: middle; text-align: center;" |08B4
|Raw value example 0x08B4 hex, 2228 dec.

Raw value needs to be divided by 100.

'''Real temperature''' is 22,28 Celsius.
|-
| style="vertical-align: middle; text-align: center;" | Humidity
| style="vertical-align: middle; text-align: center;" |12
|Raw value example 0x12 hex, 18 dec.
Decimal value is humidity in percent. Humidity 18 %
|-
| style="vertical-align: middle; text-align: center;" | Movement
| style="vertical-align: middle; text-align: center;" |0CCB
| (MSB)0000 1100 1100 1011(LSB) binary
0 - Most significant byte(MSB) represents '''Movement status'''. In this case device is not moving 0. If it was 1 device is moving.

000 1100 1100 1011 – represent detected movements count 3275 decimal value means device has detected total 3275 movement events,
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |0BFFC7
|0B – Most significant byte represents '''device pitch'''. Device pitch can be from -90 to 90 degrees.
In this example device pitch is 0000 1011 (2's complement) = 11° degrees.

FFC7– Two least significant bytes represent '''device roll'''. Device roll can be from -180 to 180 degrees.

In this example device Roll is 1111 1111 1100 0111 (2's complement) = -57° degrees
|-
| style="vertical-align: middle; text-align: center;" |Battery voltage
| style="vertical-align: middle; text-align: center;" |67
|'''Battery voltage –''' raw value example 0x67 hex. Decimal value of parameter 103'''.''' To calculate battery voltage need to use calculation 2000 + (VALUE * 10). In this case battery voltage value 2000+(103x10)= 3030 mV
|}

===FM Packet parsing example (Base firmware / Advanced mode)===

{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" | Unparsed data
|-
| style="vertical-align: middle; text-align: center;" | Received data in hexadecimal stream: <code>00000000000000488E010000017CA6B6BFD8010F0E5188209AB482008600A80F0000000</code> <code>00006000000020019090400560024000301CF0000001601D00000FF4D01D10000006D00000001014B0001B6010000CF7D</code>
|}

{| class="nd-othertables_2" style="width:100%;"
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" | AVL Data Packet Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="4" style="vertical-align: middle; text-align: center;" |
| 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;" |Data Field Length
| style="vertical-align: middle; text-align: center;" |00 00 00 48
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |8E (Codec8 Extended)
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| rowspan="34" style="vertical-align: middle; text-align: center;" |AVL Data
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 7C A6 B6 BF D8 (GMT: Friday, 22 October 2021 06:36:07)
|-
| style="vertical-align: middle; text-align: center;" | Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |0F 0E 51 88
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |20 9A B4 82
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 86
|-
| style="vertical-align: middle; text-align: center;" | Angle
| style="vertical-align: middle; text-align: center;" |00 0A
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |0E
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |00 06
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 02
|-
| style="vertical-align: middle; text-align: center;" |ID
| style="vertical-align: middle; text-align: center;" |00 19 (25 = BLE Temperature #1)
|-
| style="vertical-align: middle; text-align: center;" |Value
| style="vertical-align: middle; text-align: center;" |09 04 (2308=23.08°C)
|-
| style="vertical-align: middle; text-align: center;" |ID
| style="vertical-align: middle; text-align: center;" |00 56 (86 = BLE Humidity #1)
|-
| style="vertical-align: middle; text-align: center;" | Value
| style="vertical-align: middle; text-align: center;" | 00 36 (24 %RHT)
|-
| style="vertical-align: middle; text-align: center;" | N4 of Four Bytes IO
| style="vertical-align: middle; text-align: center;" |00 03
|-
| style="vertical-align: middle; text-align: center;" |ID
| style="vertical-align: middle; text-align: center;" |01 CF (463 - BLE 1 Custom #2 = Movement status and movement events count)
|-
| style="vertical-align: middle; text-align: center;" |Value
| style="vertical-align: middle; text-align: center;" |00 00 00 16 (Currently not moving events count 22)
|-
| style="vertical-align: middle; text-align: center;" |ID
| style="vertical-align: middle; text-align: center;" |01 D0 (464 - BLE 1 Custom #3 = Angle )
|-
| style="vertical-align: middle; text-align: center;" |Value
| style="vertical-align: middle; text-align: center;" |00 00 FF 4D (Pitch = 0°, Roll = -179°)
|-
| style="vertical-align: middle; text-align: center;" |ID
| style="vertical-align: middle; text-align: center;" |01 D1 (465 - BLE 1 Custom #4 = Battery Voltage)
|-
| style="vertical-align: middle; text-align: center;" |Value
| style="vertical-align: middle; text-align: center;" |00 00 00 6D (109 = 2000 + 109 * 10 mV = 3090 mV)
|-

| style="vertical-align: middle; text-align: center;" |N8 of Eight Bytes IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |NX of X Bytes IO
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |N’th IO ID - AVL ID.
| style="vertical-align: middle; text-align: center;" |01 4B (331 - BLE 1 Custom #1 = Flags)
|-
| style="vertical-align: middle; text-align: center;" |Length of Variable Length IO
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" | Value of Variable Length IO
| style="vertical-align: middle; text-align: center;" |B7 = (MSB)11011 0111(LSB)
It's parsed from least significant byte(LSB):

Bit 0 – Temperature value presence.

1 Means device is reading and transmitting temperature value.

Bit 1 – Humidity value presence.

1 Means device is reading and transmitting humidity value.

Bit 2 – Magnetic sensor presence.

1 Means device is reading and transmitting Magnetic sensor value.

Bit 3 – Magnetic sensor state

1 magnetic field is detected/0 magnetic field is not detected) Valid value is present only if bit 2 flag is set.

Bit 4 – Movement sensor counter.

1 Means device is reading and transmitting movement state and count values.

Bit 5 – Movement sensor angle.

1 Means device is reading and transmitting angle roll and pitch values.

Bit 6 – Low Battery indication.

0 – Means device battery is from 100 to 15 % (When value changes to 1 Battery level is lower than 15 %.

7 – Battery voltage value presence.

1 Means device is reading and transmitting battery voltage value.
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 CF 7D
|-
|}
===FM EYE Sensor record parsing example with the new firmware (Evaluation firmware / EYE Sensor filtering by name)===
'''Parsing EYE Sensor records example''' 
Below You will find an example on how to parse EYE Sensor record with two EYE Sensors present.

{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Unparsed data
|-
| style="vertical-align: middle; text-align: center;" |Received data in hexadecimal stream: <code>00000000000000908E0100000183407a2beb000f0e3fe3209ab40e008801290d00002c350001000000000</code> <code>000000000012c3500630130050f4d50315f42453241413500000000000602d60807012f0801000901000a024e000b01f90c025aff0d01000e020bcc</code> <code>30050f4d50315f33464539414100000000000602cb080701300801000901000a0263000b01000c02af000d01000e020b90</code><code>010000fef4</code>
|}

{| class="nd-othertables_2" style="width:100%;"
|+

! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |AVL Data Packet Part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="4" style="vertical-align: middle; text-align: center;" |
| 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;" |Data Field Length
| style="vertical-align: middle; text-align: center;" |00 00 00 90
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |8E (Codec8 Extended)
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| rowspan="24" style="vertical-align: middle; text-align: center;" |AVL Data
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 83 40 7a 2b eb(GMT: Tuesday, 18 June 2019 08:25:22.001)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |0f 0e 3f e3
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |20 9a b4 0e
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 88
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" | 01 29
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" | 0d
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |2c 35 (11317)
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" | 00 00
|-
| style="vertical-align: middle; text-align: center;" | N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |N4 of Four Bytes IO
| style="vertical-align: middle; text-align: center;" |00 00
|-

| style="vertical-align: middle; text-align: center;" |N8 of Eight Bytes IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |NX of X Bytes IO
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |N’th IO ID - AVL ID.
| style="vertical-align: middle; text-align: center;" |2c 35 (11317)
|-
| style="vertical-align: middle; text-align: center;" |Length of Variable Length IO
| style="vertical-align: middle; text-align: center;" |00 63 (99 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Value of Variable Length IO 11317
| style="vertical-align: middle; text-align: center;" |
'''0130050f4d50315f42453241413500000000000602d60807012f0801000901000a024e000b01f90c025aff0d01000e020bcc'''
'''30050f4d50315f33464539414100000000000602cb080701300801000901000a0263000b01000c02af000d01000e020b90'''
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 fe f4
|-
|}

===Parsing AVL ID 11317 data===

{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL ID 11317 Unparsed data
|-
| style="vertical-align: middle; text-align: center;" |<code>'''0130050f4d50315f42453241413500000000000602d60807012f0801000901000a024e000b01f90c025aff0d01000e020bcc'''</code>''' <code>30050f4d50315f33464539414100000000000602cb080701300801000901000a0263000b01000c02af000d01000e020b90'''
|}

{| class="nd-othertables_2" style="width:100%;"
|+

! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Parsing the data
|-
! colspan="2" rowspan="1" style="width:60%; vertical-align: middle; text-align: center;" |AVL Data packet part
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| rowspan="3" |
| style="vertical-align: middle; text-align: center;" |Constant
| style="vertical-align: middle; text-align: center;" |01
|-
! style="vertical-align: middle; text-align: center;" |Eye Sensor #1 data length
| style="vertical-align: middle; text-align: center;" |30 (48 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |05 (Eye Sensor Device name)
|-
| rowspan="60" style="vertical-align: middle; text-align: center;" |AVL Data
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |0f (15 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data
| style="vertical-align: middle; text-align: center;" |4d 50 31 5f 42 45 32 41 41 35 00 00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" | Parameter ID
| style="vertical-align: middle; text-align: center;" |06 (Eye Sensor #1 temperature)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |02 (2 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data
| style="vertical-align: middle; text-align: center;" |d6 08 (With firmware 03.28.04.rev.203 the value is little endian, converted to decimal and multiplied by 0.01C = 22.42C. 
With firmware 03.28.04.rev.204 the value is big endian)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |07 (Eye Sensor #1 Humidity)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |01 (1 byte)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data
| style="vertical-align: middle; text-align: center;" |2f (converted to decimal = 47%)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |08 (Eye Sensor #1 Magnet)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |01 (1 byte)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data
| style="vertical-align: middle; text-align: center;" |00 (no magnet detected)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |09 (EYE Sensor #1 Movement presence)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" | 01 (1 byte)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data
| style="vertical-align: middle; text-align: center;" |00 (none detected)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |0a (parameter ID #10, EYE Sensor #1 Movement count)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data length
| style="vertical-align: middle; text-align: center;" |02 (2 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data
| style="vertical-align: middle; text-align: center;" | 4e 00 (converted to dec = 19968)
|-
| style="vertical-align: middle; text-align: center;" | Parameter ID
| style="vertical-align: middle; text-align: center;" |0b (Parameter ID #11 Eye Sensor #1 Pitch)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data length
| style="vertical-align: middle; text-align: center;" | 01 (1 byte)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data
| style="vertical-align: middle; text-align: center;" |f9 (converted to decimal = 159 degrees)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |0c (Parameter ID #12 Eye sensor #1 Roll)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |02 (2 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data
| style="vertical-align: middle; text-align: center;" |5a ff (With firmware 03.28.04.rev.203 the value is Little endian, converted to decimal signed 2's complement =-166 degrees 
With firmware 03.28.04.rev.204 the value is Big Endian)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |0d (parameter ID #13 low battery voltage indicator)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |01 (1 byte)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data
| style="vertical-align: middle; text-align: center;" |00 (low battery voltage not detected)
|-
| style="vertical-align: middle; text-align: center;" | Parameter ID
| style="vertical-align: middle; text-align: center;" |0e (Eye Sensor #1 battery voltage)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |02 (2 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data
| style="vertical-align: middle; text-align: center;" |0b cc (Converted to decimal = 3020 mV)
|-
! style="vertical-align: middle; text-align: center;" |Eye Sensor #2 data length
| style="vertical-align: middle; text-align: center;" | 30 (48 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" | 05 (Eye Sensor Device name)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |0f (15 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data
| style="vertical-align: middle; text-align: center;" |09 (EYE Sensor #1 Movement presence)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |06 (Eye Sensor #1 temperature)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |02 (2 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data
| style="vertical-align: middle; text-align: center;" |cb 08 (little endian, converted to decimal and multiplied by 0.01C = 22.51C)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |07 (Eye Sensor #1 Humidity)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |01 (1 byte)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data
| style="vertical-align: middle; text-align: center;" |30 (converted to decimal = 48%)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |08 (Eye Sensor #1 Magnet)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |01 (1 byte)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data
| style="vertical-align: middle; text-align: center;" | 00 (no magnet presence detected)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |09 (EYE Sensor #1 Movement presence)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |01 (1 byte)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data
| style="vertical-align: middle; text-align: center;" | 00 (no movement presence detected)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |0a (parameter ID #10, EYE Sensor #1 Movement count)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |02 (2 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data
| style="vertical-align: middle; text-align: center;" |63 00 (converted to decimal = 25344)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |0b (Parameter ID #11 Eye Sensor #1 Pitch)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |01 (1 byte)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data
| style="vertical-align: middle; text-align: center;" |00 (converted to dec = 0 degrees)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |0c (Parameter ID #12 Eye sensor #1 Roll)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |02 (2 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data
| style="vertical-align: middle; text-align: center;" |af 00 (Little endian, converted to decimal signed 2's complement =175 degrees)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |0d (parameter ID #13 low battery voltage indicator)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |01 (1 byte)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data
| style="vertical-align: middle; text-align: center;" |00 (low battery voltage not detected)
|-
| style="vertical-align: middle; text-align: center;" |Parameter ID
| style="vertical-align: middle; text-align: center;" |0e (Eye Sensor #1 battery voltage)
|-
| style="vertical-align: middle; text-align: center;" |Parameter data length
| style="vertical-align: middle; text-align: center;" |02 (2 bytes)
|-
| style="vertical-align: middle; text-align: center;" |Parameter Data
| style="vertical-align: middle; text-align: center;" |0b 90 (Converted to decimal = 2960mV)
|-
|}

==Safety information==
This message contains information on how to operate BTSID1 safely. By following these requirements and recommendations, you will avoid dangerous situations. You must read these instructions carefully and follow them strictly before operating the device!

1. To avoid mechanical damage, it is advised to transport the device in an impact-proof package.

2. In case of malfunction contact yours Teltonika account manager or write to technical support team over VIP helpdesk. 
[[File:Safety.jpg]]

==Certification & Approvals==

{| class="wikitable"
|+
! style="width:50%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Certificates
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |E-Mark (EU)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_E-Mark|YES]]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |FCC (USA)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_FCC|YES]]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |CE/RED (EU)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_CE_/_RED|YES]]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |RoHS (EU)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_RoHS|YES]]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |REACH (EU)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_REACH|YES]]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Anatel (EU) (PR)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_ANATEL|YES]]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |IP rating
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_IP67|YES]]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |SIRIM QAS
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_SIRIM QAS|YES]]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |SDPPI POSTEL
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_SDPPI POSTEL|YES]]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |TELEC
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_TELEC|YES]]
|}

==Nomenclature & Classification codes==

{| class="wikitable"
|+
! style="width:50%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | Name
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |EAN
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_EAN|YES]]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |HS
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_HS|YES]]
|}

==External Links==

===Product Page===
https://teltonika-gps.com/eye/

===Product Change Notifications===

The latest Product Change Notifications can be found: [[BTSMP1_Product_Change_Notifications|Product Change Notifications]]

===Software Errata===
Firmware Errata: [https://wiki.teltonika-gps.com/view/BTS_firmware_errata BTS firmware errata]

EYE App Errata: [https://wiki.teltonika-gps.com/view/EYE_APP_errata BTS APP errata]

===Promotional Material===
[https://wiki.teltonika-gps.com/view/BTSXXX_Promotional_Material| Product Promotional Material Page]

===Compatibilty with other Teltonika Devices===
Teltonika Networks:
https://wiki.teltonika-networks.com/view/Bluetooth_EYE_Sensor_and_EYE_Beacon_support

===Partner Providers Supporting Software===
*[[3Dtracking with Fleet Management (FM)|3Dtracking]]
*[[GPS-server with Fleet Management (FM)|GPS-server]]
*[[Gurtam Wialon with Fleet Management (FM)|Gurtam Wialon]]
*[[Mapon with Fleet Management (FM)|Mapon]]
*[[WhiteLabel Tracking with Fleet Management (FM)|WhiteLabel Tracking]]

==='''[[EYE FAQ|Frequently asked questions (FAQ)]]'''===

*[[EYE FAQ#Questions%20about%20Power%20and%20Electrical%20characteristics|Questions about Power and Electrical characteristics]]
*[[EYE FAQ#Questions%20about%20EYE%20Accessory%20configuration%20.28EYE%20APP.29|Questions about EYE Accessory configuration (EYE APP)]]
*[[EYE FAQ#Questions%20about%20FMBxxx%20compatibility%20with%20EYE%20Accessories|Questions about FMBxxx compatibility with EYE Accessories]]
*[[EYE FAQ#Questions%20about%20Protocols|Questions about Protocols]]
*[[EYE FAQ#Other%20questions%20.28Questions%20without%20category.29|Other questions (Questions without category)]]

===Documents===

{|
|[[File:pdf_icon.png|32px|]]
|[https://teltonika-gps.com/datasheet_eye_sensor.pdf Datasheet PDF]
|(Updated on: {{{datasheet_date|2023-03-13}}})
|
|[[File:pdf_icon.png|32px|]]
|[[Media:Quick-manual-BTSID1.pdf|BTSMP1 Quick Manual (EN)]]
|(Updated on: {{{datasheet_date|2023-03-13}}})
|
|[[File:pdf_icon.png|32px|]]
|[https://wiki.teltonika-gps.com/images/d/d1/North-America-flyer.pdf North America Flyer]
|(Updated on: {{{datasheet_date|2023-03-13}}})
|}

[[Category:Sensors]]

EYE BEACON / BTSID1

2023-08-11T06:40:49Z

Tomas.Gudonis:

EYE BEACON / BTSID1

2023-08-11T06:37:28Z

Tomas.Gudonis:

FTC881

2023-06-14T06:31:24Z

Tomas.Gudonis:

{{Template:FT Home|model=FTC881|description=Small and smart tracker with internal backup battery|image=FTC881_(2).png|link=https://teltonika-gps.com/product/ftc881/}}

File:FTC881 (2).png

2023-06-14T06:31:07Z

Tomas.Gudonis:

FTC881 First Start

2023-06-05T05:38:43Z

Tomas.Gudonis:

{{{description|Small and smart tracker}}}
{{{pic|[[Image:FTC881.png|400px|right]]}}}
 

__TOC__

=='''HOW TO INSERT MICRO-SIM CARD AND CONNECT THE BATTERY'''==

{{{with_battery|
# Gently remove {{{model|FTC881}}} '''cover''' using '''plastic pry tool''' from one side.
# Gently remove {{{model|FTC881}}} '''cover''' using '''plastic pry tool''' from another side.
# Insert '''{{{sim_type|Nano-}}}SIM''' card as shown. Make sure that {{{sim_type|Nano-}}}SIM card '''cut-off corner''' is pointing forward to slot.
# Connect the battery as shown on device. Position the battery in place where it does not obstruct other components.
# Attach device '''cover''' back. Device is ready to be connected.}}}

{{{SIM1|[[Image:FTC881_battery_1.png|850px]]}}}
{{{SIM2|[[Image:FTC881_battery_2.png|550px]]}}}

{|
|-
| [[File:Alert.png|left|link=]] || {{{sim_type|Nano-}}}SIM card insertion/removal must be performed when device is powered off – external voltage {{{battery|and internal battery}}} disconnected. Otherwise {{{sim_type|Nano-}}}SIM card might be damaged or device will not detect it.
|}

=='''PC CONNECTION (WINDOWS)'''==
1. Power- up FTC881 with DC voltage (10-90V) power supply using power wires. LEDs should start blinking.

2. Connect device to computer using Micro-USB cable and install USB driver, see “How to install USB drivers (Windows)1”

=='''HOW TO INSTALL USB DRIVERS (WINDOWS)'''==
1. Please download COM port drivers from [https://wiki.teltonika-gps.com/images/d/d0/TeltonikaCOMDriver.zip here].

2. Extract and run TeltonikaCOMDriver.exe.

3. Click Next in driver installation window.

4. In the following window click Install button.

5. Setup will continue installing the driver and eventually the confirmation window will appear. Click Finish to complete the
setup.

=='''CONFIGURATION (WINDOWS)'''==

At first FTC881 device will have default factory settings set. These settings should be changed according to the user's needs. Main
configuration can be performed via [https://wiki.teltonika-gps.com/view/Telematics_Configuration_Tool_(TCT) Teltonika Configurator tool (TCT)].

=='''MOUNTING RECOMMENDATIONS'''==
'''DEVICE FASTENING'''

• Locate the battery in your vehicle. If present remove the battery cover to access the battery.

• There is a double sided tape on the back of the device, use it to attach the device on the battery, so that the GNSS antenna
and LEDs indicators are facing up.

'''CONNECTING POWER SOURCE'''

• Device power wire is designed to be directly connected to the positive terminal fastener of the vehicle battery.

'''CONNECTING GROUND WIRE'''

• Connect ground wire to the vehicle frame or metal parts that are fixed to the frame.

• If the wire is fixed with the bolt, the loop must be connected to the end of the wire.

• Device ground wire is designed to be directly connected to the negative terminal fastener of the vehicle battery.

[[Category:FTC881]]

File:FTC881 battery 2.png

2023-06-05T05:38:32Z

Tomas.Gudonis:

File:FTC881 battery 1.png

2023-06-05T05:38:14Z

Tomas.Gudonis:

File:FTC881.png

2023-06-05T05:33:21Z

Tomas.Gudonis:

FTC921 First Start

2023-06-05T05:31:58Z

Tomas.Gudonis:

{{{description|Small and smart tracker}}}
{{{pic|[[Image:FTC921.png|400px|right]]}}}
 

__TOC__

=='''HOW TO INSERT MICRO-SIM CARD AND CONNECT THE BATTERY'''==

{{{with_battery|
# Gently remove {{{model|FTC921}}} '''cover''' using '''plastic pry tool''' from one side.
# Gently remove {{{model|FTC921}}} '''cover''' using '''plastic pry tool''' from another side.
# Insert '''{{{sim_type|Nano-}}}SIM''' card as shown. Make sure that {{{sim_type|Nano-}}}SIM card '''cut-off corner''' is pointing forward to slot.
# Connect the battery as shown on device. Position the battery in place where it does not obstruct other components.
# Attach device '''cover''' back. Device is ready to be connected.}}}

{{{SIM1|[[Image:FTC921_How_to_insert_SIM_card_1.png|850px]]}}}
{{{SIM2|[[Image:FTC921_How_to_insert_SIM_card_2.png|550px]]}}}

{|
|-
| [[File:Alert.png|left|link=]] || {{{sim_type|Nano-}}}SIM card insertion/removal must be performed when device is powered off – external voltage {{{battery|and internal battery}}} disconnected. Otherwise {{{sim_type|Nano-}}}SIM card might be damaged or device will not detect it.
|}

=='''PC CONNECTION (WINDOWS)'''==
1. Power- up FTC921 with DC voltage (10-90V) power supply using power wires. LEDs should start blinking.

2. Connect device to computer using Micro-USB cable and install USB driver, see “How to install USB drivers (Windows)1”

=='''HOW TO INSTALL USB DRIVERS (WINDOWS)'''==
1. Please download COM port drivers from [https://wiki.teltonika-gps.com/images/d/d0/TeltonikaCOMDriver.zip here].

2. Extract and run TeltonikaCOMDriver.exe.

3. Click Next in driver installation window.

4. In the following window click Install button.

5. Setup will continue installing the driver and eventually the confirmation window will appear. Click Finish to complete the
setup.

=='''CONFIGURATION (WINDOWS)'''==

At first FTC921 device will have default factory settings set. These settings should be changed according to the user's needs. Main
configuration can be performed via [https://wiki.teltonika-gps.com/view/Telematics_Configuration_Tool_(TCT) Teltonika Configurator tool (TCT)].

=='''MOUNTING RECOMMENDATIONS'''==
'''DEVICE FASTENING'''

• Locate the battery in your vehicle. If present remove the battery cover to access the battery.

• There is a double sided tape on the back of the device, use it to attach the device on the battery, so that the GNSS antenna
and LEDs indicators are facing up.

'''CONNECTING POWER SOURCE'''

• Device power wire is designed to be directly connected to the positive terminal fastener of the vehicle battery.

'''CONNECTING GROUND WIRE'''

• Connect ground wire to the vehicle frame or metal parts that are fixed to the frame.

• If the wire is fixed with the bolt, the loop must be connected to the end of the wire.

• Device ground wire is designed to be directly connected to the negative terminal fastener of the vehicle battery.

[[Category:FTC921]]

File:FTC921.png

2023-06-05T05:31:44Z

Tomas.Gudonis:

File:FTC881 pinout.png

2023-06-01T11:54:48Z

Tomas.Gudonis: Tomas.Gudonis uploaded a new version of File:FTC881 pinout.png

File:FTC881 pinout.png

2023-06-01T11:52:25Z

Tomas.Gudonis:

File:FTC881 KNOW YOUR DEVICE.PNG

2023-06-01T11:48:42Z

Tomas.Gudonis: Tomas.Gudonis uploaded a new version of File:FTC881 KNOW YOUR DEVICE.PNG

FTC921 SMS/call settings

2023-05-31T07:58:56Z

Tomas.Gudonis: /* SMS security */

==SMS security==
[[File:FTC961 Call Settings.png|400px|right]]

'''Password''' — Layer of security when configuring devices using SMS commands. Configure the password that will be required for each SMS or add authorized numbers.

[[Category:FTC921 Configuration]]

FTC921 SMS/call settings

2023-05-31T07:57:31Z

Tomas.Gudonis: Created page with "==SMS security== right '''Password''' — Layer of security when configuring devices using SMS commands. Configure the password that w..."

==SMS security==
[[File:FTC921 Call Settings.png|400px|right]]

'''Password''' — Layer of security when configuring devices using SMS commands. Configure the password that will be required for each SMS or add authorized numbers.

[[Category:FTC921 Configuration]]

FTC921 Device status

2023-05-29T12:30:50Z

Tomas.Gudonis:

==Device information==
[[File:FTC921_device_info.png|right|700 px]]

'''Device name''' — Device Hardware name/model

'''IMEI''' — Device International Mobile Equipment Identity number

'''Firmware version'''— current device firmware version

[[Category:FTC921 Configuration]]

FTC921 Device status

2023-05-29T12:30:05Z

Tomas.Gudonis:

FTC921 Device status

2023-05-29T12:26:58Z

Tomas.Gudonis: Created page with "320 px"

[[File:FTC921_device_info.png|right|320 px]]

File:FTC921 device info.png

2023-05-29T12:26:54Z

Tomas.Gudonis:

FTC921 Features

2023-05-29T12:23:49Z

Tomas.Gudonis:

==Overspeeding==
[[File:FTC921_Overspeeding.png|right|300 px]]

When vehicle speed exceeds configured maximum speed value the scenario is activated, and an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}. Detected speed has to be greater than configured max speed +3% of configured max speed for the overspeeding event to start. To stop overspeeding event detected speed has to be lower than configured max speed -3% of configured max speed.
Configurable parameters:

 
*Priority – defines the priority of overspeeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
*Max speed – it is the maximum allowed speed that can be reached. If the speed exceeded configured value, then the event will occur.

==Trip==
[[File:FTC921_Trip.png|right|300 px]]

''Trip''' section offers user to configure the ''Trip'' feature. ''Trip'' starts when Ignition according ''Ignition source'' is ON and Movement according ''Movement source'' is ON and also 'Start Speed' is exceeded. ''Start Speed'' defines the minimum GPS speed in order to detect ''Trip'' start. ''Ignition OFF Timeout'' is the timeout value to detect ''Trip'' end once the Ignition (configured ignition source) is off. I/O Trip Odometer must be enabled to use ''Distance counting mode'' feature. When it is set to Continuous, ''Trip'' distance is going to be counted continuously (from ''Trip'' start to ''Trip'' end) and written to I/O ''Trip Odometer'' value field. When ''Trip'' is over and the next ''Trip'' begins, ''Trip Odometer'' value is reset to zero. When ''Mode'' is set to Between Records, the distance is going to be counted between every record made. This value is written to I/O ''Trip Odometer'' value field and is reset to zero every new record until the ''Trip'' ends. If later all Odometer values are summed up manually, the distance driven during the whole duration of the ''Trip'' can be obtained. 

==Odometer settings==
[[File:FTC921_Odometer_settings.png|right|300 px]]

{{{par_src|''Calculation Source'' allows to choose Odometer calculation source between GNSS, OBD. }}}''Odometer Value'' sets the starting total odometer value.

==Unplug detection==
[[File:FTC921_Unplug_detection.png|right|300 px]]

An event will be generated when {{{model|FMB1YX}}} is unplugged from {{{txt_src|external power}}} or plugged back in again.
'''Priority'''
* '''Disable''' - disable scenario.
* '''Low Priority''' - when low priority event is triggered, device '''makes additional record''' with indication of event cause.
* '''High Priority''' - module makes additional record with High priority flag and '''sends event packet immediately''' to the server by
'''GPRS'''.

==Static navigation==
[[File:FTC921_Static_navigation.png|right|300 px]]

''Static Navigation Mode'' is a filter, which filters out track jumps when the object is stationary. 
If the Static navigation filter is disabled, it will apply no changes to GPS data. If the Static navigation filter is enabled, it will filter changes in GPS position if no movement (configured movement source) or ignition (configured ignition source) is detected (depends on what static navigation settings are selected: movement, ignition or both sources). It allows filtering GPS jumps when an object is parked (is not moving) and GPS position is still traced. 

==Digital output overcurrent recovery==
[[File:FTC921_Digital_output_overcurrent_recovery.png|right|300 px]]

[[Category:FTC921 Configuration]]

FTC921 Features

2023-05-29T12:19:12Z

Tomas.Gudonis:

FTC921 Features

2023-05-29T12:18:21Z

Tomas.Gudonis:

==Driving behavior==

===Overspeeding===
[[File:FTC921_Overspeeding.png|right|300 px]]

When vehicle speed exceeds configured maximum speed value the scenario is activated, and an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}. Detected speed has to be greater than configured max speed +3% of configured max speed for the overspeeding event to start. To stop overspeeding event detected speed has to be lower than configured max speed -3% of configured max speed.
Configurable parameters:

 
*Priority – defines the priority of overspeeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
*Max speed – it is the maximum allowed speed that can be reached. If the speed exceeded configured value, then the event will occur.

===Trip===
[[File:FTC921_Trip.png|right|300 px]]

''Trip''' section offers user to configure the ''Trip'' feature. ''Trip'' starts when Ignition according ''Ignition source'' is ON and Movement according ''Movement source'' is ON and also 'Start Speed' is exceeded. ''Start Speed'' defines the minimum GPS speed in order to detect ''Trip'' start. ''Ignition OFF Timeout'' is the timeout value to detect ''Trip'' end once the Ignition (configured ignition source) is off. I/O Trip Odometer must be enabled to use ''Distance counting mode'' feature. When it is set to Continuous, ''Trip'' distance is going to be counted continuously (from ''Trip'' start to ''Trip'' end) and written to I/O ''Trip Odometer'' value field. When ''Trip'' is over and the next ''Trip'' begins, ''Trip Odometer'' value is reset to zero. When ''Mode'' is set to Between Records, the distance is going to be counted between every record made. This value is written to I/O ''Trip Odometer'' value field and is reset to zero every new record until the ''Trip'' ends. If later all Odometer values are summed up manually, the distance driven during the whole duration of the ''Trip'' can be obtained. 

===Odometer settings===
[[File:FTC921_Odometer_settings.png|right|300 px]]

{{{par_src|''Calculation Source'' allows to choose Odometer calculation source between GNSS, OBD. }}}''Odometer Value'' sets the starting total odometer value.

==Vehicle protection==

===Unplug detection===
[[File:FTC921_Unplug_detection.png|right|300 px]]

An event will be generated when {{{model|FMB1YX}}} is unplugged from {{{txt_src|external power}}} or plugged back in again.
'''Priority'''
* '''Disable''' - disable scenario.
* '''Low Priority''' - when low priority event is triggered, device '''makes additional record''' with indication of event cause.
* '''High Priority''' - module makes additional record with High priority flag and '''sends event packet immediately''' to the server by
'''GPRS'''.

==Other features==

===Static navigation===
[[File:FTC921_Static_navigation.png|right|300 px]]

''Static Navigation Mode'' is a filter, which filters out track jumps when the object is stationary. 
If the Static navigation filter is disabled, it will apply no changes to GPS data. If the Static navigation filter is enabled, it will filter changes in GPS position if no movement (configured movement source) or ignition (configured ignition source) is detected (depends on what static navigation settings are selected: movement, ignition or both sources). It allows filtering GPS jumps when an object is parked (is not moving) and GPS position is still traced. 

===Digital output overcurrent recovery===
[[File:FTC921_Digital_output_overcurrent_recovery.png|right|300 px]]

[[Category:FTC921 Configuration]]

FTC921 Features

2023-05-29T12:14:47Z

Tomas.Gudonis: Created page with "==Driving behavior== ===Overspeeding=== 300 px When vehicle speed exceeds configured maximum speed value the scenario is activated, an..."

File:FTC921 Digital output overcurrent recovery.png

2023-05-29T12:03:11Z

Tomas.Gudonis:

File:FTC921 Static navigation.png

2023-05-29T12:02:28Z

Tomas.Gudonis:

File:FTC921 Unplug detection.png

2023-05-29T12:02:13Z

Tomas.Gudonis:

File:FTC921 Odometer settings.png

2023-05-29T12:01:40Z

Tomas.Gudonis:

File:FTC921 Trip.png

2023-05-29T12:01:11Z

Tomas.Gudonis:

File:FTC921 Overspeeding.png

2023-05-29T12:00:50Z

Tomas.Gudonis:

FTC921 Tracking settings

2023-05-29T11:50:37Z

Tomas.Gudonis:

==Records settings==
[[File:FTC921_Records_settings.png|right|320 px]]

'''Saving / sending mode'''

This feature will be used to save and send records to server without time sinchronization.

'''Possible options:'''

''After Position Fix'' - records will be saved and send only after position fix

''After Time Sync'' - records will be saved and send only after time synchronization

''Always'' - records will be always saved and send even if will not be time synchronization

Note: If record is without valid coordinates – (there were no GPS fix in the moment of data acquisition) – Longitude, Latitude and Altitude values are last valid fix, and Angle, Satellites and Speed are 0. After a reboot, it will send zero coordinates.

'''Sort by'''

Can be set either Newest or Oldest. For example if the Oldest is marked the device first will send the Oldest information, if Newest then Device will send the newest information. If the device had no connection (GSM or GPRS) due to bad coverage or being in an area with no signal. Device continues to save records into internal memory, once GSM and GPRS are recovered device will start sending saved data to server. In this example, if Oldest is configured - until newest data is seen on the server all of the oldest records have to be sent first. If Newest is configured - previous data and track won't be seen until newest data is sent first. If high priority on I/O parameters or Features are configured device will send the generated records with High Priority first.

'''Data protocol'''

In ''Data Protocol'' settings user can choose which protocol version ('''[[Codec#Codec 8|Codec 8]]''' or '''[[Codec#Codec 8 Extended|Codec 8 Extended]]''') will use for data sending to the server. 

==Records profile settings==
[[File:FTC921_Records_profile_settings_1.png|right|400 px]]
[[File:FTC921_Records_profile_settings_2.png|right|380 px]]

Data Acquisition modes are an essential part of {{{model|FTC921}}} device, they are also highly configurable. Through configuration user defines how records will be saved and sent. There are two different modes: Home and Roaming. All these modes with configured data acquisition and report frequencies depend on the current GSM Operator and are switched when GSM operator changes (e.g. vehicle passes through a country border). If current GSM operator is defined as Home Operator, the device will work in Home Data Acquisition mode, if the current operator is defined as Roaming Operator, the device will work in Roaming Data Acquisition mode. This functionality allows having different AVL records to acquire and send parameter values when the object is moving or standing still. Vehicle moving or stop state is defined by the Stop Detection Source parameter. There are {{{txt_num|3}}} ways for {{{model|FTC921}}} to switch between Vehicle on Stop and Vehicle Moving modes, please refer to Movement settings in {{{ctrSystem|[[FTC921 System]]}}}. 

The operator search is performed every 15 minutes. Depending on the current GSM operator Home or Roaming mode can be changed faster than every 15 minutes. This process is separate from the operator search. Movement criteria are checked every second.

 

'''Record Saving settings'''

''Min Saved Records'' defines the minimum number of coordinates and I/O data that should be transferred within a single connection to the server. If {{{model|FTC921}}} does not have enough coordinates to send to the server, it will check again after a time interval defined in ''Send Period'' field. ''Send period'' controls the frequency of data being sent to the server over GPRS. The module makes attempts to send collected data to the server every defined period of time. If it does not have enough records (depends on the parameter ''Min. Saved Records'' described above), it tries again after the defined time interval.

{| class="wikitable" style="border-style: solid; border-width: 0px"
|+
|-
| style="text-align: left; background: #F6F6FB;" | [[Image:Bw_nb.png|50px]]
| style="text-align: left; background: #F6F6FB;" | Keep in mind that {{{model|FTC921}}} operates in GMT:0 time zone, without daylight saving.
|}

{{{model|FTC921}}} is able to collect records using four methods at the same time: time, distance, angle, and speed-based data acquisition:
* Time based data acquisition (''Min Period'') – records are acquired every time when a defined interval of time passes. Entering zero disables data acquisition based on time.
* Distance-based data acquisition (''Min Distance'') – records are acquired when the distance between the previous coordinate and current position is greater than a defined parameter value. Entering zero disables data acquisition based on distance.
* Angle based data acquisition (''Min Angle'') – records are acquired when the angle difference between the last recorded coordinate and current position is greater than a defined value. Entering zero disables data acquisition based on the angle.
* Speed based data acquisition (''Min Speed Delta'') – records are acquired when the speed difference between the last recorded coordinate and current position is greater than a defined value. Entering zero disables data acquisition based on speed.

[[Image:Fmb120_daq_mode_basis.png|700px|none]]

[[Category:FTC921 Configuration]]

FTC921 Tracking settings

2023-05-29T11:49:50Z

Tomas.Gudonis: Created page with "==Records settings== 320 px '''Saving / sending mode''' This feature will be used to save and send records to server without time..."

File:FTC921 Records profile settings 2.png

2023-05-29T11:23:45Z

Tomas.Gudonis:

File:FTC921 Records profile settings 1.png

2023-05-29T11:23:29Z

Tomas.Gudonis:

File:FTC921 Records settings.png

2023-05-29T11:21:16Z

Tomas.Gudonis:

FTC921 Accessories

2023-05-29T11:01:10Z

Tomas.Gudonis:

{{Template:Accessories|model=FTC921
|Teltonika DualCam =
|Teltonika ADAS =
|LV-CAN200 =
|ALL-CAN300 =
|CAN-CONTROL =
|ECAN01 =
|1-Wire Temperature Sensor =
|1-Wire TTJ Temperature Sensor =
|1-Wire iButton Reader =
|1-Wire RFID Reader =
|EYE Beacon =
|EYE Sensor =
}}
[[Category:FTC921 Manual]]

FTC921 Accessories

2023-05-29T10:59:57Z

Tomas.Gudonis: Created page with "{{Template:Accessories|model=FMB920 |Teltonika DualCam = |Teltonika ADAS = |LV-CAN200 = |ALL-CAN300 = |CAN-CONTROL = |ECAN01 = |1-Wire Temperature Sensor = |1-Wire TTJ..."

{{Template:Accessories|model=FMB920
|Teltonika DualCam =
|Teltonika ADAS =
|LV-CAN200 =
|ALL-CAN300 =
|CAN-CONTROL =
|ECAN01 =
|1-Wire Temperature Sensor =
|1-Wire TTJ Temperature Sensor =
|1-Wire iButton Reader =
|1-Wire RFID Reader =
|EYE Beacon =
|EYE Sensor =
}}
[[Category:FMB920 Manual|8]]

FMB920 Accessories

2023-05-29T10:59:40Z

Tomas.Gudonis:

FMB920 Accessories

2023-05-29T10:59:20Z

Tomas.Gudonis:

FTC921 First Start

2023-05-29T10:10:44Z

Tomas.Gudonis: /* CONFIGURATION (WINDOWS) */

{{{description|Small and smart tracker}}}
{{{pic|[[Image:|400px|right]]}}}
 

__TOC__

=='''HOW TO INSERT MICRO-SIM CARD AND CONNECT THE BATTERY'''==

{{{with_battery|
# Gently remove {{{model|FTC921}}} '''cover''' using '''plastic pry tool''' from one side.
# Gently remove {{{model|FTC921}}} '''cover''' using '''plastic pry tool''' from another side.
# Insert '''{{{sim_type|Nano-}}}SIM''' card as shown. Make sure that {{{sim_type|Nano-}}}SIM card '''cut-off corner''' is pointing forward to slot.
# Connect the battery as shown on device. Position the battery in place where it does not obstruct other components.
# Attach device '''cover''' back. Device is ready to be connected.}}}

{{{SIM1|[[Image:FTC921_How_to_insert_SIM_card_1.png|850px]]}}}
{{{SIM2|[[Image:FTC921_How_to_insert_SIM_card_2.png|550px]]}}}

{|
|-
| [[File:Alert.png|left|link=]] || {{{sim_type|Nano-}}}SIM card insertion/removal must be performed when device is powered off – external voltage {{{battery|and internal battery}}} disconnected. Otherwise {{{sim_type|Nano-}}}SIM card might be damaged or device will not detect it.
|}

=='''PC CONNECTION (WINDOWS)'''==
1. Power- up FTC921 with DC voltage (10-90V) power supply using power wires. LEDs should start blinking.

2. Connect device to computer using Micro-USB cable and install USB driver, see “How to install USB drivers (Windows)1”

=='''HOW TO INSTALL USB DRIVERS (WINDOWS)'''==
1. Please download COM port drivers from [https://wiki.teltonika-gps.com/images/d/d0/TeltonikaCOMDriver.zip here].

2. Extract and run TeltonikaCOMDriver.exe.

3. Click Next in driver installation window.

4. In the following window click Install button.

5. Setup will continue installing the driver and eventually the confirmation window will appear. Click Finish to complete the
setup.

=='''CONFIGURATION (WINDOWS)'''==

At first FTC921 device will have default factory settings set. These settings should be changed according to the user's needs. Main
configuration can be performed via [https://wiki.teltonika-gps.com/view/Telematics_Configuration_Tool_(TCT) Teltonika Configurator tool (TCT)].

=='''MOUNTING RECOMMENDATIONS'''==
'''DEVICE FASTENING'''

• Locate the battery in your vehicle. If present remove the battery cover to access the battery.

• There is a double sided tape on the back of the device, use it to attach the device on the battery, so that the GNSS antenna
and LEDs indicators are facing up.

'''CONNECTING POWER SOURCE'''

• Device power wire is designed to be directly connected to the positive terminal fastener of the vehicle battery.

'''CONNECTING GROUND WIRE'''

• Connect ground wire to the vehicle frame or metal parts that are fixed to the frame.

• If the wire is fixed with the bolt, the loop must be connected to the end of the wire.

• Device ground wire is designed to be directly connected to the negative terminal fastener of the vehicle battery.

[[Category:FTC921]]

FTC921 First Start

2023-05-29T09:17:04Z

Tomas.Gudonis:

{{{description|Small and smart tracker}}}
{{{pic|[[Image:|400px|right]]}}}
 

__TOC__

=='''HOW TO INSERT MICRO-SIM CARD AND CONNECT THE BATTERY'''==

{{{with_battery|
# Gently remove {{{model|FTC921}}} '''cover''' using '''plastic pry tool''' from one side.
# Gently remove {{{model|FTC921}}} '''cover''' using '''plastic pry tool''' from another side.
# Insert '''{{{sim_type|Nano-}}}SIM''' card as shown. Make sure that {{{sim_type|Nano-}}}SIM card '''cut-off corner''' is pointing forward to slot.
# Connect the battery as shown on device. Position the battery in place where it does not obstruct other components.
# Attach device '''cover''' back. Device is ready to be connected.}}}

{{{SIM1|[[Image:FTC921_How_to_insert_SIM_card_1.png|850px]]}}}
{{{SIM2|[[Image:FTC921_How_to_insert_SIM_card_2.png|550px]]}}}

{|
|-
| [[File:Alert.png|left|link=]] || {{{sim_type|Nano-}}}SIM card insertion/removal must be performed when device is powered off – external voltage {{{battery|and internal battery}}} disconnected. Otherwise {{{sim_type|Nano-}}}SIM card might be damaged or device will not detect it.
|}

=='''PC CONNECTION (WINDOWS)'''==
1. Power- up FTC921 with DC voltage (10-90V) power supply using power wires. LEDs should start blinking.

2. Connect device to computer using Micro-USB cable and install USB driver, see “How to install USB drivers (Windows)1”

=='''HOW TO INSTALL USB DRIVERS (WINDOWS)'''==
1. Please download COM port drivers from [https://wiki.teltonika-gps.com/images/d/d0/TeltonikaCOMDriver.zip here].

2. Extract and run TeltonikaCOMDriver.exe.

3. Click Next in driver installation window.

4. In the following window click Install button.

5. Setup will continue installing the driver and eventually the confirmation window will appear. Click Finish to complete the
setup.

=='''CONFIGURATION (WINDOWS)'''==

At first FTC921 device will have default factory settings set. These settings should be changed according to the user's needs. Main
configuration can be performed via Teltonika Configurator tool1 (TCT).

=='''MOUNTING RECOMMENDATIONS'''==
'''DEVICE FASTENING'''

• Locate the battery in your vehicle. If present remove the battery cover to access the battery.

• There is a double sided tape on the back of the device, use it to attach the device on the battery, so that the GNSS antenna
and LEDs indicators are facing up.

'''CONNECTING POWER SOURCE'''

• Device power wire is designed to be directly connected to the positive terminal fastener of the vehicle battery.

'''CONNECTING GROUND WIRE'''

• Connect ground wire to the vehicle frame or metal parts that are fixed to the frame.

• If the wire is fixed with the bolt, the loop must be connected to the end of the wire.

• Device ground wire is designed to be directly connected to the negative terminal fastener of the vehicle battery.

[[Category:FTC921]]

FTC921 First Start

2023-05-29T09:14:58Z

Tomas.Gudonis:

{{{description|Small and smart tracker}}}
{{{pic|[[Image:|400px|right]]}}}
 

__TOC__

=='''HOW TO INSERT MICRO-SIM CARD AND CONNECT THE BATTERY'''==

{{{with_battery|
# Gently remove {{{model|FTC921}}} '''cover''' using '''plastic pry tool''' from one side.
# Gently remove {{{model|FTC921}}} '''cover''' using '''plastic pry tool''' from another side.
# Insert '''{{{sim_type|Nano-}}}SIM''' card as shown. Make sure that {{{sim_type|Nano-}}}SIM card '''cut-off corner''' is pointing forward to slot.
# Connect the battery as shown on device. Position the battery in place where it does not obstruct other components.
# Attach device '''cover''' back. Device is ready to be connected.}}}

{{{SIM1|[[Image:FTC921_How_to_insert_SIM_card_1.png|850px]]}}}
{{{SIM2|[[Image:FTC921_How_to_insert_SIM_card_2.png|550px]]}}}

{|
|-
| [[File:Alert.png|left|link=]] || {{{sim_type|Nano-}}}SIM card insertion/removal must be performed when device is powered off – external voltage {{{battery|and internal battery}}} disconnected. Otherwise {{{sim_type|Nano-}}}SIM card might be damaged or device will not detect it.
|}

=='''PC CONNECTION (WINDOWS)=='''
1. Power- up FTC921 with DC voltage (10-90V) power supply using power wires. LEDs should start blinking.

2. Connect device to computer using Micro-USB cable and install USB driver, see “How to install USB drivers (Windows)1”

=='''HOW TO INSTALL USB DRIVERS (WINDOWS)'''==
1. Please download COM port drivers from [https://wiki.teltonika-gps.com/images/d/d0/TeltonikaCOMDriver.zip here].

2. Extract and run TeltonikaCOMDriver.exe.

3. Click Next in driver installation window.

4. In the following window click Install button.

5. Setup will continue installing the driver and eventually the confirmation window will appear. Click Finish to complete the
setup.

=='''CONFIGURATION (WINDOWS)'''==

At first FTC921 device will have default factory settings set. These settings should be changed according to the user's needs. Main
configuration can be performed via Teltonika Configurator tool1 (TCT).

=='''MOUNTING RECOMMENDATIONS'''==
'''DEVICE FASTENING'''

• Locate the battery in your vehicle. If present remove the battery cover to access the battery.

• There is a double sided tape on the back of the device, use it to attach the device on the battery, so that the GNSS antenna
and LEDs indicators are facing up.

'''CONNECTING POWER SOURCE'''

• Device power wire is designed to be directly connected to the positive terminal fastener of the vehicle battery.

'''CONNECTING GROUND WIRE'''

• Connect ground wire to the vehicle frame or metal parts that are fixed to the frame.

• If the wire is fixed with the bolt, the loop must be connected to the end of the wire.

• Device ground wire is designed to be directly connected to the negative terminal fastener of the vehicle battery.

[[Category:FTC921]]

File:FTC921 PINOUT.png

2023-05-29T08:44:38Z

Tomas.Gudonis:

File:FTC921 KNOW YOUR DEVICE.png

2023-05-29T08:36:50Z

Tomas.Gudonis:

File:FTC921 Ultra sleep.png

2023-05-29T07:05:27Z

Tomas.Gudonis: