Using a (Logitech) Controller?

[ctccromer]

Originally Posted by Mark McLeod

Your program is only a sub vi and won't perform on it's own.
It's missing some essential stuff like communication with the Driver Station that reads the joystick.
You also need to have the Driver Station app running along with your LabVIEW session.

It would be easiest if you created a default robot project, from the Getting Started window, then added your code to the project.
The default project has most of what you need already, including one joystick.
We can walk you through the steps to take. For example,

1. Create a Robot Project (inserting your team number into the IP address)
2. Expand the Team Code folder
3. Edit the Teleop.vi block diagram
4. To begin with use just the Joystick that is already there to display it's buttons.
5. Open the Robot Main.vi
6. Press the Run arrow to start your project
7. Plug your game controller into your laptop
8. Start the Driver Station app.
9. Go to the Driver Station Setup tab and see if the game controller is listed on the right in the first/top position. If not then click and drag it up to the USB 1 spot.
10. Enable the Driver Station.
11. Go to the Teleop front panel to see your button displays.

This is the general format to use a joystick


Take a look at some of the NI tutorials at: https://decibel.ni.com/content/docs/DOC-8923
The [FRC 2013] FRC Robot Framework Tutorial would be a start.

Thanks for the detailed help! I tried doing this however, after I deploy the code to the cRIO and open the drive station, it says I lose connection with the cRIO and boots me. Happened two times so far but I'll try it more with another cable after school.
Also, running RobotMain.vi does not show the lights that I linked to the 12 buttons of joystick 1 in teleop. Should I run teleop.vi instead of RobotMain.vi?

[Mark McLeod]

You start the run from RobotMain because it's at the top of the calling tree and starts everything else, so for instance, Begin.vi gets called to open all your devices before Teleop gets called to handle your driver controls.

Then you switch to the Teleop front panel to watch the indicators you added.

You should be running both LabVIEW and the Driver Station from the same laptop, same account.
Don't switch accounts or anything like that.
It is also possible to run the Driver Station on a separate computer and the LabVIEW from a programming laptop. You just have to make sure the IPs don't conflict, e.g., the Driver Station computer is 10.37.53.5, and the programming computer is 10.37.35.6

[Greg McKaskle]

You will need to run RobotMain, and then on the driver station panel, enable the robot in teleop mode.

This is more complicated than it would need to be to simply read from a joystick, but that is because it is assuming that your purpose in doing this is to safely drive a robot on a FIRST field.

The DS actually reads the joysticks and communicates it to the robot. Your code reads the joystick settings from the robot service, and then you can turn on motors, etc. The DS and robotMain framework also control which code on your robot is actually executed and whether it is allowed to turn motors.

Greg McKaskle

[ctccromer]

IT WORKED! HUZZAH!! I wish yall could have seen my reaction

I think my issue earlier was that the power cable from the cRIO to the Power Distribytion Board is.. less than reliable. However this time I was able to MAKE SURE nothing happened, so I didn't lose connection to the cRIO, so it worked flawlessly I was able to note which buttons corresponded to which "Buttons" in LabVIEW via the LED Lights vi.

Thank yall very much for the help (and patience). I really do appreciate it