powerz

ChargerLAB POWER-Z KM003C: hardware notes

Research date 2026-11-16. Desk research only; the physical device was not touched. Device label: MODEL: KM003C, DC 0-50V 0-6A, USB VID 0x5FC9, PID 0x0063.

O Official ChargerLAB / POWER-Z material: chargerlab.com, power-z.com (including the official product page S3), power-z.cn, the official manual and official downloads.
3P Independent third party: reviews, a hobbyist teardown, the Linux kernel.
C Community reverse engineering, mainly the okhsunrog GitHub repositories. These describe one HW2.1 unit and decompiled stock firmware, and ChargerLAB has not confirmed them. Treat them as strong leads, not specifications.
I My own inference or reading of a photo. It is unverified.

Links such as S2 point to the Sources list.

1. Overview and specs

The KM003C is the successor to the KM002C. ChargerLAB says the KM002C "was discontinued due to the shortage of chips" S1. The KM003C is an in-line USB-C power meter and PD analyzer/trigger. It has a USB-C plug, a USB-C receptacle and a third USB-C port labelled "HID", which powers the unit and connects it to a PC O S1 S2 S6.

SpecValueSource
Size / weight36.5 × 35.5 × 8.7 mm, 16.5 gO S1 S5
Display1.54" IPS, 240×240O S1 S3 S5
PortsUSB-C plug and USB-C receptacle (both "support USB4 Gen3, bidirectional"), plus a USB-C "HID" port for PC and powerO S2 S3 S6
HID portUSB-C (5 V). It is the only port that talks to the PCO S1 S10
VBUS range0–50 V continuous; 6 A continuous and instantaneousO S2 (spec table)
Marketing rating"up to 50V 6A (240W in PD)"O S3 S1
D+/D− and CC1/CC2 withstand50 V (the D+/D− figure is footnoted "technically supported without enough experiments")O S2
Port internal resistance"About 20 mΩ" (the KM002C is about 28 mΩ)O S1 S5
Typical operating current15–50 mA (the KM002C is 8–25 mA)O S1 S5
Input impedance / anti-surge>800 kΩ / 4 kVO S2
Operating / storage temperature−10 to +65 °C / −45 to +110 °CO S2
Processor / ADC"This tester integrates ARM Cortex-M4 processor and 20 bit ADC"O S3; 20-bit ADC also in S1 S2
PC data volume"The PC software can obtain 10 million pieces of data at a time"O S3
Storage"4MB Flash"; "Capacity 4MB"O S2 S1
Gravity sensor (auto-rotate)YesO S1 S3
SupercapacitorYes; "can run for five to ten seconds after disconnecting"O S1
Reverse-polarity protectionNone. "The USB tester has no reverse voltage protection"O S2
LanguagesEnglish / ChineseO S1 S3
Price$109.99O S1 S3

Known hardware quirks

2. Components

PartFunction / notesEvidence and source
HDSC (Huada) HC32F460, marking F460JETA (HC32F460JETA, LQFP48)Main MCU: Arm Cortex-M4F, 512 KB flash, 192 KB SRAM, 4 KB retention RAM3P The teardown author names "Huada HDSC HC32F460" and its specs S17. C The F460JETA marking is read from the photo, and the firmware matches the HC32F460 register map S19. 3P AnandTech names the same MCU, but only by inference from a KM002C photo S20. O says only "ARM Cortex-M4" S3
MCU clockConfigured to 192 MHz from a 16 MHz inputC firmware/register analysis S19. I I read "YXC 16.000" on a crystal in the teardown photo S17
TI INA22920-bit power monitor (VBUS/IBUS, die temperature) on SPI2C Photo marking "229", plus manufacturer/device IDs 0x5449/0x2291 read over SPI on HW2.1 S19. O says only "Built-in 20-bit ADC (high-precision measurement IC)" S2
TI INA228 (claimed)20-bit I²C power monitorO ChargerLAB's INA228 article is about the KM002C S11. 3P AnandTech says "The INA228 in the KM003C has a 20-bit ADC", but this rests on the KM002C photo S20. For the KM003C, the evidence points to INA229 instead
ADC temperature sensorPC software: "T1 ... is ADC chip temperature, accuracy ±1°C"; "T2 is microcontroller temperature, accuracy ±5°C"O S4
MCU internal ADC1D+, D−, CC1, CC2 voltages (pads PA0–PA3)C S19 (docs/line-adc.md). AnandTech guessed "at least 5 ADCs" 3P S20
Current shuntValue not confirmed.
  • Official specs give only "Current Sampling Resistor: 2W/20PPM".
  • The ~20 mΩ figure is whole-port insertion resistance, not the shunt.
  • AnandTech says "20 mOhm shunt resistors", inferred from a KM002C photo: unverified.
  • The community says "No physical shunt resistance is inferred".
  • I The teardown photo shows a large resistor marked "5L0F"; its value is unverified.
O S2 S5; 3P S20; C S19; I S17
Current sense amplifierBuilt into the INA229 (no separate amplifier identified)C / I S19
USB-PD PHY / CC controllerNo dedicated PD PHY chip identified. The community finds that PD runs on HC32F460 peripherals: CMP1 comparator with a DAC1 reference for receive, and TimerA2 with DMA for transmit, plus external analog parts. CC Rd is switched by MCU GPIO PB6 and AW9523B P0_3. ChargerLAB does not document thisC S19 (README, pd_phy_hc32f460.md, board_bringup.md)
USB device controllerHC32F460 on-chip Synopsys DWC2-compatible USB FS OTG with internal PHY (PA11/PA12)C S18 S19
Display1.54" IPS 240×240. Controller is ST7789-compatible on a QSPI bus shared with the flash. A 240×240 ST7789 replacement panel was reported to workO S1; C S18 S19; the replacement report is cited via S19 from S23 (not read)
AWINIC AW9523BI²C GPIO/LED expander at 0x5B (panel reset, backlight, CC2 Rd control)C Marking visible in the teardown photo, and register sequences match S19 S17
SC7A20-family accelerometerAuto-rotation ("gravity sensor"); I²C 0x19, WHO_AM_I 0x11C S18 S19; O confirms a gravity sensor exists S1
External flash4 MiB NOR (legacy ID 0x8515; exact part unknown). Holds factory settings and calibration at 0x3FF100. I It presumably also holds the offline records counted in the official "4MB Flash"C S18 S19; O S2
SupercapacitorKAMCAP 3.0 V 0.35 F3P teardown S17
Built-in loadChargerLAB credits MTK-PE/VOOC/SVOOC detection to a "built-in load". I An "8R2" (8.2 Ω?) power resistor is visible in the photo; its function is unverifiedO S1; I S17
Crypto / auth chipNone identified. Firmware updates (.mencrypt) and the PC-streaming authentication use AES-128-ECB. The community attributes this to software and the HC32F460's on-chip AES block. The authentication checks the MCU unique ID at 0x40010450C S18 (docs/firmware/format.md, docs/features/authentication.md), S19 (overview.md)
BootloaderNative DFU loader in internal flash below 0x4000 C. Official: Back "Press and hold it when power off, you can enter the DFU mode" O. Community: hold Exit/Back while connecting power to the HID port CS2 S6 S18 S19

Other markings visible in the teardown photo that I could not identify I: "SSL56" (likely a Schottky), "8633P", "85337", "2268" (8-pin) and "PQ82/H1PC" (power package). The photo is linked at S17.

3. Schematic and teardown availability

4. Measurement capabilities

Ranges, resolution and accuracy (official figures, quoted as published)

FigureValueSource
Voltage / current range0–50 V / 0–6 AO S2 S5
Voltage / current resolution0.000001 V / 0.000001 A (1 µV / 1 µA display digits)O S5 (2024.1 comparison chart)
Accuracy (chart)"0.1%+2d"O S5
"Voltage Accuracy" / "Current Accuracy" (manual table)0.00002 V / 0.000003 AO S2
Voltage / current gain error (manual table)"0.05  0.25 %" (two columns, no headers; probably typ/max)O S2
Gain error vs temperature"5  20 ppm/°C" (same two-column layout)O S2
"Accuracy" (launch comparison image)"0.00003" (no unit given)O S1
ADC bits20O S1 S2 S3
Bidirectional currentYes. The display shows a direction arrow, and the Linux driver reports direction as the sign of curr1_input (label IBUS)O S12; 3P S16
Wire units (official API)Vbus/Ibus as int32 in µV / µA; CC1/CC2/D+/D−/Vdd as uint16 at 0.1 mV; also raw (uncalibrated) averages, internal temperature and a 2-bit Rate fieldO S14 (KM002C&3C API Description.docx)
Averaged vs instantaneous valuesAnandTech found the API's Vbus_avg/Ibus_avg change "only once every second". The instantaneous values are "the first two words in the returned ADC data struct"3P S20 (page 3)

The official accuracy figures disagree across documents (0.1%+2d; 20 µV / 3 µA; 0.00003). None is clearly labelled as reading accuracy versus resolution. A client should not hard-code an accuracy claim.

Sample rates, by context

No single official list exists. Each context reports something different:

ContextRatesSource
Manual, "Features" section"Data Collection: Up to 1,000 times per second"; "Programmable Collection Speed: 1/10/50/100 times per second"O S2
On-device Dashboard refresh"2/10/50/1k Hz" (manual) vs "4sps, 15sps, 60sps, and 1Ksps" (2024 "10 functions" article)O S2 vs S6
PC software (V2.x) recorder"1SPS, 10SPS, 50SPS and 1KSPS". The cache depth is configurable up to 1999 MB, about 19.99 M points. AnandTech saw the same rates: "Available rates are 1, 10, 50, and 1000 samples per second"O S7; 3P S20
PC software V2.5.1 changelog (2026-04-16)"Added a notice that 200 SPS may affect protocol control functionality". This implies a 200 SPS option in recent PC software; I found no other documentation of itO S2
POWER-Z Lab V3.0 (beta)"Sampling Rate (Adjustable from 0.1–1K SPS)". Sub-1 SPS is probably host-side decimation IO S10
Temperature channelPC 2.1.0: internal temperature monitoring is "only valid for 1/10/50 SPS"O S2
Community wire protocol (StartGraph rate index)0 = 2 SPS, 1 = 10 SPS, 2 = 50 SPS, 3 = 1000 SPS. Measured effective rates were about 1.8 / 9.6 / 47 / 956 SPSC S18 (docs/features/adcqueue.md)
Plain ADC snapshot polling~200 ms (~5 Hz) in community captures. AnandTech polled every 100 msC S18; 3P S20
10 kSPSNo official claim found. The official API header defines ATT_ADC_QUEUE_10K = 0x004 //10K数据 ("10K data"), but the community reports it "never observed in 20k+ packets, including 1000 SPS runs"O S14; C S18
VBUS ripple module (separate on-device feature)Selectable "20.0k 1250μs to 8.0M 3μs" sample ratesO S2 S6

Offline (stand-alone) recording

5. Protocol detection and PD features

Auto-detection (KM003C), from the manual: PD2.0 / PD2.0 PPS / PD3.1 (EPR) / QC2.0 / QC3.0 / QC3+ / QC4+ / QC5 / AFC / FCP / SCP / VIFC / UFCS / APPLE2.4A / SAMSUNG / VOOC / MTK PE / SFCP / TFCP O S2. MTK-PE, VOOC and SVOOC detection is "thanks to built-in load" and is KM003C-only O S1 S2. The 2024 article's list also names SVOOC O S6.

Trigger, on-device ("Application → Charging protocol"): PD2.0 / PPS / EPR / QC2.0 / QC3.0 / AFC / FCP / SCP / VIFC / UFCS / VOOC. VOOC/SVOOC needs the original cable and a small load. MTK PE and SFCP cannot be triggered O S2 S6.

Trigger from PC (firmware ≥1.7.9 with PC 2.3.0): PD (up to 28 V 5 A shown), UFCS, QC2.0/3.0, FCP, SCP, AFC, VFCP, SFCP O S13. ChargerLAB also documents triggering over the CDC virtual serial port in "KM003C/002C Protocol Trigger by Virtual Serial Port (Instructions)". The manual and FAQ name this document O S2 S4. I read it from the community-hosted copy (S18 docs/official/); §6 summarizes it.

PD features

Firmware history (tester)

Full list in S2 and S9. Highlights:

O S8 S9 S2

6. Software, SDK and USB interfaces

PC software

Download URLs seen on official pages

The official product page S3 has no direct download links. It says "Please go to our official website to get the manual and PC software", and its navigation leads to the KM003C Technical Support page S4, where most of these links appear. I downloaded only the API toolkit (to read its source and docx) and the driver zip (file listing only). The software-re agent is handling the binaries.

WhatURLWhere seen
PC software and tester firmware (KM003C/KM002C), Google Drivedrive.google.com/drive/folders/1u63v7TAPZl0DohsziWwOkfRA4Vuk6J1QO S4 S8
PC software, direct ziphttps://chargerlab.oss-cn-shenzhen.aliyuncs.com/POWER-Z.zipO S4
All POWER-Z documents and apps, Google Drivedrive.google.com/drive/folders/1PGeIclfAEKazLUFfdVbLMX2mprdGIbVeO chargerlab.com/power-z-technical-support
All POWER-Z documents and apps, Dropboxdropbox.com/sh/wh8rsfvbhxye5g8/…O same page
Online English manual (includes version history)docs.google.com/document/d/1T55UeixUNN9La3tzAF0jO45Snw_rrd9RVGt3XQeRIM8O S4
Chinese manual / PC software changelog / FAQ (shimo.im; not read)shimo.im/docs/3WkKVWHtCkXkVQQk · shimo.im/docs/DhvPdJpdHQGK6xtq · shimo.im/docs/Ee32MX71YehxZjA2O S24
Windows driver installer (InstallDriver.exe inside)https://www.chargerlab.com/wp-content/uploads/2022/07/InstallDriver.zipO S4
Windows 7 virtual-serial-port driverhttps://power-z.oss-cn-hongkong.aliyuncs.com/driver.exeO Virtual Serial Port instructions (S18 copy)
API toolkit (libusb demo and API description)https://www.chargerlab.com/wp-content/uploads/2019/05/hiddemo_vs2019_for-KM002C3C.zipO S4
POWER-Z Lab V3.0 Beta (Win/macOS), Telegramhttps://t.me/+oGliSbeuYts1Y2Y1O S10
"POWER-Z" phone apps in the site navigation. Their relation to the KM003C is not established; they appear to be a separate phone-only appGoogle Play: cn.powerz.powerdumper · App Store: id6754865141O S3

Official API / SDK

USB interfaces

Official: the API description docx O S14 (translated) says the device offers three interfaces with one command set:

  1. USER: called WinUSB on Windows and "USB USER" elsewhere; about 200 KB/s.
  2. CDC virtual serial: baud rate ignored; about 200 KB/s; works with any serial terminal.
  3. HID: needs no driver on any platform; 64-byte packet limit; about 60 KB/s.

The manual summarizes this as "Composite USB port, driver-free" O S2. AnandTech restates the three interfaces ("WinUSB (vendor specific interface) device, a HID device, or a virtual serial port (CDC)"). On their 2023 Ubuntu 20.04 setup only the HID interface was bound (to usbhid), and no /dev/ttyACM0 appeared 3P S20.

Naming caution: in ChargerLAB documents, "HID" is also the name of the physical USB-C port used for PC and power. "Connect via the HID port" therefore does not mean the PC software uses the HID class O S2 S10.

Community descriptor dump (HW2.1) C S18 docs/usb_transport.md:

PropertyValue
DeviceUSB 2.10, Full Speed, class 0xEF (IAD), 100 mA
Family PIDsKM002C 0x0061, KM003C 0x0063
IF0Vendor 0xFF, bulk EP 0x01 OUT / 0x81 IN, 64 B. Linux binds powerz here
IF1CDC ACM, EP 0x83 interrupt IN, 8 B
IF2CDC Data, bulk EP 0x02 / 0x82, 64 B. Linux binds cdc_acm to IF1+IF2 (/dev/ttyACM*)
IF3HID 1.11, interrupt EP 0x05 / 0x85, 64 B, 1 ms. Linux binds usbhid (/dev/hidraw*)
BOSPlatform capability UUID {d8dd60df-4589-4cc7-9cd2-659d9e648a9f} with a 170-byte vendor-request blob. I This UUID is the Microsoft OS 2.0 descriptor capability, which lets Windows bind WinUSB automatically. That would fit the "driver-free" claim, but it is unverified

Endpoint discrepancy: AnandTech wrote that ChargerLAB says commands can also go to "EP 5 OUT and EP 3 OUT ... at addresses 0x5 and 0x3" 3P S20. The community dump puts the CDC data OUT endpoint at 0x02 and has no 0x03 OUT. The firmware may have changed, or one source is wrong; this is unresolved I.

Which interface the official app uses is not documented by ChargerLAB.

Together this suggests the PC app uses the vendor/WinUSB interface (IF0) I.

7. Notes for a CLI client (summary of the above)

Sources

  1. S1 ChargerLAB, "Introducing the Brand New POWER-Z KM003C" (2022-11-16): https://www.chargerlab.com/introducing-the-brand-new-power-z-km003c/. Spec images: key specifications, KM003C vs KM002C, PDO/protocol test
  2. S2 Official online manual, "ChargerLAB POWER-Z KM003C/KM002C USB Tester User Manual". It includes the version history, spec table, protocol lists and storage limits, and is linked from S4: https://docs.google.com/document/d/1T55UeixUNN9La3tzAF0jO45Snw_rrd9RVGt3XQeRIM8
  3. S3 Official product page, POWER-Z store, "ChargerLAB POWER-Z KM003C": https://www.power-z.com/products/chargerlab-power-z-km003c
  4. S4 POWER-Z KM003C/KM002C Technical Support (FAQ, downloads, API toolkit, driver): https://www.power-z.com/blogs/technical-support/power-z-km003c-km002c-technical-support
  5. S5 "Comparison of ChargerLAB POWER-Z USB PD Testers (2024.1)" chart, linked from chargerlab.com/power-z-technical-support: https://www.chargerlab.com/wp-content/uploads/2024/01/2024011906294954.png
  6. S6 ChargerLAB, "Inventory of 10 Commonly Used Functions of Power-Z KM003C" (2024-02-12): https://www.chargerlab.com/inventory-of-10-commonly-used-functions-of-power-z-km003c/
  7. S7 ChargerLAB, "How to Use ChargerLAB POWER-Z KM003C Tester to Record Charging Data" (2023-02-13): https://www.chargerlab.com/how-to-use-chargerlab-power-z-km003c-tester-to-record-charging-data-offline/
  8. S8 ChargerLAB, "V.2.0.7 | The New Software Version of ChargerLAB POWER-Z KM003C" (2026-09-30): https://www.chargerlab.com/v207-the-new-software-version-of-chargerlab-power-z-km003c/
  9. S9 ChargerLAB, "V.2.0.6 …" (2026-08-10, version history back to 1.8.0): https://www.chargerlab.com/v206-the-new-software-version-of-chargerlab-power-z-km003c/. Also V2.0.5 and V1.9.9
  10. S10 ChargerLAB, "ChargerLAB POWER-Z Lab V3.0 Beta: Now Available for Mac!" (2025-03-19): https://www.chargerlab.com/chargerlab-power-z-lab-v3-0-beta-now-available-for-mac/
  11. S11 ChargerLAB, "ChargerLAB POWER-Z KM002C PD3.1 Tester Adopts The TI INA228" (2022-08-19): https://www.chargerlab.com/chargerlab-power-z-km002c-pd3-1-tester-adopts-the-ti-ina228/
  12. S12 ChargerLAB, "Bi-directional Current Detection | … KM003C" (2023-05-11): https://www.chargerlab.com/bi-directional-current-detection-the-cool-feature-of-chargerlab-power-z-km003c/
  13. S13 ChargerLAB, "Protocol Trigger Module on PC | The New Update of POWER-Z KM003C/2C" (2023-08-13): https://www.chargerlab.com/protocol-trigger-feature-on-pc-the-new-update-of-power-z-km003c-2c/
  14. S14 Official API toolkit hiddemo_vs2019_for-KM002C3C.zip (hiddemo.cpp, KM002C&3C API Description.docx): https://www.chargerlab.com/wp-content/uploads/2019/05/hiddemo_vs2019_for-KM002C3C.zip
  15. S15 Official Windows driver installer: https://www.chargerlab.com/wp-content/uploads/2022/07/InstallDriver.zip
  16. S16 Linux kernel, "Kernel driver POWERZ": https://docs.kernel.org/hwmon/powerz.html. v6.7 copy: https://www.kernel.org/doc/html/v6.7/_sources/hwmon/powerz.rst.txt (the v6.6 URL returns 404). Patch v3 (2023-09): https://lkml.iu.edu/hypermail/linux/kernel/2309.0/00753.html
  17. S17 tomoca2, "結局、分解補修したPOWER-Z KM003C" (teardown and repair, 2024-01-06): https://tomoca2.hatenablog.com/entry/2024/01/06/091942. Component-side photo: https://cdn-ak.f.st-hatena.com/images/fotolife/t/tomoca2/20240105/20240105220534.jpg
  18. S18 okhsunrog, km003c-protocol-research (community): https://github.com/okhsunrog/km003c-protocol-research. Files used: docs/usb_transport.md, docs/firmware/README.md, docs/firmware/format.md, docs/firmware/mtools_analysis.md, docs/features/adcqueue.md, docs/features/authentication.md, docs/official/ (copies of official ChargerLAB documents)
  19. S19 okhsunrog, km003c-firmware (community; HW2.1 bring-up): https://github.com/okhsunrog/km003c-firmware. Files used: README.md, docs/line-adc.md, docs/reverse-engineering/board_bringup.md, overview.md, hc32f460_analysis.md, pd_phy_hc32f460.md
  20. S20 AnandTech, Ganesh T S, "USB-C Power Metering with the ChargerLAB KM003C: A Google Twinkie Alternative?" (2023). The live URL now redirects to forums.anandtech.com. I read the Wayback Machine snapshot from 2024-03-01: page 1, page 2 (Hardware Design and Software Interface), page 3 (API Access on Linux), page 4 (API Access on Windows). Original: anandtech.com/show/18944
  21. S21 GIGAZINE, Power-Z KM003C review (2024-01-27): https://gigazine.net/gsc_news/en/20240127-power-z-km003c-usb-tester/
  22. S22 Doug Gilbert, "POWER-Z KM002C by ChargerLab" (third party; KM002C current-sign and VBUS-power notes): https://doug-gilbert.github.io/km002c/km002c.html
  23. S23 Reddit r/UsbCHardware, KM003C display-replacement report (September 2025). Not read; cited only via S19 overview.md: https://www.reddit.com/r/UsbCHardware/comments/1njcblc
  24. S24 POWER-Z China, "POWER-Z KM003C/2C/Lite更新日志:使用说明书、固件、客户端下载以及常见问题解答" (download and changelog page): https://www.power-z.cn/blogs/download/power-z-km003c-2c-lite

View this page's source on GitHub