Difference between revisions of "EYE BEACON / BTSID1"

From Wiki Knowledge Base | Teltonika GPS
(Created page)
 
(143 intermediate revisions by 9 users not shown)
Line 1: Line 1:
−
New page
+
__TOC__
 +
 
 +
==<p style="font-size:32px><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
 +
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.
 +
[[File:EYE device.png|center|frameless|1157x1157px]]
 +
 
 +
==<p style="font-size:32px><span style="color:#0054A6">About BTSID1</span></p>==
 +
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.
 +
==<p style="font-size:32px><span style="color:#0054A6">Product Specification</span></p>==
 +
===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
 +
|}
 +
{| 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 19 g
 +
| 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 (not confirmed)
 +
! 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;" |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: 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;" |10+ years
 +
|}
 +
{| class="wikitable"
 +
|+
 +
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Electronic
 +
! 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;" |Microcontroller
 +
| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |ST Microelectronics BlueNRG-2
 +
|}
 +
{| 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;" |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
 +
|}
 +
 
 +
===Dimensions===
 +
[[File:Eye dimensions.png]]
 +
 
 +
==<p style="font-size:32px><span style="color:#0054A6">Mounting recomendations</span></p>==
 +
[[File:Neweyemouning.png]]
 +
<br>
 +
[[File:New mounting recomendations 1.png]]
 +
 
 +
==<p style="font-size:32px><span style="color:#0054A6">EYE App Configuration</span></p>==
 +
 
 +
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>• Data advertising at 3 second intervals.
 +
<br>• Eddystone protocol
 +
<br>
 +
<br> If you would like to change these settings you will need to:
 +
<br>1) Download and install EYE APP - Teltonika application to change sensor settings.
 +
<br>[[File:QR.jpg]]
 +
<br>
 +
 
 +
===<p style="font-size:24px><span style="color:#0054A6">Eye App Overview</span>===
 +
'''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"
 +
|
 +
|[[File:Detailed list - collapsed(2).jpg|border|360x640px|none]]
 +
|
 +
|[[File:Overview - without update (beacon)(2).png|border|360x640px|none]]
 +
|
 +
|[[File:Basic settings(2).png|right|border|360x640px]]
 +
|
 +
|[[File:Advance settings 4.png|right|border|360x640px]]
 +
|}
 +
 
 +
<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>
 +
<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>
 +
[[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 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
 +
 
 +
{|
 +
|- align="TOP"
 +
|
 +
[[File:IBeacon ID settings.png|frameless]]
 +
|
 +
|[[File:Eddystone ID settings.png|frameless]]
 +
|}
 +
'''*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:24px"><span style="color:#0054A6">Teltonika configurator (standard functionality)</span>===
 +
 
 +
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>
 +
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'''
 +
 
 +
#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_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.
 +
 
 +
[[Image:Beacon_project_V3.gif]]
 +
 
 +
===<p style="font-size:24px"><span style="color:#0054A6">Teltonika configurator new functionalities (not released yet)</span>===
 +
 
 +
'''Bluetooth 4.0'''
 +
<br>
 +
Functionalities were reorganized and transferred to Bluetooth 4.0 configuration tab with additional horizontal tabs selection for specific settings:
 +
<br>
 +
* '''Global''' - Parameters responsible for device scanning ability like power and duratations.
 +
* '''Beacon''' - Parameters to enable Beacon scanning scenarios.
 +
<br>
 +
'''Common settings'''
 +
<br>
 +
* '''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.
 +
<br>
 +
[[File:Configurator GUI changes.png]]
 +
<br>
 +
<br>
 +
'''Beacons'''
 +
<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?]
 +
<br>
 +
<br>
 +
[[File:EYE Beacons configurator.png]]
 +
<br>
 +
<br>
 +
'''Beacon detection''' - Parameter controls over all Beacons scanning: [[File:Beacon detection configurator.png|right|border]]
 +
* '''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 7C:D9:F4:0X:XX:XX.
 +
<br>
 +
<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.
 +
'''Periodic''' - records are generated according to Period settings. When there is no visible beacons, empty record will be generated.
 +
<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>
 +
'''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>
 +
* '''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”.
 +
<br>
 +
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>
 +
'''Proximity'''  [[File:Proximity.png|right|border]]
 +
<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>
 +
'''Proximity IO''' elements have the following structure [[File:1st beacon protocol version.png|bottom|border]]
 +
 
 +
==<p style="font-size:32px><span style="color:#0054A6">EYE Beacon Protocol overview</span></p>==
 +
 
 +
===Beacon advertising===
 +
<br>
 +
[[image:Beacon and sensors data.png|center|819x819px|alt=|frameless]]
 +
<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>
 +
<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:
 +
<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'''
 +
 
 +
 
 +
 
 +
'''Note:''' only bolded bits (6 and 7) can have value 1, on BTSID1
 +
|-
 +
|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>
 +
 
 +
===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||00002a07-0000-1000-8000-00805f9b34fb||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 - Eddsytone + 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
 +
|-
 +
|Password||e61c0000-7df2-4d4e-8e6d-c611745b92e9||e61c0008-7df2-4d4e-8e6d-c611745b92e9||BYTE ARRAY||4 bytes||4 bytes||123456||Always 6 Digits
 +
|-
 +
|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:GATT_Beacon.png|800px|frameless|center]]
 +
 
 +
 
 +
===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 (UUDI, major, minor)
 +
 
 +
Eddystone – 16B (Namespace, Instance ID)
 +
|Signed 2's complement
 +
|
 +
|
 +
|
 +
|}
 +
 
 +
==== Eddystone example with 1 beacon ====
 +
{| 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 40
 +
|-
 +
| 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 70 1F 9B 3F A9 (GMT: Friday, 07 February 2020 12:23:53.001)
 +
|-
 +
| 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 50 2A
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Latitude
 +
| style="vertical-align: middle; text-align: center;" |20 9A B4 61
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Altitude
 +
| style="vertical-align: middle; text-align: center;" |00 74
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Angle
 +
| style="vertical-align: middle; text-align: center;" |00 C6
 +
|-
 +
| 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;" |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 13
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Value of Variable Length IO
 +
| style="vertical-align: middle; text-align: center;" |1101E39B606AA38255AA8E460B154E2D0055CF
 +
|-
 +
| 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 00 56
 +
|-
 +
|}
 +
 
 +
 
 +
{| 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
 +
|17F8A274D4FBDB62D33E1842F8DF8 – UUID
 +
 
 +
014D – Major
 +
 
 +
022B – Minor
 +
|  -65
 +
| 21A579723675064DC396A7C3520129F61900
 +
000000BF
 +
|-
 +
| -
 +
|21 –  iBeacon with RSSI
 +
|A579723675064DC396A7C3520129F619 – UUID
 +
0000 – Major
 +
 
 +
0000 – Minor
 +
| -65
 +
| -
 +
| -
 +
| -
 +
|}
 +
 
 +
==<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!
 +
 
 +
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.<br>
 +
[[File:Safety.jpg]]
 +
 
 +
==<p style="font-size:32px><span style="color:#0054A6">Certification & Approvals</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;" |
 +
|-
 +
| 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;" | [[BTS_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;" | [[BTS_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;" | [[BTS_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;" | [[BTS_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;" | [[BTS_REACH|YES]]
 +
|-
 +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Anatel(EU)
 +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTS_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;" | [[BTS_IP67|YES]]
 +
|}
 +
 
 +
==<p style="font-size:32px><span style="color:#0054A6">External Links</span></p>==
 +
 
 +
 
 +
 
 +
=== Product Page ===
 +
https://teltonika-gps.com/eye/
 +
 
 +
=== Product Change Notifications ===
 +
 
 +
The latest Product Change Notifications can be found: [[BTSID1_Product_Change_Notifications|Product Change Notifications]]
 +
 
 +
=== 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]] ===
 +
 
 +
*[[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 ===
 +
 
 +
==== [https://teltonika-gps.com/datasheet_eye_beacon.pdf Datasheet PDF] ====
 +
 
 +
==== [https://teltonika-gps.com/BTS_Quick_Manual.pdf Quick Manual PDF] ====
 +
[[Category:EYE Accessories]]

Revision as of 15:49, 1 September 2022

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 600 mAh
Replaceable No
Battery life (Tx=2 dBm; interval: 3 s) 4+ years
Battery life (Tx=2 dBm; interval: 5 s), default 8+ years
Battery life (Tx=2 dBm; interval: 10 s) 10+ years
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

Dimensions

Eye dimensions.png

Mounting recomendations

Neweyemouning.png
New mounting recomendations 1.png

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

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 (default pin code is 123456) 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 (standard functionality)

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 (not released yet)

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 7C:D9:F4:0X: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

EYE Beacon Protocol overview

Beacon advertising




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

Device Name has the following default value for Beacon – ID1_XXXXXXX

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


Note: only bolded bits (6 and 7) can have value 1, on BTSID1

Value 7 1 Battery Voltage


Battery voltage in mV = 2000 + VALUE * 10
NOTE: present only if bit 7 is set, otherwise is not being sent


GATT Characteristics

Name Service UUID Characteristic UUID Data Type Min Max Default Value Notes
Device Name e61c0000-7df2-4d4e-8e6d-c611745b92e9 e61c0016-7df2-4d4e-8e6d-c611745b92e9 ASCII 0 11 Unique for each device -
Tx Power Lever 1804 00002a07-0000-1000-8000-00805f9b34fb 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 - Eddsytone + 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

Password e61c0000-7df2-4d4e-8e6d-c611745b92e9 e61c0008-7df2-4d4e-8e6d-c611745b92e9 BYTE ARRAY 4 bytes 4 bytes 123456 Always 6 Digits
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
GATT Beacon.png


FM packet parsing example

Beacon (AVL ID:385) has the following structure:

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 (UUDI, major, minor)

Eddystone – 16B (Namespace, Instance ID)

Signed 2's complement

Eddystone example with 1 beacon

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


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

AVL Data Packet
AVL Data Packet Part HEX Code Part
Zero Bytes 00 00 00 00
Data Field Length 00 00 00 5A
Codec ID 8E (Codec8 Extended)
Number of Data 1 (Number of Total Records) 01
AVL Data Timestamp 00 00 01 6B 69 B0 C9 51(GMT: Tuesday, 18 June 2019 08:25:22.001)
Priority 00
Longitude 00 00 00 00
Latitude 00 00 00 00
Altitude 00 00
Angle 00 00
Satellites 00
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 2D
Value of Variable Length IO 11216B817F8A274D4FBDB62D33E1842F8DF8014D022BBF21A579723675064DC396A7C3520129F61900000000BF
Number of Data 2 (Number of Total Records) 01
CRC-16 00 00 3E 5D


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 17F8A274D4FBDB62D33E1842F8DF8 – UUID

014D – Major

022B – Minor

-65 21A579723675064DC396A7C3520129F61900

000000BF

- 21 – iBeacon with RSSI A579723675064DC396A7C3520129F619 – UUID

0000 – Major

0000 – Minor

-65 - - -

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

Certification & Approvals

Certificates
E-Mark (EU) YES
FCC (USA) YES
CE/RED (EU) YES
RoHS (EU) YES
REACH (EU) YES
Anatel(EU) YES
IP rating YES

External Links

Product Page

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

Product Change Notifications

The latest Product Change Notifications can be found: Product Change Notifications

Compatibilty with other Teltonika Devices

Teltonika Networks: https://wiki.teltonika-networks.com/view/Bluetooth_EYE_Sensor_and_EYE_Beacon_support

Partner Providers Supporting Software

Frequently asked questions

Documents

Datasheet PDF

Quick Manual PDF

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=EYE_BEACON_/_BTSID1&oldid=75639"