nRF51 SDK
 All Data Structures Functions Variables Typedefs Enumerations Enumerator Groups Pages
0x65 - sd_ble_gap_conn_param_update

Function packet format

Frame format encoding of the sd_ble_gap_conn_param_update packet.

Operation Code = 0x65 (101) for sd_ble_gap_conn_param_update, see BLE_GAP_SVCS.

The parameter provided as input to sd_ble_gap_conn_param_update is encoded in the following order:

- 1 byte: Operation Code, Value = 0x65 (101)
- 2 bytes: Connection Handle
- 1 byte: Connection Parameters Present
0x00 Field not present
0x01 Field present and follows immediately in the packet
- 8 bytes: Conditional: Connection Parameters


As can also be seen inside Figure 1 the 8 bytes inside ble_gap_conn_params_t are encoded as:

- 2 bytes:ble_gap_conn_params_t::min_conn_interval Minimum Connection Interval
- 2 bytes:ble_gap_conn_params_t::max_conn_interval Maximum Connection Interval
- 2 bytes:ble_gap_conn_params_t::slave_latency Slave Latency in number of connection events
- 2 bytes:ble_gap_conn_params_t::conn_sup_timeout Connection Supervision Timeout


conn_param_update_packet.png
Figure 1: Packet format for sd_ble_gap_conn_param_update function.

Response packet format

Frame format encoding of the sd_ble_gap_conn_param_update response packet.

In case of an error, the following data is encoded:

- 1 byte:Operation Code, Value = 0x65 (101)
- 4 byte:nRF Error Code


default_error_response_packet.png
Figure 2: Packet format for sd_ble_gap_conn_param_update error response.

In case of a successful command, i.e. 'nRF Error Code' = NRF_SUCCESS, the following data is encoded:

- 1 byte: Operation Code, Value = 0x65 (101)
- 4 bytes:nRF Error Code


default_success_response_packet.png
Figure 3: Packet format for sd_ble_gap_conn_param_update success response.