Closed Yury-MonZon closed 3 years ago
Sorry, but we don't use github to help diagnose problems with individual printers. That said, some other process on your host computer is using too much system resources - you'll need to track that down and fix it.
-Kevin
Unfortunately, it appears the directions at https://www.klipper3d.org/Contact.html were not followed for this issue.
We choose to use github as a place that people working on improving Klipper can share the results of their work. We choose to not use github to help diagnose problems with a user's printer. We choose to not use github to answer user questions. We choose to not use github as a place to make requests.
In the future, please follow the directions at: https://www.klipper3d.org/Contact.html This ticket will be automatically closed.
Best regards, ~ Your friendly GitIssueBot
PS: I'm just an automated script, not a human being.
Oh I see. So it is definitely not Klipper's error? I couldn't get the reason from the log file.
If so - I'll deal with it myself. Just needed to confirm what's the problem.
I'll close the issue after your confirmation.
Thank you very much.
@Yury-MonZon Did you ever sort this issue out?
This gcode file just printed fine, I've run it again and in the middle of the print it stopped. Then I hit restart firmware and only after that I realized that I should save the log. Log included. Please help. Thanks a lot!
klippy.log.zip
I've had another hang ups while using hardware screen, but I don't think it is related.