docs: addition of slicer specific gcode for START_PRINT (#6063)

Signed-off-by: James Hartley <james@hartleyns.com>
This commit is contained in:
JamesH1978 2023-03-15 01:09:00 +00:00 committed by GitHub
parent 187173cbb5
commit 2337d05f48
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 35 additions and 1 deletions

View File

@ -10,7 +10,7 @@
######################################################################
# Replace the slicer's custom start and end g-code scripts with
# START_PRINT and END_PRINT.
# START_PRINT and END_PRINT. See docs/Slicers.md for more information on using these macros.
[gcode_macro START_PRINT]
gcode:

View File

@ -87,3 +87,37 @@ Klipper's maximum extrusion cross-section check.
In contrast, it is okay (and often helpful) to use a slicer's
"retract" setting, "wipe" setting, and/or "wipe on retract" setting.
## START_PRINT macros
When using a START_PRINT macro or similar, it is useful to sometimes
pass through parameters from the slicer variables to the macro.
In Cura, to pass through temperatures, the following start gcode
would be used:
```
START_PRINT BED_TEMP={material_bed_temperature_layer_0} EXTRUDER_TEMP={material_print_temperature_layer_0}
```
In slic3r derivatives such as PrusaSlicer and SuperSlicer, the
following would be used:
START_PRINT EXTRUDER_TEMP=[first_layer_temperature] BED_TEMP=[first_layer_bed_temperature]
Also note that these slicers will insert their own heating codes when
certain conditions are not met. In Cura, the existence of the
`{material_bed_temperature_layer_0}` and `{material_print_temperature_layer_0}`
variables is enough to mitigate this. In slic3r derivatives,
you would use:
```
M140 S0
M104 S0
```
before the macro call. Also note that SuperSlicer has a
"custom gcode only" button option, which achieves the same outcome.
An example of a START_PRINT macro using these paramaters can
be found in config/sample-macros.cfg