Regarding CC Pull Down, there is a PD switch as well as a Settings Interface menu item that can both be used to activate the pull down. If one says to pull it down and the other is set to not pull it down, what happens?
Hi friend
in fact, one is software control CC pull down, one is firmware to switch PD , if you want to use PD trigger, you must switch them on … if one was closed, trigger can’t work
for PC software, we just finished yet, but we did not let our foreign friend to help me test first , we have tested, I would like let others test again
if you want to , you can help me test … this is file https://drive.google.com/open?id=1pX_YLL6HNbpq8rhjxmB_QnTtyyCZedur
for PC software, we just finished yet, but we did not let our foreign friend to help me test first , we have tested, I would like let others test again
if you want to , you can help me test … this is file https://drive.google.com/open?id=1pX_YLL6HNbpq8rhjxmB_QnTtyyCZedur
for PC software, we just finished yet, but we did not let our foreign friend to help me test first , we have tested, I would like let others test again
if you want to , you can help me test … this is file https://drive.google.com/open?id=1pX_YLL6HNbpq8rhjxmB_QnTtyyCZedur
Thanks for the software; I will provide feedback later after I have tried it out.
On my Lenovo laptop with a USB-C PD charger, the Quick Charge Detection screen shows the correct 20V and 2A operation but QC2.0 as the Quick Charge protocol instead of USB-C PD. Why?
In fact, running Protocol Detection against the charger correctly shows it is USB-C PD only.
for this problem, in our user manual, there is note: D+ and D- value are just reference, not very accuracy. The product will automatically identify a device with a supported fast charging mode. At this time the device supports the QC2.0、QC3.0、APPLE 2.4A/2.1A/ 1A/0.5A、Android DCP、SAMSUNG.(Note: This quick charge agreement recognition model is not complete and for reference only, we will add other protocol in the future)
Hi friend
don’t update it now, because we did not add the update things .
now please uninstall the software and install it again to check normal function and operation
our protocol is identified by D+ and D- data, This quick charge agreement recognition model is not complete and for reference only, we will add other protocol in the future)
detection is right , it is detection by CC wire, but fast charge identity is by D+and D- value.
D+ and D- value are just reference, not very accuracy. The product will automatically identify a device with a supported fast charging mode. At this time the device supports the QC2.0、QC3.0、APPLE 2.4A/2.1A/ 1A/0.5A、Android DCP、SAMSUNG.(Note: This quick charge agreement recognition model is not complete and for reference only, we will add other protocol in the future)
You have got me started on reading up on the use of D+ and D- values for various protocols, many of which are proprietary. One article with a very good explanation of QC 2.0 and QC 3.0 is Article
Do you expect to be able to implement detection of a protocol running on the CC wire in the future?
Today my TC66C arrived. Damn is it small if you see it side by side to a UM 25C. I like it!
But I hope they make a change in the Sotware. The UM 25C turns on the second you put in a device (so i can let it connected to the charger and see the current when i connect a device).
But not so the TC66. I have to manualy turn it on to see the values.