Family Table Instance Shows Suppressed Feature

[dgschaefer]

WF4



I have a family table driven assembly with several assy level cuts. The
last assembly feature is a dependant mirror of several features prior to
it. In the generic, all features are suppressed, but all features are
resumed in 2 of the 3 instances.



In the two instances that have the final mirror set to Y in the family
table, it will not resume. It shows up in the model tree, in the
instances, as suppressed. If I resume it, it only stays resumed until I
regen the instance again.



I've tried toggling it from Y to N and back in the family table, I've
tried removing it from the family table and adding it back it, but it
won't resume.



Any ideas?



Doug Schaefer

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[davehaigh]

Doug,
You said "In the generic, all features are suppressed" Are you actually intending to use the generic as model like the instances?

I create an instance for each part that will be used. The generic never is used in an assembly.

David Haigh

[kimndave9]

Make sure the feature is eligible for resuming.

If it depends on a feature that is suppressed, it will also be suppressed.

[dgschaefer]

Yes, it is being used. Normally I follow your practice. In this case,
the generic was in production prior to it being a generic. We've added
the assembly features to it to represent various alternate versions
created by machining features away after assembly. All the features
were added to the family table. I then suppressed those features in the
generic so that it would remain unchanged, at geometrically.



To answer David's question, the features are all or none in the
instances. Nothing is suppressed in the instances, except this mirror
feature which is explicitly called out as 'Y' in the family table.



Doug Schaefer

[dgschaefer]

Assuming the mirror was the issue, I remodeled the features to eliminate
the mirroring. Now, two other features (a curve and a child of the
curve) are failing the same way. It is not a parent child situation for
this curve as there is another identical curve with identical references
but different dimensions that does not fail.



If the features are resumed in the generic, they are resumed in the
instance, if suppressed in the generic; they are suppressed in the
instance. Maddening, I need to get this out to the client and I cannot
get this to work.



I submitted it to PTC, but I've got to find a work around faster than
they will likely get back to me.



Doug Schaefer

[ptc-141274]

I know this was mentioned already, and I could be off base here.

Realizing you are using your generic in the assembly (not by your choice), could you create another instance that mimics the current generic, and then replace the generic with this new instance?

Now you can play around with the generic and maybe solve your problem.

Doug

[dgschaefer]

Doug,



That thought had occurred to me, however I really didn't want to go to
my client to see what sort of headache it will cause to replace that
generic with an instance.



However, I got it fixed, accidentally. While on a screen sharing with
PTC, he had me create a new sketch and a new extrude from that sketch
and add it to the family table to reproduce the problem. It did, but
unexpectedly it fixed the problem on the other features. So now I have
'dummy' features that don't work but my good features do. Furthermore,
when I deleted the 'dummy' features, the good features continued to work
fine. Go figure.



So all is good - for now, but we still don't know what went wrong. I'm
going to send them the assy once I have an NDA in place on this with
PTC.



Doug Schaefer

[ikamster]

Doug,

All of your "dummy features" have to be referencing a feature that is not being resumed in the instances. There must be something that did not get listed in the table. I've run into THAT before.