Load options

[Javiduc]

Sometimes I want to copy an assembly (For example Assembly "A.A") that I have used or created in a previous project (Project A) to be used in a new project (Project B) . In other software, I was used to copy in windows environment the assembly and its components from the old folder (Project A) to the new folder (Project B) and then add the Assembly A.A to the Assembly B and automaticaly the new Assembly A.A look for its components in folder B or a subfolder inside folder B (if previously Assembly A.A had is components inside a subfolder of project A). I have a problem trying to do the same with NX, because when I add assembly A.A in assembly B, the Assembly A.A is still linked to components in folder A and even renaming folder A doesn't solve the problem. I need to open the Assembly B with "as saved" load options because it also includes other components from other folders.

I have thought that I may clone Asembly A.A instead of copy it in windows explorer but I wanted to know if there is a better way of handling load options or a different recommended workflow in order to do this kind of things because if I clone Assembly A.A I lose subfolders structures or I lose links to external folders where I keep components that I don't manufacture myself like screws, nuts... and I prefer to store them out of project folder.

Thank you in advance.

 

[petulf]

Use the "From Search Folders" with explicitly stated the paths instead of the "as saved" option

For example

C:\project_name\...
K:\standard_parts\...

Adding "..." to the path makes NX search subfolders.

When the done save the Assembly load options to a file which is specific for each project.

 

[Javiduc]

Thank you petulf. What happens if I have two subassemblies in different folders and both of them contains a component with the same file name? With Solidedge I don't have to worry about that because each subassembly takes the components from its own folder and I don't know how I can do something similar with NX.

 

[petulf]

I don't think NX has that capability, thought i might be wrong as i have not tried it. You do not use unique part numbers? that would resolve any such issue.

 

[wacio]

I should use "clone" function instead of copying files. This way you create new assembly with unique file names. You can exclude common components during cloning operation.

NX8.5 + TC8.3

 

[Javiduc]

Thank you wacio for your answer.

In order to créate a new assembly with unique file name by cloning, I have to rename all components with some text that it is the same for all of them. It is a bit strange for me to do that. Maybe my aproach to naming parts and assemblies is a bit strange (I don't write the reference of the part in the file name, I write it as an atribute).

How can I exclude common components during cloning? I only see a way to do that by creating exceptions but I only can créate exceptions to components individually not to folders so it will be a huge task and very likely to make mistakes. Maybe there is a way I am not seeing.

 

[petulf]

Yup NX in native mode cannot open two parts with the same filename, irrespective of any path differences. If this is a recurring problem I would probably look into using your "reference no" as a file name or as a part of the filename such that you are always guaranteed that the file name will be unique. I would also look into the revision management that is available for NX in native mode see for example Link

The clone tools are very limited out of the box, we use our own scripts to generate clone/log files based on filenames, attributes, and lookup tables before import to teamcenter but the same principle could easily be applied for native clone.

 

[Xwheelguy]

I have to ask.....

What is the purpose of having the same model geometry (components) with the same filename in 2 or more different folders? That seems to be going completely against master model method, which is strongly encouraged in NX, not even mentioning the potential waste of storage space at some point in time, not to mention how revisions are handled when you have 300 folders with 300 instances of the very same component.....which ONE is the right revision?

Tim Flater
NX Designer
NX 9.0.3.4 Win7 Enterprise x64 SP1
Intel Core i7 2.5GHz 16GB RAM
4GB NVIDIA Quadro K3100M

 

[Javiduc]

Thank petulf for the info. Maybe using reference number can be the solution, but I have to think about that because it is a much more "rigid" way to work for me.

Xweelguy; Not 300 of them but maybe 20 and they all are the right revision, each one for its own project. Sometimes I design a machine that includes a subassembly that later I want to reuse for others machines and in some of these machines I modify this subassembly and its parts, but I also want to keep the original subassembly in the original project folder because that machine was manufactured with the original subassembly and maybe in future my client ask me to make some improvements, repairments... If for example this subassembly is a fixture that can be used in several very similar machines that can handle various fixtures at the same time, my client can ask me to place two fixtures (subassemblies) in the same machine (top level assembly) like both fixture are in fact the same with slight modifications, they have componentes with the same filename. Fixtures are only an example, this can happen with a lot of components of a product. I am used to do that very easily coping solidedge assemblies in different folders so I am trying to find a way to handle this issue in NX.