<!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>STEP utilities</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">STEP utilities</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/step_settings.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/stepex_adv.html');return(false);">How To</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Options</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('dataexchange/how_do.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><div class="title_division">Overview</div>
      <p class="para_division">The following utilities are included in the NX STEP AP203 and AP214 kits. These utilities are provided to help support your data exchange process using STEP, although they are not part of the actual STEP translator.</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">These utilities are external NX Open programs, which requires an available User Function execute license to run.</p>
               </div>
            </td>
         </tr>
      </table>
      <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">The NX environment variables must be properly set up to execute these utilities. The easiest way to use this program is to use <b class="uiTerm">UGMENU</b>, select <b class="uiTerm">UGadmin</b> and get a shell. This shell will have the necessary environment variables set. You then execute the utilities by using <b class="commandName">$UGII_BASE_DIR/step203ug/utility_name</b> or <b class="commandName">$UGII_BASE_DIR/step203ug/utility_name</b>.
                  </p>
               </div>
            </td>
         </tr>
      </table>
      <div class="title_division">Massprop</div>
      <p class="para_division"><b class="uiTerm">Massprop</b> is a program that generates a report (text file) on the mass property information associated with all of sheet and solid bodies in a NX part. This mass property data compares to the data obtained (independently) from the sending or receiving system.
      </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">The STEP AP203 and AP214 translators update to include the STEP extension of <b class="uiTerm">Validation Properties</b>. This is the preferred mechanism for exchanging mass property information for validation purposes. The <b class="uiTerm">Massprop</b> tool will be withdrawn in a future NX release.
                  </p>
               </div>
            </td>
         </tr>
      </table>
      <div class="title_division">Usage:</div>
      <p class="para_division">massprop [options] partname.prt</p>
      <ul>
         <li>
            <p class="para_item">partname.prt is the NX part file from which mass property information will be extracted. The mass property information will be output to a file named partname_mass_prop.out.</p>
         </li>
         <li>
            <p class="para_item">Options include: &ndash;c the format required for PDES Inc. STEPNet testing results in a report of each solid individually rather than all solids as a unit. This will divide the solid bodies and the sheet bodies into different sections. The name of the output file generated will be <b class="uiTerm">partname&ndash;ug.csv. legacy</b> option. This is equivalent to the <b class="uiTerm">&ndash;i</b> option.
            </p>
         </li>
      </ul>
      <div class="title_division">Examples</div>
      <ul>
         <li>
            <p class="para_item">massprop testfile.prt &ndash; will give data on all of the solids as a group in the file &ndash; testfile_mass_prop.out.</p>
         </li>
         <li>
            <p class="para_item">massprop &ndash;c testfile.prt &ndash; will give data on all of the solids as a group in the file testfile_mass_prop.out.&nbsp;It will also give data on all solids as a group in testfile.prt&ndash;ug.csv.</p>
         </li>
         <li>
            <p class="para_item">massprop &ndash;i testfile.prt &ndash; will give data on each of the solids as a group in the file testfile_mass_prop.out.&nbsp;It will also give data on &nbsp;each solid in the file testfield.prt&ndash;ug.csv.</p>
         </li>
      </ul>
      <div class="title_division">Fix_step</div>
      <p class="para_division"><b class="uiTerm">Fix_step</b> is a general utility for reformatting a STEP exchange file to break lines longer than 80 characters or unformatting a STEP exchange file to generate lines longer than 80 characters. By default, STEP files generated by the STEP AP203 translator &nbsp;reformat. A line is defined as being a STEP entity definition ending in a semicolon. The <b class="uiTerm">step_format</b> option is useful when viewing unformatted STEP exchange files with a text editor that has limits on the line length (for example, vi).
      </p>
      <div class="title_division">Usage</div>
      <p class="para_division">fix_step step_format filename.stp output_file_name [#chars]</p>
      <p class="para_division">fix_step step_unformat filename.stp output_file_name</p>
      <p class="para_division">filename.stp is the STEP file to be formatted or unformatted.</p>
      <p class="para_division">output_file_name is the name to place the formatted or unformatted file into. This should be different from the input file name (filename.stp) to avoid UNIX file contentions. After fix_step has successfully completed, you can rename the new file, (output_file_name), back to the original input file name (filename.std), if desired. If output_file_name is not used, results display to the terminal.</p>
      <p class="para_division">You can use the #chars option to break lines longer than a specified length other than 80 characters.</p>
   </body>
</html>