FR version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
32% Positive
Analyzed from 1072 words in the discussion.
Trending Topics
#usb#cable#device#power#spec#problem#don#charger#side#devices

Discussion (40 Comments)Read Original on HackerNews
dmesg was absolutely silent about it when I plugged in or out my C-C USB cable although the device switched on when I was using a simple charger instead. I opened it up to see if there was a special switch or something to put it in firmware flashing mode, to no avail. The little documentation I had only mentioned using one of the USB port.
In the end, out of ideas, I switched cables (even though I knew my cable was perfectly fine). As soon as I plugged in a A-C USB cables, everything worked immediately...
It does not. The vast majority of sinks have absolutely no knowledge of the cable used.
This is literally device engineers not bothering to read any part of the USB-C spec, or intentionally leaving out a $0.0003 part. And no, that's not a typo - I really do mean "50k unit reel for $15".
Leaving off parts should result in behavior which is identical whether you connect an A-C cable or a C-C cable. Detecting the difference between them should require adding parts.
why tf does it matter what the other side of the cable is connected to?
How is the standard supposed to work with defective devices that don't implement the standard?
There's no such thing on the device. A power sink with a USB-C receptacle has two 5.1kΩ resistors, one on each CC line. A power sink with a USB-C plug has a single 5.1kΩ resistor. Always. That's it - anything else in on the power source (or cable) side.
You only need to bother with anything more on the sink side once you want to either sense what's the max current provided by the source (which you can do simply by measuring the voltage on CC pins), or implement PD.
I have a couple of devices that do not charge on a usb c source. I have to use a USB A - C cable on their shitty usb-c ports.
Now that I know the probable reason I’m more annoyed.
I don't think the right solution to problems coming from spec-violating garbage is producing differently spec-violating garbage.
No Type-C receptacle featuring device can assume there will be no Vbus voltage on attachment from the other side, regardless of CC signals.
For a simple reason that USB C-A cable assemblies exist and can be plugged to any old charger or port on the A side, which will not wait or negotiate anything. It will just source Vbus 5V right away.
Obvious counterpoint: what's going to happen when two noncompliant "always provide 5V" USB-C wall warts are connected together with a C-C cable? How well does a charger like power being fed into it?
If you need this fix, it will literally refuse to work with any spec-compliant USB-C device on the other side of a C-C cable. No way to miss it.
In practice, most if not all networking/hardware department carries a ethernet cable tester but somehow not true for USB cables.
You don't need a cable tester to detect this problem; just plug the device into a spec-compliant USB-C power brick with a USB-C cable and see if it fails to charge.
https://a.aliexpress.com/_mtW11kT