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

BLE_HCI_LOCAL_HOST_TERMINATED_CONNECTION

Hi Nordic!

I am using nRF UART2.0 and nRF51822.

I am sending some data from nRF51822 to nRF UART2.0

But after 3 minutes, I can get disconnection.

image description

and 0x16 error is "BLE_HCI_LOCAL_HOST_TERMINATED_CONNECTION"

image description

Plus) I found that when I connect with android, disconnection occur after 3 minutes,

and when I connect with iOS, disconnection occurs after 90 seconds.

For unlimited connection, what should i change??

  • Hi

    Are you following the guidelines for connection parameters for those platforms? See this document section 3.6 for IOS guidelines.

    Update 23.10.2014 According to the above you can select connection interval as low as 20ms, and you can notify up to 6 packets in each connection interval to IOS device v7.1 or later, so you should be able to send up to 50*6=300 packets per second, each packet containing max 20 payload bytes. Perhaps this thread and this thread could provide some further hints on what you need to do.

  • Thanks Stefan.


    3.6 Connection Parameters The accessory is responsible for the connection parameters used for the Low Energy connection. The accessory should request connection parameters appropriate for its use case by sending an L2CAP Connection Parameter Update Request at the appropriate time. See the Bluetooth 4.0 specification, Volume 3, Part A, Section 4.20 for details. The connection parameter request may be rejected if it does not comply with all of these rules:

    ● Interval Max * (Slave Latency + 1) ≤ 2 seconds ● Interval Min ≥ 20 ms ● Interval Min + 20 ms ≤ Interval Max Slave Latency ≤ 4 ● connSupervisionTimeout ≤ 6 seconds ● Interval Max * (Slave Latency + 1) * 3 < connSupervisionTimeout


    did you mean this one?

    But if i follow this condition, i can not send 20 packets in a second.

    I mean, if I follow this conditions, the device notify just 4 packets in a second after FIRST_CONN_PARAMS_UPDATE_DELAY.

Related