×
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

Pre-e Wildfire to Parasolid 11

Pre-e Wildfire to Parasolid 11

Pre-e Wildfire to Parasolid 11

(OP)
My supplier has Parasolid 11. We have Pro-e Wildfire. What format can I send him an assembly model so that it can be opened in Parasolid 11?
cadjocky

RE: Pre-e Wildfire to Parasolid 11

No problems. I just did a Save a Copy as a Parasolid transmit file from Wildfire build 2003490 and it is in V10 format, which was used by UG V15. The Parasolid version in UG V18 is V13. I would guess that NX2 uses V15.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

RE: Pre-e Wildfire to Parasolid 11

(OP)
Looselib: I have WIldfire build 2003370. Please clarify on  what type of file extension (*.?) should I use to save my assembly model so that my supplier can open in Parasolid v11? File>save a copy>type>? Thanks for your quick reply.

RE: Pre-e Wildfire to Parasolid 11

The file type is .x_t

BUT, you need a hidden config.pro option:
enable_parasolid_export YES

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

RE: Pre-e Wildfire to Parasolid 11

(OP)
looslib:
A big thank you for your help. It worked.
I appreciate your help very much.

RE: Pre-e Wildfire to Parasolid 11

When I saw this thread I felt that pro-e was finnaly starting to be come friendly.  We run Solidworks also and parasolid files for file translation in the solid world are almost better than sliced bread.  So I went and added it to my config.pro and the dot when green and I exported a parasolid file, it even had size to it.  But to much over antisipation when I imported it into Solidworks, there was nothing at all, not even a crummy surface.  Am I doing something wrong?

RE: Pre-e Wildfire to Parasolid 11

Send me the file and I will see what UG can read.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

RE: Pre-e Wildfire to Parasolid 11

I was wondering if there is a different option of exporting Wildfire 2 to parasolid (UG V18).  I believe Wildfire export it to V10 and our GM customer can not read the files since they are on UG V18.

RE: Pre-e Wildfire to Parasolid 11

All Parasolid files should be upward compatable. A V10 Parasolid should have no problem being read into a system that is using a higher version of teh Parasiolid kernel. In the case of UG V18, it is using the V13 Parasolid kernel and can read files exported from Wildfire 2, which is still creating Parasolid V10 files.

We have ecported Parasolid files from V18 and read them into WF1.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

RE: Pre-e Wildfire to Parasolid 11

All Parasolid files are not upward compatable. At least that's what I've found. I'm having the same issue with Pro/E WF2 exporting a V10 Parasolid file. I have yet to find a current system that will import this older kernel transmit file. Including Pro/E's own product called Pro/Desktop 2001. Pro/Desktop gives you the option of exporting a Parasolid version 10 thru 13. Is there any way to tell Pro/E to export a V13 or higher Parasolid? A mod of the config.pro file maybe?

Regards,
Brent Nagel
Applications Engineer

RE: Pre-e Wildfire to Parasolid 11

This the answer I got from Unigraphics:
"Parasolid is upwards compatible so most systems will be able to import. Actual since V13.2 it is also backward compatible!"

I guess I need to do some checking on the PTC side now.

"Wildfires are dangerous, hard to control, and economically catastrophic."
"Fixed in the next release" should replace "Product First" as the PTC slogan.

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

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