RD TC66(C) USB Type-C Meter Tester UPM Review

The latest firmware is V1.14. 06/02/19

TL;DR:

  • Super accurate voltage
  • Android, iOS, and PC apps
  • PD, QC3.0/2.0, AFC, and FCP triggers
  • Firmware update
  • Offline data logging
  • Bugs

Update 05/03/19 – TC66C Final.

Update 04/06/19 – FW V1.13.

Update 01/18/19 – Added Type-C plug and receptacle pinouts.

Update 01/14/19 – With the upgrade of FW V1.11, it brings some advanced functions such as PD3.0+PPS trigger. Reported bugs.

Official specifications

  • Product model: TC66 / TC66C
  • Display screen: 0.96 Inch 160×80 color LCD display
  • Voltage measurement range: 0.005-30.0000V
  • Voltage measurement resolution: 0.0001V (0.1mV)
  • Voltage measurement accuracy: ±(0.5‰+10d)@23℃ (Beta)
  • Voltage measurement accuracy: ±(0.5‰+20d)@23℃
  • Current measurement range: 0-5.00000A
  • Current measurement resolution: 0.00001A (0.01mA)
  • Current measurement accuracy: ±(1‰+20d)@23℃ (Beta)
  • Current measurement accuracy: ±(1‰+30d)@23℃
  • External DC supply voltage: 3.5-24V
  • Capacity accumulation range: 0-99999mAh
  • Energy accumulation range: 0-99999mWh-999.99Wh
  • Power measurement range: 0-150W
  • Load impedance range: 1-9999.9Ω
  • Data refresh rate: high/medium/low (Beta)
  • Data refresh rate: 2Hz
  • Temperature range: 0℃~45℃/32℉~113℉ (Beta)
  • Temperature range: 0℃~80℃/32℉~176℉
  • Working temperature range: 0℃~45℃/32℉~113℉
  • Product size: 49mm × 22mm × 8mm
  • Product weight: 7.9g
Click image to enlarge.

The main difference is that the Final has two switches while the Beta has only one.

User Interfaces

RD_TC66C_Beta_VS_Final_FW
The Final comes with V1.12 FW which is for Finals only.
rd_tc66c_ui_01
UI #1: Main UI
rd_tc66c_ui_02
UI #2: Offline Data Logging
rd_tc66c_ui_03
UI #3: Fast charging protocols identification
rd_tc66c_ui_04_v1.11
UI #4: Fast charging protocols detection
rd_tc66c_ui_05_v1.11
UI #5: Fast charging trigger
rd_tc66c_ui_05_v1.11_01
UI #5.1: PD 2.0 trigger
rd_tc66c_ui_05_v1.11_02
UI #5.2: PD 3.0+PPS trigger
rd_tc66c_ui_06_01
UI #6.1: System settings 1
rd_tc66c_ui_06_02_v1.11
UI #6.2: System settings 2
rd_tc66c_ui_07_v1.11
UI #7: System info
rd_tc66c_ui_08
UI #8: Concise UI, only V, A, W and current direction.

Pinouts

Click image to enlarge.

Measurements

All tests were run with an ambient temperature of around 23℃.

Voltage Accuracy (Beta, Unloaded, w/ External Power, Switch Off, 23℃/73℉)
V Display V
0.09999751 00.1001
0.4999956 00.5001
0.9999947 01.0001
1.999989 02.0001
2.999973 03.0000
3.999961 03.9999
4.999957 04.9998
8.999928 08.9999
9.999924 09.9999
10.000425 10.0005
11.999948 11.9998
14.99994 14.9999
17.99984 17.9998
19.99981 19.9998
24.99971 24.9999
29.99963 29.9999

The following is a comparison of voltages between the Beta and the Final.
RD_TC66C_Beta_VS_Final_Voltage

Voltage Comparison (Unloaded, w/ External Power, Switch Off)
Beta V Final V
0.0500 0.0499
0.1000 0.1000
0.5000 0.5001
1.0000 1.0000
5.0000 5.0005
10.0000 10.0009
15.0000 15.0010
20.0000 20.0015
Own Current Consumption
Brightness Level 0, USB Connection Off, Bluetooth Off, CC Pulldown Off
mA, Display On mA, Display Off
21.00 20.01
Brightness Level 9, USB Connection On, Bluetooth On, CC Pulldown On
27.99 18.56
  • The voltage is super accurate when the ambient temperature is around 23℃/73℉.
  • Looks like the Final is not as accurate as the Beta, but close enough.
  • The usb-c connector is reversible; the arrow indicates the direction of the current.
  • The screen can be rotated 180 degrees.
  • Own current consumption is between 18.56mA and 27.99mA when bluetooth is not connected and no external power is connected.
  • The internal resistance is about 41mΩ (Includes both connectors).

Apps

RD_TC66C_iOS_App_01
iOS App
RD_TC66C_iOS_App_02
iOS App – Excel
RD_TC66C_XLSX
Don’t know why but the exported spreadsheet is titled “UM25C Excel”.
RD_TC66C_Android_App
Android App
RD_TC66C_PC_Program
PC Program

Temperature

RD_TC66C_Beta_VS_Final_Temp
The IR photos above were taken after 10 minutes with 16.5V 5A@20℃. The Beta displayed 64℃ and the Final displayed 48℃. The Beta was getting obviously hotter than the Final.

Bugs

FW V1.14 Bugs: B01 B02
FW V1.13 Bugs: B01 B02
FW V1.12 Bugs: B01 B02 B03
FW V1.11 Bugs: B01 B02 B03

Through some quick tests, some apparent PD bugs have been found.
rd_tc66c_v1.11_bugs

B01. The condition used to judge Power Delivery Specification Revision is incorrect. (ReportedConfirmedFixed)

It determines PD 3.0 by checking if the source has any APDO, but this is not the right way.

B02. A reserved value is filled in the Specification Revision field of a PD 3.0 Request Message. (ReportedConfirmedFixed)

This will confuse some PD 3.0 sources and make them behave strangely.

B03. An error occurs while interpreting the maximum PPS voltage above 12.7V. (ReportedConfirmedFixed (FW V1.13))

The Maximum Voltage field in an APDO is 8 bits. Suppose it is only calculated in the first 7 bits.
So 12.7V = 127 × 100mV, 127 = 1111111b (7 bits), no errors.
Then 16V = 160 × 100mV, 160 = 10100000b (8 bits), but takes only 7 bits, so 10100000b (8 bits) becomes 0100000b (7 bits) = 32, 32 × 100mV = 3.2V (error).
Therefore, 16V (15V Prog Maximum Voltage) will be considered as 3.2V (error), and 21V (20V Prog Maximum Voltage) will be considered as 8.2V (error).

This error probably happens in the Maximum Current field as well.

Conclusion

TC66(C) brings new features such as online firmware update and USB connectivity. It’s even more accurate than other RD USB meters. However, the apps are currently rudimentary. Still, some firmware glitches, such as Protocol Detection issues, PD Trigger issues, etc., are easy to find. Will everything be improved after a few updates? We can wait and see.

RD Offical Store
http://s.click.aliexpress.com/e/5v2YMNEY

Should I work with them to produce better PD functionality and add something like emarker info reader?

28 thoughts on “RD TC66(C) USB Type-C Meter Tester UPM Review

    • I don’t know if they fixed these specific bugs but I can say they fixed a few things about the USB PD. In previous firmwares (I think 1.15 that came pre-installed on mine), with a specific cheap charger when doing the PD trigger (detected as PD 3.0 PPS), when trying to lower the voltage to less than 4.8V the charger restarted by itself. In firmware 1.17 this charger still doesn’t go lower than 4.8V, but at least it doesn’t restart. They also fixed the issue of USB PD support being detected when connecting the TC66 to a charger with a USB A port using a USB A male to USB C female adapter between the two.

      Like

  1. Hello, how can i flash the firmware (TC66_V1.17.bin) i downloaded from “http://www.ruidengkeji.com/rdupdate/firmware/TC66/” ? The official RuiDengUSBMeter.exe is no more able to download a firmware.

    Like

  2. Hi, quick google search brought me to your site which is highly informative on the USB-PD testing. Can i use this device trigger function to force a specific voltage from a USBC charger (source) to a NB (sink)? eg. 65W charger > TC66(15v) > NB

    Like

    • Good question. It depends on whether your NB supports fast charging protocols. If your NB doesn’t support any fast charging protocol and needs regular DC input, it works. And you may want to check if the charger is capable to deliver enough power. Otherwise I don’t recommend to do so.

      Like

  3. Hi there, stumbled on your blog, and wanted to ask you a couple of questions.

    I am new to USB-C PD charging and have experienced some protocol incompatibility with cables, charger etc.

    This seems like it will help me, but, I dont quite understand the differences between all the units out there.

    I’d love to get a unit that could test Type-C and type A products, but can live without Type A if cost is prohibitive. I’d like to get one that can tell me which protocols are supported, PD, QC, etc.

    This unit seems like it has “trigger” function, does this mean it can send the signal to the client device even though the power source isn’t the right protocol? (assuming wattage can cover both protocols?) e.g. if a QC charger (@18W) using this trigger function can pose as PD 15W?

    Thanks for any info you can share!

    Like

    • Hey Joseph,

      I guess either ZY1280, U2, or KT001/CT-2 should be a good fit. However, they can only detect what protocols a power supply supports but not a device. Moreover, none of them can do the job perfectly.

      You can see the trigger function as a sink emulator which acts like a device. It cannot change the protocols the client device supports. It is often used to verify the results of Auto-Detection, or to trigger a specific voltage for a certain device. Usually that device does not require protocol negotiation.

      Like

      • Thanks for your reply. I went ahead and got a TC66 (nonC), as I dont really need to log anything. Mine is also on 1.12. I have downloaded the PC software, intending to update the FW to 1.14, however, I cant seem to get the driver to install. Any hints?
        Also, on 1.12, my trigger is showing PD2.0 but not 3.0 / PPS… is this normal?

        Like

      • First disconnect the TC66 from your computer. Next update the PC software to the latest version. And then try to install the driver from the PC software.

        Because of the B01 and B02 bugs, I cannot tell if it’s normal or not. I would say the source didn’t advertise any APDO at that moment.

        Like

  4. This looks really excellent. As for your question at the bottom of your post, absolutely work with them for improved PD support. That’s the main thing I am interested in with this model is the USB-C and PD support. I’d love to see what voltages and currents are getting used on a couple of power bricks and AC adapters I have for my phone and nintendo switch.

    Like

  5. when we visit the web page of this new product, the Quantity is 1 item. This action let the user to add this item at “add to cart” for buying.

    Of course this is a “bug” to the system. But it’s funny.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s