Hello, I am having an issue with a part on a Rostock Max V2 3d printer. I am working on printing parts for a drone and am having issues with the base. I will include the STL file here: https://www.dropbox.com/s/8dkrq8lxdjqjr4r/Base.nofillet.STL?dl=0. The slicing engine is matterslice(using matter control as the means of communication to said printer.) What occured today is that it was printing fine until it was moving back to the top right corner of the part where extruded mid air and then proceeded to crash into the bed. I unfortunately do not have the G code on me for this part and previous parts were faulted to intersecting faces. I am at wits end and want to get this drone flying soon so if anyone might be able to help I would appreciate it. One question I had is if there was a way to make the Rostock Max v2 follow a custom code and if so, can it be generated in solidworks. Thanks.
For what it’s worth I downloaded the stl and sliced it in Simplify3d: I thought maybe the stl was at a bad angle (I’ve seen that before), but it slice perfectly flat… so I’d rule out a bad stl, unless Matterslice has a problem with the data where S3D doesn’t.
@Eric_Pavey So what course of action should I take at this point in time? Is there a way to manually slice it or generate G code?
If you’ve already successfully printed a bunch of parts, that tells me there’s nothing wrong with your machine. It’s quite possible your slicer just hates that mesh 
It’s happened to me in the past. In that case maybe try Cura, Slic3r, KISSlicer, or any other free one and see if you get different results with the gcode they spit out? I’ve never used matterslice so I can’t really give you any tips there.
Alright I will try that and send back the resulting print logs from each one. It will take a few days to a week to get back to this thread but I might be able to have one up by tomorrow. I am currently in school so Wednesday to Sunday I am on a small break to visit the family.
Alright I just printed the part using Mattercontrol and the Slicer engine and it just caused the arm to over extend outside the enclosure. Same result with Cura Engine. The logs are found here: https://drive.google.com/file/d/0B3pUbhun7I8temxHVlBRdHRqcHc/view?usp=sharing
https://drive.google.com/file/d/0B3pUbhun7I8temxHVlBRdHRqcHc/view?usp=sharing
Very odd. Unfortunately those logs don’t mean anything to me, I’m not
familiar with that slicer. Not to mention I’ve never used a delta before,
my bots are Cartesian & core-xy. At this point you may want to visit a
form from your printer manufacturer and see if you can get help with people
more familiar with that hardware/firmware.
Are you able to preview your gcode in 3d? If so, does it have any weird
moves outside the build volume?
Also, it could be a loose wire: I’ve had some fail on my bots when things
start vibrating and suddenly things are moving in ways they shouldn’t.
Yes it was way off the bed. it showed no extrusion either. This is the same with both Slic3r and Cura Engine
To confirm, the gcode preview showed it going off-bed?
Ghé thăm nhà mình nhé @Andrew_Francis
@Eric_Pavey correct with no extrusion at all
Well, at lest you can see it failing before you print. At this point I’d try changing print settings and see if you can somehow make it go away.
When I sliced it in Simplify3d, it seemed spot on, no unnecessary travel moves.