Why is this "job start" gcode heat up the tool prematurely

janjoh

I am running Cura, and I am using the following code for job start.

What I cant figure out is why the printer starts to heat up the hotend as the G32 begins. I would like to keep it cool until the G32 is completed.

M220 S100
G28 ; Home
M140 S{material_bed_temperature_layer_0} ;Start heating bed
M190 S{material_bed_temperature_layer_0} ;Wait for bed to reach temp before proceeding
G28 ; Home
;;;M98 P"0:/macros/NozzleCleanNew"
;;G30 ; Single probe
;;G29 S2 ; Bed Mesh Probe, S2 Clear map
;;G29 ; Bed Mesh Probe
G32
G0 Z10 X0 Y0 F2500
M104 S{material_print_temperature_layer_0} ;Start heating extruder
M109 S{material_print_temperature_layer_0} ;Wait for extruder to reach temp before proceeding
G1 E5 F180

fcwilt

@janjoh

Thanks.

Just as a test add a M400 command in the print file after the G0 command that follows the G32 command.

Frederick

fcwilt

@janjoh

What code does your bed.g file contain?

Please post it here.

Frederick

janjoh

@fcwilt

; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 16 points, 6 factors, probing radius: 127, probe offset (0, 0)
G28
G30 P0 X0.00 Y127.00 Z-99999 H0
G30 P1 X81.63 Y97.29 Z-99999 H0
G30 P2 X125.07 Y22.05 Z-99999 H0
G30 P3 X109.99 Y-63.50 Z-99999 H0
G30 P4 X43.44 Y-119.34 Z-99999 H0
G30 P5 X-43.44 Y-119.34 Z-99999 H0
G30 P6 X-109.99 Y-63.50 Z-99999 H0
G30 P7 X-125.07 Y22.05 Z-99999 H0
G30 P8 X-81.63 Y97.29 Z-99999 H0
G30 P9 X0.00 Y63.50 Z-99999 H0
G30 P10 X54.99 Y31.75 Z-99999 H0
G30 P11 X54.99 Y-31.75 Z-99999 H0
G30 P12 X0.00 Y-63.50 Z-99999 H0
G30 P13 X-54.99 Y-31.75 Z-99999 H0
G30 P14 X-54.99 Y31.75 Z-99999 H0
G30 P15 X0 Y0 Z-99999 S6

fcwilt

@janjoh

Thanks.

Just as a test add a M400 command in the print file after the G0 command that follows the G32 command.

Frederick

janjoh

@fcwilt said in Why is this "job start" gcode heat up the tool prematurely:

@janjoh

Thanks.

Just as a test add a M400 command in the print file after the G0 command that follows the G32 command.

Frederick

That works, and is a simple fix. And I see the Logic. I just thought that the G32 would be blocking until completed.

Thank you.

fcwilt

@janjoh

Someone like @dc42 that knows how the firmware works could answer fully but my understanding is that movement commands are put into a queue and the processing of the print file continues as best it can.

Frederick

janjoh

@fcwilt Yeah, I know about the queue. I dunno, I guess i just Assumed that it would not be utilized for homing calibration other such things.

WHY i guessed that... I do not know. A move is a move is a move really.