Test print with modified gcode causes disconnect of DWC
-
Hey @dc42 , I have a Duet 2 Ethernet, latest revision with the latest firmware (issue has been observed with past versions of firmware and DWC as well) that will cause DWC/Duet 2 to disconnect every time when running a test gcode job and will not reconnect until I power cycle the Duet 2. Since I am still doing the last bit of testing/commissioning, my test gcode is of a random object with gcode generated from Cura 4.0 (also happens with Simplify3D) but since my hot end and bed heater are not connected i remove the lines that start the heaters to the required temp in a text editor and then save it, upload and run the job. About a few minutes into the test print is when the disconnect happens. I do get the error about attempting to extrude with no tool connected for almost exactly 4 minutes until I get a warning "Connection interrupted, attempting to reconnect... Request failed with status code 503". It may also be worth noting that although the board is a Duet 2 Ethernet, I do use a raspberry pi 3b to act as a bridge between a usb wireless card and the ethernet port and then to the Duet 2 Ethernet. Personally it doesn't seem like a big deal, never had the issue on my other Duet 2 Ethernet or Wifi when printing a normal print but just want to bring it up in case the underlying cause can cause issues somewhere else, for someone else. Let me know if there is any other information I can provide.
-
@nikker said in Test print with modified gcode causes disconnect of DWC:
Let me know if there is any other information I can provide.
Firmware versions and the results of a M122 would be useful.
Can you tell if the raspberry pi still has a connection? It's definitely a more complicated setup than expected but should still work. Can you test with a direct ethernet connection just to remove that from the equation?
You could use M302 to allow cold extrudes which would stop the error. I'm not sure if it's related or not, but it could be worth eliminating.
https://duet3d.dozuki.com/Wiki/Gcode#Section_M302_Allow_cold_extrudes
-
My guess is that the repeated and frequent"Attempting to extrude with no tool selected" messages are causing the firmware to run out of output buffers. Try selecting a tool and enabling cold extrusion.
