Template:Bluetooth® 4.0 settings: Difference between revisions
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 70: | Line 70: | ||
}}} | }}} | ||
{{#switch: {{{model}}} | {{#switch: {{{model}}} | ||
|TFT100 = | |TFT100 = | ||
==Sensors== | ==Sensors== | ||
TFT100 allows configuring '''Custom Sensors''' and '''EYE Sensors'''. | TFT100 allows configuring '''Custom Sensors''' and '''EYE Sensors'''. | ||
[[File:TFT100 - Sensor Configuration.png]] | [[File:TFT100 - Sensor Configuration.png]] | ||
*When '''Custom Sensors''' is selected, BLE connectionless functionalities will appear. | *When '''Custom Sensors''' is selected, BLE connectionless functionalities will appear. | ||
*When '''EYE Sensors''' is selected, EYE sensor by MAC functionalities will appear. | *When '''EYE Sensors''' is selected, EYE sensor by MAC functionalities will appear. | ||
|#default= | |#default= | ||
| Line 103: | Line 108: | ||
===Supported Sensors List=== | ===Supported Sensors List=== | ||
This list shows the supported BLE sensors and where their Presets can be found in the configurator to use those sensors with FMB devices. The prests and sensors have been fully tested by Teltonika and are confirmed to work properly. | This list shows the supported BLE sensors and where their Presets can be found in the configurator to use those sensors with FMB devices. The prests and sensors have been fully tested by Teltonika and are confirmed to work properly. | ||
| Line 144: | Line 148: | ||
{{#switch: {{{model}}} | {{#switch: {{{model}}} | ||
|TFT100 = | |TFT100 = | ||
==EYE Sensors== | ==EYE Sensors== | ||
'''Note:''' Feature only available from firmware version '''55.02.03.Rev.02''' and later. | '''Note:''' Feature only available from firmware version '''55.02.03.Rev.02''' and later. | ||
| Line 155: | Line 161: | ||
*'''MAC Settings''' - parameter specifies the MAC address of the EYE Sensor for the FM tracker to read, parse its data and put to corresponding IO elements. If the sensor is not found for set amount of scan retries, error values will be stored into IO elements. | *'''MAC Settings''' - parameter specifies the MAC address of the EYE Sensor for the FM tracker to read, parse its data and put to corresponding IO elements. If the sensor is not found for set amount of scan retries, error values will be stored into IO elements. | ||
*'''Data clear period (s)''' – parameter defines period in seconds, for how long sensor has to be not detected in order to remove it from EYE Sensor List. | *'''Data clear period (s)''' – parameter defines period in seconds, for how long sensor has to be not detected in order to remove it from EYE Sensor List. | ||
*'''I/O elements''' - allows for advanced EYE sensor. More information can be found in [[{{{model}}}I/O settings]]. | *'''I/O elements''' - allows for advanced EYE sensor. More information can be found in [[{{{model}}} I/O settings]]. | ||
[[File:EYE Sensor conifiguration.png]] | [[File:EYE Sensor conifiguration.png]] | ||
| Line 161: | Line 167: | ||
===EYE Sensor AVL IDs=== | ===EYE Sensor AVL IDs=== | ||
{{{model}}} EYE Sensor AVL ID's are provided in [[{{{model}}} | {{{model}}} EYE Sensor AVL ID's are provided in [[{{{model}}} AVL ID List]]. | ||
===Eye Sensor Error Values=== | ===Eye Sensor Error Values=== | ||
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. | 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. | ||
}} | |||
{{#switch: {{{model}}} | |||
|TFT100 = | |||
{| class="nd-othertables_2" style="width:100%;" | {| class="nd-othertables_2" style="width:100%;" | ||
| Line 240: | Line 251: | ||
| style="vertical-align: middle; text-align: center;" |251 | | style="vertical-align: middle; text-align: center;" |251 | ||
|} | |} | ||
}} | }} | ||
Revision as of 09:32, 18 March 2026
Disclaimer
If you are not using Bluetooth®, please consider turning it off or change Bluetooth® PIN to remove potential risks.
If you are using Bluetooth® we strongly recommend using AES encryption for enhanced security.
X offers Bluetooth® 4.0 (Bluetooth® Low Energy, also referred as BLE) functionality.
Common settings
|
Configuration modes
- If the Non Stop Scan is Enabled, the Non Stop sensor scans until any error will be hidden. Although BLE scan duration will still be active because it is important for btgetlist SMS command.
The Scan time period will be selected from two sources:
For example, if Update frequency - 120 seconds and BLE Scan Duration - 60 Seconds, the device will start the first scan after 120 seconds and will scan nearby BLE devices for 60 seconds to update configured sensor data. The sensor data will be updated every 120 seconds. Update Frequency is counted even while a scan is performed. Update frequency period passes. 120 seconds -> 0 seconds, a 60 second scan is initiated. Update Frequency countdown is restarted (countdown from configured value to 0) while the scan (according to the BLE Scan duration parameter) is performed. |
BLE Serial Encryption
If BLE Encryption Key is set, then device will communicate over BLE SPP (Serial Port Profile) with AES cipher mechanism. All incoming and outgoing data will be crypted with AES128 algorithm with entered key. Connected to the other side device must have similar encryption method and algorithm BLE Encryption Key is a 16 byte hex coded string, like 00112233445566778899AABBCCDDEEFF
Keep BLE Encryption Key blank to non crypted communications.
This Simple BLE Terminal is for AES128 functionality testing as it has an Encryption Key option. Set correct key in app settings.
Detailed instructions on how to test AES128 BLE Encryption Functionality can be found in the following link.
BLE connectionless functionalities
 Currently to the X device up to 4 sensors can be connected. |
When Advanced mode is selected a table with configurable parameters will appear.
- Type – EIR data type. This parameter will indicate which type to look for and work with. Note: We have also added type with value 0xFE which will indicate to work with a whole data packet and not just a single data type.
- Data Offset – start index of data we are interested in.
- Data Size – size of the data we are interested in.
- Action – two actions are possible: Match and Save. Match means that we want to perform a validation of certain data. Save means that we want to get certain data and later save it to an AVL record.
- IO – tells which IO element's data will be saved to.
- Match – hex string to be matched with BLE sensor data. Used only with Match action.
- Endianness – endianness of data: little endian (ex. 0x1122) or big endian (ex. 0x2211). Used only with Save action.
- Multiplier – value to be used to multiply output data. Used only with Save action.
- Offset – value to be added to output data. Used only with Save action.
How to correctly configure the Bluetooth® LE solutions, can be found here:
Supported Sensors List
This list shows the supported BLE sensors and where their Presets can be found in the configurator to use those sensors with FMB devices. The prests and sensors have been fully tested by Teltonika and are confirmed to work properly.
While following the steps showed in the images below, you can find the supported sensors in our Configurator.
In the Configurator, find the Bluetooth® 4.0 Settings menu, select the advanced sensors mode which was mentioned before. The following window should appear.
At the top right corner, you should see the following Buttons, press on the first one from the left.
After the named Button was pressed the list with all supported sensors and the configuration presets should appear.
Select your sensor and click load. The correct configuration and recommended settings will appear in the configuration.
The supported sensors are listed below:
- EYE Sensor
- BLE TPMS -Tire Pressure Monitoring System.
- Efento Humidity BLE sensors (version 2.2 and 4 presets)
- ELA ANG (Angle)
- ELA MOV AG (Movement and Angle)
- ELA PUCK ID (ID)
- ELA RHT (Temperature and Humidity)
- ELA T (Temperature)
- ELA MOV MAG (Movement Magnetic)
- Escort Fuel BLE sensors
- Escort luminosity BLE sensors
- Escort Temperature BLE sensors
- S1 BLE Motion, Humidity and Temperature Sensors
- Technoton Wireless fuel level sensors
- TZ-BT04 Temperature and Humidity Sensors
- TZ-BT05 Temperature and Humidity Sensors
Save your own settings as a preset/delete the preset
}