Hi,
The BLE connection disconnects after I changed the connection interval. Why is this so ? It works fine with the default settings.
SDK : 17.1.0, HRS example.
On the central side:
On the Peripheral Side:
Logs given below:
<info> app_timer: RTC: initialized.<debug> nrf_ble_lesc: Initialized nrf_crypto.<debug> nrf_ble_lesc: Initialized nrf_ble_lesc.<debug> nrf_ble_lesc: Generating ECC key pair<debug> ble_scan: Added filter on UUID 180D<info> app: Heart Rate collector example started.<info> app: Starting scan.<debug> ble_scan: Scanning parameters have been changed successfully<debug> ble_scan: Scanning<debug> ble_scan: Connecting<debug> ble_scan: Connection status: 0<debug> nrf_ble_gatt: Requesting to update ATT MTU to 247 bytes on connection 0x0.<debug> nrf_ble_gatt: Updating data length to 251 on connection 0x0.<info> app: Connected.<debug> nrf_ble_gq: Registering connection handle: 0x0000<debug> ble_db_disc: Starting discovery of service with UUID 0x180D on connection handle 0x0.<debug> nrf_ble_gq: Adding item to the request queue<debug> nrf_ble_gq: GATTC Primary Services Discovery Request<debug> nrf_ble_gq: Processing the request queue...<debug> nrf_ble_gq: GATTC Primary Service Discovery Request<debug> nrf_ble_gq: SD is currently busy. The GATT request procedure will be attempted again later.<debug> nrf_ble_gq: Processing the request queue...<debug> nrf_ble_gq: GATTC Primary Service Discovery RequestU of 247 bytes.7) on connection 0x0.<info> app: Disconnected, reason 0x8.<info> app: Starting scan.<debug> ble_scan: Scanning
Best regards,
Buja
