EYE FAQ: Difference between revisions
No edit summary Tag: Manual revert |
|||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 12: | Line 12: | ||
|EYE Sensor / BTSMP1 | |EYE Sensor / BTSMP1 | ||
|- | |- | ||
|2 | |2 years | ||
(Tx=2 dBm; interval: 1 s) | (Tx=2 dBm; interval: 1 s) | ||
|1 | |1 year | ||
(Tx=2 dBm; interval: 1 s) | (Tx=2 dBm; interval: 1 s) | ||
|- | |- | ||
|5 | |5 years | ||
(Tx=2 dBm; interval: 3 s) | (Tx=2 dBm; interval: 3 s) | ||
|2.5 | |2.5 years | ||
(Tx=2 dBm; interval: 3 s) | (Tx=2 dBm; interval: 3 s) | ||
|- | |- | ||
|8 | |8 years | ||
(Tx=2 dBm; interval: 5 s) | (Tx=2 dBm; interval: 5 s) | ||
|4 | |4 years | ||
(Tx=2 dBm; interval: 5 s) | (Tx=2 dBm; interval: 5 s) | ||
|- | |- | ||
|10 | |10 years | ||
(Tx=2 dBm; interval: 10s) | (Tx=2 dBm; interval: 10s) | ||
|5 | |5 years | ||
(Tx=2 dBm; interval: 10s) | (Tx=2 dBm; interval: 10s) | ||
| Line 98: | Line 98: | ||
Generally EYE Beacons are following format: | Generally EYE Beacons are following format: | ||
BTSID1 7CD9F4000001-7CD9F40FFFFF | BTSID1 7CD9F4000001-7CD9F40FFFFF | ||
BTSMP1 7CD9F4100000-7CD9F41FFFFF | BTSMP1 7CD9F4100000-7CD9F41FFFFF | ||
==== Does the app display the beacon's distance based on one or several signals it has received? ==== | |||
The app calculates distance based on the latest signal received from the beacon, not a fixed number of signals. | |||
The beacon broadcasts at a fixed interval (e.g., once per second). | |||
The app listens and updates when it receives a broadcast. | |||
If the signal is missed due to interference or power-saving logic (especially on mobile devices), the app may skip updates for one or more intervals. | |||
In short: beacon broadcasts regularly, but the app updates only when it receives those broadcasts so timing isn’t guaranteed to be exact every second. | |||
==== Does the application "refresh" every couple of seconds, or every second if the beacon is set to send signals in second mode, only to "miss" once it has been caught? ==== | |||
In broadcast mode (e.g., iBeacon): the phone listens passively. Updates are based on scan results, not on any active connection. | |||
In connection mode: the app establishes a BLE connection and requests data update actively. | |||
==== Does scanning depend whether the app is running in the background or in the foreground? ==== | |||
iOS: Scanning in the background is heavily limited. Only iBeacon-based region monitoring works reliably, and detailed data (like distance or scan response) is not available in the background. | |||
Android: Background scanning is allowed, but with reduced frequency unless a foreground service is used. Full access to signal data is possible, but may be delayed due to battery optimizations. | |||
===<big>Questions about FMBxxx compatibility with EYE Accessories</big>=== | ===<big>Questions about FMBxxx compatibility with EYE Accessories</big>=== | ||
| Line 139: | Line 157: | ||
The TX power value - value of processors power output to antenna. | The TX power value - value of processors power output to antenna. | ||
RFU - reserved for future use as per BLE specification, always 0x0000. | |||
Calibrated Power - power of the BLE device, measured in dBm (decibels relative to 1 milliwatt), at a reference distance. Currently Teltonika is providing beacons with pre-calibrated RSSI at 1m for iBeacon and RSSI at 0m for Eddystone that should be suitable for most use cases, however we plan to introduce user calibration in the future. | |||
=== <big>EN12830 modification related questions</big> === | === <big>EN12830 modification related questions</big> === | ||
| Line 155: | Line 171: | ||
==== Can you re-calibrate the sensors? ==== | ==== Can you re-calibrate the sensors? ==== | ||
Yes, recalibration is possible. | Yes, recalibration is possible. | ||
==== Are individual calibration certificates available? ==== | |||
Yes, see examples attached. | |||
[[File:Calib certificate example 1.png|frameless]][[File:Calib certificate example 2.png|frameless]][[File:Calib certificate example 3.png|frameless]] | |||
==== Do you need to recalibrate the sensors? ==== | ==== Do you need to recalibrate the sensors? ==== | ||
Recalibration is not mandatory under | Recalibration is not mandatory under EN 12830. The frequency of verification is instead governed by EN 13486, which states that verification should align with the user’s needs and the manufacturer’s recommendations. | ||
If the temperature sensor is mounted on a vehicle that undergoes annual or periodic inspection at a test station (e.g., refrigerated trucks or trailers), EN 13486 recommends that the verification of the temperature measuring instrument shall(must) occur at the same time as the vehicle's scheduled inspection. | |||
Please note: Certain countries or regulatory environments may impose stricter requirements than EN 12830. In such cases, we encourage clients to submit their devices for periodic verification. Our sensors are designed to maintain accuracy and pass verification without the need for recalibration. | |||
==== Our recalibration guidelines: ==== | ==== Our recalibration guidelines: ==== | ||
The temperature sensor has a long-term drift of less than 0.01°C per year, meaning it should maintain its 0.5°C accuracy class throughout its expected service life. In other words, recalibration is not expected to be needed after purchase. | The temperature sensor has a long-term drift of less than 0.01°C per year, meaning it should maintain its 0.5°C accuracy class throughout its expected service life. In other words, recalibration is not expected to be needed after purchase. | ||
===<big>Troubleshooting / rules of thumb</big>=== | |||
==== Scanning vs. Advertising Interval ==== | |||
As a general rule: Scanning Interval = 3 × Advertising Interval | |||
The scanning interval of your BLE receiver (e.g. gateway, FM device) should be at least three times longer than the beacon's advertising interval. | |||
Examples: | |||
If the EYE Beacon is set to 1s advertising, use 3s scanning | |||
If advertising is 10s, set scanning to at least 30s | |||
==== Dealing with Range Issues in Trailers ==== | |||
In heavy or metallic environments (e.g. trailers), the expected reliable Bluetooth range is 10–15 meters for most devices, including ours. | |||
Recommended configuration: | |||
EYE Beacon/Sensor: Tx Power 8 dBm, Advertising Interval 3s – balanced for performance and battery life | |||
FM Device: Enable non-stop scanning the fastest updates and BT power to 7 so scan response request reaches the beacon. | |||
If issues persist: | |||
If configuration changes don't help: | |||
Take photos of the beacon mounting | |||
Check whether issues occur only after the trailer is loaded or are always present. | |||
Export configuration files and Bluetooth logs(custom filters required, consult with our engineers). | |||
==== Beacon mapping with large fleets ==== | |||
If you're mapping non-powered assets with EYE Beacons and assign GPS positions by scanning them with your FM fleet – great! This is a powerful and scalable scenario to expand your telematics offering. | |||
However, you might face two common challenges: | |||
1. Assets appear stuck in an old location after transportation | |||
2. Delayed location detachment – e.g., a beacon left at home may still appear to be "traveling" with the vehicle for a few minutes or kilometers. | |||
Solutions: | |||
Use Proximity or Lost & Found scenarios, combined with RSSI averaging: | |||
The can be found @ Teltonika Configurator->Beacon List->EYE Beacon settings | |||
'''Proximity Scenario:''' | |||
Configure the RSSI threshold for when the FM device should treat the beacon as near, away, or lost – no need to implement this logic on your platform. | |||
[[File:Proximity1.png|frameless]] | |||
'''Lost & Found Scenario:''' | |||
Configure the system to only report: All beacons (default),Newly found beacons, Newly lost beacons | |||
[[File:Lost and found.png|frameless]] | |||
'''RSSI averaging const:''' | |||
Configure to adjust how quickly FM should react to RSSI changes. The bigger the constant the slower the FM reacts to changes, you can think of it as how many measurements it needs for to calculate moving average and use it to leverage against threshold for zones or lost/found. | |||
[[File:RSSI averaging .png|frameless]] | |||
===<big>Other questions (Questions without category)</big>=== | ===<big>Other questions (Questions without category)</big>=== | ||
==== What is the purpose of LED on the devices? ==== | ==== What is the purpose of LED on the devices? ==== | ||
One user touched magnet to wake up device from hibernate mode it indicates visually that it is powered and woke up correctly. | |||
==== Can EYE sensors detect temperature less than -20°C? ==== | ==== Can EYE sensors detect temperature less than -20°C? ==== | ||