[3.5.0-rc2] Head Crashing into the print at the end of the job

vBence

Hi Gents,

I have one issue where at the end of the printjob the head moves like its returning to a previous position, and collides with the print.

What i have figured out so far:
The gcode does not finish (I put some echoes in to see where the problem occurs).
Whenever a pause is involved in the print it happens,
Macro calling in the start/end gcode affect it (not the start.g and end.g)

config.g:

; General preferences
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"RatRig 500"                                  ; set printer name
M669 K1                                            ; select CoreXY mode

; Wait a moment for the CAN expansion boards to start
G4 S2

; Network
M552 P172.28.11.151 S1                             ; enable network and set IP address
M553 P255.255.255.0                                ; set netmask
M554 P172.28.11.1                                  ; set gateway
M586 P0 S1                                         ; enable HTTP
M586 P1 S0                                         ; disable FTP
M586 P2 S0                                         ; disable Telnet

; Drives
M569 P51.0 S0 D2                                       ; physical drive 121.0 goes forwards
M569 P52.0 S1 D2                                       ; physical drive 122.0 goes forwards
M569 P0.0 S0                                       ; physical drive 0.0 goes forwards
M569 P0.1 S0                                       ; physical drive 0.3 goes forwards
M569 P0.2 S0                                       ; physical drive 0.0 goes forwards
M569 P0.4 S1                                       ; physical drive 0.3 goes forwards
M569 P0.3 S1                                       ; physical drive 0.0 goes forwards
M569 P0.5 S1                                       ; physical drive 0.3 goes forwards
M584 X52.0 Y51.0 Z0.0:0.1:0.2 E0.4:0.3:0.5               ; set drive mapping
M350 X16 Y16 Z16 E16 I1                            ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 E400.00:91:91                 ; set steps per mm
M566 X600.00 Y600.00 Z30.00 E240.00                ; set maximum instantaneous speed changes (mm/min)
M203 X21000.00 Y21000.00 Z1200.00 E4500.00            ; set maximum speeds (mm/min)
M201 X2500.00 Y2500.00 Z600.00 E1000.00                ; set accelerations (mm/s^2)
M906 X1800 Y1800 Z1500 E650:1400:1400 I30                      ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout

; Axis Limits
M208 X-10 Y0 Z0 S1                                   ; set axis minima
M208 X500 Y500 Z500 S0                             ; set axis maxima


; Z-Probe
M558 P1 C"0.io6.in" H2:0.6 F1200:450 T18000 A8                             ; disable Z probe but set dive height, probe speed and travel speed
G31 X-5 Y-20 P750 Z0.95
M557 X25:475 Y25:475 S50                           ; define mesh grid
M376 H10

; Endstops
M574 X1 S1 P"52.io0.in"
M574 Y2 S1 P"51.io0.in"

;Bed Tilt correction
M671 X-5:250:505 Y0:520:0 S25					; position of leadscrew/bed pivot point at front left, rear middle and front right

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138       ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out1" T0 Q50                             ; create bed heater output on out0 and map it to sensor 0
M307 H0 B0 S1.00                                   ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                            ; map heated bed to heater 0
M143 H0 S140                                       ; set temperature limit for heater 0 to 125C
M570 H0 P45 T15                                   ; An anomaly on heater 2 must persist for 600 seconds, and must be greater or less than 20C from the setpoint, to raise a heater fault.

M308 S1 P"temp1" Y"thermistor" T100000 B4138       ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out2" T1                                 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S330                                      ; set temperature limit for heater 1 to 280C

M308 S2 P"temp2" Y"thermistor" T100000 B4138       ; configure sensor 2 as thermistor on pin temp2
M950 H2 C"out3" T2 Q500                             ; create bed heater output on ? and map it to sensor 2
M307 H2 B1 R0.06 D60                               ; bang-bang mode for the chamber heater
M141 H2                                            ; map heated chamber to heater 2
M143 H2 S55                                         ;Set max temperature for chamber
M570 H2 P600 T20                                   ; An anomaly on heater 2 must persist for 600 seconds, and must be greater or less than 20C from the setpoint, to raise a heater fault.

; Fans
M950 F0 C"out7" Q500                               ; create fan 0 on pin out4 and set its frequency
M106 P0 S0 H-1                                     ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out8" Q500                               ; create fan 1 on pin out5 and set its frequency
M106 P1 S1 H1 T50                                  ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 D0:1 H1 F0                                   ; define tool 0
M567 P0 E1.0:1.0									;Set mix ratio for tool 0
G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C

M563 P1 D0:2 H1 F0                                   ; define tool 1
M567 P0 E1.0:1.0									;set mix ratio for tool 1
G10 P1 R0 S0										; set initial tool 1 active and standby temperatures to 0C
G10 P1 X0 Y0 Z0

;Filament Flow Detection
M591 D1 P7 C"0.io3.in" L7 R75:125 E15 S0
M591 D2 P7 C"0.io2.in" L7 R75:125 E15 S0
;Filament Detection
M950 J1 C"^0.io8.in"
M950 J2 C"^0.io7.in"
M950 J3 C"^0.io5.in"
M950 J4 C"^0.io4.in"
;Triggers
M581 T2 P3:4 S0 R1

; Miscellaneous
M501                                               ; load saved parameters from non-volatile memory
;M911 S12 R20 ; set voltage thresholds and actions to run on power loss
T0                                                 ; select first tool

end of the printjob:

G1 X134.587 Y243.749 E.08246
M204 P3000
; stop printing object plate.stl id:0 copy 1
G1 E-3 F2580
M107
;TYPE:Custom
; Filament-specific end gcode
echo "Print Finished1"
;M98 P"0:/macros/Machine/M_End_Gcode.g"
G91
M83
G1 E-2 F2400
G1 Z10 F600
G90
G1 X10 Y500 F6000
M104 S0
M107
M140 S0
echo "Print Finished2"
M2
M73 P100 R0

I commented out some parts and macro calls in the slicer.
neither of the echoes shown up in console.
both the end.g, start.g files are empty
If anyone has an idea im happy to hear

droftarts

@vBence There were some reports of print jobs not completing, but generally these were fixed in 3.5.0-rc2, see https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-RC#reprapfirmware-350-rc2-changes-since-rc1.

The file position of an executing job reported in the object model was sometimes incorrect immediately after a macro invoked by the job completed (issue 901)
...
SD card jobs sometimes didn't quite complete (issue 899)

Can you send M122 in the console and post the response?
Can you update to the latest bug fix version here and see if you still have this problem? https://www.dropbox.com/scl/fo/wrp6hvr39vjxjlep89p5x/h?rlkey=hzka49sxnsqjpwsvy46m26ms0&dl=0

Ian

soare0

I had one of these too, even if on rc3. I failed to get M122, maybe I will know more soon, but it was my first anyway. F,,,d my head and some of the print (at least is usable).
It is useful to have some anticrash sensor. I have one, but it was not enabled, and this was the result at 3am.
I found an error in z-height macro, wich I do not know how could have appear,
and also I ran a sound at part finish, both situation using a M98 to call some macro/file - do not know if related though.
The message in M122 (wich I had it but I lost it was that the printer could not home on X and Y, after print finishing). Still, why go down on Z, have no ideea, only if I will encounter this again maybe...

vBence

@droftarts I did not send the M122 gcode after the crash, sadly i wasn't there, as soon as it appears again i can send one, also it needs a bit of repair since it broke the probes holder and the fanduct for the head. I check the new firmware with it. and also test it on my personal printer.

mikeabuilder

You refer to end.g being empty. Did you mean stop.g? That is the file (in the sys directory) that gets called when a print is finished.

The behavior you describe sounds like the fw is ignoring the G91 command. This is a long-shot, but maybe there's an un-printable character after the G91, making it unrecognized by RRF and skipped.

vBence

@mikeabuilder Yes i meant the stop.g my bad
For the ignoring G91 would sound logical on the Z move, but not for the XY move with it. It does it more like if it would be returning from a pause in the start of the job but the printing is already finished.
I checked the gcode and there's no character after the commands except the normal "LF" same as in the rest of the gcode
I'll update the printer's firmware soon and do some testing if the issue would appear again

vBence

@droftarts Good news I updated to the version you sent here, and did a few prints with pauses and the issue did not came back. Also one other bug seems to went away where the z probe false triggers or not activates at all.