• State Verified Answer
  • Replies 1 reply
  • Subscribers 73 subscribers
  • Views 416 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 243333
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

ways to tell peer manager not remembering peer CCCD settings

yf13

I am using nRF SDK v16 with nRF52DK pca10040 board and s112 soft device.

I understand that peer manager can remember each peers' CCCD setting following the bluetooth BLE standard.

My question is can an app choose to let peer manager not to persist such CCCD settings?

Parents
  • +1

    Hi,

    There is a requirement in BLE specification that the CCCD values should be stored for bonded relationships. So you would need to modify the peer manager to break the specification in such case, sounds odd. Maybe you can solve this in another way, e.g. that the application on the peripheral don't transmit notifications until the central have written a value to a characteristic?

    Best regards,
    Kenneth

Reply
  • +1

    Hi,

    There is a requirement in BLE specification that the CCCD values should be stored for bonded relationships. So you would need to modify the peer manager to break the specification in such case, sounds odd. Maybe you can solve this in another way, e.g. that the application on the peripheral don't transmit notifications until the central have written a value to a characteristic?

    Best regards,
    Kenneth

Children
No Data
Related
Terms of service