Teltonika-BLE: Difference between revisions
→Direct BT connection (no adapter)
| (3 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
= Direct BT connection (no adapter) = | = Direct BT connection (no adapter) = | ||
Currently, '''the TD-BLE, DU-BLE and | Currently, '''the TD-BLE, TW-BLE (TD-150-BLE) DU-BLE and TH-BLE are compatible with certain Teltonika models''' (see the list on the last page of this document; note that it is not definitive; for a more precise list, please, contact Teltonika’s tech support). | ||
* Up to 4 sensors can be connected to the majority of different Teltonika models via Bluetooth | * Up to 4 sensors can be connected to the majority of different Teltonika models via Bluetooth | ||
| Line 18: | Line 18: | ||
== Bluetooth and Bluetooth 4.0 tabs (entering MAC address, BLE Scan settings) == | == Bluetooth and Bluetooth 4.0 tabs (entering MAC address, BLE Scan settings) == | ||
In the Teltonika configurator, go to the '''Bluetooth''' tab first. Make sure that everything is configured as shown on the | In the Teltonika configurator, go to the '''Bluetooth''' tab first. Make sure that everything is configured as shown on the screenshot below: | ||
[[File:Photo 5418063427176959105 x.jpg|frameless|408x408px]] | [[File:Photo 5418063427176959105 x.jpg|frameless|408x408px]] | ||
| Line 40: | Line 40: | ||
Further below you have 4 '''Connection slots''' to pair up to 4 sensors (those can be any TD, DU or TH sensors). Click on the '''Advanced''' button and then '''enter the MAC address''' of the sensor. | Further below you have 4 '''Connection slots''' to pair up to 4 sensors (those can be any TD, TW, DU or TH sensors). Click on the '''Advanced''' button and then '''enter the MAC address''' of the sensor. | ||
| Line 56: | Line 56: | ||
- “escort fuel” for TD-BLE, | - “escort fuel” for TD-BLE, | ||
- “escort luminosity” or “escort temperature” for TH-BLE, | - “escort luminosity” or “escort temperature” for TH-BLE, | ||
- “Escort DU_BLE” for [https://drive.google.com/file/d/1xQgTjlbQ8W2oOb8Owpj2Jr_U7xh4-2a0/view DU-BLE] | |||
- "Escort_TD_150_BLE" for [https://drive.google.com/file/d/1_wiyNRlUvUn0JarXYwcJNpeahZNlH1Fw/view TD-150-BLE] (TW-BLE) | |||
| Line 83: | Line 86: | ||
== System settings (Codec 8 Extended) == | == System settings (Codec 8 Extended) == | ||
In the '''System''' tab, click on the '''Codec 8 Extended''' option. | In the '''System''' tab, click on the '''Codec 8 Extended''' option. | ||
| Line 235: | Line 236: | ||
= BLE Fuel Level missing in I/O = | = Common issues and how to resolve them = | ||
'''If you cannot find the BLE Fuel Level parameter in the I/O tab''' of a newer version of Teltonika configurator, please, use one of the old ones available via the links below in the "Compatibility list" section of this article. | |||
== BLE Fuel Level missing in I/O == | |||
'''If you cannot find the BLE Fuel Level parameter in the I/O tab''' of a newer version of Teltonika configurator, please, use one of the old ones available via the links below in the "[[Teltonika-BLE#Compatibility list|Compatibility list]]" section of this article. | |||
The links allow you to download a compressed file with an old FW version (you don’t need to install it onto the tracker) and an older version of the configurator for different tracker models. | The links allow you to download a compressed file with an old FW version (you don’t need to install it onto the tracker) and an older version of the configurator for different tracker models. | ||
| Line 245: | Line 248: | ||
If there is a connection loss, after several attempts to collect the data (the '''Scan retries until error''' setting in the Bluetooth 4.0 tab) the tracker will transmit the error '''code 3000/300 in the temperature io'''. The level value will be transmitted as the last reading transmitted by the sensor if it was connected via the BLE base, or '''0\-4\65532''' in the fuel data. | If there is a connection loss, after several attempts to collect the data (the '''Scan retries until error''' setting in the Bluetooth 4.0 tab) the tracker will transmit the error '''code 3000/300 in the temperature io'''. The level value will be transmitted as the last reading transmitted by the sensor if it was connected via the BLE base, or '''0\-4\65532''' in the fuel data. | ||
Before installing a BLE sensor and a tracker, you need to properly configure the BLE Scan sessions as indicated | '''Before installing a BLE sensor and a tracker, you need to properly configure the BLE Scan sessions as indicated [[Teltonika-BLE#Bluetooth and Bluetooth 4.0 tabs (entering MAC address, BLE Scan settings)|above]]) and check the stability of the Bluetooth connection to select the best spot to install the GPS tracker/gateway (or BLE-RS485-RS232 adapter) to minimize the risks of connection losses happening in the future. Also, be sure to orient the antennas of the devices as per recommendations provided [[Teltonika-BLE#Antenna orientation|above]].''' | ||
To determine if the connection between the Bluetooth transmitter of the sensor and the Bluetooth receiver is stable or not, you should use the RSSI parameter. When you search for a place to install the GPS tracker, you should calculate the average RSSI (Received Signal Strength Indicator) by taking into account the 10 or more measurements of the RSSI taken over the course of 2-3 minutes while the engine of the vehicle is running and all electronics inside the cab and around the vehicle are switched on. | To determine if the connection between the Bluetooth transmitter of the sensor and the Bluetooth receiver is stable or not, you should use the RSSI parameter. When you search for a place to install the GPS tracker, [[Teltonika-BLE#RSSI check|you should calculate the average RSSI]] (Received Signal Strength Indicator) by taking into account the 10 or more measurements of the RSSI taken over the course of 2-3 minutes while the engine of the vehicle is running and all electronics inside the cab and around the vehicle are switched on. | ||
The reason why the RSSI should be taken as the average value is that the RSSI itself is a dynamic parameter, its value changes constantly. This average value must be within the connection stability range. | The reason why the RSSI should be taken as the average value is that the RSSI itself is a dynamic parameter, its value changes constantly. This average value must be within the connection stability range. | ||