Move queue overflow with large gcode files

General Discussion
1

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: BTT Octopus
Host / SBC: Raspberry Pi 3b+
klippy.log
klippy.zip (1.2 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:

Hello, my voron is having issues with large gcode files. I’m trying to print two models with an estimated print time of ~14 hours. After 3-5 hours, the printer randomly stops with the error message

MCU ‘mcu’ shutdown: Move queue overflow

I checked the logs, but I cannot find anything wrong.

2

Hello @Snowboard0187 !

You may check your slicer settings:

Unknown command:"G17"
Unknown command:"G3"

Do you slice with (very) high resolution?

1 Like
3

I tried a different slicer, to make sure the slicer is not causing the issue.

I slice with default resolution. The model is very large, which results in a large .gcode file.

4

This seems to be a CAN bus issue. Around 5 minutes before Klipper crashes the latency of the communication is dramatically increasing for both MCUs and you will find the following error message in the log:

Resetting prediction variance 16173.627: freq=180012203 diff=6218799 stddev=180000.000

This is the latency development:

grafik
grafik3739×565 218 KB

Also following the prediction variance, the synchronization between the MCUs seems to suffer:

grafik
grafik3620×551 77.9 KB

Unfortunately, here my “wisdom” ends. You could check if you see any errors on the CAN bus interface. See CANBUS Troubleshooting - Klipper documentation

1 Like
5

Thanks a lot for guiding me in the right direction. I just completely re-wired my canbus and also changed txqueuelen from 1024 to 128. I’m going to print the same model again, and will report back if that was actually the issue.

6

In case someone is interested: I did not found the issue. I replaced the Canbus cable, installed a new OS on a fresh sd card, changed USB cables, reflashed Katapult + Klipper on both MCUs, but the error is still the same.

I bought a Nitehawk SB and switched to Klipper USB, which is much easier to debug if something goes wrong.

7

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