Hi,
Can the central device (ble_app_hrs_c
for example) scan for and connect to a custom peripheral device (not nRF based)?
Hi,
Can the central device (ble_app_hrs_c
for example) scan for and connect to a custom peripheral device (not nRF based)?
Well that's not how the central works in my case. The BLE_GAP_EVT_ADV_REPORT
event happens only when I turn on the nRF peripheral device with the ble_app_hrs
example (or any other peripheral example). With any other BLE peripheral device, even with the matching advertising name, address or UUID, the ble_evt_dispatch()
function never gets called...
Well that's not how the central works in my case. The BLE_GAP_EVT_ADV_REPORT
event happens only when I turn on the nRF peripheral device with the ble_app_hrs
example (or any other peripheral example). With any other BLE peripheral device, even with the matching advertising name, address or UUID, the ble_evt_dispatch()
function never gets called...