Difference between revisions of "Wialon and EYE proximity"
From Wiki Knowledge Base | Teltonika GPS
Thiagojuca (talk | contribs) m |
Thiagojuca (talk | contribs) m |
||
| Line 3: | Line 3: | ||
Following sections describe '''Proximity''' and '''Lost & Found''' Scenarios. | Following sections describe '''Proximity''' and '''Lost & Found''' Scenarios. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Configuration == | == Configuration == | ||
| Line 14: | Line 9: | ||
We need to set up proper Protocol and Bluetooth settings in order to have beacons information | We need to set up proper Protocol and Bluetooth settings in order to have beacons information | ||
| − | # In System Settings Enable Codec | + | # In System Settings Enable [[Codec#Codec%208%20Extended|Codec8 Extended]]; |
| − | # In | + | # In [[FMB120 Bluetooth® settings|Bluetooth®]] settings Enable Bluetooth®, set this setting as either "Enable (hidden)" or "Enable (visible)", otherwise Bluetooth® will be disabled; |
=== Proximity Scenario === | === Proximity Scenario === | ||
| − | [[File: | + | [[File:Eye_Beacon_Proximity_Events.png|alt=|right|frameless]] |
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. | 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. | ||
| − | |||
Proximity events consist of near, away and lost events: | Proximity events consist of near, away and lost events: | ||
| Line 26: | Line 20: | ||
* 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 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. | * 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. | ||
| + | '''Event modes''' | ||
| + | |||
| + | * 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''' | ||
| + | |||
| + | 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 Scenario === | ||
| + | [[File:Lost & found.png|right|frameless]] | ||
| + | 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). | ||
| + | |||
| + | Lost and Found Beacon records only include EYE Beacon which was lost or found, not the full Beacon 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, 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. | ||
| + | |||
| + | 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) | ||
Revision as of 15:27, 19 January 2024
Introduction
Teltonika Eye Beacons have two new scenarios related to RSSI value. RSSI means “Received Signal Strength Indicator” and this value can be use as distance indicator, or to know if the Beacon is detected by the FM tracker.
Following sections describe Proximity and Lost & Found Scenarios.
Configuration
Common Settings
We need to set up proper Protocol and Bluetooth settings in order to have beacons information
- In System Settings Enable Codec8 Extended;
- In Bluetooth® settings Enable Bluetooth®, set this setting as either "Enable (hidden)" or "Enable (visible)", otherwise Bluetooth® will be disabled;
Proximity Scenario
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. Proximity events consist of near, away and lost events:
- 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.
Event modes
- 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
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 Scenario
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).
Lost and Found Beacon records only include EYE Beacon which was lost or found, not the full Beacon 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, 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.
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)
