View Single Post
  #4   Spotlight this post!  
Unread 13-03-2013, 23:27
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,112
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: What do these errors mean & how can I fix them?

The first error normally means your Teleop vi is taking too long to execute. That can be due to long-running loops or explicit delays in Teleop, neither of which is a good idea. Or it can be due to another loop elsewhere (e.g. in Periodic Tasks) that is using up all the cRIO's processing cycles, which can happen if you fail to throttle it with a Wait in the loop.

The second "error" is just to record what devices the Driver Station is able to detect on the network. The one you retyped does have an unusual feature: the D-Link router is not responding, but the cRIO is. That's not supposed to happen. Are you perhaps patching your Driver Station computer directly to the cRIO using a single Ethernet cable? You really should never disconnect the cRIO from the D-Link.

The third error is something that happens often when the robot transitions from Autonomous to Teleop. If it only shows up once, with the System count as 1, it's not a problem. If the System count starts increasing, that's something you will need to look into.
Reply With Quote