Difference between revisions of "Template:FMB Blue-tooth 4.0 settings"
From Wiki Knowledge Base | Teltonika GPS
| (57 intermediate revisions by 21 users not shown) | |||
| Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
| − | |||
| − | + | ==Bluetooth 4.0 settings== | |
| − | + | {{{model|FMB1YX}}} offers Bluetooth 4.0 (Bluetooth Low Energy, also referred as BLE) functionality. User is able to discover nearby BLE devices and their services. Another feature is TZ-BT04/05 sensor support. Sensors provide data about temperature (TZ-BT04 and TZ-BT05) and humidity (TZ-BT04 only). | |
| − | + | [[Image:Blue-tooth 4.0v2 settings.PNG|300px|none]] | |
| − | |||
| − | |||
| − | |||
Configurable parameters: | Configurable parameters: | ||
| − | *'''''Non Stop Scan''''' - Enabled Non Stop Scan feature, | + | *'''''Non Stop Scan''''' - Enabled Non Stop Scan feature, device will try to scan for the sensors all the time if any of them are configured. |
| − | *'''''TZ-BT04/05/05B Update frequency''''' – changes sensor's temperature/humidity/battery voltage data update frequency. <br /> Minimum value: | + | *'''''TZ-BT04/05/05B Update frequency''''' – changes sensor's temperature/humidity/battery voltage data update frequency. <br /> Minimum value: 120 s, maximum value: 65535 s, default value: 120. |
*'''''BLE Scan Duration''''' - Sensors data reading time. | *'''''BLE Scan Duration''''' - Sensors data reading time. | ||
*'''''Scan retries until error''''' - Configured scan retries, to show the Error Value '3000' - sensor disconnected. | *'''''Scan retries until error''''' - Configured scan retries, to show the Error Value '3000' - sensor disconnected. | ||
| − | *'''''Working mode''''' – | + | *'''''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''.'' |
| − | |||
| − | |||
| − | |||
| − | + | ==Few Examples of the Configured Values:== | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Non Stop Scan Enabled. | Non Stop Scan Enabled. | ||
[[Image:Non Stop.png|300px|none]] | [[Image:Non Stop.png|300px|none]] | ||
| − | In | + | |
| + | In configurator when nonstop sensor scan is active update frequency & scan retries until error will be hidden. Although BLE scan duration will still be active because it is important for btgetlist SMS command. | ||
| Line 42: | Line 27: | ||
[[Image:Scan.png|300px|none]] | [[Image:Scan.png|300px|none]] | ||
| − | From the picture above, the Scan time period will be selected from two sources, '''''BLE Scan Duration'' -''' the time when sensors | + | From the picture above, the Scan time period will be selected from two sources, '''''BLE Scan Duration'' -''' the time when sensors is scanned and the '''''Update frequency''''' - The time when the sensors information is packet as the AVL Data record. |
| − | For example | + | For example. |
'''''Update frequency''' - 120 seconds.'' | '''''Update frequency''' - 120 seconds.'' | ||
| Line 50: | Line 35: | ||
'''''BLE Scan Duration''''' ''- 60 Seconds'' | '''''BLE Scan Duration''''' ''- 60 Seconds'' | ||
| − | Device | + | Device first scan the sensors for the 60 seconds, after this time, the device will pack the remaining records to the AVL data package. Total sensors information update time will be 120 seconds. |
| − | + | <br /> | |
| − | ==Advanced Mode== | + | == Advanced Mode == |
<br>When Advanced mode is selected a table with configurable parameters will appear:[[Image:BLE advanced window.png|1000px|none]]<br /> | <br>When Advanced mode is selected a table with configurable parameters will appear:[[Image:BLE advanced window.png|1000px|none]]<br /> | ||
| Line 60: | Line 45: | ||
*#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 | + | *#Data Size – size of 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 | + | *#IO – tells which IO elements 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.''' | ||
*#Multiplier – value to be used to multiply output data. '''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.''' <br /> | *#Offset – value to be added to output data. '''Used only with Save action.''' <br /> | ||
| − | |||
| − | |||
==IO elements choices== | ==IO elements choices== | ||
| Line 149: | Line 132: | ||
|474 | |474 | ||
|478 | |478 | ||
| − | |} | + | |}<br /> |
==Supported Sensors List== | ==Supported Sensors List== | ||
| − | + | Devices which are listed with the BT 4.0 supportive, have the extended List of the BLE Sensors which are available as the Preset settings and was fully tested from our end with the supportive. | |
| − | |||
| − | |||
| − | + | While following the steps showed in the images below, you can find the supported sensors in our configurator. | |
[[Image:Preset1.png|1200px|none]] | [[Image:Preset1.png|1200px|none]] | ||
| − | + | After the '''Showed Presets Button''' was pressed, the following window should appear. | |
[[Image:Preset2.png|200px|none]] | [[Image:Preset2.png|200px|none]] | ||
| − | |||
| − | |||
| − | |||
| − | + | The supportive sensors are listed below: | |
| − | |||
| − | |||
| − | |||
*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) | ||
| Line 189: | Line 164: | ||
*TZ-BT05 Temperature and Humidity Sensors | *TZ-BT05 Temperature and Humidity Sensors | ||
| − | + | ==FMB Family Bluetooth 4.0 support== | |
| − | |||
| − | == | ||
| − | |||
| − | |||
| − | |||
| − | == | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<br> | <br> | ||
| − | + | 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 older version installed. Date shown in 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 | ||
<br> | <br> | ||
<table class="nd-othertables" style="width: 40%;"> | <table class="nd-othertables" style="width: 40%;"> | ||
| Line 254: | Line 172: | ||
<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> | <tr> | ||
| − | <td style="vertical-align:middle"> | + | <td style="vertical-align:middle">FMB010 </td> |
| − | <td | + | <td>2018.04</td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
| − | <td style="vertical-align:middle"> | + | <td style="vertical-align:middle">FMB001</td> |
<td style="vertical-align:middle">2018.04</td> | <td style="vertical-align:middle">2018.04</td> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 287: | Line 193: | ||
<td style="vertical-align:middle">2019.07</td> | <td style="vertical-align:middle">2019.07</td> | ||
</tr> | </tr> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<tr> | <tr> | ||
| Line 305: | Line 206: | ||
<td style="vertical-align:middle">FMB125</td> | <td style="vertical-align:middle">FMB125</td> | ||
<td>2017.11</td> | <td>2017.11</td> | ||
| + | </tr> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
</table> | </table> | ||
Revision as of 12:57, 7 January 2020
Bluetooth 4.0 settings
FMB1YX offers Bluetooth 4.0 (Bluetooth Low Energy, also referred as BLE) functionality. User is able to discover nearby BLE devices and their services. Another feature is TZ-BT04/05 sensor support. Sensors provide data about temperature (TZ-BT04 and TZ-BT05) and humidity (TZ-BT04 only).
Configurable parameters:
- Non Stop Scan - Enabled Non Stop Scan feature, device will try to scan for the sensors all the time if any of them are configured.
- TZ-BT04/05/05B Update frequency – changes sensor's temperature/humidity/battery voltage data update frequency.
Minimum value: 120 s, maximum value: 65535 s, default value: 120. - BLE Scan Duration - Sensors data reading time.
- Scan retries until error - Configured scan retries, to show the Error Value '3000' - sensor disconnected.
- 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.
Few Examples of the Configured Values:
Non Stop Scan Enabled.
In configurator when nonstop sensor scan is active update frequency & scan retries until error will be hidden. Although BLE scan duration will still be active because it is important for btgetlist SMS command.
Non Stop Scan Disabled, Scan period is selected manually.
From the picture above, the Scan time period will be selected from two sources, BLE Scan Duration - the time when sensors is scanned and the Update frequency - The time when the sensors information is packet as the AVL Data record.
For example.
Update frequency - 120 seconds.
BLE Scan Duration - 60 Seconds
Device first scan the sensors for the 60 seconds, after this time, the device will pack the remaining records to the AVL data package. Total sensors information update time will be 120 seconds.
Advanced Mode
When Advanced mode is selected a table with configurable parameters will appear:
- 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.
- Data Offset – start index of data we are interested in.
- Data Size – size of 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 elements 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.
- 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.
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
Devices which are listed with the BT 4.0 supportive, have the extended List of the BLE Sensors which are available as the Preset settings and was fully tested from our end with the supportive.
While following the steps showed in the images below, you can find the supported sensors in our configurator.
After the Showed Presets Button was pressed, the following window should appear.
The supportive sensors are listed below:
- 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
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 older version installed. Date shown in table depends on when hardware production has started, but not when first lot was sold.
| Device Model | BT 4.0 manufacture starting date |
|---|---|
| FMB010 | 2018.04 |
| FMB001 | 2018.04 |
| FMB900 | 2018.08 |
| FMB920 | 2018.07 |
| FMB964 | 2019.07 |
| FMB120 | 2018.01 |
| FMB122 | 2017.11 |
| FMB125 | 2017.11 |
