ModelCHECK intro

Editor’s Note: I’ve posted two new checks (.dtl file, drawing formats) which are not included in the .zip file, yet.

ModelCHECK configuration consists of several simple files located in a specific directory structure located in $LOADPOINT/modchk/text/usascii/config or pointed to by the environment variable $MCDIR.

TIP: Develop your ModelCHECK config by copying the default config directory to your home directory and set $MCDIR to $HOME. Keep the basic format of the default files and add/comment as necessary.

In order of creation, and execution:

config_init.mc – the “config” file that takes care of the ModelCHECK. The default is pretty usable. There are separate locations for UNIX and NT, which I’ve stripped out to save space. I’ve added comments to changes I’ve made. Updates to this file will take effect after ModelCHECK is re-started.

condition.mcc – the “trigger” file. This file determines which files will be checked and which checks will be used. The simplest condition (as in example) is a default that checks everything. You can check on the following conditions:

USERNAME — User currently logged in
GROUPNAME — User’s group
MODELNAME — Name of the current model
FT_GENERIC_PRT and FT_GENERIC_ASM — If the model is a family table generic
FT_INSTANCE_PRT and FT_INSTANCE_ASM — If the model is a family table instance
MODEL_UNIT — Model units can select different constant files
PRO_VERSION — Version of Pro/ENGINEER
DATE_CREATED — Date created

Parameter — Parameter name or value (easiest way to exclude classes of parts, such as libraries, from ModelCHECK)

default.mch – the “questions” or “check” file. The “check” file is basically a text file of config options, with severity parameters: Y(es),N(o),E(rror),W(arning) separated by white space to determine the applicability of that config to different modes:I(nteractive),B(atch),R(egenerative),S(ave),M(etrics). The default check file will guide you as to the limitations of mode, severity, and config. I’m going to re-organize this file slightly, and limit the checks to Interactive mode. You can add checks for execution during regeneration (R), or file save (S), or for collecting metrics (M) yourself, but personally, I prefer to run ModelCHECK at my convenience. Batch mode is interesting, but that’s another discussion!

default.mcs – The “answers” or “start” file. This is the “template” for your standard part, assembly, and drawing all rolled into one.

*NOTES

  • You need to define at least four files: config file, the condition file, the default checks file, the default start file.
  • Some items are informational only and coded with either ‘Y’ or ‘N’.
  • There is a GUI editor for these files new to WF2, but it’s easier to get started with text files, and then learn how to use the editor to modify these files later.

6 Responses to “ModelCHECK intro”

  1. Balaji Gopinath K. says:
    July 5, 2006 at 6:29 am

    Got a good outline of the modelcheck file structure and file types and their function.

    Thanks and Regards,

    Balaji Gopiath K.
    Engineer-Product Design and Development

    Larsen & Toubro Limited.

  2. Joe STabnik says:
    April 4, 2008 at 2:07 pm

    When I save, proE dialogue box states

    ModelCHECK is Processing widget.PRT
    ModelCHECK will not run – ‘NOCHECK’

    Thsi model came from a supplier, and the usual mapkey “nc” has no effect.
    also in config.pro modelcheck is enabled.

    How do I turn modelcheck back on?

    Regards,
    JoePro/E

  3. proegeek says:
    April 11, 2008 at 7:40 pm

    Joe,

    I’m guessing that someone has created a “NOCHECK” condition in the condition.mcc file that is true for widget.prt?

  4. JScott says:
    February 17, 2009 at 6:02 pm

    Hi All
    How to configure ModelCheck to:
    A) Search through the assemblies and update the parts with:

    · Add Parameters if no match is found

    · Rename old Parameters to new names or Map?

    · Convert real_number parameters to string (IE. Detno (Type = Real_number), now called Detail_Num (Type = String)

    What files need to be created, Start.mch, Check.mch, Start.mcs?

    I have reviewed the help files, the PTC site and searched topics with limited results.

    Does anyone know if any E-Training is available and or books on this topic?

    Here is a list of some of the parameters:

    Description (default value xxx) type String
    Size (default value xxx) (soon to be replaced by Bounding_Box “overall_size, but modelcheck outputs only 2 place decimals.)
    Material (Rename to Prt_No) (default value xxx) type String
    Hardness (default value xxx) type String
    Finish (default value xxx) type String
    Total_Qty (rename to Qty) (default value xxx) type String
    Supplier (Rename to MFG) (default value xxx) type String
    Detno (Map to Detail_num and change from Real_number to String)

    Suggestions?

    Thanks, JScott

  5. proegeek says:
    February 20, 2009 at 7:45 pm

    JScott,

    A lot of ModelCHECK config is trial-and-error, but here are a few ideas to get started:

    ModelCHECK can add & delete parameters in batch mode. Each check generally requires a coordinated change to the .mch and .mcs files.

    Parameters can be deleted:

    .mch > EXTRA_PARAMS WWWW
    .mcs > Define all your standard parameters.

    Parameters can be renamed:

    .mch> PARAMRENAME WWWW
    .mcs> PRT_PARAM_RENAME MATERIAL PRT_NO)

    Parameters can be checked for type and value:

    .mch> PARAMCHECK EEWW
    .mcs> PRT_PARAMETER HARDNESS STR NE xxx

    Note, there is a way to create custom checks, but I’ve never worked with it.

  6. Jason says:
    February 26, 2009 at 1:00 pm

    Here’s an article I wrote on configuring ModelCHECK. It is for WF2 but the concept is the same.

    http://www.profilesmagazine.com/p31/cover.html

    -jason

Leave a Reply