RemoteUserTerminatedConnection reason causes disconnection between central and peripheral

RE: RemoteUserTerminatedConnection reason causes disconnection between central and peripheral

Ole Morten — Tue, 11 Mar 2014 10:23:26 GMT

Great that you got it working! To better understand connection interval, you may have use in taking a look at these questions: https://devzone.nordicsemi.com/index.php/how-do-i-calculate-throughput-for-a-ble-link https://devzone.nordicsemi.com/index.php/what-is-connection-parameters https://devzone.nordicsemi.com/index.php/discussions/how-to-minimize-current-consumption-for-ble-application-on-nrf51822

Finally, if you found my reply helpful, I'd appreciate it if you could accept it as an answer, by clicking the button below it, to clear up this question! :-)

RE: RemoteUserTerminatedConnection reason causes disconnection between central and peripheral

John Vourvoulakis — Tue, 11 Mar 2014 07:31:18 GMT

Ole, thank you for your reply. Problem is solved. It seems it was the connection interval. The peripheral was configured to have 500ms connection interval and when I changed to 20ms it did not disconnected any more. I am not sure if this is the best solution since I do not know how it affects the power consumption but it is acceptable at the moment. As you can see I try to figure out fundamental things and procedures on BLE and example code. Thanks once more. John

RE: RemoteUserTerminatedConnection reason causes disconnection between central and peripheral

Ole Morten — Mon, 10 Mar 2014 13:30:56 GMT

If it weren't for the disconnect reason, I'd guess that this disconnect happened due to connection parameters negotiation failing, but this should give the reason BLE_HCI_CONN_INTERVAL_UNACCEPTABLE. This would explain the different behavior of the MCP (which connects with 20 ms by default, but accepts any update request), HealthThermoDemo (which connects with 20 ms, and does not accept any updates) and your custom app (which most likely connects with some other interval, and may not accept updates). To accept updates, you must set a handler for the ConnectionUpdateRequest event on the MasterEmulator object, and reply by calling UpdateConnectionParameters.

The reason you see is what would be expected if the Peripheral device disconnects the link voluntarily, typically by calling sd_ble_gap_disconnect() with this particular error code as a parameter. I would therefore not normally expect to see this unexpectedly, unless there is some code path in which your application does this.

If you can't solve this problem, could you please supply the complete code of your project? If you can't share it here in the open, feel free to create a support case and submit it there. Any code shared there will be handled in confidentiality.