Difference between revisions of "Template:Beacons List"
| Line 27: | Line 27: | ||
===Beacon List=== | ===Beacon List=== | ||
| − | List of authorized beacons | + | List of authorized beacons, Eddystone and iBeacon protocols are ''supported*.'' Example of the configured beacons detection in the List:<br> |
| − | [[ | + | [[Image:FixedBeaconsList.png|none]] |
| − | ''* | + | ''*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::Minor, etc | + | can be omitted ex., Namespace:. UUID::, UUID::Minor, etc'' |
The Beacons settings are 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: | + | * '''''iBeacon''''' – 20 Bytes (UUDI (16-bytes : Major(2-bytes) : Minor (2-bytes)) |
| − | * '''''Eddystone''''' – | + | * '''''Eddystone''''' – 16 Bytes (Namespace (10-bytes) : Instance ID(6-bytes)) |
There is a possibility to detect the devices just by UUID or Namespace (see the 2 and 6 elements 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). | ||
| Line 71: | Line 71: | ||
===Beacon List=== | ===Beacon List=== | ||
| − | List of authorized beacons | + | List of authorized beacons, Eddystone and iBeacon protocols are ''supported*.'' Example of the configured beacons detection in the List:<br> |
| − | [[ | + | [[Image:FixedBeaconsList.png|none]] |
| − | + | ''*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::Minor, etc | + | can be omitted ex., Namespace:. UUID::, UUID::Minor, etc'' |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
The Beacons settings are 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: | + | * '''''iBeacon''''' – 20 Bytes (UUDI (16-bytes : Major(2-bytes) : Minor (2-bytes)) |
| − | * '''''Eddystone''''' – | + | * '''''Eddystone''''' – 16 Bytes (Namespace (10-bytes) : Instance ID(6-bytes)) |
There is a possibility to detect the devices just by UUID or Namespace (see the 2 and 6 elements 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 elements 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/> |
| + | 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. | ||
| + | |||
===Beacon On Change=== | ===Beacon On Change=== | ||
Revision as of 14:22, 17 August 2021
Beacon Settings before FW ver. 3.27.07.00
This page is dedicated for explanation of Bluetooth settings and also Beacon parameters in FMB device configurator. A more extensive guide can be found How to start with FMB devices and Beacons?.
Beacon Detection
- Disabled – Functionality disabled.
- All – All visible beacons are detected.
- Configured – Only beacons from the list are sent to server
Beacon Record
- Eventual – Record is sent after scan procedure is completed. This parameter depends from the Bluetooth 4.0 Scan Settings.
- Periodic – All beacons are sent to the server. (Record will be saved according to configured period).
Record Period - Beacon record saving period:
- 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)
- 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.
Beacon List
List of authorized beacons, Eddystone and iBeacon protocols are supported*. Example of the configured beacons detection in the List:
*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::Minor, etc
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))
- Eddystone – 16 Bytes (Namespace (10-bytes) : Instance ID(6-bytes))
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 elements in the 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.
Beacon Settings after FW ver. 3.27.07.00
This page is dedicated for explanation of Bluetooth settings and also Beacon parameters in FMB device configurator. A more extensive guide can be found How to start with FMB devices and Beacons?.
Beacon Detection
- Disabled – Functionality disabled.
- All – All visible beacons are detected (Max. 50).
- Configured – Only beacons from the list are sent to server
Beacon Mode
- Simple – When simple mode is selected beacon parsing is done automatically (Eddystone and iBeacon protocols are supported).
- Advanced – When advanced beacon mode is selected, beacon data capturing can be configured manually.
Beacon Record
- On Change – On change mode - device will not create Beacon record after every scan procedure is completed unless scanned Beacon list will change.
- Periodic – All beacons are sent to the server. (Record will be saved according to configured period).
Beacon Record Priority - Beacon record saving period:
- None - No records will be generated
- Low - Beacon record will be generated and sent once link with the server is established
- High - Beacon record will be generated and sent immediately
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.
Beacon List
List of authorized beacons, Eddystone and iBeacon protocols are supported*. Example of the configured beacons detection in the List:
*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::Minor, etc
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))
- Eddystone – 16 Bytes (Namespace (10-bytes) : Instance ID(6-bytes))
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 elements in the 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.
Beacon On Change
New functionality Beacon On Change has been implemented from 03.27.04.Rev.01 firmware version. The purpose of it is to create Beacon records only when there are changes in Beacon List. The New configurable parameter Beacon On Change (Parameter ID: 143) has been added with two possible settings: Monitoring (0) and On Change (1). When monitoring is selected, Beacon record generating is working as usual. When On Change is selected, Beacon records are generated only when there are changes in the Beacon list.
Beacon On Change settings:
Example 1.
Non-Stop Scan is Disabled. Scan starts. Beacon is detected and added to the list. Scan ends and Beacon records are created.
- The second scan starts. The same Beacon is still present. Scan ends and the Beacon record is not created because the list has not changed.
- The third scan starts. The same Beacon is still present but disappeared during that scan. Scan ends and Beacon record is not created because it is still considered that this Beacon is valid thus Beacon List hasn’t updated.
- The fourth scan starts. The same Beacon is not present from the start of the scan. Scan ends and Beacon is removed from Beacon list. Record is created since Beacon List has changed.
Example 2.
Non-Stop Scan is Disabled. Scan starts. Beacon is detected and added to the list. Scan ends and Beacon records are created.
- The second scan starts. The same Beacon is still present but is lost during that scan. Scan ends and the Beacon record is not created because the list has not changed.
- The third scan starts. At the start of the scan, Beacon was not present but during that scanning period, it has been detected again. At the end of the scan, the Beacon record is not created since Beacon List has not changed.
Example 3.
Non-Stop Scan is Enabled. Beacon Timeout is set to 10s. Beacon is detected and added to the list. Beacon record is created immediately after it is detected. The scan continues and during that time Beacon is lost. After 10s if Beacon has not been detected anymore Beacon record will be created. If that Beacon reappears after the set Beacon Timeout (in this case 10s) period has passed for that particular Beacon, a new Beacon record will be created. If That Beacon reappears before set Beacon Timeout (in this case 10s) period has passed. Beacon record will not be created.
