This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

immediately Disconnected,reason:0x3e

Hey guys,

I've been troubled by the this 0x3E issue for almost disappointed to Nordic.

I'm working on a CENTRAL,which is going to connect a headphone with to read some information.It is an easy application.

I started from the example ble_app_hrs_c. After I send to CONNECT_REQ, it immediately happened "Disconnected,reason:0x3e".

So I moved to the nRF Connect desktop APP,and it also comes to the same problem.

So

1.What maybe the reason to this BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED?

1.The BLE device is OK,I already tried it on the phone APP (IOS and android). No such problems.

2.Why nRF Connect also cannot handle this issue?It should be a GENERAL tool,right?

Thanks very much.

Parents Reply Children
  • Yes,it happens almost every time.Very ocasionally,it is able to make the connetion.

    Use nRF Connect on the phone is always OK.

    I sniffer the packets and found that after CONNECT_REQ,the central indeed sent other 6 EMPTY PDUs to the headphone,but the headphone doesn't respond.

    From the sniff track,I found that the only difference is WINDOW SIZE and WINDOWS OFFSET,on my central window offset is 0ms ,while the phone APP has 2.5ms windows offser. Does this matter?

  • Hi,

    Can you provide me with which chipset that is used in the peripheral? and which brand and model of the headset?

    Which Nordic-kit are you using? Do you have other nordic-kits you can test with?

    Can you also provide me with which SDK and Softdevice version you are using?

Related