3.5.0rc4 - G29 crashes nozzle into bed after first probe point

omtek

Last night I upgraded my Duet 3 Mini 5+ and RRF36 toolboard to 3.5.0rc4 (using SBC mode; got the RRF36 firmware from the teamgloomy repo. There's also a CannedERCF board running 3.5.0rc4. It wasn't involved here, but I'm using it for the CAN-FD passthrough and ERCFv2).

I went to start a print. As usual, start.g ran, then the slicer start gcode ran. Here I'm passing the "only probe where printing" parameters to mesh.g found here. After the first probe point, the nozzle crashed into the bed. I hit the stop button on the PanelDue and reset everything. I didn't notice at the time but I had bent and cross-threaded the nozzle on my E3D Revo hotend.

After resetting the printer, everything came back up again. After homing XYZ and performing a G32, I ran a G29 with the default mesh settings. Printer picks up the probe and moves to the first probe point, probes one time, the bed raises for the second, slower probe (I use F300:120 with M558), and instead of raising the bed again to move to the second point, the nozzle crashes into the bed, and without raising the bed, attempts to move to the second probe point.

If the first crash didn't do my nozzle in, then the second one definitely finished it off.

I downgraded to 3.5.0rc3 on both the main board and the RRF36 and reset, After homing everything, then G32 followed by a G29, and was able to generate a mesh without issue.

heightmap.csv

Rat Rig V-Core 3.1
Duet 3 Mini 5+
RRF36 toolboard
KlickyPCB on EVA3

relevant configuration files below:

<<< snip >>>
I had a much longer post prepared with all the relevant configuration files included, but the forum didn't like that it was so long. So I'll supply the necessary configuration files as requested.

I also made sure my github has up-to-date copies of everything.

M122 - Duet3Mini5+

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.3 (2024-01-24 17:56:48) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: NTK2Z-J196U-D65J0-40KMN-1V03Z-ZJMGF
Used output buffers: 1 of 40 (31 max)
=== RTOS ===
Static ram: 103200
Dynamic ram: 109324 of which 0 recycled
Never used RAM 25892, free system stack 140 words
Tasks: SBC(2,ready,8.2%,427) HEAT(3,nWait 6,0.1%,334) Move(4,nWait 6,0.0%,243) CanReceiv(6,nWait 1,0.3%,794) CanSender(5,nWait 7,0.0%,330) CanClock(7,delaying,0.0%,349) TMC(4,nWait 6,6.2%,68) MAIN(2,running,81.3%,764) IDLE(0,ready,0.2%,30) AIN(4,delaying,3.6%,260), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 02:03:44 ago, cause: software
Last software reset at 2024-04-16 13:36, reason: User, Gcodes spinning, available RAM 27908, slot 1
Software reset code 0x6003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00489000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 7425043, completed 7425043, timed out 0, errs 0
MCU temperature: min 27.5, current 30.9, max 42.8
Supply voltage: min 24.3, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/24, heap memory allocated/used/recyclable 2048/516/40, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 29, reads 19589, writes 25, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 25, reads 19589, writes 25, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 25, reads 19588, writes 25, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 26, reads 19586, writes 27, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 29, reads 19588, writes 26, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 131, reads 19603, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 131, reads 19603, writes 10, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2024-04-16 15:40:22
Cache data hit count 4294967295
Slowest loop: 194.42ms; fastest: 0.11ms
=== Storage ===
Free file entries: 20
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 6, maxWait 5656544ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 285, completed 285, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], CDDA state -1
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC* is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000007
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
check 0 clear 0
Extruder 1 sensor: no data received
=== CAN ===
Messages queued 67149, received 212125, lost 0, errs 0, boc 0
Longest wait 3ms for reply type 6013, peak Tx sync delay 270, free buffers 26 (min 25), ts 37125/37124/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 22790/22790
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0d600
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.0-rc.3 (2024-01-26 12:34:19)
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 38.40, max time between full transfers: 61.5ms, max pin wait times: 66.6ms/9.6ms
Codes per second: 0.04
Maximum length of RX/TX data transfers: 4432/820

M122 - RRF36

m122 b20
Diagnostics for board 20:
Duet FLY36RRF firmware version 3.5.0-rc.3+101 (2024-01-28 17:59:13)
Bootloader ID: 
All averaging filters OK
Never used RAM 196592, free system stack 436 words
Tasks: Move(3,nWait 7,0.0%,133) HEAT(2,nWait 6,0.6%,113) CanAsync(5,nWait 4,0.0%,57) CanRecv(3,nWait 1,0.0%,351) CanClock(5,nWait 1,0.2%,335) ACCEL(3,nWait 6,0.0%,53) TMC(2,nWait 6,6.0%,53) MAIN(1,running,86.6%,430) IDLE(0,ready,0.0%,27) USBD(2,blocked,0.0%,151) AIN(2,delaying,6.6%,248), total 100.0%
Owned mutexes:
Last reset 02:03:48 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 671.6 steps/mm, standstill, SG min 4, read errors 0, write errors 1, ifcnt 141, reads 43899, writes 17, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
Peak sync jitter -17/21, peak Rx sync delay 435, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 23.6, current 23.6, max 23.7
MCU temperature: min 35.6C, current 36.0C, max 37.0C
Last sensors broadcast 0x00000002 found 1 143 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 298133, send timeouts 0, received 67147, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00

I do not have an M122 from running 3.5.0rc4. I'm a little wary about going back, but I will if needed.

Let me know if there is anything other information I can provide.

omtek

adding configuration:

config.g

;=== initialize variables ===;
M98 P"0:/sys/init.g"
;=== discard if necessary ===;

;=== configuration - initial networking setup ===;
M586 P0 S1                                                ;; enable http, disable ftp, disable telnet, set printer name, wait 5s for expansion boards
M586 P1 S0
M586 P2 S0
G4 S5
M550 P"legionXY"                                          ;; in SBC mode, M550 goes in dsf-config.g, not config.g


;=== configuration -  PanelDue init ===;
M575 P1 S1 B115200

;=== configuration - printer ===;
G90                                                       ;; absolute coordinates, relative extruder moves
M83
M669 K1                                                   ;; Kinematics type: 1 = CoreXY

;=== configuration - drive ===;
M569 P0.0 S0 D2                                           ;; Z-axis motors, 0.driver0,0.driver1,0.driver2
M569 P0.1 S0 D2
M569 P0.2 S0 D2
M569 P0.3 S1 D2                                           ;; Left and right motors (X- and Y- axis), 0.driver3,0.driver4
M569 P0.4 S1 D2
M569 P20.0 S1 D2                                          ;; Extruder, RRF36.driver0

;=== configuration - drive - axis mapping ===;
M584 X0.3 Y0.4 Z0.1:0.0:0.2 E20.0                         ;;  map E-axis here as toolboard will be connected

;=== configuration - drive - microstepping ===;
M350 X16 Y16 Z16 I1

;=== configuration - drive - steps/mm, current, idle timeout ===;
M92 X80 Y80 Z800                                          ;; set steps/mm, current (mA), idle timeout
M906 X1600 Y1600 Z1600 I30
M84 S30                                                   ;; set idle hold 30s

;=== configuration - drive - speed, acceeleration, jerk ===;
M98 P"0:/sys/setMaxSpeed.g"                               ;; set all the max speeds below as these are adjusted during home moves so we only want to adjust in one spot

;=== configuration - axis - min/max ===;
M208 X0 Y0 Z0 S1
M208 X310 Y300 Z300 S0

;=== configuration - axis - endstops ===;
M574 X1 S1 P"20.io2.in"                                   ;; configure active high (S1) X endstop at X- (X1) on RRF36.io2.in (20.io.in)
M574 Y2 S1 P"0.io2.in"                                    ;; configure Y active high (S1) endstop at Y+ (Y2) on duet.io2.in (0.io2.in)
M574 Z1 S2                                                ;; configure Z-probe (S2) endstop at low end (Z1)

;=== configuration - axis - z-probe ===;
M558 P8 C"^20.io0.in" H5:1 F300:120 T6000 A20 B0          ;; klicky pcb probe installed on RRF36.io0.in (20.io0.in)
M98 P"0:/sys/setBuildPlate.g"                             ;; see setBuildPlate.g for Z probe trigger value, offset, trigger height

;=== configuration - axis - mesh compensation and bed dismensions ===;
M98 P"0:/sys/setDefaultProbePoints.g"                     ;; define mesh grid with allowance for mesh generation on printed area only
if !exists(global.Bed_Center_X)                           ;; calculate bed center, insert into object model
	global Bed_Center_X = floor(move.axes[0].max / 2)
if !exists(global.Bed_Center_Y)
	global Bed_Center_Y = floor(move.axes[1].max  / 2)

;=== configuration - axis - lead screw position ===;
M671 X-4.5:150:304.5 Y-4.52:305:-4.52 S5

;=== configuration - sensor - bed heater & thermistor  ===;
M308 S0 P"0.temp0" Y"thermistor" T100000 B3950 A"Bed"     ;; create sensor S0 on duet.temp0 named "Bed"
M950 H0 C"0.out0" T0 Q11                                  ;; create heater (H0) for bed
M307 H0 B0 S1.00                                          ;; on bed H0 disable bang-bang mode and set PWM limit
M140 H0                                                   ;; map heated bed to heater 0 (H0)
M143 H0 S120                                              ;; set heater H0 temperature limit to 120C

;=== !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ===;
;; run bed PID tune using code below
;;; ;;; H0 = heater 0, or bed
;;; ;;; S = temperature in C (90C)
;;; ; M303 H0 S90
;;;
;;; replace M307 below with results from M303
;;; M307 may have a Vnnn included with it
;;;  if you're using mains (AC) bed heater on your bed, omit it
;=== !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ===;
M307 H0 R0.480 K0.256:0.000 D2.03 E1.35 S1.00 B0          ;; this is my M307, find your own

;=== configuration - sensor - chamber monitoring ===;
M308 S5 P"0.io4.out+0.io4.in" Y"dht22" A"Chamber"         ;; DHT22 setup
M308 S8 P"S5.1" Y"dht-humidity" A"Humidity[%]"
M308 S11 Y"mcu-temp" A"MCU"                               ;; MCU temperature, with offset
M912 P0 S-1.2

;=== configuration - LEDs, chamber ===;
M950 P0 C"0.out5" Q1000                                   ;; configure Dayspring LEDs P0 on duet.out5 (0.out5)

;=== configuration - overrides ===;
;M501                                                     ;; config-override.g should remain empty      

;=== configuration - gizmo1 ===;
M98 P"0:/sys/gizmo1.g"
;; housekeeping
M568 P0 R0 S0 A0                                          ;; turn tool0 heater off
M140 S-273.1                                              ;; turn bed off
T0 P0                                                     ;; select T0, don't run any toolchange macros
;=== configuration ===;

setMaxSpeed.g

;=== configuration - drive - current and idle factor ===;
M906 X1600 Y1600 Z1600 I30                                                            ;; set motor currents and motor idle factor in per cent, December 2023
M913 X100 Y100 Z100                                                                   ;; ensure motors are at 100% current after homing

;=== configuration - drive - jerk ===;
M205 X5.00 Y5.00 Z0.4 P1                                                              ;; set maximum instantaneous speed changes (mm/min) and jerk policy 

;=== configuration - drive - speed ===;                                             
M203 X18000.00 Y18000.00 Z900.00                                                      ;; set maximum speeds (mm/min) 

;=== configuration - drive - acceleration ===;
M201 X5000.00 Y5000.00 Z100.00                                                        ;; set accelerations (mm/s^2), orbiter v2
M204 P2500 T5000                                                                      ;; Set printing and travel acceleration (mm/s^2)

setBuildPlate.g

;=== configuration - bed - mesh compensation ===;
;M376 H3                                                ;; fade mesh compensation at 3mm

;=== configuration - bed - z-probe offset ===;
;;set in config.g, but change here // old offset: G31 K0 P500 X-27.8 Y-12.0 Z1.55
G31 P500 X-23.34 Y-20.49 Z1.937                         ;; klickyPCB with stock switch

setDefaultProbePoints.g

M557 X15:275 Y15:275 P7

gizmo1.g

;; gizmoN.g is the comprehensive definition of a tool (extruder, hotend, heater, thermisistor, filament monitoring, input shaping, tool and part cooling fans)
;; includes hotend (thermistor, heater), fan (tool, part), extruder (axis, microstepping), tool assignment and offset

;=== gizmo1 - fan ===;
M950 F1 C"!0.out4+0.out4.tach"                                                ;; create fan F1 named "4028" with duet.out4+duet.out4.tach (0.out4+0.out4.tach)
M106 P1 C"4028" S0 H-1

;=== gizmo1 - hotend thermistor ===;

M308 S1 P"20.temp0" Y"thermistor" T100000 B4725 C7.060000e-8 A"e3drevo"       ;; configure sensor 1 (S1) on pin RRF36.temp0 (20.temp0) as thermistor
M950 H1 C"20.out0" T1                                                         ;; create heater output (H1) on RRF36.out0 (20.out0) and map to sensor 1 (T1)
M307 H1 B0 S1.00                                                              ;; set PWM limit (S1.00)
M563 P0 S"revo" D0 H1 F1                                                      ;; define tool0 (T0)
                                                                              ;; assign fan F1, extruder drive D0 (E0) and heater H1 to tool T0 named "revo"
G10 P0 X0 Y0 Z0                                                               ;; set axis offsets, max temperature, initial temperature
M143 H1 S280
G10 P0 R0 S0

;=== gizmo1 - fan ===;
M950 F1 C"!0.out4+0.out4.tach"                                                ;; create fan F1 named "4028" with duet.out4+duet.out4.tach (0.out4+0.out4.tach)
M106 P1 C"4028" S0 H-1

;=== gizmo1 - hotend thermistor ===;
M308 S1 P"20.temp0" Y"thermistor" T100000 B4725 C7.060000e-8 A"e3drevo"       ;; configure sensor 1 (S1) on pin RRF36.temp0 (20.temp0) as thermistor
M950 H1 C"20.out0" T1                                                         ;; create heater output (H1) on RRF36.out0 (20.out0) and map to sensor 1 (T1)
M307 H1 B0 S1.00                                                              ;; set PWM limit (S1.00)
M563 P0 S"revo" D0 H1 F1                                                      ;; define tool0 (T0)
                                                                              ;; assign fan F1, extruder drive D0 (E0) and heater H1 to tool T0 named "revo"
G10 P0 X0 Y0 Z0                                                               ;; set axis offsets, max temperature, initial temperature
M143 H1 S290
G10 P0 R0 S0

;=== !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ===;
;; run hotend PID tune!! using code below
;;; T0 = PID tune tool0
;;; S210 = temperature in C (210C)
;;; F0.45 = Fan PWM value; 0.45 = 45%
;;; ; M303 T0 S210 F0.45
;;; replace M307 below with results from M303
;=== !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ===;
M307 H1 R3.611 K0.702:0.541 D1.95 E1.35 S1.00 B0 V23.5                        ;; this is my M307, find your own

;=== gizmo1 - fan - hotend ===;
M950 F0 C"20.out2" Q250                                                       ;; create fan 0 (F0) on pin RRF.out2 (20.out2)
M106 P0 C"tool" S0 H1 T45 L255                                                ;; set fan 0 (P0) to thermostatic control (45C), full-speed (L255) named "tool"

;=== gizmo1 - extruder ===;
                                                                              ;; Orbiter v2 with LDO motor
M906 E1200 I10                                                                ;; set extruder motor current and idle factor
M350 E16 I1                                                                   ;; set microstepping to 16 with interpolation
M92 E671.64                                                                   ;; set extruder steps per mm
M203 E7200                                                                    ;; set max speed, jerk, acceleration
M205 E5.0
M201 E3000

T0 P0                                                                         ;; select T0, don't run toolchange macro

M703                                                                          ;; load filament specific gcode
                                                                              ;; I keep filament-specific PID tuning, retraction, and pressure advance 
                                                                              ;; settings here.
                                                                              
;=== gizmo1 - options ===;
M955 P20.0 I12                                                                ;; accelerometer on RRF36
M950 E0 C"20.rgbled" T2 U2 Q3000000                                           ;; configure toolhead LED E0 on FLY36.rgbled (20.rgbled)
;M98 P"0:/sys/setFilamentMonitor.g"                                           ;; filament monitor
;M98 P"0:/sys/setInputShaping.g"                                              ;; input shaping parameters

mesh.g

; perform mesh compensation only where printing

M98 P"0:/sys/setDefaultProbePoints.g" ; reset probe points again, just in case

if (exists(param.A) && exists(param.B) && exists(param.C) && exists(param.D) && exists(param.N))
	M557 X{max(move.compensation.probeGrid.mins[0],param.A),min(move.compensation.probeGrid.maxs[0],param.B)} Y{max(move.compensation.probeGrid.mins[1],param.C),min(move.compensation.probeGrid.maxs[1] ,param.D)} S{param.N}
	if result != 0
		abort "Invalid M557 parameters"

G29 S0

gloomyandy

@omtek What sort of probe are you using? Is this the M588 that will be active during probing?

M558 P8 C"^20.io0.in" H5:1 F300:120 T6000 A20 B0

A height of 1 seems very close to the bed if using a probe that extends below the nozzle. Though having said that I'm not sure why that would work with rc.3 and not rc.4 unless rc.4 fixed something that means setting two probe heights works when perhaps it didn't in rc.3? Interestingly the docs do not document having two different dive heights (one for @droftarts perhaps).

droftarts

@omtek What is in the macro that is called at the beginning of config.g? ie M98 P"0:/sys/init.g"

If you are using a lot of variables, it's possible that the stack space used per level of expression nesting has increased. There was some new code to handle this between rc3 and rc4, but @dc42 has established that the new code to handle arrays does increase the stack space used in one of the commonly-used functions by quite a lot, even when arrays are not used. This has been fixed, but there's currently no release to test until 3.5.0 is released.

This is a similar issue to this thread: https://forum.duet3d.com/topic/35462/long-standing-macro-not-working-only-on-3-5rc4-and-mini5

Ian

droftarts

@omtek Looking through the rest of your config.g and associated files, the only other thing I would note is that your Z axis jerk and acceleration seem high for the high number of steps per mm of the Z axis. It is configured as:

M92 X80 Y80 Z800                                          ;; set steps/mm, current (mA), idle timeout
...
M205 X5.00 Y5.00 Z0.4 P1                                                              ;; set maximum instantaneous speed changes (mm/min) and jerk policy 
M203 X18000.00 Y18000.00 Z900.00                                                      ;; set maximum speeds (mm/min) 
M201 X5000.00 Y5000.00 Z100.00                                                        ;; set accelerations (mm/s^2), orbiter v2

I don't think there were any changes between rc3 and rc4 to the motion code (see https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-RC#reprapfirmware-350-rc4-changes-since-rc3), so I'm not sure why it works in rc3 and not rc4. If you could update to rc4 again, and check that the Z axis can move in the positive direction at the maximum speed, that might narrow down where this problem is coming from.

Ian

omtek

@gloomyandy I'm using a KlickyPCB. I don't remember when I added the second dive height (I think I was still using an inductive probe at the time) and I'm not sure why it's not documented but probing is noticeably faster when using H5:1 due to the decreased travel time.

omtek

@droftarts

init.g

if !exists(global.RunDaemon)
	global RunDaemon = true 

if !exists(global.BedPreheatTemp)  
	global BedPreheatTemp = 60
	
if !exists(global.Cancelled)  ; global variable for exiting out of loops
	global Cancelled = false 

if !exists(global.filamentDistance)
	global filamentDistance = 0

if !exists(global.filamentFeedSpeed)
	global filamentFeedSpeed = 180

if !exists(global.filamentRetractSpeed)
	global filamentRetractSpeed = 1800

It sets up some global variables I had hoped to use for universal filament load/unload but haven't fully implemented. I was planning on using them to make dropping a configuration for a ERCFv2 on top of everything a little more seamless.

I have another file of variables that gets loaded along with the ERCFv2 configuration. They were present in the OM during the first nozzle crash, but not during subsequent crashes.

ercf_init.g


;; global declarations for ERCF
;; some defaults established
;; and variables set and loaded

if !exists(global.ercf_settings_loaded)
	;=== configuration - general settings ===;
	global ercf_bowden_length = 630                              ;; distance until the filaent is at the end
	global ercf_extruder_load_length = 50                        ;; Orbiter 2.0 on EVA3 with E3D Revo Voron hotend
	;=== configuration - blinky pulse count ===;
	global ercf_pulse_count = 0
	global ercf_last_count = 0
	;=== configuration - selector ===;
	global ercf_selector_loaded = 0
	global ercf_selector_engaged = 0	
    ;global ercf_selector_array = {0,22,43,69.2,90.7,112,112,112}
	global ercf_selector_0 = 0
	global ercf_selector_1 = 24
	global ercf_selector_2 = 47
	global ercf_selector_3 = 70
	global ercf_selector_4 = 93
	global ercf_selector_5 = 116
	global ercf_selector_6 = 139
	global ercf_selector_7 = 162
	global ercf_selector_offset = 3.700

droftarts

@omtek It may be the stack space issue. @gloomyandy suggested @Nurgelrot rewrite his macro without so much nesting, which worked, so that may solve your problem. See their conversation on Discord here https://discord.com/channels/711873626080804914/930484450389786655/1229517039174025277
Or wait and see if the changes made post-rc4 (this one, I believe https://github.com/Duet3D/RepRapFirmware/commit/e7cc658546652d32756b1c5b05c1cf923f234edb) fix your problem when 3.5.0 stable is released (very soon!).

Sorry for the damage to your machine. We try very hard NOT to break things!

Ian

0

dc42 committed to Duet3D/RepRapFirmware

Reduce stack usage of ParseExpectKet when no array indices are used

omtek

@droftarts

I updated back to 3.5.0rc4 and tested the Z-motion again. Bed was able to move fully throughout it's range and I didn't observe any knocking or binding. DWC reported the speed capped out at 15mm/sec during the moves.

I double checked the original settings and my Z-axis jerk was a bit higher than the RatRig default (their M205 was Z0.1, mine was Z0.4). I've made the necessary change to my configuration.

Since I was back on 3.5.0rc4, I captured video of the occurrence, and the different behavior between H5 and H5:1.

This is with a single dive height specified in M558 (H5)

https://www.youtube.com/watch?v=SRwe0mazqtQ

This is with M558 H5:1. This is what bent the nozzle and scored the PEI.

https://www.youtube.com/watch?v=r0-zQG1yvtM

oliof

@omtek just to make sure, did you do true bed leveling before the mesh?

omtek

@oliof Correct, during these tests/videos I ran G32 followed by a G29.

During a print, my start.g contains the G32, while the G29 is handled by the slicer start g-code calling mesh.g directly and passing the parameters for mesh generation only where printing.

start.g

T0         ; ensure the tool is selected

M220 S100  ; set speed factor back to 100% in case it was changed
M221 S100  ; set extrusion factor back to 100% in case it was changed
M290 R0 S0 ; clear any baby-stepping
M106 P0 S0 ; turn layer fan off if it is on
M400       ; finish all moves, clear the buffer

M98 P"0:/sys/setBuildPlate.g" ; pull in build plate parameters 
							; heightmap, probe height, etc.

; chamber LEDs on
M98 P"0:/macros/LEDs/led_on.g"
		
G32		   ; 3-point bed leveling

;M501	   ; load config-override.g
M703	   ; load filament-specific config.g


M98 P"0:/sys/setInputShaping.g" ; pull in input shaping parameters

G90        ; absolute Positioning
M83        ; extruder relative mode

;=== DuetLapse3 control ===;
;M291 P"DuetLapse3.start" S2
;M292
;G4 S10
    
M98 P"0:/sys/setDefaultProbePoints.g" ; reset probe points, just in case

;=== slicer start code ===;

slicer start g-code

M98 P"0:/sys/mesh.g" A{first_layer_print_min[0]} B{first_layer_print_max[0]} C{first_layer_print_min[1]} D{first_layer_print_max[1]} N20 ; set N to your desired distance between points
G29 S1 ; load small mesh
M140 S[first_layer_bed_temperature] ; set bed temp
M104 S[first_layer_temperature] ; set extruder temp
G0 X30 Y30 Z0.2 F6000 ; move ahead of prime line position and wait for temp
G92 E0.0
M190 S[first_layer_bed_temperature] ; wait for bed temp
M109 S[first_layer_temperature] ; wait for extruder temp
G0 X5 E10.0 Z0.2 F6000 ; move to prime line position and advance filament 10mm to fill heat break
G1 X60.0 E9.0 F1000.0 ; intro line
G1 X140.0 E10 F1000.0 ; intro line
G92 E0.0
G0 Z1 F1000 ; dab
M106 S0

gloomyandy

@omtek I'm a bit confused both of those videos show the probe getting pretty mangled. I assume neither is correct? Are both of those with 3.5.0rc4?

omtek

@gloomyandy Both videos are taken with 3.5.0rc4.

The first video was taken with M558 H5 while the second video was taken with M558 H5:1.

The second video depicts the nozzle crash as I initially experienced it; after the second lower & slower probe point, the bed is driven into the nozzle instead of raising. Then it tries to move to the second point.

In the first video, I adjusted M558 so only one dive height (H5) is used. There you see the bed being driven into the probe, completely ignoring that the switch was triggered.

droftarts

@omtek can you try the 3.5.0 release? https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.0

Ian

omtek

@droftarts I can, however I should probably wait for Team Gloomy to finalize their 3.5.0 release for the RRF36 board before testing anything.

gloomyandy

@omtek In the above videos what did you do to run the G29? Was it simply G29 from the console or did you run the mesh.g with parameters?

I don't think there are any changes in the expansion board code so you should be fine to go ahead and use the rc.4 version of the RRF36 firmware for testing with 3.5.0. DWC will complain about mismatched versions but I think it should work fine.

It might be worth reducing the z motor current to try and avoid any further damage.

omtek

@gloomyandy Both videos I ran G29 from DWC (after homing XYZ, and running G32, also from the DWC).

G32 runs with out issue, too. Usually takes a few tries, though.

It might be worth reducing the z motor current to try and avoid any further damage.

An excellent idea. I've modified the M913 in my config accordingly.

Nurgelrot

I was just able to reproduce this issues using a detachable prob (Klicky) Homing works G32 works. manually running M401/402 to get and store the porbe works but when issuing G29 it error with 4/17/2024, 8:26:56 PM g29 Error: G1: Probe already triggered before probing move started and all hell breaks loose if you dont hit estop fast.

This was with 3.5.rc4 on an Octopusprov1.0 and a 1LC toolboard. So it dosen't seem to be port/board specific. Let me know what data you need. This is one of my best printing units so I'm loth to do too much damage to it testing but happy to help out as much as I can.

omtek

@gloomyandy I just finished updating what I could to 3.5.0. ~~(still need to compile firmware for the CannedERCF board, but I think it's ok doing CAN passthrough~~compiled tonight).

After making sure motors were running at 80%, homing XYZ, then ran G32 (almost got it in two passes) followed by G29 (using the buttons in DWC), the KlickyPCB is picked up and moved to the first probe point, and as soon as the Klicky is triggered the bed drives itself into the probe. I had my finger on the E-Stop this time so I wasn't able to see if it attempted to move to the second probe point.

gloomyandy

@omtek So basically it does the same thing with 3.5.0 as it was doing before?