SCAN_REQ and SCAN_RSP logging

[Felipe1]

Hello, I have a question about the scan request event.

I checked the logs of BLE_GAP_EVT_SCAN_REQ_REPORT.  If this event is received, does Softdevice recognize the packet as SCAN_REQ properly and surely send back SCAN_RSP?  If there are any problems in receiving a SCAN_REQ packet (e.g. CRC error), can I see any logs/messages?  Or if there are any problems in sending a SCAN_RSP packet, can I see any logs/messages as well?

I am looking for any tools/methods to make sure the scan response procedure works in the software level.

[Environment]

nRF52832 custom board

nRF5 SDK 17.1.0

Softdevice S132 v7.0.1, 7.2.0, 7.3.0

Sample source code : ble_peripheral\ble_app_blinky

 

[Modification]

I added the following lines in main.c and built a debug module.  The log messages are seen.

// In advertising_init

    adv_params.scan_req_notification  = 1;

 // In ble_evt_handler

         case BLE_GAP_EVT_SCAN_REQ_REPORT:

            NRF_LOG_INFO("SCAN_REQ");

            break;

[Vidar Berg]

Hello,

If this event is received, does Softdevice recognize the packet as SCAN_REQ properly and surely send back SCAN_RSP?

Yes, that is correct.

If there are any problems in receiving a SCAN_REQ packet (e.g. CRC error), can I see any logs/messages?

You will only receive the event if the scan request was received properly. The same goes for any other BLE packet. Packets with CRC errors are not processed by the stack.

Or if there are any problems in sending a SCAN_RSP packet, can I see any logs/messages as well?

A scan response packet will not be acknowledged by the scanner, so there is no way for the advertiser to know if the response was received or not. In other words, if the scanner failed to receive the scan response, then it will have to send new SCAN_REQ.

Best regards,

Vidar