waits

[Mark McLeod]

That will start the motors, while the Wait twiddles it's virtual thumbs letting them run for one second, before leaving the frame.

Of course, the way it's written, nothing stops the motors, so after the frame finishes executing the motors will still be running and will continue to run until told otherwise.

[tilky]

ok think i got it now. thanks

[Alan Anderson]

Originally Posted by tilky

so will this run the motors for 1 second, or will it pulse the motors once, and then wait 1 second before moving on

It will tell the motors to run, then wait one second. It doesn't keep telling the motors to run after it's done it once. For most motors, that means they will continue to run, but not for Drive motors.

Originally Posted by Mark McLeod

Of course, the way it's written, nothing stops the motors, so after the frame finishes executing the motors will still be running and will continue to run until told otherwise.

It's a Drive function, so the motor safety will stop the motors after a tenth of a second unless something has been changed from the default configuration.

[Mark McLeod]

True enough.
What Alan means is, your structure would work the way you intend for individual motors, but drive motors (Open2Motor, Open4Motor) have an automatically applied Safety that will shut down the motors if you don't keep rapidly telling them what to do.

To make your structure work the way you intend it would need an extra vi call.
And at the end you would re-enable the Safety, before Teleop began, as well as set your motors to neutral.

[tilky]

ok, so this way i don't have to use for loops every time i try to drive in autonomous

[tilky]

one more question: is there a way to get the time from the driver station? The wait time is not at all accurate, and it would be easier than using encoders

[Alan Anderson]

In my experience, the wait time is very accurate. How are you finding it not to be? What time are you looking for, and what do you intend to do with it?

[Greg McKaskle]

You can send the data from the DS, but that will require a bit of networking.

The Match Info that is an input parameter to the teleop should be pretty accurate, and show should elapsed times. How are you testing to determine they are "not at all accurate", and how much error is that?

Greg McKaskle

[tilky]

i tried firing solenoids once per second and it seemed like it was once every 3 seconds.