Why does Repetier-Host always crash slicing large files?

Having a problem? Post it here and someone will be along shortly to help
Post Reply
User avatar
elqisqeyano
Printmaster!
Posts: 256
Joined: Sat Mar 30, 2013 1:29 pm
Location: Franklin County Ohio

Why does Repetier-Host always crash slicing large files?

Post by elqisqeyano »

Every time I slice large files using Repetier-Host, itr completes the slice but crashes and will not print from Repetier-Host. Anyone know why this is?
User avatar
dsnettleton
Printmaster!
Posts: 102
Joined: Fri Mar 22, 2013 11:09 am

Re: Why does Repetier-Host always crash slicing large files?

Post by dsnettleton »

I can't address your problem specifically, but I can give you a few suggestions. First, you could do the plating and slicing in slic3r itself. When you hit the configure button to change your settings for slic3r, it's not just opening a new window; it's opening a new program. Try clicking the add button on the plater tab of slic3r and slicing your model from there (click export gcode you can load this code back into repetier by hitting F2). If you're still having problems, at least you know the issue is with slic3r and not repetier host. One caveat is that I believe the latest version of repetier host disables the plater tab by default when it launches slic3r. To get around this, just navigate to your installation directory and launch slic3r yourself. If you're still having trouble, try updating/reverting the offending software to another version.
Trust me, sir. I'm a wizard.
User avatar
elqisqeyano
Printmaster!
Posts: 256
Joined: Sat Mar 30, 2013 1:29 pm
Location: Franklin County Ohio

Re: Why does Repetier-Host always crash slicing large files?

Post by elqisqeyano »

I sliced it with Slic3r directly from Slic3r. Then when I open Repetier-Host and load the Gcode generated by Slic3r it goes into a none responsive mode so I have to force close the program. It only does this with large prints I noticed. Smaller prints I can slice right from within Repetier-Host others I have to slice directly from Slic3r.
Polygonhell
ULTIMATE 3D JEDI
Posts: 2417
Joined: Mon Mar 26, 2012 1:44 pm
Location: Redmond WA

Re: Why does Repetier-Host always crash slicing large files?

Post by Polygonhell »

elqisqeyano wrote:I sliced it with Slic3r directly from Slic3r. Then when I open Repetier-Host and load the Gcode generated by Slic3r it goes into a none responsive mode so I have to force close the program. It only does this with large prints I noticed. Smaller prints I can slice right from within Repetier-Host others I have to slice directly from Slic3r.
Have you tried waiting, it can take a while after a large GCode file is loaded, I assume it's generating the tool paths for the 3D render.
User avatar
elqisqeyano
Printmaster!
Posts: 256
Joined: Sat Mar 30, 2013 1:29 pm
Location: Franklin County Ohio

Re: Why does Repetier-Host always crash slicing large files?

Post by elqisqeyano »

Polygonhell wrote:
elqisqeyano wrote:I sliced it with Slic3r directly from Slic3r. Then when I open Repetier-Host and load the Gcode generated by Slic3r it goes into a none responsive mode so I have to force close the program. It only does this with large prints I noticed. Smaller prints I can slice right from within Repetier-Host others I have to slice directly from Slic3r.
Have you tried waiting, it can take a while after a large GCode file is loaded, I assume it's generating the tool paths for the 3D render.
Not really, I have waited maybe 2 to 3 minutes. Maybe I should just let it be and see.
User avatar
elqisqeyano
Printmaster!
Posts: 256
Joined: Sat Mar 30, 2013 1:29 pm
Location: Franklin County Ohio

Re: Why does Repetier-Host always crash slicing large files?

Post by elqisqeyano »

Still waiting, been 20 minutes.
User avatar
elqisqeyano
Printmaster!
Posts: 256
Joined: Sat Mar 30, 2013 1:29 pm
Location: Franklin County Ohio

Re: Why does Repetier-Host always crash slicing large files?

Post by elqisqeyano »

I slice it with Slic3r and load it onto pronterface. Repetier Host always freezes.
Post Reply

Return to “Troubleshooting”