Command Based Auto - Windriver C++ Having trouble to add sequential auto commands

[dougwilliams]

Originally Posted by RufflesRidge

This part is easy. There is no "requires" statement in your DriveAuto command which means there is nothing to tell the Scheduler that DriveAuto and your default command for the DriveBase should not run concurrently.

That was correct - adding requires prevented the teleop portion from running.

Still debugging why it jumps right to the last command in the sequence:

Originally Posted by KPSch

Looking at the documentation for Timer, the resolution is in milliseconds (1000 in a second).

What documentation are you seeing that in, please? Finding good WPILIb documentation is difficult. Looking at WPILib Timer C Code, it specifically mentions seconds. In the code we have it print the timer value each iteration through the DriveAuto call, and it increases between .1 and .2 (seconds) each time. The robot stops after .3. In actuality, I would say it moves for about 1 second.

What I'm thinking is that the separate calls to DriveAuto aren't being treated as "new", and unique, and each constructor is overwriting the previous calls and it effectively only acts on the last.

The prints seem to corroborate that, I'm just not sure why that would be now...

[KPSch]

Originally Posted by dougwilliams

What documentation are you seeing that in, please? Finding good WPILIb documentation is difficult. Looking at WPILib Timer C Code, it specifically mentions seconds. In the code we have it print the timer value each iteration through the DriveAuto call, and it increases between .1 and .2 (seconds) each time. The robot stops after .3. In actuality, I would say it moves for about 1 second.

I found two different sources and they conflict. One says milliseconds, here: http://users.wpi.edu/~bamiller/WPIRo...$@#$@#$@#_timer.html. I'm guessing it's incorrect. The other source I found was here: http://amhsrobotics.com/oldsitev3/wp...8h_source.html.

The best place I've found (sortof) documentation is inside WindRiver itself. Hold down Ctrl while clicking on a class name and it will take you to the header file. It does, indeed, look like it's in seconds.