> It would require only for cable to signal it's max current capacity.
As you say yourself a bit later, you'd need at least two "simple" resistors (one for the cable itself, one for the adapter) – otherwise it's only fixed-cable power supplies (and I really, really hate having to throw away an entire high-quality power supply just because the cable frayed at the laptop end).
> But USB-PD is generally horrifically complicated for what it does
Which parts would you suggest are safe to omit, in a world where you want to be able to charge both small accessories (Bluetooth headphones etc.), smartphones, and large laptops using a single connector?
> As you say yourself a bit later, you'd need at least two "simple" resistors (one for the cable itself, one for the adapter) – otherwise it's only fixed-cable power supplies (and I really, really hate having to throw away an entire high-quality power supply just because the cable frayed at the laptop end).
You could have end device regulate itself by looking at voltage drop, akin to MPPT. And note that simple (sub-10W) devices could opt to implement nothing whatsoever and just get the minimum 20V/0.5A, making small accessories need nothing whatsoever when it comes to extra chips to handle it.
You really need communication only when you start needing features like switchable sink/source function or voluntarily lowering power usage.
>>But USB-PD is generally horrifically complicated for what it does
> Which parts would you suggest are safe to omit, in a world where you want to be able to charge both small accessories (Bluetooth headphones etc.), smartphones, and large laptops using a single connector?
Not talking about featureset but how hideously complex the implementation is. I remember some early adopters tried to implement it using a microcontroller and it ate like 30+kB of code and it was more than half of total product's code
The spec (3.0, rev 1.1) is 574 pages. No fucking wonder we have so many devices implementing it subtly wrong. Hell, they even decided "no, none of the existing serial protocols fits our super special use case, need to invent that too. At least they didn't reinvent CRC32...
I don't understand the implementation, it's pretty nuts. And the multiple layers of optional features and fragmentation are pretty awful. I kinda wish they hadn't specified any power levels other than 5v and full programmable PPS....
I also wish they had implemented a dedicated solar profile to simplify solar generators, so a panel could say "I will act like a current source and do MPPT".
They probably could have done Dallas One Wire for the signalling and been just fine. It could also be how the cable chip communicates, and very small simple devices could use it without the full USB stack.
But, I can accept it just because of how well it works in practice as is.
As you say yourself a bit later, you'd need at least two "simple" resistors (one for the cable itself, one for the adapter) – otherwise it's only fixed-cable power supplies (and I really, really hate having to throw away an entire high-quality power supply just because the cable frayed at the laptop end).
> But USB-PD is generally horrifically complicated for what it does
Which parts would you suggest are safe to omit, in a world where you want to be able to charge both small accessories (Bluetooth headphones etc.), smartphones, and large laptops using a single connector?