# Random/new Stepcompress errors **URL:** \ **Category:** General Discussion\ **Created:** [July 28, 2023, 6:55pm UTC](https://klipper.discourse.group/t/random-new-stepcompress-errors/9707 "2023-07-28T18:55:08Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![lukeslaboratory](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/lukeslaboratory/32/6495_2.png) [@lukeslaboratory](https://klipper.discourse.group/u/lukeslaboratory)\ **Post date:** [July 28, 2023, 6:55pm UTC](https://klipper.discourse.group/t/random-new-stepcompress-errors/9707/1 "2023-07-28T18:55:08Z")
### Basic Information: Printer Model: Stablebot MCU / Printerboard: Octopus Pro, Huvud [Error.txt](https://klipper.discourse.group/uploads/short-url/ps8zAgTXNQYGxawUkvynrQGIVCx.txt) (9.7 KB) [klippy (14).zip](https://klipper.discourse.group/uploads/short-url/dZ9FvmbJW3rRcpkIvgn8FnFo9ZO.zip) (4.5 MB) ### Describe your issue: Printing a long file, ~2 days or so. The last two times i’ve tried to print it, its failed at around this point give/take a few hours, and gave these errors. What could be going on? everyhing else seems to be pretty happy. I tried googling the error, and the only thing i could find is related to my use of a series extruder and pressure advance, which are both things I am using here. Thanks. ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [July 28, 2023, 8:17pm UTC](https://klipper.discourse.group/t/random-new-stepcompress-errors/9707/2 "2023-07-28T20:17:01Z")
Hello @lukeslaboratory ! > [@lukeslaboratory](#): > > I’m not allowed to upload my klippy.log (too big) so here’s a linky You have the possibility to upload a zipped (Compressed) klippy.log. * * * What is this fast move stuff good for? I mean the feed rates are ridiculous. (`G1 X325 Y325 F999999999`) Does the error appear during such a move? ---
**Author:** ![lukeslaboratory](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/lukeslaboratory/32/6495_2.png) [@lukeslaboratory](https://klipper.discourse.group/u/lukeslaboratory)\ **Post date:** [July 28, 2023, 10:13pm UTC](https://klipper.discourse.group/t/random-new-stepcompress-errors/9707/3 "2023-07-28T22:13:11Z")
I’ve added the .zip Those moves are never called during a print. They exist only for comissioning, and always obey the maximum printer speed. I’ve printed the same file 3 times and had same error, different spot. Its not even the pause sequence unless its bugged -it recovered a few times from a snag/clog in this print alone! Luke ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [July 29, 2023, 6:16am UTC](https://klipper.discourse.group/t/random-new-stepcompress-errors/9707/4 "2023-07-29T06:16:53Z")
Your error actually is: ```auto Filament Sensor filament_sensor: runout event detected, Time 66265.46 Exiting SD card print (position 15673233) Timeout with MCU 'mcu' (eventtime=66266.044442) Transition to shutdown state: Lost communication with MCU 'mcu' ``` The other errors are just consequential. Looks a bit like an issue with your filament sensor. I recommend testing it separately and also to verify the config. Is the pull-down on the pin correct? Side note: I have removed these filament motion sensors from my system, as I found them very unreliable and prone to do stupid things. ---
**Author:** ![lukeslaboratory](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/lukeslaboratory/32/6495_2.png) [@lukeslaboratory](https://klipper.discourse.group/u/lukeslaboratory)\ **Post date:** [July 29, 2023, 6:19am UTC](https://klipper.discourse.group/t/random-new-stepcompress-errors/9707/5 "2023-07-29T06:19:18Z")
What kind of issue are you proposing with it? It successfully detects errors, pauses the print, and allows recovery, and resumption. If you look at the logs, that happened a few times during the print, and has been working successfully throughout the week. Regardless of your opinion on them, there’s something that is breaking within klipper and/or causing issues with the board. Is your proposal that its delivering voltages that are temporarily killing the board? ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [July 29, 2023, 6:23am UTC](https://klipper.discourse.group/t/random-new-stepcompress-errors/9707/6 "2023-07-29T06:23:31Z")
No idea. Could be anything from faulty hardware over broken cables to you-name-it. From the log I can only tell you that there was a run-out event and at the same time the MCU stopped responding. So apparently the filament sensor did something that killed the MCU. ---
**Author:** ![lukeslaboratory](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/lukeslaboratory/32/6495_2.png) [@lukeslaboratory](https://klipper.discourse.group/u/lukeslaboratory)\ **Post date:** [July 29, 2023, 6:27am UTC](https://klipper.discourse.group/t/random-new-stepcompress-errors/9707/7 "2023-07-29T06:27:41Z")
So its definitely not related at all to similar historical issues with synced extruders and long prints. Which definitely don’t have similar errors for their similar issue in the step compressor. Definitely faulty hardware that counts pulses. Considering there is no ryhme or reason, but only happens when i’m well over a kilo of filament into the print, I strongly believe its a resurgence of old errors, which even follow similar forms > > > Near the end of a 2.5 days, 1.3kg print, Klipper suddenly stopped. The control d…isplay seems hung, showing the printing temperatures but the printer is shutdown and cooled down. OctoPrint is disconnected from Klipper showing an error: "Too many consecutive timeouts". > The log file seems to indicate an internal error in Klipper caused this. > \[klippy.log\](https://github.com/KevinOConnor/klipper/files/4543561/klippy.log) > > This error seems exactly the same as issue #2771. But I run a rather recent version of Klipper, I had updated to the latest version about one week back before starting this large print job, which I now regret as I never had problems before. This print was part 3 of a large part, I did not restart Klipper or OctoPrint in between jobs. Klipper did finish the first two parts (one is a mirror from the one that now failed) without issue, so it had been running and printing nonstop for about a week. ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [July 29, 2023, 6:34am UTC](https://klipper.discourse.group/t/random-new-stepcompress-errors/9707/8 "2023-07-29T06:34:51Z")
Honestly, what kind of answer do you expect now? - That I solemnly swear that it is definitively not something else? - A undersigned charta that it is your filament sensor? Check your log yourself: Run-out event → Crash. Nothing in between. ---
**Author:** ![lukeslaboratory](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/lukeslaboratory/32/6495_2.png) [@lukeslaboratory](https://klipper.discourse.group/u/lukeslaboratory)\ **Post date:** [July 29, 2023, 7:02am UTC](https://klipper.discourse.group/t/random-new-stepcompress-errors/9707/9 "2023-07-29T07:02:05Z")
Lets go this way: Why does “internal error on command: G1” indicate hardware issues? When I see that it successfully detected and initiated a pause for runout (as it has successfully done) but then immediately dies, with very unique errors “Internal Error on command: G1” I’m a little baffled that an error only happens when its significantly underway with a print (a few kg+) The hardware is new. Wire is good. It has detected over 100 clogs in the last week alone (voids in filament, I forgot how spoiled I am with my normal suppliers), but the only time it errors is only when there is significant filament through the system and then detects a clog. I understand that you’re trying to help, I really do. I have checked the log myself. I can read. I see that it ran out. It happened before too. That time it didn’t even give me the error list of G1. But why I’m here is that I don’t believe its _hardware_ - there is no hardware reason that only after a significant portion of time and filament that a filament runout event causes the entire machine to shut down. It doesn’t make sense. Considering the history of sync’d extruders and large prints, i’m mostly looking for someone who knows code (my blind spot) to tell me there’s no way that there’s similar issues as what has been done in the past, as the smart filament sensor since its tracking pulses/passage of filament might have something to do with the error. > > > Near the end of a 2.5 days, 1.3kg print, Klipper suddenly stopped. The control d…isplay seems hung, showing the printing temperatures but the printer is shutdown and cooled down. OctoPrint is disconnected from Klipper showing an error: "Too many consecutive timeouts". > The log file seems to indicate an internal error in Klipper caused this. > \[klippy.log\](https://github.com/KevinOConnor/klipper/files/4543561/klippy.log) > > This error seems exactly the same as issue #2771. But I run a rather recent version of Klipper, I had updated to the latest version about one week back before starting this large print job, which I now regret as I never had problems before. This print was part 3 of a large part, I did not restart Klipper or OctoPrint in between jobs. Klipper did finish the first two parts (one is a mirror from the one that now failed) without issue, so it had been running and printing nonstop for about a week. > > > \