GAP disconnect stops app timer

[Bryan V]

I'm running a BLE application on the nRF51822. And I have an application timer to keep track of the real time clock. However, when I receive a BLE_GAP_EVT_DISCONNECTED event, I notice the "m_conn_params_timer_id" timer gets stopped. But this timer ID is also the same as the RTC timer ID I have running (= 0), thus it is stopping my RTC app timer as well.

Is there a way around having to restart the RTC app timer whenever I receive the disconnect event? Or if I configure the RTC hardware registers directly will this get around this issue?

Thank you!

[Einar Thorsrud]

As RK says, you cannot use the same ID for two timers. You may find it worh reading the Application Timer Tutorial.

[Bryan V]

I gathered that much, but from what I'm reading the timer ID is populated by the app timer APIs and it is not a variable I am in control of setting. I am currently following the steps outlined in the tutorial; I am using SDK 9 so maybe I will try with SDK 10 to see if it gets resolved.