Line 1: |
Line 1: |
| __TOC__ | | __TOC__ |
− | ===Configuring Blue Puck/Coin/Slim Beacon===
| + | [[File:EYE device.png|center|frameless|800x800px|EYE Beacon BTSID]] |
− | [[Image:Screen beacon.png|right|frame]] | |
− | Bluetooth LE Blue Puck, Blue Coin and Blue Slim beacons are disabled by default. <br>Configurations to these beacons are written through NFC.<br>
| |
− | To do this download <b>[https://play.google.com/store/apps/details?id=com.ela.mobileapp.elamobileapp&hl=en_US| Device Manager Mobile]</b> by Ela from <i>Google Play Store</i> to your Android-powered device.<br>
| |
− | <b>Note!</b> Android-powered device that is used for configuring Blue Puck/Coin sensors must support NFC read/write functionality.<br><br>
| |
| | | |
− | Follow these instructions to easily configure Blue Puck/Coin/Slim Bluetooth LE Beacon:
| + | == 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. |
| | | |
− | *Enable <code>Bluetooth</code> and <code>NFC</code> on your Android-powered device.
| + | [[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. |
− | *Launch <b>Device Manager Mobile</b> on your Android-powered device.
| |
− | *Select <i>Configuration.</i>
| |
− | *Place your Android-powered device on top of Blue Puck/Coin/Slim Beacon to scan it.
| |
− | *Click <i>Enable</i> to allow Blue Puck/Coin/Slim Beacon transmit advertising data.
| |
− | *We recommend to set <i>Power</i> to 4 to get the best possible distance.
| |
− | *Set ''TAG Format'' to iBeacon.
| |
− | *Set ''BLE Emit Period'' to 1 second to get the best possible sensor detection.
| |
− | *Click <i>Write</i> button.
| |
− | *Place your Android-powered device on top of Blue Puck/Coin/Slim sensor to write configuration to it.
| |
| | | |
− | Once the configuration is written successfully, the Blue Puck/Coin/Slim Beacon will be enabled and use the settings configured in the APP.<br>
| |
− | <b>Note!</b> Make sure that <i>Manufacturer data mode</i> is Disabled, otherwise BLE Beacon will not be detected without additional changes in configuration.
| |
| | | |
− | ==Beacon Configuration and data sending== | + | Devices work constantly and are ready to perform out of the box. Default basic Sensor settings are set to: |
− | <br>
| + | |
− | ===Beacon configuration=== | + | • 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 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 31: |
Line 39: |
| [[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]]. |
| | | |
| | | |
Line 128: |
Line 136: |
| | 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 |
Line 141: |
Line 152: |
| | 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== |
Line 166: |
Line 177: |
| |- | | |- |
| ! 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 |
Line 180: |
Line 192: |
| | 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%;" |
| |+ | | |+ |