S130 central disconnected immediately after connection to iOS peripheral

[Adam Heinrich]

Dear developers, I am developing a scheme where the nRF51 (central role) connects to iOS device (peripheral roles). The nRF51 connects, performs the discovery procedure and interacts with desired characteristics.

However, this only works for some iOS peers (some phones always work and some don't, even if the model and iOS version is the same). The others seem to refuse the connection immediately after connection, i.e. the nRF51 application code receives event BLE_GAP_EVT_CONNECTED followed by BLE_GAP_EVT_CONNECTED (with reason BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED or 0x3E).

I have already experimented with different configurations of connection parameters (which comply with recent Guidelines by Apple), but it did not help.

Do you have any experience with connecting to iOS devices in peripheral role? Could you please share your experience and configuration?

Thank you,

Adam

[endnode]

Ahoj Adame,

It seems to be working fairly well for me. Do you have RF trace from these failures to analyze what are connection parameters and which peer disconnects (through LL_TERMINATE or through timeout)?

Cheers Jan

[Adam Heinrich]

Ahoj Jane, thank you for the reaction. I'll try to determine which peer terminates the connection. Connection parameters are set by Central (nRF51) and they are always the same.

Adam

[strengthstrong]

Is this solved? I also encountered the same problem and asked for help.

[FormerMember]

Could you check which side of the connection that initiattes the disconnect?

 

If there is a BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED: Could you use the nRF Sniffer to check if the connection really  was established or not?

[strengthstrong]

this is my sniffer , but  i do not know what