Quote:
Originally Posted by Alexa Stott
1. I recommend disabling the watchdog entirely. This should be done by simply entering GetWatchdog.SetEnabled(false), NOT by "killing" the watchdog. That causes even more problems. I found this feature to be more of a pain than anything.
|
Watchdog's exist for a reason. I would not give a blanket statement saying disable the watchdog because for a number of teams this may be a bad idea. I know that there are parts of our robot that could be broken if our code were to hang and not be disabled by the watchdog.
For some teams disabling the watchdog may be the easy solution for now, but the "better" solution is probably a properly fed watchdog.
Border Guard: "Anything to declare?" Team: "Oh, just these trophies!" - dtengineering [more] 
03-03-2009, 20:39
Similar Threads
Threaded Mode