Diagnostics & command line
Export a sample or sensor listing without opening the everyday monitoring interface.
Choose a diagnostic output
Use --diag for a named sensor listing, --dump for a current sample as JSON, or --render for an English screenshot. Diagnostic outputs are local files; choose the listing when comparing sensor coverage.
Command-line tools
Open PowerShell in the application folder. Use a writable output location. Protected sensor access still depends on privileges and driver support.
.\MomoMonitor.exe --dump --out snapshot.json
.\MomoMonitor.exe --diag diag.txt
.\MomoMonitor.exe --render dashboard.png --english --theme paper| Command | Result |
|---|---|
| --dump --out snapshot.json | One current sample as JSON. |
| --diag diag.txt | A list of visible sensors; inspect Motherboard entries when investigating board fans. |
| --render dashboard.png --english --theme paper | A read-only PNG preview with English labels and Paper Pop. |
| --render settings.png --english --settings | A read-only preview of Settings. |
| --render process.png --english --process | A read-only preview of the Process page. |
| --render mini.png --english --mini | A read-only preview of the Mini panel. |
Render previews use temporary settings, disable hardware fan writes and do not save the session into your normal histories. Alert render examples use supplied preview events. A PNG export captures a state; it does not record a video.
Build from source
Developers need the .NET 8 SDK. From the project root, run:
powershell -ExecutionPolicy Bypass -File .uild.ps1
# Explicitly create a portable distribution:
powershell -ExecutionPolicy Bypass -File .uild.ps1 -PortableThe normal build updates the root executable. Only -Portable creates a distribution folder and ZIP. Existing user settings and histories are not packaged. A framework-dependent build is an optional developer choice. See the repository README for build details.