View Single Post
  #13   Spotlight this post!  
Unread 17-02-2013, 07:44
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: Help 2013 Robot won't run

LabVIEW uses the term probe, but it could be called a watchpoint or a variable viewer, etc. If you probe a wire and data goes down the wire, that small window lets you see what value your code produced.

So if you probe the wire going into the RobotDrive, it will show you whether it is running at all, and whether the value being sent makes sense and is what you intended.

If the value going into RobotDrive makes sense, then you should verify that PWM channels and wiring and other things make sense. If it never runs or the value is always zero, you debug in the other direction to the driver station or to upstream elements.

So, by probing wires in teleop, what can you deduce?

Greg McKaskle
Reply With Quote