9.1. Using the Product & CAD Configuration Manager

The Product & CAD Configuration Manager allows you to configure geometry interfaces for Mechanical APDL and ANSYS Workbench. CAD configuration is typically handled during the product installation; however, if you chose to skip those steps, or if you make changes to your local CAD configuration between releases (for example, you install, move, or update your CAD package, or remove it entirely), you can use this utility.

This document describes how to use the Product & CAD Configuration Manager to progress through the configuration process.

  1. From Windows 7, click Start > All Programs > ANSYS 18.2 > Utilities > Product & CAD Configuration Manager 18.2. From Windows 10, right-click the Start > All apps> ANSYS 18.2> Product & CAD Configuration Manager 18.2.

  2. From the Product & CAD Configuration Manager, click Configure Products & CAD.

  3. From the selection screen, choose the CAD products that you need to configure. Click the Next arrow.

  4. Configure the appropriate CAD products as described below:

    AutoCAD

    • If you selected AutoCAD as one of your CAD products, you will have to choose which AutoCAD product to configure. You can choose the Reader (non-associative) or the Workbench Associative Interface (requires that the CAD product be installed).

    CATIA V5

    • If you selected CATIA V5 and any product that includes ANSYS Workbench, you will be required to select the appropriate CAD reader/plugin for ANSYS Workbench. You can choose to configure the Reader or the CADNexus CAPRI CAE Gateway.

    Autodesk Inventor

    • If you selected Inventor as one of your CAD products, you will have to choose which Inventor product to configure. You can choose the Reader (non-associative) or the Workbench Associative Interface (requires that the CAD product be installed).

    NX

    1. If you selected NX, you will have to choose which NX product to configure. You can choose the Reader (non-associative) or the Workbench Associative Interface (requires that the CAD product be installed).

    2. If you choose the Workbench Associative Interface and the UGII environment variables were not set, you may need to specify the NX installation path for an existing NX installation. If you are an administrative user, a file required to load the NX plug-in is placed in the administrative user's Application Data folder by default, which may not be accessible by other, non-administrative users. To allow non-administrative users to run, you will need to define the environment variable UGII_CUSTOM_DIRECTORY_FILE prior to installation and specify a location where other users have read access.

    3. If you selected the ANSYS ICEM CFD NX Interface product but not the NX Geometry Interface product on the product selection screen, you will need to specify the NX installation path.

    Creo Parametric

    1. If you selected Creo Parametric, you will have to choose which Creo Parametric product to configure. You can choose the Reader (non-associative) or the Workbench Associative Interface (requires that the CAD product be installed).

    2. If you choose the Workbench Associative Interface, you may need to specify the Creo Parametric language, the Creo Parametric command, and the full Creo Parametric installation path (C:\Program Files\PTC\Creo 1.0\Parametric by default) for an existing Creo Parametric installation.

    SolidWorks

    • If you selected SolidWorks as one of your CAD products, you will have to choose which SolidWorks product to configure. You can choose the Reader (non-associative) or the Workbench Associative Interface (requires that the CAD product be installed).

    Solid Edge

    • If you selected Solid Edge as one of your CAD products, you will have to choose which Solid Edge product to configure. You can choose the Reader (non-associative) or the Workbench Associative Interface (requires that the CAD product be installed).

  5. When all of your CAD products have been successfully configured, click Exit.

You can review the Product & CAD Configuration Manager log file, CADConfigurationMgr.log, in \ANSYS Inc.


Important:  If you change your source from reader to associative plug-in or vice-versa (Creo Parametric, NX, SolidWorks, Autodesk Inventor, SolidEdge, AutoCAD or Catia V5), you must first unconfigure the existing source and then configure using the new source.


9.1.1. Unconfiguring

If you need to unconfigure any of your CAD products, follow the steps above, but choose Unconfigure Products & CAD from the Product & CAD Configuration Manager.

9.1.2. Running the Product & CAD Configuration Manager in Batch Mode

You can configure ANSYS Geometry Interfaces by supplying the Product & CAD Configuration Manager with arguments specific to the CAD sources you want to make available. The following table contains a list of supported arguments.

The command to run the Product & CAD Configuration Manager in batch mode on Windows is:

"<installpath>\commonfiles\CAD\bin\winx64\Ans.CadInt.CADConfigurationUtility.exe" 
     -arguments
Argument Value Comment
UNCONFIGURE_SPECIFIEDNoneResults in any specified CAD sources being unconfigured. When this flag is absent, the Product & CAD Configuration Manager will attempt to configure all designated CAD sources.
UNCONFIGURENoneResults in all CAD sources being disabled along with prerequisite libraries.
Either: PE_CONFIG_WB or PE_CONFIG_WBSPATIAL NoneSpecify Creo Parametric source as either the associative plug-in or the reader (Spatial, no Creo Parametric install required). When the plug-in is specified, additional arguments PROELOADPOINT and PROE_START_CMD are required.
PROELOADPOINT Full path to Creo Parametric installation (quotes required on Windows).Not required with unconfigure operation.
PROE_START_CMD Full path to command used to launch Creo Parametric (quotes required on Windows)Not required with unconfigure operation.
Either: UG_CONFIG_WB or UG_CONFIG_WBSPATIALNoneSpecify NX source as either the associative plug-in or the reader (Spatial, no NX install required). When the plug-in is specified, the argument UGII_BASE_DIR must also be specified.
UGII_BASE_DIR Full path to NX installationThis should agree with environment variable UGII_BASE_DIR. Not required with unconfigure operation.
Either: CATIA_SPATIAL or CATIA_CAPRI NoneSpecify Catia V5 source as either the Reader (Spatial, no Catia install required) or CAPRI (CADNexus install required).
OSDM_CONFIG NoneConfigure/unconfigure Creo Elements/Direct Modeling.
Either: INVENTOR_CONFIG or INVENTOR_CONFIG_WBSPATIALNoneSpecify Inventor source as either the associative plug-in or the reader (Spatial, no Inventor install required).
Either: SOLIDWORKS_CONFIG or SW_CONFIG_WBSPATIALNoneSpecify SolidWorks source as either the associative plug-in or the reader (Spatial, no SolidWorks install required).
Either: SOLIDEDGE_CONFIG or SOLIDEDGE_CONFIG_SPATIALNoneSpecify Solid Edge source as either the associative plug-in or the reader (Spatial, no Solid Edge install required).
Either: ACAD_CONFIG or ACAD_CONFIG_SPATIALNoneSpecify AutoCAD source as either the plug-in or the reader (Spatial, no AutoCAD install required).
TEAMCENTER_CONFIG NoneConfigure/unconfigure Teamcenter; for configuration requires TC_ROOT flag.
TC_ROOTPath to Teamcenter installation.Not required with unconfiguration operation.
JTOPEN_CONFIGNoneConfigure/unconfigure JT.
CATIA4_CONFIGNoneConfigure/unconfigure CATIA v4.
CATIA6_CONFIGNoneConfigure/unconfigure CATIA v6.
TC_DISCRIMINATORAn identifier for the ANSYS Teamcenter Plug-InNot required with unconfigure operation.

Note:  All arguments require a dash (-) before them in order to be properly recognized by the Product & CAD Configuration Manager. Arguments' values should not have a dash preceding them.


For example, you can configure Creo Parametric and SolidWorks Geometry Interfaces to ANSYS Workbench from the command line by using the following:

"<installpath>\commonfiles\CAD\bin\winx64\Ans.CadInt.CADConfigurationUtility.exe" 
-SW_CONFIG -PE_CONFIG_WB -PROELOADPOINT "C:\Program Files\PTC\Creo 2.0\Parametric" 
-PROE_START_CMD "C:\Program Files\PTC\Creo 2.0\Parametric\bin\parametric.bat"

where installpath is the same as the value of environment variable %AWP_ROOT182%, platform is the value of environment variable %ANSYS_SYSDIR%, and Creo Parametric is installed to C:\Program Files\PTC\Creo 2.0\Parametric.

To unconfigure the same CAD Interfaces, the command would be:

"<installpath>\commonfiles\CAD\bin\winx64\Ans.CadInt.CADConfigurationUtility.exe" 
-unconfigure_specified -SW_CONFIG -PE_CONFIG_WB

Although the argument order does not matter, an argument value must immediately follow its argument.

9.1.3. Network Considerations

When Workbench is installed to a network location (made available from a mapped network drive), any configuration actions will make the selected geometry interfaces available/unavailable only to the user who is currently logged in.  To make changes that apply to all users, the configure/unconfigure action must be run as an administrator logged into the system hosting the Workbench installation.  Configuration actions performed as an administrator on this server machine will impact all users on all machines referencing that install, except for users who have overridden the server configuration by configuring for themselves.

For loading associative geometry interfaces into their respective CAD environments, when the Workbench installation is referenced from a network location:

  • A local administrator’s configuration changes will set up associative CAD interfaces to load into the CAD environment of all local users, when that scope is selected (applicable to AutoCAD, Inventor, SolidWorks, Solid Edge, Creo Elements/Direct and NX).

  • The associative geometry interface for Creo Parametric will load into the CAD environment of all users when the CAD installation is writable for that administrative user.  Otherwise, it will load only into the CAD environment of the administrator who is currently logged in, and each additional user must be configured individually.

CAD Readers for JT, Creo Parametric, Inventor, NX, CatiaV5, CatiaV6, AutoCAD, Solid Edge and SolidWorks may not fully unconfigure on a client of a network installation, even when this action is attempted by a client's administrator. An administrative user on the server must execute an unconfigure action, using Product & CAD Configuration Manager, in order for these interfaces to be fully deactivated on the client.

9.1.4. Uninstalling

Warning:  Do not proceed with an uninstall for CAD-specific unconfigure actions or you will leave some ANSYS Workbench products unusable.

9.1.5. Creo Parametric Configuration

Running the Product & CAD Configuration Manager for Creo Parametric performs the following steps to activate the Creo Parametric plug-in:

  • Sets the environment variable PROE_START_CMD182 to the file used to launch Creo Parametric (for example C:\Program Files\PTC\Creo 3.0\F000\Parametric\bin\parametric.bat).

  • For administrative installations, adds the ANSYS 18.2 entry to the config.pro file located in <creo_path>\text. An example for Creo Parametric would be:

    PROTKDAT C:\Program Files\PTC\Creo 3.0\F000\Common Files\text
  • Updates the WBPlugInPE.dat file referenced in the config.pro file, so that it contains information for loading the WorkBench Plug-In and the ANSYS Connection product.

  • Registers the Plug-In file WBPlugInCreo3COM.dll (Creo Parametric 3.0) or WBPlugInPECOM.dll (Creo Parametric 2.0) referenced in the WBPlugInPE.dat file.

  • When Workbench is installed on a network location and the local administrator has write permissions to <creo_path>\text, a version-specific WBPlugInPE182.dat file will be created and placed in that folder.  However, when <creo_path>\text is unwriteable, both the config.pro and the WBPlugInPE182.dat will be placed in either %HOME% or %HOMEDRIVE%%HOMEPATH%.

If you do not have write access to your ANSYS Workbench installation, you may encounter the following error when attempting to import Creo Parametric models without an active CAD session:

No write access, please choose another startup directory for trail file creation.

To prevent this issue, add the following line to your config.pro file:

trail_dir $TEMP

WBPlugInPE.dat File Contents The WBPlugInPE.dat file should look like this example:

NAME WB182PluginProWF
EXEC_FILE E:\Program Files\ANSYS Inc\V182\AISOL\CADIntegration\ProE\
     winx64\WBPlugInPECOM.dll
TEXT_DIR E:\Program Files\ANSYS Inc\V182\AISOL\CADIntegration\ProE\
     ProEPages\Language\<locale>
STARTUP dll
delay_start FALSE
allow_stop TRUE
unicode_encoding FALSE
END

NAME ac4pro182dll
exec_path E:\Program Files\ANSYS Inc\V182\ANSYS\ac4\bin\pro\winx64\ac4pro.exe
text_path E:\Program Files\ANSYS Inc\V182\ANSYS\ac4\data\pro\text
STARTUP dll
delay_start FALSE
allow_stop TRUE
unicode_encoding FALSE
unicode_encoding FALSE
revision 24.0
end

Do not delete any of these lines. If you modify this file, do NOT enter a carriage return after the END line. The file may be customized with other information. If these lines are deleted, or if the WBPlugInPE.dat file is not present in any of the directories in the search path, Creo Parametric will not load ANSYS-related CAD interfaces. You should typically never have to edit these files for path information contained within them. Paths are determined by environment variable settings, which are set automatically during installation. If you encounter problems when attempting to run Creo Parametric, use the Product & CAD Configuration Manager to reconfigure rather than attempting to edit files directly.

Following an update of an existing Creo Parametric 2.0 or 3.0 installation to a different maintenance release (for example upgrading from datecode F000 to M010), the ANSYS Workbench Associative Plug-In will no longer be configured.  To reactivate your plug-in, follow the steps described in Using the Product & CAD Configuration Manager.  This situation does not apply to Creo Elements/Pro 5.0.

In order for Product & CAD Configuration Manager to successfully perform configuration of the Creo Parametric Associative Geometry Interface it is required that the Windows Operating System's decimal separator be the same symbol when running configuration as it was when the original Creo Parametric installation was performed.

9.1.5.1. Configuring the Connection for Creo Parametric

All Creo Parametric users must have copies of the WBPlugInPE.dat file and the config.anscon.182 (connection for Creo Parametric) files. The config.anscon.182 file is placed in the Program Files\ANSYS Inc\V182\ansys\ac4\data\winx64 directory. config.anscon.182 must be copied into the user's working directory at the time Creo Parametric is started. The WBPlugInPE.dat file is placed in the Program Files\ANSYS Inc\V182\AISOL\CADIntegration\%ANSYS_PROEWF_VER%\ProEPages\config directory. This file defines the name of the executable, the path to the executable, the path to the message file, and the current revision of Creo Parametric.


Note:  If the ANSGeom menu in Creo Parametric does not appear correctly, copy the config.anscon.182 file into your working directory and restart Creo Parametric.


9.1.5.1.1. The WBPlugInPE.dat File and config.pro File

Creo Parametric uses the WBPlugInPE.dat file to locate related executables such as the connection for Creo Parametric.

Mechanical APDL/ANSYS Workbench also requires a config.pro file.

  • The config.pro file resides <path-to-creo-parametric>\..\Common Files\<Creo Ship Code>\text for Creo Parametric. The Creo Ship Code is a three digit number preceded by a single letter.   The ship code is specified in the Creo Parametric installation log, which can be found in <path-to-creo-parametric>\bin\pim\xml\creobase.xml. In the cases that the crebase.xml file is missing, the ship code can be determined by looking in the Windows Registry using regedit. For Creo 2.0, that value is located in SOFTWARE\Wow6432Node\PTC\Creo Parametric\2.0\<DateCode>\Shipcode. For Creo 3.0 the value is located in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PTC\PTC Creo Parametric\3.0\<DateCode>. <Datecode> is a integer reflecting the date of the Creo build.

The config.pro file contains a PROTKDAT line that points to the WBPlugInPE.dat file. This file is generated either during the product install or by running the Product & CAD Configuration Manager to configure the Mechanical APDL /ANSYS Workbench products for Creo Parametric.

The <proe_platform> variable is the name that Creo Parametric gives to its platform directories:

WBPlugInPECOM

Hardware Platform

ANSYS Platform <platform>

Creo Parametric Platform <proe_platform>

Win 7 and Wind 8.1 x64winx64x86e_win64
9.1.5.1.2. The config.pro File

A typical config.pro file might look like the following example. This example has an entry for ANSYS Workbench. You may have other Creo Parametric specific customizations.

PROTKDAT E:\Program Files\ANSYS Inc\V182\AISOL\CADIntegration\$ANSYS_PROEWF_VER\
     ProEPages\config\WBPlugInPE.dat
9.1.5.1.3. The config.anscon.182 File

Users who launch Mechanical APDL from Creo Parametric will need the information from the config.anscon.182 file. This file is installed for all users in the \ac4\data\winx64 subdirectory. You typically do not need to edit this file. Here is a sample config.anscon.182 file:

ANSYS_CMD %AWP_ROOT182%\ANSYS\bin\%ANSYS_SYSDIR%\ansys182.exe
ANSYS_GRAPHIC_DEVICE WIN32
ANSYS_SOLVER Sparse**
ANSYS_SELECTED_LAYERS 1-256**
ANSYS_GEOMETRY_TYPE Solids Only**
ANSYS_NEUTRAL_FORMAT Yes**
ANSYS_PRODUCT_NAME ANE3FL

**These variables are not supported by Creo Parametric and are ignored by Creo Parametric.

See Setting ANSYS Configuration Parameters in the Connection User's Guide for more information about the config.anscon.182 file.

9.1.5.2. Creo Parametric Environment Variables

Most environment variables are set during product installation. In general, you will not need to reset these variables. Check the manuals for the individual CAD products for information about environment variables and their settings.

PROE_START_CMD182

Specifies the name of the .bat file which launches Creo Parametric on the system. The path to the executable should be already set if the Creo Parametric installation path has been defined for the PATH environment setting.

PROE_START_CMD182 Default = C:\Program Files\PTC\Creo 2.0\Parametric\bin\parametric.bat

9.1.6. NX Configuration

Running the Product & CAD Configuration Manager for NX performs the following steps to activate the NX plug-in:

  • If not already existing, sets the environment variable UGII_CUSTOM_DIRECTORY_FILE to %APPDATA%\ANSYS\v182\Unigraphics\custom_dirs.dat.

  • If not already present, adds an entry to the custom_dirs.dat file specifying the location of the Plug-In, e.g., C:\Program Files\ANSYS Inc\V182\AISOL\CADIntegration\UnigraphicsNX\winx64.

  • Registers the Plug-In file (DSPlugInUGCOM.dll). For the previous example, these files would be located in C:\Program Files\ANSYS Inc\V182\AISOL\CADIntegration\UnigraphicsNX\winx64\startup.

9.1.6.1. Configuring the Connection for NX

User-Defined Environment Variables You will need to have the following environment variable set if you will be running the connection for NX product from inside NX.

UGII_BASE_DIR and UGII_ROOT_DIR

The environment variables UGII_BASE_DIR and UGII_ROOT_DIR must be defined for proper operation of NX and the ANSYS Workbench Plug-In to NX. These environment variables are typically created by the NX installer; however, in rare cases, you may have to create/update these two variables. In these situations, the NX Installation Location field will be left blank within the Product & CAD Configuration Manager's NX tab.

When multiple NX versions are installed on a system, the UGII_BASE_DIR environment variable must be set to the install path of the NX version to be launched, prior to starting that version of the CAD.  Otherwise errors will be encountered during CAD startup and the plug-in will not load. For example, if switching from NX 8.5 to run NX 9.0, you must update UGII_BASE_DIR to the NX 9.0 path before starting NX 9.0. Similarly, the UGII_ROOT_DIR environment variable must be set to the ugii subdirectory in the install path of the NX version to be launched.

9.1.6.2. Configuring for Teamcenter

Running the Product & CAD Configuration Manager for Teamcenter performs the following step to activate the Teamcenter plug-in:

  • When Teamcenter Unified is detected, the environment variable TC_ROOT is set to the Teamcenter Unified installation path.


Release 18.2 - © ANSYS, Inc. All rights reserved.