Klipper firmware: Add the ability for custom gcode to recognize PRINT_START/START_PRINT macro

[MrCroup]

Version

Latest

Add the ability for custom gcode to recognize PRINT_START/START_PRINT macro or, as in SuperSlicer (based on PrusaSlicer) add a function to only use the custom start gcode with no modifications by PrusaSlicer.

I would like to use PrusaSlicer for my 3D Printers that are using Klipper firmware, but PrusaSlicer doesnt recognize the PRINT_START/START_PRINT macro as a valid startup gcode and adds gcode to set the temperature for extruder and bed.

With klipper, the macro is used to bring the heat up in stages and allow for heat soak time without bringing the system up to 100% temp on the extruder. A typical Klipper START_PRINT macro would look like this in the start custom gcode:

START_PRINT T_BED=[first_layer_bed_temperature] T_EXTRUDER=[first_layer_temperature]

[rtyr]

I believe this is a duplicate of #2420. This workaround should work for you #2420 (comment).

[besser]

Before, if I wanted to use PrusaSlicer with Klipper, I had to open the G-code and remove the M104 and M190 codes that are always appearing before the custom G-code.

But now, I do this in my PrusaSlicer Custom G-code:

;-----------------------------------------
; Klipper Custom Start G-Code - START HERE
;-----------------------------------------
M104 S0
M140 S0
START_PRINT EXTRUDER_TEMP={first_layer_temperature[0]} BED_TEMP={first_layer_bed_temperature[0]} 
;-----------------------------------------
; Klipper Custom Start G-Code - END HERE
;-----------------------------------------

[besser]

Complementing what MrCroup said:

[lukasmatena]

Setting temperatures automatically is optional since 2.6.0-alpha6. Closing.