<!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>Output CLSF</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_topic3" id="xps10_pagetitle">Output CLSF</div>
      <hr noshade="true">
      <p class="para_topic">Using Output CLSF, you can export internal tool paths in a Cutter Location Source File (CLSF) for use by GPM and other post processors. With customization you can modify these formats by changing their Event Handler (.tcl) and Definition (.def) files for specific requirements.</p>
      <p class="para_topic">To output a CLSF for an operation or program, follow the list below:</p>
      <ul>
         <li>
            <p class="para_item">In the Operation Navigator, choose the program or operation you wish to output or choose the root in the Program Order View to output all operations. </p>
         </li>
         <li>
            <p class="para_item">Choose the Output CLSF icon in the main menu bar or Tools&rarr;Operation Navigator&rarr;Output&rarr;CSLF. This displays the Output CLSF dialog.</p>
            <table border="0">
               <tr>
                  <td valign="top" align="left"><img align="left" src="../graphics/warning.gif" alt="Warning" title="Warning"></td>
                  <td valign="bottom" align="left" width="100%">
                     <div class="para_warning">
                        <p class="para_warning_body">When outputting multiple operations, you should always be in the Program Order View. Although the system allows it, you should not select groups for outputting multiple operations outside the Program Order View because the operations are not in the context of their program order. </p>
                     </div>
                  </td>
               </tr>
            </table>
         </li>
      </ul>
      <ul>
         <li>
            <p class="para_item">In the dialog, choose an available format from the list.</p>
         </li>
      </ul>
      <table cellspacing="3" align="center">
         <tr valign="top">
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">CLSF_STANDARD</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">is the most common choice. This creates a CLSF in APT format (ASCII) which is later postprocessed using NX GPM or other postprocessing software for the intended machine tool.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">CLSF_ADVANCED</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">This automatically extracts the post commands from the Operation Navigator and puts them into the CLSF. It generates a load tool for mills and a turret command for lathe, a spindle statement or command (for both speed and direction), output mode, and Select/Tool (the tool number of the next operation) based on the current operation data. You won't need to create any of them since it outputs the information from the Tool definition.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">CLSF_COMPRESSED</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">outputs only START and END OF PATH statements</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">CLSF_BCL</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">creates a CLSF in BCL or ACL format for machine tool controllers capable of directly reading (i.e., without having to postprocess) the generated BCL or ACL RS-494 file. This is your choice only if your machine tool is BCL compatible. NX specific replay codes (MSYS, PAINT, etc.) are not included in the BCL file. This produces a CLS file with special commands for BCL. Then you use the CLS2CLF program to convert this file to BCL. CLS2CLF will output a file with the correct BCL extension. </p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">CLSF_ISO</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">creates a CLSF in ASCII format using ISO 4343 (International Standard Organization) conventions. It is similar to Standard but has several different commands and associated parameters. Then you use the CLS2CLF program to convert this file to ISO. CLS2CLF will output a file with the correct ISO extension. </p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">CLSF_IDEAS_MILL and CLSF_IDEAS_MILL_TURN</p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td">creates a CLSF for the legacy SDRC cpost</p>
            </td>
         </tr>
      </table><br><ul>
         <li>
            <p class="para_item">Then specify an output file destination and name. This is where you store your output.</p>
            <ul>
               <li>
                  <p class="para_item">The Browse button allows you to browse through the directories to choose your output file destination and name.</p>
               </li>
               <li>
                  <p class="para_item">If you do not enter an extension it is determined by the format you select. The default extension is .cls. If you enter a &quot;.&quot;, the system thinks you have entered an extension.</p>
               </li>
            </ul>
         </li>
      </ul>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_note">
                  <p class="para_note_body">If you are in a Teamcenter environment, or if your configuration includes LIBRARY_CAM_OUTPUT, the name and location of the output file is chosen for you. </p>
               </div>
            </td>
         </tr>
      </table>
      <ul>
         <li>
            <p class="para_item">You can turn on the List Output option if you would like to see the output in the information window, in addition to the output to a file. If you have only made minor changes to the program and do not want to take the time for the display to appear on the screen, you can uncheck List Output to speed up the output process.</p>
         </li>
      </ul>
      <p class="para_topic">This produces the output file, which you provide as input to GPM or your third party postprocessor.</p>
   </body>
</html>