Difference between revisions of "FMB120 Beacon List"
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | __TOC__ | |
| − | |||
| − | |||
| − | |||
| + | ==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 '''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]] | ||
| + | |||
| + | <br /> | ||
[[Category:FMB120 Configuration]] | [[Category:FMB120 Configuration]] | ||
Revision as of 11:08, 8 January 2020
Main Page > Advanced Trackers > FMB120 > FMB120 Configuration > FMB120 Beacon ListBeacon Settings
Beacon Detection
0 (Disabled) – Functionality disabled.
1 (All) – All visible beacons are detected (Max. 100).
2 (Configured) – Only beacons from the list are sent to server
Beacon Record
0 (Eventual) – Disabled. (Record is sent after scan procedure is completed). This parameter depends from the Bluetooth 4.0 Scan Settings.
1 (Periodic) – All beacons are sent to server. (Record will be saved accordint to configured period).
Record Period - Beacon record saving period
Record Period on Move & Record Period on Stop. Timers for record generation when device is moving and staying at place.
Record Period on Move (Default value 60 seconds)
Record Period on Stop (Default value 60 seconds)
While selecting the Beacons Detection as All, the device will detect all beacons which are located around the device.
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.
The Beacons which was found will be shown in the Configurator and send as the AVL ID 314 record data.
Beacon List
List of authorized beacons. Eddystone and iBeacon protocols are supported*.
*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.
