whats wrong with the nx503.2 wave linker

[uwam2ie]

I have trouble with wave links ...
Please look at the picture. What's the reason for this new behaviour in nx5.03.2
is it a bug or a feature
thx in ad

 

[cowski]

Please attach the picture you reference in the original post.

 

[uwam2ie]

the picture

 

[moog2]

problem is its in a foreign language !! (sorry just a joke)

 

[uwam2ie]

Ok,
in the partnav you can see failed linked bodies.
I've never seen wave geometrie failed this way.
Broken links ended in former version in broken chain sysmbol.
... whats this?

 

[hudson888]

For wave linked geometry to work it needs basically two outside of your part. Those are the other part with the original geometry which supplied the linked body, and the assembly context in which that link was made. The red cross means that updating the link has failed because something has gone wrong with its ability to find one or the other of the original parameters that it used to build the wave linked geometry. If you can open the other part in the assembly context that you used to make the link, and remember to open the components fully, then you may be able to get the links to update successfully. Otherwise edit the parameters of the link and reselect the bodies that you want to use to recreate the wave links.

I think they are all linked bodies not link mirrors and by the icons. Verbundener Korper, is I think in German or a similar language, Google translator gave me body for Korer which I had already guessed, and Altavista babelfish got connected out of Verbundener, but lost out on Korper. Sorry for my ignorance of your tongue, we english speakers forget to appreciate the effort other make to accomodate us almost constantly on your part.

If they were mirrored bodies you may need to be able to find and reselect the correct datum planes also.

Anyway this is the simplest most likely solution. If it still doesn't work there may be a more serious problem. I don't know what it is, but lets have you at least try what I've suggested and get back to me if you're still stuck.

Best Regards

Hudson

 

[acciardi]

Hudson -

Are you 100% certain about having to retain the context assembly that the WAVE child was created in?

I have not been saving them and my WAVE links are usually fine. I do have to be careful when Cloning to put the WAVE parent at the top of the list of items to be cloned, but I've never cloned the context assembly.

The WAVE child uses the revision of the parent that it was last saved with, irrespective of Load Option. To get the child to reference a different revision of the parent, you just load the parent before the child, then save the child.

Our UGS consultant told us that we shouldn't bother saving the context assembly, mainly because other users may not know about it.

Ed

 

[JohnRBaker]

The so-called 'context assembly' is just that, something that provides the spatial relationships ('context') between the parts which have WAVE linked objects in them. But that's ALL that it does. And as mentioned, there is nothing lost, other than that spatial 'context', if and when those assemblies are deleted.


John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

 

[hudson888]

You have been given good advice, but if you're wave links have reached a error state, which is what the red cross means then the most likely and stable way to edit the parameters in order to get the error to right itself is to re-create the context in order to re-establish everything that the wave link needs to know about how it was created. I think that if you're going to be able to fix this at all you need to start by trying to go though edit edit parameters and re-select the bodies to link. You can't really do that unless you create an assembly context. By what you say you will have most likely used a third part to define that assembly context even if you only did so temporarily. Had you tried to do it with two parts by loading one into the other and creating those links then by removing one part from the assembly the links should automatically have become broken.

If you look at the information for a wave linked body it will say something like the listing below.

Defining Part for Linked Body(2) : model1 (Fully Loaded)
Defining Feature for Linked Body(2) : Block(1)
Position determined by assembly : model3 (Fully Loaded)
Position based upon arrangement : Arrangement 1
Link Status : Up to Date

Under normal circumstances you can maintain links by opening two parts without the assembly context except where model3 reads (Fully Loaded) it would say (Unloaded). But unless as in your case something has gone wrong then normally the wave links will update okay.

Please let us know if you are working in teamcenter or whether the parts were initially created in an earlier version of NX. Sometimes with wave linked geometry it has some bearing. I have not at this stage been able to duplicate your errors.

With regard to whether you need to keep the assembly context long term. I would say if the part is loaded in absolute or in a position relative to some centerline that is both self evident and easy to recreate then you don't need to save an assembly with the linked part loaded if you don't want to. In cases where if you did need to re-create the linking context in order to edit the parameters of that linked feature then perhaps think about saving it in an assembly and maybe suppress the component when you're not using it. Remember also that in your assemblies wave linking can occur between any two parts whether above or below in the assembly tree, so most of the time there would usually be some way to maintain the context, so that you can edit the parameters of a linked feature if the link gets broken or anything else goes wrong.

Best regards

Hudson