Joysticks

[theawesome1730]

Originally Posted by LedLover96

No, it isn't. The KOP joystick is a Logitech Attack 3, this is an Extreme 3.

While similar, the Extreme 3 has an extra button and a mini-joystick (I don't know the correct term) on the top. Plus this has a twist stick, the KOP one does not.

Hope this helps!

Ah, I see, our team never uses the KOP joysticks, we get the Extreme 3Ds and store them with the KOP stuff.

[apalrd]

Having driven with a few types of joysticks and gamepads, the Logitech Attack 3's are my least favorite by far.

Over the past 3 years, we've used:
-Logitech DualAction gamepad (all three years)
-Logitech F310 or Xbox (identical functionally, F310 is better to me, two years)
-Custom Cypress-based box (never will use Cypress board again)
-Custom box based on Logitech Precision (no analog inputs, otherwise very good)
-Custom box based on uHID (very very good, would use uHID again)

I personally prefer the (very old) CH Flightsticks in terms of actual joysticks, as I like the spring feel much more than that of the Attack 3.

I would highly recommend the Logitech Dual Action and F310 gamepads, as well as the uHID, to any team.

[marccenter]

Andrew,
Is there anything special one has to do to use the Logitech DualAction gamepad with the base FRC Labview software?

[apalrd]

No.

Left stick shows up as axis 1 and 2 (X and Y respectively), right stick shows up as axis 3 and 4 (x and y again), and D-pad shows up as axis 5 and 6 (it's binary, so it will be either 0, +1, or -1 for each axis).

All of the buttons are numbered on the joystick, and correspond to the same number in software. L3 and R3 (pressing the joysticks) are buttons 11 and 12, they are not labeled on the joystick. I attached a pair of LabVIEW controls for the mapping of the buttons and axis, if you cast the LabVIEW Joystick Get clusters to these two controls, it will name all of the buttons correctly.

The F310 and 360 have identical button/axis mappings. See attached 360 files. Please note that L2 and R2 (buttons 9 and 10) are actually unused, I have some code that gets a digital output from the analog triggers (axis 3 is the raw trigger data fro L2 and R2).

(I had to zip them as CD does not allow uploading of .ctl files).

[PAR_WIG1350]

We took the KOP joysticks and unscrewed the two halves of the actual stick portion and unplugged the wires from the PCB, tucked the end of the cable into the stub-stick that remained, and wrapped it with rubber tape. it takes a bit more force to actuate as a result of the shorter lever, but it is much shorter, also, the cable could be attached to a custom button array either on-stick or off by simply replicating the circuitry of the original PCB, or at least the parts you need.

[BEEKMAN]

I've been using the Cyborg for a few years now:

http://www.amazon.com/Saitek-Cyborg-.../dp/B001EYU1VO

the WPILib joystick don't let you use all of the buttons, but if you write some custom objects/dashboard you get full functionality. it has more buttons than you'll ever really need, and its fully customizable