Skip to main content
T
TL_100362466-Contributor
6-Contributor
June 3, 2025
Question

Multiple Assy Configurations using Constraint Sets & Family Tables

  • June 3, 2025
  • 4 replies
  • 814 views

I have an assembly that needs multiple configurations. In one configuration component A is assembled to component B. In another configuration, A is assembled to component C and B doesn't exist or is suppressed.


I think using a Family Table and Constraint sets would be a great solution. In the first FT instance I have a Constraint Set that constrains A to B and in a second instance, I have another Constraint Set that assembles A to C. However, the problem is that when I suppress B in the second instance, A becomes suppressed as well. I'm assuming this is because the Constraint Set that is used in the first instance makes A a child of B. Is there any workaround for this?

 

Is there any discussion about having disabled Constraint Sets severing or negating parent/child relationships? It seems to me that would make sense and open more flexibility when using Creo assemblies.

 

Currently using Creo 11

4 replies

Dale_Rosema
23-Emerald III
Dale_Rosema23-Emerald III
23-Emerald III
June 3, 2025

Something I have done (and it may not be the best practice) is have (2) instances of "A" in the generic assembly. One is constrained to "B" and the other is constrained to "C". For the first instance in the family table I have the first "A" and "B" and in the second instance I have the second "A" and "C".

That way you have one configuration in the first instance and the second configuration in the second instance.

 

As you have learned, if a model is not in the instance, anything constrained to that model is no longer in the instance either since it is constrained to nothing.

    tbraxton
    22-Sapphire II
    tbraxton22-Sapphire II
    22-Sapphire II
    June 3, 2025

    Using a skeleton and constraining all of the components (A,B) to the skeleton model is another option and the one I would use. By constraining to the skeleton there are no direct parent child relationships between the components.

     

    A family table for this type of thing can be unstable and cause problems with Windchill.

      Dale_Rosema
      23-Emerald III
      Dale_Rosema23-Emerald III
      23-Emerald III
      June 3, 2025

      FYI: I work for a small company - 2 seats and no Windchill.

      (... and simple designs)

      M
      MartinHanak24-Ruby III
      24-Ruby III
      June 4, 2025

      Hi,

      workaround:

      1. assemble A as first component
      2. assemble B to A
      3. assemble C to A
        A
        anursinghCommunity Manager
        Community Moderator
        August 11, 2025

        Hi @TL_10036246,

         

        I wanted to see if you got the help you needed.

        If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
        Of course, if you have more to share on your issue, please pursue the conversation. 

         

        Thanks,
        Anurag 

        Terms & ConditionsAccessibility statement