current time service and calendar in nrf connect sdk

RE: current time service and calendar in nrf connect sdk

Einar Thorsrud — Mon, 06 Jan 2025 09:04:23 GMT

Hi,

The orginal post here refered to the peripheral_cts_client sample. If you have other questions, please make a new question.

RE: current time service and calendar in nrf connect sdk

lara — Fri, 03 Jan 2025 06:10:10 GMT

can you share the api u used or sample code?

RE: current time service and calendar in nrf connect sdk

Einar Thorsrud — Thu, 20 Apr 2023 08:31:10 GMT

Hi,

The accuracy is given by your low frequency clock source. If you use the internal RC oscillator that will be 500 ppm when calibrated regularly (which is the default configuration). The reason for this not begin 250 is erratum 146. If you have an external 32.768 kHz on your board and use that, the accuracy of the crystal will dictate the accuracy

RE: current time service and calendar in nrf connect sdk

aurna — Wed, 19 Apr 2023 18:12:14 GMT

Hey Einar!

I just wanted to say thanks for your help in clarifying things for me. With your guidance, I was able to successfully add the date and time feature to my application!

However, I do have a question about the accuracy of the rtCounter when it comes to maintaining time on the board. Do you happen to know if the oscillator is 250 ppm? And if so, do you have any suggestions on how to improve the accuracy? Thanks so much!

RE: current time service and calendar in nrf connect sdk

Einar Thorsrud — Mon, 17 Apr 2023 14:02:12 GMT

Hi,

The CTS sample demonstartes how to get the current data and time via Bluetooth. Internally, Zephyr has a 64 bit timer to keep track of the uptime, and that can be combined. If you store the system time when you get the current data and time via CTS, you can subsequently compensate for that to know the current data and time at any point after that. See Time Utilities.