View source for Configuring Blue Puck/Coin/Slim ID beacons


__TOC__
==Configuring Blue Puck/Coin/Slim BLE advertising Beacon==

<b>1.</b> Bluetooth® LE Blue Puck, Blue Coin and Blue Slim beacons are disabled by default. Configurations to these beacons are written through NFC. To do this download Device Manager Mobile by Ela from Google Play Store to your device, can be also downloaded to your Apple phone, tested with iPhone X model. <br>

<b>Note:</b> Device that is used for configuring Blue Puck/Coin BLE advertising sensors must support NFC read/write functionality.<br>

<b>2.</b> Follow these instructions to easily configure Blue Puck/Coin/Slim Bluetooth® LE advertising Beacon:<br>
* Enable Bluetooth® and NFC on your Android-powered device.
* Launch Device Manager Mobile on your device.
* Select Configuration.
* Place your device on top of Blue Puck/Coin/Slim BLE advertising Beacon to scan it.
* Click Enable to allow Blue Puck/Coin/Slim Beacon transmit advertising data.
* Place your device on top of Blue Puck/Coin/Slim BLE advertising Beacon again to scan the changes.<br>

[[Image:BLE_enable1.gif|1000px|frame|center]]<br>

* We recommend to set Power to 4 to get the best possible distance.
* Set TAG Format to iBeacon.
* Set BLE Emit Period to 1 seconds to get best possible sensor detection.
* Click Write button.
* Place your device on top of Blue Puck/Coin/Slim BLE advertising sensor to write configuration to it.
<br>

[[Image:BLE_tag_parameters.gif|1000px|frame|center]]<br>


* Any Beacon ID can be typed in, as long as it in hex format.
<b>Note:</b> Beacon UUID must have 32 values set.<br>

In the example below, Beacon UUID is <code>AAAAAAAAAAAAAAAAAABBCC526F6F6D31</code>
When converted from <b>HEX</b> to <b>DEC</b>, <code>526F6F6D31</code> means <b>Room1</b>, to make beacon identifying easier.<br>
Major: <code>5231</code> when converted from <b>HEX</b> to <b>DEC</b>, it means <b>R1</b><br>
Minor: <code>010A</code><br>

[[Image:UUIDconfigurations.gif|1000px|frame|center]]<br>

==Configuring device==
[[File:Alert.png|30px]] <b>Before Beacon configuration, visit how to set up your device for the very first data sending to the server:</b>
[[First_time_with_Teltonika_device#Setting_up_your_configuration_for_the_very_first_data_sending_to_the_server | Setting up your configuration for the very first data sending to the server]]

These are instructions on how to easily configure ELA Blue Puck/Coin/Slim Beacon ID with Teltonika Configurator on GH5200 device.<br>

<b>1.</b> First the device <b>Bluetooth® settings</b> need to be configured. These are the required steps:<br>
* Press Bluetooth® settings
* Turn on BT Radio by pressing Enable (hidden) or Enable (visible)

[[Image:BLE_enable.gif|1000px|frame|center]]<br>

<b>2.</b> Press <b>Beacon list</b> tab.<br>
* Select <code>All</code> or <code>Configured</code> (for seeing only preferred beacons) in Beacon Detection options.<br>
* If you have selected <code>Configured</code> to see preferred beacons, you must add beacons to the Beacons list.<br>
* Select <code>Periodic</code> option
* Set <b>Periodic settings</b> according to your needs.<br>
* After all these steps press Save to device to save the configuration.<br>

[[File:Alert.png|30px]] <b>To find out how to add beacons to the Beacons list, click on one of the devices:</b>
[[TST100 Beacon List|TST100]] | [[TFT100 Beacon List|TFT100]] | [[GH5200 Beacon List|GH5200]] | [[TMT250 Beacon List|TMT250]]
<br>

[[Image:Beaconlistall.gif|100px|frame|center]]<br>


<b>3.</b> Now you can see detected Beacons in <b>Status -> Beacons List</b><br>
<br>
[[Image:Beacons_list.png|100px|frame|center]]<br>

<b>4.</b> Example of the server view:<br>
<br>
[[Image:Serverview_beacon1.png|1000px|frame|center]]<br>
<br>
In the server view picture above, displayed: 
* The date when the packet arrived to the server
* Device IMEI number
* AVL ID 385 – Beacon AVL ID
* Beacon ID and RSSI <br>

Beacon 1 ID: <code>0102030405060708090A0B0C0D0E0F00020B010A</code><br>
Beacon 1 Major: <code>020B</code><br>
Beacon 1 Minor: <code>010A</code><br>
RSSI: <code>-60</code> <br>
<br>
Beacon 2 ID: <code>AAAAAAAAAAAAAAAAAABBCC526F6F6D31</code><br>
Beacon 2 Major: <code>5231</code><br>
Beacon 2 Minor: <code>010A</code><br>
RSSI: <code>-56</code>
<br>

==Configured iBeacon packet data structure==
<br>

<b>Example of configured data parsing which comes with <i>AVL ID 385</i> 
<br>
Two detected Beacons:</b>
{| class="wikitable"
| colspan="3" style="text-align:center; height: 4em;" |<span style="background:silver">11</span><span style="background:red">21</span><span style="background:lime">0102030405060708090A0B0C0D0E0F00</span><span style="background:DodgerBlue">020B</span><span style="background:gold">010A</span><span style="background:aqua">C4</span><span style="background:red">21</span><span style="background:lime">AAAAAAAAAAAAAAAAAABBCC526F6F6D31</span><span style="background:dodgerblue">5231</span><span style="background:gold">010A</span><span style="background:aqua">C8</span>
|-
| style="background: silver; width: 4em;" |
|Data Part<b><sup>1</sup></b>
|11
|-
| colspan="3" |First Beacon:
|-
| style="background:red;" |
|iBeacon with RSSI flag<b><sup>2</sup></b>
|21
|-
| style="background: lime;" |
|UUID (Beacon #1)
|0102030405060708090A0B0C0D0E0F00
|-
| style="background: dodgerblue;" |
|Major
|020B
|-
| style="background: gold;" |
|Minor
|010A
|-
| style="background: aqua;" |
|RSSI (Signal Strength: Signed 2's complement)
|C4 (-60)
|-
| colspan="3" |Second Beacon:
|-
| style="background:red;" |
|iBeacon with RSSI flag<b><sup>2</sup></b>
|21
|-
| style="background: lime;" |
|UUID (Beacon #2)
|AAAAAAAAAAAAAAAAAABBCC526F6F6D31
|-
| style="background: dodgerblue;" |
|Major
|5231
|-
| style="background: gold;" |
|Minor
|010A
|-
| style="background: aqua;" |
|RSSI (Signal Strength: Signed 2's complement)
|C8 (-56)
|}
<br>

<b><sup>1</sup></b> Data part <b>11</b> - 1 Record out of 1 Beacon record. First half byte specifies current record, second half specifies how many there are in total. For example: 23 - second record out of three records (that means the server can expect 1 more records with Event I/O ID 385). If the data does not fit in a single data transfer, they are separated. Data Part is used to determine if more data will be coming from the device. <b>Maximum value of the Data part is 33.</b>
<br>
<br>
<b><sup>2</sup></b> Flags:

{| class="wikitable"
| colspan="2" |Flags:
|-
|21
|iBeacon with RSSI
|-
|23
|iBeacon with RSSI, Battery Voltage
|-
|27
|iBeacon with RSSI, Battery Voltage, Temperature
|-
|01
|Eddystone with RSSI
|-
|03
|Eddystone with RSSI, Battery Voltage
|-
|07
|Eddystone with RSSI, Battery Voltage, Temperature
|}
<br>