Thread: No Robot Code
View Single Post
  #11   Spotlight this post!  
Unread 18-02-2010, 20:20
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,756
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: No Robot Code

Reviewing the meaning of the LEDs may help a bit. The robot LED means that the robot IP ping succeeds. The communications LED means that the communications task on the cRIO is responding to the control packets being sent from the DS. Finally, the Robot Code light really means that the robot code is calling into the communications task often enough.

If the cRIO is vastly overtaxed by the code you are writing, it might behave the way you describe, where the WPI framework is not being updating the battery value and other fields as it is supposed to.

I don't remember what language you are using, but if you can determine the CPU usage via spy or a similar tool, it may help you figure out what portion of code is responsible.

Greg McKaskle
Reply With Quote