0
edits
Changes
Template:FMB Blue-tooth 4.0 settings (view source)
Revision as of 17:16, 12 December 2019
, 17:16, 12 December 2019BT advanced mode screenshot and description of each parameter. BLE sensors IO elements AVL IDs
[[File:Blue-tooth 4.0v2 settings.PNG|thumb|left]]
[[File:Blue-tooth 4.0v2 settings.PNG|thumb|left]]
Configurable parameters:<br/>
Configurable parameters:<br />
* '''''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.
* '''''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.
*'''''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.
<br>
*'''''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''.'' <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br>When Advanced mode is selected a table with configurable parameters will appear:
<br>
*[[File:BLE advanced window.png|none|thumb|795x795px]]<br />
<br>
*The table has 9 types of parameters:
<br>
*# 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.
<br>
*# Data Offset – start index of data we are interested in.
<br>
*# Data Size – size of data we are interested in.
<br>
*# 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.
<br>
*# 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.'''
<br>
*# Match – hex string to be matched with BLE sensor data. '''Used only with Match action.'''
<br>
*# Endianness – endianness of data: little endian (ex. 0x1122) or big endian (ex. 0x2211). '''Used only with Save action.'''
<br>
*# Multiplier – value to be used to multiply output data. '''Used only with Save action.'''
<br>
*# Offset – value to be added to output data. '''Used only with Save action.''' <br />
<br>
<br>
== IO elements choices ==
<br>
{| class="wikitable"
<br>
|Name
<br>
|Connection #1 AVL ID
<br>
|Connection #2 AVL ID
<br>
|Connection #3 AVL ID
<br>
|Connection #4 AVL ID
== FMB Family Bluetooth 4.0 support ==
|-
|None
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|-
|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
|}
==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 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.
<td style="vertical-align:middle">FMB964</td>
<td style="vertical-align:middle">FMB964</td>
<td style="vertical-align:middle">2019.07</td>
<td style="vertical-align:middle">2019.07</td>
</tr>
</tr>
<tr>
<tr>
<td>2017.11</td>
<td>2017.11</td>
</tr>
</tr>
</table>
</table>
<br>
<br>
