NX... A mind of its own? Replacing components on its own.

[ingallspw]

Here's what I got...

I open up an NX assembly. Inside that assembly it has a Center Disk. That CD is often replaced by another very similar CD. Now once and a while I'll have more than one assembly open at a time all with different center disks.

I've noticed that sometimes when I replace one CD in one assembly all the assemblies have that CD.

Or I've also noticed that it will do that by simply opening another CD, modifying it and saving it... when I come back to the assembly the CD part number has changed to the one I just saved.

I may not have the logic of this exact as I usually notice it after several minutes or hours have passed since I did the above steps.

I am sure there is some sort of logic or maybe something I am doing wrong but it's fairly random when this happens and I am not sure exactly what constitutes this action.

Anybody have any ideas as to what to do or not to do to get this to happen?

Oh also (if it matters) the center disk I referred to above are so similar that we usually just copy it and save it as the next part number so all the surfaces, lines, etc will be the same and update easier when replacing components.

Thanks!

Keegan

 

[cowski]

If you are performing a 'save-as' to get the next center disk, it will replace the old CD with the new CD in any assemblies that are open and use that CD. As an alternative you could copy the file in windows explorer, rename it then open it and edit as necessary. This process won't swap any components out in assemblies.

If you are not doing a 'save-as' then perhaps you should look into your loading options. There is an option in there to substitute components; depending on your part numbering/naming scheme this may have an effect.

 

[hudson888]

If you're running NX Native and you have two files with the same name, even if they live in different directories NX is going to allow you to open up one or the other and not both. That may explain your problem.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

 

[Berserk]

Hello,

All I can think of is that the CD is on a sub assembly and this sub assembly exist on different top assembly. When a component (CD) is replaced on the sub assembly, it would affect the other top assembly unless they have different sub assembly part numbers.

UGNX5.0.4.1 MP6 \ WinXP-SP3
Productive Design Services

http://www.productivedesign.com