Why the le_param_req() callback is never called again (zephyr) with example peripheral BLE

RE: Why the le_param_req() callback is never called again (zephyr) with example peripheral BLE

Dinh Son — Tue, 21 Nov 2023 03:17:38 GMT

Thank you for providing the solution and I have solved this problem

RE: Why the le_param_req() callback is never called again (zephyr) with example peripheral BLE

Vidar Berg — Mon, 20 Nov 2023 10:52:50 GMT

The callback will only be invoked when the central issues a connection parameter update *request*, and not when it just updates the connection parameters without asking the peripheral first through the 'connection update procedure' (Ref. Bluetooth core spec, Vol. 6, Part B, section 5.1.1).

RE: Why the le_param_req() callback is never called again (zephyr) with example peripheral BLE

Dinh Son — Fri, 17 Nov 2023 12:43:41 GMT

Thank you for responding
I tried using the phone with the nRF Connect mobile app to connect to the peripheral and only request the connection priority when the le_param_updated() function is called again, while the callback function le_param_req() is never called again. I am using sdk 2.4.2.

Here is my code

My peripheral terminal is displayed like this

This is the app I used on my phone

Best regards!

RE: Why the le_param_req() callback is never called again (zephyr) with example peripheral BLE

Vidar Berg — Fri, 17 Nov 2023 12:04:52 GMT

Hi,

Are you sure the central has sent a connection parameter update when you expect to receive the le_param_req() callback? You can confirm this by capturing a sniffer trace with the nRF sniffer (https://www.nordicsemi.com/Products/Development-tools/nrf-sniffer-for-bluetooth-le)

Best regards,

Vidar