View Single Post
  #5   Spotlight this post!  
Unread 20-02-2013, 15:40
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,795
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Robot Main.VI Driving Issues

That's got some things wrong with it.
Mostly the code isn't structured that way.
Teleop is supposed to be a quick execute and leave, so it can go pick up new driver orders.
The new code you added includes a While loop that doesn't ever let it leave to go get new driver commands, staying in there forever, because it's structured as a stand-alone program that's been stuck inside a sub-program. The For loops don't accomplish anything other then to slow down execution while they set the motor output over and over again to the same value.
  • Device Opens on the left belong in Begin.vi (you'll have to name them there and use the new names in Teleop to reference them).
  • Using the Device goes in Teleop.vi (remove the While loop and all the For loops)
  • Device Closes on the right go in Finish.vi
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 20-02-2013 at 15:52.
Reply With Quote