"Extrude only move too long" during manual Resonance Compensation

General Discussion
1

Basic Information:

Printer Model: Formbot T-Rex 3
MCU / Printerboard: Vivedino V2 - ATMega 2560
Host / SBC: Raspberry Pi 4
klippy.log: Resonance Compensation_logs.zip (2.0 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:

Today me :slight_smile:

I tried a manual Resonance Compensation as describes here. Resonance Compensation - Klipper documentation
After setting up the printer accordingly to the Ringing frequency - section,
shortly after start I was greeted with this error message:

Extrude only move too long (-5331.738mm vs 101.000mm)

As for the serial.log, the previous commands were these (complete in the serial.log):

2025-08-18 19:28:23,611 - Send: N56 M300 S440 P500*21
2025-08-18 19:28:23,619 - Recv: ok
2025-08-18 19:28:23,624 - Send: N57 G1 X-43 F4000*42
2025-08-18 19:28:23,636 - Recv: ok
2025-08-18 19:28:23,641 - Send: N58 G1 E5 F250*20
2025-08-18 19:28:23,652 - Recv: // Extrude only move too long (-5326.625mm vs 101.000mm)
2025-08-18 19:28:23,654 - Recv: // See the 'max_extrude_only_distance' config option for details
2025-08-18 19:28:23,655 - Recv: !! Extrude only move too long (-5326.625mm vs 101.000mm)
2025-08-18 19:28:23,729 - Changing monitoring state from "Printing" to "Cancelling"
2025-08-18 19:28:23,821 - Recv: ok

I tried with relative and absolute extrusion.

Curiously, after resetting Klipper, the gcode file runs fine.

2

Just a guess, it seems that you use G90, so if the E axis was not at zero, the G1 E5 F250 would cause an excessive move

Like:

  • (G91) E0 → E5 (+5)
  • G90 E100 → E5 (-95)

Also, it seems that under normal printing, you do use the G92 to reset the position eventually, but there is no such command right before the test.

1 Like
3

I thought that too.
Actually G90 is set quite at the start of the gcode file.
I may set a G92 E0 just before the G1 E5 F250 and give it a try.

But that does not explain why it runs fine under normal conditions.
Ad the deviation is quite excessive: Over 5 metres retraction?

4

Obviously the G92 E0 did the trick.

Thanks for leading the way.

1 Like
5

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