Buttons and Pneumatics Help

[Alan Anderson]

Originally Posted by RedWolf55AJ

what is even worse is that mysteriously, the right side of the robot stopped working, without any changes in code that I could see. Fearing a joystick problem I swapped the joysticks in USB Ports 1 and 2. The Right Jaguar Speed Controller remained inoperative regardless of the joystick. When I did reach into the code to switch which USB Port fed which side of the "Tank Drive" VI, the problem then switched to the other motor/jaguar. I fear that somewhere between "Open Joystick" (USB 2) and "Close Joystick" USB 2 some input is being lost. Can anyone help me with that? I really only have one more day to work on this thing and I'm fighting time.

The code pictures you posted are not clear enough for me to follow the connections. You can debug a running program by clicking wires and placing a "probe" to show the live value on that wire; maybe that will help you determine where the fault is.

[RedWolf55AJ]

Alright, this is now officially ridiculous.
I'm working with the code the we(huskyrobotics is a team account) had yesterday and now the robot will not move at all. when I probe the connections, I see an obvious problem in the Get Axis VIs.

The Front Panel of the "Get Axis" VI is now reading USB 3 instead of USB 1. I have 2 instances of my "Get Axis" VI running, but on the Front Panel, I see 2 near-identical diagrams. One says USB 3 in serveral spots and the one below it says USB 2 in those same places. I need the USB 3 changed to USB 1 Please.

Now when I probe the connection between the 2nd "Get Axis" VI and the other input of the Tank Drive system, I get no recorded input, as if there is no controller there. At all.

This is ridiculous and my team and I are at our wits end pondering why it does not work. Screen schots will be up momentarily

[airnate]

Be aware that if you are calling a subVI from multiple places in the program, it can be misleading to open the subVI and view its front panel to try and understand what is going on because you may or may not see all of the data that is flowing through the subVI. The data may move to quickly for the screen to update and display every piece of data.

For instance if the system alternately calls the GetAxis with USB1 and then with USB2, you may, or you may not see the alternating USB1 and USB2 values. Depending on the timing, you might see just one, or the other, or both at different times.

Also, since your diagram is large, it may be easier for us to diagnose your actual code than screen shots of it.

[RedWolf55AJ]

Originally Posted by airnate

Also, since your diagram is large, it may be easier for us to diagnose your actual code than screen shots of it.

how would I post the code instead of these screenshots then?

[airnate]

Just zip it (in Windows explorer, right click on the folder or file you want to compress and Sent To->Compressed (zipped) Folder or file.

Then upload the zipped file or folder.

[RedWolf55AJ]

Alright, well, my team decided to try and clean up/clean out our old code, with a heavy emphasis on following the LabVIEW examples that we were provided with. With that said...

[airnate]

The first thing that I notice is that you are using Controls to specify which channels you are using. You should right click these and Change to Constant because otherwise they will revert to the default value of the control when you deploy a stand alone executable and reboot.

Other than that I don't see functional problems with the code.

Aesthetically you should separate your subVIs on the diagram so it's clear where the wires are going. You want to expose all the wires and try not to cover any of the wires up when possible.

Are you still having functional difficulties?

[CHSboy]

Hey, I was looking at the pictures of coding from the attachments, and I was wondering, how do you get the status thing coming from the compressor enabled vi's error out, and how do you get the TF status things that aren't selecting true or false like the others. Sorry if this sounds somewhat stupid, but it's over my head.

[Joe Ross]

Originally Posted by CHSboy

I was wondering, how do you get the status thing coming from the compressor enabled vi's error out

The status is using Unbundle by Name to pull the status Boolean out of the error cluster. You can access it in programming -> Cluster, Class, & Variant -> Unbundle by Name.

Originally Posted by CHSboy

and how do you get the TF status things that aren't selecting true or false like the others.

I think you're referring to the indicators. You can right click on any output on the block diagram and choose create -> indicator, which will create an indicator of the correct type on the front panel. You could also make an indicator on the front panel, and then wire it on the block diagram, for example, using a round LED. A Boolean indicator will normally have a picture of an LED on the front panel, but if you right click on it and unselect view as icon, it will use the same type of picture as the screen shots above.

[CHSboy]

Is the indicator on the "or" icon that has the arrow and green fill on the false side from the x input or x or y output?