Ilogic .ipt .iam & Excel

Ilogic .ipt .iam & Excel

BDUB2012
Enthusiast Enthusiast
462 Views
2 Replies
Message 1 of 3

Ilogic .ipt .iam & Excel

BDUB2012
Enthusiast
Enthusiast

I have a floor steel part (.ipt), a floor refractory part (.ipt) and a floor brick part (.ipt). These three parts are assembled in a floor assembly (.iam) and this assembly is assembled in a top level assembly (.iam). The features that I want to control in each of the three parts are the thicknesses of each part and a cirecular hole cutout in each part. I have an excel spreadsheet that calculates the values for the thickness and the circular cutout for each part based on additional information in the excel spreadsheet. I am able to go out to excel and read the cell values that I need for the thickness and the circular cutout for each part. My question is how is the best way to organize the Ilogic code in the assemblies and parts. Is the best way to have all the parameters that define the thickness and the circular cutout of each part  defined in the top level assembly and have an ilogic code in the top level assembly that goes out and reads the values from the excel spreadsheet and then have the Ilogic code in the top level assembly push the values down to the child assemblies and parts. Is there a better way, maybe have Ilogic code in each child assembly and parts that goes out and reads it's own values from the excel spreadsheet. What is the best way to organize this. Thanks in advance for all responses. 

0 Likes
463 Views
2 Replies
Replies (2)
Message 2 of 3

Anonymous
Not applicable

Many ways to do this but the approach that I would use so that it is easier for me to manage and remember 6 months down the road is to control majority of the info from the top level assembly. This way there's only one place to go when you need to update the rules. Also since you are reading an excel file, I would try to read the file once verse multiple times due to each subassembly reading the same excel file. Reason is each time you are reading the excel file, an excel process is started taking memory. So if multiple subassemblies are reading it then Excel is being launched and closed each time. Basically read the excel data in the top level and then push the calculated values into the parameters in parts. I would definitely create user parameters in the parts (thickness, OD, Dia, etc.). This will make it easier to find the parameters from the top level assembly verses d12, d15, etc. Since your parts are in a subassembly, use Parameter(****'y MakePath) from the code snippets to get to the parameters in the part while in the top level assembly. Others can chime in on their approach but from the info that I know, that's what I would do. Hope that helps.

Dan

0 Likes
Message 3 of 3

BDUB2012
Enthusiast
Enthusiast

I appreciate the quick response and definitly agree with naming parameters. I have done this before a couple of months ago but it seems like everything I do in inventor I end up doing several times until I am happy with the results but I guess that is common. Hopefully I can try this again this weekend and have results next week. Thanks.

0 Likes