×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Queston on translating Parasolids

Queston on translating Parasolids

Queston on translating Parasolids

(OP)
Hello,

I am trying to investigate Parasolid files a bit more. Currently when I receive outside data from a vendor that does not use NX, we request a Parasolid file of the assembly. Now I know of two ways to translate that Parasolid assembly file back into NX. One, File>Import>Parasolid, This is a No Good way because we loose the assembly structure and simply get a file with hundreds of dumb solid bodies. Two, File>Open>Parasolid, This was is Good when it comes to preserving the assembly structure but No Good when it comes to each component name. This NG condition is because every item gets __id1234_x_t added to the component name.

Does anyone have any idea if we can alter a setting in NX to not add the __id1234_x_t to every component name?

Currently our plan is to change to a step file of the assembly to both preserve the assembly structure as well as the component name. However I was asked to investigate if there is a way to improve the parasolid translation since others feel that it is a more accurate way of translating data from our vendors to NX.

Thank you,
Jaime
NX9 Native

RE: Queston on translating Parasolids

I don't know of any setting that will eliminate the suffix being added to the parts/bodies when using parasolid. However, speaking from my own experience, parasolid is not always the best way to go. A few years ago we were moving geometry back and forth between NX and Pro/E; we could not get parasolid to work reliably, but STEP worked pretty well. More recently I've been working with someone who uses Rhino. Although Rhino supports parasolid export, we get better results with STEP.

www.nxjournaling.com

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources