Scanning in codded phy

[Alan Ajit]

Dear nordic,

when i try to scan in coded phy some times works but after few minutes it fails to scan(that is not capture beacons). some times it fails from starting(that is from restart) it fails to find coded phy.

 it's totally confusing some times work some times fail. why this happen? i need a immediate reply for this. need some help for resolve this solution

Now just scanning only in coded phy. need some help. Urgently want some reply from your side

[Vidar Berg]

Hi, 

Could it be that scanning is not started in your BLE_GAP_ADV_REPORT handler? Excerpt from the API documentation (link):

A call to this function will require the application to keep the memory pointed by p_adv_report_buffer alive until the buffer is released. The buffer is released when the scanner is stopped or when this function is called with another buffer.The scanner will automatically stop in the following cases:

• sd_ble_gap_scan_stop is called.
• sd_ble_gap_connect is called.
• A BLE_GAP_EVT_TIMEOUT with source set to BLE_GAP_TIMEOUT_SRC_SCAN is received.
• When a BLE_GAP_EVT_ADV_REPORT event is received and ble_gap_adv_report_type_t::status is not set to BLE_GAP_ADV_DATA_STATUS_INCOMPLETE_MORE_DATA. In this case scanning is only paused to let the application access received data. The application must call this function to continue scanning, or call sd_ble_gap_scan_stop to stop scanning.

If a BLE_GAP_EVT_ADV_REPORT event is received with ble_gap_adv_report_type_t::status set to BLE_GAP_ADV_DATA_STATUS_INCOMPLETE_MORE_DATA, the scanner will continue scanning, and the application will receive more reports from this advertising event. The following reports will include the old and new received data.