M104/M105/M109 always emitted, even when {material_print_temperature_layer_0}
is used in the Start G-Code
#19231
Labels
Status: Under Investigation
The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion.
Type: Bug
The code does not produce the intended behavior.
Cura Version
5.7.2
Operating System
Windows 11
Printer
Ender 3 v2 - klipper
Reproduction steps
I do not want cura to emit M104/M105/M109 commands at the start of the print to heat up the print head. In the past, I was able to get around this by setting custom start G-code (under preferences > Printers > [printer] > Machine Settings > Start G-code) like so:
Which calls my
START_PRINT
macro defined in my printer.Cura would then pick up that
{material_print_temperature_layer_0}
is being used, and does not emit the M104/M105/M109 codes. However this stopped working in 5.7.2.Note that the behavior still works for the bed M140/M190 gcodes and
{material_bed_temperature_layer_0}
. Only the extruder temp gcodes are broken.Actual results
Cura emits the following gcode: (broken in 5.7.2)
Expected results
Cura emits the following gcode: (working in 5.7.1)
Add your .zip and screenshots here ⬇️
Sidenote: it was quite hard to find how to get cura to not emit these M104/M105/M109 gcodes (and similar for bed temp) in the first place.
I think it would be a good idea to add some grey text below the Start G-code box, mentioning this fact.
The text was updated successfully, but these errors were encountered: