Is there any time limit to send Gap_UpdateConnectionParameters() to central after connection established?
I read some documents. From my understanding we need to wait for 6 seconds after connection established and then we can call Gap_UpdateConnectionParameters();
Connection Parameter Update command shall only be sent if either the Central or the Peripheral does not support the Connection Parameters Request Link Layer Control procedure; so it may be required only under this condition, but for KW36 it is optional and it will be safe to update Connection Parameters after 6 seconds.
For Connection Parameter Update, the only precondition is that a connection must be in place. You can find more information on this in the Bluetooth Core Specification, Vol 3, Part C, Section 9: Operational Modes and Procedures -> 9.3 Connection modes and Procedures -> 9.3.9 Connection Parameter Update procedure.
I am very well, thank you. I hope you are well too.
I read the section of Bluetooth Core Spec. document you refereed.
Then i find these:
After the Peripheral has no further pending actions to perform and the Central has not initiated any other actions within TGAP(conn_pause_central), then the Peripheral may perform a Connection Parameter Update procedure (see Section 9.3.9). The Peripheral should not perform a Connection Parameter Update procedure within TGAP(conn_pause_peripheral) after establishing a connection.
in BLUETOOTH CORE SPECIFICATION Version 5.3 | Vol 3, Part C, Section 9: Operational Modes and Procedures -> 9.3 Connection modes and Procedures -> 9.3.12 Connection interval timing parameters -> 9.3.12.2 Conditions
Connection Parameter Update command shall only be sent if either the Central or the Peripheral does not support the Connection Parameters Request Link Layer Control procedure; so it may be required only under this condition, but for KW36 it is optional and it will be safe to update Connection Parameters after 6 seconds.
