Klipper Configuration Diagnostics

Feature Overview

Local parsing: Upload printer.cfg (supports .cfg / .conf / .txt, multiple files, directory upload and drag-and-drop, automatically expanded by [include]) or klippy.log, parsed instantly in the browser
Remote reading: Enter the host IP, and via Moonraker preferentially read the final configuration actually loaded in klippy.log; if the log has no configuration blocks, then download printer.cfg and expand it in include order
Anomaly checks: Check for missing items, duplicate items, value ranges, TMC communication configuration, thermistor configuration, axis parameters, default UI macro overrides, and FLY mainboard pin assignments
Log diagnostics: Automatically extract errors from klippy.log, and for known issues jump to the corresponding troubleshooting documentation; when there are many log issues, the first 8 are displayed by default, with the option to expand all
Version comparison: Compare the consistency of each MCU firmware version and the Klipper software version
Cross-checks: Perform cross-validation across configuration sources and configuration sections
Result search: Search parsing results by keyword and filter by Error / Warning / Info / log-related
Extended compatibility: Can recognize common configuration sections such as fans, ADXL/LIS2DW/LIS3DH/MPU9250, EDDY, etc.; unrecognized extension sections are preserved and displayed but do not participate in heuristic configuration checks
Large log optimization: When the log is large, automatically retain the tail content and MCU version lines for browser analysis
Full log mode: When historical errors need to be traced, you can manually check full log analysis and then upload the complete klippy.log
Report export: Supports one-click copying of the parsing summary or exporting a Markdown diagnostic report

The feature is continuously being improved

The current 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, and configuration content will not be uploaded
Remote reading is a read-only operation and will not modify the host configuration
Large klippy.log files will automatically have their tail captured in the browser for display and diagnostics. For the complete history, please view the original log on the host
After checking full log analysis, large logs will be parsed directly in the browser, and uploading and parsing may take a long time
Third-party plugin sections such as [scanner], [idm], [beacon], [BDsensor], [led_effect ...], [AFC...], [power_loss_resume], etc. may contain special syntax. The tool skips configuration checks for such unknown sections by default, and actual validity is subject to the Klipper startup log
Mainboard and toolboard models are determined only by the actual pin assignments and 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, and actual wiring and manufacturer manuals shall prevail