Print job completed but interrupted

General Discussion
1

Basic Information:

Printer Model: Voron Trident
MCU / Printerboard: Manta
Host / SBC
klippy.log - attached

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:

For some reason a print job is failing or being ‘interrupted’ at the exact same spot. First time or two I thought some weird network thing, but after 4 times and print head stopping at the exact same spot on the print makes me wonder what’s going on.

I looked through the log file but can’t find anything that even tells me the job was interrupted.
Can someone tell me how to identify the star/stop for a print job in klippy.log ? I can’t even find the input gcode file name in here..

Screenshot shows the 4 times I tried to print it. First one showing interrupted (no idea why), but the other 3 all show completed successfully but also stopped at the same spot as the interrupted file.

Any help appreciated!

Edit: Adding the log file from Nov 2, the actual day the ‘interrupted’ print shows up in my print history.
Also adding the G-code file
Snail1_0.2mm_PLA_0.2mm Optimal @Voron-sv__4h12m_20241102-220616.gcode (4 MB)

klippy.log.2024-11-02.zip (3.4 MB)

klipper_log_print_ended_but interrupted_2024-11-06_15-06-53
klipper_log_print_ended_but interrupted_2024-11-06_15-06-531566×312 31.9 KB

logs-20241106-144025.zip (1.5 MB)
.

2

Have you re-sliced the file?
Can you attach the gcode file?

BTW: Over 4000 lines of config. Quite huge. Are you sure you need all the macros?

3

Unless I missed something, the provided log contains only one print-job that was completed successfully. No evident errors in the log.

4

Thanks. Refactoring the config on this printer is on my backlog - acquired from someone, it was working for the most part but am planning on “rebuilding” the klipper environment.

I was trying to figure out what happened before re-slicing. I have resliced and it printed fine. (same file, just modified the temp 1 degree), didn’t change anything else.

So I guess this is just an ephemeral thing?

5

Added the G-code file for interest.

6

Thanks for the reply. Uploaded the klippy file from the day of the original ‘interrupted’ print. I looked through it and didn’t find anything that looks like an interrupted print job. What should I be looking for?

Is there a high-level guide somewhere on how to read the klipper log to identify key events (print start/end, file printed, common error messages, etc). I know it’s not feasible to maintain detailed docs on the whole structure, but an outline might be helpful.

Thanks for all your help!

7

Where did you put it?

Rule of thumb: New information always to new posts.

1 Like
8

Sorry, edited and attached to the main post.

9

Please put then to the according posts.

10

did you cut the gcode file, or is it just broken?

it ends in the middle of the print.

11

Really? Interesting. No, I didn’t cut it off. It uploaded to the printer and started printing automatically as expected. Never occurred to me to check that.

Mystery solved :slight_smile: Sorry for wasting all your time.

Have a great day

12

i downloaded it two times and it is only 2,2mm height and has no top layers.

13

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