This page is archived and will no longer be updated by National Instruments.
1. Set Up - Resources
LabVIEW Development Suite for FRC 2014
Imaging cRIO & Windows IP Configuration
Troubleshooting cRIO connections
2. LabVIEW Basics - Resources
Learn LabVIEW - Video Training
3. Vision, PID, & Simulation Resources
4. Advanced Programming Resources
Full FRC LabVIEW Training (Beginner & Advanced) 4.5 hrs each
It seems that the 2015 Joystick Palette has replaced the Get VI with a Get Value VI. The Get Value VI outputs an array (instead of the cluster output I saw last year). Is there any documentation listing & accessing the position of each buttion/axis in the array? If so where can I find it?
Thanks.
Follow up
I found that I could map the buttons and joystick axises using the simulation tool. I am still interested in knowing if there is any official documentation.
There is also a VI in the Joystick Palette called Get Info that will tell you about your joystick. We recommend you use that to find the Axes.
The buttons are simply in the same order as last year. Naturally since the buttons are in an array (0-based index) you have to subtract 1 from the number printed on the joystick buttons (1-based index).
This is the porting guide. It's really helpful
http://wpilib.screenstepslive.com/s/4485/m/13811/l/292165-labview-porting-guide-2014-to-2015
So we now have to manualy find the axes then use the index number instead of having labled clusters?
So you tried both ways and neither worked? If you can upload some screenshots of the code in question, I can look and see for you. It's always hard to understand the problem without context.
Thanks,
Nick
Sent from my iPhone
.png)
Alright, sorry it took me so long to get back to you, but I finally got a
chance to take a quick look. Anyway, from what you've shown me, you are
using the "unbundle cluster" correctly, I think any problems you are having
are on the logic end of the program. So, for example, if your power is not
at what you desire, up the numerical values you are feeding to the motors.
Also, you probably noticed by now that you have to hold the buttons to get
them to work. That is because you are using simple case structures; these
reset every 10 milliseconds with the rest of the teleop VI. If the buttons
you assigned are not working correctly, that could also just be a simple
case of misunderstanding which button corresponds to which on your
controller (I've done that a million times).
I hope this all makes sense. Feel free to ask any more questions if you
still need help.
- Nick
It all makes sence and thank you for the help. Ill will play around with the code. This help means a lot to me.
-Calvin
I did do something like that than I found another example online that showed me that code. So I wanted to try it out to see if it would work. But here is what I origanally done..png)