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

NRF52 peripheral visibility restriction

Hi,

I'm developing a peripheral sensor and central receiver as a complete set. So I wish the peripheral is only visible(or connectable) to its central device.

I know the central could lock on certain peripheral by address filtering, is there any chances I could achieve it reversely?

Thanks

Parents
  • Hi,

    You can use whitelist on the peripheral to achieve this. Whitelist is used for filtering out which scan requests and connection request it will recieve and process. Only allowing scan requests/connections for those devices whose address is in the whitelist. 

    In order to populate the whitelist, you should either know the address of the central device in advance or establish a connection/bond with the central device. To store a resolvable private address in a whitelist you will need the IRK, which you get as part of the bonding process. For other address types you can put them in the whitelist directly.

    I suggest you take a look at our HID Keyboard example in our SDK, it will give you an idea on how to implement it.

Reply
  • Hi,

    You can use whitelist on the peripheral to achieve this. Whitelist is used for filtering out which scan requests and connection request it will recieve and process. Only allowing scan requests/connections for those devices whose address is in the whitelist. 

    In order to populate the whitelist, you should either know the address of the central device in advance or establish a connection/bond with the central device. To store a resolvable private address in a whitelist you will need the IRK, which you get as part of the bonding process. For other address types you can put them in the whitelist directly.

    I suggest you take a look at our HID Keyboard example in our SDK, it will give you an idea on how to implement it.

Children
Related