Quote:
Originally Posted by Greg McKaskle
Is this reproducible? I wasn't able to provoke it.
|
Yes, 100% reproducible for us:
Attach all devices (see below), boot up, DS opens in Driver. Once stable, close lid. Wake system up. DS software will not recognize I/O board at this point. Restarting DS software (Driver Log-out, then back in, or even going to developer and running there) does not matter; it still will not find it.
Quote:
|
How are devices connected to the USB, what is right, left, and what is on the hub?
|
The cypress, the two 2009 Kit joysticks, and the STOP button are all plugged into the hub, which is plugged into the right port. Nothing is in the left port (due to physical constraints).
Quote:
|
Finally, is it possible that the FT is drawing too much current or is shorting out?
|
Given this configuration, too much current is possible I suppose. But Windows / Classmate USB subsystem is not shutting the port down as would be typical for over-current. The joysticks and e-stop on the same port continue to function and be recognized by the DS.
But, if we never suspend the system it works fine (throughout an entire day of competition). In addition, the board has LEDs attached to it which do light ("randomly" as they don't get robot-originated commands) even in this condition.
It is not shorting out.
How does the DS do recognition of the Cypress? Could this be some sort of race where the board may not be fully re-initialized/woken up sufficiently when the DS looks for its presence again? Does it look for it when you do the F1 re-enumeration? Pretty sure we tried that, but would try it again if this is the case.
We can also try changing the hook-up scenario and report back.