Live data from Hacker News

Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

arstechnica.co.uk

11–20 of 93 posts

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#11

Does anyone else find it concerning that our new and best technology is so fragile that even the slightest fezz-up in what should be a passive signal-cable can cause our otherwise state of the art equipment to fry itself? Is reliability, durability and robustness nowhere to be found in any single spec for our new standards?

USB C is not a passive signal cable.

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#12
I wonder if he will be able to recover any of his losses from this company? I know he is reviewing these cables, so hes taking a certain amount of risk, but imagine if someone bought this cable for their new device. I would be pretty pissed if I bought a new device and a new USB cord to charge it and poof out goes the magical smoke and my USB didn't work anymore.

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#13

Does anyone else find it concerning that our new and best technology is so fragile that even the slightest fezz-up in what should be a passive signal-cable can cause our otherwise state of the art equipment to fry itself? Is reliability, durability and robustness nowhere to be found in any single spec for our new standards?

Its not a slight fezz-up really though. They reversed positive and negative on the power connections. That is a very basic mistake and one that often at least blows a fuse, if not worse.

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#14

Does anyone else find it concerning that our new and best technology is so fragile that even the slightest fezz-up in what should be a passive signal-cable can cause our otherwise state of the art equipment to fry itself? Is reliability, durability and robustness nowhere to be found in any single spec for our new standards?

It was not a slight fezz-up. It was miswiring in a power cable. It's like electrician wiring the live pin into ground pin and then wondering why one gets electrocuted by so many devices.

No specification can defend against a hostile, or sufficiently incompetent, implementer.

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#15

I wonder if he will be able to recover any of his losses from this company? I know he is reviewing these cables, so hes taking a certain amount of risk, but imagine if someone bought this cable for their new device. I would be pretty pissed if I bought a new device and a new USB cord to charge it and poof out goes the magical smoke and my USB didn't work anymore.

He might have a case. It was sold as an USB cable but clearly it is not actually an USB cable. False advertisement if not anything else.

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#16

Does anyone else find it concerning that our new and best technology is so fragile that even the slightest fezz-up in what should be a passive signal-cable can cause our otherwise state of the art equipment to fry itself? Is reliability, durability and robustness nowhere to be found in any single spec for our new standards?

From the review:

> I directly analyzed the Surjtech cable using a Type-C breakout board and a multimeter, and it appears that they completely miswired the cable. The GND pin on the Type-A plug is tied to the Vbus pins on the Type-C plug. The Vbus pin on the Type-A plug is tied to GND on the Type-C plug.

Although I haven't read the spec, following the spec is a key part making use of a standard.

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#17

Does anyone else find it concerning that our new and best technology is so fragile that even the slightest fezz-up in what should be a passive signal-cable can cause our otherwise state of the art equipment to fry itself? Is reliability, durability and robustness nowhere to be found in any single spec for our new standards?

USB C is not a passive signal cable.

Tomay-to/tomay-to.

Yes, USB C can also be used to provide power (which is also a form of signal), but again my point is that a cable like this is largely expected to be a passive component.

That a crap charger can do bad things would probably surprise no one, but hooking a good charger up to a good unit shouldn't be able to fry anything, ever.

Wasn't USB C supposed to make our lives easier? If we need to ensure all our USB C gadgets, cables and chargers are all not-exploding certified, in parts and in combination, I may just go back to plain old regular USB.

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#18
post #4

Sounds strange. AFAIK USB shouldn't get fried without external power source. So the Chromebook was bad, not the cable? Down votes? Did I misunderstand something? Just comment with reference that I'm wrong and I'm very happy. Why bother building 'USB Killer' if simple paper clip would fry the motherboard?

The external power source was presumably a wall outlet, since he was testing its ability to charge.

Well that is an entirely different story. I thought that the cable was plugged into a phone and his chromebook (Just like parent).

I was concerned that this might be a flaw in the chrome book, not the cable. The USB bus should be fine to use such a cable, charging is another thing.

When you add the external power source, that completely changes the game.

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#19

Earlier quoted context omitted.

USB C is not a passive signal cable.

Tomay-to/tomay-to. Yes, USB C can also be used to provide power (which is also a form of signal), but again my point is that a cable like this is largely expected to be a passive component. That a crap charger can do bad things would probably surprise no one, but hooking a good charger up to a good unit shouldn't be able to fry anything, ever. Wasn't USB C supposed to make our lives easier? If we need to ensure all o…

Pretty sure you could make a "plain old regular" usb cable that would do similar. Maybe you should go back to RS-232? You should also beware of just about any usb device you see, as it could be a http://kukuruku.co/hub/diy/usb-killer in disguise

Re: Google engineer finds USB Type-C cable that’s so bad it fried his Chromebook

#20

Earlier quoted context omitted.

USB C is not a passive signal cable.

Tomay-to/tomay-to. Yes, USB C can also be used to provide power (which is also a form of signal), but again my point is that a cable like this is largely expected to be a passive component. That a crap charger can do bad things would probably surprise no one, but hooking a good charger up to a good unit shouldn't be able to fry anything, ever. Wasn't USB C supposed to make our lives easier? If we need to ensure all o…

Hooking up a good charger up to a good unit with the ground and voltage wires reversed can fry things.

You can try it with your laptop. Cut the cable after the transformer, flip the ground and live wires and start it. It will get fried. Is this the fault of the specification or the person who intentionally flipped the wires?

The manufacturer was the person flipping the wires in this case.

Post reply on HN