Changes

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

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