Cut a model with Prusa Slicer and put it back together with dovetail joints

The Prusa Slicer supports a couple different patterns for cutting a model into pieces and then joining it back together after the print. I wanted to print a sword that was too large for my printer.  It needed to be in 4 pieces.  The Prusa Slicer supports cutting a model using an infinite plane and joining those back together after the print with plugs, snaps, dowels, or dovetail joints.   The dovetails work great but need different reinforcement and printing settings than the plugs or snaps.

The standard planar cut

The standard cut is "planar" or a flat cut across the piece.  This is a pretty common way of cutting a figure to split printing or for some other need.



The slicer "Add Connectors" button brings you to another screen that lets you size the connectors that will join the two pieces.


You can place a connector anywhere on the cut line by clicking on it.  The geometry of the connector is specified in the panel.



Dovetail Cut

You can instead try a dovetail cut that removes the need for connectors.  The cut is more complicated so it can't or shouldn't be used in many situations based on the amount of material.


Dovetail Cuts in practice - good and bad

The sword was printed with standard perimeter and infill settings. That was not a good idea.  The material around the joint was not strong enough when using the default settings.

This picture shows two pieces of a sword joined by the dovetail cut.  I thought this technique would create a super stable and strong joint when glued because of the complexity of the join and the amount of surface area.









Here is the sword broken down into 4 pieces, every joint was a Dovetail cut.   I used a Silk filament here that is super hygroscopic and needs to be dried every time it is used. 


I tried changing the angle of the dovetail joint from 60 to 65 degrees to have more material on the piece with the two outer edges.  Increasing the angle made the joint base a little wider still did not provide enough material for this joint.  The base was too small and the settings didn't provide any infill to strengthen the pieces.  These broke off with a minimum amount of pressure.
The large side of the joint didn't have enough material either and was easily snapped off. It is pretty obvious that we need to strengthen the connector area if we're planning on putting any pressure on dovetail joints.

Reinforcing the dovetail

Prusa Slicer lets you change the slicing behavior at different layers on a per-part/component basis.  This lets you change the infill density and style for specific layers or height ranges.  The picture at the right specifies infill density changes on all the joints.

  • Highlight the part
  • Right mouse --> Add height range modifier
  • Highlight the Range
  • Right mouse --> Infill
  • Change the infill









You can click on the picture at the right to see the popup menu choices or do the same in your Prusa session



















Plug, dowel, snap

The insertion areas of the planar cuts also need to be reinforced if you intend for them to have any load. They should work fine if you are just making a piece of art or figure that isn't going to operate under any stress

Video

The first video demonstrates the dovetail joints with failure.


A followup video that shows how to change the infill at different heights to reinforce the joint.

Revision History

Created 2024 05


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