Disconnected when connected with LESC

[m-o]

Hello All

Please tell me about nRF Connect (iOS).

When the module and nRF Connect (Ver 2.0.1) are connected using LESC, they will be disconnected after bonding is completed.

Previous versions (before Ver 1.8.8) could connect.
Data can be sent and received when connected again.
I received BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION (0x13) when debugging the module.

Do I need to change the module connection sequence?
Will nRF Connect be correction?

【environment】
iPad pro
nRF Connect: 2.0.1

Thanks.

[Vidar Berg]

Hello,

I haven't had this problem with my iPhone. But the PM manager will reject new pairing requests from an already bonded peer device unless you've configured it to allow repairing. Could this maybe explain the problem you see? I.e., the bond was deleted on your iPhone at some point, but not on the peripheral, so the iPhone now tries to repair every time you re-connect but keeps getting rejected by the FW because the bond already exists? If you are unsure about this, please erase the chip and re-program it to ensure all bonding info is erased, then try to re-connect and see if you get the same problem.   

[m-o]

Tank you for your answer.

I understand that there is a problem if bonding information remains in either.
Although it was disconnected, bonding is completed.
If you connect again after being disconnected, you can connect and send / receive data without displaying the "Pairing Request" screen.

Both ipad and module delete bonding information.
The module was written from the state where FLASH was erased.
The module application software is based on the following SDK.

"nRF Connect for desk top" connects without problems.

【environment】
[module]
nRF51822: SDK12.3
nRF52840: SDK15.2

[ipad pro]
iOS: 12.2
nRF Connect:2.0.1

[Vidar Berg]

Thanks for confirming that it's not related to an aborted pairing procedure. I'm now seeing a similar issue with nRF connect v2.0.2, the app seems to disconnect after the bonding is complete, but only for the initial connection, subsequent connections do not get disconnected. I'll investigate it further.   

[m-o]

Thank you very much.

[Vidar Berg]

I don't see the disconnect when using the nRF toolbox app so it appears that it is the nRF connect app that causes the disconnect. I have reported this internally.