iLogic Form or Rules to export configured assembly

[bevansGP8JU]

Hello all, Taking a stab at iLogic assemblies, and while I can create one that works it won't suffice for what I need.
Disclaimer: Not a programmer and new at iLogic 

The Goal: Create a configurable assembly (in our example, a Door) which
The Issue: I've got a great iLogic configurable assembly, but once i'm done making the door I want, I'd like to export the door, give it a new assembly name and new part names, and move on to the next door.

This is all well and good, until we have a change and have to edit the door, in which case the iLogic tries to reference  the old part number from the 'master' door assembly and fails.

Is there a way to create a copy of whatever current configuration I have, with revised and new part numbers. Such an assembly would then also have to be editable.

Perhaps there's a better way to think about this task, either with iPart or iAssemblies. Either way, if there are resources that will help me create adaptable, sequentially numbered assemblies let me know 🙂

-b

[kelly.young · Accepted solution]

Hello @bevansGP8JU I see that you are visiting as a new member to the Inventor Forum.
Welcome to the Autodesk Community!

You may want to investigate creating a fully parametric model (possibly using derived parts) and then using Vault Copy Design or iLogic Design Copy. This way you can pick and choose which files you want to reuse and which to duplicate, rename, and replace.

Worked well for me by creating templates and then for each customer would use Vault Copy Design to rename the frame, casing, door, etc with customer name at the Prefix.

Please select the Accept Solution button if a post solves your issue or answers your question.

[johnsonshiue]

Hi! I believe you need to use iLogic Design Copy (start Inventor in zero-doc state -> Tools -> iLogic Design Copy). The tool can help you spawn a totally or partially independent dataset to capture the new configuration.

Many thanks!

[bevansGP8JU]

@kelly.young @johnsonshiue 
Thank you for the prompt response and the warm welcome, I've been using 'top level' Inventor for about 4 years, just now getting into the customization bits.

@kelly.young, can I use assembly-level parameters to control part-level features without iLogic? That's how I have it set up right now

Parameter("MM-GARD-XXXXX-005:1", "Length") = sparWidth

For example, this line assigns the parameter "Length" from part MM-GARD to be equal to the assembly level parameter 'sparWidth'
As I understand it, that's the most efficient way to manipulate multiple relevant part parameters from the assembly level document. 


@johnsonshiue Something to note, I was unable to find the iLogic Design tool you were referring to, but perhaps it is because we are using cursed software, Inventor 2014! 

[bevansGP8JU]

Nevermind @johnsonshiue I found the iLogic Design Copy. 
I'll be playing with that today to see if that will solve my puzzle.

edit: Spelling

[bevansGP8JU · Accepted solution]

so after playing with things, It seems that what I want to do, namely export an assembly to a new sub-folder with new names while holding on to the iLogic, is an advanced or even impossible task.

In lieu of a solution, I'm going to implement a workaround involving the Vault Copy Design, and re-naming the parts but with the knowledge that if the assembly needs adjusting, it'll have to be done the old fashioned way of opening the part and adjusting the parameters.

Thank you both, I have another post about iLogic coming up that will be somewhat simpler but I"ll make that a separate thread. 

[blandb]

This is exactly what I am trying to do with no avail. All the documentation, videos, books takes you to where you can make these configurable parts / assemblies, but now what. What do we do with them now that we can swap out and flex things around? Do most "copy design" this master file as a new name and swap out standard parts to make this new configuration?

There has to be a way to do this, but maybe there is a TON of extra programming involved.

We are doing configurable balconies and I have about (20) different sub-assemblies that are custom as well to be cycled in and out of the balcony depending on certain criteria. I dont know if I should have an assembly that ALL this stuff in it first, copy design that so I get all with the new name, then strip away what I dont need when its all configured? Seems like it would be easier to start from a master configurable assy, then save as all assemblies, and drawings based on that. But I cant find ANYTHING lol..

If anyone has any guidance, I'd love to see it, maybe I am over complicating all of this.