Help to understand Klippy.log

General Discussion
1

Basic Information:

Printer Model: Ratrig Vcore31
MCU / Printerboard: Octopus Pro+EBB42
Host / SBC rPi 4
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Not an issue…

From time to time the printing in progress stops, due to some other error…

I get a message in the console, explaining the error, but most of the time I don’t know how to identify it…

I know that klippy.log can help me, but the truth is that I don’t understand its structure very well.

I would like to obtain more information on how to understand the log and console errors, to be able to identify the problems that arise in a semi-autonomous way…

It is clear that there will be many of them that I do not know, and I will need your help… But, I hope, there are others that I can.

Where can I find information about the Klipper LOG? (What is its structure, events that are recorded, in what order they are recorded, errors that are recorded, possible meaning of the error codes, how much time or impressions it stores, if it has any size limit,…)

For example… this last log, I have not been able to attach it because it occupies 12 MB, and the forum has a limit of 8…

Can you limit the file size?
Do I have to delete it manually from time to time?
Maybe there is a plugin for its management…
…

2

For the easy question, You can Zip your log file to post it.
That usually dramatically reduces the size.

For your question of helping to understand it, To be honest Klippy logs are kind of cryptic. There is a python script included with Klipper that extracts info from the log but it’s honestly not much better.

Something I’ve been considering for the last month or two but would be kind of a massive undertaking… is working on a website where people could upload their log and it give a “human readable” output in simple terms of what their log says.

There are sites that do that and give you a graph of your CPU loads and stuff but that often doesn’t tell you what the issue is.

Zip your log file for now and upload it and I’ll see if we can figure out what’s going on.

3

In addition to @TheFuzzyGiggler I like to give a hint to @Sineos’ graphic analyser:

https://sineos.github.io/

4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.