From 700a1cae59cb9238521221d3225d4ba30d7f4656 Mon Sep 17 00:00:00 2001 From: Tim van Dalen Date: Sun, 20 Oct 2024 10:49:31 +0200 Subject: [PATCH] Add note about flow differences to retraction troubleshooting --- calibration.html | 1 + 1 file changed, 1 insertion(+) diff --git a/calibration.html b/calibration.html index 617352c..1766dee 100644 --- a/calibration.html +++ b/calibration.html @@ -777,6 +777,7 @@
I can't translate my test results to my own slicer! Other factors beyond the
  • Maximum extruder feedrate: Your firmware may have a hard limit imposed on extruder movement that is below the retraction speed values you are attempting to use with the form above. You may need to use M203 to raise the extruder feedrate limit to try higher values for retraction speed. This potentially needs to be saved with M500 if you want it to be permanent.
  • Travel feedrate: A travel move is one where the printer moves to a new location without extruding. The slower this move is, the more time filament will have to ooze from the nozzle and add to stringing. The default feedrate is set to 100mm/sec in the gcode generator above, and increases or decreases based on the user feedrate input. Matching this in your slicer is advised if these tests look better than your own slicer results.
  • Travel acceleration: This test does not manipulate travel acceleration but increasing its value may help reduce stringing. You can change travel acceleration with M204 and the T argument.
    • +
  • Flow differences: The gcode on this site originally had a flow rate of 90% when sliced. In Simplify3D and PrusaSlicer, this is called Extrusion Multiplier. Cura calls it Flow.
  • Linear advance: Linear advance, covered later in this guide, can drastically improve the accuracy of our extrusion. It has a significant impact of retraction (reducing the need), so after configuring linear advance you may need to revisit retraction.
  • Slicer differences: The gcode generated below was originally sliced by Simplify3D. The settings you establish should translate to your slicer quite well but there may be idiosyncrasies. For instance, Cura measures extra restart distance in volume rather than length.