Bit of coding help

[SoulSaber1]

For some reason this isn't working either. did you mean like this?

case 7: //ALL SENSORS ON *OR* MAYBE AT CROSS
                        if (time > stopTime)
                        {
                            atCross = true;
                            speed = 0;
                            gripper.set(false);         //Closes gripper
                            gripper2.set(true);         // "     "
                            drive.arcadeDrive(-.5 , 0);
                            Timer.delay(1.0);
                            drive.arcadeDrive(0 , 0);
                                                                }

[JosephC]

Originally Posted by SoulSaber1

For some reason this isn't working either. did you mean like this?

case 7: //ALL SENSORS ON *OR* MAYBE AT CROSS
                        if (time > stopTime)
                        {
                            atCross = true;
                            speed = 0;
                            gripper.set(false);         //Closes gripper
                            gripper2.set(true);         // "     "
                            drive.arcadeDrive(-.5 , 0);
                            Timer.delay(1.0);
                            drive.arcadeDrive(0 , 0);
                                                                }

Okay so I can see one clear problem here I think.

Timer.delay is generally in milliseconds so you have it going backwardsfor 1 millisecond then stopping. Try increasing Timer.delay to a greater value, say 500, then try it again.

Remeber if it goes berserk and doesnt stop for some reason you have a stop button.

[Egg 3141592654]

Timer.delay is generally in milliseconds

Timer.delay for wpilibj is in milliseconds, so 1 second would be

Timer.delay(1000);

[Robby Unruh]

Originally Posted by Egg 3141592654

Timer.delay for wpilibj is in milliseconds, so 1 second would be

Timer.delay(1000);

The javadoc only says this:

delay

public static void delay(double seconds)
Pause the thread for a specified time. Pause the execution of the thread for a specified period of time given in seconds. Motors will continue to run at their last assigned values, and sensors will continue to update. Only the task containing the wait will pause until the wait time is expired.
Parameters:
seconds - Length of time to pause

Note; "seconds". I'm pretty sure it's just in normal seconds. So one second would be

Timer.delay(1.0); // only accepts doubles as an argument

My team has had no problems using this, as opposed to using milliseconds(?).


However, when using other functions in the Timer class, like get(), it will return in microseconds. For our minibot deployment, we start a timer and have a condition timer.get()/1000000 > 110, if true it will deploy. If false, it'll let the user know you can't deploy yet.