Cancel print crashed nozzle into printed object

[eloo]

Description

Hi, when i cancel a print on the display the nozzle will everytime try to go Z25.

If the print is already higher than 25mm it crashed into the print.

Steps to Reproduce

1. Print something higher than 25mm
2. Cancel the print on the display
3. See the nozzle going down and crashing into your print

Expected behavior:

I would expect the nozzle to liften a bit or at least to not change its Z position.

Actual behavior:

Nozzle tries to go to Z position 25

Additional Information

Version: Jyers-2.0.1-E3V2-UBL-BLTouch-10x10-v4.2.2-v2.0.1.bin

[eloo]

Okay, my end g-code in cura looks like this:

G91 ;Relative positioning
G1 E-2 F2700 ;Retract a bit
G1 E-2 Z0.2 F2400 ;Retract and raise Z
G1 X5 Y5 F3000 ;Wipe out
G1 Z10 ;Raise Z more
G90 ;Absolute positioning

G1 X0 Y{machine_depth} ;Present print
M106 S0 ;Turn-off fan
M104 S0 ;Turn-off hotend
M140 S0 ;Turn-off bed

M84 X Y E ;Disable all steppers but Z

for me this looks like the z should be raised and not lowered. also rest is of this gcode seems not be executed when i abort.. because the bed is also not moving forward and so on.

[C-Noob404]

I had exactly the same problem with the Ender 3 v2. Crashed my nozzle into the bed. Went straight back to v1.3.5.b and everything worked just fine. Pls check again.

[eloo]

@tititopher68-dev

good hint with Octoprint. Yes i'm using octoprint and i guess i have found the issue.

I had the Z+25 in my octoprint and was assuming that this is relativ to the current position. But i guess its not relativ but absolut. So it was 0 + 25..

I have now adjusted my code in Octoprint to

; disable motors
M84

; disable all heaters
{% snippet 'disable_hotends' %}
{% snippet 'disable_bed' %}
;disable fan
M106 S0

; relative XYZE
G91
M83

; retract filament, move Z slightly upwards
G1 E-1 F1000
G1 Z+5 F4500

; absolute XYZE
M82
G90

; move to a safe rest position, adjust as necessary
G1 X0 Y200

But as @C-Noob404 also mentioned.. maybe there was a change from 1.3.5.b to 2.x

Because in the old version i could not remember to have this issue with my old code. Maybe the Stop/Cancel GCODE in the firmware has changed?