AnsweredAssumed Answered

Import a UG NX assembly with structure and component names?

Question asked by James Ceszyk on Oct 30, 2009
Latest reply on Apr 15, 2011 by James Ceszyk

Like • Show 1 Like1
Comment • 5

Is it possible to get the entire assembly structure including component names when opening a parasolid made from a UG NX assembly file? I have been trading STEP files back and forth with my UG customers and while this maintains component names and the assembly tree, sometimes the models need some cleaning up on both sides.

I've had good results going from SolidWorks to NX with parasolid - They get the entire assembly structure with my component names when they use "file > open > parasolid". From NX to SW is giving me some problems.

Single NX native part files open great in SW. Opening the NX native assembly does not work, or works badly (I do have all the externally referenced NX files for the assembly). Opening a parasolid of the NX assembly file gives me a flat assembly (no sub-assemblies come through) where the component names are replaced with something like, test_assembly_part-1 ...-2 ...-3.

Maybe there are some incorrect settings on the NX output side?

Any help is appreciated.

Alessandro Frattini Oct 31, 2009 5:09 PM

Correct Answer

Hi, jt file is open library.

If SolidWorks will support the jt file, you will import your NX assembly structure with color, properties and mates.

STEP 214 is the only actual solution.

Parasolid doesn't perform your needing.

See the reply in context

No one else had this question

Outcomes

Jerry Steiger Oct 31, 2009 12:59 PM

James,

I would guess that there are incorrect settings on the NX side. In SolidWorks, when I import a Parasolid, there are no options. But when I export I have two choices. One is the version number, which could possibly have an effect, and the the other is a checkbox to "Flatten assembly hierarchy", which would have exactly the effect you are seeing. Your customers should be able to tell you what choices they have on the NX end, although it is amazing how little some people understand about the software they use.

Jerry Steiger

Actions

Alessandro Frattini Oct 31, 2009 5:09 PM

Hi, jt file is open library.

If SolidWorks will support the jt file, you will import your NX assembly structure with color, properties and mates.

STEP 214 is the only actual solution.

Parasolid doesn't perform your needing.

Actions

Aric Tibbitts Mar 29, 2011 10:32 AM

I have the same question. I didn't see a answered response.

I can open NX files directly into SW. No problems however as mentioned it keeps the names of the files but internal to the assembly.

Is there a way to keep this assembly but extract the files and names together.

Actions

Eng Yeap @ Aric Tibbitts on Apr 15, 2011 2:15 AM

When exporting from UG they have to use STEP 214.

I have not found another way.

Actions

James Ceszyk @ Eng Yeap on Apr 15, 2011 8:38 AM

I've found the same - STEP 214 still gives the best results.

Actions

5 Replies

Jerry Steiger Oct 31, 2009 12:59 PM
Mark Correct
Correct Answer
James,

I would guess that there are incorrect settings on the NX side. In SolidWorks, when I import a Parasolid, there are no options. But when I export I have two choices. One is the version number, which could possibly have an effect, and the the other is a checkbox to "Flatten assembly hierarchy", which would have exactly the effect you are seeing. Your customers should be able to tell you what choices they have on the NX end, although it is amazing how little some people understand about the software they use.

Jerry Steiger
Like • Show 0 Likes0
Actions
Alessandro Frattini Oct 31, 2009 5:09 PM
Unmark Correct
Correct Answer
Hi, jt file is open library.
If SolidWorks will support the jt file, you will import your NX assembly structure with color, properties and mates.
STEP 214 is the only actual solution.
Parasolid doesn't perform your needing.
Like • Show 0 Likes0
Actions
Aric Tibbitts Mar 29, 2011 10:32 AM
Mark Correct
Correct Answer
I have the same question. I didn't see a answered response.
I can open NX files directly into SW. No problems however as mentioned it keeps the names of the files but internal to the assembly.

Is there a way to keep this assembly but extract the files and names together.
Like • Show 0 Likes0
Actions
- Eng Yeap @ Aric Tibbitts on Apr 15, 2011 2:15 AM
  Mark Correct
  Correct Answer
  When exporting from UG they have to use STEP 214.
  
  I have not found another way.
  Like • Show 0 Likes0
  Actions
  - James Ceszyk @ Eng Yeap on Apr 15, 2011 8:38 AM
    Mark Correct
    Correct Answer
    I've found the same - STEP 214 still gives the best results.
    Like • Show 0 Likes0
    Actions

Import a UG NX assembly with structure and component names?

Outcomes

Related Content

Recommended Content