iPart Bearing Housing Model Linked to Another Part

iPart Bearing Housing Model Linked to Another Part

johnster100
Collaborator Collaborator
612 Views
7 Replies
Message 1 of 8

iPart Bearing Housing Model Linked to Another Part

johnster100
Collaborator
Collaborator

Hi, I'm creating some simplified bearing housing models to be used in a layout drawing and thought iParts would be a nice way to create them as more bearings sizes and makes could be added as time goes on. My bearing model shares it's bolt hole locations and bolt sizes to a bearing support model. The bearing support model then shares it's bolt hole locations to a concrete foundation model. How do you manage linking parameters with iparts? I don't understand how to tell models further down the chain that the ipart has changed size Thanks, John

0 Likes
613 Views
7 Replies
Replies (7)
Message 2 of 8

johnsonshiue
Community Manager
Community Manager

Hi! Please share an example here. There should be a solution to your request. I would like to understand it better.

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes
Message 3 of 8

johnster100
Collaborator
Collaborator

Hi,

i've attached a simplified assembly, it contains an ipart bearing and some plates which the bearing is to bolt to.

 

How do i make the plate which bearing bolts change size when i change the ipart in the assembly?

 

thanks,

John

0 Likes
Message 4 of 8

lmc.engineering
Advocate
Advocate

Hi @johnster100 

 

There are a few options available, iAssemblies, iLogic, or adaptive parts. It really depends on what you have going on downstream. Adaptive is likely the simplest solution.

 

Attached is your assembly with an adaptive sketch in your plate file. The sketch projections are from one of the iPart members, not the Factory member (Master). Because the members contain the same geometry the holes will move with a change of part. This method wouldn't work if you were Computing/Suppressing hole features for example.

 

Hope that helps.

 

0 Likes
Message 5 of 8

johnsonshiue
Community Manager
Community Manager

Hi John,

 

Many thanks for sharing the example! I believe the best workflow for you is to use iLogic in the assembly. The nice thing about iLogic is that you get access to all parameters within any component in the assembly. You can easily set up relationship between them.

Go to Manage -> iLogic Browser -> create a simple rule. There is a tree view showing the components. Expand the nodes and you will see the parameters. Right-click on it to capture the status. The rest should be fairly straight forward.

Another way is to leverage Derive or Link Parameter workflow. You can derive or link the iPart member to the bearing support part. Then the parameters can be linked. This workflow can be tricky to deal with when you try to change the iPart to a different member. It will be like changing the Derive source, which is not a supported workflow to begin with. So, I still believe iLogic rule is the best route for you in this case.

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes
Message 6 of 8

johnster100
Collaborator
Collaborator

Hi Guys,

thanks for the reply.

 

So there is no way to place the master in the assembly and change it's size? So that components linked to it would update automatically? 

 

I'm trying to use as little illogic as possible in my models. I thought that most iparts / iAssemblies would end up being bolted to something else, so this would be a fairly common issue?

 

thanks again, 

John

0 Likes
Message 7 of 8

johnsonshiue
Community Manager
Community Manager

Hi John,

 

The issue here is that iPart member file is like a library component. Though its parameters (inherited from the iPart factory table) can be linked to other parts, they are not going to change unless you modify iPart factory table. As a result, the values are like static. More than likely, I assume you will want to use different iPart bearings. You will need to change the link source, which can be messy.

Another workflow is using iAssembly. However, you will need to pre-define the bearings and the fixture parts. You cannot use one iPart member to drive another iPart. It is like the iPart bearing has M4 holes and the iPart fixture also has M4 holes. They are explicitly specified instead having any dependency.

I believe iLogic is the right way to pursue for your case.

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes
Message 8 of 8

IgorMir
Mentor
Mentor

Hi John;

You probably could achieve what you are after if you try to do the following:

1. Create an assembly file and place the Bearing.ipt into it. Save the file to a Master folder. 

2. Start a new Part file and derive that assembly from the Master folder into it. Save the file as, say - Bearing Master.ipt

3. When creating a Base part for your bearing - start a new part file and derive into it the Bearing Master.ipt as surfaces.

     Use the surfaces to build your Base part from them.

What will happen next - if you want to change the size of the Base.ipt independently from Bearing.ipt - in the master assembly just select the member you want the base plate to adhere to. Save the file. The base plate will follow the selection.

 

Cheers,

Igor.

Web: www.meqc.com.au
0 Likes