Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations Danlap on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

NX7.5 'Save as' to an existing part number 2

Status
Not open for further replies.

Rich944

Mechanical
Feb 8, 2007
68
Hi All,

We have an existing NX large assembly of a piece of equipment (say assy1), I need to create another piece of equipment (Say Assy2) that is 90% the same as Assy1. Assy2 needs to be a specific part number which already exists on Teamcenter.

I am trying to find a way to save all of the structure and constraints from Assy1 to Assy2. I have tried doing a 'save as' but doing 'save as' to an existing part number has been disabled for us.

I have tried exporting the named references for the Assy1 NX dataset and importing them to the Assy2 NX dataset, when I open the NX dataset only 5 components out of 119 have imported. I checked all the named references and they are identical.

I have also tried copying the components from the Assy1 assy navigator and pasting into Assy2 assy navigator, however all constraints are then disassociated.

Can anyone think of anything else I can do? If not I will have to bite the bullet and build Assy2 from scratch.

Cheers,
Rich

 
Replies continue below

Recommended for you

Cant you save to a new revision of the existing number?

Khimani Mohiki
Design Engineer - Aston Martin
NX8.5
 
I would export the assembly out of Teamcenter using clone, then import it back in, changing the item id and revision. This should maintain all the constraints.

Mike Hyde
NX8.5 with TC9.1
 
Thanks for the replies, Do you both know each other from AML?

Khimani unfortunatly we do not have this functionality anymore, I remember this method worked well and also allowed the drawing file to be pulled across too.

Mike, I will try your cloning method, I clone from the NX environment correct?

Cheers
Rich
 
Hi, in NX8 when i run into this situation i just open the target file, in this case assy2, delete everything in there and do a file, import, part. Here i suggest choosing to import to the original layer, destination to be WCS, and if the assy1 is already in TC, select to "import part from TC". After you click ok, the regular search dialog will appear and just browse for assy1, after selecting the assy, it will prompt you for the location to be imported, just click ok at 0,0,0. then the same location window will appear again in case you want to import the file in another location, just click no. The components and constraints should appear.

Regards.
 
Rich

You are right, cloning is done from the NX envionment. If you want to try it, do a dry run first when importing. This will generate an import.clone file which can be edited for your new target part number and revision.

We've had variable results using 'import part from Teamcenter' but we have mainly tried importing parts rather than assemblies. We normally resort to the named references technique.

And yes, I do know Khimani but he left AML a few weeks ago. We only have around 200 CAD users here so we get to know most people on site.

Mike Hyde
NX8.5 with TC9.1
 
Thanks for all your input,

I tried the importing the part through NX as lbd said, and this has worked well, there were a few substituted components (not sure what happened there) but I have taken note of these. This should give me a good starting point and save me a whole load of time.

Mike I will have a go at the cloning as well at some point, good to have another method. 200 users is quite substantial, I visited AML a while back when you were transferring to NX. I just thought it was a coincidence that you both replied.

Cheers,
Rich
 
Yes im not at AML anymore, in back on CATIA, need to change my signature.

Khimani Mohiki
Design Engineer - Aston Martin
NX8.5
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor