crashes when I run mesh bed compensation

sg2020

I can now home all of the axis. Thank you guys for helping with that. The next problem is, when I run Mesh bed compensation it will move to the origin and crash.
refference
Re: looking for an example of rrf3.2.2 corexy with bltouch config

; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Jun 06 2021 18:17:52 GMT-0700 (Pacific Daylight Time)

; General preferences
G90                                            ; send absolute coordinates...
M83                                            ; ...but relative extruder moves
M550 P"My Printer"                             ; set printer name
M669 K1                                        ; select CoreXY mode
M564 S0 H0                                     ; allow movement outside of boundry, before homing

; Network
M552 S1                                        ; enable network
M586 P0 S1                                     ; enable HTTP
M586 P1 S0                                     ; disable FTP
M586 P2 S0                                     ; disable Telnet

; Drives
M569 P0 S0                                     ; physical drive 0 goes backwards
M569 P1 S1                                     ; physical drive 1 goes forwards
M569 P2 S1                                     ; physical drive 2 goes forwards
M569 P3 S0                                     ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3                               ; set drive mapping
M350 X32 Y32 I0                                ; configure microstepping without interpolation
M350 Z16 E16 I1                                ; configure microstepping with interpolation
M350 X32 Y32 Z16 E16 I1                        ; Configure microstepping with interpolation
M92 X160.00 Y160.00 Z3230.00 E820.00           ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00            ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00        ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00            ; set accelerations (mm/s^2)
M906 X1600 Y1600 Z1500 E800 I30                ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                        ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                               ; set axis minima
M208 X550 Y330 Z400 S0                         ; set axis maxima

; Endstops
M574 X2 S1 P"xstop"                            ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                            ; configure active-high endstop for high end on Y via pin ystop
M574 Z1 S2                                     ; configure Z-probe endstop for low end on Z

; Z-Probe

M558 P9 C"^zprobe.in" H2 F500 T8000 A1		    ; set Z probe type to bltouch and the dive height + speeds
M950 S0 C"exp.heater3"							; create servo pin 0 for BLTouch
G31 P500 X-6.5 Y-27 Z1.88                           ; set Z probe trigger value, offset and trigger height 1.88
M557 X15:500 Y15:330 S50                       ; define mesh grid
M280 P0 S10 ; send control signal to BLTouch through servo/gpio 0

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                          ; create bed heater output on bedheat 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 S120                                   ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4092  ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                           ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                               ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                   ; set temperature limit for heater 1 to 280C

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

; Tools
M563 P0 D0 H1 F0                               ; define 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

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600                              ; enable support for PanelDue





; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Jun 06 2021 18:17:53 GMT-0700 (Pacific Daylight Time)
G91                      ; relative positioning
G1 H2 Z5 F6000           ; Lift z relative to current position

G1 H1 X-555 F3000         ; home X axis
G1 X15 F3000
G1 H1 X-30 F3000
G1 X15 F3000

G1 H1 Y-335              ; home Y axis
G1 Y15 F3000
G1 H1 Y-30 F3000
G1 Y15 F3000
;G90                      ; absolute positioning is BAD REALLY REALLY BAD IT WILL CRASH!!!

G1 X290 Y160 F3000     ; go to center of bed, probe point and home Z
G30                    ; home Z by probing the bed






; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Jun 06 2021 18:17:53 GMT-0700 (Pacific Daylight Time)
G91              ; relative positioning
G1 H2 Z5 F6000   ; lift Z relative to current position
G1 H1 X-555 F600 ; move quickly to X axis endstop and stop there (first pass)
G1 X15 F600    ; go back a few mm
G1 H1 X-30 F600  ; move slowly to X axis endstop once more (second pass)
G1 X15 F600    ; go back a few mm
G1 H2 Z-5 F6000  ; lower Z again
G90              ; absolute positioning



; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Jun 06 2021 18:17:53 GMT-0700 (Pacific Daylight Time)
G91              ; relative positioning
G1 H2 Z5 F6000   ; lift Z relative to current position
G1 H1 Y-335 F600 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y15 F600     ; go back a few mm
G1 H1 Y-30 F600  ; move slowly to Y axis endstop once more (second pass)
G1 Y15 F600     ; go back a few mm
G1 H2 Z-5 F6000  ; lower Z again
G90              ; absolute positioning



; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Jun 06 2021 18:17:53 GMT-0700 (Pacific Daylight Time)
G91              ; relative positioning
G1 H2 Z5 F6000   ; lift Z relative to current position
;G90              ; absolute positioning
G1 X15 Y15 F600 ; go to first probe point
G30              ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
G91             ; relative positioning
G1 H2 Z5 F100      ; lift Z relative to current position
G90             ; absolute positioning

My Mesh Grid macro is simply G29 S0

Phaedrux

@sg2020 said in crashes when I run mesh bed compensation:

it will move to the origin and crash.

Can you be more detailed in what you mean here? Does the Duet crash? Does the print head crash? What does it do before it crashes?

sg2020

@phaedrux the extruder carriage moves towards the origin and physically crashes. It ignores the end stops. I was really close to the origin and wasn't expecting that to happen when I first ran the mesh bed compensation macro, which is G29, and it actually split my 9mm wide gt2 timing belt when it crashed. It was absolutely terrifying and awesome to see the belt split like that.

fcwilt

@sg2020 said in crashes when I run mesh bed compensation:

@phaedrux the extruder carriage moves towards the origin and physically crashes. It ignores the end stops. I was really close to the origin and wasn't expecting that to happen when I first ran the mesh bed compensation macro, which is G29, and it actually split my 9mm wide gt2 timing belt when it crashed. It was absolutely terrifying and awesome to see the belt split like that.

The movement commands that occur in response to executing G29 do not respect the min/max limits set in M208 because your probe is likely not where the nozzle is.

To put the probe where your grid settings require may result in the nozzle being outside the min/max limits - which may or may not be possible on the printer.

A simple way to setup your grid is to:

add the absolute value of the probe X offset to X min
subtract the absolute value of the probe X offset from X max
add the absolute value of the probe Y offset to Y min
subtract the absolute value of the probe Y offset from Y max
set your grid parameters to stay within these new min/max values

It will not probe as much of the bed as it could but it will avoid trying to exceed the limits of your printers X and Y axes.

Frederick

Phaedrux

@sg2020 said in crashes when I run mesh bed compensation:

the extruder carriage moves towards the origin and physically crashes. It ignores the end stops.

The origin is usually the front left corner of the bed, but your config indicates that the endstops are at the high end of travel, which would mean they are at the rear right corner.

; Axis Limits
M208 X0 Y0 Z0 S1                               ; set axis minima
M208 X550 Y330 Z400 S0                         ; set axis maxima
 
; Endstops
M574 X2 S1 P"xstop"                            ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                            ; configure active-high endstop for high end on Y via pin ystop

Where are your endstops physically located?
Where is your 0,0 point?

-X should move left, +X should move right
-Y should move to the front, +Y should move to the back

If it's crashing into the frame that indicates that your axis limits aren't set correctly or there is a misconfiguration of the coordinate system.

sg2020

Hmm, my endstops are physically located in the front left corner. That is my 0,0 point.
-X moves left, +X moves right
-Y moves to the front, +Y moves to the back

My homing sequence is working for x,y and z.

Are endstops supposed to be active low? should I invert it like is shows in the M574 Gcode dictonary?

"Endstop type S0 (active low switch) is no longer supported in M574 commands. Instead, use type S1 and invert the input by prefixing the pin name with '!'. Ex: M574 X1 S1 P"!xstop". Invert the input when using an NPN output inductive or capacitive sensor, or using a NO switch (not recommended, use a NC switch instead)."

Phaedrux

Post your homing files.

If your endstops are on the low end of travel, then your config is wrong, and your homing files are likely also wrong to compensate. And in this case, two wrongs make it worse.

Are endstops supposed to be active low? should I invert it like is shows in the M574 Gcode dictonary?

No I'm not talking about the S1.

M574 X2 S1 P"xstop"                            ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                            ; configure active-high endstop for high end on Y via pin ystop

Y2 X2 mean high end of axis travel. So when the endstop is triggered during homing, the position is set to the M208 maxima.

If your endstops are at the low end of travel, then they should be Y1 X1 and your homing moves should be in the negative direction.

sg2020

@phaedrux

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Jun 06 2021 18:17:53 GMT-0700 (Pacific Daylight Time)
G91                      ; relative positioning
G1 H2 Z5 F6000           ; Lift z relative to current position
 
G1 H1 X-555 F3000         ; home X axis
G1 X15 F3000
G1 H1 X-30 F3000
G1 X15 F3000
 
G1 H1 Y-335              ; home Y axis
G1 Y15 F3000
G1 H1 Y-30 F3000
G1 Y15 F3000
;G90                      ; absolute positioning is BAD REALLY REALLY BAD IT WILL CRASH!!!
 
G1 X290 Y160 F3000     ; go to center of bed, probe point and home Z
G30                    ; home Z by probing the bed
 
 
 
 
 
 
; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Jun 06 2021 18:17:53 GMT-0700 (Pacific Daylight Time)
G91              ; relative positioning
G1 H2 Z5 F6000   ; lift Z relative to current position
G1 H1 X-555 F600 ; move quickly to X axis endstop and stop there (first pass)
G1 X15 F600    ; go back a few mm
G1 H1 X-30 F600  ; move slowly to X axis endstop once more (second pass)
G1 X15 F600    ; go back a few mm
G1 H2 Z-5 F6000  ; lower Z again
G90              ; absolute positioning
 
 
 
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Jun 06 2021 18:17:53 GMT-0700 (Pacific Daylight Time)
G91              ; relative positioning
G1 H2 Z5 F6000   ; lift Z relative to current position
G1 H1 Y-335 F600 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y15 F600     ; go back a few mm
G1 H1 Y-30 F600  ; move slowly to Y axis endstop once more (second pass)
G1 Y15 F600     ; go back a few mm
G1 H2 Z-5 F6000  ; lower Z again
G90              ; absolute positioning
 
 
 
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Jun 06 2021 18:17:53 GMT-0700 (Pacific Daylight Time)
G91              ; relative positioning
G1 H2 Z5 F6000   ; lift Z relative to current position
;G90              ; absolute positioning
G1 X15 Y15 F600 ; go to first probe point
G30              ; home Z by probing the bed
 
; Uncomment the following lines to lift Z after probing
G91             ; relative positioning
G1 H2 Z5 F100      ; lift Z relative to current position
G90             ; absolute positioning

Phaedrux

Ok, so change your M574 X2 Y2 to X1 Y1.

Your homing directions are already negative so that's good.

Then make sure everything is homing correctly and then carefully check that your axis limits are accurate.

Then setup your grid as described by @fcwilt above.

sg2020

@phaedrux
Changing the X2 Y2 to X1 Y1 seems to have done the trick.

I setup the grid from fcwilt's advice.

Thanks everybody. I really appreciate it. For some reason going to RRF 2.1 to RRF 3.2.2 really confused me so thank you all for helping me get back up and running.