+

+# Large local research archives kept out of regular git history

+Documentation/Research Resources/Software/PC Software/UM24C PC Software V1.3.rar

+

+## Working Layout

+

+- `Project History.md`

+  Narrative context and decisions that explain how the project got here.

+- `Platform Decision - iOS 15.md`

+  App-level platform choices that affect implementation.

+- `Research Resources/`

+  External source material plus the notes derived from it.

+

+## Documentation Layers

+

+We keep two distinct layers of documentation:

+

+- project documentation

+  Notes that describe our app, decisions, assumptions, and roadmap

+- research documentation

+  Vendor manuals, software archives, contact sheets, protocol notes, and model-specific findings

+

+## Retention Rule

+

+Prefer keeping:

+

+- small curated Markdown notes

+- raw manuals and reference PDFs

+- small software artifacts that are directly useful for reverse engineering

+- one canonical copy of each vendor artifact line

+

+Avoid committing by default:

+

+- very large archives with low immediate value

+- duplicate files already represented elsewhere

+- generated exports that can be reproduced from a kept source

+

+## Collected Manuals

+

+### `USB tester UM24C - User Manual.pdf`

+

+- status: added to repository

+- apparent scope: `UM24C`

+- pages: `19`

+- document language hint: `zh-CN`

+- creator metadata: `Microsoft Word 2010`

+- extraction status: text extraction not yet cleaned; review will likely require manual reading or OCR-aware extraction

+- compatibility note: keep as `UM24C`-specific until we find stronger evidence that the same manual applies unchanged to `UM25C` or `UM34C`

+

+### `UM24(C) USB tester meter  Instruction   PC software intruction  Android APP instruction- 3 in 1 -  2018.6.30(3).pdf`

+

+- status: not imported separately

+- reason: duplicate of `USB tester UM24C - User Manual.pdf`

+- SHA-1: `b85dde3d36ee017a7a7f643690283d64aa29d516`

+

+### `TC66.pdf`

+

+- status: added to repository

+- apparent scope: `TC66` / `TC66C`

+- pages: `9`

+- title metadata: `TC66/TC66C`

+- creator metadata: `Microsoft Word 2010`

+- SHA-1: `c9272064731ab462b6c872d92536d7291b2bda1d`

+- extraction status: reviewed; summarized in `../Specifications/TC66 Manuals Working Summary.md`

+

+### `User Maual for Operation and PC software and APP of TC66(C) Type-c USB PD Trigger Meter 2019.6.5.pdf`

+

+- status: added to repository

+- apparent scope: `TC66(C)` including device operation, PC software, and Android app workflow

+- pages: `12`

+- creator metadata: `WPS 文字`

+- SHA-1: `a497356baab166af7cf0806e3095a59ad18f0276`

+- extraction status: reviewed; summarized in `../Specifications/TC66 Manuals Working Summary.md`

+

+### `User_Manual_UM34C.pdf`

+

+- status: added to repository

+- apparent scope: shared `UM25C` / `UM34C` family operation manual, but model labeling is inconsistent inside the document

+- pages: `12`

+- creator metadata: `Microsoft Word 2016`

+- SHA-1: `71f6ccae85ba6930e626208e24f66dead07d3e52`

+- extraction status: text extracted and summarized in `../Specifications/UM34C Manual Working Summary.md`

+

+### `UM25 User Manual.pdf`

+

+- status: added to repository

+- apparent scope: `UM25` family manual as provided from local source

+- pages: `27`

+- creator metadata: `WPS 文字`

+- source filename: `98c297e2b477494d7de0babe2b77877749c3.pdf`

+- SHA-1: `518898c297e2b477494d7de0babe2b77877749c3`

+- extraction status: imported as raw manual; content review not yet performed

+

+## Collected Notes

+

+### `UM24C-UM25C-UM34C from floriandotorg-um24c.md`

+

+- external protocol notes for the UM family

+

+### `TC66C Transport and Payload Working Note.md`

+

+- implementation-oriented note derived from the TC66 manuals and the current app code

+- captures current transport assumptions, command surface, encrypted snapshot framing, and decoded field map

+# TC66C Transport and Payload Working Note

+

+This note translates the reviewed `TC66` manuals and the current app code into an implementation-oriented working reference.

+

+## Scope

+

+This note is about `TC66C`, not `TC66`.

+

+Reason:

+

+- the manuals say `TC66` is USB-only

+- the iOS and Android apps are `TC66C`-only

+- the current app code has a separate `TC66C` BLE path

+

+## Evidence Sources

+

+Primary sources used for this note:

+

+- `Documentation/Research Resources/Specifications/TC66 Manuals Working Summary.md`

+- `USB Meter/Model/Meter.swift`

+- `USB Meter/Model/BluetoothRadio.swift`

+- `USB Meter/Model/BluetoothSerial.swift`

+

+## Current App Assumptions

+

+The current app already treats `TC66C` as a different protocol family than `UM25C` / `UM34C`.

+

+Confirmed from code:

+

+- model enum contains a dedicated `TC66C` case

+- `TC66C` is mapped to radio type `PW0316`

+- peripheral names `TC66C` and `PW0316` are both recognized as `TC66C`

+- the scan path includes services `FFE0` and `FFE5` for this radio family

+

+## BLE Transport Assumptions In Code

+

+The current code assumes the following BLE transport for `TC66C`:

+

+- notify characteristic: service `FFE0`, characteristic `FFE4`

+- write characteristic: service `FFE5`, characteristic `FFE9`

+

+This differs from the `UM` family path already documented elsewhere:

+

+- `UM25C` / `UM34C` use `FFE0` / `FFE1`

+- `TC66C` uses a separate `PW0316`-style path in the current app

+

+## Request / Response Shape

+

+The current app polls `TC66C` using ASCII commands.

+

+Confirmed command surface already used by the app:

+

+- measurement snapshot request: `bgetva\r\n`

+- next page: `bnextp\r\n`

+- previous page: `blastp\r\n`

+- rotate screen: `brotat\r\n`

+

+Expected snapshot response size in current code:

+

+- `192` bytes

+

+Important implication:

+

+- the app assumes fixed-length snapshot framing for `TC66C`

+- this is not derived from the manuals directly; it comes from the existing reverse-engineered implementation

+

+## Encrypted Snapshot Structure

+

+The current parser decrypts the `192`-byte response with `AES ECB`.

+

+Observed implementation details:

+

+- the app uses a hard-coded `32`-byte AES key

+- the decrypted payload is treated as three `64`-byte packets

+- those packets are referred to as `pac1`, `pac2`, and `pac3`

+

+Each packet is validated as:

+

+- first four bytes are ASCII header `pac1`, `pac2`, or `pac3`

+- bytes `0...59` are CRC-covered

+- CRC seed is `0xFFFF`

+- stored CRC is little-endian at offset `60`

+

+If any of the three packets fail validation, the app rejects the snapshot as invalid.

+

+## Field Map Currently Parsed By The App

+

+The offsets below are offsets inside the decrypted packet blocks, not offsets into the encrypted `192`-byte BLE frame.

+

+### `pac1`

+

+- offset `4`, size `4`: candidate model name as ASCII

+- offset `8`, size `4`: candidate firmware version as ASCII

+- offset `12`, size `4`: candidate serial number, little-endian `UInt32`

+- offset `44`, size `4`: candidate boot count, little-endian `UInt32`

+- offset `48`, size `4`: voltage, raw / `10000`

+- offset `52`, size `4`: current, raw / `100000`

+- offset `56`, size `4`: power, raw / `10000`

+

+Confidence:

+

+- voltage / current / power are high-confidence because the app actively uses them

+- model / firmware / serial / boot count are medium-confidence because they exist as commented decoding hints in code, not active UI fields

+

+### `pac2`

+

+- offset `4`, size `4`: load resistance, raw / `10`

+- offset `8`, size `4`: data group `0` accumulated charge, raw / `1000`

+- offset `16`, size `4`: data group `1` accumulated charge, raw / `1000`

+- offset `48`, size `4`: data group `0` accumulated energy, raw / `1000`

+- offset `56`, size `4`: data group `1` accumulated energy, raw / `1000`

+- offset `24`, size `4`: temperature sign flag, `1` means negative in current parser

+- offset `28`, size `4`: temperature magnitude

+- offset `32`, size `4`: `D+` voltage, raw / `100`

+- offset `36`, size `4`: `D-` voltage, raw / `100`

+

+Confidence:

+

+- load resistance, temperature, `D+`, and `D-` are high-confidence in the sense that the app displays them

+- exact data-group interpretation is medium-confidence because the parser only fills groups `0` and `1`

+

+### `pac3`

+

+- no fields are currently decoded from `pac3`

+

+This is a major open area for further reverse engineering.

+

+## Mismatch Between Manuals And Current App

+

+### 1. Device pages vs exposed controls

+

+The manuals describe many on-device capabilities:

+

+- offline recording

+- protocol detection

+- trigger / decoy

+- system settings

+- information page

+- simple mode

+

+The current app only implements these direct `TC66C` controls:

+

+- request live snapshot

+- previous page

+- next page

+- rotate screen

+

+Not implemented in the current app for `TC66C`:

+

+- clear data group

+- select data group

+- brightness change

+- screen timeout change

+- recording-threshold change

+

+The code explicitly guards these setters off for `TC66C`.

+

+### 2. Data-group coverage

+

+The manuals discuss data groups, but the current parser only populates two groups for `TC66C`.

+

+Working interpretation:

+

+- either `TC66C` exposes only two remotely readable groups in the current snapshot layout

+- or the current parser only decodes the first two groups and leaves the rest unknown

+

+This needs verification from captures or app analysis.

+

+### 3. Bluetooth scope

+

+The manuals are clear that:

+

+- `TC66` is not a Bluetooth target

+- `TC66C` uses BLE for mobile apps

+

+This matches the current app architecture and strengthens confidence that `TC66C` should remain a separate transport family in the codebase.

+

+## Working State Model For `TC66C`

+

+The current implementation implicitly models at least these state domains:

+

+- connection state

+- active device page

+- instantaneous electrical measurements:

+  - voltage

+  - current

+  - power

+  - current direction is documented in manuals but not currently decoded into a separate published field

+- accumulated data:

+  - charge

+  - energy

+  - at least two data groups

+- cable and charger context:

+  - load resistance

+  - `D+`

+  - `D-`

+  - quick-charge related behavior

+- environment:

+  - temperature

+- device metadata:

+  - firmware version candidate

+  - serial number candidate

+  - boot count candidate

+

+## Practical Implications For Implementation

+

+### Keep `TC66C` separate from UM-family decoding

+

+- transport is different

+- request commands are different

+- payload framing is different

+- encryption is different

+

+The code already reflects this split and the manuals support it.

+

+### Treat `pac3` as the highest-value unknown

+

+We already have enough for a basic live meter UI from `pac1` and `pac2`.

+

+What is still likely hidden:

+

+- additional device settings

+- active page information

+- recording configuration

+- protocol-detection or trigger state

+- more complete data-group information

+

+### Do not over-trust current group mapping

+

+The app's `TC66C` parser only maps two groups, while the manuals talk more generally about groups and offline storage.

+

+Until verified, avoid hard-coding a stronger assumption than:

+

+- `TC66C` snapshots currently expose at least two group-like accumulators in our parser

+

+### Separate manual truth from protocol truth

+

+The manuals are strong for:

+

+- feature list

+- UX flow

+- transport family split

+- required `PD / CC pull-down` behavior

+

+The manuals are not enough for:

+

+- exact BLE field map

+- command framing completeness

+- full payload offsets

+

+## Suggested Verification Priorities

+

+1. confirm `FFE0/FFE4` notify and `FFE5/FFE9` write behavior against real `TC66C` hardware

+2. capture and archive one or more raw `192`-byte encrypted snapshots

+3. decrypt and annotate unknown bytes in `pac3`

+4. verify whether more than two data groups exist in BLE snapshots

+5. determine whether current device page is present in payload

+6. verify whether recording state and interval are exposed remotely

+7. promote candidate metadata fields in `pac1` from code comments to confirmed fields

+

+## Recommended Next Notes

+

+The next helpful artifacts for the repository would be:

+

+- a raw `TC66C` sample-capture note in `Payload Notes`

+- a byte-offset map for `pac1`, `pac2`, and `pac3`

+- an implementation checklist for exposing currently undocumented `TC66C` features in the UI

+- archived software packages

+- vendor contact information

+

+Imported sources can include:

+

+- raw PDFs, DOCX, APK, RAR, and similar archival files

+- companion README notes describing provenance, duplicates, hashes, and extraction status

+

+## Folder Roles

+

+- `Manuals/`

+  Raw manuals and manual inventory notes.

+- `Software/`

+  Raw APKs, desktop packages, and notes about retained or intentionally skipped software artifacts.

+- `Vendor Contacts/`

+  Vendor contact documents and extracted contact details.

+- `Specifications/`

+  Curated product and family-level summaries derived from manuals and software.

+- `Payload Notes/`

+  Protocol-facing notes, field maps, framing assumptions, and verification targets.

+- `Related Projects/`

+  External reverse-engineering references that help us compare assumptions.

+

+## Retention Policy

+

+Keep in git:

+

+- source manuals that are directly cited by our notes

+- compact software artifacts that are useful for quick inspection

+- extracted Markdown notes that save future reverse-engineering time

+- one canonical copy of a duplicated vendor artifact

+

+Do not keep in regular git history by default:

+

+- very large archives that are expensive to clone and not yet central to active work

+- duplicate bundles that do not add new information

+- generated intermediate files created only during extraction

+# Android Apps

+

+This folder contains Android application packages collected as raw reference material.

+

+## Imported Files

+

+### `UM Meter_V3.0.5.apk`

+

+- status: added to repository

+- source: `UM24` archive

+- SHA-1: `b1427fba05c5fbcb64d9bab1f174a8eab63cc996`

+- extraction status: APK preserved as raw artifact; contents not yet analyzed

+- working applicability: likely broader than `UM24C` only; quick string scan shows RuiDeng branding but no immediate model lock

+

+### `RuiDeng_V1.0.2.apk`

+

+- status: added to repository

+- source: `UM24` archive

+- SHA-1: `25154f7ab5da6c727eab17ed903c1a8e06d82c71`

+- extraction status: APK preserved as raw artifact; contents not yet analyzed

+- working applicability: likely broader than `UM24C` only; quick string scan shows RuiDeng branding but no immediate model lock

+

+### `TC66C_V1.1.6.apk`

+

+- status: added to repository

+- source: `TC66` archive

+- SHA-1: `1054cc6122a3ac0668d1c6908b273bf24012ff39`

+- extraction status: APK preserved as raw artifact; quick inspection only

+- quick findings: string scan surfaced repeated `TC66C` markers, RuiDeng branding, and text indicating applicability to `TC66C` data acquisition display

+# PC Software

+

+This folder contains archived desktop software packages related to RuiDeng USB meters.

+

+## Imported Files

+

+### `UM24C PC Software V1.3.rar`

+

+- status: reviewed locally but intentionally not committed to regular git history

+- source: `UM24` archive

+- SHA-1: `b2e16ca006c185571bc0f7e3a1a79c4c13dbe9f1`

+- apparent scope: `UM24C`

+- archive status: preserved as raw artifact; detailed extraction not yet documented

+- initial observation: archive appears to contain a Windows installer tree with National Instruments / LabVIEW-related runtime components

+- compatibility note: quick archive scan did not surface direct `UM25` or `UM34` strings, so any broader applicability remains an inference only

+- retention note: excluded from this repository's normal history because the archive is very large relative to its current investigation value

+

+### `RuiDengUSBMeter_V1.0.0.6.rar`

+

+- status: added to repository

+- source: `TC66` archive

+- SHA-1: `10280f20f6979b4b2ee9468d89d0f9b2dd79d552`

+- apparent scope: likely `TC66` family desktop software

+- archive status: preserved as raw artifact; quick archive listing only

+- quick findings: archive contains `RuiDengUSBMeter.exe`, x86/x64 drivers, `CH.xaml`, `EN.xaml`, and bundled `.NET Framework 4.6`

+# Software

+

+Archive vendor or third-party software related to supported USB meter models here.

+

+Recommended contents:

+

+- Android applications

+- PC software packages

+- extracted binaries or installers when legally safe to preserve

+- companion notes about supported models, versions, and observed protocol hints

+

+Current status:

+

+- Android applications imported from the `UM24` archive

+- Android application imported from the `TC66` archive

+- compact `TC66` PC software archive retained in repository

+- large `UM24C` PC software archive inspected locally but intentionally not committed to regular git history because of size

+- font file from the archive intentionally not imported for now because it does not appear device-specific

+

+Working note:

+

+- some imported software artifacts appear branded at the RuiDeng family level rather than clearly tied to a single model

+- until deeper reverse engineering confirms scope, treat them as potentially relevant to `UM24C`, `UM25C`, and `UM34C`

+- the `TC66` archive also contains TC66-specific software artifacts that should be treated as a separate line unless overlap is later confirmed

+

+Retention note:

+

+- prefer keeping software artifacts that are small enough to clone comfortably and directly useful for protocol or workflow analysis

+- keep metadata notes for larger archives even when the archive itself stays out of git

+

+## Collected Notes

+

+### `UM24-UM25-UM34 Family Compatibility Note.md`

+

+- family-level compatibility and inference note across related USB testers

+

+### `UM34C Manual Working Summary.md`

+

+- working summary extracted from the imported `User_Manual_UM34C.pdf`

+- focuses on confirmed UI behavior, measurement features, storage semantics, app workflow, and caveats

+

+### `UM25 Manual Working Summary.md`

+

+- working summary extracted from the imported `UM25 User Manual.pdf`

+- focuses on confirmed `UM25/UM25C` capabilities, Android/iOS/Windows workflow, and transport caveats

+

+### `TC66 Manuals Working Summary.md`

+

+- combined working summary for the imported `TC66` Chinese and English manuals

+- focuses on model split, USB vs BLE communication, trigger and PD behavior, and PC/mobile workflow

+# 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:

+  - system power

+  - `PD`

+- 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:

+  - `C` / `F`

+- 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

+# 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`

+

+## 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

+

+## 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 be useful for identifying USB/driver assumptions and desktop-side workflows even before full extraction

+- the payload working note `TC66C Transport and Payload Working Note.md` now records how the current app models `TC66C` transport and decoded fields

+# UM24 / UM25 / UM34 Family Compatibility Note

+

+This note records what can currently be inferred from the archived `UM24` resource bundle about the `UM24C`, `UM25C`, and `UM34C` family.

+

+## Confirmed Facts

+

+- the archived manual is explicitly labeled `UM24C`

+- the archived PC software package is explicitly labeled `UM24C`

+- the `UM24` line is known to use classic Bluetooth serial-port style communication and is not intended to be supported by this application

+- the newly imported `User_Manual_UM34C.pdf` uses mixed model labels internally: `UM25/UM25C` in one heading and `UM34/UM34C` in the technical parameter section

+- the same newly imported PDF titles its app section `UM34C Android APP Instruction`

+- a separate `UM25` manual has now been imported as `Documentation/Research Resources/Manuals/UM25 User Manual.pdf`

+- the `UM25` manual explicitly includes Android app, iOS app, and Windows PC software sections for `UM25C`

+- the two Android APKs are branded more generically around RuiDeng / `UM Meter`

+- the duplicate "3 in 1" PDF is byte-for-byte identical to the already imported `UM24C` manual

+

+## Quick Inspection Results

+

+- quick string scans of the Android APKs surfaced RuiDeng branding but did not immediately expose model-specific names such as `UM25` or `UM34`

+- quick string scan of the PC software archive surfaced `UM24C` labeling and installer/runtime filenames, but no direct `UM25` or `UM34` hits

+- the imported `UM34C` PDF reads like an operational manual for the same product family and strengthens the case that RuiDeng reused documentation structure across closely related models

+- the newly added `UM25` PDF likely gives us a cleaner model-specific source for separating `UM25` behavior from `UM24C` and `UM34C`, but it still needs review

+- the reviewed `UM25` PDF confirms that `UM25C` had official Android, iOS, and Windows software support, which makes it a better primary product reference than the older `UM24C` manual

+- the existing external project note for `floriandotorg/um24c` remains the stronger indication that `UM24C`, `UM25C`, and `UM34C` are closely related at the protocol level

+

+## Working Assumption

+

+- use the imported Android applications and vendor contact document as family-level reference material that may still help with `UM25C` and `UM34C`

+- exclude classic-Bluetooth `UM24` support from current application scope

+- use the imported `User_Manual_UM34C.pdf` as a family-level UI and feature reference, while keeping its model-specific claims tentative

+- use the reviewed `UM25` manual as the current best product-level reference for `UM25C`

+- use the imported manual and PC software primarily as `UM24C` references until stronger cross-model evidence is found

+

+## Practical Implication

+

+- focus implementation effort on the app-supported `UM25C` / `UM34C` direction rather than classic-Bluetooth `UM24`

+- treat the `UM25` manual as the best current guide for user-visible features and supported control surfaces

+- for payload decoding and Bluetooth behavior, keep comparing `UM25C` and `UM34C` observations against `UM24C` notes

+- for UI, wording, and software workflow clues, the imported APKs may be useful even if the desktop package stays `UM24C`-centric

+# UM25 Manual Working Summary

+

+This note summarizes the imported manual [`UM25 User Manual.pdf`](../Manuals/UM25%20User%20Manual.pdf) as a working reference for the project.

+

+## Source Snapshot

+

+- imported file: `Documentation/Research Resources/Manuals/UM25 User Manual.pdf`

+- source filename: `98c297e2b477494d7de0babe2b77877749c3.pdf`

+- model label in manual: `UM25/UM25C`

+- manual date: `2019.9.24`

+- pages: `27`

+- creator metadata: `WPS 文字`

+- SHA-1: `518898c297e2b477494d7de0babe2b77877749c3`

+

+## Why This Source Matters

+

+Compared with the previously imported `UM34C` PDF, this manual is a cleaner product reference for `UM25/UM25C`.

+

+Confirmed scope improvements:

+

+- the title page explicitly says `UM25/UM25C`

+- the table of contents includes Android app, iOS app, and PC control software sections

+- the technical parameter block is internally consistent with `UM25/UM25C`

+

+## Confirmed Device Capabilities

+

+- color LCD display: `1.44 inch`

+- measurement ranges:

+  - voltage: `4-24.000 V`

+  - current: `0-5.0000 A`

+  - capacity: `0-99999 mAh`

+  - energy: `0-99999 mWh`

+  - temperature: `-10 C to 100 C`

+- measurement resolutions:

+  - voltage: `0.001 V`

+  - current: `0.0001 A`

+- accuracy claims:

+  - voltage: `±(0.5‰ + 2 digits)`

+  - current: `±(1‰ + 4 digits)`

+- refresh rate: `2 Hz`

+- quick-charge recognition claims support for:

+  - `QC2.0`

+  - `QC3.0`

+  - Apple `2.4A / 2.1A / 1A / 0.5A`

+  - `Android DCP`

+  - `SAMSUNG`

+

+## Hardware and UI Notes

+

+- hardware layout includes:

+  - `Micro USB` port

+  - `USB-A female` port

+  - `USB-A male` port

+  - `Type-C input` port

+  - `Type-C output` port

+  - Bluetooth switch

+  - Bluetooth indicator

+- the manual says both Type-C ports expose only `VBUS`, `GND`, `CC1`, and `CC2`

+- the interface model is the same six-page pattern seen in related manuals:

+  - main measurement

+  - quick-charge recognition

+  - charging record

+  - cable impedance measurement

+  - graphing

+  - system settings

+

+## Measurement and Storage Behavior

+

+- the main screen shows voltage, current, power, temperature, accumulated `mAh`, accumulated `mWh`, load impedance, and active data-group index

+- the device provides `10` data groups: `0-9`

+- groups `1-9` persist accumulated `mAh` and `mWh` across power cycles

+- group `0` is temporary and resets once accumulation resumes past `1 mAh`

+- holding `PREV` clears the active group totals

+

+## Recording and Cable Testing

+

+- recording starts automatically when current rises above the configured low-current trigger

+- trigger range: `0.01 A` to `0.30 A`

+- graphing includes:

+  - voltage/current over time

+  - `D+` / `D-` voltage over time

+- cable resistance mode uses a two-step differential measurement:

+  1. measure directly at the charger under load

+  2. repeat through the cable under test at the same load

+

+Practical notes from the manual:

+

+- recommended cable-test load is approximately `1 A`

+- if voltage drop is too high, the tester can power down near `4 V`

+- the tester must be power-cycled after cable-resistance measurement to resume normal mode

+

+## Settings

+

+- auto screen-off: `0-9 min`

+- brightness: `0-5`

+- temperature unit: `C` / `F`

+- theme background color

+- theme foreground color

+- hidden boot menu options:

+  - Chinese UI

+  - English UI

+  - reset settings

+

+## Android App Notes

+

+Confirmed from the manual:

+

+- minimum Android version: `5.0`

+- app distribution:

+  - vendor MediaFire folder for `UM25`

+  - Google Play search term: `UM Meter`

+- pairing code: `1234`

+- app features include:

+  - Bluetooth connection

+  - export to phone storage

+  - sharing exported files to other apps

+  - multi-language UI

+  - voltage/current graph

+  - quick-charge mode display

+  - `D+` / `D-` voltage display

+  - brightness and screen-off adjustment

+  - temperature-unit switching

+  - data-group switching

+  - data-group clearing

+  - screen rotation

+  - low-current trigger adjustment

+

+## iOS App Notes

+

+Confirmed from the manual:

+

+- minimum iOS version: `8.0`

+- App Store search term: `UM Meter`

+- workflow described by the manual:

+  - tap `Find` to discover nearby Bluetooth devices

+  - connect to the device

+  - enter `data communication`

+  - export form files

+  - share exported files to other apps

+  - select language in the personal center

+- manual states the iOS app version matching the document is `1.2.1`

+

+## PC Software Notes

+

+- explicitly labeled for `UM25C`

+- supported OS: `Windows 7 and above`

+- manual references PC package `UM25C PC Software V1.3.zip`

+- manual says to install `Arial Unicode MS` before unzipping/installing

+- PC connection flow:

+  - enable device Bluetooth

+  - pair from Windows

+  - inspect Bluetooth COM-port assignment

+  - use the outgoing COM port labeled for `UM25C`

+  - connect once the tester Bluetooth indicator becomes steady

+

+Important PC notes from the manual:

+

+- prefer the Windows built-in Bluetooth driver, not the adapter vendor driver

+- after power-cycling the tester, select the COM port again

+- do not press tester buttons during communication because error data may appear

+- exported graph data is intended for Microsoft Office Excel

+

+## Relevance for This Project

+

+Useful as a product-behavior reference:

+

+- confirms `UM25/UM25C` as a distinct documented model family

+- confirms the same six-page device UI model used in related manuals

+- confirms app-visible concepts we may need to represent in our model:

+  - active data group

+  - quick-charge mode

+  - `D+` / `D-` levels

+  - graph pages

+  - low-current trigger

+  - brightness and screen-off settings

+- confirms that `UM25C` had vendor-supported Android, iOS, and Windows software

+

+Important transport caveat:

+

+- the PC section clearly describes Bluetooth COM-port use, which fits classic serial-port style communication on Windows

+- the same manual also describes an iOS app, which means transport behavior cannot be reduced to the PC workflow alone

+- for implementation, radio and protocol details still need to be verified from runtime captures or app analysis before we lock assumptions

+

+## Relationship to Current App Scope

+

+- `UM24` classic-Bluetooth serial support remains out of scope for this application

+- this manual makes `UM25C` a higher-priority reference than `UM24C` for supported-device investigation

+- the `C` variants remain the main target family until runtime evidence suggests otherwise

+

+## Open Questions

+

+- whether `UM25C` uses one Bluetooth mode for Android/Windows and another for iOS

+- whether the iOS app talks to the same payload structure as Android and PC software

+- whether `UM34C` and `UM25C` share identical transport and field mappings

+# UM34C Manual Working Summary

+

+This note summarizes the imported manual [`User_Manual_UM34C.pdf`](../Manuals/User_Manual_UM34C.pdf) as a working reference for the project.

+

+## Source Snapshot

+

+- imported file: `Documentation/Research Resources/Manuals/User_Manual_UM34C.pdf`

+- source filename: `User_Manual_UM34C.pdf`

+- pages: `12`

+- creator metadata: `Microsoft Word 2016`

+- SHA-1: `71f6ccae85ba6930e626208e24f66dead07d3e52`

+

+## Scope and Labeling Caveat

+

+The document should be treated as a family-level reference, not yet a clean single-model specification.

+

+Confirmed inconsistencies inside the PDF:

+

+- the source filename points to `UM34C`

+- the first instruction heading says `-Model: UM25/UM25C`

+- the technical parameter block says `Model: UM34/UM34C`

+- the app section is titled `UM34C Android APP Instruction`

+

+Working interpretation:

+

+- the manual most likely describes a closely related `UM25C` / `UM34C` family device

+- UI flow and user-facing features are likely reusable across the family

+- protocol details should not be assumed from this manual alone because it is operational documentation, not a transport spec

+

+## Confirmed Device Capabilities

+

+- color LCD display: `1.44 inch`

+- measurement ranges:

+  - voltage: `4-24.00 V`

+  - current: `0-4.000 A`

+  - capacity: `0-99999 mAh`

+  - energy: `0-99999 mWh` and `0-999.99 Wh`

+  - temperature: `-10 C to 100 C`

+- refresh rate: `2 Hz`

+- quick-charge recognition claims support for:

+  - `QC2.0`

+  - `QC3.0`

+  - Apple `2.4A / 2.1A / 1A / 0.5A`

+  - `Android DCP`

+  - `SAMSUNG`

+- port and hardware notes:

+  - USB 3.0 `A male`

+  - USB 3.0 `A female`

+  - `Micro USB`

+  - `Type-C input`

+  - Bluetooth switch and Bluetooth status indicator are present on the `C` variant

+

+## Important Functional Notes

+

+### Measurement and storage

+

+- the main screen exposes voltage, current, power, temperature, accumulated `mAh`, accumulated `mWh`, load impedance, and current data-group index

+- the tester offers `10` data groups: `0-9`

+- groups `1-9` persist accumulated `mAh` and `mWh` across power cycles

+- group `0` behaves as temporary storage and is cleared when accumulation resumes beyond `1 mAh`

+- holding `PREV` clears the current accumulated `mAh` and `mWh`

+

+### Screen flow

+

+The manual describes six interface pages:

+

+- main measurement interface

+- quick-charge recognition interface

+- charging record interface

+- data cable impedance measurement interface

+- graphing interface

+- system parameter setting interface

+

+### Recording behavior

+

+- charging record mode auto-starts when current rises above a configurable trigger

+- trigger range: `0.01 A` to `0.30 A`

+- the device records accumulated capacity, energy, and elapsed time

+

+### Cable resistance measurement

+

+The cable test is a two-step differential measurement:

+

+1. connect the tester directly to the power supply and record voltage/current under load

+2. reconnect through the cable under test at the same load and record again

+

+Practical implications:

+

+- the manual recommends approximately `1 A` load for the test

+- if voltage drop is too high, the tester can brown out near `4 V`

+- after finishing the cable-resistance test, the manual says the tester must be power-cycled to return to normal measurement

+

+### Graphing

+

+- one graph view shows voltage and current over time

+- a second graph view shows `D+` / `D-` voltages over time

+

+### Settings

+

+User-facing settings documented in the manual:

+

+- auto screen-off: `0-9 min`

+- brightness: `0-5`

+- temperature unit: `C` / `F`

+- theme background color

+- theme foreground color

+

+## Android App Notes

+

+The manual includes an Android app section, but still at workflow level only.

+

+Confirmed app notes:

+

+- minimum Android version: `5.0`

+- pairing code: `0000` or `1234`

+- the app can:

+  - connect over Bluetooth

+  - export recorded data to phone storage

+  - switch language

+  - display graph pages

+  - show quick-charge and `D+` / `D-` values

+  - adjust brightness and screen-off timer

+  - switch temperature units

+  - clear current data group

+  - rotate the tester display

+  - adjust low-current trigger value

+

+## Relevance for This Project

+

+Useful as a product-behavior reference:

+

+- confirms the user-visible page model and feature set

+- confirms persistent data groups and their semantics

+- confirms graphing and recording features that may exist in app or payload state

+- confirms Bluetooth control exists on the `C` variant

+- confirms `D+` / `D-` readings and quick-charge mode are first-class features

+

+Not sufficient as a protocol reference:

+

+- no BLE services, characteristics, or packet format are documented

+- no field-level payload mapping is documented

+- no desktop or mobile transport framing is documented

+- no model-to-model compatibility table is documented

+

+## Working Assumptions

+

+- treat this manual as valid for shared UI concepts across at least part of the `UM25C` / `UM34C` family

+- do not treat quick-charge detection strings as authoritative protocol identifiers

+- do not assume the USB-C input is a full Type-C measurement path; the manual limits it to a narrower role

+- continue comparing runtime observations with this manual before promoting anything to a hard specification

+

+## Open Questions

+

+- whether `UM25C` and `UM34C` expose identical Bluetooth payloads

+- whether the Android app supports more device variants than the manual title suggests

+- whether the non-`C` variants share the same UI/page layout but without Bluetooth control

+# Vendor Contacts

+

+This folder stores vendor contact documents and notes extracted from archived material.

+

+## Imported Files

+

+### `Factory technical support and  conctact way .docx`

+

+- status: added to repository

+- source: `UM24` archive

+- SHA-1: `f1bda965c4845e51fe901d49a3ebb52f6fc9fbbb`

+- extraction status: key contact fields manually extracted

+- duplicate note: the same file was also present in the `TC66` archive and was not imported twice

+

+## Extracted Contact Fields

+

+- email: `1749808860@qq.com`

+- WeChat: `15868147353`

+- AliExpress store: `https://rdtech.aliexpress.com/store/923042`

+- YouTube: `https://www.youtube.com/channel/UCy73jJ5-ZqhPzT7wJ6KTIaw?view_as=subscriber`

+		1C6B6B972A2D4F5100A0B001 /* USB tester UM24C - User Manual.pdf */ = {isa = PBXFileReference; lastKnownFileType = image.pdf; path = "USB tester UM24C - User Manual.pdf"; sourceTree = "<group>"; };

+		1C6B6BA52A2D4F5100A0B001 /* TC66.pdf */ = {isa = PBXFileReference; lastKnownFileType = image.pdf; path = TC66.pdf; sourceTree = "<group>"; };

+		1C6B6BA62A2D4F5100A0B001 /* User Maual for Operation and PC software and APP of TC66(C) Type-c USB PD Trigger Meter 2019.6.5.pdf */ = {isa = PBXFileReference; lastKnownFileType = image.pdf; path = "User Maual for Operation and PC software and APP of TC66(C) Type-c USB PD Trigger Meter 2019.6.5.pdf"; sourceTree = "<group>"; };

+		1C6B6BAA2A2D4F5100A0B001 /* UM25 User Manual.pdf */ = {isa = PBXFileReference; lastKnownFileType = image.pdf; path = "UM25 User Manual.pdf"; sourceTree = "<group>"; };

+		1C6B6BAB2A2D4F5100A0B001 /* User_Manual_UM34C.pdf */ = {isa = PBXFileReference; lastKnownFileType = image.pdf; path = User_Manual_UM34C.pdf; sourceTree = "<group>"; };

+		1C6B6B982A2D4F5100A0B001 /* Software README.md */ = {isa = PBXFileReference; lastKnownFileType = net.daringfireball.markdown; path = README.md; sourceTree = "<group>"; };

+		1C6B6B992A2D4F5100A0B001 /* Android Apps README.md */ = {isa = PBXFileReference; lastKnownFileType = net.daringfireball.markdown; path = README.md; sourceTree = "<group>"; };

+		1C6B6B9A2A2D4F5100A0B001 /* PC Software README.md */ = {isa = PBXFileReference; lastKnownFileType = net.daringfireball.markdown; path = README.md; sourceTree = "<group>"; };

+		1C6B6B9B2A2D4F5100A0B001 /* Vendor Contacts README.md */ = {isa = PBXFileReference; lastKnownFileType = net.daringfireball.markdown; path = README.md; sourceTree = "<group>"; };

+		1C6B6B9C2A2D4F5100A0B001 /* UM Meter_V3.0.5.apk */ = {isa = PBXFileReference; lastKnownFileType = file; path = "UM Meter_V3.0.5.apk"; sourceTree = "<group>"; };

+		1C6B6B9D2A2D4F5100A0B001 /* RuiDeng_V1.0.2.apk */ = {isa = PBXFileReference; lastKnownFileType = file; path = RuiDeng_V1.0.2.apk; sourceTree = "<group>"; };

+		1C6B6BA72A2D4F5100A0B001 /* TC66C_V1.1.6.apk */ = {isa = PBXFileReference; lastKnownFileType = file; path = TC66C_V1.1.6.apk; sourceTree = "<group>"; };

+		1C6B6BA82A2D4F5100A0B001 /* RuiDengUSBMeter_V1.0.0.6.rar */ = {isa = PBXFileReference; lastKnownFileType = file; path = RuiDengUSBMeter_V1.0.0.6.rar; sourceTree = "<group>"; };

+		1C6B6B9F2A2D4F5100A0B001 /* Factory technical support and  conctact way .docx */ = {isa = PBXFileReference; lastKnownFileType = file; path = "Factory technical support and  conctact way .docx"; sourceTree = "<group>"; };

+		1C6B6BA42A2D4F5100A0B001 /* UM24-UM25-UM34 Family Compatibility Note.md */ = {isa = PBXFileReference; lastKnownFileType = net.daringfireball.markdown; path = "UM24-UM25-UM34 Family Compatibility Note.md"; sourceTree = "<group>"; };

+		1C6B6BA92A2D4F5100A0B001 /* TC66 Resource Inventory.md */ = {isa = PBXFileReference; lastKnownFileType = net.daringfireball.markdown; path = "TC66 Resource Inventory.md"; sourceTree = "<group>"; };

+		1C6B6BAC2A2D4F5100A0B001 /* UM34C Manual Working Summary.md */ = {isa = PBXFileReference; lastKnownFileType = net.daringfireball.markdown; path = "UM34C Manual Working Summary.md"; sourceTree = "<group>"; };

+		1C6B6BAD2A2D4F5100A0B001 /* UM25 Manual Working Summary.md */ = {isa = PBXFileReference; lastKnownFileType = net.daringfireball.markdown; path = "UM25 Manual Working Summary.md"; sourceTree = "<group>"; };

+		1C6B6BAE2A2D4F5100A0B001 /* TC66 Manuals Working Summary.md */ = {isa = PBXFileReference; lastKnownFileType = net.daringfireball.markdown; path = "TC66 Manuals Working Summary.md"; sourceTree = "<group>"; };

+		1C6B6BAF2A2D4F5100A0B001 /* TC66C Transport and Payload Working Note.md */ = {isa = PBXFileReference; lastKnownFileType = net.daringfireball.markdown; path = "TC66C Transport and Payload Working Note.md"; sourceTree = "<group>"; };

+				1C6B6BA02A2D4F5100A0B001 /* Software */,

+				1C6B6BA32A2D4F5100A0B001 /* Vendor Contacts */,

+				1C6B6B972A2D4F5100A0B001 /* USB tester UM24C - User Manual.pdf */,

+				1C6B6BA52A2D4F5100A0B001 /* TC66.pdf */,

+				1C6B6BA62A2D4F5100A0B001 /* User Maual for Operation and PC software and APP of TC66(C) Type-c USB PD Trigger Meter 2019.6.5.pdf */,

+				1C6B6BAB2A2D4F5100A0B001 /* User_Manual_UM34C.pdf */,

+				1C6B6BAA2A2D4F5100A0B001 /* UM25 User Manual.pdf */,

+				1C6B6BA42A2D4F5100A0B001 /* UM24-UM25-UM34 Family Compatibility Note.md */,

+				1C6B6BA92A2D4F5100A0B001 /* TC66 Resource Inventory.md */,

+				1C6B6BAC2A2D4F5100A0B001 /* UM34C Manual Working Summary.md */,

+				1C6B6BAD2A2D4F5100A0B001 /* UM25 Manual Working Summary.md */,

+				1C6B6BAE2A2D4F5100A0B001 /* TC66 Manuals Working Summary.md */,

+		1C6B6BA02A2D4F5100A0B001 /* Software */ = {

+			isa = PBXGroup;

+			children = (

+				1C6B6B982A2D4F5100A0B001 /* Software README.md */,

+				1C6B6BA12A2D4F5100A0B001 /* Android Apps */,

+				1C6B6BA22A2D4F5100A0B001 /* PC Software */,

+			);

+			path = Software;

+			sourceTree = "<group>";

+		};

+		1C6B6BA12A2D4F5100A0B001 /* Android Apps */ = {

+			isa = PBXGroup;

+			children = (

+				1C6B6B992A2D4F5100A0B001 /* Android Apps README.md */,

+				1C6B6B9D2A2D4F5100A0B001 /* RuiDeng_V1.0.2.apk */,

+				1C6B6B9C2A2D4F5100A0B001 /* UM Meter_V3.0.5.apk */,

+				1C6B6BA72A2D4F5100A0B001 /* TC66C_V1.1.6.apk */,

+			);

+			path = "Android Apps";

+			sourceTree = "<group>";

+		};

+		1C6B6BA22A2D4F5100A0B001 /* PC Software */ = {

+			isa = PBXGroup;

+			children = (

+				1C6B6B9A2A2D4F5100A0B001 /* PC Software README.md */,

+				1C6B6BA82A2D4F5100A0B001 /* RuiDengUSBMeter_V1.0.0.6.rar */,

+			);

+			path = "PC Software";

+			sourceTree = "<group>";

+		};

+		1C6B6BA32A2D4F5100A0B001 /* Vendor Contacts */ = {

+			isa = PBXGroup;

+			children = (

+				1C6B6B9B2A2D4F5100A0B001 /* Vendor Contacts README.md */,

+				1C6B6B9F2A2D4F5100A0B001 /* Factory technical support and  conctact way .docx */,

+			);

+			path = "Vendor Contacts";

+			sourceTree = "<group>";

+		};

+				1C6B6BAF2A2D4F5100A0B001 /* TC66C Transport and Payload Working Note.md */,