topic Hole Presets Doesn't Save Threads in Inventor Forum

Hole Presets Doesn't Save Threads

APComany — Wed, 01 Jul 2020 22:40:44 GMT

I just started using Inventor 2021. I've been trying to setup my hole presets for the most common holes we use. What I'm finding is a hole preset never saves the thread settings I choose.

Here are my steps:

I am using a part that is set to inches but I tried using a metric part and the behavior was the same.

-Make a tapped M5x0.8 fully threaded through hole.

-Click the "+" icon to make a new Preset.

-Name the Preset: M5 THRU

-Then save the Current Preset

I then close Inventor and restart the program.

-Make a new part with a center mark.

-Hit the hole tool

-When I select my preset the hole behaves like it always does and matches the thread to the size

=Hole size is 0.25in

-Thread is set to 1/4-20

-Also it doesn't save that the thread check box Full Depth

Does the new Hole Preset not save the thread information or is this a bug or am I saving the Hole Preset wrong?

Re: Hole Presets Doesn't Save Threads

karthur1 — Thu, 02 Jul 2020 14:37:50 GMT

I think you are saving the hole preset correctly.

Under Tools > App options, File tab, look at where the presets are being saved to. Make sure that folder is accessible. Maybe even browse to it and see what is there. Mine has one file there named "HoleCmd.preset" that was recently modified because I added a preset hole.

I am using 2020.3 not 2021.

Re: Hole Presets Doesn't Save Threads

APComany — Thu, 02 Jul 2020 16:11:27 GMT

Mine is in the Presets folder and is called HoleCmd.preset. The folder is Read Only but the .preset file is accessible and not read only. It does say I modified it yesterday so it is being overwritten.

Re: Hole Presets Doesn't Save Threads

APComany — Thu, 02 Jul 2020 18:19:58 GMT

This solved the problem:

https://knowledge.autodesk.com/support/inventor/troubleshooting/caas/sfdcarticles/sfdcarticles/Hole-presets-in-Inventor-2021-doesn-t-include-the-type-of-hole.html

Re: Hole Presets Doesn't Save Threads

APComany — Thu, 02 Jul 2020 19:02:48 GMT

Well the file worked until I started making new presets.

I can get the hole preset to work by editing the HoleCmd.preset file.

By looking at the holes that work and the holes that don't it is clear Inventor isn't saving the hole thread info.

I made a preset for an M8 hole going an inch deep with full threads and this is what was saved out:

The thread type input should have values with them.

Here is the same for a M5 hole going an inch deep with full threads that seems to work correctly:

Problem is it will work for a while then override the settings while saving out a new preset erasing the values.

What I'm going to try is to make all the presets check the code then replace the broken taps by hand. Luckily I only use about five taps. This would be real annoying if you used more.

This is the value that determines the thread:

I believe the 27 is the # the M5 is in the drop down menu. Change that value to move the tap up or down.

Re: Hole Presets Doesn't Save Threads

APComany — Thu, 02 Jul 2020 20:09:17 GMT

i checked the file right after it overwrote all the hole presets:

I wasn't saving hole presets this time. I just added a new hole and all my presets were gone.

This is what it replaced them with:

Re: Hole Presets Doesn't Save Threads

dwweekly — Fri, 07 Apr 2023 17:48:13 GMT

I like the idea of presets.
I made probably 50 different ones.
But now they are terribly problematic.

I have counterbored holes that I slightly oversize the "std" to fit for a flat washer.

The callout in the drawing needs the "Size"
Just so no one gets confused, using my presets, the "Fastener Type" should be what I set it to be.
but even the dimensions don't save.
AutoDesk please fix your presets!

This what it should stay as:

This is one of the many forms it scrambles to:
The dimensions are wrong too but they are inconsistant.
sometime correct sometimes not.

Re: Hole Presets Doesn't Save Threads

johnsonshiue — Fri, 07 Apr 2023 23:13:12 GMT

Hi! If I recalled correctly, this was a known issue on 2023. It was reported as INVGEN-64847. The latest status shows it has been resolved on 2024 and the coming 2023.3 update.

Many thanks!