Thanks for the reply, but I don't think it has anything to do with the Start gcode as cura would not have access to it when slicing the file. Although if it does help, here it is:
gcode:
{% set BED_TEMP = params.BED_TEMP|default(60)|float %}
{% set EXTRUDER_TEMP = params.EXTRUDER_TEMP|default(190)|float %}
# Start bed heating
M140 S{BED_TEMP}
# Use absolute coordinates
G90
# Reset the G-Code Z offset (adjust Z offset if needed)
SET_GCODE_OFFSET Z=0.0
# Home the printer
G28
SMART_PARK
# Wait for bed to reach temperature
M190 S{BED_TEMP}
BED_MESH_CALIBRATE
# Set and wait for nozzle to reach temperature
M109 S{EXTRUDER_TEMP}
# Reset Extruder
G92 E0
# Move Z Axis up
G1 Z2.0 F3000
# Move to start position
G1 X2.1 Y20 Z0.28 F5000.0
# Reset Extruder
G92 E0
# Move Z Axis up
G1 Z2.0 F3000
; run line purge macro
LINE_PURGE
It runs well, but I just have to wait for the extruder to get to it's target temp first as cura adds it in.
I also updated the cura output in the first post as it still had some debugging code.
Edited by Trilex214
Recommended Posts
Slashee_the_Cow 541
Cura doesn't officially support Klipper, it just produces Marlin code and that works because Klipper supports a subset of Marlin commands required for movement, printing, etc.
If you could post the start gcode for your printer that would greatly help diagnose this. Cura automatically adds commands to set the extruder temperature if there isn't an M104 and/or M109 (I'm not sure if it requires a replacement pattern or if a static number would suffice, but obviously you'd want the former) line in the startup gcode, to prevent cold extrusion (which you really don't want your printer to try and do).
Link to post
Share on other sites