Rostock Stopping during printing?

[truenorthtrader]

Hey folks

I'm not sure if it's the model I'm printing, mechanical, something with the Cura slicing code, but it's STOPPING the printing...yet the bed and Nozzle heat stays on.
Seems to always be a ways into printing a larger model at different heights.

Reset the printer and the motors run, heat works etc.

The only mechanical change was I added a small Fan to the board and it's on during the whole print. I've seen people with 3 or more fans on the Rostock and I insulate any exposed wires.

I also upgraded to the ONYX but this happened before I installed the ONYX bed.

Anyone else experience this problem and know the solution??

[lordbinky]

Eliminate one possibility quickly, check your endstop connections and make sure the end stop wires are not routed right next to your stepper motor wiring.

[truenorthtrader]

Endstops are fine, Goes home without problems, checked incase. They're all above the motor wiring and made sure they don't get close to the heat of the motors as well.
thanks

[Eaglezsoar]

That is one pretty blob.
Seriously, I suspect something in the code is causing the problem. The first thing I would try is a different slicer either Slic3r or Kisslicer and try the print again.
I suspect that the print will continue with a different slicer. What is in the code causing the problem? To answer that would require that you post the code generated
by Cura and someone on the forum with more knowledge than I would have to take a look at it and try to find the offending line. Please try the different slicer and let
us know the results.

[Batteau62]

I would also be suspicious of usb connection. Do you still have control of the printer with the host after it stops. Are you using Repetier?

[JohnStack]

It's the model file having errant characters. Been there....clean it with meshlab (or Netfabb) and see if you can't remove the errant characters.

You might also just try by using something like a strong text editor (like on a Mac, eMacs, Text Wranger) first. I'm not sure the other software packages would filter for bad chars...

[truenorthtrader]

Yes it did it again!

I can post the full code but it's really long as it's a large piece about 13 inches high

If stopped at Layer 892 of 1134 of a different model. it was going for about 13 hours then just STOPPED while the Heating was still on and the motors were making quiet sound, nothing in the code I could see, just stopped at printing layer 892.

Luckily with Cura I can start at a point and continue then glue together but it's a pain doing that but the 13 hours are not lost.

How can I find that code for those lines and what do I look for that is bad?
thank you again guys!
A

[kbob]

You could turn on echo, then look at the last thing printed in Repetier Host's log window.

[kbob]

Luckily with Cura I can start at a point and continue then glue together but it's a pain doing that but the 13 hours are not lost.

A

Can you start the print a couple of layers below the stopping point? If you do, does it stop reliably at the same place?

[truenorthtrader]

yes thanks I finished it by looking at the model and continuing it at that spot just below as I'd probably have to sand it a bit and it printed the rest without problems.

But I'm always worried it will happen again. I hope the programs can be updated to stop this if it's not mechanical but it happens at different heights.

[Durandal]

I'm getting the same issue with Cura at right around the same point, what's your layer height? I've had two prints stop at 875 and 890 with a .2mm layer height. Odd that it seems to be right around the same layer for both of us.

In my case on the second one I was watching when it happened, it finished up layer 889 and then just froze in place without going to 890.

The first time I was running the print from the SD card reader the second time through Repetier Host via USB.

[barnett]

Do you guys remember this thread about repetier firmware causing halts during large prints? Highcooley was having this same problem.

I think John Oly's version version of the firmware may fix it, but I didn't read all the way through to confirm it.

[Eaglezsoar]

Do you guys remember this thread about repetier firmware causing halts during large prints? Highcooley was having this same problem.

I think John Oly's version version of the firmware may fix it, but I didn't read all the way through to confirm it.

Can you tell us what you read or better yet, where you read it? Thanks!

[Durandal]

I am using the SeeMeCNC fork of Repetier, version 0.80.

Truenorthtrader, what version of Cura are you running?

[barnett]

OK yeah that's a huge thread. Here's where Highcooley reports it stopping on Feb 11th.

... Somebody reported aborted prints. This happened to me twice now. Once after about 3 and once after about 5 hours, the printer reported idle and repetier host also didn't report any error. The movement of the printer just stopped mid print and the hot-end kept temperature. This never happened with marlin so far. Somehow I can't believe that this is only a USB issue...

Here's the error posted on github.

I don't know if the problem here is the same thing, it just sounded familiar to me.

[kbob]

There is a button on Repetier Host labeled Fake OK. I have never had to push it, but it sounds like it might be applicable to these stalled jobs.

[barnett]

Your error could be the same as the error first reported by Highcooley back in February. Personally I have not experienced it, but I rarely do 8hr jobs (although I did a giant gear bearing that was 8hrs 14 min).

It you might try newer repetier firmware or switching to Marlin.

Here's a quote from the last time I saw the symptom reported here.

OK yeah that's a huge thread. Here's where Highcooley reports it stopping on Feb 11th.

... Somebody reported aborted prints. This happened to me twice now. Once after about 3 and once after about 5 hours, the printer reported idle and repetier host also didn't report any error. The movement of the printer just stopped mid print and the hot-end kept temperature. This never happened with marlin so far. Somehow I can't believe that this is only a USB issue...

Here's the error posted on github.

I don't know if the problem here is the same thing, it just sounded familiar to me.

[Nylocke]

I've had this happen with marlin so it isn't repetier specific, it seems as if it gets stuck in a G5 Dwell command I think.... I never found an answer to the issue, but it hasn't happened since even with the 10 hour print I did... Or with any other prints I've done.... I was using Slic3r at the time rather than cura.

[Zerosink]

2 in a row for me, Repetier, version 0.90, USB. No errors or nuttin
Once 2 hours in to a 5 hours print, and once on the 20th layer of a 4 hour print.

One "may' have been while Win7 was downloading a new update. The computer didn't reboot but the notice was there to reboot.

[Eaglezsoar]

2 in a row for me, Repetier, version 0.90, USB. No errors or nuttin
Once 2 hours in to a 5 hours print, and once on the 20th layer of a 4 hour print.

One "may' have been while Win7 was downloading a new update. The computer didn't reboot but the notice was there to reboot.

Your decision but I would never have the computer connected to the Internet while performing a print. You discovered one reason and I
just wouldn't chance all the malware etc plus the fact that the computer should have as few processes going on as possible.

[Nylocke]

Heh.... I watch you tube videos and slice things while printing......

[Zerosink]

Ya know, sometimes I just don't have a choice

I would rather someone fix a problem that for everyone go and hide from it.
If we don't speak up no one would know there is a problem.
I don't have the "know how" to fix it.
I have an up to date system, SSD drives, lots of memory, debugged all I can, running the best antivirus I can.

I still am going to take a shower even if that's where most injury's at home take place.

If the price is $2.00 and 2 hours of waste .... well as long as it is not often I will deal with it.

I run this thing wide open, MANY programs at once most of the day and all the time I am printing.
I have printed close to 6kg of PLA with only 2 "stopped printing for no reason"' issues.

If running other processes where an issue I would bet I would be the one to have them.

Now where is the error? RH hasn't a clue. We wish it would give a hint even guess at the reason for the error not just stop.
That being said RH is still worth a lot more that what we paid for it

[Nylocke]

I'm fairly certain that something in the G-code make it get stuck on a G4 Dwell command.... or maybe in the firmware...

[inventabuild]

To help narrow down the problem try printing from the SD Card. If your print runs fine from there then chances are there is a USB issue or your computer is getting bogged down causing the print to stop.

[truenorthtrader]

I don't have an SD card reader I got one of the first Rostock Max's that didn't have that.

I'm still having the problem it's completely useless can't print anything large, ran through Netfabb and Meshlab fixing everything I could but model's just stop printing while the hot end and bed stays on heated. And not at the same point always at a different spot

I have a quad core computer and the computer has plenty of speed only using a fraction of the CPU power.

Could it be a bad thermistor or something causing this?

I've tried printing many different models it's not likely that all the models I print have bad code when I never encountered this problem originally.