Live data from Hacker News

I stopped trusting USB-C cable labels and started testing them

makeuseof.com

151–160 of 266 posts

Re: I stopped trusting USB-C cable labels and started testing them

#151

> But I shouldn't have had to do any of this. It's time cables came with a label of their own, or some sort of color coding. There shouldn't even need to be a label. A USB-C cable should be a USB-C cable should be a USB-C cable. There should be a single connectivity/performance spec, and if the cable meets it, it can be called a USB-C cable, and if it doesn't, it should have to be marketed as USB-JUNK or something. T…

then how do you update capabilities/the spec? like 240w usb PD?

Re: I stopped trusting USB-C cable labels and started testing them

#152

> But I shouldn't have had to do any of this. It's time cables came with a label of their own, or some sort of color coding. There shouldn't even need to be a label. A USB-C cable should be a USB-C cable should be a USB-C cable. There should be a single connectivity/performance spec, and if the cable meets it, it can be called a USB-C cable, and if it doesn't, it should have to be marketed as USB-JUNK or something. T…

Because the spec is applied for either $1 Chinese toy or $10000 Apple Mac studio. Such dynamic range requires a lot of detail

Spec range is not the issue, its the inept thinking of designers that people should qll become little detectives and find out themselves what which cable does. Which is ridiculous assumption and judt doesnt work in real life.

Clear big labeling saying version, speed, watts or similar mix so everybody can quickly glance and know whats being sold. Whatever chinese crapware has mislabeled is another topic.

Re: I stopped trusting USB-C cable labels and started testing them

#153
post #72

> But I shouldn't have had to do any of this. It's time cables came with a label of their own, or some sort of color coding. There shouldn't even need to be a label. A USB-C cable should be a USB-C cable should be a USB-C cable. There should be a single connectivity/performance spec, and if the cable meets it, it can be called a USB-C cable, and if it doesn't, it should have to be marketed as USB-JUNK or something. T…

Unless you want all cables to be thick, $60, and cap out at 1 meter long, this is not a reasonable standard. 480mbps USB-C is perfectly adequate for many applications. Likewise for 60W cables.

And for the applications it not adequate for, a different cable should be used. But instead I have a drawer full of USB c cables and no idea which ones are which.

Re: I stopped trusting USB-C cable labels and started testing them

#154

I just pay a premium to a reliable source: Apple Regardless of tests they do charge my most energy hungry devices and everything else Many of us are privileged enough to make our lives easier in this way and haven't thought about it

I don't know how my wife and kids are treating charging cables, but the cables seem not to live that super long in their hands :) So paying premium constantly seemed like a money sink hole for me. Strangely enough once they start to buy their own damn cables instead of me paying, the lifespan of said cables seemed to quadruple. Strange strange universe we live in. :)

it's just psychology, there's not much thought when there just are cables around and new ones come when they break, but when you have to choose and buy ones yourself and look at the price tag and all that, you tend to place more value and significance to that thing and remember how much it costs etc...

I'd say most of us have experienced this ourselves in some form at some point in our lives

Re: I stopped trusting USB-C cable labels and started testing them

#155

> But I shouldn't have had to do any of this. It's time cables came with a label of their own, or some sort of color coding. There shouldn't even need to be a label. A USB-C cable should be a USB-C cable should be a USB-C cable. There should be a single connectivity/performance spec, and if the cable meets it, it can be called a USB-C cable, and if it doesn't, it should have to be marketed as USB-JUNK or something. T…

> A USB-C cable should be a USB-C cable should be a USB-C cable.

This would completely defeat the point.

There is a range of needs for cables. Some devices have simple needs for power/data transfer/extra functionality, and some devices have more. A $3 USB-powered lamp does not need a cable for gigabit data transfer and 100W charging - this cable would be more expensive than the product. Similarly, new features & performance levels will emerge and we want to be able to use these in new cables backward compatibly.

Given a range of needs, you have two options:

- A single cross-compatible connector, but with a range of capabilities

- Different types of connector for every capability

We used to be in the latter situation, USB-C is an attempt to do the former. Having different capabilities for same-shaped cables is the goal.

Labelling would be great, but standardizing one single spec for all cables would defeat the point.

Re: I stopped trusting USB-C cable labels and started testing them

#156

As always, these testers (the affordable ones) are capable of testing continuity, and, I guess, the cable chip report. If you want to test bandwidth, that's a five- or six-figure bit of gear.

This keeps needing to be pointed out every thread this appears on. Plenty of cables have eMarkers that claim "40Gbps" or whatever speeds, or support 240W PD...but absolutely cannot deliver either of those. And none of these consumer level testers can test either of those claims. Resistance measurements can cursorily test claims of 240W but resistance changes with temperature which changes with current...so unless you…

I had a cheap no-name cable which claims 3.1 speeds (and thus needs a marker), though it lacks all differential pairs and borks every usb connection (after I cut it, it was obvious). No clue why it contains a marker chip but doesn't have any conductors. Likely for usb-pd but you do not want to put any power though it anyway as the conductors were cheap copper clad aluminium.

Re: I stopped trusting USB-C cable labels and started testing them

#157

Earlier quoted context omitted.

Think about it. You need to generate a precise, calibrated, 40GHz signal, transmit it, then precisely measure the returned signal for phase, amplitude, and waveform integrity -at that speed. Oscilloscopes and logic analyzers that run at that speed, are damn expensive.

But for bandwidth can't you just have two simple computers at either end that can send a 100GB file and if it arrives in 20 seconds, you know you have 40gbps of bandwidth?

> But for bandwidth can't you just have two simple computers at either end that can send a 100GB file and if it arrives in 20 seconds, you know you have 40gbps of bandwidth?

Because that is not reproducible and introduces all sorts of other random variables to your test.

Expensive equipment is the only answer here.

Its a bit like when you ask an electrician to install network cable (yuk !).

They consider their job done after a continuity test (if they bother to do a continuity test at all).

Meanwhile, if you put a Fluke on it, you will pick up all sorts of subtle faults that the electrician's continuity tester will never pick up, but will cause subtle and hard-to-diagnose problems when you try to push data over the cable.

Its the same thing with all those cheap USB testers.

They might have all sorts of fancy displays, but in the end they are no substitute for the real thing and will end up lulling you into a false sense of security.

Re: I stopped trusting USB-C cable labels and started testing them

#158
post #82

Earlier quoted context omitted.

> There shouldn't even need to be a label. A USB-C cable should be a USB-C cable should be a USB-C cable. Then USB is forever frozen in time, unless we start using new connectors. This was the tradeoff we got when standardizing on one connector. The protocol versions change (USB, USB-PD, Thunderbolt), the cables that go between each connector change based on the needs of the spec they supports. But the connectors sta…

> now we’re living in the hell we asked for N=1, but my quality of life has greatly improved. Literally all devices I use daily (laptop, phone, mp3 player, Bluetooth speaker, headphones) I charge from a single cable. I'm still grateful for this unification every time I charge my phone via the laptop charger.

Exactly this. Or charge my laptop via the phone cable, sure, it's slower, but it still works.

Re: I stopped trusting USB-C cable labels and started testing them

#159
post #2

LTT has created true spec cables with the actual spec mentioned on the cables but they can not keep up with demand despite being expensive get sold out as soon as new stock comes in. https://www.youtube.com/watch?v=Hfovjw7Ts_U&t=974s

They are not TB5 compatible though, and if you are going to drive monitors through it, or connect external GPU, 120Gbit (TB5) is much better than 40Gbit TB4 gives you. If you are willing to pay a bit more, consider TB5 cables from CalDigit, StarTech, CableMatters, or Apple.

I can't find it anymore, but I'm pretty sure that the only reason they don't say it support TB5 is because they would need a license to say so.

Re: I stopped trusting USB-C cable labels and started testing them

#160

> But I shouldn't have had to do any of this. It's time cables came with a label of their own, or some sort of color coding. There shouldn't even need to be a label. A USB-C cable should be a USB-C cable should be a USB-C cable. There should be a single connectivity/performance spec, and if the cable meets it, it can be called a USB-C cable, and if it doesn't, it should have to be marketed as USB-JUNK or something. T…

There should be proper error correction. So you will have "this is a fast cable" versus "this is a slow cable", and NOT "this is a good cable" versus "this is a broken cable". Unfortunately, the second situation is the one we're in.
Post reply on HN