Line 8: |
Line 8: |
| * '''''Configured''''' – device will only capture beacons by given data in Beacon list and Advanced list if enabled. | | * '''''Configured''''' – device will only capture beacons by given data in Beacon list and Advanced list if enabled. |
| | | |
− | '''Beacon Mode'''<br> | + | '''Beacon Mode''' |
| * '''''Simple''''' – When simple mode is selected beacon parsing is done automatically (Eddystone and iBeacon protocols are supported) ('''AVL ID 385'''). | | * '''''Simple''''' – When simple mode is selected beacon parsing is done automatically (Eddystone and iBeacon protocols are supported) ('''AVL ID 385'''). |
− | * '''''Advanced''''' – When advanced beacon mode is selected, beacon data capturing can be configured manually ('''AVL ID 548''').<br> | + | * '''''Advanced''''' – When advanced beacon mode is selected, beacon data capturing can be configured manually ('''AVL ID 548'''). |
| | | |
− | '''Beacon Record'''<br> | + | '''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. | | * '''''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).<br> | + | * '''''Periodic''''' – All beacons are sent to the server. (Record will be saved according to configured period). |
| | | |
| '''Beacon Record Priority''' - Beacon record saving period: | | '''Beacon Record Priority''' - Beacon record saving period: |
Line 47: |
Line 47: |
| | | |
| 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. |
| + | |
| + | |
| + | ===Beacon List=== |
| + | List of authorized beacons, Eddystone and iBeacon protocols are ''supported*.'' Example of the configured beacons detection in the List:<br> |
| + | [[File:BeaconCongif.mp4|1750px]] |
| + | |
| + | ''*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).<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. |
| + | |
| + | From '''3.27.07.Rev.00''' Beacon list is expanded to support 50 beacons IDs. |
| | | |
| When Advanced Beacon mode is selected - Beacon list acquires new option too. No longer it is required to insert full UUID, major or minor. In advanced mode it is possible to mask / ignore specific parts of UUID or major, or minor. Symbol " * " is used for masking. This allows to write shorter or only partial UUIDs in the Beacon list. Note: it is not possible to use " * " symbol to mask Manufacturer ID in the Advanced list. | | When Advanced Beacon mode is selected - Beacon list acquires new option too. No longer it is required to insert full UUID, major or minor. In advanced mode it is possible to mask / ignore specific parts of UUID or major, or minor. Symbol " * " is used for masking. This allows to write shorter or only partial UUIDs in the Beacon list. Note: it is not possible to use " * " symbol to mask Manufacturer ID in the Advanced list. |
Line 214: |
Line 232: |
| |- | | |- |
| |} | | |} |
− |
| |
− |
| |
− | ===Beacon List===
| |
− | List of authorized beacons, Eddystone and iBeacon protocols are ''supported*.'' Example of the configured beacons detection in the List:<br>
| |
− | [[File:BeaconCongif.mp4|1750px]]
| |
− |
| |
− | ''*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).<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.
| |
− |
| |
− | From '''3.27.07.Rev.00''' Beacon list is expanded to support 50 beacons IDs.
| |
| | | |
| | | |