Print just stopping dead after about 1 hour.

[Lochemage]

Hi guys, I just built a new Rostock MAX. I made a couple test calibration prints when all of a sudden, my printer refused to print passed the first perimeter (on both PC and SD modes were the same result). Very similar to the problem here, so I have tried a lot of your guys' suggestions, but none of them worked. What's weird is that whenever I try printing in Dry mode, it printed the entire part fine. After a lot of battling and cursing, I finally discovered what it was. This may not be the answer to your problem, but it might also be similar. I was experimenting with the EEPROM settings and had changed the "OPS Operation Mode" to "2" and that caused the issue. Possibly shouldn't be experimenting with options I don't know too much about, but that ended up being my issue. I have not tried testing it out using "1" as the option.

[Generic Default]

I should have posted in this thread in June 2013 because I've been having this problem for 7 months now. But for the last week or so I've been getting consistent print failures with all of the symptoms mentioned by other people. Every time it costs me time and money in wasted nylon, and although I've had my rostock since May 2013, I haven't feel that I have ever had a working 3d printer.
Patterns I've noticed;

-It happens the most with Cura
-It happens with larger files (low layer heights; complex parts)
-It happens at the -exact- same layer and position for the same gcode

I ran the same gcode twice for a print two nights in a row and it stopped in the same spot both times. The next night I re-saved the STL file with about twice as many vertices/polygons, and when I printed it, my rostock stopped at about 1/2 the height that the previous two had stopped at.

Has anybody solved this problem yet? Has anybody found a solution, because this seems like a serious problem to me!

Also, foshon said he switched to marlin to print reliably, but that was like 9 months ago. Is running marlin firmware essentially the same as running repetier?

[ccavanaugh]

It's a known repetier bug. Upgrade to the 0.90 / 0.91 release and it should solve the problem.

http://forum.seemecnc.com/viewtopic.php?f=54&t=3985

[Flateric]

Problem is resolved. Have not had deadstop of anykind for a few months on this issue.

[Eaglezsoar]

Problem is resolved. Have not had deadstop of anykind for a few months on this issue.

Was it fixed in the firmware .83 that is currently available for the Rostock Max from SeeMeCNC?

[Flateric]

I have not used the .83 firmware for many many months, so I couldn't tell you for sure on that question.

[Polygonhell]

Problem is resolved. Have not had deadstop of anykind for a few months on this issue.

Was it fixed in the firmware .83 that is currently available for the Rostock Max from SeeMeCNC?

I don't believe so, I started seeing this a couple of weeks ago after using Cura and the latest Slicer to generate GCode, it's what prompted me to upgrade to 0.9

[Generic Default]

Has anyone gotten the newest firmware to work yet? They released it on New Year's Day.

I tried uploading it to my rostock but the LCD doesn't show anything and the steppers twitch a little bit. I can't print what I need to print with the current firmware because it stops, but I can't install the new firmware either. yarg

[Polygonhell]

I have it running, but mines setup for the original machine, not the current versions.
I manually configure the LCD because I've never gotten the preset LCD configurations to work.

[TRAILtech]

Its happening for the .9 version as well for the record... Haven't tried the .91 version in afraid its probably full of bugs, hopefully they'll release a rev 2

[Eaglezsoar]

Its happening for the .9 version as well for the record... Haven't tried the .91 version in afraid its probably full of bugs, hopefully they'll release a rev 2

The .9 version is that the development version?

[truenorthtrader]

I have the newest Mac repeteir and Cura versions.

I just had a large print stop on me after 3 hours
It's really frustrating not knowing when something will die on you

Am I assuming that using Slicer never causes prints to stop?

Mine also stops with heat still running but motion halted

[Flateric]

Read through this entire thread for many different preventative things you can do.

Alot of the deadstops are related to wirie routing and electrical interferrances.

[enggmaug]

I am currently running a 5 hours print.

The MAX stopped after 3 hours printing. As I just read this thread this morning, I imediately switched off/on the machine, homed the head, and reheated the bed to avoid my print to separate from the bed.

Then I plugged a spare 10m fan I had in unused FAN1 slot as I knew it drives the FAN continuously (the fan on my plateform is plugged in FAN0 for being able to control it) . I then put the fan towards the RAMBO.

I removed the Gcode from layer 1 to 92 (layer wher the machine stuck) before relaunching the print.

I am 15 mins away to the end, and it looks fine. woohoo !! It was close to total failure, but once again, I got lucky enough to be here when it happened.