View Single Post
  #3   Spotlight this post!  
Unread 15-01-2010, 15:53
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,748
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Problem with System Watchdog

If the message is about a User watchdog, then your approach is correct, but the system watchdog is totally independent and not affected using WPI APIs.

It would be really useful to know the user actions or other conditions that provoke the system watchdog printout. The driver station uses a tab change as a hook for saving off the configuration file. Producing this file is likely delaying a control packet long enough for the cRIO system watchdog to temporarily glitch.

The diagnostic print statement to catch these short watchdog glitches wasn't even in last year's system, and were only added in December, thus we don't have enough experience with when they may occur. Internal and beta testing found and corrected a few issues that produced noticeable and reproduceable glitches. If the tabs or another action triggers a system watchdog that interferes, there are many ways of dealing with them. Once again, at this point, please describe as fully as possible, the background and steps to reproduce.

Greg McKaskle
Reply With Quote