Failed Prints Due to Partially Uploaded GCode
-
I believe I just had an instance where the WiFi was dropped during a file upload and led to a failed print due to a partial upload of the file. The file should have been about 28 MB but only 17MB was uploaded. Because I usually use the upload and print, the machine started the print when it thought it was done. I did not think anything else of it as I have not run into this yet that I am aware of. Usually if a file fails to upload or the WiFi drops, the prints don't start. Prior to this attempt, an upload did fail when the WiFi dropped and it indicated that it failed.
14Hrs into a 28 Hr print it stopped. The machine indicated it finished the print but did not execute /sys/end.g
-
DuetWebControl checks that the length of the stored file matches the original, so that is most unlikely.
Were you uploading a file that you just generated with slic3r? There was any maybe still is a known issue with slic3r, in that it lets you read the file it is generating before it has finished generating it. So it is easy to upload the file before it is complete.
-
DuetWebControl checks that the length of the stored file matches the original, so that is most unlikely.
Were you uploading a file that you just generated with slic3r? There was any maybe still is a known issue with slic3r, in that it lets you read the file it is generating before it has finished generating it. So it is easy to upload the file before it is complete.
I only use Kisslicer. Pretty certain that I saved it out and walked away before coming back and uploading. I've been weary of accidentally uploading while it is saving out so I have made a habit to check that Kisslicer is done saving before I upload.
Does the fact that end.g did not get executed despite reaching the end of the file mean anything? I was under the impression that end.g gets run at the end of the file, regardless of the final command in it.
-
The stop.g file only gets run when command M0 is read from the gcode file and executed.
-
The stop.g file only gets run when command M0 is read from the gcode file and executed.
end.g is my own doing then and I normally call it in the post fix gcode from kisslicer. I thought there was a file that got called when the end of any gcode file was reached. Sorry for the confusion.
I'm not sure how this happened then, I guess I may have uploaded the file before it was completely saved out but I feel like I checked that it was done before doing so.
-
I just switched the machine over to use an ethernet. Sure enough, on my first file upload it failed but did so by checking that the sizes differed. Second attempt worked and I verified by opening the file in DWC editor.
I was hoping this problem may give some insight on WiFi issues but it's only convinced me that the network my machine is on just has some issues/incompatibility. So far I have not lost connection of my ethernet board…. we'll see in the morning. The network is large and in the control of IT professionals. If all else fails, I'll have to devise a way to put the slicing/control PC and the machine on their own network of sorts.
-
FWIW, the ethernet maintained connection over night. Normally, the WiFi would have been disconnected and unable to reconnect without resetting the WiFi module.
-
Are you checking the file size right after uploading? or checking after the print fails? I had an issue a while back where my SD card was corrupting the gcode files while printing. I would upload a file and size would be right. Then part way through printing, the end of the file would get deleted. I reformatted my SD card and haven't had the problem since.
-
Are you checking the file size right after uploading? or checking after the print fails? I had an issue a while back where my SD card was corrupting the gcode files while printing. I would upload a file and size would be right. Then part way through printing, the end of the file would get deleted. I reformatted my SD card and haven't had the problem since.
It seems to me that it is something to do with the uploading process. I've only seen it happen that one time. I'm really not sure at which point something went astray. If I see more problems, I'll keep reformatting in mind. Thanks for the heads up!
