Re: Recognizing PD QC chargers

Arno Welzel, 2024-10-14 22:47:

Mickey D, 2024-10-14 16:58:
 

On 14 Oct 2024 11:34:09 +0100 (BST), Theo wrote:
>

There are testers you can buy which will talk to the PD or QC control
signals and tell you what it claims to do.  Look on Amazon, Aliexpress, etc.
>
Not a recommendation, just an example:
https://www.amazon.com/Voltage-Multimeter-Detection-Capacity-Measurement/dp/B0BS2ZS813/
>
If the microprint tells you the voltages (5/9/12/15/20/48V) you can infer
the PD capability from that, but to do that you'd need to read it.  Try
taking a photo when lit from an oblique angle, which should pick up the
embossing, then zoom into the photo.

>
Thanks for that information.
>
What happened to me is I have a desktop portable Jteman bluetooth mount
which is charged by USB-C but which won't charge out of my only USB-C
charger (which is an ONKO with 2 USB-C ports and one USB-A port).
>
 Charger: 67W Multiport GaN charger
 Model CH-GN67W2ClA
 The specs are super complicated (depending on how many ports are used).
 But I only used one port at a time.

 
What means "super complicated"? Can you provide a source for that? Maybe
a picture?
 

The cables are all known to be good because they charge my phone fine.
>
When I plug the Jteman to the USB-C ports of the charger, it won't charge.
 JTEMAN Phone Stand with Bluetoolh Speaker
 Product Model: L9
 Battery capacity: 1800mah
 Type-C  Input · DC  5V  1A
 Bluetooth Name: MH669
 Power of Speaker: 403W
 Product Size: 136x89x48mm        ~
>
But when I plug the Jteman to the USB-A port of the charger, it charges.
Does anyone have any idea why that happens?

 
Most likely the speaker does use USB-PD and the USB-C connection is just

... does NOT USE USB-PD of course ...

Because then it ALWAYS works with a USB-A connector, maybe just with the
minimum charge at 5V and 0.5A. But USB-C requires to negotiate the
charging protocol before you can draw power to charge.

there because many smartphones have USB-C cables even for QC using USB A
on the charger side.
 

I'm assuming it's a PD/QC thing - but I have no real idea why it happens.

 
Get a USB tester which displays the protocol as suggested - then you can
check it.

--
Arno Welzel
https://arnowelzel.de