Driver station only regognizes USB 1 and 2

Technical Programming
1

So on our bot, we decided to have 4 joysticks. 2 for the driver, in tank mode, and 2 for the person handling the ball mechanism. Driver gets USB1 and USB2, and ball handler gets USB3 and USB4.

I spent hours today trying to figure out why when I go all the way to -1 on the USB3 and 4 joysticks, nothing happened… Then I just set up the motor VI with a constant of -1, and it ran. Then I hooked up the joystick indicator to a display, and realized that the joystick wasn’t talking to the program.

I tried too many things to list in order to get it work. Several reboots, switching around joysticks, and can’t find a way around it.

Anybody have any ideas on why it’s doing that? I’m pretty much stumped.

2

You turned off the driver station before you plugged in the joysticks right? You cant plug them in after it already has power. Hope that helps

3

Yep, I had all 4 plugged in, cut power for 10 minutes to take a lunch break, came back, and the same thing happened.

4

Did you swap the joysticks around to be sure it isn’t a joystick failure?

5

If you’d like to post your code, I’m sure someone will take a look at it. I suspect that’s probably where the issue is.

6

I did swap them, and had the same issue. I even plugged them into the computer to verify that they work… they do.

Not really sure how to share labview code, in php I’d just copy and paste… so I’ll screenshot it, I guess. Don’t mind the random uncompleted code, I’m attempting to implement traction control and figure how to make buttons execute code. Got to tackle one thing at a time, though.
When I attempt to use USB 3 and 4, the following is what the numeric indicators read:
Numeric 5: always zero
Numeric 6: always zero

http://img520.imageshack.us/img520/3521/labviewmo6.png

7

You could always try re-imaging the DS with the .BIN file they gave, it might just not have updated properly.

8

Try running the “Joystick Input Example” (unmodified) and test each joystick with known good code.

If you get Joystick 3 to respond, then the problem is in your code (maybe you are not opening the joystick?).

Regards,

Mike

9

The code seems pretty straight forward.
To eliminate it as a possible source I’d try a default template switched to use USB3 then USB4, then post your results on the FIRST forum where they can make a determination if the USB ports are bad.

P.S. What Mike said :slight_smile:

10

Actually, this was one of the first things I tried.

Tried doing that too, but I’ll have to try the posting on the FIRST forums part.

I’ll try that tommorow. I don’t know if we updated the driver station when we updated the cRIO, or if that even matters, but hopefully it’ll give us some results.

11

Not exactly on topic, but i see that you are using 12 Boolean indicators to show the different buttons on the joystick. Might i suggest just creating an indicator on the output to the “Get Raw” VI (the pink wire), and it will be much less cluttered and you can still see each separate button on teh frontpanel.

12

Out of curiosity, are your joysticks already opened in the begin.vi?

You’ll probably have this issue if you reopen those same joysticks again.

13

I actually haven’t looked into any other vi’s yet, just the sub-vi’s. I’ve just been messing with main.vi. I’m not sure right now, I don’t have access to labview right now, but I think begin.vi is only in the advanced framework?
Speaking of which, I tried the advanced framework, and the joysticks still do not work.

14

Sorry, my mistake, I didn’t realize you weren’t using the advanced framework. That’s the only one I’ve been spending time with.

15

We just tested three joysticks with the basic framework, and all worked. If a simplified example will not work after a reboot, I’d diagnose it as a HW problem.

Greg McKaskle