DWC Seems to Crash After Uploading a Print

Phaedrux

Does it also crash if you upload from another slicer like PrusaSlicer, or an older version of SuperSlicer?

Does it upload successfully in DWC itself?

CCS86

This actually seems to be a more global DWC issue. I just tried to download a variety of files from DWC and it keeps crashing. The largest file I was able to download was around 6MB. Even a 10MB file causes a connection interruption and aborted download:

4/17/2022, 10:12:08 AM	Connection established
4/17/2022, 10:12:08 AM	Failed to download Vent Lips.gcode
Could not complete action because the connection has been terminated
4/17/2022, 10:12:08 AM	Connection interrupted, attempting to reconnect...
Network error
4/17/2022, 10:11:51 AM	Download of Drain Adapter.gcode successful after 6s
4/17/2022, 10:11:36 AM	Connection established
4/17/2022, 10:11:35 AM	Failed to download Outlet Nozzle3.gcode
Could not complete action because the connection has been terminated
4/17/2022, 10:11:35 AM	Connection interrupted, attempting to reconnect...
Network error
4/17/2022, 10:11:10 AM	Connection established
4/17/2022, 10:11:10 AM	Failed to download Outlet Nozzle3c.gcode
Could not complete action because the connection has been terminated
4/17/2022, 10:11:10 AM	Connection interrupted, attempting to reconnect...
Network error
4/17/2022, 10:10:49 AM	Connection established
4/17/2022, 10:10:48 AM	Failed to download Outlet Nozzle3c.gcode
Could not complete action because the connection has been terminated

Uploading a lager file via DWC causes the same issue.

Phaedrux

Do you have another SD card you can try?

CCS86

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

Do you have another SD card you can try?

This doesn't seem like an SD card issue.

I tried uploading a 5.2MB file repeatedly. Each time it gave me this error and DWC had to reconnect:

Failed to upload Loctite4.gcode
Could not complete action because the connection has been terminated

But, these files were still present in the jobs folder. So, I downloaded the files and they are perfect matches to the original. So, there is no actual failure to write and read from the card, and no corruption.

This seems like purely a network connectivity glitch in DWC.

Can I gather more detailed logs?

Phaedrux

If you downgrade to 3.3 does it persist? It would be useful to know if it's tied to the firmware or the hardware.

CCS86

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

If you downgrade to 3.3 does it persist? It would be useful to know if it's tied to the firmware or the hardware.

Okay, I flashed back to 3.3 and the problem persists.

This is really odd, because I have a number of larger files uploaded already without that issue. So, it started recently.

No changes to me network or the printer. I'm stumped at the moment.

Phaedrux

A wireshark trace could maybe show where the problem is.

CCS86

@phaedrux

Is there a way for DWC to gather detailed logs?

Phaedrux

These are your options for logging but I don't know if it will capture what is happening.

https://docs.duet3d.com/en/User_manual/Troubleshooting/Logging

A wireshark trace would at least tell us where the connection is failing.

CCS86

@phaedrux

First attempt to capture packets during a failed upload:

Maestro_Wireshark.zip.txt

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