At long last! The final part of my little "iFeatures & Autodesk Inventor" series (at least for now)!
In this final post, I'll discuss taking and iFeature, and driving it via a table.
But first of all, why drive an iFeature with a table? What does a table do for us?
Well the single biggest reason to use a table driven iFeature is to create is to create a consistent series of choices for features that vary in predictable ways.
|An Example of an iFeature Table|
For example, lets say there's a mounting hole of three consistent variations. It may have two different size holes, but the holes all expand in intervals of a given increment (.125 inches for example).
|An example of different holes (yes, I know the biggest one is 'too big'|
If a non-table driven iFeature is used, the different diameter holes could be mixed and matched.
|The 'standard' iFeature screen|
In other words, a "create a combo" situation could arise, and a non-existant hole created.
If a table driven iFeature is used, then the mounting holes can be called out by a specific value, such as an "tool number", and a consistent set of holes can be placed.
Special fields can also be created, so institution specific criteria can be used for selecting an iFeature. For example, in my video, I use Tool Number.
But enough of the describing! Let's switch to the video, and see how these tables can be used!
And on a final note.... Who knows what an iFeature was called before it was named an iFeature? Hint: it's the reason an iFeature has the file extention "*.ide"!