Line 1: |
Line 1: |
| __TOC__ | | __TOC__ |
− |
| |
| | | |
| ==Beacon Settings== | | ==Beacon Settings== |
− | <br>
| |
| This page is dedicated for explanation of Bluetooth settings and also Beacon parameters in [[Teltonika_Configurator_versions#For_FMB_series|'''FMB device configurator''']]. A more extensive guide can be found [[How to start with FMB devices and Beacons?|'''How to start with FMB devices and Beacons?''']].<br> | | This page is dedicated for explanation of Bluetooth settings and also Beacon parameters in [[Teltonika_Configurator_versions#For_FMB_series|'''FMB device configurator''']]. A more extensive guide can be found [[How to start with FMB devices and Beacons?|'''How to start with FMB devices and Beacons?''']].<br> |
| | | |
| '''Beacon Detection'''<br> | | '''Beacon Detection'''<br> |
− | | + | * '''''Disabled''''' – Functionality disabled.<br> |
− | 0 (Disabled) – Functionality disabled.<br>
| + | * '''''All''''' – All visible beacons are detected (Max. 100).<br> |
− | 1 (All) – All visible beacons are detected (Max. 100).<br>
| + | * '''''Configured''''' – Only beacons from the list are sent to server<br> |
− | 2 (Configured) – Only beacons from the list are sent to server<br>
| |
| | | |
| '''Beacon Record'''<br> | | '''Beacon Record'''<br> |
| + | * '''''Eventual''''' – Record is sent after scan procedure is completed. This parameter depends from the [[{{{model|FMB120}}} Bluetooth 4.0 settings|'''Bluetooth 4.0 Scan Settings'''.]]<br> |
| + | * '''''Periodic''''' – All beacons are sent to the server. (Record will be saved according to configured period).<br> |
| | | |
− | 0 (Eventual) – Record is sent after scan procedure is completed. This parameter depends from the [[FMB120 Bluetooth 4.0 settings|'''Bluetooth 4.0 Scan Settings'''.]]<br>
| + | '''Record Period''' - Beacon record saving period: |
− | 1 (Periodic) – All beacons are sent to server. (Record will be saved accordint to configured period).<br>
| + | * Record Period on Move & Record Period on Stop. Timers for record generation when the device is moving and staying at the place. |
− | | + | * Record Period on Move (Default value 60 seconds)<br> |
− | '''Record Period''' - Beacon record saving period<br> | + | * Record Period on Stop (Default value 60 seconds)<br> |
− | | |
− | Record Period on Move & Record Period on Stop. Timers for record generation when device is moving and staying at place. <br> | |
− | Record Period on Move (Default value 60 seconds)<br> | |
− | Record Period on Stop (Default value 60 seconds)<br> | |
| | | |
| [[Image:Beacon Settings.PNG|300px|none]] | | [[Image:Beacon Settings.PNG|300px|none]] |
Line 32: |
Line 27: |
| | | |
| ==Beacon List== | | ==Beacon List== |
− | <br>
| |
| List of authorized beacons. Eddystone and iBeacon protocols are supported*.<br> | | List of authorized beacons. Eddystone and iBeacon protocols are supported*.<br> |
| | | |
Line 38: |
Line 32: |
| <br> | | <br> |
| ''*''Beacon Ids can be entered the following way: Namspace:CompanyID, UUID:Major:Minor. Any of the ID parts | | ''*''Beacon Ids can be entered the following way: Namspace:CompanyID, UUID:Major:Minor. Any of the ID parts |
− | can be omitted ex., Namespace:. UUID::, UUID::Minotr, etc | + | can be omitted ex., Namespace:. UUID::, UUID::Minor, etc |
| | | |
| | | |
| There is also possible to select Beacons Detection as the Configured, in this case, the beacons will only be detected and send if they were added to the Beacons List. | | There is also possible to select Beacons Detection as the Configured, in this case, the beacons will only be detected and send if they were added to the Beacons List. |
| | | |
− | Example for the configured beacons detection in the List. | + | Example of the configured beacons detection in the List. |
| | | |
| | | |
− | Below there is provided the example of the List, while using the '''Beacons Detection source as Configured.''' The provided example is showing the configuration for the iBeacon and Eddy-stone. | + | Below there is provided the example of the List while using the '''Beacons Detection source as Configured.''' The provided example is showing the configuration for the iBeacon and Eddy-stone. |
| [[Image:Configured List.png|800px|none]] | | [[Image:Configured List.png|800px|none]] |
| | | |
− | The Beacons settings is configured as showed. The iBeacon or Eddystone is added to the list with the following structure: | + | The Beacons settings are configured as showed. The iBeacon or Eddystone is added to the list with the following structure: |
− | | + | * '''''iBeacon''''' – 20 Bytes (UUDI (16-bytes:major(2-bytes):minor (2-bytes)) |
− | iBeacon – 20 Bytes (UUDI (16-bytes:major(2-bytes):minor (2-bytes)) | + | * '''''Eddystone''''' – 16B (Namespace (10-bytes):Instance ID(6-bytes)) |
− | | |
− | Eddystone – 16B (Namespace (10-bytes):Instance ID(6-bytes)) | |
| | | |
− | There is possibility to detect the devices just by UUID or Namespace (see the 2 and 6 element in the list). | + | There is a possibility to detect the devices just by UUID or Namespace (see the 2 and 6 elements in the list). |
| | | |
− | Or by the Major/Minor for iBeacons and Namespace for Eddystone. (see the 3 and 7 element in the list).<br /> | + | Or by the Major/Minor for iBeacons and Namespace for Eddystone. (see the 3 and 7 elements in the list).<br /> |