Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Fri, 03 Aug 2018 12:21:15 GMT

Please help me, I am very worried

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Wed, 25 Jul 2018 00:54:37 GMT

this is my sniffer

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

Hung Bui — Wed, 11 Jul 2018 07:28:02 GMT

Hi,

Håkon is on vacation, so I will take over this case.

This look more like an hardware issue to me. Which hardware board did you use to test ? Have you got your antenna tuned ? what is the tolerance of your HF crystal and LF crystal ?

You receive 0x3E when the connect request wouldn't reach the peer device (iPhone), could comes from poor antenna design, or poor frequency drifting.

Have you tried to test with the same iPhone but using our nRF5 DK as the central ?

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Tue, 10 Jul 2018 03:45:30 GMT

Why didn't you reply?

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Mon, 09 Jul 2018 06:33:37 GMT

Host discovery service, there are two characteristic that are not available in the slave, I think it has something to do with this, because this is a temporary slave, do you think this is the case?

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Mon, 09 Jul 2018 06:13:35 GMT

i find this , what the matter

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Mon, 09 Jul 2018 06:12:46 GMT

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Mon, 09 Jul 2018 01:26:43 GMT

I think this has nothing to do with the iphone. After all, the nordic routine I used will also have this problem. Although the effect is better than my program, it cannot be ruled out that this is a bug.

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

Håkon Alseth — Fri, 06 Jul 2018 12:00:34 GMT

Hi,

Sorry for the late reply. Do you see the same issue if you use SDK v15 as well?

Unfortunately, I do not have two iphone's available here, but which iphone's specifically are you using?

I would still strongly recommend that you try to capture the BLE traffic using the nRF-sniffer (given that you have a spare kit to use):

https://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer

Kind regards,

Håkon

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Tue, 03 Jul 2018 11:51:24 GMT

But this is not the case, the probability of this situation is very large

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Tue, 03 Jul 2018 11:47:33 GMT

when i use nRF52-DK , do like this. my test

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

Håkon Alseth — Tue, 03 Jul 2018 07:35:45 GMT

Hi,

Is this performed on custom hardware? Have you tried using a nRF52-DK to see if this also behaves like this?

Kind regards,

Håkon

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Tue, 03 Jul 2018 03:15:57 GMT

It really does have a relationship with the distance between the two devices, but I still have occasional 0x3e when the distance between the two devices is close to 0m. When I widen the distance between devices, even <1m range, there are often multiple 0x3e disconnect events. If the reason is attributed to the signal and the distance, I am wondering if the communication quality is too bad. Can I still connect successfully at such a distance?

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Mon, 02 Jul 2018 07:49:20 GMT

I found that the nordic routine also has such a problem. I ran ble_app_uart and ble_app_uarat_c and found that they also had the same problem in the process of connecting. Not every time, the connection is successful. In most cases, the number of connections is greater than 1 is this a bug for nordic ???

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

Håkon Alseth — Mon, 02 Jul 2018 06:51:41 GMT

Hi,

I would recommend that you look into using nRF Sniffer to debug your link. This would make things a lot easier in terms of looking at what the bluetooth link does.

0x3e = BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED. This indicates that the initial connection request was missed by the peripheral. Have you tried reducing the range between devices to see if the issue disappears?

Best regards,

Håkon

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

strengthstrong — Fri, 29 Jun 2018 02:31:43 GMT

I have no way to capture, central and peripheral have mutual binding information, please let me know, this may be due to the possible reason 0x3e may be the reason

RE: Immediately after the connection is established, the connection 0x3e is disconnected. After several connections, the connection is not broken. Occasionally, the connection is disconnected after the connection is established. 0x08

Håkon Alseth — Thu, 28 Jun 2018 11:21:01 GMT

Hi,

When testing, have you removed the device (and it's bond information) from the iPhone? If yes, then you will have to delete the bond on the nRF as well.

Do you have a sniffer trace showing the issue? You can use the nRF-sniffer to capture this.

Best regards,

Håkon