Todd Wolven
Theme

WireView Monitor

By Todd Wolven · Updated 2026-11-01 · Source on GitHub

A compact native Windows monitor for the Thermal Grizzly WireView Pro II. Window size, including decorations, is targeted at 1280 × 720 pixels: one quarter of a 2560 × 1440 display. Drag it into the desired quarter or use Windows Snap. It also resizes down to 850 × 480 client pixels. The Windows title bar and border use the dashboard's dark background with light caption text, preserving standard dragging, resizing, minimize, and close controls.

Windows only (it uses the Win32 title-bar and DPI APIs). Create the isolated Python environment once with uv, then start it with Launch.ps1. The only dependency is pyserial 3.5.

git clone https://github.com/twolven/wireview-monitor
cd wireview-monitor
uv venv --python 3.12 .venv
uv pip install --python .venv/Scripts/python.exe -r requirements.txt
./Launch.ps1

Readings

Click KEEP ON TOP or press T to toggle the floating window.

Click LIMITS & PROTECTIONS or press S to see the actual device alarm thresholds and per-fault display, buzzer, soft-shutdown, and hard-shutdown settings. The complete active configuration is read every 30 seconds; it is never changed. The physical motherboard shutdown connection cannot be verified over USB.

Pin bars color by load: green below 90% of the display reference, amber from 90%, and red at/above that reference. The reference is the lower of 9.2 A and the configured device per-pin alarm. A red marker shows it on each bar. The 9.2 A value comes from Molex's Micro-Fit+ PCIe 12V-2x6 data sheet; it is a display reference, not confirmation of this PC's particular contact/cable rating. Other connector products have different ratings (for example, Amphenol lists 9.5 A). Load colors are immediate guidance; actual device fault bits remain authoritative for its own configured alarm timing and actions. Green is not a guarantee of connection safety.

The total power card colors against the lower of cable rating and device power alarm, total current against the device total-current alarm, and every temperature against the device temperature alarm. Unknown/stale readings are grey.

The power is measured on the GPU power cable; it excludes PCIe slot power. The displayed connector temperatures are not GPU die temperatures. Per-pin spread is an absolute current difference, not a replacement for the device's fault logic.

USB access and privacy

This app talks directly to the WireView USB serial port (automatically discovered by VID 0483/PID 5740) at 115200 baud. Only commands 01 (identity), 02 (UID), 04 (live sensors), and 05 (read active configuration) are permitted by its transport. It does not change firmware, configuration, thresholds, GPU settings, or device fault registers.

Close the stock WireView app and any other program using this port before launching. Only one program can own the serial port. Two copies of this monitor are prevented by a named mutex.

Startup

Install-Startup.ps1 registers the monitor under the HKCU Run key WireViewMonitor (-Remove undoes it). It does not touch any other program's startup entries. If you also run the stock WireView app, disable its autostart yourself: only one program can own the serial port. (Install-Startup.ps1 was written for this public release and has been syntax-checked, not run through a sign-in.)

Keep the stock app for firmware and configuration work. Close this monitor first, then open the stock app. Onboard alarms and protection actions operate independently of either desktop application.

The application has no network code, cloud integration, desktop capture, or app inspection. The live source is the WireView device, plus the optional PC-power file described above. Logs stay here in monitor.log (rotated at 1 MB) and status.json (latest sample only). These files include the device identity and readings; status updates every 500 ms.

Protocol reference (community documentation; this project is not affiliated with Thermal Grizzly): https://github.com/Gustav0ar/wireview-pro-ii/blob/main/docs/protocol.md

Contact rating references: https://www.molex.com/content/dam/molex/molex-dot-com/en_us/pdf/datasheets/987651-9552.pdf https://cdn.amphenol-cs.com/media/wysiwyg/files/documentation/gs-12-1706.pdf

Files

To run checks:

& ./.venv/Scripts/python.exe -m unittest -v test_protocol

License

MIT. See LICENSE.

This page is generated automatically from the GitHub README, which is the single source of truth.  ← Back to toddwolven.com