View Single Post
  #6   Spotlight this post!  
Unread 26-01-2010, 18:23
wireties's Avatar
wireties wireties is offline
Principal Engineer
AKA: Keith Buchanan
FRC #1296 (Full Metal Jackets)
Team Role: Mentor
 
Join Date: Jan 2006
Rookie Year: 2004
Location: Rockwall, TX
Posts: 1,170
wireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond repute
Send a message via AIM to wireties
Re: How to Spade and Neuter the Dog

The watchdog serves an important purpose. You should have spent 7 hours restructuring your code so that it does not fire instead of turning it off.

The timeout is much longer than the normal interval between messages, around 100ms I think. It is OK to turn it off while debugging since numerous print statements, stepping through code/VIs etc will sometimes trigger it. But if it is firing in your final code, it is a BIG problem. It means your software is spending large amounts of time doing something between the calls to pet the watchdog. This is normally an indication that something else is seriously wrong, the kinds of things that can make servos act funny, cameras not respond, communications fail etc if not fixed.

Good luck.