2.2.22. Post-processing PrusaSlicer G-Code

Todo

Post-processing PrusaSlicer g-code.

Note

These notes are based on my experiences with the Prusa i3 Mk3 and Artillery/Evnovo Sidewinder X1 printers. If you are using a different printer, please verify the hardware details are similar.

There are some things that PrusaSlicer simply doesn’t do. The ability to automatically modify gcode is provided through post-processing scripts. Scripts can be written in a variety of languages, but you are responsible for installing and configuring the programming language and support files on your system.

Once you’ve properly configured your programming language of choice, you can call a program to modify standard input and write it to another file. Here’s an example python script to briefly bump fan speeds to 100% whenever the fan is started.

Listing 2.26 Example post-processing script to bump fan to 100%

#!/usr/bin/python
import sys
import re
import os

sourceFile=sys.argv[1]

# Read the ENTIRE g-code file into memory
with open(sourceFile, "r") as f:
    lines = f.readlines()

destFile = re.sub('\.gcode$','',sourceFile)
os.rename(sourceFile,destFile+".bumpfan.bak")
destFile = re.sub('\.gcode$','',sourceFile)
destFile = destFile + '.gcode'

with open(destFile, "w") as of:
    for lIndex in xrange(len(lines)):
        oline = lines[lIndex]
        # Parse gcode line
        parts = oline.split(';', 1)
        if len(parts) > 0:
            # Parse command
            command = parts[0].strip()

            if command:
                stringMatch = re.search ('^M106 S(.*)', command)
                if stringMatch:
                    # Insert code to bump fan to max before fan speed commands
                    of.write('M106 S255\n')
            
            # Write original line       
            of.write(oline)
of.close()
f.close()

Specify the path to the script

Fig. 2.27 Specify post-processing script path