• State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 62 subscribers
  • Views 4468 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

    This example has pretty complex functionality as it bonds with the peer and establishes security (from what I see). Isn't it so that you've connected these two boards/FWs together once and then scanner/central looks for its peer only? I see there is whitelist used at some point which would explain that it sees only particular peer (running sensor example). If you re-flash the board, do you see different adv. reports? Have you added some NRF_LOG_xxx right after case BLE_GAP_EVT_ADV_REPORT: ? Because if not then you won't see all reports on UART, there are logging functions only for these which matches one of conditions (specific hardcoded Adv. address, Device Name or Service UUID in Adv. data...)

Reply
  • 0 in reply to endnode

    This example has pretty complex functionality as it bonds with the peer and establishes security (from what I see). Isn't it so that you've connected these two boards/FWs together once and then scanner/central looks for its peer only? I see there is whitelist used at some point which would explain that it sees only particular peer (running sensor example). If you re-flash the board, do you see different adv. reports? Have you added some NRF_LOG_xxx right after case BLE_GAP_EVT_ADV_REPORT: ? Because if not then you won't see all reports on UART, there are logging functions only for these which matches one of conditions (specific hardcoded Adv. address, Device Name or Service UUID in Adv. data...)

Children
No Data
Related