View Single Post
  #9   Spotlight this post!  
Unread 21-02-2010, 18:55
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: Watchdog Problem

The current printout in the Diagnostics doesn't identify the reason, so legitimate disabling of the robot shows up as a watchdog.

The user watchdogs are due to code not feeding the watchdog. System watchdogs are either due to a disable or due to a timing glitch caused by the DS. The second ones should be pretty rare, but we are still tracking down some reasons they can occur.

Anyway, look for the reasons that your code is getting hung up. Put timing code in each and every loop and in the teleop subVI. Watch those either on your panels or on your dashboard to determine which loop is late.

Greg McKaskle
Reply With Quote