View Single Post
  #2   Spotlight this post!  
Unread 18-01-2011, 12:11
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: A newbie to Labview Questions about interrupts

Newcomers to LabVIEW should probably not be thinking about interrupts. They aren't "the right way" to do simple tasks, and even complex tasks usually have good non-interrupt ways to implement them.

I don't understand what "their entire robot is based on if statment" means.

The LabVIEW team code runs specific Virtual Instruments at specific times. Begin.vi runs once during initialization. Autonomous Independent.vi is started at the beginning of Autonomous Mode and is automatically stopped when Autonomous Mode is over. Teleop.vi is run each time the robot receives a communication packet from the Driver Station, and is where just about everything the team wants the robot to do gets done. Finish.vi runs once when the program ends...which never happens except when you click the big "Finish" button on the Robot Main.vi front panel during development.
Reply With Quote