EYE SENSOR / BTSMP1: Difference between revisions

(15 intermediate revisions by 6 users not shown)

Line 45:

|-

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Battery life (Tx=2 dBm; interval: 3 s)

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |2.5+ years

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |2.5 years

|-

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Battery life (Tx=2 dBm; interval: 5 s), default

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4+ years

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4 years

|-

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Battery life (Tx=2 dBm; interval: 10 s)

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |5+ years

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |5 years

|}

{| class="wikitable"

Line 59:

|-

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Bluetooth®

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Bluetooth® 4.2 compliant,

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Bluetooth® 4.2 compliant

~~Bluetooth® 5.2 certified~~

|-

| style="width:10%;border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Range

Line 117:

Line 116:

==Value-adding Features==

===EN12830 ~~Certification~~===

===EN12830 Certified Model version===

EN12830 is a European standard specifying the requirements and test methods for temperature recording devices used in the storage, transport, and distribution of chilled, frozen, deep-frozen, and quick-frozen food and other types of products. It ensures these devices meet specific accuracy, resolution, and response time criteria to maintain product safety and quality.

Line 144:

Line 143:

* Improves product quality and extends shelf life.

====How ~~it works~~====

====How to receive temperature data from EN12830 sensors====

You can download:

* Current temperature via FM trackers.

* Current and historical* temperature via FM trackers (* for historic data download, evaluation firmware version 03.29.00.Rev.255 is available by request via HelpDesk).

* Current and historical temperature via <big>[https://wiki.teltonika-gps.com/view/Teltonika_EN12830_EYE_APP EYE APP EN12830].</big>

* Current and historical temperature via your own application. Download functionality and implementation instructions <big>[[Media:BTSXXXX.EN12830 Functionality Description for Client V1.1.pdf|HERE]]</big>.

Please note that temperature recording must be enabled beforehand via the same APP.

[[File:~~EN12830 how it works~~.png|871x871px]]

[[File:EN12830_how_it_works_V2.png|871x871px]]

===Hibernate mode===

Line 689:

Line 688:

===Teltonika configurator new functionalities EYE Sensor filtering by name===

Starting with firmware 03.28.04.Rev.~~207~~ there is additional tabs available in Bluetooth® 4.0 section that allow for easier configuration to connect FM and EYE sensor or beacon.

Starting with firmware 03.29.00.Rev.13 there is additional tabs available in Bluetooth® 4.0 section that allow for easier configuration to connect FM and EYE sensor or beacon.

'''It's now possible to connect up to 100 sensors at once just by entering one name in the configurator name list.''' It's required to enter at least 3 characters(case sensitive) in the name for FM to scan the sensors. Super easy to set up!

For example, ~~the~~ you may order Sensors with special configuration from factory where the EYE Sensor names would be TRAILER_1,TRAILER_2,...,TRAILER_99 and so on.

For example, you may order Sensors with special configuration from factory where the EYE Sensor names would be TRAILER_1,TRAILER_2,...,TRAILER_99 and so on.

If you would enter ~~TRAILERS~~ in the EYE Fimrware FM configurator then sensors who meet this name condition, for example TRAILER_1, TRAILER_21 , TRAILER_17, would be scanned, while other sensors named Tools, MP1_123546, etc. will not be scanned.

If you would enter TRAILER in the EYE Fimrware FM configurator then sensors who meet this name condition, for example TRAILER_1, TRAILER_21 , TRAILER_17, would be scanned, while other sensors named Tools, MP1_123546, etc. will not be scanned.

With this option, you can upload one configuration to FOTA web and it doesn’t matter which sensor from the list end user will mount, it will be scanned and sent to the server as long as it meets the name criteria.

Line 1,309:

Line 1,308:

<td style="width: 25%; text-align:center; vertical-align:middle;">Movement count value of EYE Sensor 4</td>

</tr>

<tr>

<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Magnet count 1</td>

<td style="width: 10%; text-align:center; vertical-align:middle;">unsigned</td>

<td style="width: 25%; text-align:center; vertical-align:middle;">Magnet trigger count measure by EYE Sensor 1</td>

</tr>

<tr>

<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Magnet count 2</td>

<td style="width: 10%; text-align:center; vertical-align:middle;">unsigned</td>

<td style="width: 25%; text-align:center; vertical-align:middle;">Magnet trigger count measure by EYE Sensor 2</td>

</tr>

<tr>

<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Magnet count 3</td>

<td style="width: 10%; text-align:center; vertical-align:middle;">unsigned</td>

<td style="width: 25%; text-align:center; vertical-align:middle;">Magnet trigger count measure by EYE Sensor 3</td>

</tr>

<tr>

<td style="width: 20%; text-align:center; vertical-align:middle;">EYE Magnet count 4</td>

<td style="width: 10%; text-align:center; vertical-align:middle;">unsigned</td>

<td style="width: 25%; text-align:center; vertical-align:middle;">Magnet trigger count measure by EYE Sensor 4</td>

</tr>

</table>

Eye sensor parameters have error code values, which will written to the I/O value if parameter data is not received. From the error code value, it is possible to distinguish whether the issue is on the FM tracker side or the EYE Sensor. Below is a table describing these values.

Line 2,344:

Line 2,385:

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |All

|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Anatel (EU) (PR)

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Anatel (BR) (PR)

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |[[BTSMP1_ANATEL|Yes]]

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | All

Line 2,424:

Line 2,465:

Teltonika Networks:

https://wiki.teltonika-networks.com/view/Bluetooth_EYE_Sensor_and_EYE_Beacon_support

https://wiki.teltonika-networks.com/view/Teltonika_EYE_device_pairing_and_data_sender_configuration_example

===Partner Providers Supporting Software===

Line 2,467:

Line 2,510:

|(Updated on: {{{datasheet_date|2024-04-02}}})

|}

==Additional information==

{{{EOL|For EOL policy please refer to link [https://teltonika-gps.com/support/eol-products here].}}}

[[Category:Sensors]]