| Line 1: |
Line 1: |
| − | __TOC__
| + | {{ |
| | + | Template:FMB Blue-tooth 4.0 settings |
| | + | |model=FMB120 |
| | + | }} |
| | | | |
| − | ==Beacon Settings==
| |
| − | <br>
| |
| − | '''Beacon Detection'''
| |
| − | <br>
| |
| − | 0 (Disabled) – Functionality disabled.<br>
| |
| − | 1 (All) – All visible beacons are detected (Max. 100).<br>
| |
| − | 2 (Configured) – Only beacons from the list are sent to server<br>
| |
| − |
| |
| − | '''Beacon Record'''<br>
| |
| − |
| |
| − | 0 (Eventual) – Disabled. (Record is sent after scan procedure is completed). This parameter depends from the [[FMB120 Bluetooth 4.0 settings|'''Bluetooth 4.0 Scan Settings'''.]]<br>
| |
| − | 1 (Periodic) – All beacons are sent to server. (Record will be saved accordint to configured period).<br>
| |
| − |
| |
| − | '''Record Period''' - Beacon record saving period<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]]
| |
| − |
| |
| − | While selecting the '''Beacons Detection''' as '''All''', the device will detect all beacons which are located around the device.
| |
| − | [[Image:All.png|300px|none]]
| |
| − |
| |
| − | 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.
| |
| − | [[Image:Configured.png|300px|none]]
| |
| − |
| |
| − | The Beacons which was found will be shown in the Configurator and send as the '''AVL ID 314''' record data.
| |
| − | [[Image:Beacons.png|1000px|none]]
| |
| − |
| |
| − | ==Beacon List==
| |
| − | <br>
| |
| − | List of authorized beacons. Eddystone and iBeacon protocols are supported*.<br>
| |
| − |
| |
| − | [[File:Beacon List.PNG|Beacon List]]
| |
| − | <br>
| |
| − | ''*''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
| |
| − |
| |
| − |
| |
| − | 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.
| |
| − |
| |
| − |
| |
| − | 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]]
| |
| − |
| |
| − | The Beacons settings is 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))
| |
| − |
| |
| − | 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).
| |
| − |
| |
| − | Or by the Major/Minor for iBeacons and Namespace for Eddystone. (see the 3 and 7 element in the list).<br />
| |
| | [[Category:FMB120 Configuration]] | | [[Category:FMB120 Configuration]] |
