<!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>Import</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">Import</div>
      <hr noshade="true">
      <div class="title_division">Import CLSF into Operation</div>
      <div class="figure">
         <p align="center"><img align="bottom" src="graphics/progview.gif"></p>
      </div>
      <div class="title_figure">Program before and after CLSF Import</div>
      <p class="para_division">If a CLSF was used to group tool paths; the CLSF Import function provides a way to preserve that organization. &nbsp;</p>
      <ul>
         <li>
            <p class="para_item">When you use the Import function, a program parent is created and named for each imported CLSF. Operations whose names match the tool paths in the imported CLSF are listed under the created program name. The imported tool path does not replace it. If an operation does not contain an internal tool path, the CLSF tool path data is written to the internal path.</p>
            <p class="para_item">In the image below operations 4,10, and 11 do not have tool paths. This is indicated by both the red circular icon to the left of the operation name and the word None in the Path column before Import. After import None is changed to Imported. </p>
            <div class="figure">
               <p align="center"><img align="bottom" src="graphics/import_prog_captr1.gif"></p>
            </div>
            <div class="title_figure">Program View before CLSF Import</div>
            <div class="figure">
               <p align="center"><img align="bottom" src="graphics/import_prog_captr2.gif"></p>
            </div>
            <div class="title_figure">Program View After CLSF Import</div>
         </li>
         <li>
            <p class="para_item">If no operation exists for an imported CLSF tool path, a Machine Control Operation is created. Again, an internal tool path is created from the CLSF tool path for that Machine Control Operation. This can be seen as operation P3 in the above example. </p>
            <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">Keep in mind that after Import if this operation is regenerated, &nbsp;the original tool path that originated from the CLSF tool path is replaced by the newly generated tool path.</p>
                     </div>
                  </td>
               </tr>
            </table>
         </li>
         <li>
            <p class="para_item">A CLSF will not overwrite an internal tool path that already exists. Therefore, if you have edited a CLSF tool path, you should delete the internal tool path before you import the CLSF tool path.</p>
         </li>
         <li>
            <p class="para_item">A report is generated when you import a CLSF allowing you to verify the Import operation.</p>
         </li>
         <li>
            <p class="para_item">Since the order of operations in the pre-V16 Operation Manager did not necessarily follow the order of the tool paths in the CLSF, a CLSF Import will cause the order of the operations in the Program View to match the order of the tool path in the imported CLSF. </p>
         </li>
      </ul>
      <p class="para_division">The path to import a CLSF is shown below.</p>
      <ul>
         <li>
            <p class="para_item">Tools&rarr;CLSF</p>
         </li>
         <li>
            <p class="para_item">Select the CLSF program you want to import and click OK</p>
         </li>
         <li>
            <p class="para_item">Click Import</p>
         </li>
         <li>
            <p class="para_item">Look in the Operation Navigator to see the newly imported CLSF tool paths.</p>
         </li>
      </ul>
   </body>
</html>