8000 GitHub - foreachthing/Slic3rPostProcessing at e380090c032cc4cc4f88c4ae5a10976068a0a55f
[go: up one dir, main page]

Skip to content

Post-Processing Script to make the "Cura-Move" and add counter file prefix and much more...

License

Notifications You must be signed in to change notification settings

foreachthing/Slic3rPostProcessing

Repository files navigation

Slic3r-Post-Processing

What it does

Post processing for PrusaSlicer, SuperSlicer and maybe Slic3r:

All-New Python Script:

In /SPP-Python/ is the Python-version of the "Cura"-move:

  1. Heat up, down nozzle and ooze at your discretion.
  2. Move to the first entry point on XYZ simultaneously.
    • Before: heat up, ooze, move to first layer height (Z), move to first start point (XY). This could lead to crashing the nozzle into the clips.
    • Now: heat up, ooze, move to first start point (XYZ). The Python version does not require the verbose mode enabled or any other changes to the Start-, End-, or Layer-code.

Only requirement: the gcode has to have ;HEIGHT:[layer_z] after G92 E0, or after Header G-Code. If you use a recent version of PrusaSlicer, you don't have to do anything. With Slic3r you'd have to add ;HEIGHT:[layer_z] to the "Before layer change G-Code" field.

Parameters for the Python Version

  1. Optional: --xy will move to X and Y first, then drops on Z (eases-in a bit: full speed to 15 times "first layer height", then at half speed to first layer height). Omitting this option will lead to XYZ simultaneous move to first point. This will still clear the clips on the Ultimaker 2 plate. If not, you'd have to edit your start gcode to place the nozzle somewhere "better" (i.e. in the center of the bed) first.
  2. Optional: --oc obscures slicer configuration at the end of the file. None of the settings will remain for anyone to see.
  3. Optional: --rk removes comments except configuration and real comments.
  4. Optional: --rak removes all comments.
  5. Optional: --backup create a backup file if True is passed.
  6. Optional: --filecounter adds a file counter (prefix) to the output file name.
  7. Optional:  --rev reverse counter (count down).
  8. Optional:  --setcounter set counter manually to this [int].
  9. Optional:  --digits set counter's number of digits. I.e. 5 = 00123.
  10. Optional: --notprusaslicer should work with non-PrusaSlic3r (not tested!).
  11. Optional: --prog a progress bar will be pushed to display (M117).
  12. Optional: --pwidth progress bar width in chars (= display-char-width - 2).
  13. GCode file name (will be provided by the Slicer; must be provided if used as standalone)

Installation

Add this line to your "Print Settings" under "Output options" to the "Post-Processing scrips" field: <path to python.exe> <path to script>\Slic3rPostProcessor.py;, or <path to python.exe> <path to script>\Slic3rPostProcessor.py --xy; (see above).

If you have one or more script active, add this to the correct spot (add new line). Scripts will be processed from top to bottom.

to use in Slic3r

  • The option verbose in Slic3r (Slic3r -> Print Settings -> Output options), needs to be set to true.
    • In Post-Processing Scripts, add the full path to this exe (see screenshot below).
  • In Slic3r -> Printer -> Custom G-Code; add this:
    • Start G-Code:
      • ; START Header
      • ; ... your header here
      • ; END Header
    • End G-Code:
      • ; START Footer
      • ; ... your footer here
      • ; END Footer
    • Before layer change G-Code: ;layer:[layer_num]; \n M117 Layer [layer_num];

NOTE:

CS version will no longer be maintained and has been removed.

About

Post-Processing Script to make the "Cura-Move" and add counter file prefix and much more...

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published
0