Forum Replies Created
-
After several hours of a deeper dive into USB than I thought I’d ever do, I have discovered and solved (well, sort of) the problem — The short version is that there is some kind of USB 3.0 incompatibility. I can elaborate if you care. Basically, it does an enumeration of devices when it notices the new one, then asks it for its description. I can’t tell why that is failing, but it looks like there might be a timing issue or the Intel USB3 chipset is impatient, because it terminates the request, deletes the logical device constructs, and tries again (and again).
My jury-rigged solution was to put an old USB 1.0 hub in between the device and my SurfaceBook’s port and everything seems happy. I haven’t yet made the board spin any motors — I think that’ll have to wait til tomorrow. But I’m happy as a clam that the thing shows up in the device manager and ChiliPeppr can see it.
I’m far from an expert, but it might be prudent to investigate the board’s ability to interact properly with USB 3.0 controllers and do a VCP chip update for v9.
I tried it on a win10 desktop and it appears to be connecting fine. Without installing any drivers, I simply powered up the TinyG, plugged in the usb connection, and everything simply worked. It appears to be using a generic driver that was already in place. So.. my laptop appears to be the problem.
This victory is bittersweet since I need to figure out why the laptop isn’t working the same way.
At any rate, I appreciate your help.
Edit: It didn’t use a generic driver — upon closer inspection, it loaded the 2.12.16.0 driver without my ever installing it myself.
