https://devzone.nordicsemi.com/f/nordic-q-a/22299/ble---nus-data-communication-problemenvironment 1 - nrf51822/SDK 10/SD110/NUS peripheral/device manager use SEC_PARAM_BOND 0 SEC_PARAM_MITM 1 SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_DISPLAY_ONLY SEC_PARAM_OOB 0 SEC_PARAM_MIN_KEY_SIZE 7 SEC_PARAM_MAX_KEY_SIZE 16 en-USTelligent Community 13Wed, 14 Jun 2017 00:09:09 GMThttps://devzone.nordicsemi.com/thread/87670?ContentTypeID=1Wed, 14 Jun 2017 00:09:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:53a1a485-81c9-4903-bba9-1cfda047a973air<p>I will check more about this. Thanks .</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/87671?ContentTypeID=1Wed, 24 May 2017 09:19:10 GMT137ad170-7792-4731-bb38-c0d22fbe4515:574294dc-9d97-460f-9da9-324a9d2830a2Petter Myhre<ol> <li> <p>Why can it not be set?</p> </li> <li> <p>What behavior do you want? Pairing with passkey first, and then deny pairing after that? Then you can call pm_sec_params_set(NULL) after the first pairing.</p> </li> <li> <p>If you can initialize Peer Manager twice? Why would do that?</p> </li> </ol><div style="clear:both;"></div>