# 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 serial-port style communication on Windows
- the imported `DX-BT18` module manual shows one plausible way this can coexist with iOS support: the module can expose SPP-style workflows for desktop while also supporting BLE for iOS
- for implementation, exact module identity is still not fully proven, but the current `FFE0` / `FFE1` transport assumption is now much better supported

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