Have you tried to create 2 distinct constraints between your 2 rooms and use the family table to delete/activate the one you are interested in depending on the config?
Thanks, it's a good idea, but between my instance in the rest position and in the actuated position, the order of the components in my model tree changes. So I don't think your idea can work What do you think??
Thanks s.b, my colleague is looking at creating a parameter.
The constraint is that one must not use a rating.
We try to create a PMH or PMB parameter and write a relation that says: If the parameter is LMP the difference between the contact between the planes is equal to a reference dimension measured in TDC.
Except that its increments, and its addition the rating.
In PMH, the black part is in plane/plane stress on the lower surface of the red part. A rating is a reference rating. (the result of the assembly and which cannot be entered by hand).
In PMB, we must make sure that the plane/plane constraint cancels out and that it comes into contact with the plane^/plane at the top. (if necessary and especially if possible, we can use the reference number)
In fact, you want A to update itself if you evolve the assembly, right?
If, for example, you make a sketch in your assembly that rests on the faces of the different parts, you can get dimensions (reference) x= black part/green part opening and y= red part thickness.
From there, A = x-y that you reinject into your relations with the Boolean method proposed by s.b
To be honest, it seems to me to be at least as risky to pass on as entering a rating by hand.