Disconnection 0x3b in Master Control Panel APP

RE: Disconnection 0x3b in Master Control Panel APP

Stefan Birnir Sverrisson — Fri, 22 Apr 2016 09:57:47 GMT

If you are not getting a disconnect after commenting out the conn_params_init() function, then you surely know that this is a connection parameter negotiation problem of some sort. Please check this thread in order to realize how the connection parameter update procedure works, then check the things I have already mentioned in my answer.

RE: Disconnection 0x3b in Master Control Panel APP

Thangaraj — Thu, 21 Apr 2016 04:42:02 GMT

Hi Stefan, Thanks for your reply. I just commented one function after that disconnect was not happening , But am not sure how this solve the issue .

       device_manager_init(true);
     //conn_params_init(); -> This function I commented to make it work 
       gap_params_init();
       services_init();
       advertising_init();

Please let me know what change this will give and is it a proper fix?

RE: Disconnection 0x3b in Master Control Panel APP

Stefan Birnir Sverrisson — Wed, 20 Apr 2016 13:42:55 GMT

These connection parameter settings seem to be pretty normal. Letting the central device choose connection parameters between 20ms and 75ms should be fine.

In the sniffer trace, what is the connection interval that the central device (phone) is proposing? If it is not between 20ms and 75ms, the default procedure of the nRF51 (the ble_conn_params library in the nRF5 SDK) is to reject the proposed parameters from the central and disconnect (see conn_params_negotiation function). See also here how to see the actual connection interval proposed by the central (1) (2)

Update 20.4.2016 There are apparently also a few Android phones behaving badly, see this thread