View Single Post
  #3   Spotlight this post!  
Unread 12-02-2010, 02:30
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: Autonomous Problems

The framework supports several ways of doing autonomous. This was mostly for compatibility with how things were done on the old system and to match the capabilities across the languages. I would definitely recommend opening the Autonomous Independent VI and examining what is in its diagram. It is started at the beginning of autonomous, and either runs to completion or is aborted at the end of the period.

You can Get Refnums at any time, such as at the beginning of the autonomous, use them, and unless something in teleop is used very differently, you do not need to worry about closing or anything else until Finish.

You typically set the Drive values based on how you would imagine moving the joystick. You use time, distance, or another sensor feedback to determine how to adjust your path.

By default, the LV template runs the vision code independently, including during autonomous. This means you can simply read the global variable about targets. You can use this to time kicks, turn the robot, etc.

Greg McKaskle
Reply With Quote