In-context relations - config specific?

Another thought....

If this assy were used twice in a higher level assy, and the 2 instances used different configs, how would SWX decide which config defined the ICR?

John H

could you just hide the ICR part in the new config and then insert another instance of that part and mate it?

Rich

"Rich" wrote

I'll give that a try. I suppose it could work, because presumably the ICR is tied to a specific component instance rather than to the part itself. Whether it will allow me to add a second instance remains to be seen - it might set up soe unresolvable condition.

Thanks, John H

On a side note, why can't there be more than one in-context feature per part? I have one to determine the length and want another to position mounting holes for another part.

I used to design hinges. The challenge there was to have multiple positions and maintain in-context relations through the early stages of the design process (we removed in-context refs at product release).

I used an envelope (not regular component) in the "design position" to connect all the in-context references to. The "regular" instances had no in-context references, so they could be moved anywhere and not jumble the design.

I prefer envelopes for this purpose because they do not carry through to BOMs or to higher levels of a design.

For an example, download "Hinge.zip" from

Sketch relations, including incontext sketch relations, are configurable. Edit a sketch with incontext relations, launch Display/ Delete relations and in the property page you can see that you can select individual relations and suppress them and at the bottom of the property page you can select which configurations to suppress the relation in.

I am not sure how to do this same thing for planes that are defined incontext (for example a plane in a part that is defined as being offset from a plane in the assembly). And same thing for features that are defined incontext, not sure how to control those incontext relations per configuration.

Hope that helps.

Thanks for all the suggestions - gives me a number of avenues to explore.

John H

"Rich" wrote

Rich,

I am now using this method (first instance suppressed in the alternative assy config), and although it visually gives the result I want, the second instance shows up as olive in the Feature Manager because the "sketch contains dimensions or relations to model geometry which no longer exists".

This means I have permanent errors in my assemblies, which is not something I'm keen to live with.

Any other thoughts?

John H

Scrub that last post - my mistake!

John H

Did you try locking external references after it was defined in the proper assembly config?

TOP

I can't do this (yet) because the assembly is still evolving.

Thanks, John H