Prusa 2.6 3D Slicer demonstrates the power of open source contributions - tree supports

Prusa Slicer is another fantastic example of the strength of open-source software.  The Prusa Slicer 2.6 release showed out-of-the-box thinking that can significantly impact 3D print times and simplify trimming and post-processing. My favorite new feature is tree supports where the program takes an intelligent approach to building supports for overhangs and spans that are too big to be printed over nothing but air.

Video

3D Model Used

Supports

Prusa Slicer 2.5 supported the printing of removable supports when rendering longer spans over open spaces.  The molten filament will droop as it crosses from one support to another. The best practice guidance is to use supports for any angle over 45 degrees.

The green zig-zag is the removable support material. They are dense and can be difficult to remove. The end result is that the final print can have a lot of places that may need minor touchups. The zig-zag ends can have a bit more filament as it moves in one direction and then moves over and back in the opposite direction.

This is the same party using Prusa Slicer 2.6 tree supports. The support layout algorithm minimizes the amount of contact  on the bottom edge and fans out at the top to touch as many overhanging wedges as needed. Some of the support bases are outside of the box area. These supports are very easy to remove and do not affect the bottom surface or the quality of the side.

This is the same part with tree supports enabled. You can see that large portions of the bottom surface are not touched which reduces cleanup.

Here we have an inverted view with the bottom sliced off.  You can see how the tree supports branch out at the top to touch as many places as required on the overhang while minimizing the number of touchpoints on the bottom surface.

Video


Revision History

Created 2023 06

Comments

Post a Comment

Popular posts from this blog

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

DNS for Azure Point to Site (P2S) VPN - getting the internal IPs

Image
I wanted to access all my Azure resources without making any of them visible to the Internet.   The easiest give my local machine access to everything on my Azure Virtual Network (VNET) was to connect to it over VPN. It turns out creating Azure VPN gateways and connecting to Azure VPN endpoints is easy.  There are some subtleties in getting DNS name resolution to work that can confuse when first starting out. Setting the Stage There are a few ways to get to Azure endpoints and resources that are blocked from the internet.  We can  Create a Point-to-Site connection from our local machines to Azure Network Gateways Create a Site-to-Site network connection from our local networks to Azure Network Gateways. Use Bastion Hosts Use Cloud Shell Leave everything open to the internet. I chose a Point-to-Site (P2S) VPN connection that connects from my laptop to a VNet Gateway.  That joins my laptop
Read more