- May 11, 2008
- 22,502
- 1,467
- 126
I have to read it all to help co-develop a circuit for work.
The differences of how USB Power Delivery is communicated makes it not that easy. My head hurts from reading all day. And trying to find all the chips for the desired proto design.
A small summary :
The newest usb standard for power delivery is 2.0.
But it is interesting.
The old USB power requirements were 5V @ 500mA.
Now we can choose by use of negotiation :
5V @ 900mA.
5V @ 1.5A.
5V @ 3A.
12V @ 3A
12V @ 5A.
20V @ 3A
20V @ 5A.
And even have 12V at the usb power pins of the new type c connector with a maximum current of 5A equally divided over 4 pins.
With a maximum voltage of 20V @ 5A for 100W of power that can be provided when supported. 5V @ 500mA (or 900mA, not sure about that)is the default voltage. But the USB PD protocol allows to communicate for higher voltages and currents when more power needed.
Through the USB PD there is even more possible, the superspeed differential data line pairs (4 of them for a total of 10Gb/second) can also be used for other signals than USB , for example display port signals or even pci-e signals. This will be negotiated over the USB PD communication channel.
The new type c connector is a great design, just like the micro usb connector. The plug on the cable holds the spring contacts, the receptable on the device the sturdy contacts. Since the springs will wear out quicker, this means that the devices do not have to be replaced just because of a worn out connector. Just a new cable will do.
I am really happy to be honest. Another step up for me. The last designs i helped with turned out ok. I am getting a littler more confidence (That i do not have that nasty feeling that i have forgotten something )each iteration.
With software development, when you make an error, you reprogram the MCU, test the new code and it works. Software development allows for trial and error methods when needed. But an expensive hardware design with schematics and with printed circuit boards that have been drawn and made, every HW engineers wants to get it right the first time. Even in the prototype stage.
That means going through datasheets with a fine comb.
The differences of how USB Power Delivery is communicated makes it not that easy. My head hurts from reading all day. And trying to find all the chips for the desired proto design.
A small summary :
The newest usb standard for power delivery is 2.0.
But it is interesting.
The old USB power requirements were 5V @ 500mA.
Now we can choose by use of negotiation :
5V @ 900mA.
5V @ 1.5A.
5V @ 3A.
12V @ 3A
12V @ 5A.
20V @ 3A
20V @ 5A.
And even have 12V at the usb power pins of the new type c connector with a maximum current of 5A equally divided over 4 pins.
With a maximum voltage of 20V @ 5A for 100W of power that can be provided when supported. 5V @ 500mA (or 900mA, not sure about that)is the default voltage. But the USB PD protocol allows to communicate for higher voltages and currents when more power needed.
Through the USB PD there is even more possible, the superspeed differential data line pairs (4 of them for a total of 10Gb/second) can also be used for other signals than USB , for example display port signals or even pci-e signals. This will be negotiated over the USB PD communication channel.
The new type c connector is a great design, just like the micro usb connector. The plug on the cable holds the spring contacts, the receptable on the device the sturdy contacts. Since the springs will wear out quicker, this means that the devices do not have to be replaced just because of a worn out connector. Just a new cable will do.
I am really happy to be honest. Another step up for me. The last designs i helped with turned out ok. I am getting a littler more confidence (That i do not have that nasty feeling that i have forgotten something )each iteration.
With software development, when you make an error, you reprogram the MCU, test the new code and it works. Software development allows for trial and error methods when needed. But an expensive hardware design with schematics and with printed circuit boards that have been drawn and made, every HW engineers wants to get it right the first time. Even in the prototype stage.
That means going through datasheets with a fine comb.
Last edited: