Klipper Configuration Diagnosis

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 for instant browser-based parsing
Remote Reading: Enter the host IP, prioritize reading the final configuration actually loaded in klippy.log via Moonraker; if no configuration block exists in the log, download printer.cfg and expand it in include order
Anomaly Checking: Check for missing items, duplicates, value ranges, TMC communication configuration, thermistor configuration, axis parameters, default UI macro overrides, and FLY motherboard pin assignments
Log Diagnosis: Automatically extract errors from klippy.log, jump to corresponding troubleshooting documents for known issues; when there are many log issues, the first 8 items are displayed by default, with an option to expand all
Version Comparison: Compare firmware versions of each MCU and Klipper software version consistency
Cross-Checking: Perform cross-validation across configuration sources and configuration sections
Result Search: Search parsing results by keyword, and filter by Error / Warning / Info / Log-related
Extension Compatibility: Recognize common fan, ADXL/LIS2DW/LIS3DH/MPU9250, EDDY, and other configuration sections; unrecognized extension sections will be retained and displayed but will not participate in heuristic configuration checks
Large Log Optimization: Automatically retain tail content and MCU version lines for browser analysis when logs are large
Full Log Mode: When historical errors need to be traced, manually check the full log analysis option and upload the complete klippy.log
Report Export: Support one-click copy of parsing summary or export Markdown diagnostic report

Features Are Continuously Being Improved

Current features are still being updated. Feel free to provide feedback if you have suggestions or encounter issues.

Important Notes

Access via PC for a better experience
All parsing is done locally in the browser; 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 be automatically truncated at the tail for display and diagnosis in the browser; for a complete history, view the original log on the host
After checking full log analysis, large logs will be directly parsed in the browser, and upload and parsing may take longer
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 based on Klipper startup logs
The motherboard and toolboard model are determined jointly by actual pin assignments and the MCU chip model in klippy.log. Uploading only printer.cfg may not display the specific model
Pin analysis results are for reference only, and actual wiring and manufacturer manuals should be consulted