watchdog timer wake up problem for 12hrs

suresh53 · Joined: 02 Aug 2016 Posts: 4

hi

I have faced a problem in watchdog timer wake up for 12hrs once.

temtronic · Posted: Sat Sep 03, 2016 5:06 am

This is probably simple basic 'timing'... though I haven't run your code, I see you're using internal oscilllator and WDT.

You have to read the 500+ pages of the datasheet and find the 'accuracy' or 'range' or 'nominal' specifications for both the WDT and the internal RC oscillator. Important specs to read...'somewhere'...
In the past, the WDT was +-50 to 100% of the value. Say the WDT is set for 1 second. Valid, by the book, numbers would be 1/2 to 2 seconds ! I don't use that PIC and heaven't looked for the spec but I assum it's fairly 'wide'.
Also the Internal clock is NOT exactly 4,000,000.000000000 Hz! Again due to the RC nature,even though laser trimmed, it is NOT precise. So since every clock cycle is just a 'little' off what you think it should be ,or observe, over time it all adds up. In your case the clock may be running fast, so the WDT resets sooner than the calculation says it should. Added to this is the temperature factor. The 'specs' are at a certain temperature and the actual performance WILL be different as the PIC heats up(during lots of use) and slows down( when it's asleep). This is normal and the effect will be different on every PIC,although same batch PICs tend to be very close.
You could run several 'timing tests' and fine tune the WDT counter variable to get the WDT to trigger when you want. you'll need a LOT of time to run these tests though. I don't think it will matter if you,for instance, set the WDT for 1 second and externally counter 256, interrupts versus setting the WDT for 256 seconds and see 1 interrupt. In the first case the PIC is internally counting, in the second you are.
The only easy and accurate way to get precise timing is by using an external crystal/caps clock.

Jay

Ttelmah · Joined: 11 Mar 2010 Posts: 19329

Temtronic has given the basic answer.

Critical thing is that if you read the data sheet line about using the watchdog, it says:

"Configurable time-out period is from 1 ms to 256
seconds (typical)".

Note the 'typical'.

Then parameter 31, Table 30-5:
Low-Power Watchdog Timer
Time-out Period min 12, Typ 16, Max 20.

So the nominal 256 seconds could be anything from 192, to 320 seconds.

This is far tighter than many of the older watchog's, that had figures like 7 to 28mSec.

The watchdog is not designed as an accurate timer. If you want accurate times, you need to use something like an external crystal based RTC.

As a comment, your clearing SWDTEN does nothing. You have the watchdog fuse set, and when this is set, the SWDTEN bit is disabled. Again in the data sheet. The WDTE bits in configuration word 1. To allow the watchdog to be controlled by SWDTEN, instead of the fuse 'WDT', you need the fuse 'WDT_SW' which sets the watchdog so it can be software controlled.