PrusaSlicer adding gcode to output file
Hi,
I have an Ender 3 Pro with BL Touch and Sprite Hotend running on Klipper. I have a START_PRINT and END_PRINT macro setup in the Mainsail.cfg, but PrusaSlicer adds some code to the output and I cannot find out why.
; generated by PrusaSlicer 2.5.0+linux-x64-GTK3 on 2022-11-09 at 19:05:11 UTC;
; external perimeters extrusion width = 0.45mm
; perimeters extrusion width = 0.45mm
; infill extrusion width = 0.45mm
; solid infill extrusion width = 0.45mm
; top infill extrusion width = 0.40mm
; first layer extrusion width = 0.42mm
M107
M190 S65 ; set bed temperature and wait for it to be reached
M104 S210 ; set temperature
;TYPE:Custom
START_PRINT
I'm not worried about the comments but where is the block coming just before START_PRINT?
Thanks,
Graham
RE: PrusaSlicer adding gcode to output file
Are you using Prusa Slicer in 'Expert Mode'?
If you are, have a look at
Printer Settings> Custom Gcode > Start Gcode
and you should see something like
G90 ; use absolute coordinates
M83 ; extruder relative mode
M104 S150 ; set temporary nozzle temp to prevent oozing during homing
M140 S{first_layer_bed_temperature[0]} ; set final bed temp
G4 S20 ; allow partial nozzle warmup
G28 ; home all axis
G1 Z50 F240G1 X2.0 Y10 F3000M104 S{first_layer_temperature[0]} ; set final nozzle temp
M190 S{first_layer_bed_temperature[0]} ; wait for bed temp to stabilize
M109 S{first_layer_temperature[0]} ; wait for nozzle temp to stabilize
G1 Z0.28 F240G92 E0G1 X2.0 Y140 E10 F1500 ; prime the nozzle
G1 X2.3 Y140 F5000G92 E0G1 X2.3 Y10 E10 F1200 ; prime the nozzle
G92 E0
(THIS IS ENDER3 STUFF, i DON'T HAVE AN ENDER3 pRO PROFILE LOADED AT THE MOMENT) Sorry for shouting...
Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: PrusaSlicer adding gcode to output file
Hi Joan,
thanks for the reply.
Yes I've moved that to the START_PRINT macro, but because there was nothing in the Start gcode block PS would add some basic heater code 😡
Somebody showed me their config and the trick was to add :
M190 S0 ; Prevents prusaslicer from prepending m190 to the gcode ruining our macro
M109 S0 ; Prevents prusaslicer from prepending m109 to the gcode ruining our macro
START_PRINT B_TEMP=[first_layer_bed_temperature] E_TEMP1={first_layer_temperature[0] - 50} E_TEMP2=[first_layer_temperature]
Now it's working like it did before the switch to Klipper
Thank you,
Graham
RE: PrusaSlicer adding gcode to output file
Cheers.
Glad it's sorted
Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: PrusaSlicer adding gcode to output file
I'm using ver 2.5 and the M109 S<temp> gets added AFTER(!) the custom start code. Therefor it's not possible to cancel it out with "M109 S0". A workaround would be to call the Klipper start macro filament custom start code section instead or alternatively not use a start macro at all, at least not for temp control.
In short, Prusa Slicer adds stuff that can't be removed or controlled. Cura on the other hand appears to skip native gcode temp settings when a Klipper start macro is added.