whats wrong with the nx503.2 wave linker
whats wrong with the nx503.2 wave linker
(OP)
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
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





RE: whats wrong with the nx503.2 wave linker
RE: whats wrong with the nx503.2 wave linker
RE: whats wrong with the nx503.2 wave linker
RE: whats wrong with the nx503.2 wave linker
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?
RE: whats wrong with the nx503.2 wave linker
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
RE: whats wrong with the nx503.2 wave linker
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
RE: whats wrong with the nx503.2 wave linker
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/
RE: whats wrong with the nx503.2 wave linker
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