Klipper Advanced Log Inspector

General Discussion
1

Klipper offers the logextract.py tool, which can be used for advanced log analysis:

  • It extracts Klipper shutdown information
  • It orders log lines created by the shutdown chronologically
  • It adds advanced, raw UART messages sent to/from the MCU into readable TMC register accesses

It is mainly thought of as a debug aid, but for the interested and advanced klippy.log reader, it has some merits as well:

  • It splits large logs and extracts only shutdowns
  • It extracts configs

I have created a web application that facilitates using the tool by adding a bit of interface and also a compare function to diff potential changes and evolutions in the config. Surely not an everyday tool, but it might be useful.

Find it here: Klipper Advanced Log Inspector

(Of course, the name is purely a marketing scam)

2 Likes
2

Looks good.

It’s a nice complement to your

Klipper Log Visualizer

Would you ever consider adding checking:

  1. To see if a Klipper version is “dirty”
  2. List the Klipper versions in the host and MCUs
  3. Add using this (and the Klipper Log Visualizer) to the required actions by somebody requesting help in “General Discussion” topics?
3

{608FCC50-E2FF-44A0-8CD2-915419BBA2DD}
{608FCC50-E2FF-44A0-8CD2-915419BBA2DD}3075Ă—373 47.4 KB

Adding the MCU version would be a good idea, yes.

I would rather prefer to get an unmodified full log and decide how to analyze it. As stated above, this tool focuses on true shutdowns..

4

I didn’t try it with a failing log - sorry, I should have.

I agree that the full klippy.log should be posted, just that the user should run their log through the tool before posting to get clues as to the problem on their own.

Putting links to them in the “General Discussion” actions is a good way to keep it in people’s minds that they are there.