New Timer Too Close... Need Help

General Discussion
1

Basic Information:

Printer Model: V1 MP3DP V5
MCU / Printerboard: Manta M8P / EBB36
Host / SBC : CB1
klippy.log
klippy (23).zip (3.7 MB)

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:

…

In the past week I have been having MCU 'EBBCan' shutdown: Timer too close. This printer has been operating without change for several months without ever having this issue pop up. The only thing that has changed in the last week is a klipper update. None of my macros have changed. I have checked everything in this post to the best of my ability but I am not finding anything wrong. I have updated all of the boards to the latest klipper just to make sure everything was on the same page. Any help of what I need to check would be great! Tired of wasting filament on failed prints lol. Thanks!!!

2

I am still having issues with this. I have disabled gcode_arcs in both klipper and orca. I have tripple checked the settings on everything. I am not running a camera on this printer but I do have klipper screen.

After doing away with gcode_arcs it seemed to go away. Then I did the update last night to 258 and now every other print I get a timer too close error on EBBcan.

Any help at all with this would be greatly appreciated!

Here is the latest klippy log right after a shutdown.

klippy (25).zip (2.1 MB)

3

Remove the unofficial modification and see if the crash repeats. If you had really followed the advice in the above link, you should already have tried without any 3rd party modifications.

4

Just because I don’t understand something doesn’t mean I am not trying my best to follow it. Can you tell me what you are calling a 3rd party modification?

5

I think, @Sineos is talking about this in your klippy.log

Git version: ‘v0.12.0-258-g9318901f-dirty’

You’ll find the answer here How-To Trouble-Shoot, what “dirty” means. See
5. Consult the klippy.log file

Good luck, hcet14

1 Like
6

Ok I think I fixed it. Its no longer showing “dirty” in mainsail. I will continue to print and see if I have any errors. If so I will post a new log here.

I apologize for not knowing about that prior. Those things have been on there for months without a single issue. Thank you for the help!

Here is a new log as it sits now for reference
klippy (26).log (293.5 KB)
.

1 Like
7

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