Shutdown: Timer Too Close, high bandwidth utilization

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: Btt octopus pro
Host / SBC Raspi 3b
klippy.log

Hey all, I’ve been attempting to track down a regular shutdown that seems to happen randomly, but almost every print. If I restart enough I can usually get a print off. I have a nighthawk-Sb toolhead so Im guessing it may be related the usb usage. The logs indicate that I have incredibly high bandwidth utilization throughout the print but especially after the initialization and QGL getting into the print.

So far I have attempted:
-unplugging the usb webcam
-replacing the usb cable from raspi to octopus
-various raspi config changes I’ve found on this forum.

Additional config items:
-64 microsteps on all axis

I’m at a bit of a loss, my latest theory is that is may be a bad cable to my tool head board? I believe it’s the octopus mcu that is the issue, but I’m not certain if the log would differentiate between the two as I’ve only seen the same error pop up.

Any guidance or help would be deeply appreciated! Thank you :slight_smile:

Describe your issue:


klippy.log (6.9 MB)

Try reverting all 3rd party modification to the Klipper code.

Gotcha. I’m going to struggle for a little while longer before I nuke everything. I ran the shutdown log and generated this, but I don’t quite know how to dig into it yet…
klippy.log.shutdown06306.txt (95.0 KB)

It appears that newer versions of Klipper are struggling with complex LED effects during QGL. Disabling the effects solved my issue.

The LED effects modification is known to cause these sorts of instabilities.

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