PRINT_START heat nozzle and bed at once

Basic Information:

Printer Model: Ender 3V2
MCU / Printerboard: Creality
Host / SBC: RPI3

I would like to create a macro START_PRINT that heats nozzle and bed at the same time.

I replaces the start gcode in Cura with PRINT_START

The Macro looks like this:

[gcode_macro PRINT_START]
 gcode:
     {% set BED_TEMP = params.BED_TEMP|default(30)|float %}
     {% set EXTRUDER_TEMP = params.EXTRUDER_TEMP|default(150)|float %}
     # Home the printer
     G28
     # Start bed heating
     M140 S{BED_TEMP}
     M104 S{EXTRUDER_TEMP}
     M190 S{BED_TEMP}
     M109 S{EXTRUDER_TEMP}
     # Use absolute coordinates
     G90
     # Move the nozzle near the bed
     G1 Z5 F3000
     # Move the nozzle very close to the bed
     G1 Z0.15 F300

But what ever I do with heating commands, always the bed is heated first.
I either end up with parse errors. Also I doesn’t execute G28 first. I want it to home before heating. At the moment it is the other way arround.

When I change the nozzle or bed temp in cura these temps are used while printer, so klipper is overlooking the default temps.

I am out of ideas. Also the klippy.log is not updating for some reason.
I installed klipper using the raspberry imager tool.

Hello @rgrs !

Please do not delete the lines that ask for the klippy.log - please attach it to your next post.

When you post code snippets, please use the Preformatted Text feature of the forum editor, else characters get lost.

Format

Of course

# Start bed heating
M140 S{BED_TEMP}
M104 S{EXTRUDER_TEMP}
M190 S{BED_TEMP}  # <- this waits until the temp is reached.
M109 S{EXTRUDER_TEMP}

You may have a look on this:

klippy.log (2.2 MB)
I added the klippy.log I had to press the refresh button apparently.
I commented out M190, still does not heat the bed and nozzle at the same time. Starts with the bed first.

Nevermind, I figured it out.

And how did you do it?

1 Like

Well, to do this I at first did not read the docs, lazy as I am I watched a youtube video on how to do this, from CHEP. Not realizing this was an old video.
Next I had a look at the sample macro.cfg. It mentioned that I need to add START_PRINT I my slicer. However… I read the docs more closely and than realised, it is never that easy. I had to add more information to my slicer, which is exactly not what I expected.

This line did the trick: PRINT_START BED_TEMP={material_bed_temperature_layer_0} EXTRUDER_TEMP={material_print_temperature_layer_0}

Thanks for pointing me to the docs :slight_smile:

Ow, and I have to add, that I do own a Sonicpad, for some reason that does work different, because I have a completely different startcode in cura. This code threw a parse error in klipper. So my confusion was complete.

1 Like

The sonic Pad is a story of it’s own:

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.