I have the same issue, but my failed prints always fail on my first layer only. I'll run the exact print again and it will work just fine. It's obviously my printer, but I have no clue as to why it happens.
- 3 weeks later...
AN update on the problem, so like you sugested i printed the code that came with the printer but no luck. This means that the g code is not the problem. This leaves software, hardware or the motherboard. For the software i tried five differet versions of marlin and all had the same problem. For hardware i disconected the heated bed (i thought it might have been shorting the power supply), but that didn't help at all, i also checked all the conections and made shore nothing is overheating .The only thing teft is the motherboard, and i really hope it's not fried. The problem remains the same the printer works compleatly fine for the first hower or two (it sometimes even finishes short prints), but then it abruptly stops- the lcd screen freazes (the temperatures stay at what they ware at the moment it froze, and it says it's printing), the bead and nozzle stop being heated and all the motors turn of. I realy have absolutly no idea how to fix this so pleas help
- 2 weeks later...
I am having a similar problem with my Ultimaker S5. This is only my 2nd print with it and the first went 5hrs with no issues. This newest print was set for a little under 2 days and was printing fine when I left work last night but when I came in this morning it was not moving and the clock was calling out that it had been printing for 19 hrs but clearly nothing has printed. Nothing has shown errors its just not running.
- 1 year later...
My setup:
Anycubic Mega-S
Cura Version: 4.7.1 (have not changed for a while)
Did anyone find a solution to this issue?
I just had two consecutive prints fail like that. My guess is that its something about Cura because it says the print should take 1h 47min for something I know I printed before (with other settings admittedly, but nothing that should make that big of a difference) that took like 2h 50min.
What seems to happen is that Cura is just writing about half of the file, the printer reaches the end saying it's done printing but the end gcodes aren't run (the head just stops; the bed is kept heated and so is the head).
For the second attempt, I tried re-slicing with slightly diffrerent settings but I got the same results.
@Ili - is it possible your power supply shut off for a 100ms and your printer rebooted? The behavior is quite different. Try turning on your printer and noting exactly what the screen looks like (take a pic). then when a print finishes, look at what the screen looks like.
The power bricks these days are too smart. They have little computers in them and often will shut down briefly.
If this is the problem you probably need a new power supply.
I have the same issue with 4.7.1 .
I have a 30+ hour print. and the print will run to about 40%, and then all of a sudden it says it is done, head freezes on the part, screen says the print is done and wants me to confirm.
This only happens with the 4.7.1 - 4.6.x never had the issue.
I did notice, this happened on some smaller prints when I had previewed sliced and then exported the gcode.
So far.. wasted about half a spool of pla - but now.. trying 4.6 to get things done.
I appreciate anyone's thoughts or help.
How do you get the gcode to the printer? Are you doing USB printing, octoprint, SD card, USB flash drive or other?
If you are doing SD card or flash drive then please check the gcode file on the storage versus the gcode file that was created when you sliced. Look at the bottom of the gcode file on the storage and see what layer it ends on (search backwards from the bottom for the letter Z a few times which typically only appears once per layer). Also do a file comparison - e.g. I think there is a command console program called "diff" you just say "diff file1.gcode file2.gcode" and if even one character is different it will list all the lines of the files that are different.
- 2 weeks later...
Hi,
Same problem since yesterday on 4.5.0, it stops mid-print, it just freezes but my lcd screen shows "printing", and the countdown also freezes on Cura (I'm printing with the usb cable)...
I've tried with the last version of Cura and it did the same... What is going on?
EDIT : Nevermind, it was my USB port
Edited by Feuille-
Our picks
-
UltiMaker Cura 5.7 stable released
ArunC posted a topic in UltiMaker Cura,
Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more.
-
-
- 16 replies
.thumb.jpeg.0b7a05eafc09add17b8338efde5852e9.jpeg)
Picked By
MariMakes, -
-
Release Notes: S-Line Firmware 8.3.0 (Latest)
Dustin posted a topic in Firmware,
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.-
-
- 0 replies
Picked By
MariMakes, -
-
.thumb.jpeg.0b7a05eafc09add17b8338efde5852e9.jpeg)
Recommended Posts
Smithy 1,144
Do you have any GCode which was probably shipped with your printer? Just to be sure it is not a printer issue.
Link to post
Share on other sites