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

    No, it is called by your BLE stack (Nordic Soft Device) when any relevant event happens. There is no way to find out if adv. device is running from Nordic chip or not (you can put some string into data and claim it as proof but I can take any other BLE chip and fake it, in general no way to tell the difference).

    To ble_app_hrs_c example: what I see in nRF SDK v13.0.0 is that once it starts scanning it gets BLE_GAP_EVT_ADV_REPORT and there it looks for any device which has either specific Adv. address or Device Name AD object in the data or Service UUID in the data. So as long as your peripheral meets one of these criteria ble_app_hrs_c example should find it and connect to it. And if you enable logging on that event you will see Adv. reports from ANY BLE peripheral in the range (again regardless if it is Nordic example running on Nordic chip or anything else...)

Reply
  • 0 in reply to endnode

    No, it is called by your BLE stack (Nordic Soft Device) when any relevant event happens. There is no way to find out if adv. device is running from Nordic chip or not (you can put some string into data and claim it as proof but I can take any other BLE chip and fake it, in general no way to tell the difference).

    To ble_app_hrs_c example: what I see in nRF SDK v13.0.0 is that once it starts scanning it gets BLE_GAP_EVT_ADV_REPORT and there it looks for any device which has either specific Adv. address or Device Name AD object in the data or Service UUID in the data. So as long as your peripheral meets one of these criteria ble_app_hrs_c example should find it and connect to it. And if you enable logging on that event you will see Adv. reports from ANY BLE peripheral in the range (again regardless if it is Nordic example running on Nordic chip or anything else...)

Children
No Data
Related