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.

iOS 6.1.4 master, LL_CONNECTION_UPDATE_REQ followed too soon by new timings

Other Parts Discussed in Thread: CC2541

With TI BLE version 1.3.1 on CC2541 as peripheral (slave), using iOS 6.1.x as a Central (master), we've seen sporadic drops of the connection after updating the connection parameters with LL_CONNECTION_UPDATE_REQ. It doesn't always happen, but it does seem to be related to the update request.

One thing we have consistently observed is that there are only 5 connection events between sending LL_CONNECTION_UPDATE_REQ and an actual parameter change. The spec says there should be at least 6 events (Vol 6, section 5.1.1 

Connection Update Procedure:

The Instant field of the LL_CONNECTION_UPDATE_REQ PDU shall be used

to indicate the connEventCount when the updated parameters shall be applied;

this is known as the instant. The master should allow a minimum of 6 connection

events that the slave will be listening for before the instant occurs.

Could this "early instant" cause a problem for the TI stack? I've seen the peripheral respond ONCE to the first packet with new timings, and then never again.


  • I found it in keyfob

    everytime i update connection parameter, iphone 5 will lose connection with key fob

    i measure 32K by GPIO output, and it has 30ppm accuracy, so i think 32K is ok.

    Also i measure 32M, it has 20ppm accuracy.

    I download stack 1.3.1 to key fob,  and connection interval is 500ms or 1000ms, it also lose connection from ipod touch 5th(IOS 6.1.3).

    So any other advice ?