![]() |
nRF Connect SDK API 3.3.99
|
| void(* bt_fast_pair_fhn_pf_ranging_mgmt_cb::ranging_config_request) (struct bt_conn *conn, uint16_t ranging_tech_bm, struct bt_fast_pair_fhn_pf_ranging_tech_payload *config_payloads, uint8_t config_payload_num) |
Ranging Configuration Request received.
This callback is mandatory. It is called when a Ranging Configuration message is received by the application from the connected peer. The application must configure the requested ranging technologies according to the provided technology-specific configuration payloads, start the ranging sessions and then respond using the bt_fast_pair_fhn_pf_ranging_config_response_send API. The response can be sent asynchronously if the configuration and starting of certain ranging technologies requires time to complete.
The config_payloads array contains the technology-specific configuration data for each ranging technology that must be configured and started. The config_payload_num parameter indicates the number of elements in the config_payloads array. The config_payloads array is only valid during the callback execution.
This callback is executed in the cooperative thread context. You can learn about the exact thread context by analyzing the
CONFIG_BT_RECV_CONTEXT
Kconfig option. By default, this callback is executed in the Bluetooth-specific workqueue thread (
CONFIG_BT_RECV_WORKQ_BT
).
| conn | Connection object. |
| ranging_tech_bm | Bitmask of the ranging technologies to configure and start, composed of bt_fast_pair_fhn_pf_ranging_tech_id bit positions. |
| config_payloads | Array of technology-specific configuration payloads. |
| config_payload_num | Number of elements in the config_payloads array. |