View Single Post
  #10   Spotlight this post!  
Unread 15-01-2010, 16:52
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: Problem with Default Program/Deploy

From those symptoms, the things I'd check are to see if the cRIO version is v19. Using 2010 WPILib with a 2009 cRIO image will look sorta like this.

Second thing to check is if the watchdog has triggered. The diagnostics page has a place for errors to display, and when a watchdog triggers, it will printout and display the number of triggers that have taken place. I honestly don't think it is the watchdog because the example does the same thing, but if the first test doesn't explain it, I'd double check the watchdog anyway.

Another test I just thought of is to add a relay test. The relay module has LEDs which indicate whether they are working or not, and they are guarded by the same watchdog as the PWM. If the relay in slot 8 doesn't light up, I'd investigate the watchdog more fully. If the LED and therefore the relay I/O works, I'd actually look at the power and wiring to the Jaguar.

Greg McKaskle
Reply With Quote