iAssembly - Flexible / Adaptive / Custom

[NachitoMax]

Hey

I have made an iAssembly, i rarely use them but for this particular job, i have a stack of drawers that all are the same construction detail except for the material thickness, height & width. How can i make my new iAssembly so that i just need to input 2 values

DrawerWidth

DrawerHeight

MaterialThick

all of the parts are iparts and assembled in my assembly. they change ok when selecting a predetermined table row but i need it to be faster and flexible enough to receive my inputs (at any size)

Thanks

[NachitoMax]

Hey

I have made an iAssembly, i rarely use them but for this particular job, i have a stack of drawers that all are the same construction detail except for the material thickness, height & width. How can i make my new iAssembly so that i just need to input 2 values

DrawerWidth

DrawerHeight

MaterialThick

all of the parts are iparts and assembled in my assembly. they change ok when selecting a predetermined table row but i need it to be faster and flexible enough to receive my inputs (at any size)

Thanks

[johnsonshiue]

Hi Nigel,

iPart and iAssembly are designed to create library components. It means the components are clearly defined and totally driven by the author table. The components are for reuse purpose.

So, Flexible, Adaptive, and Custom are somewhat contradicting to the nature of table driven. Because of being table driven, it is very hard to establish inter-component relationship.

I believe you will be better of using iLogic. You can use iLogic rule to drive parameters in the parts from top-level assembly. To create another variation, simply use iLogic Design Copy to make a new set of files.

Many thanks!

[johnsonshiue]

Hi Nigel,

iPart and iAssembly are designed to create library components. It means the components are clearly defined and totally driven by the author table. The components are for reuse purpose.

So, Flexible, Adaptive, and Custom are somewhat contradicting to the nature of table driven. Because of being table driven, it is very hard to establish inter-component relationship.

I believe you will be better of using iLogic. You can use iLogic rule to drive parameters in the parts from top-level assembly. To create another variation, simply use iLogic Design Copy to make a new set of files.

Many thanks!