TC66 Manuals Working Summary
This note summarizes the two imported TC66 manuals as a working reference for the project.
Source Set
TC66.pdf
- imported file:
Documentation/Research Resources/Manuals/TC66.pdf
- apparent scope:
TC66 / TC66C
- language:
zh-CN
- pages:
9
- title metadata:
TC66/TC66C
- creator metadata:
Microsoft Word 2010
- revision date inside manual:
2022-01-07
- SHA-1:
c9272064731ab462b6c872d92536d7291b2bda1d
User Maual for Operation and PC software and APP of TC66(C) Type-c USB PD Trigger Meter 2019.6.5.pdf
- imported file:
Documentation/Research Resources/Manuals/User Maual for Operation and PC software and APP of TC66(C) Type-c USB PD Trigger Meter 2019.6.5.pdf
- apparent scope:
TC66(C) operation plus PC and mobile software
- language:
en
- pages:
12
- creator metadata:
WPS 文字
- version label inside manual:
TC66/TC66C(2020.6.5)
- SHA-1:
a497356baab166af7cf0806e3095a59ad18f0276
Reading Strategy
Working interpretation of the two documents:
- the English manual is the easier baseline for product behavior and software workflow
- the Chinese manual is newer and appears to supersede or extend some product details
- when the two overlap, treat the Chinese manual as the newer reference unless runtime evidence says otherwise
Confirmed Model Split
TC66 supports USB communication only
TC66C supports USB and Bluetooth communication
- Android and iPhone app support are described only for
TC66C
- PC software communicates with
TC66 and TC66C by micro-USB, not Bluetooth
This split is one of the most important conclusions from the manuals.
Confirmed Device Capabilities
- display:
0.96 inch color IPS
- screen resolution:
160 x 80
- voltage measurement range:
0.0050 V to 30.0000 V
- current measurement range:
0 to 5.00000 A
- supply voltage:
3.5 V to 24 V
- power range:
0 to 150 W
- voltage resolution:
0.0001 V
- current resolution:
0.00001 A
- capacity accumulation:
0-99999 mAh
- energy accumulation:
- older English manual:
0-99999 mWh and 999.99 Wh
- newer Chinese manual still speaks in
mWh/Wh terms but does not restate the full line in the same layout
- load impedance range:
- English manual:
1 Ω to 9999.9 Ω
- Chinese manual confirms load impedance display but not all values in the same line block
- temperature range:
- measurement / working range in manuals centers on
0 C to 45 C
- refresh rate:
2 Hz
Product-Specific Behavior
- this is a
Type-C tester rather than the older USB-A style family
- the product has hardware switches for:
- there is also a
micro-USB port for isolated power or PC connection
- the manuals stress an important operating rule:
- turn
PD or CC pull-down off during normal charging measurements
- turn it on for trigger and fast-charge protocol detection
UI and On-Device Pages
The manuals describe eight default device pages:
- main measurement
- offline recording
- quick-charge recognition
- quick-charge protocol detection
- trigger / decoy
- system settings
- system information
- simple measurement
Main measurement page
- shows voltage, current, capacity, energy, temperature, data-group number, load impedance, power, and current direction
- long press
K1 clears the active data group
- long press
K2 switches the data group
Data-group behavior
- the manuals describe multiple data groups with
0 as a temporary group
- group
0 restores and flashes the previous totals after reboot, then clears once accumulation exceeds 1 mAh
- at least group
1 persists totals across power cycles
- the wording in the English manual appears truncated around group numbering, so group semantics should be verified on-device before we hard-code exact persistence rules for every group
Offline recording page
- records measurements into onboard storage
- configurable recording interval:
1 to 60 seconds
- total recording duration ranges roughly from
24 minutes to 24 hours, depending on interval
- recording pauses automatically after power loss
- stored data can be cleared from the device menu
Quick-charge recognition
- reports
D+ and D- levels
- recognizes at least:
QC2.0
QC3.0
- Apple
2.4A / 2.1A / 1A / 0.5A
Android DCP
Samsung
- manuals say recognition is only a reference indication
Protocol detection
- dangerous operation that can make the USB-C side output high voltage
- manuals say to disconnect the load before running detection
- supported auto-detection includes:
QC2.0
QC3.0
- Huawei
FCP
- Huawei
SCP
- Samsung
AFC
PD
Trigger / decoy
- supported trigger families include:
QC2.0
QC3.0
- Huawei
FCP
- Huawei
SCP
- Samsung
AFC
PD2.0
PPS
PD mode allows switching supported voltages and adjusting step value for PPS
- after most trigger modes, unplugging and replugging is required to return to
5 V
Settings
- auto screen-off:
0-9 minutes
0 means always on
- brightness:
- Chinese manual says
10 levels
- temperature unit:
- PC communication switch
- Bluetooth switch
- screen rotation
PD software switch / CC line mode
- language choice
- restore factory settings
Important behavior from the newer Chinese manual:
- enabling
CC pull-down can auto-light the screen on PD chargers
CC pull-down may affect normal charging measurement
- if measuring PD charging behavior, turn
CC pull-down off
- if doing protocol detection or trigger,
CC pull-down must be on and no load should be connected
System and Recovery Notes
- system info page includes serial number, firmware version, boot count, and current runtime
- abnormal-state recovery:
- hold
K2 during power-on to restore factory settings
- hold
K1 during power-on to enter boot mode for firmware update
PC Software
- supported OS:
- Chinese manual:
Windows 7 to Windows 10
- English manual:
Windows 7 and above
- PC communication is via
micro-USB
- manuals mention
RuiDengUSBMeter desktop software
- first-time use requires driver installation
- firmware update is performed from PC software while booting the device into update mode
Important workflow details:
- avoid USB hubs with compatibility issues; prefer a native computer USB port
- offline data can be downloaded into the PC application
- viewing offline data pauses real-time curve recording
- the graph can export table and image data
- manual software version references:
- English manual:
V1.0.0.5
- newer Chinese manual:
V1.0.0.6
Android App
- Android support:
- English manual:
Android 5.0+
- newer Chinese manual narrows expectation to
Android 5.0-10.0
- Bluetooth requirement:
BLE 4.0+
- app support is only for
TC66C
- Android
6.0+ requires location permission for BLE scanning
- BLE devices must be discovered in the app, not through system Bluetooth settings
App and distribution notes:
- English manual points to Google Play search
TC66C
- newer Chinese manual points to Google Play search
RuiDeng
- manual also references direct download from RuiDeng download pages
- export of recorded data to spreadsheet form is supported
- version references:
- English manual: Android app
V1.1.1
- newer Chinese manual: Android app
V1.0.3
The version mismatch likely reflects different release snapshots rather than a contradiction in core behavior.
iPhone App
- iPhone app only supports
TC66C
- iOS support:
- English manual:
iOS 8.0+
- newer Chinese manual:
iOS 8.0 to iOS 14
- App Store search terms differ by manual:
- English manual:
TC66C
- Chinese manual:
TC66C
- version references:
- English manual:
1.2.0
- newer Chinese manual:
1.2.3
Important Scope Conclusions for This Project
TC66 and TC66C should not be treated as identical communication targets
- app support is explicitly
TC66C-only
- Bluetooth behavior for
TC66C is explicitly BLE, not classic serial Bluetooth
- desktop integration for the
TC66 family is explicitly USB-based
PD / CC pull-down state is likely relevant to what users see and may affect how measurements behave
Implementation-Relevant Concepts
Concepts likely worth reflecting in app state or decoding assumptions:
- active page
- active data group
- temporary vs persistent accumulation behavior
- offline recording state and interval
- quick-charge recognition result
- protocol-detection support matrix
- trigger protocol and selected voltage
PD or CC pull-down switch state
- Bluetooth enabled / disabled state on
TC66C
- firmware version and serial number
Open Questions
- exact data-group count and persistence behavior across all groups on current firmware
- whether Bluetooth payloads expose all device pages or only a subset
- whether the mobile apps expose offline-recording management or only live data and export
- whether English and Chinese manuals map to distinct firmware branches or only different documentation snapshots