Long range scan with 52840 and SDK16

RE: Long range scan with 52840 and SDK16

Avi — Fri, 20 Mar 2020 21:20:27 GMT

Yes, this solved the problem.

Thank you!

RE: Long range scan with 52840 and SDK16

hmolesworth — Fri, 20 Mar 2020 16:46:46 GMT

In a recent post this tip was useful:

// <o> NRF_BLE_SCAN_BUFFER - Data length for an advertising set. 
#ifndef NRF_BLE_SCAN_BUFFER
#define NRF_BLE_SCAN_BUFFER 31 // Change to BLE_GAP_SCAN_BUFFER_EXTENDED_MIN for coded PHY
#endif

I believe BLE_GAP_SCAN_BUFFER_EXTENDED_MIN is 255

See scanning-and-advertising-parameter-setting-for-coded-in-ble_app_att_mtu_throughput

RE: Long range scan with 52840 and SDK16

Avi — Fri, 20 Mar 2020 10:12:02 GMT

This is what I did. I get resets

RE: Long range scan with 52840 and SDK16

Vidar Berg — Fri, 20 Mar 2020 09:55:55 GMT

Please open the diff in my attachment and review the changes I made. It shouldn't be much different from the ble_app_uart_c example. You don't have to make code changes inside the scan module (nrf_ble_scan.c).

RE: Long range scan with 52840 and SDK16

Avi — Fri, 20 Mar 2020 09:40:46 GMT

I am using the example of ble_app_uart_c (SDK16).

It works as is with BLE4 detection.

I tried to change the following:

p_scan_ctx->scan_params.scan_phys = BLE_GAP_PHY_CODED;
p_scan_ctx->scan_params.extended = 1;

But I get resets.

RE: Long range scan with 52840 and SDK16

Vidar Berg — Fri, 20 Mar 2020 09:00:42 GMT

Hi,

The scan parameters should still be the same. I recently enabled coded PHY for the blinky examples in SDK 16.0.0, maybe you could go over the changes I made and see if you can spot any relevant differences compare to your implementation?

Attachment:

devzone.nordicsemi.com/.../central_5F00_and_5F00_peripheral_5F00_coded_5F00_phy.zip