Control iParts length using iLogic

[Anonymous]

Hello All,

I have an aluminum door frame with four different ipart driven extrusions that make up each side. I want to be able to use iLogic to drive these part lengths. I've been able to control a few parts that don't have an ipart tables using 

Parameter("154:1", "Length154") = (OverallWidth / 4) -3

 When i try this with an iPart part I get this error message: Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED)). 

How would i go about using iLogic to control an iPart member length? Is it even possible? 

Thank you

[johnsonshiue]

Hi! It is tricky to use iLogic rule within iPart. It is because iPart members are supposed to be totally driven by iPart factory table. iLogic rule within the iPart factory is like another driver which can conflict with the author table. Please share the example here so forum experts can take a look.

Many thanks!

[Anonymous]

I've attached a basic representation of what I'm trying to do. The goal is to be able to pick a member from the iPart table and then change the extrusion length of the profile based on an equation driven user parameter in the assembly. 

[johnsonshiue]

Hi Dan,

Many thanks for sharing the files! I think I know what you are going after. I have seen such frame assembly using iAssemblies and iParts. I have also seen users using iLogic rules only.

Like I said before, iAssemblies and iParts are meant to create library components. Each component should be clearly defined and driven by the author table. There should not be any other variables or drivers to drive the iComponents. Any inter-component relationship, association should be avoided.

I believe you should simply use iLogic instead. The way to do it is straight forward. It looks like you know quite a bit of iLogic already. You should focus on creating one configuration. Then you use parameters and iLogic rules to drive geometric variations. Once you are done with a configuration, use iLogic Design Copy to spawn another set of files.

Certainly, you should be able to keep using the assembly you attached as is. But, the trouble is that you can end up with out-of-sync issues, meaning the iPart members do not react to the change request by iLogic rules. It can get complicated and hard to understand.
Many thanks!