Problem with Auto
 

Our auto program won't run correctly. We are simply trying to drive forward and fire a piston. once in a while it runs fine, but then the drive motors wont fire but the piston does. We are using the WPI mecanum auto VI in Lab view.
Any ideas?

Re: Problem with Auto
 

Are you using encoders on your drive, or a timer?

If you're using encoders, are you resetting those values to zero before you start your auto mode?

-Nick

Re: Problem with Auto
 

Is motor safety enabled? (If you haven't explicitly disabled it, then it probably is). Are you getting any errors on the driver station/netconsole?

The motor safety feature will stop running the motors if you are not constantly feeding it values for motor speeds, and will say something like "Output not updated often enough" if you set the motor to full speed once, and then wait a while and stop it.

Re: Problem with Auto
 

Especially if you are using a Jaguar

Re: Problem with Auto
 

The safety vi was disabled before we started programming autonomous. I'm curious why autonomous doesn't work, but teleop does, when the motors are referenced the same way for both. We are programming using labview and we are using jaguars for the drive system.

Re: Problem with Auto
 

Are there any error messages on the driver station (under the diagnostics tab) or on the netconsole?

Re: Problem with Auto
 

Probe your error wires and see what they return.

Re: Problem with Auto
 

We can share plenty of ideas. Since we don't see your code, we can't know whether any of those ideas are good ones. Show us your Autonomous vi and help us help you.

Re: Problem with Auto
 

Here's a photo of the code. We literally enabled one of the stock structures already in the Autonomous code and added a solenoid. The added solenoid code works, the default drive code doesn't.

Re: Problem with Auto
 

Are you actually using a Mecanum drivebase?

Is your drive motor reference in Begin named "Four Motors"?

Re: Problem with Auto
 

yes and yes. The motors will turn as programmed sometimes but it's really inconsistent. They will usually only turn once every time we load the code to the cRio, and generally it does not work the first time we enable the code. We don't have the code actually burned to the cRio yet so could that have something to do with it?