Can saved shrinkwrap be updateable?

[TomM]

Hi,

Creo 9, Windchill 12.1.2

I have a need to create (lots of) simplified files (to protect IP) in order to send them out. There doesn't seem to be a good solution which fulfills everybodies' needs but here's what I would love to achieve.

Save as -> Shrinkwrap doesn't have an option to choose a "subset" like the feature-creating version of the tool does. This sucks because once I create a shrinkwrap file I don't seem to be able to edit it in any way(add/remove parts and it won't update if a part is updated). 

So 1) Am I missing something or saved shrinkwraps can't be updated because they lack the parent-child relationship to the original assembly?

Based on the above - in order to have control over what's included in the shrinkwrap I create a feature shrinkwrap inside the assembly. Then I create a save-as shrinkwrap of the feature-based shrinkwrap. This kind of sucks cause the feature stays in the assembly...and the part-type shrinkwrap doesn't update. But is necessary because I need to make further part-level adjustments.

2) Is it an ok-ish approach or is there a better way?

The ideal would be if I could:

a) have an assembly

b) create a part file with a shrinkwrap

c) have the shrinkwrap update if anything related in the assembly updates.

Any input welcome!

Just a note - I know instead of creating feature-shrinkwrap I can create a simplified rep but for some reason shrinkwraps miss some surfaces (even with detail set to 10), Both ways don't cut it anyway cause I need to edit features further down the line in the model environment.

[tbraxton]

Yes. Shirinkwrap features are associative by default. If your SW features do not have dependencies, then they were intentionally created with no dependency.

Shrinkwrap Associativity

Shrinkwrap features are associative and automatically update to reflect changes in the parent copied surfaces. Shrinkwrap features are updated when components have been added or removed. You can control the dependency of the Shrinkwrap feature on the surfaces it references. The independent state is useful if you wish to avoid unwanted regeneration cycles.

When a sub-feature of a shrinkwrap fails, the shrinkwrap feature will also fail. Right-click the failed feature and redefine the references.

Copied Geometry Update—Set geometry dependency of the Shrinkwrap feature. The Shrinkwrap feature is dependent, by default, on the source components. If the size or position of the original component are changed, the Shrinkwrap feature updates accordingly.

[TomM]

You're talking about the "feature" shrinkwrap, not the "part" shrinkwrap. When saving-as you can't choose the associativity as far as I can see.

When it comes to the "feature" shrinkwrap you can only edit the shrinkwrap settings but you can't edit the geometry (using flexible modelling for example). And I need that.

Edit:

Oh, I've found the answer....

 

[tbraxton]

Yes, the reason is as follows:

Shrinkwrap Models (save as shrinkwrap)

A shrinkwrap model is an automatically created non-associative, simplified copy of a selected part or assembly.

The two main uses for a shrinkwrap model are the following:

• Create a simplified model used to share geometry with vendors or customers while eliminating any proprietary detail you do not want to share.
• Create a lightweight version of a complex part or assembly to be used as a reference or packaging model.

If you need associativity, then saving as shrinkwrap is not going to work.

[tbraxton]

I just saved a part as a shrinkwrap model. I am able to use flexible modeling features in the derivative model in Creo 7.0.10.0

You will need to elaborate on exactly what you need to filter in order to protect your IP. There are probably other ways to deal with this other than SW if it does not work for you.

[pausob]

Perhaps I am misunderstanding, but I am thinking you should be making the "shrinkwrap part" by 1) assembling an empty part into your assembly, 2) activating it, and 3) using the shrink-wrap feature to generate the geometry?

The geometry in the "shrinkwrap part" can be modified using flexible-modeling tools:

If the parent assembly changes (in a significant way):

then indeed the "shrinkwrap part" will need to be updated manually:

 

-->