This parameter determines how long time passed from either connection or CCCD write (depending on the value used for start_on_notify_cccd_handle) it will take before a Connection Parameter Update Request is sent, if the initial connection parameters of the Central are not within the Peripheral's requirements.
If the start_on_notify_cccd_handle is set to BLE_GATT_HANDLE_INVALID, the time will be measured from the CONNECTED event. If the start_on_notify_cccd_handle is set to the value of a CCCD, time will be measured from that specific CCCD is written by the GATT Client.
it seems I have had a better understanding about it now.
And I get a futher question:
Assuming that the start_on_notify_cccd_handle is set to BLE_GATT_HANDLE_INVALID, is that means the device can only connect again after FIRST_CONN_PARAMS_UPDATE_DELAY?(even if i have disconnected my device during the peroid)?
I'm not sure I understand your question. When you get a disconnect, you should be able to reconnect again as soon as you start advertising. This delay doesn't affect that in any way.
OK,sorry for my unreasonable guess because I met this phenomenon on my device and I think it is due to FIRST_CONN_PARAMS_UPDATE_DELAY.Forget about it.
I actually has another question,please.
That is: when my device connect to my i-pod sucessfully,i press the 'Disconnected' button at my app immediately, but my device does not disconnect as soon as i press, instead it will disconnect after about 5 seconds. I want to konw if this delay is determined by some parameters, or just because this connection process do take so long time so it can not disconnect during this period?
Thank you very much!
