Compressor and Pneumatics help for 3329
 

We are using Labview. We are nubes at this so lots of help would be usefull. We are having trouble with our compressor and pnuematics system - for some reason our compressor was working but we ran into trouble. We put our Compressor Open.vi >> Compressor Start.vi in the periodic tasks inthe 100ms loop. It worked for a while until We programed our solenoids in the teleop code (by setting the soleoids with the joystick buttons - we have a duel solenoid valve) and then we got error codes: -44027 and -44046. It says the DIO module has already been allocated but our set up for the compressor is correct. We're really confused!!!! Please somebody help!!

-- thanks --

Re: Compressor and Pneumatics help for 3329
 

Big problem - Put the Compressor Open in Begin. It has already allocated the compressor in a previous loop, so you can't open it more than once. You can put a Start in Begin then set a refnum and pick it up in PeriodicTasks to Start.

Re: Compressor and Pneumatics help for 3329
 

HEy thanks! We tried that already but the watchdog started misbehaving. And thats where we are lost. It doesn't show that message anymore but the compressor still isn't starting

Re: Compressor and Pneumatics help for 3329
 

Hey again! I tried what you said again and its giving us error code -44027

I put the Get refnum.vi >> Compressor start.vi in the 100ms periodic tasks loop. I'm still not sure on what to do
Also I just deleted all watchdog references so i wouldn't get any trouble with it
ps: thanks for responding so quickly:o

Re: Compressor and Pneumatics help for 3329
 

In Begin.VI:

Open Compressor (configure the DIO Port, DIO Slot, Comp Slot, and Comp Relay) -> Compressor Start -> Compressor Set Refnum (name it "compressor" or something like that)

In Periodictasks OR Teleop:

Compressor Get Refnum (same name as before) -> Compressor Start -> Compressor Enabled State -> Indicator of Compressor Enabled State and Compressor State (those help with debugging - make sure the terminal for the indicators is in the loop with the Enabled State.



Run Robot Main.vi by pressing the play button. When it is done downloading and you have Teleop Disabled on the Classmate (with stop button, comm, and code), open Periodic Task.vi and look at the front panel. Compressor Enabled State should always be TRUE, and Compressor State should show what the compressor is doing. Then, enable it. The compressor should turn on.

Whatever you do, do NOT open the compressor more than once. You can use Start more than once, but NOT open. That will throw that DIO Cache error.

Do you have a Watchdog Feed in Teleop? Another thing I recommend - Call Teleop.vi from Disabled.vi. Then, you can see what the code is trying to do without letting it do stuff. Once the code is running from Robot Main (Teleop Disabled on the Classmate) you can probe wires and see what is happening. Be warned - Probing a wire before Robot Code is green will almost certainly cause LabVIEW to crash. Make sure Robot Code is green before probing. When you are done with the probing and indicators, you can do a full Build and Deploy. You must do a Build and Deploy to save the code permanently, so it is required at competition. Generally. I do a full deploy every time I leave or am done debugging.

One more reason for Watchdog errors: Do you have any WAIT's in Teleop, for something like kicker timing? That is a big no-no. You can run your kicker timing loop asynchronously (e.g. Periodictasks or something of the like) and communicate via global variables if you would like.

Re: Compressor and Pneumatics help for 3329
 

While you can call the Compressor Start VI more than once it really isn't necessary unless you called Compressor Stop for some reason.

Compressor Start launches a separate thread to handle the compressor which will run straight through Autonomous and Teleop just fine.

Re: Compressor and Pneumatics help for 3329
 

Thanks ALOT!!!!!!!!!!!!!!! I'll give it a go and see if it works... Thanks !!!!!!!!!!!

Re: Compressor and Pneumatics help for 3329
 

Ok. I tried it and there is now a comm error with the camera (-44003)

Should I delete the Camera script all together (if another option is possible that would be splendid)

Thnx