# 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