View Single Post
  #6   Spotlight this post!  
Unread 18-02-2010, 21:31
theprgramerdude theprgramerdude is offline
WPI Freshman
AKA: Alex
FRC #2503 (Warrior Robotics)
Team Role: Mentor
 
Join Date: Feb 2010
Rookie Year: 2008
Location: Brainerd, Minnesota
Posts: 347
theprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud oftheprgramerdude has much to be proud of
Re: Watchdog programming error

Well, after a bit of testing today, I've narrowed down the problem. It appears that the watchdog itself does not cause an error; in fact, I believe it's simply acting the way it's designed to. It's timing out after there's a call error somewhere when switching to either autonomous or teleoperated mode. One of the methods or calls might be causing some error, as evidenced by the Netbeans output error. It'll take a little while longer to isolate the exact cause of this. Simply telling the Teleop periodic default to feed the watchdog only does not fix the issue in my original code, yet deleting/commenting out my reference variables and the variables in the constructor do fix the issue when switching to Teleop.
Reply With Quote