Template:Beacon List: Difference between revisions

← Older edit

VisualWikitext

Latest revision as of 10:41, 19 March 2026

Beacon Settings

Beacon Detection

Disabled – Functionality disabled.
All – Any visible beacon is detected (Max. 100).
Configured – Only data received from listed beacons in Beacon List is sent to server.

Beacon Record

Eventual – Record is sent after the scanning procedure is completed. This parameter depends on Update Frequency that is configured in Bluetooth 4.0
Periodic – Record will be saved based on configured time period.
- Record Period on Move - Timer for record generation when the device is moving.
- Record Period on Stop - Timer for record generation when the device is staying at the place.
No Send – Records will not be saved and sent. Could be used together with Beacon On Demand feature to avoid excess records of the beacons.

Beacon On Demand

Beacon On Demand functionality can be triggered, by a Mandown, No Movement, Alarm event, Button press or SMS/GPRS command, after a trigger, device start scanning for the Beacons and sending found beacon data to the server according to the configured Interval and determined Duration. For beacon detection can be chosen – All or Configured beacons. When this scenario is activated, BLE scan and send time depends on Interval parameter and is repeated before Duration time is expired, additionally feature can be turned off by SMS/GPRS command or if Beacon On Demand OFF button is pressed.

Example of use:

Set Beacon Detection settings All, then choose which event trigger is required or otherwise activate Beacon On Demand button functions in Keyboard section. Next step is to choose Interval, how often records have to be sent and Duration is how long interval will be repeating (ex. interval 30s and duration 300s, which should generate 10 records during this duration period of 300s). Beacon On Demand generates High Priority records, so a device will wake up when beacon on demand functionality is activated.

For commands control, after device receives SMS/GPRS command “beacon_on_demand#” where # is a number 0 or 1.

Possible # values are:
0 – Stops Beacon on Demand functionality.
1 – Starts Beacon on Demand functionality and Starts scanning for determined Duration.

NOTE! At Beacon Settings, parameter (ID 134) Beacon detection, must be chosen in order Beacon On Demand to work.

Beacon List

List of authorized beacons. Eddystone and iBeacon protocols are supported.
Beacon IDs can be entered the following way:

Namspace:InstanceID
UUID:Major:Minor

Any of the ID parts can be omitted. Ex. Namespace:, UUID::, UUID::Minor, etc.
Note! UUID, Namespace or Major/Minor for iBeacon and Namespace for Eddystone.

If Beacon Detection selected as Configured, then beacons will be detected and their data transmitted to the server only if their IDs are included in Beacon List.

If Non Stop Scan is enabled in Bluetooth 4.0 tab settings, then a Beacon Clear Timeout will appear under Beacon Settings.

BLE Devices Settings

BLE Devices Table can be used to read BLE packets coming from any device and deliver filtered data to the server as AVL ID: 585 record. The device according to the entered Manufacturer ID searches BLE devices that have the same advertised constant data part as entered in the configuration. Usually, Manufacturer ID is found after 5 bytes offset, but this filter allows to set any offset and size up to 8 bytes in size.
The Main Data parameter provides is used to determine and filter out only the desired part of the advertised data that will be sent to the server.
The Additional data parameter works the same as the Main Dara parameter, this way you can extract another data part from the packet.

Each filter/slot is independent. For example, each line in the table can be configured to take different or even the same information from the same beacon and we get separate data listing in the record according to the specific filter/slot number.

List of BLE devices settings:

Filter Switch - Enables/disables filter
Manufacturer ID - Match string in HEX. A constant value on the BLE device advertising frame.
Manufacturer ID Offset - determines from which byte the match string starts.
Manufacturer ID Size - determines match string size in bytes.
Main Data Offset - determines how many bytes offset.
Main Data Size - determines size in bytes.
Additional Data Offset - determines how many bytes offset.
Additional Data Size - determines size in bytes.

@@ Line 3: / Line 3: @@
 {|style="width: 100%;"
 ==Beacon Settings==
-|[[Image:Beacon_Settings{{{beacon_set|}}}.PNG|right]]
+{{#switch: {{{model}}}
+|TFT100 =
+[[Image:Beacon_Settings{{{beacon_set|}}}.PNG|right]]
+|#default =
+[[File:Beacon Settings TFT100.png|right]]
+}}
 ====Beacon Detection====
 * <code>Disabled</code> – Functionality disabled.<br>
@@ Line 10: / Line 17: @@
 ====Beacon Record====
-* <code>Eventual</code> – Record is sent after the scanning procedure is completed. This parameter depends on <span style=color:#F6A83E>Update Frequency</span> that is configured in [[{{{model|X}}} Bluetooth 4.0 settings | Bluetooth 4.0]]
+* <code>Eventual</code> – Record is sent after the scanning procedure is completed. This parameter depends on <span style=color:#F6A83E>Update Frequency</span> that is configured in [[{{{model|X}}} Bluetooth® 4.0 settings| Bluetooth 4.0]]
 * <code>Periodic</code> – Record will be saved based on configured time period.<br>
 **<code>Record Period on Move</code> - Timer for record generation when the device is moving.
@@ Line 50: / Line 57: @@
 <br>
 If <span style=color:#F6A83E>Beacon Detection</span> selected as <code>Configured</code>, then beacons will be detected and their data transmitted to the server only if their IDs are included in <span style=color:#F6A83E>Beacon List</span>.<br><br>
+If <span style=color:#F6A83E>Non Stop Scan</span> is enabled in '''Bluetooth 4.0 tab''' settings, then a <span style=color:#F6A83E>Beacon Clear Timeout</span> will appear under '''Beacon Settings'''.
+|}
+{{#switch: {{{model}}}
+|TFT100 =
+'''Beacon Clear Timeout''' - Time period in seconds in which beacons are “visible” to the device and if beacons are not detected repeatedly in these time periods, they are considered lost and deleted from visible beacons list. In case of periodic scan, visible list will be cleared after the scan if beacons were not found during the last scan.
 <b>iBeacon</b> and <b>Eddystone</b> data frame has the following structure:
 * <b>iBeacon</b> – 20 Bytes (UUID(16 Bytes):major(2 Bytes):minor(2 Bytes))
 * <b>Eddystone</b> – 16 Bytes (Namespace(10 Bytes):Instance ID(6 Bytes))<br>
-|}
+<b>Identifier</b> - There are two identifiers which can be packed into records:
+*ID - IBeacon or Eddystone specific data (UUID or Namespace/Instance ID respectively).
+*MAC - MAC address of Beacons.
+==EYE Beacon Settings==
+<br>
+<br>
+[[File:EYE Beacon Settings.png]]
+<br>
+*The 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>
+* '''Beacon ID''' - configurator allows to configure beacon ID in iBeacon or Eddystone format in Beacon List.
+* '''Beacon Name''' - The names of beacons which need to be filtered can be entered. Only the beginning part of the EYE Beacon local name has to match. For example, if in the EYE Beacon name list “EYE_Beacon” is added and the FM tracker detects EYE_Beacon1, EYE_Beacon2, EYE_BeaconXYZ, all these EYE Beacons will be added to EYE Beacon name list.
+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. However, Filtering only works Beacon Mode is set to Simple.
+<br>
+<br>  [[File:Eye Beacon Prox.png|right|border]]
+===Eye Feature Mode: Proximity===
+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>
+*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 above 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.
+'''Event modes''' <br>
+*Disabled – Record generating is disabled for the selected range
+*Periodic – Records will be periodically generated for the selected range, according to the configured record period on move or on stop value.
+*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
+===Eye Feature Mode: Lost & Found===
+<br>
+[[File:Lost & found.png]]
+'''Lost & Found  EYE Beacon Feature'''<br>
+Purpose of this functionality is to '''periodically''' generate records with all EYE Beacon list (AVL ID: 10828) and create eventual '''On Change''' records only when EYE Beacon is lost (AVL ID: 10831) or found (AVL ID: 10829). <br>
+Lost and Found Beacon records only include EYE Beacon which was lost or found, not the full Beacon list. <br>
+*If multiple EYE Beacons were found or lost at the same time, multiple will be  included into the record. <br>
+*If Visible Beacon List is enabled, Beacon records containing the list of visible beacons will be generated according to the configured period parameters ''Record Period on Move'' and ''Record Period on Stop''
+Advanced Beacon protocol is being used to send Lost & Found records.  <br>
+Note:Same AVL ID’s as for Proximity events are being used, since two features cannot work at the same time.
+*'''AVL ID: 10828''' Visible Beacon List (periodic)
+*'''AVL ID: 10829''' Found Beacon List (On Change)
+*'''AVL ID: 10831''' Lost Eye Beacon List (On Change)
+'''Proximity and Lost & found AVL ID''' elements have the following structure:<br> [[File:1st beacon protocol version.png|border]]
+When Proximity or Lost & Found events are sent, the records will always include Beacon RSSI, Beacon ID, low battery indicator and Battery Voltage.
+|#default =
+}}
 {|style="width: 100%;"