# TC66 Resource Inventory

This note captures what was directly observed from the archived `TC66` resource bundle before any deeper reverse engineering.

## Imported Artifacts

- `TC66.pdf`
- `User Maual for Operation and PC software and APP of TC66(C) Type-c USB PD Trigger Meter 2019.6.5.pdf`
- `TC66C_V1.1.6.apk`
- `RuiDengUSBMeter_V1.0.0.6.rar` (reviewed locally, not retained in git)
- `PW0316_User_Manual_V2.9.pdf`

## Skipped Duplicate

- `Factory technical support and  conctact way .docx`
  Reason: byte-for-byte duplicate of the contact document already imported from the `UM24` archive

## Quick Findings

- `TC66.pdf` is a shorter 9-page document with title metadata `TC66/TC66C`
- the longer `User Maual ... TC66(C) ... 2019.6.5.pdf` appears intended to cover device operation plus PC and Android software usage
- string scan of `TC66C_V1.1.6.apk` surfaced repeated `TC66C` identifiers and RuiDeng branding, which makes this artifact more model-specific than the generic UM-family APKs
- quick archive listing of `RuiDengUSBMeter_V1.0.0.6.rar` shows a Windows desktop application, English and Chinese language files, x86/x64 drivers, and a bundled `.NET Framework 4.6` installer

## Review Status

- both imported TC66 manuals have now been text-reviewed
- the working synthesis is recorded in `TC66 Manuals Working Summary.md`

## Key Confirmations From Manual Review

- `TC66` is USB-only
- `TC66C` supports USB and Bluetooth
- Android app support is `TC66C`-only and explicitly BLE-based
- iPhone app support is `TC66C`-only
- desktop software communicates over `micro-USB`, not Bluetooth
- the manuals make `PD` / `CC pull-down` state an important part of correct measurement behavior
- the supplementary `PW0316` module manual explicitly validates the `FFE0/FFE4` notify path and `FFE5/FFE9` write path already assumed by the app

## Practical Use

- manuals may provide UI, feature, and workflow clues specific to `TC66(C)`
- the Android APK is a good candidate for later string extraction or decompilation when we need model-specific labels and behavior hints
- the PC software archive may still be useful for identifying USB/driver assumptions and desktop-side workflows, but it is intentionally left out of git for now
- the payload working note `TC66C Transport and Payload Working Note.md` now records how the current app models `TC66C` transport and decoded fields
- the `PW0316 BLE Module Working Summary.md` note now records what the radio module manual validates at the BLE transport layer
