Importing Parasolids

I'm trying to drag some mid size (95Mb) parasolid files into Pro/E -
but pro is just hanging. I can re-open the files in UG NX3, but pro
doesn't want to know.
Any config options I should know about?

 

No special insights or much experience with Parasolid imports,
but some thoughts, things I'd try:

Most of this is generic ...
www.prostep.org/en/services/bp/cadkombi/unigraphicsproengineer.htm
Follow the system, pre / post processor links on the right side of the page.
I'd pay special attention to the recommendations to clean out any geometry
not necessary to the communication (i.e. everything but the solid bodies?),
checking geometry integrity, insuring accuracy is set to an appropriate
value (i.e. not to 1E-8 meter?).

When the system is hanging it might be best to make sure any config opts
that try to massage or heal on import are disabled.
fix_boundaries_on_import
intf3d_in_close_open_boundaries
try_g2_fix_on_import
(or try setting if they aren't?)

I'd clear, if set
intf_in_external_accuracy
intf_in_use_template_models

STEP export from UG isn't an option? PTC's Parasolid translators are
relatively new (and maybe buggy?).

A free, on-line Parasolid <-> STEP service. I don't know if they'll
handle large files, but don't see a stated limitation...
www.steptools.com/strepo/login.cgi?URL=/strepo/translate%2Ecgi%3F

 

Just a procedural point which can greatly affect content: never "open" an
import directly as a file; always, first, create a part from a start part so
that it has all of your most intelligent settings, layers, views, etc. built
in. If you have things like default abs accuracy built in, this will give
you a leg up too. Otherwise, you are left with opening with a lot of default
system settings and none of the advantages of the start part. With the new
named part created from a template, do 'Insert>Shared Data>From file'.
Assuming that your parasolid data is in your working directory or workspace,
you should either immediately see the file as a selectable one or need to
change the open 'File type'.

As a complementary point, many times just changing all the parts to a given
absolute accuracy or just moving relative accuracy one or two decimals to
the left will allow stuff that regenerated badly or not at all to regenerate
correctly. It is, perhaps, the single most troubling and disruptive element
in importing data.

David Janes

 

Okay, I'm saving this one. Jeez, there's just SO MUCH. Thanks for that one.
It ought tod help!

David Janes

 

WF2 M180.

Drat slow. I've got there in the end. Project manager is climbing all
over me asking where his budget is going and when I'll start doing some
real work.

 

Hi

Try creating a part in proe make sure units are set to inches and the
go to insert shared data and pick you file to import.

To just open a parasolid in proe the default is to do it in metric
which will take forever.

 

To just open a parasolid in proe the default is to do it in metric

Interesting observation. I can't fathom why ``doing it in metric'' would influence the processing time. The Parasolid data is in
meters, isn't it? Wonder if it might have something to do with using a default rel acc of .0012 (which eventually will work out to
some fraction of a meter that's huge compared to the same tolerance in inches or mm)? Have to dig an old x_t out and play with it
sometime. Thanks for bringin' it up.