https://devzone.nordicsemi.com/f/nordic-q-a/10805/ble-communication-causes-rtc1-to-stopHello everybody, I am using RTC1 for time measurement, this works fine as long as no BLE communication is running. The RTC is initialized with const nrf_drv_rtc_t rtc = NRF_DRV_RTC_INSTANCE(1); // Declaring an instance of nrf_drv_rtc for RTC1en-USTelligent Community 13Tue, 15 Dec 2015 06:39:14 GMThttps://devzone.nordicsemi.com/thread/40392?ContentTypeID=1Tue, 15 Dec 2015 06:39:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:96f3fbea-685d-467a-822f-a9e7edd757a7Matthias P.<p>That helped and was actually the problem. I was mixing nrf_drv_rtc and app_timer, which is wrong in this case.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/40391?ContentTypeID=1Fri, 11 Dec 2015 15:29:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:782cda5c-c1b3-4cc1-9623-f6699262a2b8Ole Bauck<p>Question is how did you get nrf_drv_rtc and app_timer to work in the same project, they are conflicting. Some modules like ble_conn_params uses app_timer to update the connection variables some time after the a bluetooth connection is established. Some app_timer call may stop the rtc from running. You should either just use nrf_drv_rtc or just use app_timer. I will suggest to use app_timer, as this is used heavily in the BLE examples.</p><div style="clear:both;"></div>