why connection interval parameter setting don't take effect

[nicholasldf]

the interval parameter setting in application  don't take effect,,,   device still run  with DFU-bootloader's connection interval setting.

i use nRF5_SDK_13.0.0-1.alpha.

application connection interval is:

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(400, UNIT_1_25_MS) /**< Minimum acceptable connection interval (0.4 seconds). */
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(650, UNIT_1_25_MS) /**< Maximum acceptable connection interval (0.65 second). */
#define SLAVE_LATENCY 0 /**< Slave latency. */
#define CONN_SUP_TIMEOUT MSEC_TO_UNITS(4000, UNIT_10_MS)

DFU-bootloader connection interval is:

#define MIN_CONN_INTERVAL (uint16_t)(MSEC_TO_UNITS(15, UNIT_1_25_MS)) /**< Minimum acceptable connection interval. */
#define MAX_CONN_INTERVAL_MS 30 /**< Maximum acceptable connection interval in milliseconds. */
#define MAX_CONN_INTERVAL (uint16_t)(MSEC_TO_UNITS(MAX_CONN_INTERVAL_MS, UNIT_1_25_MS)) /**< Maximum acceptable connection interval . */
#define SLAVE_LATENCY 0 /**< Slave latency. */
#define CONN_SUP_TIMEOUT (4 * 100) /**< Connection supervisory timeout (4 seconds). */

thank you!

[FormerMember]

In a connection, the peripheral cannot decide the connection parameters, but it can request a set of connection parameters, and the central can choose to accept or reject the update. Does your application do a connection parameter update? (sd_ble_gap_conn_param_update() )

[nicholasldf]

hi, kristin,,  i use Nordic's  nRF Toolbox app,,,  so i think this issue is not cause by APP.

also, my application is base on  "nRF5_SDK_13.0.0-1.alpha\examples\ble_peripheral\ble_app_hrs",  and i see that,  update_timeout_handler() call sd_ble_gap_conn_param_update() to  do a connection parameter update.

[FormerMember]

Could you double check that your application actually do the connection parameter update request?

You can for example do so by running the application in debug mode and put a breakpoint where sd_ble_gap_conn_param_update() is called?