LabView code of other teams ?

[Alpha Beta]

Originally Posted by eren96

Hi,

My main role in the team is programming and I've been learning labview for a few weeks. I have read many pdf s and watched tutorials, but the way how i'm going to program our robot isn't enough clear in my mind yet. I need to control 2 super shifters with 4 CIM in drive train, 2 pneumatics pistols and 2 CIM in other systems. All systems is going to run in Autonomous Mode as well.

I think If I had some example robot codes from past years including controls like above, It would be great to understand and make other things clear in my mind. Any help would be ok.

Thanks from now.

http://www.chiefdelphi.com/media/papers/2874

In BEGIN you'll see how to start single and double action solenoids as well as how to set-up a 4 motor drive.

In FINISH you'll see how to end each of those things.

In TELEOP we just read the state of our driver controls and write them to global variables. We used button 3 for shifting and button 2 to control our arm moving up and down. We also read the X and Y joystick axis to pass along to our drive loop.

In PERIODIC TASKS/TIMED TASKS you'll find us reading the global variables. The X and Y joystick variables are read in the drive loop. You can ignore the logic involving the "SkySwitch".

When reading the button 3 variable you'll notice some logic used to toggle so the driver doesn't have to keep the button pressed to stay shifted. Ignore the "shift overide" logic. After the toggle we set the state of the solenoid. Single action solenoids are set to either off or on.

Our appendage on button 2 is set up in a similar fashion with a toggle. Again, you can ignore the intermediate logic. You'll notice that the double action solenoid is set to either forward or reverse instead of off or on.

During AUTONOMOUS we write to the same global variables that the driver's controls write to during teleop. If we wanted to lower the appendage we would write button 2 to true which simulates a driver button press. To raise the appendage we have to write it false (simulating the driver releasing the button) than write it true again (switching the output state of the toggle).