That sounds like the motor safety mechanism is kicking in and stopping your motors because you are not setting the output powers quickly enough (the one second pause from your timer delay).
So, you have two choices. The simple solution is to disable the motor safety feature.
// Turn off drive safety feature as there are long delays between
// changing motor speeds during autonomous
drive.setSafetyEnabled(false);
// Your autonomous code
// Optionally turn drive safety feature back on (if you want it for teleop)
drive.setSafetyEnabled(true);
Alternatively, you can break your time delay up into smaller chunks.
Our team leaves the drive safety feature disabled for the entire match and rely on manual intervention to hit the Enter key when we need to disable a run away robot.
The first important question is whether you’re using SimpleTemplate or IterativeTemplate. If you’re using SimpleTemplate, then your only problem is Motor Safety. If you are using IterativeRobot, you will need to restructure your code to remove the delays.
I am using the SimpleRobot class. It turns out that I did turn safety off. My robot does nothing in autonomous. The robot works great in TeleOperator mode. I must have missed something else.
I have another related question. I want to use the method myDrive.mecanumDrive.Polar(x,y,z) in my autonomous method. Please explain the three numbers x,y,z. What does each do to the robot?
RobotDrive#mecanumDrive_Polar() takes input in the form of polar coordinates, as opposed to RobotDrive#mecanumDrive_Cartesian() which takes Cartesian (Rectangular) coordinates. The three parameters for RobotDrive#mecanumDrive_Polar() are as follows:
You can find information like this in the Javadocs in the sunspotfrcsdk directory.