Difference between revisions of "EYE BEACON / BTSID1"

From Wiki Knowledge Base | Teltonika GPS
(223 intermediate revisions by 19 users not shown)
Line 1: Line 1:
 
__TOC__
 
__TOC__
  
==<p style="font-size:32px"><span style="color:#0054A6">Introduction</span></p>==
+
==<p style="font-size:72px><span style="color:#0054A6">Introduction</span></p>==
 
Wireless solutions open up new horizons for your business and help to keep an eye on your assets. Discover our
 
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 beacon model from Teltonika with robust waterproof
+
brand-new and certified Bluetooth Low Energy ID beacon model from Teltonika with robust waterproof
 
casing and a long-lifetime battery. The model designed for a low-cost fast and easy configuration and integration to
 
casing and a long-lifetime battery. The model designed for a low-cost fast and easy configuration and integration to
 
save precious time, resources, and ensure accountability.
 
save precious time, resources, and ensure accountability.
[[File:BTSID1-datasheet-2023-12-18.2.png|center|frameless|1157x1157px]]
+
[[File:EYE device.png|center|frameless|1157x1157px]]
  
==<p style="font-size:32px><span style="color:#0054A6">About BTSID1</span></p>==
+
==<p style="font-size:72px><span style="color:#0054A6">About BTSID1</span></p>==
 
Perfect for traceability use cases, delivery tracking, monitoring of various movable objects in logistics (trailers,
 
Perfect for traceability use cases, delivery tracking, monitoring of various movable objects in logistics (trailers,
 
containers), agriculture (tractor attachments), and constructions (tools and inventory). Also, it suitable for indoor
 
containers), agriculture (tractor attachments), and constructions (tools and inventory). Also, it suitable for indoor
Line 15: Line 15:
 
platform which provides extended functionality. Configure, scan, and update anytime anywhere with a dedicated
 
platform which provides extended functionality. Configure, scan, and update anytime anywhere with a dedicated
 
Teltonika mobile app.
 
Teltonika mobile app.
==<p style="font-size:32px><span style="color:#0054A6">Product Specification</span></p>==
+
==<p style="font-size:72px><span style="color:#0054A6">Product Specification</span></p>==
 
===Features===
 
===Features===
 
{| class="wikitable"
 
{| class="wikitable"
Line 47: Line 47:
 
|-
 
|-
 
| 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;" |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;" |620 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;" |Replaceable
Line 53: Line 53:
 
|-
 
|-
 
| 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;" |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;" |4 years
+
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |5+ years
|-
+
(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;" |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;" |8 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;" |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;" |10 years
+
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |10+ years
 +
(Tx=2 dBm; interval: 10s)
 
|}
 
|}
 
{| class="wikitable"
 
{| class="wikitable"
Line 74: Line 73:
 
! 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 #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
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Bluetooth® 4.2 compliant
+
| 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;" |Range
Line 118: Line 118:
 
|-
 
|-
 
| 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;" |Eddystone
 +
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Yes
 +
|}
 +
{| class="wikitable"
 +
|+
 +
! style="width:10%; 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="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |CE (EU)
 +
| 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;" |FCC (USA)
 +
| 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;" |UKCA (UK)
 +
| 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;" |RoHS
 +
| 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;" |E-mark
 
| 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;" |Yes
 
|}
 
|}
Line 124: Line 144:
 
[[File:Eye dimensions.png]]
 
[[File:Eye dimensions.png]]
  
==<p style="font-size:32px><span style="color:#0054A6">Value-adding Features</span></p>==
+
==<p style="font-size:72px><span style="color:#0054A6">Mounting recomendations</span></p>==
 
+
[[File:Mounting recomendations.jpg]]
===<p style="font-size:24px"><span style="color:#0054A6">Hibernate mode</span>===
 
 
 
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.  Order codes are described on [https://teltonika-gps.com/products/accessories/sensors-beacons/eye eye page]
 
 
 
====<p style="font-size:24px"><span style="color:#0054A6">Value of hibernate mode</span>====
 
 
 
Hibernated versions of EYE devices simplify stock management for our partners while maximizing battery life. <br>1. '''Accelerated delivery times:'''
 
 
 
By stocking up on hibernated EYE devices, you ensure readiness to deploy EYE devices with full battery capacity at any moment. This proactive approach provides fastest possible service, increases your reputation for efficiency and positions you as an industry frontrunner, enhancing your competitive edge.
 
 
 
2. '''Mitigated project risks:'''
 
 
 
In scenarios where projects encounter unforeseen challenges, our hibernated EYE devices offer a buffer. Hibernate feature allows to safeguard your investments and potential revenue streams. This means that even if projects encounter delays or complications, you can still deploy EYE devices with full battery capacity, ensuring optimal performance when the time is right.
 
 
 
====<p style="font-size:24px"><span style="color:#0054A6">How to activate hibernated eye device?</span>====
 
 
 
Attach any magnet to sleeping device and wait for LED to blink.
 
<br>'''NOTE: ANY MAGNET CAN BE USED'''
 
<br>[[File:520746 Magnet EYE gif v1.6-min.gif|frameless|684x684px]]
 
<br>Now device is discoverable, scannable, connectable via BLE.
 
 
 
====<p style="font-size:24px"><span style="color:#0054A6">How to send the device to hibernate mode?</span>====
 
 
 
If you want to put the EYE device back to hibernate mode after accidental activation or simply pause its use, you may do that following steps below:
 
<br>Step 1. While connected and in overview tap "Send device to sleep":
 
<br>Step 2. Confirm your selection:                                   
 
<br>Step 3. Wait for EYE App to disconnect:                           
 
<br>[[File:Device screen 1.2.8 2.jpg|400x400px]][[File:Screenshot 20230509 173323 EYE APP.jpg|400x400px]][[File:Screenshot 20230512 164509 Gallery.jpg|400x400px]]
 
 
 
====<p style="font-size:24px"><span style="color:#0054A6">Can All devices hibernate?</span>====
 
 
 
1. All EYE Sensors with firmware version starting from 1.2.9.R.8 can hibernate.
 
 
 
2. Only new EYE Beacons bought with order codes that have hardware modification can hibernate standard codes are available in [https://teltonika-gps.com/products/accessories/sensors-beacons/eye eye page], for special order codes consult your sales manager.
 
 
 
==<p style="font-size:32px><span style="color:#0054A6">Mounting recomendations</span></p>==
 
[[File:Neweyemouning.png]]
 
 
<br>
 
<br>
[[File:New mounting recomendations 1.png]]
+
[[File:Mounting recomendations 1.jpg]]
  
==<p style="font-size:32px><span style="color:#0054A6">EYE App Configuration</span></p>==
+
==<p style="font-size:72px><span style="color:#0054A6">EYE Accessory Configuration</span></p>==
  
 
Devices work constantly and are ready to perform out of the box. Default basic Sensor settings are set to:
 
Devices work constantly and are ready to perform out of the box. Default basic Sensor settings are set to:
 
<br>• Transmitting at 2 dBm power.
 
<br>• Transmitting at 2 dBm power.
<br>• Data advertising at 5 second intervals.
+
<br>• Data advertising at 3 second intervals.
 
<br>• Eddystone protocol
 
<br>• Eddystone protocol
 
<br>
 
<br>
Line 179: Line 161:
 
<br>
 
<br>
  
===<p style="font-size:24px><span style="color:#0054A6">Eye App Overview</span>===
+
===Eye app===
'''With the application you will be able to scan for visible Teltonika EYE devices, check their statuses, connect for configuration, download it or update the firmware.'''<br>
+
'''With the application you will be able to scan for visible Teltonika EYE devices, check their statuses or connect for configuration or firmware update.'''
 +
<br>
 
{|
 
{|
 
|- align="TOP"
 
|- align="TOP"
|[[File:1.1.1.jpg]]
 
 
|
 
|
 +
|[[File:Detailed list - collapsed(2).jpg|border|360x640px|none]]
 
|
 
|
 +
|[[File:Overview - without update (beacon)(2).png|border|360x640px|none]]
 
|
 
|
|[[File:2.1.1.jpg]]
+
|[[File:Basic settings(2).png|right|border|360x640px]]
 
|
 
|
|
+
|[[File:Advance settings 4.png|right|border|360x640px]]
|
 
|[[File:3.1.1.jpg]]
 
|
 
|
 
|
 
|[[File:4.1.1.jpg]]
 
 
|}
 
|}
  
 
 
<br>
 
<br>
[[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<br>
+
[[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 you will go to device overview window.
 +
<br>
 +
<br>
 +
[[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.
 +
<br>
 
<br>
 
<br>
[[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 and download the configuration. If you select to Configure device new window will open with Basic and Advanced settings. Other actions include changing the device PIN code and putting the device to sleep. A device in sleep mode will no longer be findable or connectable via the app. To wake it up, you need to attach a magnet and look for a green LED flashing.<br>
+
[[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 transmition type*. For more settings go to Advanced settings tab to enable various events.
 
<br>
 
<br>
[[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.<br>
 
 
<br>
 
<br>
 
[[File:Group 117.png|sub|frameless|upright=0.2|link=|alt=]]'''Advanced configuration window''': 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
 
[[File:Group 117.png|sub|frameless|upright=0.2|link=|alt=]]'''Advanced configuration window''': 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
Line 217: Line 197:
 
'''*iOS doesn't show devices with iBeacon protocol'''
 
'''*iOS doesn't show devices with iBeacon protocol'''
  
==<p style="font-size:32px><span style="color:#0054A6">FM Tracker Configuration</span></p>==
+
==<p style="font-size:72px><span style="color:#0054A6">FM Tracker Configuration</span></p>==
  
===<p style="font-size:24px"><span style="color:#0054A6">Teltonika configurator (Base firmware)</span>===
+
===Teltonika configurator===
  
If you have firmware / configurator which does not support EYE Beacon tab in Bluetooth® 4.0 section, then you can use Beacon list section of the configurator to scan available EYE Beacons.
+
If you have firmware / configurator which does not support EYE Beacon tab in Bluetooth 4.0 section, then you can use Beacon list section of the configurator to scan available EYE Beacons.
 
<br>
 
<br>
 
Below are short instructions which show how we recommend configuring the device to Enable the Beacon functionality for testing.
 
Below are short instructions which show how we recommend configuring the device to Enable the Beacon functionality for testing.
Line 228: Line 208:
  
 
#In System Settings Enable [[Codec#Codec_8_Extended|Codec8 Extended]];
 
#In System Settings Enable [[Codec#Codec_8_Extended|Codec8 Extended]];
#In [[FMB120_Bluetooth®_settings|Bluetooth®]] settings Enable Bluetooth®, set this setting as either "Enable (hidden)" or "Enable (visible)", otherwise Bluetooth® will be disabled;
+
#In [[FMB120_Bluetooth_settings|Bluetooth]] settings Enable Bluetooth, set this setting as either "Enable (hidden)" or "Enable (visible)", otherwise Bluetooth will be disabled;
#In [[FMB120_Bluetooth®_4.0_settings|Bluetooth® 4.0]] settings, 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|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_Beacon_List|Beacon list]] settings, configure Beacon Detection as "All" and Beacon Record as "Eventual". This will detect all surrounding Beacons and create Beacon records every 30 seconds.
 
#In [[FMB120_Beacon_List|Beacon list]] settings, configure Beacon Detection as "All" and Beacon Record as "Eventual". This will detect all surrounding Beacons and create Beacon records every 30 seconds.
  
 
[[Image:Beacon_project_V3.gif]]
 
[[Image:Beacon_project_V3.gif]]
  
===<p style="font-size:24px"><span style="color:#0054A6">Teltonika configurator new functionalities (Evaluation firmware)</span>===
 
  
'''Bluetooth® 4.0'''
+
===Teltonika configurator new functionalities (unreleased)===
 +
 
 +
'''Bluetooth 4.0'''
 +
<br>
 +
Functionalities were reorganized and transferred to Bluetooth 4.0 configuration tab with additional horizontal tabs selection for specific settings:
 
<br>
 
<br>
 +
* '''Global''' - Parameters responsible for device scanning ability like power and duratations.
 +
* '''Beacon''' - Parameters to enable Beacon scanning scenarios.
 
<br>
 
<br>
 
'''Common settings'''
 
'''Common settings'''
Line 245: Line 230:
 
* '''BLE Scan Duration''' - Sensors data reading time. 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.
 
* '''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.
+
* '''BT Power Level''' - Telematics device Bluetooth power level setting.
 
* '''BLE Broadcasting service ID''' - Telematics device can broadcast configured ID.
 
* '''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.
 
* ''' BLE connection control''' - Connection mode settings. If broadcasting ID is configured, parameter should be set to Prohibit.
 
<br>
 
<br>
[[File:BLE_4.0.png]]
+
[[File:Configurator GUI changes.png]]
<br>
 
 
 
 
<br>
 
<br>
'''Beacon List'''
 
 
<br>
 
<br>
 +
'''Beacons'''
 
<br>
 
<br>
 
Beacons configuration instruction: [https://wiki.teltonika-gps.com/view/How_to_start_with_FMB_devices_and_Beacons%3F How to start with FMB devices and Beacons?]
 
Beacons configuration instruction: [https://wiki.teltonika-gps.com/view/How_to_start_with_FMB_devices_and_Beacons%3F How to start with FMB devices and Beacons?]
 
<br>
 
<br>
 
<br>
 
<br>
[[File:Beacon settings.png]]
+
[[File:EYE Beacons configurator.png]]
 
<br>
 
<br>
 
<br>
 
<br>
[[File:Beacon all settings.png|right|border]]
+
'''Beacon detection''' - Parameter controls over all Beacons scanning: [[File:Beacon detection configurator.png|right|border]]
'''Beacon detection''' - Parameter controls over all Beacons scanning:  
 
 
* '''Disabled''' – Beacon scanning and transmitting disabled.
 
* '''Disabled''' – Beacon scanning and transmitting disabled.
 
* '''All''' – Read all visible beacons;
 
* '''All''' – Read all visible beacons;
 
* '''Configured''' – Read only beacons set in Beacon List;
 
* '''Configured''' – Read only beacons set in Beacon List;
'''Beacon Mode'''  
+
* '''Teltonika MAC''' – Filter and transmit only Teltonika EYE packets*.
* '''Simple''' - beacon parsing is done automatically (Eddystone and iBeacon protocols are supported).  
+
    *It allows to filter only MAC addresses which will be assigned to BTSX device. The MAC address that is currently filtered by this parameter is FD:5F:9A:XX:XX:XX.
* '''Advanced''' - beacon data capturing can be configured.<br>
+
<br>
'''Beacon record'''  
+
<br>
 +
'''Beacon record''' [[File:Beacon record on change.png|right|border]]
 +
'''Eventual''' settings have two modes:
 +
* '''Monitoring''' - Beacon record generating every scan period
 
* '''On change''' - Beacon records are generated only when there are changes in scanned list.
 
* '''On change''' - Beacon records are generated only when there are changes in scanned list.
* '''Periodic''' - Beacon record generating according to the configured Record Period on Move and Record Period on Stop parameters.
+
'''Periodic''' - records are generated according to Period settings. When there is no visible beacons, empty record will be generated.
*'''Beacon Record Priority''' - When set to '''None''' Records will not be generated. '''Low priority''' means the Module makes an additional record which will be sent according to configured send period. When '''High Priority''' is configured, the Beacon record will be sent immediately to the server as soon as it is generated.<br>
 
 
<br>
 
<br>
'''EYE Beacon Settings'''
 
 
<br>
 
<br>
 +
'''Beacon Mode''' [[File:Beacon Mode SImple.png|right|border]]
 +
* '''Simple''' - beacon parsing is done automatically (Eddystone and iBeacon protocols are supported).
 +
* '''Advanced''' - beacon data capturing can be configured.
 
<br>
 
<br>
[[File:Beacon detection.gif]]
 
 
<br>
 
<br>
*The New firmware has two Beacon lists, so it is possible to create two separate lists of beacons, standard one with Beacons ID (UUID:Major:Minor, or Namespace:InstanceID) and new one according Beacon Name (by name or prefix, for example all beacons with prefix "ID1" can be saved.)
+
'''Filter type''' [[File:Filter Type.png|right|border]]
 +
New firmware has two Beacon lists, so it is possible to create two separate lists of beacons, standard one with Beacons ID (UUID:Major:Minor, or Namespace:InstanceID) and new one according Beacon Name (by name or prefix, for example all beacons with prefix "ID1" can be saved.
 
<br>
 
<br>
* '''Beacon ID''' - configurator allows to configure beacon ID in iBeacon or Eddystone format in Beacon List.
+
* '''Beacon ID''' - configurator allows to configure beacon id in iBeacon or Eddystone format.
* '''Beacon Name''' - The names of beacons which need to be filtered can be entered. Only the beginning part of the EYE Beacon local name has to match. For example, if in the EYE Beacon name list “EYE_Beacon” is added and the FM tracker detects EYE_Beacon1, EYE_Beacon2, EYE_BeaconXYZ, all these EYE Beacons will be added to EYE Beacon name list.
+
* '''Beacon Name''' - user can enter names of beacons which needs to be filtered. It would filter the full name or only if the prefix of the name is configured like “BTS”.
Both ID and Name filters can work at the same time. If beacon doesn’t match ID filter, but matches the name, it will be added to beacon list. However, Filtering only works Beacon Mode is set to Simple.
 
 
<br>
 
<br>
<br>  [[File:Eye Beacon Prox.png|right|border]]
+
Both ID and Name filters can work at the same time. If beacon doesn’t match ID filter, but matches the name, it will be added to beacon list. Filtering only works Beacon Mode is set to Simple.
 
<br>
 
<br>
'''Eye feature mode: Proximity'''
 
 
EYE beacon Proximity events is a functionality which creates three different types of records, depending on the captured Beacons RSSI level. This functionality is only supported with Teltonika EYE beacons.<br> Proximity events consist of near, away and lost events: <br>
 
*When EYE beacon RSSI level is below the first configured threshold, the beacon will be added to Near Beacon Record '''(AVL ID: 10828)'''
 
*When EYE BEACON RSSI level is between the second and first configured threshold, beacon is added to Away Beacon record '''(AVL ID: 10829)'''
 
*When EYE Beacon RSSI level is lower than the second configured threshold, beacon is added to Lost Beacon record '''(AVL ID: 10831)'''. In the case of EYE Beacon disappearing from the environment and not being detected by the FM tracker anymore, the beacon will be added to Lost Beacon record and will be removed from Beacon list.
 
 
'''Event modes''' <br>
 
*Disabled – Record generating is disabled for the selected range
 
*Periodic – Records will be periodically generated for the selected range, according to the configured record period on move or on stop value.
 
*On Change – Records will be generated as soon as the Eye Beacon number changes for the selected range.
 
 
'''Averaging Timeout''' <br>
 
This parameter specifies how long it will take current RSSI value to reach new RSSI value. For example, current EYE Beacon RSSI value is -40 dBm. FMB captures same EYE Beacon with RSSI value of -60 dBm. If averaging timeout is configured to be 10 seconds, it will take 10 seconds for RSSI value to reach -60 dBm from -40 dBm. Keep in mind that this is assuming perfect conditions and subsequent EYE Beacon RSSI
 
 
'''Eye feature mode: Lost & Found '''<br>
 
[[File:Lost & found.png]]
 
 
'''Lost & Found  EYE Beacon feature.'''<br>
 
Purpose of this functionality is to '''periodically''' generate records with all EYE Beacon list (AVL ID: 10828) and create eventual '''On Change''' records only when EYE Beacon is lost (AVL ID: 10831) or found (AVL ID: 10829). <br>
 
Lost and Found Beacon records only include EYE Beacon which was lost or found, not the full Beacon list. <br>
 
*If multiple EYE Beacons were found or lost at the same time, multiple will be  included into the record. <br>
 
*If Visible Beacon List is enabled, Beacon records containing the list of visible beacons will be generated according to the configured period parameters ''Record Period on Move'' and ''Record Period on Stop''
 
Advanced Beacon protocol is being used to send Lost & Found records.  <br>
 
Note:Same AVL ID’s as for Proximity events are being used, since two features cannot work at the same time.
 
 
*'''AVL ID: 10828''' Visible Beacon List (periodic)
 
*'''AVL ID: 10829''' Found Beacon List (On Change)
 
*'''AVL ID: 10831''' Lost Eye Beacon List (On Change)
 
 
 
'''Proximity and Lost & found AVL ID''' elements have the following structure:<br> [[File:1st beacon protocol version.png|border]]
 
 
When Proximity or Lost & Found events are sent, the records will always include Beacon RSSI, Beacon ID, low battery indicator and Battery Voltage.
 
 
Below is the mentioned Parameters description:
 
{| class="wikitable nd-othertables_2" style="width:100%;" ;
 
|+'''Table 1. EYE Beacon Parameter IDs'''
 
|-
 
!Parameter ID!!Name
 
!Data type!!Description
 
|-
 
| 0||Beacon RSSI Level
 
|1 byte unsigned integer||Received signal strength indication (RSSI) value in dBm.
 
Hex value must be converted to decimal from signed 2s complement.
 
|-
 
|1||Beacon ID
 
|Array||For EYE Beacons that are transmitting using Eddystone protocol: Beacon ID is Namespace , InstanceID (16 bytes)
 
For EYE beacons that are transmitting using iBeacon protocol: Beacon ID is UUID, Major, Minor (20 bytes)
 
|-
 
|13
 
|EYE Beacon Low battery indicator
 
|1 byte integer
 
|Low battery state measured by EYE beacon; value is either 0 (low voltage not detected) or 1 (low voltage detected)
 
|-
 
|14
 
|EYE Beacon battery Voltage
 
|2 byte unsigned integer
 
|EYE Beacon battery voltage value in mV
 
|-
 
|15
 
|EYE Beacon MAC
 
|6 byte unsigned integer
 
|Device’s MAC address is sent if it's enabled in FMB configuration
 
|-
 
|}
 
 
==<p style="font-size:32px><span style="color:#0054A6">EYE Beacon Protocol overview</span></p>==
 
 
===Beacon advertising===
 
 
<br>
 
<br>
[[image:Beacon and sensors data.png|center|1000x1000px|alt=|frameless]]
+
'''Proximity'''  [[File:Proximity.png|right|border]]
 
<br>
 
<br>
 +
'''Proximity Events''' allow to configure 3 different zones: Near, Away, Far Away. There is additional Lost parameter for beacons which were lost from any of the 3 zones. Averaging timeout determines period how often results are evaluated to avoid fake event detection. Periodic option will generate records at known interval while On Change option will generate record when beacon enters/exits certain zone.
 
<br>
 
<br>
 
===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.
 
<br><br>
 
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.
 
<br><br>
 
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).
 
<br><br>
 
Device Name has the following default value for Beacon – ID1_XXXXXXX
 
 
<br>
 
<br>
<div style="display:inline-table">
+
'''Proximity IO''' elements have the following structure [[File:1st beacon protocol version.png|bottom|border]]
{| 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:
 
<br>0 – Temperature value presence
 
<br>1 – Humidity value presence
 
<br>2 – Magnetic sensor presence
 
<br>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.
 
<br>4 – Movement sensor counter
 
<br>5 – Movement sensor angle
 
<br>'''6 – Low Battery indication (if set to 1 low battery voltage detected)
 
<br>'''7 – Battery voltage value presence'''
 
  
 +
==<p style="font-size:72px><span style="color:#0054A6">Protocol overwiev</span></p>==
  
 
+
===Beacon advertising===
'''Note:''' only bolded bits (6 and 7) can have value 1, on BTSID1
+
<br>
|-
+
[[File:Beacon advertising.png|center]]
|Value 7||1|| Battery Voltage
 
<br>Battery voltage in mV = 2000 + VALUE * 10
 
<br>NOTE: present only if bit 7 is set, otherwise is not being sent
 
|}
 
</div>
 
<div style="display:inline-table"></div>
 
 
<br>
 
<br>
 
===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 || 12 || 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*
 
 
 
<small>*Max 2 with 01.02.10+ firmware</small>
 
| 1 for EYE_Beacon,
 
4 for EYE_Sensor*
 
 
 
<small>*with 01.02.10+ firmware 1 for both EYE_Beacon & EYE_Sensor</small>
 
| 0 - iBeacon
 
1 - Eddystone
 
2 - EYE Sensor
 
3 - iBeacon + EYE Sensor*
 
4 - Eddystone + EYE Sensor*
 
 
 
<small>*01.02.10+ sensors are enabled over ''Activate / Deactivate Sensors''</small>
 
|-
 
|Activate / Deactivate Sensors*
 
 
 
<small>*from 01.02.10+ firmware</small>
 
|e61c0000-7df2-4d4e-8e6d-c611745b92e9
 
|e61c0021-7df2-4d4e-8e6d-c611745b92e9
 
|UINT8
 
|0
 
|15
 
(0b1111)
 
|4 (0b0100) for EYE_Beacon,
 
15 (0b1111) for EYE_Sensor
 
|(LSb) bit 0 – Temperature
 
Bit 1 – Humidity
 
 
Bit 2 – Magnetic
 
 
Bit 3 - Movement
 
 
 
E.g. EYE_Sensor disabled movement & enabled temperature, humidity, magnetic sensors 7 (0b0111)
 
|-
 
 
| Advertising Interval|| e61c0000-7df2-4d4e-8e6d-c611745b92e9 || e61c0002-7df2-4d4e-8e6d-c611745b92e9 || UINT16 || 1000 || 10000 || 5000 || 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<br>2 B - major<br>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<br>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|| 6 bytes||6 bytes||123456||Always 6 Digits
 
 
|-
 
 
|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
 
|-
 
| 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
 
|}
 
  
 
===FM packet parsing example===
 
===FM packet parsing example===
Beacon (AVL ID:385) has the following structure:
 
{| class="nd-othertables_2" style="width:100%;"
 
|+
 
! colspan="7" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL 385 Parsing
 
|+
 
|Data part
 
|BLE beacon flags #1
 
|Beacon ID #1
 
|Signal Strength #1
 
|Beacon data #2
 
|-
 
|1 Byte
 
| 1 Byte
 
|20/16 Bytes
 
| 1 Byte
 
|…
 
|-
 
|First half byte – current data part
 
 
Second half byte – total number of data parts
 
|Bitwise parameter, specify BLE beacon type and parameters.
 
 
Two options available are:
 
  
21    iBeacon with RSSI
 
 
01    Eddystone with RSSI
 
|Beacon – 20B (UUID, major, minor)
 
 
Eddystone – 16B (Namespace, Instance ID)
 
|Signed 2's complement
 
|
 
|
 
|
 
|}
 
 
====Eddystone example with 1 beacon====
 
 
{| class="nd-othertables_2" style="width:100%;"
 
{| class="nd-othertables_2" style="width:100%;"
 
|+
 
|+
Line 722: Line 339:
 
| style="vertical-align: middle; text-align: center;" |01 81 (385)
 
| style="vertical-align: middle; text-align: center;" |01 81 (385)
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" | N of Total ID
+
| style="vertical-align: middle; text-align: center;" |N of Total ID
 
| style="vertical-align: middle; text-align: center;" |00 01
 
| style="vertical-align: middle; text-align: center;" |00 01
 
|-
 
|-
Line 758: Line 375:
 
|}
 
|}
  
 
+
==<p style="font-size:72px><span style="color:#0054A6">Safety information</span></p>==
{| class="nd-othertables_2" style="width:100%;"
 
|+
 
! colspan="7" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL 385 Parsing
 
|-
 
|Data part
 
|BLE beacon flags #1
 
|Beacon ID #1
 
|Signal Strength #1
 
|Beacon data #2
 
|-
 
| 1 Byte
 
|1 Byte
 
|20/16 Bytes
 
| 1 Byte
 
|…
 
|-
 
|11 – Data part, 1 Record out of 1 Beacon Packet.
 
|01 – Eddystone with RSSI
 
|Eddystone – 16B (Namespace, Instance ID)
 
 
 
 
 
 
 
 
 
 
 
E39B606AA38255AA8E46  – BLE Beacon Namespace
 
 
 
0B154E2D0055 – BLE Beacon Instance ID
 
|  -49
 
| -
 
| -
 
| -
 
|}
 
 
 
====iBeacon example with 2 beacons====
 
 
 
{| 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 5A
 
|-
 
| 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 6B 69 B0 C9 51(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;" |00 00 00 00
 
|-
 
| style="vertical-align: middle; text-align: center;" |Latitude
 
| style="vertical-align: middle; text-align: center;" |00 00 00 00
 
|-
 
| style="vertical-align: middle; text-align: center;" |Altitude
 
| style="vertical-align: middle; text-align: center;" |00 00
 
|-
 
| style="vertical-align: middle; text-align: center;" |Angle
 
| style="vertical-align: middle; text-align: center;" |00 00
 
|-
 
| style="vertical-align: middle; text-align: center;" |Satellites
 
| style="vertical-align: middle; text-align: center;" |00
 
|-
 
| 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;" |01 81 (385)
 
|-
 
| 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;" |01 81 (385)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Length of Variable Length IO
 
| style="vertical-align: middle; text-align: center;" |00 2D
 
|-
 
| style="vertical-align: middle; text-align: center;" |Value of Variable Length IO
 
| style="vertical-align: middle; text-align: center;" |11216B817F8A274D4FBDB62D33E1842F8DF8014D022BBF21A579723675064DC396A7C3520129F61900000000BF
 
|-
 
| 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 3E 5D
 
|-
 
|}
 
 
 
 
 
{| class="nd-othertables_2" style="width:100%;"
 
|+
 
! colspan="7" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL 385 Parsing
 
|+
 
|Data part
 
|BLE beacon flags #1
 
|Beacon ID #1
 
|Signal Strength #1
 
|Beacon data #2
 
|-
 
| 1 Byte
 
| 1 Byte
 
|20/16 Bytes
 
| 1 Byte
 
|…
 
|-
 
|11 – Data part, 1 Record out of 1 Beacon Packet.
 
|21 –  iBeacon with RSSI
 
|6B817F8A274D4FBDB62D33E1842F8DF8 – UUID
 
 
 
014D – Major
 
 
 
022B – Minor
 
| -65
 
|21A579723675064DC396A7C3520129F61900
 
000000BF
 
|-
 
| -
 
|21 –  iBeacon with RSSI
 
|A579723675064DC396A7C3520129F619 – UUID
 
0000 – Major
 
 
 
0000 – Minor
 
| -65
 
| -
 
| -
 
| -
 
|}
 
 
 
 
 
===<p style="font-size:24px"><span style="color:#0054A6">FM EYE Beacon record parsing example with the new firmware</span>===
 
Below You will find an example on how to parse lost (AVL ID 10831) or found (AVL ID 10829) EYE Beacon record.
 
 
 
 
 
====Lost & found EYE Beacon records 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;" |Received data in hexadecimal stream: <code>000000000000004b8e010000018368952793000f0e54fc209ab05800b300b40e0000<br>
 
2a4f000100000000000000000001</code><span style="background-color:#91d4b9;">2a4f001e011c0001a40110eb47706aa38255aa96f21a154e2d00550d01000e020bd6<code>010000823f</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 4b
 
|-
 
| 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 68 95 27 93 (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 54 fc
 
|-
 
| style="vertical-align: middle; text-align: center;" |Latitude
 
| style="vertical-align: middle; text-align: center;" |20 9a b0 58
 
|-
 
| style="vertical-align: middle; text-align: center;" |Altitude
 
| style="vertical-align: middle; text-align: center;" |00 b3
 
|-
 
| style="vertical-align: middle; text-align: center;" |Angle
 
| style="vertical-align: middle; text-align: center;" |00 b4
 
|-
 
| 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;" |2a 4f (10831)
 
|-
 
| 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;" |2a 4f (10831)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Length of Variable Length IO
 
| style="vertical-align: middle; text-align: center;" |00 1e (30 bytes)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Value of Variable Length IO 10831
 
| style="vertical-align: middle; text-align: center;" |
 
'''011c0001a40110eb47706aa38255aa96f21a154e2d00550d01000e020bd6'''
 
|-
 
| 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 01 2a 4f
 
|-
 
|}
 
 
 
 
 
{| class="nd-othertables_2" style="width:100%;"
 
|+
 
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL ID 10831 Unparsed data
 
|-
 
| style="vertical-align: middle; text-align: center;" |<code>'''011c0001a40110eb47706aa38255aa96f21a154e2d00550d01000e020bd6'''</code>'''<br>'''
 
|}
 
 
 
{| 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 Beacon #1 data length
 
| style="vertical-align: middle; text-align: center;" |1c (28 bytes)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |00 (Eye Beacon RSSI)
 
|-
 
| 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;" |01 (1 byte)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter data
 
| style="vertical-align: middle; text-align: center;" |a4 (Converted to Decimal from signed 2s complement = -92dBm)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |01 (Beacon ID)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter data length
 
| style="vertical-align: middle; text-align: center;" |10 (16 bytes)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter data
 
| style="vertical-align: middle; text-align: center;" |eb 47 70 6a a3 82 55 aa 96 f2 '''1a 15 4e 2d 00 55''' (Eddystone Namespace + '''Instance ID''')
 
|-
 
| 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 (no low battery voltage detected)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |0e (Eye Beacon 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 d6 (3030mV)
 
|-
 
|}
 
NOTE: The record structure for Lost Beacon Record (AVL ID:10829) is the same
 
 
 
====Visible EYE Beacons record parsing example with 3 EYE Beacons====
 
Below You will find an example on how to parse visible Beacons list (AVL ID 10828) EYE Beacon record.
 
 
 
{| 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: <br>
 
<code>00000000000000898e0100000183a1c8fbe3000f0e310b209ab02600e900760d0000<span style="background-color:#91d4b9;">2a4c0001000000000000000000012a4c005c011c0001c00110eb577075868d55aa96021b20313800550d0100</code><br><code><span style="background-color:#91d4b9;">0e020c1c1c0001b60110ef3f3f74868d55aa9aeae91e313800550d01000e020bae200001a50114faffffff34b6f6aa38255aa9ef619154d0e200050d01000e020ad2</code><code>0100008811</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 89
 
|-
 
| 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="80" 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 a1 c8 fb e3 (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 31 0b
 
|-
 
| style="vertical-align: middle; text-align: center;" |Latitude
 
| style="vertical-align: middle; text-align: center;" |20 9a b0 26
 
|-
 
| style="vertical-align: middle; text-align: center;" |Altitude
 
| style="vertical-align: middle; text-align: center;" |00 e9
 
|-
 
| style="vertical-align: middle; text-align: center;" |Angle
 
| style="vertical-align: middle; text-align: center;" |00 76
 
|-
 
| 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;" |2a 4c (10828)
 
|-
 
| 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;" |2a 4c (10828)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Length of Variable Length IO
 
| style="vertical-align: middle; text-align: center;" |00 5c (92 bytes)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Value of Variable Length IO 10831
 
| style="vertical-align: middle; text-align: center;" |
 
'''011c0001c00110eb577075868d55aa96021b20313800550d01000e020c1c1c0001b60110ef3f3f74868d55aa9aeae91e313800550d01000e020bae<br>200001a50114faffffff34b6f6aa38255aa9ef619154d0e200050d01000e020ad2'''
 
|-
 
| 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 88 11
 
|-
 
|}
 
 
 
{| class="nd-othertables_2" style="width:100%;"
 
|+
 
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL ID 10828 Unparsed data
 
|-
 
| style="vertical-align: middle; text-align: center;" |<code>'''011c0001c00110eb577075868d55aa96021b20313800550d01000e020c1c1c0001b60110ef3f3f74868d55aa9aeae91e31380055'''</code><br><code>0d01000e020bae200001a50114faffffff34b6f6aa38255aa9ef619154d0e200050d01000e020ad2<br>
 
|}
 
 
 
{| 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 Beacon #1 data length
 
| style="vertical-align: middle; text-align: center;" |1c (28 bytes)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |00 (Eye Beacon RSSI)
 
|-
 
| 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;" |01 (1 byte)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter data
 
| style="vertical-align: middle; text-align: center;" |c0 (Converted to Decimal from signed 2s complement = -64dBm)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |01 (Beacon ID)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter data length
 
| style="vertical-align: middle; text-align: center;" |10 (16 bytes)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter data
 
| style="vertical-align: middle; text-align: center;" |eb 57 70 75 86 8d 55 aa 96 02 '''1b 20 31 38 00 55''' (Eddystone Namespace + '''Instance ID''')
 
|-
 
| 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 (no low battery voltage detected)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |0e (Eye Beacon 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;" |0c 1c (3100mV)
 
|-
 
! style="vertical-align: middle; text-align: center;" |Eye Beacon #2 data length
 
| style="vertical-align: middle; text-align: center;" |1c (28 bytes)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |00 (Eye Beacon RSSI)
 
|-
 
| 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;" |b6 (Converted to Decimal from signed 2s complement = -74dBm)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |01 (Beacon ID)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter data length
 
| style="vertical-align: middle; text-align: center;" |10 (16 bytes)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter data
 
| style="vertical-align: middle; text-align: center;" |ef 3f 3f 74 86 8d 55 aa 9a ea '''e9 1e 31 38 00 55''' (Eddystone Namespace + '''Instance ID''')
 
|-
 
| 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 (no low battery voltage detected)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |0e (Eye Beacon 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 ae (2990mV)
 
|-
 
! style="vertical-align: middle; text-align: center;" |Eye Beacon #3 data length
 
| style="vertical-align: middle; text-align: center;" |20 (32 bytes)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |00 (Eye Beacon RSSI)
 
|-
 
| 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;" |a5 (Converted to Decimal from signed 2s complement = -91dBm)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |01 (Beacon ID)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter data length
 
| style="vertical-align: middle; text-align: center;" |14 (20 bytes)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter data
 
| style="vertical-align: middle; text-align: center;" |fa ff ff ff 34 b6 f6 aa 38 25 5a a9 ef 61 91 54 '''''d0 e2''''' '''00 05''' (iBeacon UUID + '''''Major''''' + '''Minor''')
 
|-
 
| 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 (no low battery voltage detected)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Parameter ID
 
| style="vertical-align: middle; text-align: center;" |0e (Eye Beacon 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;" |0a d2 (2770mV)
 
|-
 
|}
 
 
 
==<p style="font-size:32px"><span style="color:#0054A6">Safety information</span></p>==
 
 
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!
 
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.
 
1. To avoid mechanical damage, it is advised to transport the device in an impact-proof package.
  
2. In case of malfunction contact your Teltonika account manager or write to the technical support team over the Helpdesk.<br>
+
2. In case of malfunction contact yours Teltonika account manager or write to technical support team over VIP helpdesk.<br>
[[File:Safety information.png]]
+
[[File:Safety.jpg]]
  
==<p style="font-size:32px"><span style="color:#0054A6">Certification & Approvals</span></p>==
+
==<p style="font-size:72px><span style="color:#0054A6">External Links</span></p>==
 
 
{| 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;" |Links
 
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Valid for Model
 
|-
 
| 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;" |[[BTSID1_E-Mark|Yes]]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |All
 
|-
 
| 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;" |[[BTSID1_FCC|Yes]]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |All
 
|-
 
| 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;" |[[BTSID1_CE_/_RED|Yes]]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |All
 
|-
 
| 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;" |[[BTSID1_RoHS|Yes]]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |All
 
|-
 
| 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;" |[[BTSID1_REACH|Yes]]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |All
 
|-
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Anatel (BR) (PR)
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSID1_ANATEL|Yes]]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |All
 
|-
 
| 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;" |[[BTSID1_IP67|Yes]]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |All
 
|-
 
| 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;" |[[BTSID1_SIRIM QAS|Yes]]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |All
 
|-
 
| 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;" |[[BTSID1_SDPPI POSTEL|Yes]]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |All
 
|-
 
| 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;" |[[BTSID1_TELEC|Yes]]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |All
 
|-
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |ATEX
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSID1_ATEX|Yes]]
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |ATEX
 
|}
 
 
 
==<p style="font-size:32px"><span style="color:#0054A6">Memberships</span></p>==
 
 
 
{| 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;" |Links
 
|-
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Bluetooth® SIG
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSID1 Bluetooth® SIG|Yes]]
 
|-
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |WEEE
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSID1 WEEE|Yes]]
 
|}
 
 
 
==<p style="font-size:32px"><span style="color:#0054A6">Nomenclature & Classification codes</span></p>==
 
 
 
{| 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;" |Links
 
|-
 
| 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;" |[[BTSID1_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;" |[[BTSID1_HS|Yes]]
 
|-
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |ECCN
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSID1_ECCN|Yes]]
 
|}
 
 
 
==<p style="font-size:32px"><span style="color:#0054A6">External Links</span></p>==
 
 
 
 
 
===Product Page===
 
 
https://teltonika-gps.com/eye/
 
https://teltonika-gps.com/eye/
  
===Product Change Notifications===
+
[[Category:EYE Accessories]]
 
 
The latest Product Change Notifications can be found: [[BTSID1_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 EYE 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
 
 
 
https://wiki.teltonika-networks.com/view/Teltonika_EYE_device_pairing_and_data_sender_configuration_example
 
 
 
===Partner Providers Supporting Software===
 
*[[3Dtracking with Fleet Management (FM)|3Dtracking]]
 
*[[GPS-server with Fleet Management (FM)|GPS-server]]
 
*[[Wialon with Fleet Management (FM)|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|]]
 
|[[Media:Datasheet-BTSID1 EYE BEACON 4.1.pdf|Eye Beacon Datasheet]]
 
|<small>(Updated on: {{{datasheet_date|2024-03-15}}})</small>
 
|
 
|[[File:pdf_icon.png|32px|]]
 
|[[Media:EYE BEACON ATEX Datasheet-1.0.pdf|Eye Beacon ATEX Datasheet]]
 
|<small>(Updated on: {{{datasheet_date|2024-05-29}}})</small>
 
|
 
|[[File:pdf_icon.png|32px|]]
 
|[[Media:QM-BTSMP1.pdf|BTSID1 Quick Manual (EN)]]
 
|<small>(Updated on: {{{datasheet_date|2024-01-17}}})</small>
 
|}
 
 
 
==Additional information==
 
 
 
{{{EOL|For EOL policy please refer to link [https://teltonika-gps.com/support/eol-products here].}}}
 
 
 
[[Category:Sensors]]
 

Revision as of 08:55, 21 October 2021

Main Page > Sensors > EYE BEACON / BTSID1

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 beacon model from Teltonika with robust waterproof casing and a long-lifetime battery. The model designed for a low-cost fast and easy configuration and integration to save precious time, resources, and ensure accountability.

EYE device.png

About BTSID1

Perfect for traceability use cases, delivery tracking, monitoring of various movable objects in logistics (trailers, containers), agriculture (tractor attachments), and constructions (tools and inventory). Also, it suitable for indoor tracking solutions for items tracking in warehouses, hospitals, transport hubs and other types of industrial areas. EYE beacon 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

Functionalities
Beacon ID, LED
Dimensions and weight
Dimensions 56,6 mm x 38 mm x 13 mm
Weight 19 g 18g
Battery and power (not confirmed)
Model CR2450
Type Type Lithium, Manganese Dioxide
Total Capacity 620 mAh
Replaceable No
Battery life (Tx=2 dBm; interval: 3 s) 5+ years

(Tx=2 dBm; interval: 3 s)

Battery life (Tx=2 dBm; interval: 10 s) 10+ years

(Tx=2 dBm; interval: 10s)

Electronic
Microcontroller ST Microelectronics BlueNRG-2
Connectivity
Bluetooth Bluetooth 4.2 compliant,

Bluetooth 5.2 certified

Range 80 m
Available transmission power levels Up to 8 dBm
Sensitivity -88 dBm
Casing
Protection IP67
Mounting Two holes to screw/leash/strip, tape
Customization Custom logo upon request (Special conditions)
Environmental Requirements
Operational temperature -20 °C / +60 °C (-4 °F / +140 °F)
Protocols compatibility
iBeacon Yes

*iOS doesn't show devices with iBeacon protocol

Eddystone Yes
Certificates
CE (EU) Yes
FCC (USA) Yes
UKCA (UK) Yes
RoHS Yes
E-mark Yes

Dimensions

Eye dimensions.png

Mounting recomendations

Mounting recomendations.jpg
Mounting recomendations 1.jpg

EYE Accessory 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 3 second intervals.
• Eddystone 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.
QR.jpg

Eye app

With the application you will be able to scan for visible Teltonika EYE devices, check their statuses or connect for configuration or firmware update.

Detailed list - collapsed(2).jpg
Overview - without update (beacon)(2).png
Basic settings(2).png
Advance settings 4.png


Devices in view: In this window you will see all visible devices. You have options to see devices in Short list Shortlist.jpg or in default list. When looking at devices in default list you will be able to open Detailed view Detailed.jpg of devices and check transmitted data statuses. Additionaly if you are looking for specific devices you will be able to use Search Search button eye app.jpg function to filter search options. When in this window select a device of your choice to connect and after passing pin code you will go to device overview window.

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.

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 transmition type*. For more settings go to Advanced settings tab to enable various events.

Advanced configuration window: 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

IBeacon ID settings.png

Eddystone ID settings.png

*iOS doesn't show devices with iBeacon protocol

FM Tracker Configuration

Teltonika configurator

If you have firmware / configurator which does not support EYE Beacon tab in Bluetooth 4.0 section, then you can use Beacon list section of the configurator to scan available EYE Beacons.
Below are short instructions which show how we recommend configuring the device to Enable the Beacon functionality for testing.

Steps to follow according to the visual representation

  1. In System Settings Enable Codec8 Extended;
  2. In Bluetooth settings Enable Bluetooth, set this setting as either "Enable (hidden)" or "Enable (visible)", otherwise Bluetooth will be disabled;
  3. In 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;
  4. In Beacon list settings, configure Beacon Detection as "All" and Beacon Record as "Eventual". This will detect all surrounding Beacons and create Beacon records every 30 seconds.

Beacon project V3.gif


Teltonika configurator new functionalities (unreleased)

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.
  • Beacon - Parameters to enable Beacon scanning scenarios.


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.


Configurator GUI changes.png

Beacons
Beacons configuration instruction: How to start with FMB devices and Beacons?

EYE Beacons configurator.png

Beacon detection - Parameter controls over all Beacons scanning:

Beacon detection configurator.png
  • Disabled – Beacon scanning and transmitting disabled.
  • All – Read all visible beacons;
  • Configured – Read only beacons set in Beacon List;
  • Teltonika MAC – Filter and transmit only Teltonika EYE packets*.
    *It allows to filter only MAC addresses which will be assigned to BTSX device. The MAC address that is currently filtered by this parameter is FD:5F:9A:XX:XX:XX.



Beacon record

Beacon record on change.png

Eventual settings have two modes:

  • Monitoring - Beacon record generating every scan period
  • On change - Beacon records are generated only when there are changes in scanned list.

Periodic - records are generated according to Period settings. When there is no visible beacons, empty record will be generated.

Beacon Mode

Beacon Mode SImple.png
  • Simple - beacon parsing is done automatically (Eddystone and iBeacon protocols are supported).
  • Advanced - beacon data capturing can be configured.



Filter type

Filter Type.png

New firmware has two Beacon lists, so it is possible to create two separate lists of beacons, standard one with Beacons ID (UUID:Major:Minor, or Namespace:InstanceID) and new one according Beacon Name (by name or prefix, for example all beacons with prefix "ID1" can be saved.

  • Beacon ID - configurator allows to configure beacon id in iBeacon or Eddystone format.
  • Beacon Name - user can enter names of beacons which needs to be filtered. It would filter the full name or only if the prefix of the name is configured like “BTS”.


Both ID and Name filters can work at the same time. If beacon doesn’t match ID filter, but matches the name, it will be added to beacon list. Filtering only works Beacon Mode is set to Simple.

Proximity

Proximity.png


Proximity Events allow to configure 3 different zones: Near, Away, Far Away. There is additional Lost parameter for beacons which were lost from any of the 3 zones. Averaging timeout determines period how often results are evaluated to avoid fake event detection. Periodic option will generate records at known interval while On Change option will generate record when beacon enters/exits certain zone.

Proximity IO elements have the following structure 1st beacon protocol version.png

Protocol overwiev

Beacon advertising


Beacon advertising.png


FM packet parsing example

AVL Data Packet
AVL Data Packet Part HEX Code Part
Zero Bytes 00 00 00 00
Data Field Length 00 00 00 40
Codec ID 8E (Codec8 Extended)
Number of Data 1 (Number of Total Records) 01
AVL Data Timestamp 00 00 01 70 1F 9B 3F A9 (GMT: Friday, 07 February 2020 12:23:53.001)
Priority 01
Longitude 0F 0E 50 2A
Latitude 20 9A B4 61
Altitude 00 74
Angle 00 C6
Satellites 0E
Speed 00 00
Event IO ID 01 81 (385)
N of Total ID 00 01
N1 of One Byte IO 00 00
N2 of Two Bytes IO 00 00
N4 of Four Bytes IO 00 00
N8 of Eight Bytes IO 00 00
NX of X Bytes IO 00 01
N’th IO ID - AVL ID. 01 81 (385)
Length of Variable Length IO 00 13
Value of Variable Length IO 1101E39B606AA38255AA8E460B154E2D0055CF
Number of Data 2 (Number of Total Records) 01
CRC-16 00 00 00 56

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.
Safety.jpg

External Links

https://teltonika-gps.com/eye/