Unable to assign a part-driven value

Hello
I'm looking to create a family table for an epicyclic gear crankcase cap.
This part has 3 family parameters: a diameter of the part, the number of fixing screws and the diameter of its screws.
My first two parameters change without problem depending on the instance of my part but the diameter refuses to change.
when I click on relations it writes to me under the formula that helots the diameter "Impossible to assign a value driven by a part.".
I specify that the diameter of the hole is an MxXy so I wonder if it doesn't come from there.
How do you make the holes change size?
Thank you in advance.
Kind regards

1 Like

Hello

When you select your diameter parameter to add it to your family table, the base value should appear for the generic. Is it of the same shape?

What is the y-value (pitch, depth)? It probably needs to be managed by 2 separate parameters.

Hello

As far as the variation of a tapped hole is concerned, shouldn't we go through a relationship, for example:

If Øpiece>50 then Øhole=M16x1.5

 

Because piloting a tap by family table I have never done, but maybe it's possible.

 

Thomas

 

Hello

 

If you use the Pro/e Hole function, there are lock dimensions inherited from the screw table.

You can see them by looking at the Function Information.

 

I advise you to make the shape (for example a screw countersink) with a sketched hole.

You can put the values in the family table.

 

@Tomalam

A family table on tapping is possible. You don't have a family table for nuts? ;)

 

S.B

2 Likes

And no, I can't. Before I arrived at my current company the nuts were already created one by one, and if I make a table I couldn't put the same name! ^^

Hello

Drilling controlled by drilling standards (HOL file) cannot be controlled by a family table. The solution is therefore to create simple holes to which a cosmetic thread function is added. The dimensions of these functions can then be controlled, either by parameters or by relationships, and included in the family tables.

Thank you for your answers.

In the end I did two holes in my generic part and then depending on the instance I activated one or the other