In the connectivity palette is a submenu of VIs for querying HID devices (Human Interface Devices). It should list the mouse, keyboard, and your joystick(s). There are also VIs for opening a connection and reading the button and axis and POV state.
If you want to use it with the Control system for a FIRST robot, this is quite easy to do. We have a Logitech gamepad for our team to and it works great. Just acquire data from it the same way you would a normal FRC joystick. The buttons and axis will be switched around though, so I suggest you make a test program to see which buttons react to which default button number.
On another note, the Logitech gamepads I’ve used in FTC (I know, different realm, but might still be relevant) have always reported negative values from what you’d expect. This might just be signing issues with the NXT/FTC Toolkit, I don’t know, but do watch out for that.
Also, as RoboMaster said, the buttons and axes may not necessarily line up how you expect them to. I would suggest making a “wrapper” VI to simplify usage, basically a custom-made VI that contains the regular VI, but outputs the pins to the correct configuration for your gamepad. Then name it something like Gamepad.vi so you can use it more intuitively.
Daltore:
It appears to work mostly as expected; the axis are polarized intuitively, the buttons correspond correctly. However, the right joystick is the “z axis” and “z rotate”, while the left joystick is “y axis” and “x axis”.
Here is a chart for the Logitech Dual Action controller. Tested in lab view code which i will be more than willing to give out the .vi if anyone wants it(id post it if i knew how). http://tinyurl.com/y9sx84c