Move queue overflow occurred in Resonance Test

Basic Information:

Printer Model: DIY CoreXY
MCU / Printerboard: DUE / RAMPS-FDv2
klippy.log
klippy.log (226.7 KB)

Describe your issue:

Hello.

Since the MKS-THR42 has an ADXL345 attached, when I ran a resonance test, a move queue overflow occurred at around 58Hz.
What could be the cause?

There is no problem with printing.
Host is RASPI 4B, MKS-THR42 can connect via MKS-UTC.

To quote Kevin:

A “move queue overflow” indicates the Klipper host queued a move on the micro-controller when there was no space available for it. The Klipper host code is designed to only send out new movements after the mcu has processed existing movements, such that this error should never occur.

However there have been some recent fixes in the shaper code that caused crashes so you might check for Klipper updates.
You are currently on v0.12.0-104-g1b24f6a2

Thank you.

I tried updating klipper to the latest version, but there was no change in the problem.

v0.12.0-104-g1b24f6a2 → v0.12.0-114-ga77d0790

klippy.log (194.4 KB)

You’ve set the baud for your main mcu to 115200. That is not recommended. It appears you ran out of bandwidth during the test which caused the unusual error report.

I recommend setting the main mcu to the recommended baud of 250000. I also recommend using a 1Mbit canbus frequency for your MKS_THR mcu.

-Kevin

EDIT: Also consider consider compiling the main MCU with USB support and using the dedicated USB port on the Arduino Due. Using the dedicated USB port provides dramatically higher bandwidth.

Thank you.
The speed is intentionally slow because I have a HAM radio and solar power facility near the printer.
Once I have a solution, I will try again.

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