Eddie Control Board USB 3.0 Issues?
So I upgraded my laptop to an HP Pavilion I7 that has both USB 2.0 and 3.0 controllers. The 2.0 seems to work OK, but with RDS4 I pretty much need to devote that to the Kinect (because, as a data point it doesn't like my 3.0 ports. Possibly forensic evidence, the drivers load but the video and depth streams are corrupted). When I plug Eddie into the 3.0 port all sorts of BAD things happen.
1. A horrible 60 Hz square wave type of sound comes out of the speakers.
2. The laptop bluescreens.
3. On reboot I get one of two scenarios:
A. I get a Windows restore screen and things are pretty much OK
B. The machine won't even boot and I have to recover to a restore point.
I loaded the FTDI drivers.
I checked the drivers on the USB controller and they are (apparently) working and up to date.
Anyone seen issues with USB 3.0?
Todd C.
1. A horrible 60 Hz square wave type of sound comes out of the speakers.
2. The laptop bluescreens.
3. On reboot I get one of two scenarios:
A. I get a Windows restore screen and things are pretty much OK
B. The machine won't even boot and I have to recover to a restore point.
I loaded the FTDI drivers.
I checked the drivers on the USB controller and they are (apparently) working and up to date.
Anyone seen issues with USB 3.0?
Todd C.
Comments
I've been running Eddie on a USB 3.0 port without problems. I've also run the Kinect on USB 3, and haven't had issues (at least, not that I've noticed)....
Art
You can also use a powered HUB but most of those are meant to run from a 5V supply. Either get one meant for automotive use with a 12V adapter or get a DC/DC 12V to 5V converter with enough capacity to power the HUB and then power it from the batteries on the robot.
Robert
Thanks for confirming that 3.0 isn't the problem. The flaky way the Kinect was working was leading me to the problem being the laptop USB controller, although on the other hand it wasn't the answer I was looking for, if you know what I mean.
Robert,
I may try and isolate the problem with your hub idea. The one that I have is powered, but since Eddie has a 5 volt supply I can make a cable to power it. I will probably check current flows between the neg to make sure there aren't any problems with potential differences.
Todd
Probably the wrong way to start things out, but as I mentioned in the post above, I had a lot of problems with my HP and the drivers for the USB 3.0 port. I thought the update of the driver control software fixed it but it started blue-screening again. I finally took it back and purchased a Samsung Chronos 7, which I am very happy with and have had no problems.
That being said, the way I have my Eddie configured is the Kinect is connected to one of the two USB 3.0 ports. Since the Kinect doesn't like to share USB controllers I have everything else connected to the USB 2.0 controller. My laptop only has two USB 2.0 ports so I put a 12 volt powered hub on one of these. This worked out well since Eddie has 12 volts available, I simply made a cable to power the hub from the control board. I have the control board, powered USB speakers, webcam and wireless Xbox controller all connected to the hub with no issues. I even have the camera configured for HD and haven't seen a problem.
Microsoft RDS does look for the comm port associated with the control board, but not exactly sure what the protocol is. I would really like to get some USB sniffer software to watch the commands as they are exchanged, it would be valuable info. So, based on that, you could probably connect another Prop board from the USB but I'm not exactly sure how you would configure their USB/serial driver to use two comm ports. Probably a better solution would be to feed the second Prop board from the Eddie controller board using one of the high speed interfaces in the OBEX. I think Beau has one there. Do you need another Prop for the additional I/O pine?
Todd
Todd