UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
Cura tries to protect your printer against cold extrusion.
Cura tries to see if there is anything in your start gcode that heats up your extruder(s), and bed. If not, it will insert a heatup sequence on its own. Cura does not know about your PRINT_START macro.
Cura looks for the text "{material_print_temperature}", "{material_print_temperature_layer_0}", "{default_material_print_temperature}", "{material_initial_print_temperature}", "{material_final_print_temperature}" or "{material_standby_temperature}" in the start gcode to check if the start gcode contains extruder heating commands (so it does not actually care if you use M104 or M109 or not).
Cura looks for the text "{material_bed_temperature}" or "{material_bed_temperature_layer_0}" in the start gcode to check if the start gcode contains bed heating command (so it does not actually care if you use M140 or M190 or not).
As AHoeben explained...if there are Cura keywords in the startup then Cura itself doesn't have to include the temperature prepend lines.
For example: If your StartUp G-Code contained something like this:
M140 S{material_bed_temperature_layer_0}
M109 S150
PRINT_START
G0 F600 Z2.0
G0 F3600 X0 Y0
M109 S{material_print_temperature_layer_0}
Then the hot end would wait until it hit 150, then the "print_start" macro would run in the firmware, and then printhead would move up and off to a corner to ooze, and then the hot end would wait until it hit the "Initial Layer Print Temperature".
So it appears that at least one Voron model will accept temperature parameters as part of the "PRINT_START" macro.
So your homework assignment for today includes some light reading and a bit of detective work to see if your machine will accept any parameters for PRINT_START. (BTW The curly brackets are required for Cura keywords.)
1
1
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more.
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
Recommended Posts
ahoeben 1,951
Cura tries to protect your printer against cold extrusion.
Cura tries to see if there is anything in your start gcode that heats up your extruder(s), and bed. If not, it will insert a heatup sequence on its own. Cura does not know about your PRINT_START macro.
The logic is here:
https://github.com/Ultimaker/Cura/blob/4.4/plugins/CuraEngineBackend/StartSliceJob.py#L428
Cura looks for the text "{material_print_temperature}", "{material_print_temperature_layer_0}", "{default_material_print_temperature}", "{material_initial_print_temperature}", "{material_final_print_temperature}" or "{material_standby_temperature}" in the start gcode to check if the start gcode contains extruder heating commands (so it does not actually care if you use M104 or M109 or not).
Cura looks for the text "{material_bed_temperature}" or "{material_bed_temperature_layer_0}" in the start gcode to check if the start gcode contains bed heating command (so it does not actually care if you use M140 or M190 or not).
Link to post
Share on other sites
GregValiant 1,259
As AHoeben explained...if there are Cura keywords in the startup then Cura itself doesn't have to include the temperature prepend lines.
For example: If your StartUp G-Code contained something like this:
M140 S{material_bed_temperature_layer_0}
M109 S150
PRINT_START
G0 F600 Z2.0
G0 F3600 X0 Y0
M109 S{material_print_temperature_layer_0}
Then the hot end would wait until it hit 150, then the "print_start" macro would run in the firmware, and then printhead would move up and off to a corner to ooze, and then the hot end would wait until it hit the "Initial Layer Print Temperature".
The Voron2 250 has this in the startup:
print_start EXTRUDER={material_print_temperature_layer_0} BED={material_bed_temperature_layer_0} CHAMBER={build_volume_temperature}
So it appears that at least one Voron model will accept temperature parameters as part of the "PRINT_START" macro.
So your homework assignment for today includes some light reading and a bit of detective work to see if your machine will accept any parameters for PRINT_START. (BTW The curly brackets are required for Cura keywords.)
Link to post
Share on other sites