DWC Seems to Crash After Uploading a Print

[clegg78]

@ccs86 I've been seeing similar with DWC after going to 3.4.0. There is some real weird behavior in the UI now with resets, reconnections, crashes on saving big macros/config files, etc... Very frustrating.

[CCS86]

@clegg78 said in DWC Seems to Crash After Uploading a Print:

@ccs86 I've been seeing similar with DWC after going to 3.4.0. There is some real weird behavior in the UI now with resets, reconnections, crashes on saving big macros/config files, etc... Very frustrating.

Interesting.

I never noticed this issue before going to the release version of 3.4.0.

I tried flashing back to earlier versions of DWC, but I left RRF at 3.4.0. So, maybe there is actually an issue with RRF that is causing the DWC disconnects.

[clegg78]

@ccs86 So... I may have stumbled on something in my case today... Disabling both filament sensors (Duet rotating magnet ones, one on each print head) = no reconnections/DWC crashes.
Enabling one = some random drops.
Enabling both = Crashes galore.

I am going to be doing more testing on this.

[CCS86]

@clegg78

I'm actually using no filament sensors. Just a BL Touch.

[clegg78]

@ccs86 Interesting. I also have a BLTouch. curious what bug was introduced in 3.4.0 to cause these weird behaviors.

[CCS86]

@clegg78

Have you tried downgrading RRF? That's my next step.

[clegg78]

@ccs86 I have not. My machine is used for pretty consistent production use and the DWC thing is annoying, very annoying, but hasn't been a show stopper for it to run. And the code/config tweaks for 3.4.0 I don't want to unwind. I guess if it turns out there is no fix, I may have to go back.

[CCS86]

@Phaedrux @dc42

We might want to move this thread.

I just flashed back to RRF 3.4.0 RC1 (DWC 3.4.0 stable) and the issue vanishes.

[dc42]

@ccs86 is this still on Duet Maestro?

[CCS86]

@dc42 Yes

[dc42]

@ccs86 please provide your config.g file and any other macro files that it calls.

[CCS86]

@dc42

; Configuration file for Duet Maestro (firmware version 3)
 
 
; General preferences
G90                                                    ; absolute coordinates
M83                                                    ; relative extruder
M550 P"Maestro86"                                      ; set printer name
 
 
; Network
M552 P0.0.0.0 S1                                       ; enable network and acquire dynamic address via DHCP
M586 P0 S1                                             ; enable HTTP
M586 P1 S0                                             ; disable FTP
M586 P2 S0                                             ; disable Telnet
 
 
; Drives
M569 P0 S0                                             ; drive 0 goes backwards
M569 P1 S1                                             ; drive 1 goes forwards
M569 P2 S0                                             ; drive 2 goes backwards
M569 P3 S0                                             ; drive 3 goes backwards
 
M569 P0 D2 ;D3 V468					; X Stealthchop2 till about 10 mm/sec 
M569 P1 D2 ;D3 V468					; Y Stealthchop2 till about 10 mm/sec 
M569 P2 D3 V40 						; Z Stealthchop2 till about 46.9 mm/sec
M569 P3 D2 						; Extruder in Spreadcyle
 
M584 X1 Y0 Z2 E3                                       ; Drive mapping
M92 X160.0 Y160.0 Z401.5 E695                          ; Steps per mm
M350 X16 Y16 Z16 E16 I1                                ; Microstepping with interpolation
 
M201 X5000.00 Y5000.00 Z230.00 E2500.00                ; Max accelerations (mm/s^2)
M203 X12000.00 Y12000.00 Z2100.00 E2400.00             ; Max speeds (mm/min)
M204 P2500 T4000                                       ; Accelerations (mm/s^2)
;M205 X12 Y12 Z3 E4.5                                  ; Maximum jerk rates (mm/s)
M566 X600 Y600 Z180.0 E270 P1                          ; Maximum jerk rates (mm/min)
 
M593 P"MZV" F40.5					; Input Shaping
M572 D0 S0.032 						; Pressure Advance
 
M906 X1300 Y1300 Z1400 E490 I50                        ; Motor currents (mA) and motor idle factor
M84 S30                                                ; Idle timeout
 
; Axis Limits
M208 X0 Y0 Z0 S1                                       ; Axis minima
M208 X195 Y180 Z220 S0                                 ; Axis maxima
 
; Endstops
M574 X1 S1 P"!xstop"                                   ; Active-high endstop for low end on X via pin !xstop
M574 Y1 S1 P"!ystop"                                   ; Active-high endstop for low end on Y via pin !ystop
 
 
; Z-Probe
M574 Z1 S2                                             ; Z endstop controlled by probe
M558 P5 C"^zprobe.in" H5 F500 T6000 A1                 ; Z probe type to bltouch and the dive height + speeds
M950 S0 C"zprobe.mod"                                  ; create servo pin 0 for BLTouch
G31 P25 X20 Y-14 Z.98                                  ; Z probe trigger value, offset and trigger height
M557 X20:195 Y0:166 S18.8                              ; define mesh grid
M376 H1.5                                              ; mesh taper
 
 
;Accelerometer
M955 P0 C"twck0+twd0" R12
 
 
; Heaters
M308 S0 P"spi.cs1" Y"rtd-max31865"                     ; configure sensor 0 as a PT100 sensor in the first position on the Duet 2 daughter board connector
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 bed heater 0
M308 S1 P"e0temp" Y"pt1000" ;T100000 B4725 C7.06e-8    ; configure sensor 1 as PT1000 on pin e0temp
M950 H1 C"e0heat" T1                                   ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S243                                           ; set temperature limit for nozzle heater 1
M307 H1 B0 S1.00                                       ; disable bang-bang mode for heater and set PWM limit
M308 S2 Y"drivers" A"DRIVERS"                          ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
M308 S3 Y"mcu-temp" A"MCU"                             ; configure sensor 3 as thermistor on pin e1temp for left stepper
 
 
 
; Heater model parameters
;Bed
;M307 H0 R0.194 C896.8 D2.07 S1.00
;M307 H0 R0.190 K0.196:0.000 D2.03 E1.35 S1.00 B0
M307 H0 R0.190 K0.174:0.000 D1.95 E1.35 S1.00 B0
 
;Hotend
;M307 H1 R2.523 C231.0:134.5 D5.90 S1.00 V24.3
;M307 H1 R2.324 K0.389:0.146 D3.76 E1.35 S1.00 B0 V24.3
M307 H1 R2.459 K0.398:0.160 D3.91 E1.35 S1.00 B0 V24.3
 
 
; 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 B1.5 X180                            ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" ;Q800                                  ; create fan 2 on pin fan2 and set its frequency                        
M106 P2 H1:2:3 L1 X1 T53                               ; set fan 2 value
 
 
; Tools
M563 P0 S"E0" 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
 
M595 P40
 
T0                                                     ; select first tool

[CCS86]

Do you need anything else @dc42 ?

[CCS86]

@dc42

Does 3.4.1 have any potential improvements for this issue?

[Phaedrux]

@ccs86 said in DWC Seems to Crash After Uploading a Print:

Does 3.4.1 have any potential improvements for this issue?

I'm not sure, but worth testing with the latest code base regardless.

[CCS86]

Bug seems to be gone in 3.4.1 RC1

[dc42]

@ccs86 said in DWC Seems to Crash After Uploading a Print:

Bug seems to be gone in 3.4.1 RC1

Thanks for confirming this. Based on your report and on another one on a Duet 2, I suspected that in some configurations parts of the object model might be getting too large to fit in the available buffer space to send to DWC. So in 3.4.1 I increased the buffer space on Duet 2 and Maestro, and shrunk the object model data a little.