• State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 85 subscribers
  • Views 6095 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 121232
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Central and a custom peripheral device

Matija Tudan

Hi,

Can the central device (ble_app_hrs_c for example) scan for and connect to a custom peripheral device (not nRF based)?

Parents
  • 0 in reply to endnode

    The FW on a peripheral device doesn't have to be the heart rate example, any other peripheral example will do the same thing. Yes, I've added NRF_LOG_xxx inside of the case BLE_GAP_EVT_ADV_REPORT:, at the beginning of the on_ble_evt() function and inside of the ble_evt_dispatch() function. I see this logs only when the nRF peripheral device is turned on (with any of the peripheral examples), so I assume it has to be something with the SoftDevice? Re-flashing the central FW didn't help.

Reply
  • 0 in reply to endnode

    The FW on a peripheral device doesn't have to be the heart rate example, any other peripheral example will do the same thing. Yes, I've added NRF_LOG_xxx inside of the case BLE_GAP_EVT_ADV_REPORT:, at the beginning of the on_ble_evt() function and inside of the ble_evt_dispatch() function. I see this logs only when the nRF peripheral device is turned on (with any of the peripheral examples), so I assume it has to be something with the SoftDevice? Re-flashing the central FW didn't help.

Children
No Data
Related
Terms of service