ble_app_hrs connection timeout

[Olivier Scalbert]

Hello,

I am testing the ble_app_hrs project on two eval boards, with s110 and s120. Everything works. If I power-off the peripheral board (s110), it seems that the master board restart scanning around 5 seconds later. Is there a way to restart scanning earlier ? What is the shortest time ?

Thanks,

Olivier

[Olivier Scalbert]

Thanks for your reply !!! I know it is not easy by mail ... :-)

I have put some traces in the Central code:

Hello from fix module !!! [APPL]: Scan started ble_evt_dispatch:BLE_GAP_EVT_ADV_REPORT, [APPL]: Scan stopped

[APPL]:[37 11 AF 64 BA C4]: Connection Requested ble_evt_dispatch:BLE_GAP_EVT_CONNECTED [APPL]:[37 11 AF 64 BA C4]: Connection Established

ble_evt_dispatch:SD_BLE_GATTC_PRIMARY_SERVICES_DISCOVER ble_evt_dispatch:SD_BLE_GATTC_CHARACTERISTICS_DISCOVER ble_evt_dispatch:SD_BLE_GATTC_DESCRIPTORS_DISCOVER [APPL]: Heart rate 8192 ble_evt_dispatch:SD_BLE_GATTC_WRITE ble_evt_dispatch:SD_BLE_GATTC_HV_CONFIRM [APPL]: HR Measurement received 180 ble_evt_dispatch:SD_BLE_GATTC_HV_CONFIRM [APPL]: HR Measurement received 180 ble_evt_dispatch:BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST ble_evt_dispatch:SD_BLE_GATTC_HV_CONFIRM [APPL]: HR Measurement received 180 ble_evt_dispatch:BLE_GAP_EVT_DISCONNECTED [APPL]: Disconnected [APPL]: Scan started

When I power on the peripheral, the connection is done immediatly. Nice ! But then the 3 DISCOVER messages arrive slowly (one every 1.5 sec) and I receive the BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST 10 seconds later. Or at the Peripheral side, I have set: FIRST_CONN_PARAMS_UPDATE_DELAY APP_TIMER_TICKS(1000, APP_TIMER_PRESCALER) NEXT_CONN_PARAMS_UPDATE_DELAY APP_TIMER_TICKS(2000, APP_TIMER_PRESCALER)

[Ole Morten]

Unfortunately, it seems there is an issue with the connection manager, that I haven't actually noticed. It uses hard coded connection parameters, and you'll therefore have to do those changes in conn_mngr.c on lines 187-188 instead of just in the header file. I'm terribly sorry for not noticing this before, and I've reported it internally so that it can be fixed in a future version.