Differences

This shows you the differences between two versions of the page.

--- print_start_workflows [2025/11/04 01:56] – dshoop
+++ print_start_workflows [2025/11/05 17:52] (current) – [Example Orca Machine Start gcode] dshoop
@@ Line 1: / Line 1: @@
 ====== Print Start Workflows ======
-{{tag> articles setup}}
+{{tag> articles setup about}}
 One way (slicer side and [[slicer machine start print gcode]]), or another (Klipper side and [[PRINT_START macro]]), there's certain steps we need to take to start printing the gcode that's slice from an object. There's reasons and rationale for why you'd place certain actions where.
@@ Line 29: / Line 29: @@
 <code>
 ;
-; Orca Slicer Machine Start G-code by @dshoop v2.1
+; Orca Slicer Machine Start G-code by @dshoop v2.2a
 ;
@@ Line 37: / Line 37: @@
 ; was called automatically.
-G28; Home, if this fails no point to continue
+G28; Home, if this fails no point to continue; required before BED_MESH_CALIBRATE
 M190 S[bed_temperature_initial_layer_single] ;wait for bed to reach temperature
 M104 S150 ;pre-warm extruder to 150C below typical extrusion temps so as not to ooze, no wait
@@ Line 66: / Line 66: @@
 [gcode_macro PRINT_START]
 gcode:
-	RESPOND PREFIX="" MSG=">> PRINT START <<"
+	RESPOND PREFIX="" MSG=">> Klipper PRINT_START Macro <<"
-	M117 Starting Klipper START_PRINT code
+	M117 Starting Klipper START_PRINT macro
-	M400	; wait for current moves to finish
+	M400 ; wait for current moves to finish
-	CLEAR_PAUSE
+	CLEAR_PAUSE ; clear any pause conditions
 	G28 ; home before SCREWS_TILT_CALCULATE
 	SCREWS_TILT_CALCULATE max_deviation=0.02 ; assume bed's z plane is level within given deviation
-  	M105 ;Request a temperature report to be sent to the host as soon as possible
+  	M105 ;Request temperature reports to be sent to the host as soon as possible
-	RESPOND PREFIX="" MSG=">> GCODE START <<"
+	RESPOND PREFIX="" MSG=">> PRINT_START Macro complete <<"
-  	M117 Executing gcode
+  	M117 PRINT_START Macro complete
 </code>