https://devzone.nordicsemi.com/f/nordic-q-a/75877/unable-to-scan-all-ble-devices-which-is-advertising-the-dataHello, I want to scan all ble devices present near by nrf52-dk and process the data in my application. I am unable to find the scanning ble device code in nrf52 sdk. I am absolutely new in nrf development. Please give some idea.en-USTelligent Community 13Mon, 07 Jun 2021 10:30:46 GMThttps://devzone.nordicsemi.com/thread/313882?ContentTypeID=1Mon, 07 Jun 2021 10:30:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5602a379-7451-482d-8449-98857c239496Rohan Sharma<p>In main.c, i have found the function scan_start(). This function is being called and right after the scan_start(), i expect the scan data(UUID, data, rssi, tx_value).</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/313874?ContentTypeID=1Mon, 07 Jun 2021 10:05:30 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f3d91c34-6c8d-46fb-bfb8-e1096d931b38Kenneth<p>Did you call&nbsp;<span>sd_ble_gap_rssi_start()?</span></p> <p><span>Kenneth</span></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/313775?ContentTypeID=1Sat, 05 Jun 2021 15:31:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:15bcad8a-2c63-4c4c-97cb-c4f1d82fc5f4Rohan Sharma<p>Thanks for reply. Just, I have tried. I have initialized &quot;ble_gap_evt_adv_report_t <span>ble_gap_evt_adv_report_temp_var</span>&quot; in main.c and printing the rssi value in &quot;ble_evt_handler&quot; function by &quot;NRF_LOG_INFO(&quot;%d&quot;,<span>ble_gap_evt_adv_report_temp_var.rssi</span>)&quot;. Output is 0 . Can you please help me in detail what exactly, i have to do?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/313193?ContentTypeID=1Wed, 02 Jun 2021 16:22:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2b7733ce-da0a-47d2-972a-9c8b4e545df3Kenneth<p>A good starting point would be a BLE central example, for instance the ble_app_blinky_c in the nRF5 SDK.</p> <p>What you are looking for is handling of the&nbsp;BLE_GAP_EVT_ADV_REPORT event, this is typically handled by the nrf_ble_scan.c module. However you may&nbsp;also&nbsp;add it to your&nbsp;ble_evt_handler() in main.c and extract whatever information you want.&nbsp;</p> <p><pre class="ui-code" data-mode="text">/**@brief Event structure for @ref BLE_GAP_EVT_ADV_REPORT. * * @note If @ref ble_gap_adv_report_type_t::status is set to @ref BLE_GAP_ADV_DATA_STATUS_INCOMPLETE_MORE_DATA, * not all fields in the advertising report may be available. * * @note When ble_gap_adv_report_type_t::status is not set to @ref BLE_GAP_ADV_DATA_STATUS_INCOMPLETE_MORE_DATA, * scanning will be paused. To continue scanning, call @ref sd_ble_gap_scan_start. */ typedef struct { ble_gap_adv_report_type_t type; /**&lt; Advertising report type. See @ref ble_gap_adv_report_type_t. */ ble_gap_addr_t peer_addr; /**&lt; Bluetooth address of the peer device. If the peer_addr is resolved: @ref ble_gap_addr_t::addr_id_peer is set to 1 and the address is the peer&#39;s identity address. */ ble_gap_addr_t direct_addr; /**&lt; Contains the target address of the advertising event if @ref ble_gap_adv_report_type_t::directed is set to 1. If the SoftDevice was able to resolve the address, @ref ble_gap_addr_t::addr_id_peer is set to 1 and the direct_addr contains the local identity address. If the target address of the advertising event is @ref BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE, and the SoftDevice was unable to resolve it, the application may try to resolve this address to find out if the advertising event was directed to us. */ uint8_t primary_phy; /**&lt; Indicates the PHY on which the primary advertising packet was received. See @ref BLE_GAP_PHYS. */ uint8_t secondary_phy; /**&lt; Indicates the PHY on which the secondary advertising packet was received. See @ref BLE_GAP_PHYS. This field is set to @ref BLE_GAP_PHY_NOT_SET if no packets were received on a secondary advertising channel. */ int8_t tx_power; /**&lt; TX Power reported by the advertiser in the last packet header received. This field is set to @ref BLE_GAP_POWER_LEVEL_INVALID if the last received packet did not contain the Tx Power field. @note TX Power is only included in extended advertising packets. */ int8_t rssi; /**&lt; Received Signal Strength Indication in dBm of the last packet received. @note ERRATA-153 and ERRATA-225 require the rssi sample to be compensated based on a temperature measurement. */ uint8_t ch_index; /**&lt; Channel Index on which the last advertising packet is received (0-39). */ uint8_t set_id; /**&lt; Set ID of the received advertising data. Set ID is not present if set to @ref BLE_GAP_ADV_REPORT_SET_ID_NOT_AVAILABLE. */ uint16_t data_id:12; /**&lt; The advertising data ID of the received advertising data. Data ID is not present if @ref ble_gap_evt_adv_report_t::set_id is set to @ref BLE_GAP_ADV_REPORT_SET_ID_NOT_AVAILABLE. */ ble_data_t data; /**&lt; Received advertising or scan response data. If @ref ble_gap_adv_report_type_t::status is not set to @ref BLE_GAP_ADV_DATA_STATUS_INCOMPLETE_MORE_DATA, the data buffer provided in @ref sd_ble_gap_scan_start is now released. */ ble_gap_aux_pointer_t aux_pointer; /**&lt; The offset and PHY of the next advertising packet in this extended advertising event. @note This field is only set if @ref ble_gap_adv_report_type_t::status is set to @ref BLE_GAP_ADV_DATA_STATUS_INCOMPLETE_MORE_DATA. */ } ble_gap_evt_adv_report_t;</pre></p> <p><span>Kenneth</span></p><div style="clear:both;"></div>