Comment

Comment on I bought a £16 smartwatch just because it used USB-C

tiramichu@sh.itjust.works ⁨2⁩ ⁨weeks⁩ ago

The person you replied to is referencing findings made by the author, in the article.

The author tried plugging a PD charger into the watch to charge it, and it wouldn’t work. It’s probably not PD as a specification couldn’t work, but that the watch failed to negotiate with the charger.

Whatever the reason, the findings were that trying to charge this cheap little watch with your PD laptop charger does not work.

source

Sort:hotnew top

ChaoticNeutralCzech@feddit.org ⁨2⁩ ⁨weeks⁩ ago
And the author wrongly said

PD will not negotiate down to 1W power levels

The correct way ro ask for 0.8 W (5 V, 0.16 A) is to request 5 volts. Doesn’t matter if the charger is capable of 500 mA, 1 A or 3.1 A. The PD standard can accomodate the watch, it’s just that the watch lacks active electronics that are required to talk to the charger (and even the supplied C-C cable is non-compliant by being power-only).

source
pupbiru@aussie.zone ⁨2⁩ ⁨weeks⁩ ago
right… i think that’s less of a problem with PD chargers and more of a problem with non-compliant A chargers (and the device itself being non-compliant): wattage/amperage at these has nothing to do with the protocol (other than auto shutoff under a given current draw, but that’s not instantaneous)

i believe that the USB spec says there needs to be a resistor bridging one of the pins to receive power? i can see USB-A chargers just dumping 5v through the cable no matter what and USB-PD more reliably implementing the spec because it’s more complex, so less reason to cut corners

source
- Aceticon@lemmy.dbzer0.com ⁨2⁩ ⁨weeks⁩ ago
  The device is probably just using a USB-C format connector to get power, without using the data connection at all, and a strict implementation of the USB protocol on the other side (the so called Host) would mean the device gets from the host only the minimal power levels (100mA @ 5V, if I remember it correctly) meant to merelly to power enough a connected device which has no batteries (say, a mouse) for it to actually do the initial USB connection negotiation, and that current will only get increased by the host it if during that negotiation the device tells the host it requires high-current (which in different USB versions has a different value - in USB 1.0 it was 500mA but latter versions increase it), a negotiation which that device can’t do because it doesn’t actually do USB data at all and just treats the whole thing as a dumb power cable.
  
  Dumb charger bricks don’t care at all because they themselves only do power and not the USB protocols, so really just treat the USB cable as a power cable into which they always make available whatever current the other side demands up to their max supply capacity (usually 1A or 2A) with no “USB negotiation”.
  
  This is why even in the times of USB-A some devices would charge fine from a dumb USB power brick but charge really slow if connected to a host which is a data device that can also do charging (like, for example, a notebook).
  
  This is even without getting USB PD into the mix.
  
  Because USB PD is a comms and power protocol, were the device tells the host the characteristics of the power it expects to get (not only current but even voltage) the USB PD brick has a proper USB implementation were it acts as a USB host.
  
  I expect the USB PD brick has a strict implementation of the USB protocol which, in the absence of USB negotiation, just provides that minimum current that per the protocol a USB host is expected to provide pre-negotiation.
  
  source