https://devzone.nordicsemi.com/f/nordic-q-a/35955/multiple-connect-bugBecause I encountered the same problem, so I needed help. I ran the nordic official example E:\sdk\nRF5_SDK_14.2.0_17b948a\nRF5_SDK_14.2.0_17b948a\examples\ble_central\ble_app_multilink_central The results of this routine surprised me. Is a bug? I useden-USTelligent Community 13Tue, 10 Jul 2018 07:33:25 GMThttps://devzone.nordicsemi.com/thread/139516?ContentTypeID=1Tue, 10 Jul 2018 07:33:25 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2683a5bb-65a6-4efe-a5c3-d0def960c196Susheel Nuguru<p>it is <a href="https://en.wikipedia.org/wiki/Frame_check_sequence">Frame Check Sequence</a> error, which is done by your sniffer (i think).&nbsp;Please look at this <a href="https://www.youtube.com/watch?v=K7ByRmElA5Y">video</a>.</p> <p>Since this is TI sniffer, you need to ask in their forum, how it is calculated and what it means to show a red color.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/139496?ContentTypeID=1Tue, 10 Jul 2018 03:49:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8bdab00f-a3c3-48b1-8f43-379b45af68a3strengthstrong<p><img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/8053.IMFY_5D00_U_7D007D00_D_6000_40_2400250025007B007B00_5BJCHI.png" /></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/139495?ContentTypeID=1Tue, 10 Jul 2018 03:49:16 GMT137ad170-7792-4731-bb38-c0d22fbe4515:aa809de3-11de-40c4-ab53-ee65528c891astrengthstrong<p><img class="align-left" style="float:left;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/_2900_S_5F00_66ZR_2500_3DIX_5F00_12DD_6000_1GE84.png" />i find this&nbsp; ， what is the&nbsp; matter？</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/138439?ContentTypeID=1Mon, 02 Jul 2018 08:01:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:81b7f2fb-c2a6-4915-8a0a-75ce66f3a4b1Susheel Nuguru<p>The central sends a connect request and enters into a connect_request sent state. But if the peer did not respond to this connect request before the supervision timeout then it has to abandon this state and based on your application, starts scanning again.&nbsp;</p> <p><a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v2.0.0%2Fgroup___b_l_e___h_c_i___s_t_a_t_u_s___c_o_d_e_s.html">Disconnect reason 0x3E</a>, most likely happens when the peer device is not responding. Please check why the peer device is not responding to the central connect request (or maybe the peer is asserting after it enters connect request. Either way, you need to debug the peer device)</p><div style="clear:both;"></div>