adndevblog.typepad.com

Tips for creating large assemblies using Inventor API - Manufacturing DevBlog Manufacturing DevBlog The resource for software developers working with Design, Lifecycle and Simulation technologies from Autodesk. Home Subscribe Follow Useful Links Autodesk About this Blog « VBA of Inventor 2014 cannot work | Main | Inventor API: Intersection of Two Bodies » 07/28/2013 Tips for creating large assemblies using Inventor API by Vladimir Ananyev This DevNote touches upon some general tips on creating large assemblies using Inventor API. This does not deal with hardware configurations or recommendations. 1. Use an in-process program such as an add-in. An out-of-process executable substantially deteriorates performance. Add-ins implemented with .Net can have a negative influence on performance because .Net runtime reserves 100 MB of address space away from Inventor. 2. Create the assembly with the assembly document invisible. 3. Make all work planes invisible. 4. Consider Substitute Level of Detail representation to use a part file in place of the assembly to improve capacity. 5. After applying constraints, remove them if the problem we are solving is only to position the components and delete the constraints. This is because when a constraint is applied, Inventor constraint solver checks for all the previously applied constraints. 6. If constraints need to be retained, one approach is to group the parts into subassemblies. This greatly decreases the maximum length of recalculated constraint chains. 7. If possible, identify unique and repeated subassemblies. If several subassemblies are repeated, structure the program so that only unique subassemblies are created and they are reused to represent the repeated subassemblies. 8. As large assemblies with several subassemblies are being generated, save, close, and reopen them. This will reduce the burden of saving a large assembly in one shot in the end. It has often been observed that it takes more time to save an assembly than to create it. If a subassembly needs to be made visible for some reason, then zoom into an area of constant color/ texture before saving it. This can have a positive influence on the saving process. 9. In case of designing an assembly configurator, input data is normally obtained from other programs such as Excel or Access. In this case, it is advantageous to read all the relevant data from Excel/ Access first and store them as global variables. This obviates the need to access Excel/ Access several times. 10. Whenever an object is no longer going to be used, set it to null or nothing. This releases memory (which is a constraint in large assembly creation). 11. If a 2D drawing (IDW) is generated from a huge assembly, it will be beneficial to write a program to close the assembly, reopen it invisibly, and then create the drawing. Posted at 02:07 PM in Inventor , Vladimir Ananyev | Permalink | | | Comments Tips for creating large assemblies using Inventor API by Vladimir Ananyev This DevNote touches upon some general tips on creating large assemblies using Inventor API. This does not deal with hardware configurations or recommendations. 1. Use an in-process program such as an add-in. An out-of-process executable substantially deteriorates performance. Add-ins implemented with .Net can have a negative influence on performance because .Net runtime reserves 100 MB of address space away from Inventor. 2. Create the assembly with the assembly document invisible. 3. Make all work planes invisible. 4. Consider Substitute Level of Detail representation to use a part file in place of the assembly to improve capacity. 5. After applying constraints, remove them if the problem we are solving is only to position the components and delete the constraints. This is because when a constraint is applied, Inventor constraint solver checks for all the previously applied constraints. 6. If constraints need to be retained, one approach is to group the parts into subassemblies. This greatly decreases the maximum length of recalculated constraint chains. 7. If possible, identify unique and repeated subassemblies. If several subassemblies are repeated, structure the program so that only unique subassemblies are created and they are reused to represent the repeated subassemblies. 8. As large assemblies with several subassemblies are being generated, save, close, and reopen them. This will reduce the burden of saving a large assembly in one shot in the end. It has often been observed that it takes more time to save an assembly than to create it. If a subassembly needs to be made visible for some reason, then zoom into an area of constant color/ texture before saving it. This can have a positive influence on the saving process. 9. In case of designing an assembly configurator, input data is normally obtained from other programs such as Excel or Access. In this case, it is advantageous to read all the relevant data from Excel/ Access first and store them as g