Archive for the ‘interface’ Category

Pro/E tip (interface): Import tips

Friday, October 30th, 2009

There’s a lot of discussion on the Exploder about the config.pro option:

intf_in_use_template_models yes

Old hat says:

If you just want a one click import, fine.

Experience says you should probably do some setup and editing before using import geometry. Things like checking the accuracy and creating a meaningful geometry frame. Sometimes I re-export the data according to the new coordinate system.

Accuracy:

Old FAQ info (IGES Accuracy)
Possible clues at Delcam Support Forums (STEP Accuracy)

Don’t know if this info is that valuable – you decide:

CAx Implementor Forum
STEP at Wikepedia

Pro/E tip (interface): Getting started with WF4 Data Doctor

Saturday, August 29th, 2009

Just prowling around the PTC website and came across this document. Pretty concise introduction to Data Doctor if you need to get going in a hurry. (These files are used in the tutorial)

Pro/E Tip (interface): “Hide”-ing parts during export

Sunday, May 18th, 2008

Did you know that “hidden” parts will not be exported during IGES exports? Use the menu tree to hide components, and set “intf_out_blanked_entities” to “NO”. (default is “yes”)

It’s a quick and dirty way to protect your intellectual property or simplify models. There are other ways to remove components during export, but this is definitely “KISS”.

Pro/E Mantra: You’re only as good as your last save…

Thursday, April 5th, 2007

Sooner or later, everyone loses their work when Pro/E crashes. Eventually, paranoia sets in and your work habits include frequent saves. In the way old days, Pro/E had a tendency to crash when plotting, and I realized the safest thing to do was create a mapkey that saved my drawing before plotting.

Over the years this little mapkey has evolved into quite a timesaver.

NOTE:”Your Printer Here” is the plot config description from your .pcf file.

mapkey pb %~refit;%~save;%~print;\
mapkey(continued) ~ Activate `print` `Your Printer Here`;\
mapkey(continued) ~ Activate `print` `OK`;

mapkey ~print ~ Activate `main_dlg_cur` `File.psh_print`;
mapkey ~refit ~ Activate `main_dlg_cur` `ProCmdViewRefit.view`;
mapkey ~save #DBMS;#Save;;

For Pro/INTRALINK users:
mapkey ~saveall ~ Activate `main_dlg_cur` `File.psh_save_all_changed`;\
mapkey(continued) ~ Activate `infodlg` `okbutton`;

Teaser: I actually have another mantra that superseded this one in the last year:
“3-2-1″
Think about it. :)

Pro/E Tip (interface): STEP file links

Thursday, January 4th, 2007

It’s always a good idea to check your export files by importing them before sending them to someone else. But, today, components were being scattered all over when I ran my checks.

I’m not sure why, but Pro/E had problems with something in my assembly. Of course, my assembly had just about everything nasty: imported parts, mirrored parts, merged parts, family tables, and default placements. No geom checks, though :)

EDIT: Did I mention mixed units? I really thought those days were behind us, but even Pro/E seems to have some problems with mixed units. And even if Pro/E converted units correctly on import, my customer’s software didn’t. Metric seems to be the default, so if you have a choice, convert to metric units – avoid the warning message “WARNING: Length unit set to INCH according to STEP data”.

Update: Sometimes it’s faster to export to a neutral file and then to STEP. Pro/E handles the units problem better with neutral files.

Moral of the story: Consistent units will give better results in import / export operations, especially when other CAD packages are involved.

By the way, I didn’t realize some other packages were still so primitive at importing assemblies. When I checked with our Unigraphics guy, he still imports components individually. Pro/E does a real nice job working through the file relationships.

And, since Pro/E opens .zip files for models, why can’t it open .zip files for IGES imports as well?

Here are a few PTC links:

How can the units of STEP and IGES files be Determined?

To Export a Part or Assembly to STEP

When Importing a STEP Assembly Into Pro/ENGINEER, all Components are Oriented to One Coordinate System. (Fixed WF2 M070)

While Saving a File Type as *.step of an Assembly by Using a Custom Co-ordinate System the Orientation of the Assembly Changes.

Suggested Technique for Analyzing a Pro/ENGINEER STEP file

About Configuring the Export to IGES and STEP