<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Configuration Files</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic2" id="xps10_pagetitle">Configuration Files</div>
      <hr noshade="true">
      <p class="para_topic">CAM configuration files define the CAM working environment. They define the available machining processors, tool libraries, postprocessors, and other high level parameters for your session. In addition to using the configuration files supplied by NX, you can also create your own customized configuration files. Creating customized files allows you to define a working environment that meets your specific needs.</p>
      <p class="para_topic">In order to enter Manufacturing, the CAM configuration file must be valid and the environment variable UGII_BASE_DIR must be set. The user must select a configuration file and then specify a setup (a template part file) contained within that configuration file when entering Manufacturing with a particular part for the first time.</p>
      <p class="para_topic">Comments only add readability and description to the template file itself. Any text literals following two pound signs, ##, are treated as comments. They are not directed to the final output.</p>
      <div class="title_division">Example of a Configuration File</div>
      <p class="para_division">The following is an example of an NX supplied CAM configuration file. All configuration files, whether NX-supplied or custom must follow the same syntax; a key word followed by an environment variable which identifies the location of a reference file.</p>
      <p class="para_division">## This is a template for a CAM configuration file.</p>
      <p class="para_division">TEMPLATE_OPERATION, ${UGII_CAM_TEMPLATE_SET_DIR}cam_general.opt</p>
      <p class="para_division">TEMPLATE_DOCUMENTATION, ${UGII_CAM_SHOP_DOC_DIR}shop_doc.dat</p>
      <p class="para_division">TEMPLATE_POST, ${UGII_CAM_POST_DIR}template_post.dat</p>
      <p class="para_division">USER_DEFINED_EVENTS, ${UGII_CAM_USER_DEF_EVENT_DIR}ude.cdl, ${UGII_CAM_USER_DEF_EVENT_DIR}ude.tcl</p>
      <p class="para_division">TEMPLATE_CLSF, ${UGII_CAM_TOOL_PATH_DIR}template_clsf.dat</p>
      <p class="para_division">LISTING_FORMAT, ${UGII_CAM_TOOL_PATH_DIR}clsf.def, ${UGII_CAM_TOOL_PATH_DIR}clsf.tcl</p>
      <p class="para_division">LIBRARY_TOOL, ${UGII_CAM_LIBRARY_TOOL_ASCII_DIR}dbc_tool_ascii.def, ${UGII_CAM_LIBRARY_TOOL_ASCII_DIR}dbc_tool_ascii.tcl</p>
      <p class="para_division">LIBRARY_MACHINE, ${UGII_CAM_LIBRARY_MACHINE_ASCII_DIR}dbc_machine_ascii.def, ${UGII_CAM_LIBRARY_MACHINE_ASCII_DIR}dbc_machine_ascii.tcl</p>
      <p class="para_division">LIBRARY_MACHINING_DATA, ${UGII_CAM_LIBRARY_FEEDS_SPEEDS_ASCII_DIR}machining_data.def, ${UGII_CAM_LIBRARY_FEEDS_SPEEDS_ASCII_DIR}machining_data.tcl</p>
      <p class="para_division">LIBRARY_FEEDS_SPEEDS, ${UGII_CAM_LIBRARY_FEEDS_SPEEDS_DIR}feeds_speeds.def, ${UGII_CAM_LIBRARY_FEEDS_SPEEDS_DIR}feeds_speeds.tcl</p>
      <p class="para_division">LIBRARY_PART_MATERIAL, ${UGII_CAM_LIBRARY_FEEDS_SPEEDS_DIR}part_materials.def, ${UGII_CAM_LIBRARY_FEEDS_SPEEDS_DIR}part_materials.tcl</p>
      <p class="para_division">LIBRARY_TOOL_MATERIAL, ${UGII_CAM_LIBRARY_FEEDS_SPEEDS_DIR}tool_materials.def, ${UGII_CAM_LIBRARY_FEEDS_SPEEDS_DIR}tool_materials.tcl</p>
      <p class="para_division">LIBRARY_CUT_METHOD, ${UGII_CAM_LIBRARY_FEEDS_SPEEDS_DIR}cut_methods.def, ${UGII_CAM_LIBRARY_FEEDS_SPEEDS_DIR}cut_methods.tcl</p>
      <p class="para_division">LIBRARY_SETUP_TEMPLATE, ${UGII_CAM_LIBRARY_TEMPLATE_DIR}template.def, ${UGII_CAM_LIBRARY_TEMPLATE_DIR}template.tcl</p>
      <p class="para_division">LIBRARY_CAM_OUTPUT, ${UGII_CAM_LIBRARY_TEMPLATE_DIR}cam_output.def, ${UGII_CAM_LIBRARY_TEMPLATE_DIR}cam_output.tcl</p>
      <p class="para_division">WIZARD, ${UGII_CAM_WIZARD_DIR}wizard_cam_library.tcl</p>
      <p class="para_division">Each of above resource files that make up the configuration file are described below.</p>
      <p class="para_division">TEMPLATE_OPERATION is a key word that specifies the default  <a class="links" href="javascript:void(0)" onclick="top.openFile('mfggeneral/cust_create_temp.html');return(false);">template set</a> (.opt file). The .opt file defines the available setups and templates from which the user can choose when creating operations, tools, methods, and geometry groups.
      </p>
      <p class="para_division">TEMPLATE_DOCUMENTATION specifies a template set that contains the available templates for shop floor documentation. It defines the list of available templates that the user sees in the Part Documentation dialog box.</p>
      <p class="para_division">TEMPLATE_POST is a key word that specifies a file containing a list of postprocessors for Post. It defines the list of available machines that the user sees in the Post Process dialog box.</p>
      <p class="para_division"> <a class="links" href="javascript:void(0)" onclick="top.openFile('mfggeneral/cust_user_def_events.html');return(false);">USER_DEFINED_EVENTS</a> is a key word that specifies the available machine control events for machine tools in the machine tool library. It defines the contents of the Available List in the User Defined Events dialog box in Machine Control.
      </p>
      <p class="para_division">TEMPLATE_CLSF is a key word that specifies a file containing a list of CLSF formats. It defines the list of available CLSF's in the Output dialog.</p>
      <p class="para_division">LISTING_FORMAT specifies the listing format of tool paths displayed in the Info window.</p>
      <p class="para_division">LIBRARY_TOOL defines the access to a database of tools to be retrieved within NX.</p>
      <p class="para_division">LIBRARY_MACHINE defines the access to a database containing all available machine tools to be retrieved within NX.</p>
      <p class="para_division">LIBRARY_MACHINING_DATA defines the access to a database for calculating machining data (speed, feed, stepover, depth of cut) based on cut method, part material, tool material, tool diameter, tool length, and rigidity factor.</p>
      <p class="para_division">LIBRARY_FEEDS_SPEEDS defines the access to a database containing available feeds and speeds based on cut method, part material, and tool material.</p>
      <p class="para_division">LIBRARY_PART_MATERIAL defines the access to a database containing available raw materials and their properties to be used in feeds and speeds calculations.</p>
      <p class="para_division">LIBRARY_TOOL_MATERIAL defines the access to a database containing available tool materials and their properties to be used in feeds and speeds calculations.</p>
      <p class="para_division">LIBRARY_SETUP_TEMPLATE is an optional keyword that defines access to a database containing available setup templates, and the type templates assigned to each. When defined the setup selection dialog uses NX Library instead of showing the template set defined by TEMPLATE_OPERATION. In a Teamcenter Manufacturing environment the setups are stored in a data management system.</p>
      <p class="para_division">LIBRARY_CAM_OUTPUT is an optional keyword that defines access to a database where CLS, post, and shop documentation files are stored in a Teamcenter Manufacturing environment. In a native environment this defines the directory organization used to store output files. </p>
      <p class="para_division">WIZARD is an optional keyword that defines the program to be used for process assistants.</p>
      <div class="title_division">Directory Structure</div>
      <p class="para_division">The following is an illustration of the directory structure in which the configuration and resource files reside:</p>
      <p align="center"><img align="bottom" src="graphics/cust_directoriefi01.gif"></p>
      <div class="title_division">Creating Custom Configuration Files</div>
      <p class="para_division">The /custom/ directory has been created specifically to contain your customized configuration (.dat) files. &nbsp;The environment variable UGII_CAM_CUSTOM_DIRThis indicates this directory which defaults to $(UGII_BASE_DIR}\mach\custom. If you use a different location than the default, you need to be sure this variable points to your location. To customize a configuration file, we recommend that you copy an existing configuration file from the /mach/resource/configuration/ directory into the /mach/custom/ directory. If you rename the copied configuration file, it will appear in the interactive dialog box in addition to the original configuration file. If you do not rename the copied configuration file, it will appear in the interactive dialog box in place of the original configuration file.</p>
      <p class="para_division">Once you have defined your custom configuration file, copy the desired resource files you wish to modify into the appropriate subdirectory under /mach/custom/. Be sure your custom configuration file references the correct resource files. Modify your copies of the resource files.</p>
      <p class="para_division">By copying and modifying existing configuration in the /custom/ directory, you will prevent these files from being overwritten when subsequent versions of NX are installed on your system.</p>
      <div class="title_division">Example of Customizing</div>
      <p class="para_division">If you want to create a custom configuration that includes your template parts:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item">copy mill_contour.dat into /custom/configuration/my_config.dat</p>
         </li>
         <li>
            <p class="para_item">copy mill_contour.opt into /custom/template_part/english/my_templates.opt</p>
         </li>
         <li>
            <p class="para_item">edit my_config.dat ; change the path of TEMPLATE_OPERATION to /custom/template_part/english/my_templates.opt</p>
         </li>
         <li>
            <p class="para_item">edit my_templates.opt , adding your part to the list just as in the previous releases.</p>
         </li>
      </ol>
   </body>
</html>