Bluetooth LE scanning module
The nRF Desktop’s Bluetooth® LE scanning module is based on the nRF Connect SDK’s Scanning module.
Use the Bluetooth LE scanning module for the following purposes:
Apply scanning filters.
Control the Bluetooth scanning.
Initiate the Bluetooth connections.
This module can only be used by an nRF Desktop central.
See the Overview: Firmware architecture for more information about the event-based communication in the nRF Desktop application and about how to read this table.
Complete the following steps to enable the Bluetooth LE scanning module:
Complete the basic Bluetooth configuration, as described in the Bluetooth in nRF Desktop documentation. Make sure that both CONFIG_DESKTOP_ROLE_HID_DONGLE and CONFIG_DESKTOP_BT_CENTRAL options are enabled. The Bluetooth LE scanning module is enabled by the CONFIG_DESKTOP_BLE_SCAN_ENABLE Kconfig option which is implied by CONFIG_DESKTOP_BT_CENTRAL Kconfig option together with other application modules. These modules that are required for HID dongle that forwards the data from HID peripherals connected over Bluetooth.
Make sure that the number of scan filters based on the Bluetooth address (
CONFIG_BT_SCAN_ADDRESS_CNT) is equal to the number of Bluetooth bonds. The number of Bluetooth bonds is defined by the
CONFIG_BT_MAX_PAIREDKconfig option. The Bluetooth LE scanning module uses the Bluetooth address filters to look for bonded peripherals.
Make sure that the number of scan filters based on the Bluetooth name (
CONFIG_BT_SCAN_NAME_CNT) is equal to the number of peripheral types the nRF Desktop central connects to. The Bluetooth LE scanning module uses Bluetooth name filters to look for unbonded peripherals. The peripheral type may be either a mouse or a keyboard.
If you want to limit the number of attempts to connect to a device, you can use the connection attempt filter (
CONFIG_BT_SCAN_CONN_ATTEMPTS_FILTER). The Kconfig option is enabled by default. After the predefined number of disconnections or connection failures, the nRF Desktop central will no longer try to connect with the given peripheral device. This is done to prevent connecting and disconnecting with a peripheral in a never-ending loop.
You can further configure this setting with the following Kconfig options:
CONFIG_BT_SCAN_CONN_ATTEMPTS_FILTER_LEN- This option defines the maximum number of filtered devices.
CONFIG_BT_SCAN_CONN_ATTEMPTS_COUNT- This option defines the connection attempt count for a given peripheral.
The Scanning module counts all disconnections for a peripheral. The Bluetooth LE scanning module uses
bt_scan_conn_attempts_filter_clear()to clear all the connection attempt counters on the following occasions:
After a successful peripheral discovery takes place (on
When you request scan start or peer erase.
If filters are not cleared by the application, the Bluetooth Central will be unable to reconnect to the peripheral after exceeding the maximum connection attempts.
Configure the maximum number of bonded mice (CONFIG_DESKTOP_BLE_SCAN_MOUSE_LIMIT) and keyboards (CONFIG_DESKTOP_BLE_SCAN_KEYBOARD_LIMIT) for the nRF Desktop central. By default, the nRF Desktop central connects and bonds with only one mouse and one keyboard.
Define the Bluetooth name filters in the
ble_scan_def.hfile that is located in the board-specific directory in the application configuration directory. You must define a Bluetooth name filter for every peripheral type the nRF Desktop central connects to. For an example, see
The Bluetooth device name for given peripheral is defined as the
CONFIG_BT_DEVICE_NAMEKconfig option in the peripheral’s configuration. For more detailed information about the Bluetooth advertising configuration in the nRF Desktop application, see the Bluetooth LE advertising module documentation.
Set the CONFIG_DESKTOP_BLE_SCAN_PM_EVENTS to block scanning in the power down mode to decrease the power consumption. The Kconfig option is enabled by default.
By default, the nRF Desktop central always looks for both bonded and unbonded peripherals.
You can set the CONFIG_DESKTOP_BLE_NEW_PEER_SCAN_REQUEST option to make the device look for unbonded peripherals only on user request.
The request is submitted by Bluetooth LE bond module as
ble_peer_operation_event.op set to
The central always looks for new bonds also after the bond erase (on
ble_peer_operation_event.op set to
If CONFIG_DESKTOP_BLE_NEW_PEER_SCAN_REQUEST is enabled, you can also set the CONFIG_DESKTOP_BLE_NEW_PEER_SCAN_ON_BOOT option to make the central scan for new peers after every boot.
The following scanning scenarios are possible:
If no peripheral is connected, the central scans for the peripheral devices without interruption.
If a peripheral is connected, the scanning is triggered periodically. If none of the connected peripherals is in use for at least CONFIG_DESKTOP_BLE_SCAN_START_TIMEOUT_S, the scanning is started.
The Bluetooth LE scanning module relies on Scanning module to perform Bluetooth scanning.
The Bluetooth LE scanning module selects
Apart from that the following default values are applied:
The scanning will not start if one of the following conditions occurs:
There are no more free Bluetooth connections.
The Bluetooth LE discovery module is in the process of discovering a peer.
The central is going to scan only for bonded peers and all the bonded peers are already connected.
The central is in the power down mode and CONFIG_DESKTOP_BLE_SCAN_PM_EVENTS is enabled.
The number of Bluetooth connections is defined as the
CONFIG_BT_MAX_CONN Kconfig option.
The scanning is interrupted if one of the following conditions occurs:
A connected peripheral is in use. Scanning in this situation will have a negative impact on user experience.
The maximum scan duration specified by CONFIG_DESKTOP_BLE_SCAN_DURATION_S times out.
The scanning is never interrupted if there is no connected Bluetooth peer. If CONFIG_DESKTOP_BLE_SCAN_PM_EVENTS is enabled, the power down event will also interrupt scanning.
The module supports a dedicated forced scan state that prevents interrupting scanning when a connected peripheral is in use. The forced scan speeds up establishing new connections with peripherals, but it also negatively impacts the performance of already connected peripherals. If the CONFIG_DESKTOP_BLE_FORCED_SCAN_DURATION_S Kconfig option is set to a value greater than zero, the module enters the forced scan state after one of the following conditions is met:
Boot or wakeup
Successful peripheral discovery
After the duration that is specified in the CONFIG_DESKTOP_BLE_FORCED_SCAN_DURATION_S Kconfig option, the module switches to regular scanning. The regular scanning can be interrupted by using connected peripherals and times out after the scan duration specified by CONFIG_DESKTOP_BLE_SCAN_DURATION_S if there are peripherals connected over Bluetooth.
The conditions described under Scanning not started prevent the starting of the forced scan.
The Bluetooth LE scanning module stores the following information for every bonded peer:
Peripheral Bluetooth address.
Peripheral type (mouse or keyboard).
Information about Low Latency Packet Mode (LLPM) support.
The module uses Zephyr’s Settings subsystem to store the information in the non-volatile memory. This information is required to filter out unbonded devices, because the nRF Desktop central connects and bonds only with a defined number of mice and keyboards.
After the scan filter match, the following happens:
The scanning is stopped and the nRF Connect SDK’s Scanning module automatically establishes the Bluetooth connection with the peripheral. The initial Bluetooth connection interval is set by default to 7.5 ms, that is to the shortest connection interval allowed by the Bluetooth specification.
The peer discovery is started.
After the Bluetooth LE discovery module completes the peer discovery, the Bluetooth LE connection parameters module receives the
ble_discovery_complete_eventand updates the Bluetooth connection interval. At this point, the scanning can be restarted.
If the dongle supports Low Latency Packet Mode (
CONFIG_CAF_BLE_USE_LLPM) and more than one Bluetooth connection (
CONFIG_BT_MAX_CONN), a 10-ms connection interval is used instead of 7.5 ms.
This is done to avoid Bluetooth scheduling issues that may lead to HID input report rate drops and disconnections.