Template:Bluetooth 4.0 settings

Pages with broken file links > Template:Bluetooth 4.0 settings


X offers Bluetooth 4.0 (Bluetooth Low Energy, also referred as BLE) functionality.

Common settings

Bluetooth 4.0 common settings.png
  • Non Stop Scan - Enabled Non Stop Scan feature, the device will try to scan for the sensors all the time if any of them are configured.
  • BLE Scan Start Period - This parameter determines when the next BLE scan will start for Beacons and TZ sensors.
  • BLE Scan Duration - Sensors data reading time.
  • Scan retries until error - Configured scan retries, to show the Error Value '3000' - sensor disconnected.
  • BT power level - The BT power level can be selected. Approximate range in meters:
    1 - <0.5
    2 - 0.5
    3 - 11
    4 - 13
    5 - 15
    6 - 27
    7 - 50
  • BLE broadcasting service ID - When any ID is provided, the broadcasting is enabled.
  • BLE connection control - if Enabled, the BLE connections are allowed.
  • Backup Tracker - enabled or disabled Backup tracker scenario.
NOTE! Backup Tracker feature only available on the FW 55.01.00 Rev 0 or newer.


Configuration modes

Bluetooth 4.0 common settings non stop scan.png
  • 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.
Bluetooth 4.0 common settings.png
  • If Non Stop Scan Disabled, Scan period is selected manually.

The Scan time period will be selected from two sources:

  • BLE Scan Duration - the time when sensors are scanned,
  • Update frequency - The time when the sensor information is packed as the AVL Data record.

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


Aes encryption.png

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.

BLE terminal ciphered.png

This Simple BLE Terminal is for AES128 functionality testing as it has an Encryption Key option. Set correct key in app settings.


NOTE! AES128 feature only available on the 55.01.06.Rev.00 FW or newer.


Detailed instructions on how to test AES128 BLE Encryption Functionality can be found in the following link.


BLE connectionless functionalities

BLE connectionless functionalities.png

Currently to the X device up to 4 sensors can be connected.

When Advanced mode is selected a table with configurable parameters will appear. BLE connectionless functionalities advanced.png

  • 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.

Preset1.png


At the top right corner, you should see the following Buttons, press on the first one from the left.

Preset2.png

After the named Button was pressed the list with all supported sensors and the configuration presets should appear.

Preset3.png


Select your sensor and click load. The correct configuration and recommended settings will appear in the configuration.

Preset4.png

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

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.

Example for formatting:

IMAGE DISCLAIMER.png