Designing and using reusable parametric components

[denis.itskovich]

I was not able to find any clue about how to create parametric component, whose parameters can be set one inserting instance of such component into another model. For example: I'm modeling 3D printer frame, made of extrusion profiles. So I'd like to create a component for single extrusion profile piece, where its length is parametric. I'd like to insert multiple instances of this component into the model of the entire frame, but to choose each time different value for the length parameter (actually, to set the lengths of the profiles to be calculated from the frame parameters). 

I was able to create profile component with length parameter and saved it as a stand-alone model (let's call it "Profile model). I'm able to change parameter value when editing Profile Model. But when I insert this component into another model (let's call it "Frame Model") - the length parameter is always the one which I set when saved "Profile Model" and I was not able to find a way to change it for each inserted instance independently. 

Is what I am trying to achieve possible? Is the any other way to reuse components, while keeping them parametric in a way that parameter can be defined when used and not when designed?

[jhackney1972 · Accepted solution]

I hope I have understood you question correctly, if I did not please correct me and I will try again.  Please see the attached screencast for the process I think you want.

[denis.itskovich]

Hi. Thanks for your answer! This definitely helps! Is there a way to get the same result, but without breaking the link? I would prefer to keep the link in order to be able to continue making changes in the source component and to apply them seamlessly to all instances

[jhackney1972]

I think you are out of luck on that desire.  If you do not break the link, you cannot change the parameter inside the assembly because the part is just a representation.  The only way to do what you seem to desire is create all your components, with the parameters you want, link them to your assembly and then open them up individually, from the assembly, modify the parameter, save and update.  Seems like a lot of banjo motions but I do it all the time and it works well.

[rafal_kruszyna]

And here are the significant problems with Fusion 360 exposed: the parameter system is weak. In the QML language of Qt, this is much better resolved. There, you create a component file where you define the parameters of that component. But what's important in QML is that parameters are assigned to the node, not to the entire file. In each project node, you can have any list of parameters, and additionally, each node can have its own ID, for example, id = "red_bolt", which is a great convenience because you can refer to this parameter elsewhere in the document, for example, length = red_bolt.x. Parameters assigned to the node significantly facilitate work, and the ability to identify a node by its ID is a great feature. Then, when we want to use a particular component in an assembly, we simply add the component to the assembly twice, and on the node of each component, we set the parameters arbitrarily. This way, we have two "screw" objects in the assembly, each with its own set of parameters that we can freely change, and there's no need for "unlink" or other similar workarounds.

[rafal_kruszyna]

And here are the significant problems with Fusion 360 exposed: the parameter system is weak. In the QML language of Qt, this is much better resolved. There, you create a component file where you define the parameters of that component. But what's important in QML is that parameters are assigned to the node, not to the entire file. In each project node, you can have any list of parameters, and additionally, each node can have its own ID, for example, id = "red_bolt", which is a great convenience because you can refer to this parameter elsewhere in the document, for example, length = red_bolt.x. Parameters assigned to the node significantly facilitate work, and the ability to identify a node by its ID is a great feature. Then, when we want to use a particular component in an assembly, we simply add the component to the assembly twice, and on the node of each component, we set the parameters arbitrarily. This way, we have two "screw" objects in the assembly, each with its own set of parameters that we can freely change, and there's no need for "unlink" or other similar workarounds.

[TrippyLighting]

@rafal_kruszyna 

What you are describing can be achieved and is the sole purpose of Configurations in Fusion 360. It is only open to users of paid subscriptions, however.