![]() But that instructor was an engineer, not a frustrated high school administrator that had to teach one class that he barely knew about. I was terrified to take drafting in college after that. And he made us use these green plates that pretty much had a chemical reaction with an eraser, so I did very poorly in that class. If he could detect an erase mark it was a letter grade off for each mark. On a side tangent… I had a horribly tough drafting instructor in high school. If you don’t know one then here’s two really isn’t a number disagreement, because you can not know one and then meet two, right? (As opposed to, say, if you want one you can buy a dozen at….). ![]() Nah, then what would you do with your day other than protect the Internet from the ungrammatical? Besides, I’m not sure that’s really a disagreement (or is that what you are alluding to?). And that’s when your code starts to become complex and harder to follow. Going from lines to gcode should be trivial if you are a bit software minded.Ĭombing, retraction, multiple extruders, support material are all features that come after that. Top and bottom? Substract one layers outline from the other, what’s left needs to be filled. (It’s extremely high poly, and has holes and self intersections where the support was hacked in) It was a key difference from Slic3r at that time, which flat out refused to slice any model that wasn’t perfectly manifold.Īfter you have your model cut in layers with outlines, it is pretty much smooth sailing from there on. This model was key, because it covers a lot of edge cases where the initial slicing step can fail. I used the “Ultimaker robot with support” as test model for a lot of initial tests. So if you look at the code before support material was added, you have a pretty solid simple base that should work reasonably. Support material was pretty much the last major feature that was initially added. But that didn’t have infill or tops/bottoms. I had my first print after 2 days of work, thanks to libclipper. It all started out as a quick experiment to see if I could make something that resembled a slicing engine instead of using Skeinforge. Those core concepts still remain today, but greatly expanded. It’s functional and should be easy to follow. You could go back to the first months of the CuraEngine code. Posted in 3d Printer hacks, Software Development Tagged 3d printing, 3d slicing, autodesk dynamo, dynamo, gcode, slicer, stl Post navigation What tricks do you like to use when it comes to slicing? ![]() We even have our own tool for merging Gcode with different options (like layer height). We’ve also talked about using scripting languages to munge the Gcode output from a slicer. We’ve covered slicing tricks like variable height layers, before. However, those are usually mature products full of features and it can be difficult to figure out how to insert your own code into them (with the possible exception of writing a Cura plug in). ![]() Granted, a lot of slicers are open source, so you could start there, too. But if you insist, think about how your own slicer could allow you to experiment with different types of support structure generation, infill patterning, and other details. Why build your own slicer? Well, we never really need a reason before we do things like this around here. Slicers have to determine what each slice of the 3D model looks like and create Gcode to represent those layers. You sort of know what it must be doing, but until you’ve seen one taken apart, there are a lot of subtleties you probably wouldn’t think of right away if you were building one from scratch. However, the details aren’t really specific to Dynamo. Their post is very detailed and uses Autodesk Dynamo as a graphical programming language. and want to encourage you to write your own 3D slicer. If you don’t know him, maybe it is you! If you really don’t know one, then meet these two. If he’s not using assembly language, he uses a compiler he wrote. We all know that hacker that won’t use a regular compiler.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |