USB ports going away during match

[BitTwiddler]

Not sure if it makes a difference but we use two Logitech controllers, one for the driver and one for the operator. As far as I know, they both drop out at the same time.

[Boltman]

We fixed our usb issues in Ventura with simple "Power Option" setting changes on the windows laptop there are main ones and ones specific to USB ports in the advanced area.

[marshall]

Originally Posted by BitTwiddler

Not sure if it makes a difference but we use two Logitech controllers, one for the driver and one for the operator. As far as I know, they both drop out at the same time.

That's interesting and useful info. If that is the case then that to me points to either a software fault or a more upstream hardware fault like the USB controller within the laptop.

As I said though, we've seen it happen to us and it is typically one controller that drops and it is because of a faulty cable. I've been able to repair a handful of the controllers but it is typically more cost effective to recycle it and then buy a new one.

[kiettyyyy]

Most of the fixes that I've done for teams was to change the power settings for the USB port.

To clarify, the issue is not isolated to gamepad controllers of a specific brand. This can happen to ANY joystick device.

[MrForbes]

Actually one of the controllers was dropping, and the other stayed "lit up" on the DS display. And we changed the dropping controller with another one during one of the last matches, and the problem persisted, with no apparent change.

We can look at power settings, but I'm a bit confused why something like that would make the USB port come and go several times during a match, while the control is being used continuously? Although I do understand that Windows works in strange and mysterious ways.

I wonder if this is the advanced setting? btw this is on my desktop, which also runs Windows 7. I could probably end global climate change by leaving the setting as is, rather than allowing the pesky USB hub to run all the time!

[kuraikou]

We were having the same issue at AZ East but we fixed the issue by triple checking the connection before every match and being ready to replug and rescan at the beginning of each match. Our issue was caused by bad USB ports and cables on our ps4 controllers, so we got new cables and that helped significantly.

[evanperryg]

Correct me if I am wrong, but I believe 2451 may have been having a similar problem at Midwest, that caused them to withdraw from alliance selections.

[Jared]

Here's a few ideas:

-Turn off the power save setting. This has caused similar problems for some teams in the past

-Uninstall and reinstall the USB driver

-Make sure that there is no other USB device that could be shorting the USB 5V supply.

-Make sure the contacts on the USB connectors are not corroded or dirty

-Make sure the USB cable fits snugly. If it doesn't, you can try gently crushing the joystick connector so that it has a better fit.

-Make sure the laptop is plugged in when you're driving.

-Make sure the laptop battery is healthy. Bad batteries can cause really weird things to happen.

-Uninstall/Reinstall the USB driver

-Disable your wireless adapter and bluetooth (if you have it). Sometimes the bluetooth adapter connects to an internal usb port, and may be causing issues.

[popnbrown]

Originally Posted by evanperryg

Correct me if I am wrong, but I believe 2451 may have been having a similar problem at Midwest, that caused them to withdraw from alliance selections.

I believe they were having issues with their roboRIO and software on the robot itself. I don't think it was a driver station issue.

[orangemoore]

Originally Posted by popnbrown

I believe they were having issues with their roboRIO and software on the robot itself. I don't think it was a driver station issue.

It was some kind of RoboRio related issue. I don't believe it had to do directly with their driver station.

[autox_vette]

Originally Posted by evanperryg

Correct me if I am wrong, but I believe 2451 may have been having a similar problem at Midwest, that caused them to withdraw from alliance selections.

The stimulus of the problem WAS the joysticks (I'm not sure if one failed, or if it just got unplugged moving the drivers station around), but the real problem was a programming issue which caused the application to die immediately upon entering teleop. The thrash to find the problem then introduced other issues which clouded the issue and sent everyone down wrong paths (multiple times).

Kenton Cabiness (Aka. Mr. C)

[BitTwiddler]

We found another interesting "feature" of Windows called "USB Selective Suspend" that allows Windows to power down an individual USB port. We disabled that potential troublemaker. Google it to find out more.

[kiettyyyy]

Originally Posted by MrForbes

Actually one of the controllers was dropping, and the other stayed "lit up" on the DS display. And we changed the dropping controller with another one during one of the last matches, and the problem persisted, with no apparent change.

We can look at power settings, but I'm a bit confused why something like that would make the USB port come and go several times during a match, while the control is being used continuously? Although I do understand that Windows works in strange and mysterious ways.

I wonder if this is the advanced setting? btw this is on my desktop, which also runs Windows 7. I could probably end global climate change by leaving the setting as is, rather than allowing the pesky USB hub to run all the time!

Jim, this is the setting that you'd be looking for.

[MrForbes]

Thanks for all the suggestions, everyone!

We have several things to check. We have not been plugging in the DS laptop charger during matches, it's been running on battery all the time.

I don't have the laptop here, hopefully it made it home on the bus Saturday night, and I can check it in an hour or so when I drop off the robot at school.

[Alan Anderson]

Originally Posted by MrForbes

We have not been plugging in the DS laptop charger during matches, it's been running on battery all the time.

Failing to take advantage of the provided power at the field is not a good idea. It's too easy for Windows to kick in power-saving features if you're not plugged in. And if you do successfully disable them all, you're going to run down the battery much faster than "normal".