Changes

44 bytes added , 09:42, 27 December 2023

no edit summary

Line 3: Line 3:

==Disclaimer==

−

[[File:Alert.png|left|link=]] If you are not using ~~Bluetooth~~, '''please consider turning it off''' or '''change ~~Bluetooth~~ PIN''' to remove potential risks.

+

[[File:Alert.png|left|link=]] 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.

+

If you are using Bluetooth® we strongly recommend '''using AES encryption''' for enhanced security.

==General functionality==

[[Image:FMB_Blue-tooth_settings.gif|{{{general|size}}}|right]]

−

General functionality configures ~~Bluetooth~~ to work in slave mode. This mode allows any external device to connect to {{{model|FMB1YX}}}. Parameter ''BT Radio'' allows enabling or disabling ~~Bluetooth~~. There are three different settings:

+

General functionality configures Bluetooth® to work in slave mode. This mode allows any external device to connect to {{{model|FMB1YX}}}. Parameter ''BT Radio'' allows enabling or disabling Bluetooth®. There are three different settings:

−

*Disabled – ~~Bluetooth~~ functionality will be disabled.

+

*Disabled – Bluetooth® functionality will be disabled.

−

*Enable (hidden) – ~~Bluetooth~~ functionality will be enabled, external devices will be able to connect to {{{model|FMB1YX}}}, but no devices will be able to detect it.

+

*Enable (hidden) – Bluetooth® functionality will be enabled, external devices will be able to connect to {{{model|FMB1YX}}}, but no devices will be able to detect it.

−

*Enable (visible) – ~~Bluetooth~~ functionality will be enabled and any external device will be able to detect and connect to {{{model|FMB1YX}}}.

+

*Enable (visible) – Bluetooth® functionality will be enabled and any external device will be able to detect and connect to {{{model|FMB1YX}}}.

It is possible to configure the Local name of the device, as well as the Local PIN, which will be used when trying to pair with the {{{model|FMB1YX}}} device. There are two different parameters:

*Local Name parameter lets user declare a visible name of {{{model|FMB1YX}}} to external devices.

−

*Local PIN parameter lets user configure ~~Bluetooth~~ PIN of {{{model|FMB1YX}}} device.

+

*Local PIN parameter lets user configure Bluetooth® PIN of {{{model|FMB1YX}}} device.

−

The {{{model|FMB1YX}}} supports composed ~~Bluetooth~~ Local names, which allows the user to have a predefined number of IMEI digits at the end of the device name. The format of the composed ~~Bluetooth~~ name looks like this:

+

The {{{model|FMB1YX}}} supports composed Bluetooth® Local names, which allows the user to have a predefined number of IMEI digits at the end of the device name. The format of the composed Bluetooth® name looks like this:

<code>Device name + %imeiX</code>

X - how many digits will be taken from IMEI to show in Local name, digits will be taken from the end of IMEI. Minimum value of X is 1 and the Maximum value is 15.

Line 26: Line 26:

Example:

If the configured Local Name parameter is "FMB_120_%imei7" and the IMEI of the device is 352093089520901, name will be displayed as FMB_120_9520901 (whether "_LE" is added at the end depends on whether device supports BLE or not. The full name of the device, which supports BLE would be FMB_120_9520901_LE).

−

If the Local Name is written incorrectly, the ~~Bluetooth~~ name of the device will be broadcasted as it is. An example can be seen below.

+

If the Local Name is written incorrectly, the Bluetooth® name of the device will be broadcasted as it is. An example can be seen below.

Example:

Line 35: Line 35:

|-

| style="text-align: left; background: #F6F6FB;" |[[Image:Bw_nb.png|50px]]

−

| style="text-align: left; background: #F6F6FB;" |The Composed ~~Bluetooth~~ name is supported from 03.25.05 firmware version.

+

| style="text-align: left; background: #F6F6FB;" |The Composed Bluetooth® name is supported from 03.25.05 firmware version.

|}

−

{{{model|FMB1YX}}} ~~Bluetooth~~ has several different ''Security Modes'':

+

{{{model|FMB1YX}}} Bluetooth® has several different ''Security Modes'':

*PIN only – only Local PIN will be reacquired to complete connection to {{{model|FMB1YX}}}.

Line 52: Line 52:

*None – disables auto connection functionality.

−

*[[How to connect ~~Bluetooth~~ Hands Free adapter to FMB device|Hands Free]] or [[How to connect OBD II ~~Bluetooth~~ Dongle to FMB device|OBDII]] – {{{model|FMB1YX}}} starts searching for an external hands free headset or OBD II Dongle. If {{{model|FMB1YX}}} finds a device which matches user defined ''External MAC'' or ''External Name'' then FMB1YX will try to pair with that external device. If the external device asks for PIN then {{{model|FMB1YX}}} will send user defined ''External PIN''. After successfully pairing {{{model|FMB1YX}}} will connect to paired device.

+

*[[How to connect Bluetooth® Hands Free adapter to FMB device|Hands Free]] or [[How to connect OBD II Bluetooth® Dongle to FMB device|OBDII]] – {{{model|FMB1YX}}} starts searching for an external hands free headset or OBD II Dongle. If {{{model|FMB1YX}}} finds a device which matches user defined ''External MAC'' or ''External Name'' then FMB1YX will try to pair with that external device. If the external device asks for PIN then {{{model|FMB1YX}}} will send user defined ''External PIN''. After successfully pairing {{{model|FMB1YX}}} will connect to paired device.

−

*Data Link – BT Data link mode is enabled by Configurator ''Data Link'' parameter: when Data Link is configured and {{{model_2|FMB}}} has a link with the server, paired device can send messages via ~~Bluetooth~~ SPP profile directly to the server. Messages will be encoded by [[Codec#Codec 12|Codec12]].

+

*Data Link – BT Data link mode is enabled by Configurator ''Data Link'' parameter: when Data Link is configured and {{{model_2|FMB}}} has a link with the server, paired device can send messages via Bluetooth® SPP profile directly to the server. Messages will be encoded by [[Codec#Codec 12|Codec12]].

*Inateck Scanner – {{{model|FMB1YX}}} automatically connects to Inateck BT Barcode Scanner BCST-70 and will be ready to receive data (coded in barcode). ''Scanner must be configured for using “ENTER” as suffix.'' {{{model|FMB1YX}}} supports online and inventory mode. A new record will be generated on every data portion received from scanner via SPP. Data will be stored with AVL ID 264, variable data length, max length is 32 bytes. '''''Note:''''' ''Added from FW version 03.16.00.Rev.00+''

*User ID - This mode makes {{{model|FMB1YX}}} connect automatically to a device and stores its BT MAC address in I/O element ''User ID'' (I/O ID: 50520). This is used for driver authentication. If there‘s no connection, the I/O element value is set to 0.

Line 67: Line 67:

''External Name'' parameter works as a substring, which allows user to enter a part of the full external device name. For example, if external device name is "HandsFreeHeadset" and user enters "HandsFree" in ''External Name'' parameter window, then {{{model|FMB1YX}}} will be allowed to connect to an external device named "HandsFreeHeadset".

−

===~~Bluetooth~~ solutions===

+

===Bluetooth® solutions===

−

*[[How to connect ~~Bluetooth~~ Hands Free adapter to FMB device|How to connect ~~Bluetooth~~ Hands Free adapter to {{{model|FMB1YX}}} device]]

+

*[[How to connect Bluetooth® Hands Free adapter to FMB device|How to connect Bluetooth® Hands Free adapter to {{{model|FMB1YX}}} device]]

−

*[[How to connect OBD II ~~Bluetooth~~ Dongle to FMB device|How to connect OBD II ~~Bluetooth~~ Dongle to {{{model|FMB1YX}}} device]]

+

*[[How to connect OBD II Bluetooth® Dongle to FMB device|How to connect OBD II Bluetooth® Dongle to {{{model|FMB1YX}}} device]]

*[[Logging the FMB1YX device using your mobile phone|Logging the {{{model|FMB1YX}}} device using your mobile phone]]

Arnas.Zeb

Administrators

5,131

edits

Changes

Template:FMB Blue-tooth settings (view source)

Revision as of 09:42, 27 December 2023