Datasheet

Page 119 of 161
nRF8001 Product Specification
Revision 1.2
Data returned in the CommandResponseEvent is:
• Command code:
ChangeTimingRequest
• Status: Success / Status code
• Response data: None
Figure 53.
illustrates the communication scenarios for the ChangeTimeRequest command.
Figure 53. ChangeTimingRequest MSC
24.18.5 Bluetooth low energy procedures used
The following GAP procedures are used to change connection timing:
• Connection Parameter Update Procedure
27
27.Bluetooth Core specification v4.0, Vol. 3, Part C (GAP), Sect. 9.3.9
Appl. controller Device Peer
CHANGE TIMING REQ
Connection Parameter
Update Procedure
-----
L2CAP_SIG: ConnectionParameterUpdateRequest (new timing values)
L2CAP_SIG: ConnectionParameterUpdateResponse
(Connection Parameter Accepted / 0x0000)
RTX timer = 60 sec
Procedure Timer
= 30 sec
HCI: LE Connection Update Complete event
CommandResponseEvent
(
ChangeTimingReq, Success)
RTX timer timeout
L2CAP_SIG: ConnectionParameterUpdateResponse
(Connection Parameter Rejected / 0x0001)
Procedure timer
timeout
RTX timer stop
Procedure Timer
Stop
TimingEvent
(
Old timing values)
DisconnectedEvent
(
Extended: TerminatedByLocalHost)
TimingEvent
(
Old timing values)
TimingEvent
(
new timing values)
Connection Parameter update
Successful
Transfer
Error
scenario 1
Error
scenario 2
Error
scenario 3
Terminate Connection Procedure
HCI: LE Disconnect event
RTX timer stop
-----
Actual timing is within the requested
Connection interval range
TimingEvent
(
Old timing values)
CommandResponseEvent
(
ChangeTimingReq, Success)
Successful
Transfer
(No airtraffic generated)