Joysticks not reading

[MaGiC_PiKaChU]

are you trying to deloy your code with eclipse? That might not work at all, go back to netbeans

[Poseidon5817]

Originally Posted by MaGiC_PiKaChU

are you trying to deloy your code with eclipse? That might not work at all, go back to netbeans

I'm sorry, I am in Netbeans, exactly as it was on kickoff day. If I upload the old robot project, the joysticks read properly.

After a quick check, the Joystick instance is non-null, it is being created, but it is only returning 0's.

I am using a red Afterglow Xbox 360 controller.

[MaGiC_PiKaChU]

Have you tried printing values in autonomous init? robot init? just to have a look if your code actually runs

[Poseidon5817]

robotInit() runs. I haven't tested autonomousInit(). It still works in old projects but won't work in this one.

[GeeTwo]

As I recall, the axis numbers changed from 2014 to 2015. Oh well, joystick axis 4 appears to be the horizontal on the right joystick both years.

Is your controller perhaps mapping to a different number than control 1? Have you tried 0 or 2 as the argument to new Joystick() in robotInit? Actually, even easier as you seem to have the hardware, you could try plugging in "multiple different controllers" at the same time and see if any of them works.

[Poseidon5817]

Originally Posted by GeeTwo

As I recall, the axis numbers changed from 2014 to 2015. Oh well, joystick axis 4 appears to be the horizontal on the right joystick both years.

Is your controller perhaps mapping to a different number than control 1? Have you tried 0 or 2 as the argument to new Joystick() in robotInit? Actually, even easier as you seem to have the hardware, you could try plugging in "multiple different controllers" at the same time and see if any of them works.

I've already tried all of that, with gamepads, Xbox controllers, and actual joysticks. All of them had the same issue.

[MaGiC_PiKaChU]

also, the joystick mapping start at 0, so try changing your joystick port on your DS in the usb section

[GeeTwo]

Did you back-load (or do you still have) the 2014 driver station software installed on your classmate/laptop, or are you running 2015 driver station? I understand that there were significant protocol changes from 2014 to 2015.

[Poseidon5817]

I am running the 2015 DS with the option for 2014 DS and FMS mode selected.

[Pault]

Originally Posted by Poseidon1671

I am running the 2015 DS with the option for 2014 DS and FMS mode selected.

That doesn't seem to be what that mode is supposed to do.

From the wpilib screensteps documentation:

FMS Protocol - This controls which version of the DS to FMS communication protocol to use. This control is only needed when connecting to a 2014 FMS such as at a Week Zero event, where it should be set to '14. This control will reset to '15 (the setting required for 2015 Competition Events) each time the DS is started.

[Poseidon5817]

Regardless, the joystick reads in our main program (although axis mapping is messed up), but not this one.

[GeeTwo]

Originally Posted by Poseidon1671

Regardless, the joystick reads in our main program (although axis mapping is messed up), but not this one.

By "our main program", do you mean the driver station? If so, then that's what Pault was saying would happen. It appears that the legacy mode is only for connections via the FMS, not direct connections. Here, it's not FMS that is the old version, but the robot computer. I believe that you will have to run the 2014 driver station or a work alike.