Get disconnection immediately after sending CONNECT_REQ to an Ammicom BLE module from a centralhttps://devzone.nordicsemi.com/f/nordic-q-a/34294/get-disconnection-immediately-after-sending-connect_req-to-an-ammicom-ble-module-from-a-centralHi, I am designing a central using nRF51422, SDK V11, S130V2.0.0, modifying the central example to connect to a Ammicom BLE module of a product. After the CONNECT_REQ is sent from the central, it is disconnected with the reason 0x1E or 0x3E. Attacheden-USTelligent Community 13Mon, 14 May 2018 12:30:46 GMTRE: Get disconnection immediately after sending CONNECT_REQ to an Ammicom BLE module from a centralhttps://devzone.nordicsemi.com/thread/131869?ContentTypeID=1Mon, 14 May 2018 12:30:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a5edd66d-be7f-4484-a1b2-6008dc5f9bacEinar Thorsrud<p>Hi,</p> <p>The 0x1E disconnect reason is&nbsp;<code>BLE_HCI_STATUS_CODE_INVALID_LMP_PARAMETERS.</code>The peripheral device sends an invalid packet with LLID 0x00 in 0003 nrf3.pcapng (#2283), which is reserved for future use and thus not valid. The SoftDevice will disconnect on invalid peer behavior. This should be fixed in the peer device.</p><div style="clear:both;"></div>