Most designers have parts that differ by size, material, or other variables, although the same design works in many models. You can create these designs as iParts, and then use one or more of the variations.
You use the iPart Author to create part families that contain a table. For standard iParts, each iPart variation is an iPart member, which is defined by a row in the table. When placing the part in an assembly, select the row (member) needed.
In general:
Working with iParts has two phases: part authoring and part placement.
In part authoring, you design the part and define all of its variations. You create a row in a table for each possible version. Each version, called a member, is stored in an iPart factory.
You can create two types of iPart factories: standard and custom.
In part placement, choose a row in the table to represent the appropriate version. An iPart member is generated, using the values in the table row, and inserted in your assembly like any other component.
There are two types of iParts:
You can include:
Standard iPart factories generate parts that have fixed values. Because these parts are reused in many assemblies, we recommend that you store them in a library whose path is included in your active project file. This path is called a proxy path.
The library directory where you want to save the iParts must have the same name as the factory library, preceded with an underscore character. For example, if your factories are stored in a library named Bolts, you can define a library named _Bolts. Autodesk Inventor automatically stores all iParts generated by factories in the library _Bolts. You can define multiple proxy paths, and you can designate them in your project. This technique is helpful if, for example, you want to group table-driven components by category. Redundant paths are shown in red. You can delete these in the project file.
You are not required to specify a proxy path. When iPart members are placed in the assembly, Autodesk Inventor creates a subdirectory in the same directory that contains the iPart factory. For example, consider you have an iPart called Bolt.ipt in C:\temp. When you place an iPart member in the assembly, a subdirectory called Bolt is created (C:\temp\Bolt), and the iPart member file is created there.
Custom iPart members always are stored in a location specified using Browse in the Place Custom iPart dialog in assemblies.
When creating an iPart factory, you determine whether or not parameters can be modified when an iPart is placed in an assembly. Parts created from standard iPart factories cannot be modified. Parts created from custom iPart factories can have designated parameters modified when placed.
Standard iPart factories, such as bolt factories, are not edited. Because bolts are parts that do not change, you select the individual iPart member to use, but you do not edit any values. Usually, standard iPart members are stored in a library. By default, files for standard iPart members are located in a folder of the same name as the factory or in a location designated as the proxy path. For more information, see the section Where to store iParts in the Use iParts in assemblies topic.
If an iPart member is created already, successive placement of the iPart member in an assembly reuses the member file. If a key determines the selection criteria for an iPart member, meaning that the member is defined by fixed values from the factory table, then the iPart member is standard. It implies that there is a finite number of input combinations to create the iPart member. Examples are Nut, Bolt, and Washer.
Custom iPart factories are not edited directly, but you can choose the value for custom parameters when you place a member from the factory. For example, with an angle iron factory, you select the iPart to use, and then modify certain values such as length, width, or thickness. Only the values specified when the iPart factory was created can be modified. Custom iPart members are usually specific to a particular assembly and can be stored anywhere other parts are stored.
The location of files created for custom iPart members is based on the path specified using Browse in the Place Custom iPart dialog box. With custom iPart members, you can input a custom value not contained in the table. Custom iPart member columns appear with a blue background in the iPart factory. You can edit custom iPart members by adding additional features, sketches, and so on. It means that two custom iPart members produced with identical parameters can be different.
Differences at a glance between standard and custom iPart members: |
||
iPart Behavior |
Standard iPart |
Custom iPart |
Parameter values for member creation |
Select from a list |
For custom parameters, typically you can specify any value. For other parameters, you select from a list. |
Location of member files |
Determined when the file is created by subdirectory of the same name or by proxy path |
User-specified |
Number of members |
Finite; one member per row |
Typically infinite; each row can produce multiple members based on different custom parameter values |
Member reuse |
Reused if available |
Always newly created |
Member editing? (Adding features to members) |
No |
Yes |
Specify member file names through the iPart table? |
Yes |
No |
Use Flat Pattern Edit Features? |
Yes |
No |
Work features are useful in iParts to constrain parts in assemblies and to create pins in electrical parts.
Create work features in a part before you transform it into an iPart factory, and then determine which work features to include or exclude in iPart members.
In the iPart Author dialog box, work features have default Include or Exclude settings. You can override the setting by selecting work features to include or exclude in the iPart table. Each row can have work features Included or Excluded. Default settings are:
For standard iParts, each row in the iPart table represents a member. A column for each work feature indicates whether it is included or excluded. You can modify the setting for each row in the table.
Sheet metal iParts include additional attributes:
Effectively taking advantage of these attributes requires additional consideration when the sheet metal iPart is to include the suppression of features which eliminate bends, thereby impacting the bend order sequence.
When a sheet metal iPart factory is created, a default bend order is created. The default bend order depends on whether a flat pattern body already exists within the sheet metal document.
Suppressed Features Within Members - In the case of factory scope editing, the default bend order behaves identically to that of a regular sheet metal component flat pattern, but it may appear to behave differently within the context of the iPart factory. The flat pattern automatically manages the bend order based upon the visible centerlines (modeled or cosmetic) for the active member. Centerlines which are absent for a given member (due to suppression) release their bend order number to maintain a gapless sequence order on the remaining features.
Publishing from an iPart factory produces a DWF file containing an iPart table. Activate the iPart table in the browser, and then use Save As Save Copy As. Specify the DWF file type and appropriate options.