App Timer problem...

RE: App Timer problem...

Øyvind — Tue, 17 Sep 2019 07:31:05 GMT

Very glad to hear! Have a nice day! 🙂

Kind regards,
Øyvind

RE: App Timer problem...

Erik_pxq — Mon, 16 Sep 2019 06:39:55 GMT

Yes, my application is working nicely together with the app timer v2.

Thanks very much for the help.

Best regards, Erik

RE: App Timer problem...

Øyvind — Fri, 13 Sep 2019 13:46:43 GMT

[quote user="Erik_pxq"]I have not yet found anything wrong with the experimental app timer!![/quote]

I'm glad to hear! Does this mean that your application is working as intended?

-Øyvind

RE: App Timer problem...

Erik_pxq — Fri, 13 Sep 2019 12:16:03 GMT

Sorry, I made a mistake in my test code!

I have not yet found anything wrong with the experimental app timer!!

Best regards,

Erik

RE: App Timer problem...

Erik_pxq — Fri, 13 Sep 2019 09:34:25 GMT

I have now tried the the experimental app timer and made some testing with it.

It works correctly at the 256 second mark. Unfortunately, I find it fails occasionally when more than 3 timers is running at the time.

Do you know off any thirdparty libraries which implement some of the same functionality as the app timer library?

Best regards,

Erik

RE: App Timer problem...

Øyvind — Tue, 10 Sep 2019 13:58:49 GMT

[quote user="Erik_pxq"]Is the app timer designed to handle wrap arounds?[/quote]

Yes, it should handle wrap arounds, however, there are some issues that we are aware of, and working with. This is why we have added app_timer_v2 in components\libraries\timer\experimental. However, this is currently in experimental status, and we do not have any good examples at the moment.

Kind regards,
Øyvind

RE: App Timer problem...

Erik_pxq — Tue, 10 Sep 2019 13:29:00 GMT

Hi Øyvind,

Thanks for your answer.

I have just verified, that setting the app timer clock to 32768/2=16384 solves the problem for delays under 256 seconds.

But I have also verified that the problem is just moved, so it instead occurs after 512 seconds. I guees the same probably happens with other prescalers.

Are you sure that APP_TIMER_KEEPS_RTC_ACTIVE=0 actually solves the problem, and not just moves it around?
Setting APP_TIMER_KEEPS_RTC_ACTIVE=0, ensures that the app timer doesn't overflow while no app timers is running, but eventually the app timer will overflow and the problem could occur.

Is the app timer designed to handle wrap arounds?

Best regards, Erik

RE: App Timer problem...

Øyvind — Tue, 10 Sep 2019 12:45:38 GMT

Hello Erik,

I have been able to reproduce your error. There are two possible solutions to this in sdk_config.h:

Disable RTC Always on

// <q> APP_TIMER_KEEPS_RTC_ACTIVE  - Enable RTC always on
 
// <i> If option is enabled RTC is kept running even if there is no active timers.
// <i> This option can be used when app_timer is used for timestamping.

#ifndef APP_TIMER_KEEPS_RTC_ACTIVE
#define APP_TIMER_KEEPS_RTC_ACTIVE 0
#endif

Or lower the RTC prescaler, as a high prescaler causes it to wrap around.

// <o> APP_TIMER_CONFIG_RTC_FREQUENCY  - Configure RTC prescaler.
 
// <0=> 32768 Hz 
// <1=> 16384 Hz 
// <3=> 8192 Hz 
// <7=> 4096 Hz 
// <15=> 2048 Hz 
// <31=> 1024 Hz 

#ifndef APP_TIMER_CONFIG_RTC_FREQUENCY
#define APP_TIMER_CONFIG_RTC_FREQUENCY 0
#endif

I've tested with RTC Always ON and prescaler = 16384 Hz, and got:

App timer fired OK : Elapsed time(ms)=10090, expected(ms)=10000

Let me know how that works for you.

Kind regards,
Øyvind