Changes

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: ====

==== 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.

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 FMB device - it will be registered as well, just by different ID or MAC address. Also, in current situation if first beacon leaves the range of FMB 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 disappear from the FMB device.