1

The print is a collapsible sword I'm using as a test. Everything seems fine on the outside, but inside it seems the segment parts of the sword inside the hilt are fusing together at the seam lines causing them to stick together.

Model: https://thangs.com/designer/3dprintingworld/3d-model/Collapsing%20Katana-22696

Finished Print (looks fine) enter image description here

Concentric blade pieces (fuse marks that I sheared off and broke to get out) enter image description here

Seams on exterior of hilt look great enter image description here

Print settings/info

Printer: Prusa MK3S+

Slicer: PrusaSlicer 2.5.0a3

Settings preset: 0.15 mm QUALITY

Filament: Prusa PLA

Nozzle temp: 205 °C (default is 215 °C, but lower eases stringing and has never been a problem for many past prints)

Nozzle size: 0.4 mm

Full config: https://pastebin.com/ECa6KkYK

0scar
  • 32,029
  • 10
  • 59
  • 135
Slight
  • 141
  • 6
  • Just to make sure, did you print the whole sword as a print-in-place? If I follow the link to the print files it shows that the prints are printed apart from each other. – 0scar Jul 19 '22 at 07:32

2 Answers2

1

After some trial and error I found that the issue was stringing due to excess moisture in the filament from being stored outside of a sealed low-humidity container for long periods.

After placing it in a heated dehydrator for 2 days, my next print had low stringing and did not bond interlaced parts together significantly.

Slight
  • 141
  • 6
0

You did well to decrease the temperature. You could go even lower to 200°C As you noticed, You really have a little bit of stringing between the elements. That's what binds the parts together. Many times when you print only a single part this will be no problem. With many nested parts, you retraction really has to be set to optimal values.

Try increasing the retraction distance in the slicer.

Hacky
  • 445
  • 2
  • 11
  • I did try that before the post, but thank you for posting. I believe I found the reason for it which was excess moisture in the filament because after doing a "baking" session I was able to reduce the stringing that was causing this. – Slight Jul 31 '22 at 00:51