WAVE links not captured during 'cloning'

[acciardi]

Hello all...

I performed a clone operation today on a cast/machined model and I'm confused by what happened.

The original cast/machined relationship was created by building an empty assembly, then adding the casting model, then wave linking the casting model into a new part using the wave geometry linker on the assembly toolbar, and selecting the casting solid body to link. I then add machining features to the new part, and voila, there is my machined model.

When I cloned these parts, the new machined model was still wave-linked to the original casting model. I wanted it to point to the new (cloned) casting model.

I then went through a fairly convoluted process of re-parenting the new machining model to get it to point to the new casting model. I finally got what I wanted, but there was much cursing and hair pulling and pining for my old Pro/E "duplicate" command.

Did I miss something during the clone operation? I need to do this a few more times and really don't want a repeat of todays ordeal.

Thanks for any help,

Ed

 

[gieter]

I do the same kind of operation quite often and can't remember having problems of this kind.

What load options do you use?

I agree with you that when a link is messed up, it's very hard to get it right again.

 

[acciardi]

We're using TCe 9.1.3.5, and I usually set the load options to "as saved".

What is also odd is that when I close all files and load my cloned machining model, I now get the helper assembly that I used to do the wave linking pulled into session. The assembly is empty, but it gets retrieved every time. I seem to have created a dependancy to it.

Ed

 

[gieter]

I'm sorry, I've no experience with TC.

What I ment with the load options is in fact the behavour of the assembly components. You can leave them unloaded, but I suppose the clone action will cope with this.

 

[mjcole]

Regarding Load options I have always wished that UG would consolodate these into a setting that would set priorities for load options such as. Loas from directory first then Load models as saved and from specified directories such as C:\Common_Parts... so the users wouldn't have to constantly switch the load options depending on the assembly they are opening. Pro/E loads from directory first then from search paths and you never have to switch your load options.

Although I like Pro/E there are many drawbacks comming from their old school UNIX programming such as no spaces in file paths which they have been far behind in bringing to their software , also PTC has no subdirectory load options in their search pathe like the Name... that is pretty powerful in UG for allowing sub directories to be searched.

Load options have always been one of my major gripes with UG, not to mention Roles which have always perplexed me.

Michael

 

[mjcole]

Thinking about this in another way you should be able to assemble the new cast part before and do a replace feature and select the new cast model as the parent and UG will walk you through the process of picking the references used by any of your machine features where it will show you the old reference name and what features reference it and is a lot easier than doing so after failures.

I do believe in the clone operation you can choose a model that you want to replace the cast model with during the clone operation and you browse to the file that you want to reference I think by default UG assumes you want to keep the same reference.

I'll look through my notes to see if I have some tips for Cloning operations such as a how to process.

Michael