Pro/ENGINEER FAQ 2009

This is a fairly easy one. The only trick is linking the thickness file to the start file. Once again, let’s run through the files one by one:

1. Check file (*.mch) – add
   SHTMTL_THICK  YNEW  W  W  W  W  W
2. Start file (*.mcs) – add
   STD_SHTMTL_THICK_FILE text\thick.txt
3. Info file (*.txt) – create in the text directory
   # ModelCHECK Standard Sheet Metal Thicknesses File
   #
   UNIT INCH
   .036
   .048
   .060
   etc
   UNIT MM
   .91
   1.21
   1.52
   etc

Small problem: there’s no way to separate tables by material types.

Format names can be checked against a standard list. Once again, three files need to be in synch: the check file, the start file, and an external (info) file. Try this:

Check file (*.mch)
FORMAT_NAME YNEW W W W W W

Start file (*.mcs)
STD_DRW_INFO_FILE text/formats.txt

Info file (*.txt)
DRW_FORMAT Asomething
DRW_FORMAT Bsomething
DRW_FORMAT Csomething
...
Hint: “dir /b > formats.txt” will get you started on your format list

Adding a check against your standard detail file can be accomplished pretty easily in ModelCHECK. I like to check for independent layers, as well as any recent changes to the standard detail file.

As always, it requires a coordinated effort between the check file, start file, and support files. In this case, modify the following files:

Check file (*.mch)
STD_DTL_SETUP YNEW W W W W W

Start file (*.mcs)
#STD_DRW_DTL_FILE B text/dtl/b.dtl
#STD_DRW_DTL_FILE C text/dtl/c.dtl
#STD_DRW_DTL_FILE D text/dtl/d.dtl
STD_DRW_DTL_FILE DEFAULT text/dtl/in.dtl

Abbreviated detail file (*.dtl)
draw_layer_overrides_model yes
ignore_model_layer_status yes

NOTES:

• The check file condition flags are explained on the ModelCHECK page
• The STD_DRW_DTL_FILE format specifies a format size and detail file
• There is also a DEFAULT detail file option
• The .dtl file location could be a company standard or a special ModelCHECK file
• There is a mechanism to update the detail file, but it’s busted right now (see KB)

I always use ‘/’ in paths because ‘\’ isn’t always acceptable (need ‘\\’). Full paths are recommended, but in this case ‘text’ is the ModelCHECK config/text directory.

KB References:

• Pro/ModelCHECK Option STD_DTL_SETUP does not work when activated upon SAVE
• When specifying to apply default DTL (Drawing Setup File). ModelCHECK does not automatically browse to the path specified by STD_DRW_DTL_FILE option
• When Checking Drawing Setup Files With Drawing Formats, ModelCHECK Does Not Recognize The Drawing Setup File

Checks with multiple options can refer to a list defined outside the config files. For example, here’s a list of designers that can be checked against a parameter called “designer” in the default start part (default.mcs).

BASHFUL
DOC
DOPEY
GRUMPY
HAPPY
SLEEPY
SNEEZY 

Start with this instruction in your start part file:
   PRT_PARAMETER DESIGNER STR EQ LIST_DESIGNERS

This says check parts for a string parameter called ”designer” against a “list” of designers. You could include this list in the start part like this:
   LIST_DESIGNERS BASHFUL
   LIST_DESIGNERS DOC
   etc.

Or, you could create a simple text file that can be updated quickly. Do that by adding:
   STD_USER_LIST_FILE text\designers.txt

This is how ModelCHECK links to an external file. “DESIGNERS” is the link. “DESIGNERS” defines the file name. Any path is relative to the ModelCHECK config location, in either the default location, or set by the environment variable $MCDIR.

Finally, the designers.txt file should follow the format of the start part :

LIST_DESIGNERS BASHFUL
LIST_DESIGNERS DOC
LIST_DESIGNERS DOPEY
LIST_DESIGNERS GRUMPY
LIST_DESIGNERS HAPPY
LIST_DESIGNERS SLEEPY
LIST_DESIGNERS SNEEZY

It’s pretty easy to start with an internal list and migrate to an external list later. Besides parameters, you can list model names (with wildcards, I believe), mass units, and others.

I’ve included a designer list in the Sample ModelCHECK config files.

These characters are wildcards in ModelCHECK and can’t be escaped (AFAIK) in condition statements, so it’s very hard to check for parameters with default values. Save yourself trouble downstream: try “-”.