Changes

42 bytes added , 15:23, 28 December 2023

m

Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

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.

Example for formatting:

Line 12: Line 12:

[[Image:FMB BT NAME.png|{{{general|size}}}|right]]

−

General functionality configures ~~Bluetooth~~ to work in slave mode. This mode allows any external device to connect to {{{model|FMC800}}}. 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|FMC800}}}. 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|FMC800}}}, 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|FMC800}}}, 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|FMC800}}}.

+

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

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|FMC800}}} device. There are two different parameters:

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

−

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

+

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

−

The {{{model|FMC800}}} 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|FMC800}}} 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 29: Line 29:

Example:

If the configured Local Name parameter is "FMC_800_%imei7" and the IMEI of the device is 352093089520901, name will be displayed as FMC_800_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 FMC_800_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 38: Line 38:

|-

| 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|FMC800}}} ~~Bluetooth~~ has several different ''Security Modes'':

+

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

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

Line 56: Line 56:

*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]] – FMC800 starts searching for an external hands free headset or OBD II Dongle. If {{{model|FMC800}}} finds a device which matches user defined ''External MAC'' or ''External Name'' then FMC800 will try to pair with that external device. If the external device asks for PIN then {{{model|FMC800}}} will send user defined ''External PIN''. After successfully pairing {{{model|FMC800}}} 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]] – FMC800 starts searching for an external hands free headset or OBD II Dongle. If {{{model|FMC800}}} finds a device which matches user defined ''External MAC'' or ''External Name'' then FMC800 will try to pair with that external device. If the external device asks for PIN then {{{model|FMC800}}} will send user defined ''External PIN''. After successfully pairing {{{model|FMC800}}} 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|FMC800}}} 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|FMC800}}} 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.

*User ID - This mode makes {{{model|FMC800}}} 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 69: Line 69:

|}

−

''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 "~~BluetoothDevice~~" and user enters "~~Bluetooth~~" in ''External Name'' parameter window, then {{{model|FMC800}}} will be allowed to connect to an external device named "~~BluetoothDevice~~".

+

''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 "Bluetooth®Device" and user enters "Bluetooth®" in ''External Name'' parameter window, then {{{model|FMC800}}} will be allowed to connect to an external device named "Bluetooth®Device".

−

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

+

===Bluetooth® solutions===

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

Arnas.Zeb

Administrators

5,131

edits

Changes

FMC800 Bluetooth settings (view source)

Revision as of 15:23, 28 December 2023