Move exceeds maximum extrusion prusaslicer klipper

General Discussion
1

Basic Information:

Printer Model:
MCU / Printerboard:
Host / SBC
klippy.log

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, Good morning,

I’m having a problem with the Ender 3 v2 using Prusaslice when printing with the Pulp tower. It works perfectly with Orcaslice. However, I noticed that without the tower, the error “Move exceeds maximum extrusion” doesn’t appear. I’ve changed everything and it still doesn’t work. Has anyone found a solution for Prusaslice with the tower?

I use an M600 macro in Klipper to change the color.

Also, if anyone knows how to make Klipper’s PAUSE position itself in a different location on the heated bed?

Regards,

2

Hi @dguizzo ,

Please provide the requested klippy.log and attach it to your next post. If it’s too large, you can .zip it.

1 Like
3

logs-20250807-102403.zip (557.6 KB)
I’ll send you the zip file.

4

You may look here: Move exceeds maximum extrusion (AA mm^2 vs BB mm^2) and check your settings accordingly.

You may check also that setting in the slicer, because there appears a M900 command in the log shortly before the mentioned message.

5

to use Prusaslice start and end code with

{START CODE BLOCK)

start_print BED_TEMP={first_layer_bed_temperature[0]} EXTRUDER_TEMP={first_layer_temperature[0]}

{END CODE BLOCK}

end_print

[gcode_macro START_PRINT]
gcode:
{% set BED_TEMP = params.BED_TEMP|default(65)|float %}
{% set EXTRUDER_TEMP = params.EXTRUDER_TEMP|default(215)|float %}
#{% set BED_TEMP = BED_TEMP + 5|float %}
# Start bed heating (but don't wait for it)
M140 S{BED_TEMP}
# Use absolute coordinates
G90
# Reset the G-Code Z offset (adjust Z offset if needed)
#SET_GCODE_OFFSET Z=0.0
# Reset Extruder
G92 E0
# Home the printer
G28
# Use Adaptive bed mesh Profile
BED_MESH_CALIBRATE
# Move the nozzle near the bed
G1 Z5 F3000
# Move the nozzle very close to the bed
G1 Z1 F300
# Wait for bed to reach temperature
M190 S{BED_TEMP}
# Set and wait for nozzle to reach temperature
M109 S{EXTRUDER_TEMP}

[gcode_macro END_PRINT]
gcode:
# Turn off bed, extruder, and fan
M140 S0
M104 S0
M106 S0
# Move the nozzle away from the print while retracting
G91
G1 E-3 F300
# Raise nozzle by 2mm
G1 Z2 F3000
#Park head in the back corner
PARK_HEAD

[gcode_macro PRIME_LINE]
gcode:
# Start gcode taken from prusaslice for default Ender 3 v2 profile
#G28 ; Home all axes
G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed
G1 X0.1 Y20 Z0.3 F5000.0 ; Move to start position
G1 X0.1 Y200.0 Z0.3 F1500.0 E15 ; Draw the first line
G1 X0.4 Y200.0 Z0.3 F5000.0 ; Move to side a little
G1 X0.4 Y20 Z0.3 F1500.0 E30 ; Draw the second line
G92 E0 ; Reset Extruder
G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed
G1 X5 Y20 Z0.3 F5000.0 ; Move over to prevent blob squish
[gcode_macro PARK_HEAD]
gcode:
# Use relative coordinates
G91
# Raise nozzle by 10mm
G1 Z10 F3000
# Use absolute coordinates
G90
# Park tool head
G1 X220 Y220 F3000
G90
# Disable steppers
M8420 Y220 F3000
G90

Disable steppers

M84

1:46

Klipper state: Shutdown

11:45

action:prompt_end

11:45

RESPOND type=“command” msg=“action:prompt_end”

11:45

Move exceeds maximum extrusion (2.607mm^2 vs 0.640mm^2)

11:45

Move exceeds maximum extrusion (2.607mm^2 vs 0.640mm^2)
See the ‘max_extrude_cross_section’ config option for details

11:45

Unknown command:“T1”

11:45

RESUME

6

And how do you try to initiate a filament change?

7

I have an M600 that I point to a Klipper macro, and it only happens when I have the flea tower active. If I don’t activate it, the color change works fine.

8

You could set the max_extrude_cross_section parameter to some HIGH value and trust your slicer not to overwhelm your nozzle.

Yes this is a “kludge” but it gets printing back online.

9

Sorry to be a bit harsh, but this is not a kludge, but it is exceptionally bad advice:

  • The error is there to protect the system and your quality experience from inadequate extrusion amounts that typically do not happen during correct printing operations
  • According to the OP, it happens in Prusa but not in Orca, so apparently something is out of order and needs to be identified and corrected

Personally, I’d prefer to not see advice akin to “tape over your check engine light” here.

Compare your starting and filament change G-code in your slicers. Especially watch out for differences in M82, M83, or resetting of extruder distances.

1 Like
10

I agree which is why I identified it as such.
Kludge - Wikipedia
A kludge or kluge is a clumsy, inelegant, and temporary solution to a problem

However if getting a print or 2 completed has sufficient importance to warrant the (small) risk I thought I’d give the OP the option.

I applaud the excellent work the Klipper Dev team has done to implement safety checks into the system and would NEVER give advice to circumvent any thermal or XYZ movement checks.

1 Like
11

I tried setting max_extrude_cross_section=50, if not, the error no longer appears. However, the nozzle discharges a lot of filament when it descends onto the flea tower. This whole problem doesn’t happen with Orcaslice, but it does with PrusaSlice, and I need to print with the PrusaSlice slicer.

12

Apparently my faith in the software was ill advised.

Have you reached out to the folks at Prusa?

13

What slicers do you use? I should keep this in mind, and maybe it’ll help me stop using PRUSA.

14

First off does your filament profile for PrusaSlicer have a reasonable value set for “max volumetric speed”? That should PREVENT output of g-code that overwhelms the nozzle. I SHOULD have verified that before the “trust your slicer” advice.

I apologize for any I’ll effects that resulted.

I use Orca mostly. Prior to that I used SuperSlicer. It has a couple more “knobs” for tuning supports but I like the Orca UI and the ability to load .step files.

I don’t use the prime tower feature so I can’t recommend either for your use case.

There are a couple more forks from Slic3r out there (including Bambu Studio if I recall correctly). With an Ender3 you can try them all easily enough. On Windows most will run without being installed if you download the .zip instead of the .exe installer.

15

How do I print multi-color with a single extruder? Because now I have the Move exceeds maximum extrusion error with ORCA. The problem is when I activate the extruder tower to change the filament.

16 
print.cfg
> [stepper_x]
> step_pin: PC2
> dir_pin: PB9
> enable_pin: !PC3
> microsteps: 16
> rotation_distance: 40
> endstop_pin: ^PA5
> position_endstop: 0
> position_max: 220
> homing_speed: 50
> 
> [stepper_y]
> step_pin: PB8
> dir_pin: PB7
> enable_pin: !PC3
> microsteps: 16
> rotation_distance: 40
> endstop_pin: ^PA6
> position_endstop: 0
> position_max: 220
> homing_speed: 50
> 
> [stepper_z]
> step_pin: PB6
> dir_pin: !PB5
> enable_pin: !PC3
> microsteps: 16
> rotation_distance: 8
> endstop_pin: ^PA7
> position_endstop: 0.0
> position_max: 230
> 
> [extruder]
> #max_extrude_cross_section: 5
> max_extrude_only_distance: 100.0
> step_pin: PB4
> dir_pin: PB3
> enable_pin: !PC3
> microsteps: 16
> rotation_distance: 34.406
> nozzle_diameter: 0.400
> filament_diameter: 1.750
> heater_pin: PA1
> sensor_type: EPCOS 100K B57560G104F
> sensor_pin: PC5
> control: pid
> # tuned for stock hardware with 200 degree Celsius target
> pid_Kp: 21.527
> pid_Ki: 1.063
> pid_Kd: 108.982
> min_temp: 0
> max_temp: 250
> 
> [heater_bed]
> heater_pin: PA2
> sensor_type: EPCOS 100K B57560G104F
> sensor_pin: PC4
> control: pid
> # tuned for stock hardware with 50 degree Celsius target
> pid_Kp: 54.027
> pid_Ki: 0.770
> pid_Kd: 948.182
> min_temp: 0
> max_temp: 130
> 
> [fan]
> pin: PA0
> 
> [mcu]
> serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
> restart_method: command
> 
> [printer]
> kinematics: cartesian
> max_velocity: 300
> max_accel: 3000
> max_z_velocity: 5
> max_z_accel: 100`Preformatted text`
17

Please use Preformatted Text for posting code instead of Blockquote.
With Blockquote things can be messed up.
Format

2 Likes
18

#hi, for me, this work, in klipper configs.

[exclude_object]

#hello for me this works, even if there are no multiple objects to print, there may be parts so to not add the extrusion then reset extrusion needs to be understood. and the m600 which I think is something else. or it may not be any of that, as in the past.