Printer stopped working 1/4" from finished...

[Norm77]

I just got done with a 4 1/2 hour plot. The object was stopped about a 1/4"
from being done and the printer stopped. The printer did not home the
towers, it just stopped. What in Repetier-Host or Slic3r is set incorrectly.
Very frustrated'

Thanks,

Norm77..

[Polygonhell]

It's going to be hard to diagnose without more information.

What version of the I firmware are you running?
Did the LCD show any indication of error I.e. Def printed in the temperature fields?
Did you disable all of the power saving features on the computer connected to the printer?

[Norm77]

I'm running Repetier-Host ver. 0.95F. I don't believe there were any errors in
the LCD screen but as soon as it stopped printing, the hot end was resting on
the part so I went ahead and homed the towers. I also just noticed that when
I clicked on the G-Code Editor, in the display screen, It does show that the top
did not complete the part. In other words, the print looks just like the G-Code
editor. I hadn't noticed that before.

I also was running AutoCAD, working on the next project, as well as Internet
Explorer. Concerning the power features, I have never really messed with
them, so I would have to say no to that question.

Also, I had the computer connected to the printer via USB cable. I did not
consider that a problem since I've been using it to print for the last 3 weeks.
Going back to your question about the temperature fields, I do remember
them being set back to "zero"

I guess I'm really perplexed as to why this happened. I've printed several
items experimenting with different settings in Slic3r and although I had a
few mistakes I really never had one like this. The main difference is that
this print was a lot taller than some of my other prints.

Thanks,

Norm77...

[Polygonhell]

The are two common versions of Repetier FIRMWARE (not host), the 0.8x version was known to have a bug where it just stopped. It should print the version number on the LCD when you reset it.

If you have 0.8x installed you'll want to upgrade to 0.91, the bug is fixed there.

If you already have 0.91, the odds are there was an issue in comms between the computer and printer.

[Eaglezsoar]

If you need to work with your computer while it is being used to also process print jobs, you may find everything works better if you put the gcode on
a class 10 SD card and use the SD card with the LCD reader to process the print jobs and disconnect the printer from the computer.