Line 5: |
Line 5: |
| | | |
| ==== How to turn ON the device / does the device need to be turned on? ==== | | ==== How to turn ON the device / does the device need to be turned on? ==== |
− | Devices are turned ON from the factory by default. | + | It depends on ordering code used. Devices can be turned ON from the factory or come in hibernate mode and will need to be turned on by placing a magnet on the device. |
| | | |
| ==== What is the battery life for different advertising intervals? ==== | | ==== What is the battery life for different advertising intervals? ==== |
Line 42: |
Line 42: |
| | | |
| ==== Can I disable not-used sensors to conserve the battery? ==== | | ==== Can I disable not-used sensors to conserve the battery? ==== |
− | You can only disable only data sending of all sensors the sensors by configuring device protocol to send as a beacon, the sensors will be still active. It's also not possible to disable only one or part of the sensors. | + | From firmware version 1.2.10.Rev.4 separate sensors can be disabled. These are movement, temperature, humidity and magnetic field. Disabling accelerometer sensor will improve battery lifetime. Disabling other sensors will disable advertising only without improving battery lifetime. |
− | However, there are options to create special order codes with assembly modifications with only one or selected sensors to be soldered and produced. | + | However, there are options to create special order codes with assembly modifications with only one or selected sensors to be soldered and produced. Such changes will only be considered for large quantity orders or high potential customers. |
− | If you don't want to receive particular sensor data, but have no need for saving battery life, you can can disable the related sensor IO element in Teltonika Configurator. EYE Sensor will be still sending data, but FM will filter it according to your choice. | + | If you do not want to receive particular sensor data, but have no need for saving battery life, you can disable the related sensor IO element in Teltonika Configurator. EYE Sensor will be still sending data, but FM will filter it according to your choice. |
| | | |
| ==== Is there any graph to estimate device lifespan with different advertising settings? ==== | | ==== Is there any graph to estimate device lifespan with different advertising settings? ==== |
Line 60: |
Line 60: |
| CR2450 Lithium, Manganese Dioxide(MnO2), Self-discharge 1% per 1 year | | CR2450 Lithium, Manganese Dioxide(MnO2), Self-discharge 1% per 1 year |
| ==== What is the direction of EYE Senor's or Beacon's antenna? ==== | | ==== What is the direction of EYE Senor's or Beacon's antenna? ==== |
− | BTS Beacon/Sensor antenna is identical and its signal strength is very similar in all directions. | + | BTS Beacon/Sensor antenna is unidirectional. Antenna signal strength is very similar in all directions. |
| | | |
| ==== What is the BLE transmission range of BTS devices? ==== | | ==== What is the BLE transmission range of BTS devices? ==== |
Line 78: |
Line 78: |
| | | |
| ==== Can you change configuration of EYE devices remotely? ==== | | ==== Can you change configuration of EYE devices remotely? ==== |
− | No, the devices only have bluetooth chip, so you have to be relatively close to the device to update configuration. No implementation of updating EYE devices via services other than EYE APP is planned in near future. | + | No, the devices only have bluetooth chip, so you have to be relatively close to the device to update configuration. If you are using a 3rd party or developing your own application/software, GATT characteristics can also be used to configure the device. |
| + | No implementation of updating EYE devices via services other than EYE APP or GATT characteristics is planned in the near future. |
| | | |
| ==== Can you update firmware or configuration on a few sensors at the time via the EYE app? ==== | | ==== Can you update firmware or configuration on a few sensors at the time via the EYE app? ==== |
Line 101: |
Line 102: |
| | | |
| ==== How many sensors can you use with FM device? ==== | | ==== How many sensors can you use with FM device? ==== |
− | At the moment 4 sensors (Base firmware / advance mode), this is expanded up to 100 in evaluation firmware release which includes new EYE features. It will be available with 03.29.XX base firmware. You do not need to configure the MAC address but instead enter the name(or part of name) of the sensor and all sensors with that name(or part of name) will be scanned in case there are more than 100 then the ones with the strongest RSSI will be scanned and put into the packet | + | At the moment 4 sensors (Base firmware / advance mode), this is expanded up to 100 in base firmware release which includes new EYE features. It is available with 03.29.XX base firmware. You do not need to configure the MAC address but instead enter the name (or part of name) of the sensor and all sensors with that name (or part of name) will be scanned. In case there are more than 100 sensors found then the ones with the strongest RSSI will be saved and put into the data packet. |
| | | |
− | ==== How to configure FM device for reading data from EYE sensor with standard Teltonika configurator(advanced mode)? ==== | + | ==== How to configure FM device for reading data from EYE sensor with standard Teltonika configurator (advanced mode)? ==== |
| + | Please follow the steps in EYE Sensor wiki page: https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Teltonika_configurator_.28standard_functionality_.2F_advanced_mode.29 |
| Please follow the steps in EYE Sensor wiki page: https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Teltonika_configurator_.28standard_functionality_.2F_advanced_mode.29 | | Please follow the steps in EYE Sensor wiki page: https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Teltonika_configurator_.28standard_functionality_.2F_advanced_mode.29 |
| | | |
Line 117: |
Line 119: |
| At the moment only presence is sent(1 or 0). | | At the moment only presence is sent(1 or 0). |
| A counter is only included in movement sensor's data. | | A counter is only included in movement sensor's data. |
− | It's possible to get evaluation firmware version with magnet counter functionality. | + | It is possible to get evaluation firmware version with magnet counter functionality. |
− | It's planned that it will be available in base firmware starting with EYE device firmware 1.2.10, you can follow changes here [[BTS firmware errata]] | + | It is planned that it will be available in base firmware in one of the future updates. You can follow changes here [[BTS firmware errata]] |
| Source:https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Protocol_description | | Source:https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1#Protocol_description |
| | | |
Line 126: |
Line 128: |
| | | |
| ==== What data can be read from the accelerometer? ==== | | ==== What data can be read from the accelerometer? ==== |
− | Only angle at the moment, with special development it's possible to receive accelerometer data. | + | Only angle at the moment, with special development it is possible to receive accelerometer data. |
| Angle consists of 3 Bytes, i.e.: Angle is received as 0BFFC7 in frame advertised by the sensor, it parses to: | | Angle consists of 3 Bytes, i.e.: Angle is received as 0BFFC7 in frame advertised by the sensor, it parses to: |
| C1 – Most significant byte represents device pitch. Device pitch can be from -90 to 90 degrees. | | C1 – Most significant byte represents device pitch. Device pitch can be from -90 to 90 degrees. |
Line 139: |
Line 141: |
| Calibrated Power - in the Beacon protocol is a critical parameter that helps estimate the distance between a beacon and a receiving device. For example, this value is sent in Byte 29 of the iBeacon packet and is typically set to a predefined value in the sensor's configuration. It indicates the transmitting power of the beacon at a reference distance of 1 meter and is measured in decibels referenced to 1 milliwatt (dBm). | | Calibrated Power - in the Beacon protocol is a critical parameter that helps estimate the distance between a beacon and a receiving device. For example, this value is sent in Byte 29 of the iBeacon packet and is typically set to a predefined value in the sensor's configuration. It indicates the transmitting power of the beacon at a reference distance of 1 meter and is measured in decibels referenced to 1 milliwatt (dBm). |
| | | |
− | RFU - Similarly to Calibarated Power, RFU is set for Eddystone protocols. The difference is iBeacon, the calibrated power is reference RSSI value that is the expected RSSI value at 1 meter from the beacon, while for Eddystone, it's the expected RSSI value at 0 meters. | + | RFU - Similarly to Calibarated Power, RFU is set for Eddystone protocols. The difference is that for iBeacon, the calibrated power is reference RSSI value that is the expected RSSI value at 1 meter from the beacon, while for Eddystone, it is the expected RSSI value at 0 meters. |
| | | |
| 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. | | 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. |
Line 146: |
Line 148: |
| | | |
| ==== What is the purpose of LED on the devices? ==== | | ==== What is the purpose of LED on the devices? ==== |
− | It does not have any functions currently that would be apparent for users. It's used internally for doublechecking device visually that it's powered correctly. It's left on PCB for future development options. | + | It does not have any functions currently that would be apparent for users. It is used internally for double checking device visually that it is powered correctly. It is left on PCB for future development options. |
| | | |
| ==== Can you calibrate the sensors? ==== | | ==== Can you calibrate the sensors? ==== |
| Temperature / Humidity sensors are pre-calibrated from factory. | | Temperature / Humidity sensors are pre-calibrated from factory. |
| For example, temperature long term drift is 0.03 Celsius/year, so the sensor should remain accurate within expected service-life time. | | For example, temperature long term drift is 0.03 Celsius/year, so the sensor should remain accurate within expected service-life time. |
− | It would be cheaper to purchase new sensor then to re-calibrate it. | + | It would be cheaper to purchase new sensor then to re-calibrate it. Therefore, there is no manual calibration option available/planned at the moment. |
− | Therefore there is no manual calibration option available/planned at the moment.
| + | If there are any specific requirements why the sensor be must be recalibrated, please contact your sales manager with detailed description of your use case. |
− | If there are any specific requirements why the sensor be must be recalibrated earlier or periodically, please contact your sales manager with detailed description of your use case. | |
| | | |
| ==== Can EYE sensors detect temperature less than -20°C? ==== | | ==== Can EYE sensors detect temperature less than -20°C? ==== |
− | It can detect less than -20°C we have been testing it in -40°C to +80°C, however, it's not recommended to use the device in temperature outside the compatible range for longer than a few hours. Temperature beyond recommended ranges will drain the battery faster than expected. | + | It can detect less than -20°C. We have tested devices in -40°C to +80°C. However, it is not recommended to use the device in temperature outside the compatible range for longer than a few hours. Temperature beyond recommended ranges will drain the battery faster than expected. |
| | | |
| ==== Can the EYE Sensor store data in memory and send it later in case of BT connection issues? ==== | | ==== Can the EYE Sensor store data in memory and send it later in case of BT connection issues? ==== |
− | Not possible with current HW assembly, in the future, we plan to have modifications with additional flash memory and functionality to save records in memory with an option to download data later. | + | Please refer to [https://teltonika-gps.com/products/accessories/sensors-beacons/eye-sensor-en12830 EN12830] sensor for temperature logging to internal memory. Temperature data stored in EN12830 modification is accessible via EYE App or your own custom solution. We are working on firmware for FM devices to retrieve historic data as well. |
| + | Other data can be stored to internal memory but would require firmware development that is not currently planned. |
| | | |
| ==== Do you need an additional magnet accessory to detect a magnet with the EYE Sensor? What is magnet detection range? ==== | | ==== Do you need an additional magnet accessory to detect a magnet with the EYE Sensor? What is magnet detection range? ==== |
− | Yes, we offer the needed accessory order code on our [https://teltonika-gps.com/eye/ landing page] The maximum range for magnet detection is 4cm. Please refer to the below image for mounting recommendation. | + | Yes, we offer the needed accessory order code on our [https://teltonika-gps.com/eye/ landing page]. The maximum range for magnet detection is 4cm. Please refer to the below image for mounting recommendation. |
| | | |
| [[File:MAGNET TRAILER MOUNTING.png|frameless|676x676px]] | | [[File:MAGNET TRAILER MOUNTING.png|frameless|676x676px]] |