Quote:
Originally Posted by propionate
I'm a little confused as to why you have contained your separate motor control VI's in a flat sequence. Are you attempting to run these controls in a particular order if a certain combination of buttons is pressed? If not, there is no need for the flat sequence structure.
|
I had the idea that it was running too many things at once, and that if I put it into a flat sequence structure, it will slow down a bit. That, and I'm more used to coded languages such as python or java, the flat sequence make a little bit more "sence" to me.
Quote:
Originally Posted by Greg McKaskle
I assume you placed that code into teleop. If teleop doesn't read the joysticks and update the robotDrive many times per second, it will act as you describe. Once your sequence starts, the delays prevent teleop from doing the robotDrive task.
What most teams do is to move the code you've shown into periodic tasks. That way teleop can run quickly and return to the scheduler.
Greg McKaskle
|
I'll try that tonight, thanks.