0
edits
Changes
Advanced Beacon Capturing Configuration (view source)
Revision as of 12:51, 17 December 2021
, 12:51, 17 December 2021no edit summary
==Beacon List Settings after FW ver. 3.27.07.Rev.00==
==Beacon List Settings after FW ver. 3.27.07.Rev.00==
This page is dedicated for explanation of Bluetooth settings and also Beacon parameters in [[Teltonika_Configurator_versions#For_FMB_series|'''FMB device configurator''']]. Prior to capturing specific Beacon data it is mandatory to have Beacons communication protocol - advertising packet structure. Without knowing packet structure - it is impossible to configure device properly to capture important data. A more extensive guide can be found [[How to start with FMB devices and Beacons?|'''How to start with FMB devices and Beacons?''']].
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?''']].
===Beacon Settings===
===Beacon Settings===
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.
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.
=== Idea of Beacon Capturing Configuration ===
=== Advanced Beacon Capturing Configuration ===
Prior to capturing specific Beacon data it is mandatory to have Beacons communication protocol - advertising packet structure. Without knowing packet structure - it is impossible to configure device properly to capture important data.
==== Idea of Beacon Capturing Configuration ====
Functionality allows to capture advertising packet of any kind of Beacon which broadcasts its information automatically. Beacon Capturing Configuration list also can be called as the set of rules to capture and transfer Beacon data. Advanced mode main purpose is to capture additional or only specific data (''by Manufacturers ID'') according to configured Offsets and Data sizes.
Functionality allows to capture advertising packet of any kind of Beacon which broadcasts its information automatically. Beacon Capturing Configuration list also can be called as the set of rules to capture and transfer Beacon data. Advanced mode main purpose is to capture additional or only specific data (''by Manufacturers ID'') according to configured Offsets and Data sizes.
=== Configurable parameters in Beacons Capturing Configuration table (Advanced Mode) ===
==== Configurable parameters in Beacons Capturing Configuration table (Advanced Mode) ====
[[File:BeaconMode.gif|right]]
[[File:BeaconMode.gif|right]]
In advanced mode device can detect any Beacon type, the device can be configured to capture data from Universal beacons as seen in the configured in table (The fields in the Beacons Capturing Configuration will be empty), for example this configuration is set to detect iBeacon and EddyStone Beacons, also with additional data(in this case whole packet).
In advanced mode device can detect any Beacon type, the device can be configured to capture data from Universal beacons as seen in the configured in table (The fields in the Beacons Capturing Configuration will be empty), for example this configuration is set to detect iBeacon and EddyStone Beacons, also with additional data(in this case whole packet).
When Advanced mode is selected - Beacon data arrives through AVL ID 548 (''Beacon list and Advanced list'' ''are not separated''). In Simple mode data arrives by AVL ID 385. Codec 8 Extended is mandatory for both Beacon capturing modes.
When Advanced mode is selected - Beacon data arrives through AVL ID 548 (''Beacon list and Advanced list'' ''are not separated''). In Simple mode data arrives by AVL ID 385. Codec 8 Extended is mandatory for both Beacon capturing modes.
==== Difference between On change and Periodic parameters when using Advanced Beacon Mode: ====
As it is known that Advanced Beacon mode is capturing Beacons by the Manufacturer ID - "On change" mode in some scenarios can be a better option than Periodic. For example in asset tracking scenario – beacons do not leave the range of FMB BLE scan, meaning that device will not constantly send visible beacons to the server but only will report if one beacon goes missing or new (same type) beacon occurs. This allows to save a lot of data and be sure when asset is gone and has returned back. More technical example while "On change" mode is active - device will capture the first seen beacon by e.g. "E1FFA108" ID and if second beacon with '''same''' manufacturer ID approaches FMB125 - it will be registered as well, just by different ID or MAC address. Also, in current situation if first beacon leaves the range of FMB125 but the second with same manufacturer ID stays in the range - device will make a report that one has left the area. Device strictly checks beacons by the manufacturer ID in the Advanced Beacon list. "Periodic" beacon mode would be constantly by configured parameters reporting to the server of visible beacons, regardless if they appear or dissapear from the FMB device.
''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.
''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.
===Parsing Advanced Beacon data from record (AVL ID 548)===
===Parsing Advanced Beacon data from record (AVL ID 548)===
