Changes

<br>

<br>

<br>

<br>

[[File:EYE Beacons configurator.png]]

[[File:Beacon settings.png]]

<br>

<br>

<br>

<br>

'''Beacon detection''' - Parameter controls over all Beacons scanning: [[File:Beacon detection configurator.png|right|border]]

'''Beacon detection''' - Parameter controls over all Beacons scanning:  

* '''Disabled''' – Beacon scanning and transmitting disabled.

* '''Disabled''' – Beacon scanning and transmitting disabled.

* '''All''' – Read all visible beacons;

* '''All''' – Read all visible beacons;

* '''Configured''' – Read only beacons set in Beacon List;

* '''Configured''' – Read only beacons set in Beacon List;

* '''Teltonika MAC''' – Filter and transmit only Teltonika EYE packets*.

'''Beacon Mode'''  

    *It allows to filter only MAC addresses which will be assigned to BTSX device. The MAC address that is currently filtered by this parameter is 7C:D9:F4:0X:XX:XX.

* '''Simple''' - beacon parsing is done automatically (Eddystone and iBeacon protocols are supported).  

* '''Advanced''' - beacon data capturing can be configured.<br>

'''Beacon record'''  

'''Beacon record''' [[File:Beacon record on change.png|right|border]]

'''Eventual''' settings have two modes:

* '''Monitoring''' - Beacon record generating every scan period

* '''On change''' - Beacon records are generated only when there are changes in scanned list.

* '''On change''' - Beacon records are generated only when there are changes in scanned list.

'''Periodic''' - records are generated according to Period settings. When there is no visible beacons, empty record will be generated.

* '''Periodic''' - Beacon record generating according to the configured Record Period on Move and Record Period on Stop parameters.

*'''Beacon Record Priority''' - When set to '''None''' Records will not be generated. '''Low priority''' means the Module makes an additional record which will be sent according to configured send period. When '''High Priority''' is configured, the Beacon record will be sent immediately to the server as soon as it is generated.<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

<br>

New firmware has two Beacon lists, so it is possible to create two separate lists of beacons, standard one with Beacons ID (UUID:Major:Minor, or Namespace:InstanceID) and new one according Beacon Name (by name or prefix, for example all beacons with prefix "ID1" can be saved.

New firmware has two Beacon lists, so it is possible to create two separate lists of beacons, standard one with Beacons ID (UUID:Major:Minor, or Namespace:InstanceID) and new one according Beacon Name (by name or prefix, for example all beacons with prefix "ID1" can be saved.

<br>

<br>

* '''Beacon ID''' - configurator allows to configure beacon id in iBeacon or Eddystone format.

* '''Beacon ID''' - configurator allows to configure beacon id in iBeacon or Eddystone format.

* '''Beacon Name''' - user can enter names of beacons which needs to be filtered. It would filter the full name or only if the prefix of the name is configured like “BTS”.

* '''Beacon Name''' - user can enter names of beacons which needs to be filtered. It would filter the full name or only if the prefix of the name is configured like “BTS”.

Both ID and Name filters can work at the same time. If beacon doesn’t match ID filter, but matches the name, it will be added to beacon list. Filtering only works Beacon Mode is set to Simple.

Both ID and Name filters can work at the same time. If beacon doesn’t match ID filter, but matches the name, it will be added to beacon list. Filtering only works Beacon Mode is set to Simple.

<br>

<br>

<br>

<br>

'''Proximity''' [[File:Proximity.png|right|border]]

'''Eye feature mode: Proximity'''

<br>

 

'''Proximity Events''' allow to configure 3 different zones: Near, Away, Far Away. There is additional Lost parameter for beacons which were lost from any of the 3 zones. Averaging timeout determines period how often results are evaluated to avoid fake event detection. Periodic option will generate records at known interval while On Change option will generate record when beacon enters/exits certain zone.

 

<br>

EYE beacon Proximity events is a functionality which creates three different types of records, depending on the captured Beacons RSSI level. This functionality is only supported with Teltonika EYE beacons.<br> Proximity events consist of near, away and lost events: <br>

<br>

*When EYE beacon RSSI level is below the first configured threshold, the beacon will be added to Near Beacon Record '''(AVL ID: 10828)'''

*When EYE BEACON RSSI level is between the second and first configured threshold, beacon is added to Away Beacon record '''(AVL ID: 10829)'''

*When EYE Beacon RSSI level is lower than the second configured threshold, beacon is added to Lost Beacon record '''(AVL ID: 10831)'''. In the case of EYE Beacon disappearing from the environment and not being detected by the FM tracker anymore, the beacon will be added to Lost Beacon record and will be removed from Beacon list.

 

*Disabled – Record generating is disabled for the selected range

*On Change – Records will be generated as soon as the Eye Beacon number changes for the selected range.

 

'''Averaging Timeout''' <br>

This parameter specifies how long it will take current RSSI value to reach new RSSI value. For example, current EYE Beacon RSSI value is -40 dBm. FMB captures same EYE Beacon with RSSI value of -60 dBm. If averaging timeout is configured to be 10 seconds, it will take 10 seconds for RSSI value to reach -60 dBm from -40 dBm. Keep in mind that this is assuming perfect conditions and subsequent EYE Beacon RSSI

 

 

Lost & Found is a new EYE Beacon feature. Purpose of this functionality is to periodically create records with all EYE Beacon list and create on change records only when EYE Beacon is lost or found. On change records include only EYE Beacon which was lost or found, not full list. If multiple EYE Beacons were found or lost at the same time, multiple will be  included into the record. If Visible Beacon List is enabled, record period is configured by parameters Record Period on Move ID:256 and Record Period on Stop ID:257.

 

<br>  

<IN PROGRESS!!!!!!!!!!!!!>

'''Proximity IO''' elements have the following structure [[File:1st beacon protocol version.png|bottom|border]]

'''Proximity IO''' elements have the following structure [[File:1st beacon protocol version.png|bottom|border]]