- #Does waves nx does the jon update#
- #Does waves nx does the jon software#
- #Does waves nx does the jon license#
The reason the link remained unbroken in your instance is because the WAVE link was created this way.
#Does waves nx does the jon update#
If you open Part B and the part is not updated, it will update as soon as you load Part A into an active session. If you make a change to Part A, Part B will update so long as Part A is open in an active window. Close everything out and you will see that the link will remain unbroken between Part A and B. Save Part B once the link is generated but do not save the assembly (you can if you like but it is not necessary). Create the WAVE link within the assembly linking Part A's geometry into Part B.
#Does waves nx does the jon license#
Since you do not have the WAVE license leave the position dependent. Create an assembly, lets call it Assembly C and assemble Part A and a blank Part B file into the assembly. Let's say you want Part A to be linked to Part B. (Phoenix, Arizona) RE: NX WAVE links behaviour Lockdain my experience with WAVE Linking, the best way for the link to be unbroken is to create a link like so.
#Does waves nx does the jon software#
Siemens Product Lifecycle Management Software Inc. NX Product Manager, Knowledge Reuse and NX Design Now of course, for the target part to pick up any geometric changes in the source part, both will need to be opened in a common NX session, but they need not reside in the same assembly permanently. The position of that linked geometry will be less constrained, so you'll likely need to do some additional positioning with this method, but in the end, removing the source component will leave the WAVE link completely intact and still referencing the source component - even though it is no longer in the assembly: So that's a lot more useful than a "dumb" Unparameterized Body.īUT (.and you'll see where this is going.) if the WAVE link was created as a Position Independent link, then even without the common assembly context, NX can quite easily still link the geometry. The Linked Body feature is still there, albeit in a broken state, and that feature can be edited and relinked or reparented to any new body in the future. Now of course, the linked geometry is not completely "dumb" at this point. with a Position Dependent WAVE link in the target part, removing the source component will indeed give you an alert: Why? Because without the common assembly context - which carries the relative position of the source and target components - the feature can't resolve the position of the linked geometry any more. Removing the source for a WAVE link that is Position Dependent will in fact create the "automatically broken" behavior you describe.
In the WAVE Link creation dialog, there's an option to either "Make Position Independent", or not: So, there's an important principle to understand here. NX 10.0.2 / Teamcenter 10 RE: NX WAVE links behaviour Lockdain (Mechanical) Hopefully this is helpful and I've understood your query! How: Right click on the 'parent component' in "Assembly Navigator" -> "Properties" -> "Assembly" tab -> Tick "Component is Reference Only" If you do any calculations of assembly weight/volume you don't want it included twice. Also this ignores the material of the 'parent component'. Why: So that the 'parent component' is not included in your BOM ("Structure Manager" in Teamcenter). (You could also just hide it or put on a layer but this method is neater and easier to find at a later date)ģ) Make 'parent component' reference only How: Right click on the 'parent component' in assembly navigator -> "Replace Reference Set" -> "Empty". Why: So the 'parent component' is not in the way while your working on the wave-linked instance. I hold down and click in the "Assembly Navigator" to do this. Deselect the relevant 'parent component' (be careful not to select the wave-linked instance). Select the Solid Model reference set (and others if you need to). How: Open "Reference Sets" (from Menu -> Format).
if you are creating two different component variants with some similar topology, like a left-hand and right-hand variant) Why: This is so that you don't see the 'parent component' (only the wave-linked instance) when you assemble your model into a subsequent assembly. There are scenarios when you might just want to do 1 or 2 of these steps.įor instance with an over-moulding then you wouldn't do any of this and you can leave the 'parent component' in. There are three places to hide it which each giving different results depending upon what you are trying to achieve. Instead what you need to do is suppress/hide the original 'parent component' so that you can't see it. Otherwise you have just got a dumb solid.
You MUST keep the assembled 'parent component' in the model so if you make future changes to the 'parent component' then the wave-linked instance will update. Then the wave-linked instance becomes un-associative. If I understand correctly after you have performed the wave-link operation you are removing/deleting the assembled 'parent component' from the assembly structure.
0 kommentar(er)
