Back to projects

Portable Power Monitor

USB-C instrumentation for bring-up benches and field kits.

USB-C PDINA228RP2040KiCad 8

Project status

Rev B bring-up

Document every power anomaly where the hardware team can actually find it.

bring-upfirmware loggingfixture design

Project overview

The Portable Power Monitor exists because too many power investigations vanish into chat logs and scattered screenshots. This project page is meant to gather the board story, the debug process, and the generated hardware artifacts in one place.

Every revision should leave a paper trail: what changed, why it changed, and which files a future engineer should trust during manufacturing, assembly, and test.

Why this structure works

  • Captures voltage, current, and accumulated energy during field tests.
  • Pairs firmware drops with schematics and board outlines in predictable folders.
  • Makes tutorial and blog content discoverable from the project itself.

Generated file buckets

Another repository can publish generated board files into these paths without requiring route changes in the frontend. When files are present, they appear here automatically at build time.

Board dimensions

Mechanical exports, keep-outs, and enclosure references.

pipeline

/generated/portable-power-monitor/board-dimensions/

No files are published in this bucket yet. The sync workflow will create links here when the source repository pushes fresh artifacts.

Code

Firmware releases, examples, and support scripts.

pipeline

/generated/portable-power-monitor/code/

No files are published in this bucket yet. The sync workflow will create links here when the source repository pushes fresh artifacts.

Data sheets

Vendor documents mirrored with the dash-separated naming used upstream.

pipeline

/generated/portable-power-monitor/data-sheets/

No files are published in this bucket yet. The sync workflow will create links here when the source repository pushes fresh artifacts.

Datasheets

Compatibility bucket for generated exports that omit the dash.

pipeline

/generated/portable-power-monitor/datasheets/

No files are published in this bucket yet. The sync workflow will create links here when the source repository pushes fresh artifacts.

Schematics

Rendered PDFs, source snapshots, and revision notes.

pipeline

/generated/portable-power-monitor/schematics/

No files are published in this bucket yet. The sync workflow will create links here when the source repository pushes fresh artifacts.

Connected content

Documentation linked to Portable Power Monitor

Project pages are most useful when the related tutorials, reference pages, blog notes, and news updates stay attached to the same slug.

NewsApr 9, 20263 min read

Documentation site rebuild starts with a static-first release

The new site structure is live as a static export so content can ship immediately on GitHub while the long-term Django plan takes shape.

sitereleasestatic export
Visitors
TutorialsApr 8, 20269 min read

A repeatable bring-up checklist for fresh PCBs

Turn first power-on into a documented process instead of a one-off scramble with loose bench notes.

bring-uppcbtest workflow
Hardware engineers
NewsApr 7, 20264 min read

Generated artifact folders are reserved for automation

Project pages now expose stable target paths for schematics, firmware bundles, and mechanical exports published by other repositories.

automationgithub actionsartifacts
Maintainers
TutorialsApr 6, 20267 min read

Publishing generated hardware files into the docs site

Set up a simple convention so another repository can push schematics, code, and dimension exports without changing the frontend.

github actionsartifactsdocs pipeline
Maintainers
ProductsApr 4, 20265 min read

Portable Power Monitor kit overview

Reference page for what the board does, where it fits into the workflow, and which generated artifacts should accompany each release.

productreferencesupport
Customers and builders
BlogApr 3, 20265 min read

What Rev B actually fixed on the Portable Power Monitor

A revision summary should say more than improved stability. It should explain which assumptions failed and what was changed to remove the risk.

revisionpowerretrospective
Engineers and maintainers