Changes

[[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).

 

* '''Name''' - particular parameter does not affect Beacon capturing at all. You can name particular beacon capturing line as you wish. Note that if "dot" symbol is placed prior to the name - whole line in the table is disabled and beacons will not be captured;

* '''Name''' - particular parameter does not affect Beacon capturing at all. You can name particular beacon capturing line as you wish. Note that if "dot" symbol is placed prior to the name - whole line in the table is disabled and beacons will not be captured;

* '''Manufacturer ID''' - most crucial and important part of the configuration. Device will look for provided ID and capture beacons if ID matches. Manufacturer ID consists of 4 Bytes (8bits) and it is required to write in the table full ID of 4 Bytes. Of course, in some cases Manufacturer ID of some Beacons may be shorter - in such case shorter ID can be configured but do not forget to add zeroes after the ID inside configuration – otherwise configuration will not be valid. Actually any numbers could be written because ID size in found Beacon advertising packet can be configured with further parameters;

* '''Manufacturer ID''' - most crucial and important part of the configuration. Device will look for provided ID and capture beacons if ID matches. Manufacturer ID consists of 4 Bytes (8bits) and it is required to write in the table full ID of 4 Bytes. Of course, in some cases Manufacturer ID of some Beacons may be shorter - in such case shorter ID can be configured but do not forget to add zeroes after the ID inside configuration – otherwise configuration will not be valid. Actually any numbers could be written because ID size in found Beacon advertising packet can be configured with further parameters;

* '''Additional Data Offset''' and '''Additional Data Size''' - allows to capture specific data of the Beacons advertised packet e.g. battery voltage or status. These additional parameters depend on Beacon type and advertisement packet. In order to capture full packet of the Beacon - Offset can be left at 0 and Size matched by actual length of the advertised packet.

* '''Additional Data Offset''' and '''Additional Data Size''' - allows to capture specific data of the Beacons advertised packet e.g. battery voltage or status. These additional parameters depend on Beacon type and advertisement packet. In order to capture full packet of the Beacon - Offset can be left at 0 and Size matched by actual length of the advertised packet.

* '''Beacon ID Source'''- Beacon ID source can be selected. When Beacon ID is used, source is used as configured in Beacon ID offset and Beacon ID size columns. When Beacon MAC address is selected, Beacon ID will be replaced with MAC address. IO structure remains the same, but Beacon ID size will always be reported as 0x06.

* '''Beacon ID Source'''- Beacon ID source can be selected. When Beacon ID is used, source is used as configured in Beacon ID offset and Beacon ID size columns. When Beacon MAC address is selected, Beacon ID will be replaced with MAC address. IO structure remains the same, but Beacon ID size will always be reported as 0x06.

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

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.