https://devzone.nordicsemi.com/f/nordic-q-a/23728/s130-connection-offen-breakHi,I use S130 V1.0 working as a master,and connect a device.My device adverting interval is 800ms， and gap_conn_params.min_conn_interval = MIN_CONN_INTERVAL;//MIN_CONN_INTERVAL=500ms , gap_conn_params.max_conn_interval = MAX_CONN_INTERVAL;//MAX_CONN_INTERVALen-USTelligent Community 13Wed, 02 Aug 2017 10:51:29 GMThttps://devzone.nordicsemi.com/thread/93339?ContentTypeID=1Wed, 02 Aug 2017 10:51:29 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c4cb9978-869f-4c04-bbd2-28ff3e9ffea1FormerMember<p>When the central doesn&#39;t receive any notifications, which error code does the peripheral have on its side when it tries to transmit notifications?</p> <p>Note: For the peripheral to be able to transmit notifications, the central will first have to enable notifications by writing to the CCCD in the characteristic in question on the peripheral side.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/93340?ContentTypeID=1Thu, 27 Jul 2017 00:10:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b30e73fd-39da-46df-bab7-4de4e64c0e85Songplus<p>I don&#39;t know, connection param update success,and device server discover success.Some time can receive device notify,but these day central receives nothing.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/93338?ContentTypeID=1Wed, 26 Jul 2017 12:36:15 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c55b0d56-3ad2-4a45-a1f2-3596cabb20acFormerMember<p>If the master/central is calling <code>sd_ble_gap_disconnect()</code> you will need to figure out why it does so, and change that if you want a different behavior.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/93337?ContentTypeID=1Tue, 25 Jul 2017 09:57:53 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3c9f6a3e-e05a-445d-9e26-58133d3f3bcaSongplus<p>It is master <code>sd_ble_gap_diconnect()</code> happen.Device connect to the NRF Connect APP , never happen connect break for a long time connection.I sure that device has not error ,because I have use the device frame in my production for 2 years ,and never happen connection break for app using.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/93336?ContentTypeID=1Tue, 25 Jul 2017 08:56:22 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c63dbdfc-0614-4d96-b943-65ec45770411FormerMember<p>How does the disconnect happen, is it connection supervision timeout, a hardfault, app_error_handler triggering a reset, or is sd_ble_gap_diconnect() explicitly being called? I would recommend you to check both the central and the peripheral side of the link.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/93335?ContentTypeID=1Tue, 25 Jul 2017 00:11:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:151b76ba-4cff-4967-9195-61f701d5c4e8Songplus<p>After connecting,the master keep connecting for receiving the device notify. Device send notify every second,but the master go to disconnect after missing receive some device notify.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/93334?ContentTypeID=1Mon, 24 Jul 2017 12:48:10 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4696e9e4-9ffa-4b53-a6bf-a153318e07a3FormerMember<p>To find you why the connection breaks, you will need to do some debugging: What is the reason for the disconnect? Does any of the devices actively disconnect the link for instance?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/93341?ContentTypeID=1Mon, 24 Jul 2017 10:01:23 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d71d3807-d8bc-4023-a9fd-178c4fcdaa2eSongplus<p>I think the MCU NRF51822 frequency is too low to immediately implement the SD IRQ after the UART IRQ handler.</p><div style="clear:both;"></div>