Unsolved Another aborted print - M122 attached
-
Hi,
Well for the second time in the past few days a print has stopped much of the way through the print. Oddly enough the DWC reports 100% but it is clear that is false.
I have attached a M122 dump.
This is going to be a real problem if I can no longer print anything of size.
Thanks.
Frederick
M122 Dump #2.txt -
Was this the same gcode file as the last one?
Curious, does it simulate successfully?
-
@Phaedrux said in Another aborted print - M122 attached:
Was this the same gcode file as the last one?
Curious, does it simulate successfully?
No a different print but done with the same slicer Simplify3D - most recent version.
And what do you mean by "simulate"?
Thanks.
Frederick
-
@fcwilt said in Another aborted print - M122 attached:
And what do you mean by "simulate"?
I mean, instead of printing the file, run the simulation of the print file, where the firmware runs through the entire file in faster than real time in order to give an accurate print time estimate.
https://duet3d.dozuki.com/Wiki/Duet_Web_Control_Manual#Section_Uploading_and_organizing_G_Code_files
-
Hi,
Well I've learned something new. I did not realize there was a place to list the previous prints.
I had over 400 so I got rid of them all and upload just the one of interest.
The simulation went fine.
One thing that is different in the last couple of weeks is that I am using mesh compensation. I hadn't used that before.
I have no idea if there could be a connection or not.
Frederick
-
Hi,
Well I noticed something interesting.
Both prints failed at very close to the same height of 30 mm or 150 layers.
I'm going to run some test prints.
Frederick
-
Hi,
Well I ran 5 test prints using a simple object that didn't take long to get up to the height where the problem seemed to be occurring.
Of the 5 attempts, 4 of them just stopped printing at layer 153-154. It took a hard reset to get things back working again.
The two failed prints that prompted this topic also stopped at the same heights.
Something is messed up and I have no idea what to check next.
Any ideas?
Frederick
-
Hi,
Well I found the problem but I don't actually understand why it is happening.
In the recent past I was testing the endstop inputs on the Duex5 board and using them to run triggers. Those initial tests were good but the project got put on the back burner.
However one of the sensors connected to endstop input E6 was still present and under certain circumstances was activated during a print.
I didn't suspect it to be the source of the problem in that all the trigger did was use M117 to display a message.
Here is the part I don't understand. Sometimes, when the sensor was activated, it caused a reset.
Now I do have a emergency stop button connected to endstop input E1 on the DuetWifi and it works as expected.
I also have another button connected to endstop input E0 and it runs trigger2.g which contains just an M999.
Perhaps somehow the E6 input was running trigger2.g or activating the E0 input?
I don't know.
However for now I disconnected the sensor from E6 and all is good.
Thanks.
Frederick
