Klipper Log Diagnostics
Feature Overview
- Local Parsing: Upload
printer.cfg(supports.cfg/.conf/.txt, multiple files, directory upload and drag-and-drop, automatically expands by[include]) orklippy.log, parsed instantly in the browser - Remote Reading: Enter the host IP, read the final configuration actually loaded in
klippy.logvia Moonraker with priority; when the log has no config block, downloadprinter.cfgand expand it in include order - Exception Checking: Check for missing items, duplicate items, value ranges, TMC communication configuration, thermistor configuration, axis parameters, arc fitting (
[gcode_arcs]), default UI macro overrides, and FLY mainboard pin assignments - Log Diagnostics: Automatically extract errors from
klippy.log, and jump to the corresponding troubleshooting documentation for known issues; when there are many log issues, the first 8 are shown by default and all can be expanded - Version Comparison: Compare the consistency of each MCU firmware version and the Klipper software version
- 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
- Extended Compatibility: Can recognize common configuration sections such as fans, ADXL/LIS2DW/LIS3DH/MPU9250, EDDY, etc.; unrecognized extension sections will be retained and displayed, but will not participate in heuristic configuration checks
- Full Log Analysis: Parses the full
klippy.logby default, so historical errors can be fully traced - Report Export: Supports one-click copying of the parsing summary or exporting a Markdown diagnostic report
The feature is being continuously 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 completed 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
- By default, the full
klippy.logis loaded directly into the browser for parsing. Downloading/uploading and parsing large logs may take a long time. If the browser does not respond for a short time, please wait patiently - 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. 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 onlyprinter.cfgis uploaded, the specific model may not be displayed - Pin analysis results are for reference only. Refer to the actual wiring and the manufacturer's manual
Loading...
Loading...