View Single Post
  #49   Spotlight this post!  
Unread 24-03-2010, 10:11
Racer26 Racer26 is offline
Registered User
no team
Team Role: Alumni
 
Join Date: Apr 2003
Rookie Year: 2003
Location: Beaverton, ON
Posts: 2,229
Racer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond reputeRacer26 has a reputation beyond repute
Re: Take an exit with dignity

Quote:
Originally Posted by Radical Pi View Post
It's a known issue and 100% error of the team's programmer. Java and C++ code waits for the autonomous code to finish execution even when the FMS switches to teleop. The LabVIEW error is a little tougher to explain but it is user error.



coincidence
Not entirely sure I agree here.

Yes, C++ (what 1075 uses) DOES wait to start Teleop() until after Autonomous() is completed.

However, Autonomous() at least, as defined in the SimpleRobot template, has a While(IsAutonomous()){} loop in it. If your code is designed to pay attention to this fact, you should have no problems forcing your Autonomous code to stop operation the instant FMS changes your robots status from Autonomous to Teleop.
Reply With Quote