"This Device can run Faster..."

[Beverly Howard [Ms-MVP/MobileDev]]

Been watching posts concerning the usb connect message, "This device can
run faster... usb 2.0..." and have experienced it several times myself,
and, in the past, simply given up as I knew things were plugged into 2.0
ports and hubs.

Yesterday, rearranging my (physical) desktop, I got this message but
knew that I was connecting the same device to the same port, but... was
using a different cable.

I have seen "usb 2.0 certified" cables, but not though much about them
and it finally dawned that 2.0 might be toggling down due to cable
problems... for example, unequal conductor lengths and shielding.

Pulled out a cable I was pretty sure that came with a 2.0 device and
"problem solved"

Hope this helps,
Beverly Howard

 

[RJK]

I don't believe it, I supect you swapped out a faulty cable for a good one,
or a VERY badly made one for a normal one !

regards, Richard

 

[Beverly Howard [Ms-MVP/MobileDev]]

a faulty cable <<

the usb cable tolerance specifications changed for 2.0 due to the high
data speeds... the comparison being that ethernet twisted pair mistakes
will work fine with 10mbit connections, but will completely stop a
100mbit connection.

usb 1 cables will _normally_ work on usb 2 devices and the cable in
question works fine with usb 1 devices but not with usb 2 ones.

Not necessary that you do... all I was attempting was to offer a
troubleshooting option from a learning event which educated me on the
interface, and worked for me the first time I tried it as a solution.

Over the life of usb 2, I've had this problem come up with several
different cables connected to different 2.0 ports, so, my conclusion is
that the the cable specification issue has merit.

Beverly Howard [MS MVP-Mobile Devices]

 

[Frank\(FL\)]

Been watching posts concerning the usb connect message, "This device
can run faster... usb 2.0..." and have experienced it several times
myself, and, in the past, simply given up as I knew things were
plugged into 2.0 ports and hubs.

Yesterday, rearranging my (physical) desktop, I got this message but
knew that I was connecting the same device to the same port, but...
was using a different cable.

I have seen "usb 2.0 certified" cables, but not though much about them
and it finally dawned that 2.0 might be toggling down due to cable
problems... for example, unequal conductor lengths and shielding.

Pulled out a cable I was pretty sure that came with a 2.0 device and
"problem solved"

Hope this helps,
Beverly Howard

This happens to me every once in a while. I shut the computer down,
then using compressed air and alcohol I clean the cables and ports.

 

[Lady Dungeness]

Bev,

I'm really glad you posted that information. Tomorrow I'm going to do a
little computer housecleaning.

Lady D

"Beverly Howard [Ms-MVP/MobileDev]" <BevNoSpamBevHoward.com> wrote in
message | >> a faulty cable <<
|
| the usb cable tolerance specifications changed for 2.0 due to the high
| data speeds... the comparison being that ethernet twisted pair mistakes
| will work fine with 10mbit connections, but will completely stop a
| 100mbit connection.
|
| usb 1 cables will _normally_ work on usb 2 devices and the cable in
| question works fine with usb 1 devices but not with usb 2 ones.
|
| >> I don't believe it <<
|
| Not necessary that you do... all I was attempting was to offer a
| troubleshooting option from a learning event which educated me on the
| interface, and worked for me the first time I tried it as a solution.
|
| Over the life of usb 2, I've had this problem come up with several
| different cables connected to different 2.0 ports, so, my conclusion is
| that the the cable specification issue has merit.
|
| Beverly Howard [MS MVP-Mobile Devices]
|
|
|
|