Difference between revisions of "FMC650 Bluetooth 4.0 settings"

From Wiki Knowledge Base | Teltonika GPS
(AVL IDs were corrected also, disclaimer and text "FMB1YX offers" was removed.)
(Created page with "__TOC__ ==Disclaimer== left|link= <br> If you are not using Bluetooth®, '''please consider turning it off''' or '''change Bluetooth® PIN''' to remove pot...")
Line 1: Line 1:
 
__TOC__
 
__TOC__
 +
==Disclaimer==
 +
 +
[[File:Alert.png|left|link=]] <br> 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.
 +
 
==Bluetooth® 4.0 settings==
 
==Bluetooth® 4.0 settings==
  
−
Bluetooth® 4.0 (Bluetooth® Low Energy, also referred as BLE) functionality.
+
{{{model|FMB1YX}}} offers Bluetooth® 4.0 (Bluetooth® Low Energy, also referred as BLE) functionality.
  
 
[[Image:Blue-tooth 4.0v2 settings for FMX6X0.png|300px|none]]
 
[[Image:Blue-tooth 4.0v2 settings for FMX6X0.png|300px|none]]
Line 13: Line 19:
 
*'''''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.
 
*'''''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.
 
*'''''Working mode''''' – Bluetooth® connection mode''. '''Disabled''':'' Bluetooth® 4.0 connection will not be used. '''''TZ-BT04/05/05B sensor''':'' this Bluetooth® connection will be used to communicate with TZ-BT04/05/05B sensor. '''''Advanced''' -'' It allows to gather data from BLE device‘s broadcast packets regardless of what data packing protocol is used''.''
 
*'''''Working mode''''' – Bluetooth® connection mode''. '''Disabled''':'' Bluetooth® 4.0 connection will not be used. '''''TZ-BT04/05/05B sensor''':'' this Bluetooth® connection will be used to communicate with TZ-BT04/05/05B sensor. '''''Advanced''' -'' It allows to gather data from BLE device‘s broadcast packets regardless of what data packing protocol is used''.''
−
*'''''Local Name''''' – Bluetooth® local name user for pairing. If it is empty, name will be automatically generated: FMBxxx_<last 7 IMEI digits>. Maximum name length =  16 characters
+
*'''''Local Name''''' – Bluetooth® local name user for pairing. If it is empty, name will be automatically generated: FMBxxx_<last 7 IMEI digits>. Maximum name length =  16 characters''
  
 
==Configuration modes==
 
==Configuration modes==
Line 41: Line 47:
  
 
*The table has 9 types of parameters:
 
*The table has 9 types of parameters:
−
*# 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.
+
*#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 Offset – start index of data we are interested in.
 
*#Data Size – size of the 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.
+
*#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. Possible choices for IO elements will be described later in the chapter. '''Used only with Save action.'''
+
*#IO – tells which IO element's data will be saved to. Possible choices for IO elements will be described later in the chapter. '''Used only with Save action.'''
 
*#Match – hex string to be matched with BLE sensor data. '''Used only with Match action.'''
 
*#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.'''
 
*#Endianness – endianness of data: little endian (ex. 0x1122) or big endian (ex. 0x2211). '''Used only with Save action.'''
Line 51: Line 57:
 
*#Offset – value to be added to output data. '''Used only with Save action.'''  <br />
 
*#Offset – value to be added to output data. '''Used only with Save action.'''  <br />
  
−
'''More information about Advanced Beacon Capturing Configuration can be found [[Advanced Beacon Capturing Configuration|HERE]]'''
+
'''More information about Advanced Beacon Capturing Configuration can be found [[Advanced Beacon Capturing Configuration|HERE]]
  
 
==IO elements choices==
 
==IO elements choices==
Line 57: Line 63:
 
|Name
 
|Name
 
|Connection #1 AVL ID
 
|Connection #1 AVL ID
−
| Connection #2 AVL ID
+
|Connection #2 AVL ID
 
|Connection #3 AVL ID
 
|Connection #3 AVL ID
 
|Connection #4 AVL ID
 
|Connection #4 AVL ID
Line 68: Line 74:
 
|-
 
|-
 
|Temperature
 
|Temperature
−
| 701
+
|25
−
|702
+
|26
−
|703
+
|27
−
|704
+
|28
 
|-
 
|-
 
|Battery
 
|Battery
−
|705
+
|29
−
| 706
+
|20
−
|707
+
|22
−
|708
+
|23
 
|-
 
|-
 
|Humidity
 
|Humidity
−
|709
+
|86
−
|710
+
|104
−
|711
+
|106
−
|712
+
|108
 
|-
 
|-
−
|Custom0
+
|Custom1
−
|713
+
|331
−
|714
+
|332
−
|715
+
|333
−
|716
+
|334
−
|-
 
−
|Illumination
 
−
|717
 
−
|718
 
−
|719
 
−
|720
 
 
|-
 
|-
 
|Fuel
 
|Fuel
−
|721
+
|270
−
|722
+
|273
−
|723
+
|276
−
|724
+
|279
 
|-
 
|-
−
| Fuel Frequency
+
|Luminosity
−
|725
+
|335
−
|726
+
|336
−
|727
+
|337
−
|728
+
|338
 
|-
 
|-
−
|Custom1
+
|Fuel Frequency
−
|729
+
|306
−
|730
+
|307
−
|731
+
|308
−
|732
+
|309
 
|-
 
|-
 
|Custom2
 
|Custom2
−
|733
+
|463
−
|734
+
|467
−
|735
+
|471
−
|736
+
|475
 
|-
 
|-
 
|Custom3
 
|Custom3
−
|737
+
|464
−
|738
+
|468
−
|739
+
|472
−
|740
+
|476
 
|-
 
|-
 
|Custom4
 
|Custom4
−
|741
+
|465
−
|742
+
|469
−
|743
+
|473
−
|744
+
|477
 +
|-
 +
|Custom5
 +
|466
 +
|470
 +
|474
 +
|478
 
|}
 
|}
 
==Supported Sensors List==
 
==Supported Sensors List==
Line 158: Line 164:
 
*BLE TPMS -Tire Pressure Monitoring System.
 
*BLE TPMS -Tire Pressure Monitoring System.
 
*Efento Humidity BLE sensors (version 2.2 and 4 presets)
 
*Efento Humidity BLE sensors (version 2.2 and 4 presets)
−
* ELA ANG (Angle)
+
*ELA ANG (Angle)
 
*ELA MOV AG (Movement and Angle)
 
*ELA MOV AG (Movement and Angle)
 
*ELA PUCK ID (ID)
 
*ELA PUCK ID (ID)
Line 176: Line 182:
 
==Visual demonstration==
 
==Visual demonstration==
 
Here is a visual demonstration of Bluetooth® 4.0 sensors in a cold storage truck.
 
Here is a visual demonstration of Bluetooth® 4.0 sensors in a cold storage truck.
−
<br /><br /><youtube>n0yJvoCBZLI</youtube><br />
+
<br/><br/><youtube>n0yJvoCBZLI</youtube><br/>
  
 
==FMB Family Bluetooth® 4.0 support==
 
==FMB Family Bluetooth® 4.0 support==
 
Devices that are listed in table below shows which device model has Bluetooth® 4.0 hardware installed. If your device is manufactured before the day shown in the list it means that this model does not have Bluetooth® functionality or it has an older version installed. The date shown in the table depends on when hardware production has started, but not when first lot was sold.  
 
Devices that are listed in table below shows which device model has Bluetooth® 4.0 hardware installed. If your device is manufactured before the day shown in the list it means that this model does not have Bluetooth® functionality or it has an older version installed. The date shown in the table depends on when hardware production has started, but not when first lot was sold.  
 
<br>
 
<br>
−
 
−
 
 
<table class="nd-othertables" style="width: 40%;">
 
<table class="nd-othertables" style="width: 40%;">
 
  <tr>
 
  <tr>
 
         <th style="width: 20%; text-align:center; vertical-align:middle; color: black">Device Model</th>
 
         <th style="width: 20%; text-align:center; vertical-align:middle; color: black">Device Model</th>
 
         <th style="width: 20%; text-align:center; vertical-align:middle; color: black">BT 4.0 manufacture starting date</th>
 
         <th style="width: 20%; text-align:center; vertical-align:middle; color: black">BT 4.0 manufacture starting date</th>
−
     </tr><tr><td>FM3001</td><td>2018.01</td></tr><tr>       <tr>
+
     </tr><tr><td>FM3001</td><td>2018.01</td></tr><tr>
 +
        <tr>
 
         <td style="vertical-align:middle">FMB001</td>
 
         <td style="vertical-align:middle">FMB001</td>
 
         <td style="vertical-align:middle">2018.04</td>
 
         <td style="vertical-align:middle">2018.04</td>
Line 237: Line 242:
 
         <td style="vertical-align:middle">FMB125</td>
 
         <td style="vertical-align:middle">FMB125</td>
 
         <td>2017.11</td>
 
         <td>2017.11</td>
 +
  
 
<tr><td>FMB130</td><td>All versions</td></tr>
 
<tr><td>FMB130</td><td>All versions</td></tr>
Line 254: Line 260:
 
<tr><td>FMC650</td><td>All versions</td></tr>
 
<tr><td>FMC650</td><td>All versions</td></tr>
 
<tr><td>FMM650</td><td>All versions</td></tr>
 
<tr><td>FMM650</td><td>All versions</td></tr>
−
<tr><td>FMT100</td><td>All versions</tr>
+
<tr><td>FMT100</td><td>All versions</tr></tr>
−
<tr><td>FMP100</td><td>All versions</tr>
+
<tr><td>FMP100</td><td>All versions</tr></tr>
−
<tr><td>FMC800</td><td>All versions</tr>
+
<tr><td>FMC800</td><td>All versions</tr></tr>
−
<tr><td>FMM800</td><td>All versions</tr>
+
<tr><td>FMM800</td><td>All versions</tr></tr>
−
<tr><td>FMC880</td><td>All versions</tr>
+
<tr><td>FMC880</td><td>All versions</tr></tr>
−
<tr><td>FMM880</td><td>All versions</tr>
+
<tr><td>FMM880</td><td>All versions</tr></tr>
 
</table>
 
</table>

Revision as of 09:52, 8 May 2024

Disclaimer

Alert.png


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.

Bluetooth® 4.0 settings

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

Blue-tooth 4.0v2 settings for FMX6X0.png

Configurable parameters:

  • Update frequency – changes sensor's temperature/humidity/battery voltage data update frequency.
    Minimum value: 30 s, maximum value: 65535 s, default value: 30.
  • BLE Scan Duration - Sensors data reading time.
  • Scan retries until error - Configured scan retries, to show the Error Value '3000' - sensor disconnected.
  • 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.
  • Working mode – Bluetooth® connection mode. Disabled: Bluetooth® 4.0 connection will not be used. TZ-BT04/05/05B sensor: this Bluetooth® connection will be used to communicate with TZ-BT04/05/05B sensor. Advanced - It allows to gather data from BLE device‘s broadcast packets regardless of what data packing protocol is used.
  • Local Name – Bluetooth® local name user for pairing. If it is empty, name will be automatically generated: FMBxxx_<last 7 IMEI digits>. Maximum name length = 16 characters

Configuration modes

Non Stop Scan Enabled.

Non stop scan FMX6X0.png

In Configurator when Non Stop sensor scan is active update frequency & scan retries until error will be hidden.


Non Stop Scan Disabled, Scan period is selected manually.

Scan FMX6X0.png

From the picture above, the Scan time period will be selected from two sources, BLE Scan Duration - the time when sensors are scanned and the Update frequency - The time when the sensor information is packed as the AVL Data record.

For example:

Update frequency - 120 seconds.

BLE Scan Duration - 60 Seconds

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.

Advanced Mode


When Advanced mode is selected a table with configurable parameters will appear:

BLE advanced window.png


  • The table has 9 types of parameters:
    1. 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.
    2. Data Offset – start index of data we are interested in.
    3. Data Size – size of the data we are interested in.
    4. 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.
    5. IO – tells which IO element's data will be saved to. Possible choices for IO elements will be described later in the chapter. Used only with Save action.
    6. Match – hex string to be matched with BLE sensor data. Used only with Match action.
    7. Endianness – endianness of data: little endian (ex. 0x1122) or big endian (ex. 0x2211). Used only with Save action.
    8. Multiplier – value to be used to multiply output data. Used only with Save action.
    9. Offset – value to be added to output data. Used only with Save action.

More information about Advanced Beacon Capturing Configuration can be found HERE

IO elements choices

Name Connection #1 AVL ID Connection #2 AVL ID Connection #3 AVL ID Connection #4 AVL ID
None - - - -
Temperature 25 26 27 28
Battery 29 20 22 23
Humidity 86 104 106 108
Custom1 331 332 333 334
Fuel 270 273 276 279
Luminosity 335 336 337 338
Fuel Frequency 306 307 308 309
Custom2 463 467 471 475
Custom3 464 468 472 476
Custom4 465 469 473 477
Custom5 466 470 474 478

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

Visual demonstration

Here is a visual demonstration of Bluetooth® 4.0 sensors in a cold storage truck.


FMB Family Bluetooth® 4.0 support

Devices that are listed in table below shows which device model has Bluetooth® 4.0 hardware installed. If your device is manufactured before the day shown in the list it means that this model does not have Bluetooth® functionality or it has an older version installed. The date shown in the table depends on when hardware production has started, but not when first lot was sold.


Device Model BT 4.0 manufacture starting date
FM30012018.01
FMB001 2018.04
FMB010 2018.04
FMB020 All versions
FMB002 All versions
FMB003 All versions
FMB900 2018.08
FMB920 2018.07
FMB964 2019.07
FMB110 2018.01
FMB120 2018.01
FMB122 2017.11
FMB125 2017.11
FMB130All versions
FMB140All versions
FMU125FW is on release, All versions
FMU126FW is on release, All versions
FMU130FW is on release, All versions
FMM125FW is on release, All versions
FMM130FW is on release, All versions
FMM0YXFW is on release, All versions
FMC130FW is on release, All versions
FMB202All versions
FMB204All versions
FMB208All versions
FMC640All versions
FMM640All versions
FMC650All versions
FMM650All versions
FMT100All versions
FMP100All versions
FMC800All versions
FMM800All versions
FMC880All versions
FMM880All versions
Retrieved from "https://wiki.teltonika-gps.com/index.php?title=FMC650_Bluetooth_4.0_settings&oldid=98081"