52842 acting as peripheral, connected to another 52840 acting as central both very closed to each other, transferring data, is disconnecting occasionally. What can be the reason?https://devzone.nordicsemi.com/f/nordic-q-a/40258/52842-acting-as-peripheral-connected-to-another-52840-acting-as-central-both-very-closed-to-each-other-transferring-data-is-disconnecting-occasionally-what-can-be-the-reasonDisconnection of the peripheral is done without enabling another connection, the only way is to reset the module. It happens sometimes after 5 min up to 1-2 hours. If there is an internal error due to data transfer, how can it recover without reseten-USTelligent Community 13Fri, 09 Nov 2018 16:09:57 GMTRE: 52842 acting as peripheral, connected to another 52840 acting as central both very closed to each other, transferring data, is disconnecting occasionally. What can be the reason?https://devzone.nordicsemi.com/thread/156717?ContentTypeID=1Fri, 09 Nov 2018 16:09:57 GMT137ad170-7792-4731-bb38-c0d22fbe4515:711e1961-53e4-4b6f-898d-6442482a9640Marjeris Romero<p>Hi,</p> <p>Could you print the disconnect reason?</p> <p>In ble_evt_handler, you could do something like this:</p> <p><pre class="ui-code" data-mode="text"> case BLE_GAP_EVT_DISCONNECTED: NRF_LOG_INFO(&quot;Disconnected reason: %d.&quot;,p_ble_evt-&gt;evt.gap_evt.params.disconnected.reason);</pre></p> <p></p> <p>Also note that a reset indicates that you are running into the error handler, where the default behavior is to do a reset. You should then debug in order to find the reason for the reset. See this post about debugging: <a href="https://devzone.nordicsemi.com/f/nordic-q-a/10729/my-device-is-freezing-and-restarting">https://devzone.nordicsemi.com/f/nordic-q-a/10729/my-device-is-freezing-and-restarting</a></p> <p>If you are using SES IDE, then make sure to use the Debug configuration and not the Release configuration.</p> <p>Regards,</p> <p>Marjeris</p><div style="clear:both;"></div>