Newer
■
■
■
■
■
■
■
■
■
■
Older
46 lines
|
2.518kb
| 1 |
# TC66 Resource Inventory |
|
| 2 | ||
| 3 |
This note captures what was directly observed from the archived `TC66` resource bundle before any deeper reverse engineering. |
|
| 4 | ||
| 5 |
## Imported Artifacts |
|
| 6 | ||
| 7 |
- `TC66.pdf` |
|
| 8 |
- `User Maual for Operation and PC software and APP of TC66(C) Type-c USB PD Trigger Meter 2019.6.5.pdf` |
|
| 9 |
- `TC66C_V1.1.6.apk` |
|
| 10 |
- `RuiDengUSBMeter_V1.0.0.6.rar` (reviewed locally, not retained in git) |
|
| 11 |
- `PW0316_User_Manual_V2.9.pdf` |
|
| 12 | ||
| 13 |
## Skipped Duplicate |
|
| 14 | ||
| 15 |
- `Factory technical support and conctact way .docx` |
|
| 16 |
Reason: byte-for-byte duplicate of the contact document already imported from the `UM24` archive |
|
| 17 | ||
| 18 |
## Quick Findings |
|
| 19 | ||
| 20 |
- `TC66.pdf` is a shorter 9-page document with title metadata `TC66/TC66C` |
|
| 21 |
- the longer `User Maual ... TC66(C) ... 2019.6.5.pdf` appears intended to cover device operation plus PC and Android software usage |
|
| 22 |
- 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 |
|
| 23 |
- 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 |
|
| 24 | ||
| 25 |
## Review Status |
|
| 26 | ||
| 27 |
- both imported TC66 manuals have now been text-reviewed |
|
| 28 |
- the working synthesis is recorded in `TC66 Manuals Working Summary.md` |
|
| 29 | ||
| 30 |
## Key Confirmations From Manual Review |
|
| 31 | ||
| 32 |
- `TC66` is USB-only |
|
| 33 |
- `TC66C` supports USB and Bluetooth |
|
| 34 |
- Android app support is `TC66C`-only and explicitly BLE-based |
|
| 35 |
- iPhone app support is `TC66C`-only |
|
| 36 |
- desktop software communicates over `micro-USB`, not Bluetooth |
|
| 37 |
- the manuals make `PD` / `CC pull-down` state an important part of correct measurement behavior |
|
| 38 |
- the supplementary `PW0316` module manual explicitly validates the `FFE0/FFE4` notify path and `FFE5/FFE9` write path already assumed by the app |
|
| 39 | ||
| 40 |
## Practical Use |
|
| 41 | ||
| 42 |
- manuals may provide UI, feature, and workflow clues specific to `TC66(C)` |
|
| 43 |
- the Android APK is a good candidate for later string extraction or decompilation when we need model-specific labels and behavior hints |
|
| 44 |
- 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 |
|
| 45 |
- the payload working note `TC66C Transport and Payload Working Note.md` now records how the current app models `TC66C` transport and decoded fields |
|
| 46 |
- the `PW0316 BLE Module Working Summary.md` note now records what the radio module manual validates at the BLE transport layer |