Multiple PPS profile charger bug

[CentyLab]

AP33772 driver is only design to read in 1 PPS profile. When there is more than one PPS profile in one charger, only the last profile is recognized correctly. Driver update is needed to read in more than one PPS profile.

If read correctly it should have 2 PPS profile. With the lower voltage range tent to provide higher current but still within the max charger rated power, for example:

• PDO .....
• PPS: 3.3V - 11V @ 4A
• PPS: 3.3V - 21V @ 3A

Bug image. There is no such thing as 39V profile in this charger.

[dreirund]

Bug image. There is no such thing as 39V profile in this charger.

I have this too. Firmware versions 0.9.7 and 1.0.0. Shows 39V@6A, while all other proviles are only @3a.

[CentyLab]

We were finally able to purchase a charger that has 2 PPS profiles. We were mostly going for the 100W to 140W during development which left out this edge case.
We will be developing a fix based on this charger behavior: https://www.costco.com/p/-/anker-70w30w-wall-charger-bundle/4000388367?langId=-1

[dreirund]

The power supply I have where I got the bogous 39V @ 3A can only deliver up to 20V@3.25A (PPS2: 21V @ 3A), has two PPS profiles (PPS1: 5.0V .. 11V, 3.0A, 33.0W max.; PPS2: 5.0V .. 21V, 3.0A, 63.0W max.), and has a total power rating of 65W. According to imprint.

It is this one:

Goobay 65370.

[washley]

I am getting the bogus 39V @ 6A PDO profile before a 5-21V @ 5A PPS profile on a LiteOn PA-1101-66. I don't know if it supports two PPS profiles (that datasheet is lacking PPS information), but given what I read above it sounds like this is the same issue.

Activating the bogus profile results in 5V, but the screen shows the selected output as 39000mV and 5720mA.

[CentyLab]

@dreirund @washley
Thank you for your input. Just want to let you know that we are actively working to resolve this bug. A big adjustment to the AP33772 library is needed.
In the mean time, we just created this template and Google Sheet to gather more charger profile info. Please help us build up the list with charger you own. It will help the community purchase the correct charger depend on application. Let's keep the charger with more than 1 PPS at a later time, since pocketPD cant read the range correctly just yet.
Tested Charger List - Submit Charger Profiles

[phaseOne]

Tested Charger List - Submit Charger Profiles

I see some folks have submitted chargers with more than one PPS profile. What device provided this information if the PocketPD FW doesn't currently support it?

[CentyLab]

@phaseOne ,

You can use Z-Power KM003C <- This is currently the golden tool for PD profile query.
Check out this YouTube video for demo output

[dreirund]

I see some folks have submitted chargers with more than one PPS profile. What device provided this information if the PocketPD FW doesn't currently support it?

I have not submitted yet, but I am about to just take it according to the device's documentation (manual, print on the device, …).

[washley]

Be careful about what's printed on the device. I have an Apple 96W charger that has 5.2V printed on the outside, and that is indeed what it outputs, but the profile (as reported on KM003C) is just 5V.

I also have Anker 20W chargers that according to the label are 5V and 9V only, but in reality they also offer a 12V profile.

[dreirund]

Be careful about what's printed on the device. I have an Apple 96W charger that has 5.2V printed on the outside, and that is indeed what it outputs, but the profile (as reported on KM003C) is just 5V.

So in that case the print is more correct than the electronically advertised profile specification,

I also have Anker 20W chargers that according to the label are 5V and 9V only, but in reality they also offer a 12V profile.

and here the electronically advertised profile specifications should be considered.

Not simple.

The table should accound for "profiles according to printout", "profiles according to electronic advertisement", "profiles according to external measurement" or so. (Or leave out the last one but add a column "measured values -- they might differ!)

Regards!