Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
5.95k stars 2.04k forks source link

[5.7.2] Undesired Preheating Sequence added before "Start G-code" #19264

Closed khani3s closed 1 week ago

khani3s commented 1 week ago

Cura Version

5.7.2

Operating System

Windows 11

Printer

Custom Ender3 Pro with Klipper

Reproduction steps

START_PRINT BED_TEMP={material_bed_temperature_layer_0} EXTRUDER_TEMP={material_print_temperature_layer_0} CHAMBER_TEMP={build_volume_temperature} PRINT_MIN=%MINX%,%MINY% PRINT_MAX=%MAXX%,%MAXY%

Slice a model using Cura 5.7.1 and note the generated G-code. Slice the same model using Cura 5.7.2 and compare the generated G-code.

Actual results

In Cura 5.7.2, the generated G-code includes additional preheating commands before the custom START_PRINT command:

(...)
;Generated with Cura_SteamEngine 5.7.2
M104 S210 
M105 
M109 S210
M82 ;absolute extrusion mode
START_PRINT BED_TEMP=60.0 EXTRUDER_TEMP=210.0 CHAMBER_TEMP=0 PRINT_MIN=8.355,119.078 PRINT_MAX=44.733,155.454
(...)

Expected results

In Cura 5.7.1, the generated G-code includes the custom START_PRINT command without preheating commands:

(...)
;Generated with Cura_SteamEngine 5.7.1
M82 ;absolute extrusion mode
START_PRINT BED_TEMP=60.0 EXTRUDER_TEMP=210.0 CHAMBER_TEMP=0 PRINT_MIN=8.355,119.078 PRINT_MAX=44.733,155.454
(...)

The generated G-code in Cura 5.7.2 should be similar to the G-code from Cura 5.7.1, where the custom START_PRINT command appears without additional preheating commands.

Add your .zip and screenshots here ⬇️

.

khani3s commented 1 week ago

I think that is related to with the " Improved behaviors for start temperature for multiple extruders"

yazz007 commented 1 week ago

IMHO There is unnecessary wait for hot-end temperature, in the same time bad heating can start, so both starts at the same time. ;Generated with Cura_SteamEngine 5.7.2 T1 M104 S210 M105 M109 S210 M82 ;absolute extrusion mode ;--- Start G-code Begin --- M104 S210 ;Set Hotend Temperature M140 S65 ;Set Bed Temperature G28 ;home M109 S210 ;Wait for Hotend Temperature M190 S65 ;Wait for Bed Temperature G90 ;absolute positioning G0 X-10 Y-10 F3000 G0 Z0 F1800 G92 E0 G1 E20 F200 G0 X0 Y0 F3000 ;Move to origin G0 Z1 F1800 ;Move up to avoid scraping against heated bed G92 E0 ;--- Start G-code End ---

I would prefer to leave it to Start G-code section or add at least M140 after M104, so: T1 M104 S210 M140 S65 M105 M109 S210

BearBBQ1882 commented 1 week ago

This new hot end Gcode before the start Gcode in version 5.7.2 is most certainly erroneous. For those of us with UBL and ABL, the hot end is going to heat up before probing and leave little blobs of filament all over the build plate. Rolling back to 5.7.1 is the only fix for this issue until it is fixed in an update.

GregValiant commented 1 week ago

Thanks for the report. This is a duplicate. Please see bug report #19204 . I wrote a post processor to address the problem.

Unzip the attached file and put the "CuraPrependBugFix.py" into the Cura installation folder. On Windows it would be something like: "C:\Program Files\UltiMaker Cura 5.7.2\share\cura\plugins\PostProcessingPlugin\ scripts

It could also go into the Configuration Folder which on Windows would be something like: "...\AppData\Roaming\cura\5.7\ scripts

After a restart of Cura it will be available under "Extensions / Post Processing / Modify Gcode" and then "Add Script". It simply deletes the extra temperature lines that are being mistakenly added in front of the StartUp Gcode.

CuraPrependBugFix.zip

The Cura team is aware of this so I'll go ahead and close this report in favor of the first one.