About Primary and Secondary Occurrences of Tube and Pipe Components
A primary occurrence is the driving occurrence of an exclusive tube and pipe components that can be a primary runs assembly , pipe run, flexible hose assembly, or route. It allows for most of edit options.
Secondary occurrences can be constrained as a rigid body and are not editable. Route secondary occurrences cannot be populated. If all routes in a pipe run are non-adaptive, the Populate Route command is not available.
A primary occurrence can have more than one secondary occurrence. Changes to a primary occurrence automatically update all secondary occurrences. To reuse or populate, you must make secondary occurrences adaptive.
In a normal tube and pipe assembly, use any of the following ways to place secondary occurrences from an exclusive tube and pipe component:
- Copy & Paste
- Drag & Drop
- Place Component command on the Assemble tab or context menu, when the top assembly or primary runs assembly is activated.
- Pattern Component command on the Assemble tab or Component
Pattern command on the context menu on a component in place, when the top assembly or primary runs assembly is activated. - Click File Save Copy As.
- Design Assistant
- Autodesk Vault Basic
How do tube and pipe secondary occurrences in the copy and reuse workflow differ from normal Inventor secondary occurrences?
To ensure you can continue following the tube and pipe copy and reuse workflow, you must place secondary occurrences of primary runs assembly inside of the top assembly, secondary occurrences of runs inside of the active primary runs assembly, and secondary occurrences of routes and flexible hose assemblies inside of an active run.
A placed tube and pipe secondary occurrence always goes to the active assembly hierarchy, but you cannot copy the entire active assembly hierarchy and place it into itself.
How do secondary occurrences differ in the reuse workflow and configuration workflow?
Both reuse workflow and configuration workflow involves secondary occurrences of tube and pipe components. The Make Adaptive command makes a secondary occurrence adaptive, but two workflows differ in the following aspects:
How are new primary occurrences named in the reuse workflow and configuration workflow?
In both reuse and configuration workflows, you can determine to adopt a new unique name for new adaptive primary occurrences when applying the Make Adaptive command. Be default, file naming conventions are different.
In the copy and reuse workflow, the default new adaptive primary occurrence has a file name with an incremented index number based on all the existing primary occurrences. Both file names and Model browser follow the standard naming convention as documents are normally created. For instance, a primary runs assembly currently has three runs namely Run01, Pipe Run 2, and Pipe Run 3, one secondary occurrence of Run01, and one secondary occurrence of Pipe Run 3. Making two secondary occurrences adaptive will create two new files for Pipe Run 4 and Pipe Run 5 if you do not apply your own names.
In the assembly configuration workflow, the default new adaptive primary runs assembly has a file name of the last active primary runs assembly with a prefix of configuration_name.