3DPrinting

15618 readers

376 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: !functionalprint@kbin.social or !functionalprint@fedia.io

There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml

Rules

No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
Be respectful, especially when disagreeing. Everyone should feel welcome here.
No porn (NSFW prints are acceptable but must be marked NSFW)
No Ads / Spamming / Guerrilla Marketing
Do not create links to reddit
If you see an issue please flag it
No guns
No injury gore posts

If you need an easy way to host pictures, https://catbox.moe/ may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 1 year ago

MODERATORS

j4k3@lemmy.world

andypiper@lemmy.world

henry_rowengartner@lemmy.world

GrayBackgroundMusic@lemm.ee

[HELP] PrusaSlicer and Klipper (mainsail) ERROR: Move exceeds max extrusion | SV06 (self.3dprinting)

submitted 1 year ago* (last edited 1 year ago) by TheSun to c/3dprinting@lemmy.world

17 comments fedilink hide all child comments

Hi everyone, I figured I have struggled with this enough over the past day and its time to consult the community. I've been running this same setup for about a month now with the only major change in that time being implementing the input shaping. Recently (last week) I have been unable to complete any prints because every time, I get the error: Move exceeds maximum extrusion ((in the case) 10.681mm^2 vs 0.640 mm^2).

My research says that it is likely due to a mix up between relative and absolute extrusion mode, however I did not change any of those settings in the past month prior to the start of this issue.

Troubleshooting conducted so far: 1) uncheck relative extrusion distances in printer settings>general RESULT -> same error. 2) re-enable relative extrusion in the slicer and explicitly add an M83 command to START_PRINT macro RESULT -> same error. 3) disable the check altogether and observe the print by adding MAX_EXTRUDE_CROSS_SECTION of 50 into printer.cfg RESULT -> no error, but it is massively overextruding blobs in that spot as expected given the error. Had to cancel print anyways it was so bad.

Edit: T.S. continued: 4) setting pressure advance to 0. RESULT -> same error.

Here is my START_PRINT macro before I started messing with it troubleshooting.

Pressure advance is 0.0425.

I'm not sure if there is more information I would need to share that may help find the cause like perhaps export the profile from the slicer as well?

I'm on PrusaSlicer 2.6.1 appimage on pop_OS using the Ellis 3d Sovol SV06 SuperSlicer profile adapted to PrusaSlicer with some tweaks as I go.

Printer is an SV06 running Klipper on a Raspberry Pi 4 with MainsailOS.

you are viewing a single comment's thread
view the rest of the comments

[–] CmdrShepard@lemmy.one 5 points 1 year ago* (last edited 1 year ago) (2 children)

Not sure what initially caused your issue but try throwing a G92 E0 into your start gcode right after homing and also after any purge line you may have setup.

I've encountered this same error when trying to recover failed prints by restarting them at the failed layer. If you don't tell the extruder it should already be some distance through the print, it throws out the exact same error. Since you're starting at '0' it needs to be told that.

[–] TheSun 1 points 1 year ago (1 children)

Thanks for the suggestion. Just tested by adding G92 E0 right after the PRINT_START and PURGE_LINE macros and it still has the same error at the same spot; right as it goes around the circle part of the elbow on the second layer.

[–] CmdrShepard@lemmy.one 1 points 1 year ago* (last edited 1 year ago)

Might be something wrong with the slicer. Try a different slicer and if that doesn't work try a different file. I've had Cura updates break my gcode in the past.

You might manually look through the gcode file and see if you see anything out of the ordinary at that layer.

[–] atocci@kbin.social 1 points 1 year ago

I was having a similar problem with my printer as well, and this is what solved it. I wasn't able to print 2 things back-to-back without restarting the firmware first.