Skip to content

Latest commit

 

History

History
66 lines (48 loc) · 3.96 KB

README.md

File metadata and controls

66 lines (48 loc) · 3.96 KB

Creating Custom Threads From a Thread Gauge in Fusion 360

Due to my questionable life choices, I print a lot of non-standard nuts and bolts. I bought a cheap thread gauge and had a hard time figuring out how to turn those measurements in to Fusion 360 thread profiles.

It's actually really easy, but the information is all over the place.

This README collects what I've learned.

Managing custom threads

I recommend using the ThreadKeeper plugin. It makes it easy to manage your custom threads in a separate directory and syncs your custom threads when F360 wipes out its threads directory during most (all?) updates.

This repo is my entire personal threadkeeper directory.

Workflow and tweaking custom threads

When you use Threadkeeper manage your custom threads, you can edit the thread files live and then click Utilities > THREADKEEPER > Force Sync to update the Fusion 360 directory.

It gives a message that you may need to restart F360 for the changes to take effect, but I haven't had to do that in a long time.

If your changes don't show up, you may have malformed XML. As far as I can tell, Fusion 360 silently ignores files that contain malformed XML.

If you make changes to an existing thread profile, those changes will not be reflected in the design until you edit the feature in the timeline. For example, if you change the thread profile for a nut that's already in a design, you'll have to double-click on the applicable "Thread" feature in the timeline and then click "ok"

Using the thread gauge

What do the markings mean?

  • Measurements with "G"
    • 13G means "13 gang" aka 13 TPI
    • 14G 7/16 means 13 TPI for a 7/16" thread
  • No units means pitch in mm
  • Note the angle of the thread
    • Whitworth is 55-deg
    • Metric is 60-deg

Figuring out parameters

scripts/f360-thread-calculator.rb

I wrote this to take input and calculate parameters. I don't recommend using it yet, as input is messy, but it's tested and you're welcome to poke around with it if you know Ruby. I'll be cleaning it up over time and will update here when it's generally usable.