4,745
edits
Changes
How to start with FMB devices and Beacons? (view source)
Revision as of 16:29, 28 December 2023
, 16:29, 28 December 2023Text replacement - "Bluetooth(?!®)" to "Bluetooth®"
__TOC__
__TOC__
[[File:EYE device.png|center|frameless|800x800px|EYE Beacon BTSID]]
==Beacon Configuration and data sending==
== Eye Devices ready to use ==
The easiest way to get started with beacons is to use the Teltonika's Eye Devices. All you need to do is just unbox them.
===Beacon configuration===
[[EYE BEACON / BTSID1|Eye Beacons]] are designed to make your wireless experience effortless, there is not need to make adjustments configuration, the devices are pre-configured and ON from factory, this ensures rapid deployment.
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 5 second intervals.
• Eddystone(for EYE Beacon) Eddystone and Sensors(for EYE Sensor) protocol
[[File:BTSMP1 wiki.jpg|center|frameless|401x401px]]
You can find detailed information about how to configure those parameters below:
==Beacon Configuration and data sending==
=== EYE APP Overview ===
Eye sensors are ready to use from factory, however, you can change your beacon parameters according to your needs. Eye App is Teltonika dedicated application for Eye sensor/beacon configuration.
[[File:EYEAPPBTSID.png|center|thumb|1024x1024px]]
# Eye App first screen will show you available Eye Beacons/sensors reachable, press on you beacon to access next screen
# Eye App second screen shows ID information and Firmware information, press on the icon to access beacon parameters
# Eye App third screen allows you to change Beacon Name, TX power, Advertising interval, Packet settings.
===Beacon configuration (Setting your tracking device for Beacon usage)===
Below are short instructions which show how we recommend to configure 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.
[[Image:Beacon_project_V3.gif]]
[[Image:Beacon_project_V3.gif]]
====Steps to follow according to the visual represenation====
====Steps to follow according to the visual representation====
#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.
===Beacon data parsing===
===Beacon data parsing===
Shown how Beacon data is represented on [[Gurtam_Wialon_with_Fleet_Management_(FM)|Wialon platform]].
Shown how Beacon data is represented on [[Wialon_with_Fleet_Management_(FM)|Wialon platform]].
==Parsing of Beacon records==
==Parsing of Beacon records==
Beacon records are sent as seperate Records with Event I/O ID 385 and also include I/O element 385 (Codec8 Extended has to be used, because the I/O element 385 uses Variable size IO element).
Beacon records are sent as separate Records with Event I/O ID 385 and also include I/O element 385 (Codec8 Extended has to be used because the I/O element 385 uses Variable size IO element).
Received data in hexadecimal stream: <br>
Received data in hexadecimal stream: <br>
{| class="nd-othertables_2" style="width:100%;"
{| 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="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
|-
| style="vertical-align: middle; text-align: center;" |NX of X Bytes IO
| 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;" |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;" |Length of Variable Length IO
| style="vertical-align: middle; text-align: center;" |00 00 30 CB
| style="vertical-align: middle; text-align: center;" |00 00 30 CB
|-
|-
|}
|}
==Parsing Beacon data from record==
==Parsing Beacon data from record==
===Beacon Flags===
===Beacon Flags===
The below table represents possible Beacon flags. Supported Beacon protocols are iBeacon and Eddystone.
{| class="nd-othertables_2" style="width:25%;"
{| class="nd-othertables_2" style="width:25%;"
|+
|+
|-
|-
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |23
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |23
| style="vertical-align: middle; text-align: center;" |iBeacon with RSSI, Battery Voltage
| style="vertical-align: middle; text-align: center;" |iBeacon with RSSI,
Battery Voltage
|-
|-
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |27
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |27
| style="vertical-align: middle; text-align: center;" |Eddystone with RSSi, Battery Voltage, Temperature
| style="vertical-align: middle; text-align: center;" |Eddystone with RSSi, Battery Voltage, Temperature
|}
|}
NOTE! Standard iBeacon protocol does not support Battery voltage or temperature sending.
{| class="nd-othertables_2" style="width:100%;"
{| class="nd-othertables_2" style="width:100%;"
|+
|+
| rowspan="50" style="vertical-align: middle; text-align: center;" |
| rowspan="50" style="vertical-align: middle; text-align: center;" |
| style="vertical-align: middle; text-align: center;" |Data part<br> (First half byte – current data part, Second half byte – total number of data parts)
| style="vertical-align: middle; text-align: center;" |Data part<br> (First half byte – current data part, Second half byte – total number of data parts)
| style="vertical-align: middle; text-align: center;" |11
| style="vertical-align: middle; text-align: center;" |11
|-
|-
| style="vertical-align: middle; text-align: center;" |BLE Beacon RSSI #1
| style="vertical-align: middle; text-align: center;" |BLE Beacon RSSI #1
| style="vertical-align: middle; text-align: center;" |<span style="background:#87CEEB">BA</span> - Signed 2's Complement -70 dBm
| style="vertical-align: middle; text-align: center;" |<span style="background:#87CEEB">BA</span> - Signed 2's Complement -70 dBm
|-
|-
| style="vertical-align: middle; text-align: center;" |BLE beacon flags #2<br> 21 - iBeacon, RSSI is sent
| style="vertical-align: middle; text-align: center;" |BLE beacon flags #2<br> 21 - iBeacon, RSSI is sent
|-
|-
|}
|}
[[Category: Frequently Asked Questions - FAQ]]
