This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Is there any method to hide advertise packet from nRF52 in the nRF Connect utils?

We want to use some device in the peripherial mode.

after the devices were bonded, for next connect I need to hide this advertise packet from air in the nRF Connect util. Is it possible?

I can hide name- works. 

Also I tryed (after has bonded) change 

BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE

to

BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE

At this case, there is no any device in the nRF connect but also can't connect to bonded device.

Parents
  • I'm a absolute beginner, but maybe I can still give you some advice based on what I found on this forum:

    Basically all advertisements are visible to all scanners. But the scanners can assume that:

    • if the Limited discoverable mode is used the device will only advertise for a limited amount of time. e.g. the user has put the device in bondable mode or some other time limited mode.
    • If a scanner sees a "non discoverable" advertisement it can assume this device uses a whitelist or for some other reason is not connectable. So it can save power by not trying to connect.
    • But I'm afraid the behavior will depend on the implementation, as it's up to the developer to use these flags correctly. Unless you are implementing a sig define profile with given requirements for flags.
Reply
  • I'm a absolute beginner, but maybe I can still give you some advice based on what I found on this forum:

    Basically all advertisements are visible to all scanners. But the scanners can assume that:

    • if the Limited discoverable mode is used the device will only advertise for a limited amount of time. e.g. the user has put the device in bondable mode or some other time limited mode.
    • If a scanner sees a "non discoverable" advertisement it can assume this device uses a whitelist or for some other reason is not connectable. So it can save power by not trying to connect.
    • But I'm afraid the behavior will depend on the implementation, as it's up to the developer to use these flags correctly. Unless you are implementing a sig define profile with given requirements for flags.
Children
Related