This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

How to deal with a long time's Clock drift?

Hi,

I use to the nrf51422 with nordic's dev/ev kit.I want to build a project and the purpose is to get the sensor's date and use the ant protocol to deliver the date to another chip every 5 hours.The rest of the time the chip will go to sleep.But recently I test two board's clock drift,I find the clock will drift 1s every 10min.And my test is simple,I use the way: while(1) {
nrf_gpio_pin_set(Pin); nrf_delay_ms(1000); nrf_gpio_pin_clear(Pin); nrf_delay_ms(1000); } I don't know is there any solution can solve this problem? Thanks!

Parents
  • You are right, I thought the same as you when I started implementing it. And yes, it is possible to go this way using the internal RTC but you must live with the drawbacks I mentioned.

    The power consumption is very low (0.3 uA) for external RTCs. The internal RTC consumes 0.1 uA and you need another 0.4uA for the internal 32.768 kHz crystal oscillator. So the consumption is very similar. Would be nice if someone from Nordic could confirm.

    You must decide what is best for your application. There are pros and cons on both sides.

Reply
  • You are right, I thought the same as you when I started implementing it. And yes, it is possible to go this way using the internal RTC but you must live with the drawbacks I mentioned.

    The power consumption is very low (0.3 uA) for external RTCs. The internal RTC consumes 0.1 uA and you need another 0.4uA for the internal 32.768 kHz crystal oscillator. So the consumption is very similar. Would be nice if someone from Nordic could confirm.

    You must decide what is best for your application. There are pros and cons on both sides.

Children
Related