{"id":7446,"date":"2023-10-31T14:56:53","date_gmt":"2023-10-31T14:56:53","guid":{"rendered":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/?p=7446"},"modified":"2023-11-02T19:31:52","modified_gmt":"2023-11-02T19:31:52","slug":"christopher-tye-gcode","status":"publish","type":"post","link":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/2023\/10\/31\/christopher-tye-gcode\/","title":{"rendered":"Christopher Tye, GCode"},"content":{"rendered":"
\n
\"\"<\/figure>\n<\/div>\n\n\n

Process and Code Generation<\/h2>\n\n\n\n

From the onset, I was more apprehensive on my approach to solving this assignment. Not only did sickness ravage me at the wrong time but this also happened to be the section I was “understanding” the least! That being said, I took advantage of a few key features of GCode throughout all of my forms and they’re as follows.<\/p>\n\n\n\n

My first two forms are built using custom polygon generating scripts with each having a distinguishing factor that makes it unlikely it would be able to be produced traditionally, such as the snowflakes freestanding filament or the cactus’s bumpy sides. I made these two forms specifically because I felt that each showed a different unique function of GCode. <\/p>\n\n\n\n

The snowflake was a bit of an exercise on geometry properties, but once proper counsel was found difficult tasks such as creating a repeating expansion of a polygon centered around a point became possible. With this one I wanted to use randomly placed, freestanding filament between each telescoping layer to create a strong structure on what is essentially tensioned strings. To my delight, this worked and the snowflake has immense structural integrity. I would love to go in sometime and try to create an actual telescoping form where the string are printed long but unconnected, allowing each polygon to move individually until the length of that string is matched.<\/p>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div><\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div><\/div>\n<\/div>\n\n\n\n
\n
\n
\"\"<\/figure>\n<\/div><\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div><\/div>\n<\/div>\n\n\n\n

It also allowed me to have a little bit of math fun with the cactus, as it’s actually a nonagon shape that is folded in on itself, creating a star pattern. Adding a filament variation that grows as the layer height grows is another unique capability of GCode, allowing me to both shift the polygon center as we rise but to also add extra time to my over extrusion on the sides. I find it particularly interesting how the bumpiness on the outer walls is reserved for ever other, but is seen across the entire interior.<\/p>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div><\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\"\"<\/figure>\n<\/div><\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div><\/div>\n<\/div>\n\n\n\n

Lastly, my third form is titled the crown. I wanted to use another new technique that took advantage of the ability to create your own slicer, and I took that to make a form that takes a simple slicer shapes and turns its perimeter into a range of rising points. This form is notable for being the biggest pain to print, mostly due to its inclusion of multilayer Z Axis printing. As the form grows, the points of the crown become steeper. This also makes it more troublesome though, as the available space to move with the nozzles between multiple layers is quite small. I wanted to make this effect as noticeable as possible but eventually found myself doing a dozen of two test prints trying to maximize the effect. This form also has very flexible properties like some of those shown in class, and seems to hold its shape well regardless!<\/p>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div><\/div>\n<\/div>\n\n\n\n
\n
\n
\"\"<\/figure>\n<\/div><\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div><\/div>\n<\/div>\n\n\n\n

Iterative Design Process<\/h2>\n\n\n\n

One foundational aspect of this assignment that I was expecting, but not to this degree, was the iterative design process. Since we have full power over the printer when we write our own GCode, it is sometimes an experimental game of making a small change and doing a test print to achieve certain properties. <\/p>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div><\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div><\/div>\n<\/div>\n\n\n\n

Above are two examples of what this process looked like, specifically the right one. I would often run between rooms making the slightest iteration in design, or more frequently I’d do the first few layers of a print using different printer settings. These printer settings were made almost entirely by trial and error, meaning that for my crown form I had printed almost a dozen trial prints to find the best temperatures and speed to print at to reduce lifting. Due to the increasing slopes on this form as well, there were many fails that helped me dial in a good angle that still worked with my printer.<\/p>\n\n\n\n

The snowflake and cactus forms were much more take it or leave it, not being too picky about exactly at what temperature I was printing or how fast. The snowflake did have 2 test prints beforehand to test the procedure and to shift things in the design slightly, but I don’t believe any other sweeping changes would’ve been made. One thing I found frustrating about this assignment and this aspect specifically, is that there would often times be a move that didn’t show in Cura at all that would still be present in the final print. Surely then this must’ve been me making a move with an extrusion rate change? Well if it is, I have no idea how because I specifically defined when it should and shouldn’t be extruding as well. I’m curious if anyone else also shared this problem!<\/p>\n\n\n\n

Code <\/h2>\n\n\n\n

The code used for this project can be found\u00a0here<\/span><\/a>. Each form has been separated into it\u2019s own Grasshopper file for simplicities sake.<\/p>\n","protected":false},"excerpt":{"rendered":"

Process and Code Generation From the onset, I was more apprehensive on my approach to solving this assignment. Not only did sickness ravage me at the wrong time but this also happened to be the section I was “understanding” the least! That being said, I took advantage of a few key features of GCode throughout all of my forms and […]<\/p>\n","protected":false},"author":36,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[40],"tags":[],"class_list":["post-7446","post","type-post","status-publish","format-standard","hentry","category-gcode_23"],"_links":{"self":[{"href":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/wp-json\/wp\/v2\/posts\/7446","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/wp-json\/wp\/v2\/users\/36"}],"replies":[{"embeddable":true,"href":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/wp-json\/wp\/v2\/comments?post=7446"}],"version-history":[{"count":3,"href":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/wp-json\/wp\/v2\/posts\/7446\/revisions"}],"predecessor-version":[{"id":7622,"href":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/wp-json\/wp\/v2\/posts\/7446\/revisions\/7622"}],"wp:attachment":[{"href":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/wp-json\/wp\/v2\/media?parent=7446"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/wp-json\/wp\/v2\/categories?post=7446"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/handandmachine.org\/classes\/computational_fabrication\/wp-json\/wp\/v2\/tags?post=7446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}