This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BLE connection interval (timing inconvenience)

Hello,

My firmware uses a BLE connection (BLE's TI stack version 1.1) with the parameters below:

- Min. Interval = 40 msec.

- Max. Interval = 60 msec.

- Slave latency = 4.

- Timeout = 200.

The effective interval connection should be: 60 * (4+1) = 300 msec. I chose this values due to a task with a duration of 290 msec.

As we can see, the slave ignore 4 connection events, but what happens if i execute my task after 2 connection events? Im going to explain that:

1)  time = 0 ms    -> Slave answers to the master (first connection event of the effective interval conn.)

2) time = 60 ms   -> Slave ignores the second conn. event.

3) time = 120 ms -> Slave ignores the thirst conn. event. and inmediatly executes the task (300 msec. spent)

4) time = 180 ms -> Slave is busy executing the task (conn. event is ignored, no problem).

5) time = 240 ms -> Slave is busy executing the task (conn. event is ignored, no problem).

6) time = 300 ms ms -> Slave is busy executing the task, and it doesn't answer to the conn. event ---> LINK LOST.

And my question is: how could i know when i should execute the task? Is there any way to check when the peripheral sends the answer to these connection events? LL task? L2CAP task? Any timer which can tell me that? Any function?

Regards, David M.L.