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.

  • TheSun@slrpnk.netOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      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.