How can the central (nrf51) force bonding its peripherals?

[nordicdev]

Hi, I have an application where first nrf51 would be the central (remote control) and the second nrf51 would be the peripheral. I got the peripheral to bond with the nRFConnect App (here the nRFConnect App acts as central). How to make the first nrf51 (remote control) to force bonding with the second nrf51 (peripheral) - preferably upon pressing a button in the remote control(which is the first nRF51)? Is there any example code for this(softdevice130v2 and sdk12.3.0)? I have a working example code that does this job -but that is s130v1 and SDK10.0. I cant just copy that over to sdk12.3.0 because device manager is now peer manager, if I understand it right. Thanks.

[Hung Bui]

Hi,

If you have a look at the ble_central\ble_app_hrs_c example in SDK v12.3 you can find in hrs_c_evt_handler() after we have done service discovery and found the heart rate service, we start encryption (bonding) by calling pm_conn_secure().

You can add your code to call pm_conn_secure() when you press the button.

[Hung Bui]

Hi Marco, yes you can skip service discovery if you know the handles. Disadvantage is if your central connect to a wrong peripheral, it will write to stored handles (which is wrong for that peripheral) and may cause unexpected behavior.