GAP disconnect stops app timer

RE: GAP disconnect stops app timer

Bryan V — Wed, 24 Feb 2016 14:37:06 GMT

I found the real root of the problem. I was never initializing the connection parameters (ble_conn_params_init), and on disconnect my dispatch handler function was, however, calling ble_conn_params_on_ble_evt() which stops the one shot timer that ble_conn_params_init() should have created.

Since the m_conn_params_timer_id is initialized to zero, app_timer_stop() stops the timer ID with ID = 0, which is ID of the real time clock.

RE: GAP disconnect stops app timer

Bryan V — Tue, 23 Feb 2016 14:47:29 GMT

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.

RE: GAP disconnect stops app timer

Einar Thorsrud — Tue, 23 Feb 2016 07:36:48 GMT

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

RE: GAP disconnect stops app timer

RK — Tue, 23 Feb 2016 01:27:00 GMT

Neither of the above.

Your problem is that two timers have the same ID, which is clearly wrong, hence one or both of them were initialised incorrectly. So you need to fix that, as that is your actual issue.