Klipper Log Diagnostics

Feature Overview

Local Parsing: Upload printer.cfg (supports .cfg / .conf / .txt, multi-file, directory upload and drag-and-drop, automatically expands [include] directives) or klippy.log, parsed instantly in the browser
Remote Reading: Enter the host IP to preferentially read the final configuration actually loaded in klippy.log via Moonraker; if the log has no configuration block, then download printer.cfg and expand it in include order
Anomaly Checks: Checks for missing items, duplicates, value ranges, TMC communication configuration, thermistor configuration, axis parameters, default UI macro overrides, and FLY mainboard pin assignments
Log Diagnostics: Automatically extracts errors from klippy.log; known issues link to the corresponding troubleshooting documentation; when there are many log issues, the first 8 are shown by default with an option to expand all
Version Comparison: Compares MCU firmware versions and Klipper software version consistency
Cross-Checks: Performs cross-validation across configuration sources and configuration sections
Result Search: Search parsed results by keyword and filter by Error / Warning / Info / log-related
Extended Compatibility: Recognizes common fan, ADXL/LIS2DW/LIS3DH/MPU9250, EDDY and other configuration sections; unrecognized extension sections are retained and displayed but do not participate in heuristic configuration checks
Full Log Analysis: Parses the full klippy.log by default, allowing complete tracing of historical errors
Report Export: Supports one-click copying of the parsing summary or exporting a Markdown diagnostic report

Feature Under Continuous Improvement

This feature is still being continuously updated. Feedback and suggestions are welcome.

Notes

PC access is recommended for a better experience
All parsing is done locally in the browser; configuration content is never uploaded
Remote reading is a read-only operation and will not modify the host configuration
By default, the full klippy.log is loaded directly into the browser for parsing; downloading/uploading and parsing large logs may take a long time. Please be patient if the browser is unresponsive for a short period
Third-party plugin sections such as [scanner], [idm], [beacon], [BDsensor], [led_effect ...], [AFC...], [power_loss_resume] may contain special syntax. The tool skips configuration checks for such unknown sections by default; actual validity is subject to the Klipper startup log
Mainboard and toolboard models are determined only by actual pin assignments combined with the MCU chip model in klippy.log; when only printer.cfg is uploaded, the specific model may not be displayed
Pin analysis results are for reference only; refer to actual wiring and the manufacturer's manual