USB-C power meters for a homelab: check PD voltage, cables and charging

A USB-C plug fits. That doesn’t mean your Pi, mini PC and charger have agreed on the power you expected. Choose ChargerLAB POWER-Z KM003C for detailed USB-C and higher-voltage PD work, AVHzY CT-3 for logging and scripting, or FNIRSI FNB58 for a desk full of USB-A and USB-C devices. A meter turns “why is this charging so slowly?” into something you can actually investigate.

Specs and operating steps come from the makers; the power examples below are calculated, not bench readings.

Quick picks: buy the investigation you need

USB-C and higher-voltage work: POWER-Z KM003C. The maker’s manual lists a 0–50V, 0–6A measurement range, PD/PPS analysis, cable e-marker reading and stored curves. Pick it when USB-C is the main event.
Logs and repeatable experiments: AVHzY CT-3. Offline recording, PC software and Lua scripting suit the person who wants to save a trace and come back to it.
Mixed USB ports: FNIRSI FNB58. USB-A, Micro-USB and USB-C connections make it useful for older chargers as well as newer kit. The selected model includes app support, alongside on-screen curves and PC tools.

Need the electricity used by the entire charger and computer? That’s a different job: start with our plug-in AC power meter guide. This guide follows the low-voltage USB side.

KM003C vs CT-3 vs FNB58

Meter, connections and range	Protocols and recording
POWER-Z KM003C: 0–50V, 0–6A per the manual. USB-C input/output plus a separate USB-C HID connection for PC/power.	PD/PPS triggering and protocol analysis; e-marker reader; offline curves and Windows PC analysis.
AVHzY CT-3: 0–6A; use the linked 26V version up to 26V. Current maker specifications list 0–29V for the family.	PD/PPS trigger, PC PD listener and e-marker reader. Offline logging up to 100 samples/s; PC logging up to 1,000 samples/s; Lua scripting.
FNIRSI FNB58: 4–28V, 0–7A, with a published 140W power limit. USB-A, Micro-USB and USB-C.	PD/PPS functions, PD monitoring and e-marker reading; offline voltage/current curves, PC software and Bluetooth app support.

The ChargerLAB manual, AVHzY specification page and FNIRSI manual are the references for those limits. Stay inside the meter’s voltage, current and power limits together; multiplying two separate range maxima doesn’t create a higher power rating.

For ordinary USB-C power checks around a mini PC, the useful features are a readable live display, the right connectors and a log you can save. For higher-voltage charging work, choose the KM003C’s wider range. A protocol name on a menu never expands the hardware’s voltage range.

What should you check?

Your question	The useful check
Is the Pi 5 supply offering the right profile?	Look for the official supply’s 5.1V/5A capability and observe the Pi’s low-voltage power path. Available current is a ceiling; the Pi draws what its workload needs.
Can this USB-C charger power my mini PC?	Read the computer’s documented PD input voltage and power, then compare them with the charger’s advertised profiles and the live negotiated voltage. First establish that the port accepts power at all.
Is this removable USB-C cable rated for 5A?	Read its e-marker current capability. Cables carrying more than 3A need electronic marking; the chip identifies the cable’s advertised capability.
Why does the USB SSD disconnect?	Record voltage/current while repeating the same copy, then change one cable or supply at a time. Use the enclosure’s documented host and power requirements too.

Texas Instruments explains the e-marker and VCONN mechanism: the connection powers the chip so its capability information can be read. A 5A result identifies a rating, not a command to draw 5A.

For enclosure choices and host compatibility, use the USB4 NVMe enclosure guide. Reading a cable’s USB4 capability field and testing a real high-speed storage link are separate tasks.

Try this first: read a cable with the KM003C

Give the mystery cable in your drawer a useful label. The maker’s menu walkthrough calls this Application → Modules → USB-C eMarker.

Disconnect the cable you want to inspect from all equipment.
Power the KM003C through its separate HID USB-C connection, following the manual’s independent-power arrangement.
Open Application → Modules → USB-C eMarker.
Insert one end of the cable into the meter’s USB-C female measurement socket, leaving the far end free.
Read the current capability and the available cable information. For a 5A job, look for a 5A rating; save the result or label the cable.
If the meter asks you to reverse the connector, follow that prompt and retry. Then exit the cable-reading function before changing to a different kind of test.

The e-marker is the cable’s identity card. Follow it with the actual charging or data task you care about. A cable can advertise a capability while a damaged connector still makes it troublesome in use.

Watch the negotiation; don’t force a voltage into the computer

Normal inline monitoring lets the charger and device negotiate while you watch voltage, current and power. Active triggering makes the tester request a charger output itself. Start with normal monitoring when a Pi or mini PC is attached.

The CT-3 operating manual tells you to turn its PD switch off after using trigger/listener functions and to avoid attaching equipment that cannot tolerate a triggered voltage. For the FNB58, follow its manual’s PD-switch instructions after trigger, listener and cable-reading functions. Use one measurement input/output pair at a time.

For a simple charging check, connect the supply, meter and device in the manual’s measurement arrangement, with active trigger functions disabled. Observe the negotiated voltage and current under a repeatable workload. Save a short trace if the problem comes and goes; a changing reading often tells you more than a single screenshot.

The Pi 5 example: why 27W doesn’t mean 27W at every voltage

The official Raspberry Pi supply brief lists these profiles. Multiply voltage by current to get the advertised output capacity:

Official supply profile	Calculated capacity
5.1V × 5A	25.5W
9V × 3A	27W
12V × 2.25A	27W
15V × 1.8A	27W

For the Pi, the important capability is 5.1V/5A. Don’t select a higher voltage just to make the displayed watts match the supply’s name. The supply’s cable is captive, so the removable cable-reading exercise above applies to separate USB-C cables, not to unplugging that lead from its power brick.

Our Pi 5 kit guide covers the supply and matching build parts. For a different computer, use its own input specification. An illustrative 20V/3A requirement is 60W; a 5A cable at 20V has a 100W current-capacity ceiling. Neither calculation changes what the charger advertises or what the computer requests.

Accuracy, logs and the digits on the screen

Buy the functions you will use before counting decimal places. AVHzY publishes a 0.1% maximum gain error for voltage and current. FNIRSI’s manual expresses voltage accuracy as ±(0.2‰ of reading + 2 counts) and current accuracy as ±(0.5‰ of reading + 2 counts). Keep those complete maker expressions when comparing specifications; display resolution and ADC bit count are different specifications.

The CT-3 is the attractive pick for a saved sequence: offline recording and Lua let you build repeatable checks. KM003C’s manual covers stored curves, export and PC protocol analysis. Use the ChargerLAB support page for current downloads rather than assuming the same desktop tools run on every OS.

Record the supply, cable, meter mode and workload beside each trace. Change one thing, repeat the task, then compare. Keep the AC meter for monthly electricity-cost planning, because the USB-side reading excludes losses upstream in the charger.

Keep the tester from becoming the problem

An inline meter becomes part of the connection. If a storage device works directly but disconnects through the tester, repeat the direct connection before replacing the enclosure. AVHzY’s operating manual explains that extra circuit-board routing can attenuate SuperSpeed signals. Use the meter to investigate power, then remove it for your final USB4 transfer test.

For a useful before-and-after check, save the starting setup first: charger port, cable, device, workload and meter mode. Repeat the same task with one changed component. Compare the negotiated voltage and the shape of the current trace, not just its highest number. A computer sitting idle and the same computer working hard are different tests.

Finish with the device connected normally. For the Pi, shut it down before inserting or removing the meter from its power path. That keeps the troubleshooting session from turning into an unexpected power cut halfway through a write.

Which one belongs in your toolbox?

Choose KM003C for USB-C analysis and the wider voltage range, CT-3 for logs and scripts, or FNB58 for mixed connectors and app support. Start with one real question—a missing power profile, an unidentified cable or a flaky charging path—and work through it. That’s how a small screen becomes a useful troubleshooting tool instead of another glowing thing on the desk.

Choosing a supply next? Our USB-C PD charger guide compares the power left on each port when your mini PC shares a charger with other devices.