MULTIPLE CONNECT BUG!!!

[strengthstrong]

Because 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 used three dk boards to test one as the master and one as the slave. As a result, the two slaves connected after the flash are sometimes very smooth, but when you run them several times, you will find that there are many Times connect->disconnect(error 0x3e) , I don't know what the situation is, ask for help, because I also encountered a similar situation

[Susheel Nuguru]

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. 

Disconnect reason 0x3E, 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)

[strengthstrong]

i find this  ， what is the  matter？

[strengthstrong]

[Susheel Nuguru]

it is Frame Check Sequence error, which is done by your sniffer (i think). Please look at this video.

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.