View Single Post
  #5   Spotlight this post!  
Unread 15-02-2010, 08:47
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,751
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: Need a Full "Watchdog for idiots" explanation

The real issue may be with the code you aren't asking about. Watchdog's are used to ensure that machinery or equipment the computer is supposed to control is being paid attention to often enough. If the computer doesn't do its job, the watchdog steps in and takes over the job, hopefully making things safer by turning off power. The FRC watchdog doesn't latch once it is thrown, so I believe what you are seeing is feeding that is way too slow.

The computer sets up the motors, then delays for a bit too long so the watchdog turns everything off. Then the code comes back, feeds, and the motors jerk back to their current settings, and then we repeat.

I don't recall seeing what mode the robot is in, but if it is teleop, this could likely be caused by putting vision or some other expensive task inside the robot Main or inside TeleOp. I think the best thing to do is post code you've modified, or pictures of the code.

Greg McKaskle
Reply With Quote