MULTICAx ID Plug-in Overview What's New? User Tasks Customizing Glossary Index

Transcription

1 MULTICAx ID Plug-in Overview What's New? User Tasks Requirements Methodologies and Advice Initializing the Initializing the for Indirect Mode Initializing the for Direct Mode with 3d com Importing IDEAS Data Importing Files Interactively Importing IDEAS Data Interactively in VPM Importing IDEAS Data Interactively in 3d com Loading I-DEAS Data in DMU from 3d com Translating Files from the Command Line Improved Associativity Support on MultiCAD Data Checking and Updating the Status of Assemblies Replacing MultiCAD Links Troubleshooting Configuration Errors Customizing External Formats Glossary Index

2 Overview Welcome to the MULTICAx ID (I) Plug-in User's Guide! This guide is intended for users who need to become quickly familiar with the product. This overview provides the following information: MULTICAx ID (I) Plug-in in a Nutshell Before Reading this Guide Getting the Most Out of this Guide Accessing Sample Documents Conventions Used in this Guide MULTICAx ID (I) Plug-in in a Nutshell Direct mode The MULTICAx ID Plug-in allows users to import IDI data generated from IDEAS native data (part and assembly models). This import converts IDI part geometry into the CATIA Graphical Representation (CGR) or CATPart formats, which renders it readable by V5. The MULTICAx ID Plug-in imports IDI assembly files into a V5 product structure document. Users can perform this import interactively or from the command line. Indirect mode The MULTICAx I Plug-in allows users to import: I-DEAS native data (part and assembly models). This import converts I-DEAS part geometry into the CATIA Graphical Representation (CGR) or CATPart formats, which renders it readable by V5. The MULTICAx I Plug-in imports I-DEAS assembly files into a V5 product structure document. Users can perform this import interactively or from the command line. Before Reading this Guide Prior to reading the MULTICAx ID (I) Plug-in User's Guide, you are recommended to have a look at the Infrastructure User's Guide for information on the generic capabilities common to all products. Getting the Most Out of this Guide To make the most out of this book, we suggest that a beginning user reads the Requirements chapter first of all and the other Users Tasks to find his way around the MULTICAx ID (I) Plug-in.

3 Accessing Sample Documents To perform the scenarios, sample documents are provided all along this documentation. For more information about this, refer to Accessing Sample Documents in the Infrastructure User's Guide.

4 What's New? New Functionalities IDI converter is available on UNIX Support of FTA 3D Annotations Enhanced Functionalities Update Status Checker Interactive update is now available. Naming Conventions in CGR

5 User Tasks Requirements Methodologies and Advice Initializing the Importing IDEAS Data Translating Files from the Command Line Improved Associativity Support on MultiCAD Data

6 Requirements Never modify data generated in V5: information could be lost and the MULTICAD Update could result in incorrect results. Part Number must be unique, all parts with the same name are considered as identical. On Windows, make sure the files to translate are not encrypted: push the Advanced button in the Properties dialog box of the file and uncheck the Encrypt contents to secure data option. Direct mode The MULTICAx ID Plug-in allows users to import IDI data generated from IDEAS native data (part and assembly models). This import converts IDI part geometry into the CATIA Graphical Representation (CGR) or CATPart formats, which renders it readable by V5. The MULTICAx ID Plug-in imports IDI assembly files into a V5 product structure document. Users can perform this import interactively or from the command line. The assembly import converts the I-DEAS assembly hierarchy into product structure, along with the proper positions. No attributes of the assembly other than hierarchy, positions, and colors of the geometry are addressed in assembly import.

7 Protocols and attributes For conversions, the following protocols or attributes apply: Length units for both parts and assemblies are converted to millimeters. Assembly-level colors and other features are not supported. Pure wire frame data is not supported during the conversion. Text and annotations are not supported. Protocols and attributes For conversions, the following protocols or attributes apply: Length units for both parts and assemblies are converted to millimeters. Assembly-level colors and other features are not supported. Pure wire frame data is not supported during the conversion. Text and annotations are not supported. Licensing requirements.mf1,.prt,.asm and.pkg extensions are not natively supported in DELMIA, therefore, in DELMIA, MIP license is required to access these extensions..idi extension is not natively supported in CATIA, therefore, in CATIA, IDL licenses (ENOVIA PORTAL, CATIA) are required to access these extensions. Foreign CAD license CAD Format Part Assembly File Extension V5 License required I-DEAS (native data) OK OK YES (indirect mode).mf1,.prt,.asm,.pkg MIP (DELMIA) I-DEAS (IDI) OK OK NO (direct mode).idi IDL (ENOVIA Portal) IDL (CATIA) IDP (DELMIA)

8 Methodologies and Advice This section provides information regarding exact geometry that users should be familiar with prior to configuring and using MULTICAx ID Plug-in. It also offers advice regarding when this technology should be used. Output Formats Importing I-DEAS data into V5 results in a conversion of the imported data to one of three formats, selectable by the user. Depending on how the imported data will be used, the user can choose whether to create CGR, CGR with canonical information or CATPart data. Each format has its own advantages and limitations: CGR (Visu mode). CATIA Graphical Representation is the visualization format of CATIA V5. With this very light format, you can do approximate measurement and have access to all the basic DMU functionalities. CGR with canonical information which enable exact measurement and exact snapping (Visu Snap mode) CATPart (CATPart mode). It is a standard V5 CATPart, therefore you can use it as any other CATPart. As the associative mode is specific to Multi-CAD data, it is advised to use publications before putting a link onto the Part. Otherwise, your link would be broken as soon as the CATPart is re-generated after the original CAD Part modification. Supported Features Access to part user attributes (via Edit->Properties) Move Exact positioning (Snap command) when using CATPart mode Exact positioning when using Visu mode To activate the Exact snapping support, the user has to be in Visu mode (Tools/Options/General/Compatibility/ExternalFormats/Link Mode). On top of that, the variable MCI_IDI_SNAP must be exported to any value. any value. Exact snapping for CGR conversion can be performed only if the IDI file contains BRep and Analytic data. Clash detection (on CGR) Approximate measurements (or exact measurement with a CATPart) Inertia and volume calculations. Color support. Translation of FTA data from IDI files to CATIA V5 CATPart files This functionality is available in CATPart mode, when the IDI 3D Annotation option is selected. See the Customizing section for more details. The annotations translated are:

9 Dimensions as Dimensions, Hole (matrix) as Note Object Attribute Hole, Notes as Texts, Spot Welds as Note Object Attribute Spot weld. The translation results in CATParts containing both BRep and FTA data, with no conceptual link between the BRep data and the geometry. The visual display of those annotations depends on the V5 settings. Naming Conventions in CGR The name of an IDEAS part or assembly inserted in V5 is as follows: if the Part Number of the inserted IDEAS part or assembly is xxxxx_yyyyy and its Part Name is abcd, the name in V5 will be xxxxx_yyyyy_abcd.cgr In the example below, the Part Number is Z04, the Part Name is SUPT ASSY-BED The name in CGR and in the specification tree is Z04#SUPT-ASSY-BED_347.1 Step Attribute support The names of the parts present in an I-DEAS model file appear as Part Number attributes in the Properties -> Product tab page in DMU Navigator. In addition, the I-DEAS part revision number is also imported into this tab page as the Revision attribute. These fields may be used for defining criteria used in the Product Structure Search command. Limitations Exact measuring not fully supported in Exact Geometry mode Other exact geometric features supported only by CATPart (assembly constraints, kinematics) Analysis limitations: volume and inertia calculation not possible in visualization and design modes; inclusion not detected during clash tests (even in visualization mode) The generated cgr are only surfacic, it means that no volume calculation can be performed on the models. On Windows platform, if IDEAS contain a part with characters like ">" or "<" in its Part Name, the conversion will fail. IDI data in V5

10 Options to be set in IDEAS modeler to generate correct IDI file Exporting of IDEAS part or assembly to IDI 1. Select menu File->Export->Viewer XML (IDI). User will be prompted to select part. After selection, options dialog box will pop-up. This box will have options listed in following table. Recommended setting of these options for type of IDI file ( BREP/FACET) are also listed in the table. IDI File Type Option Status Location of option Comments Options->Advanced->Advanced Export Options BRep Auxiliary attributes ON Part Options Auxiliary attributes are exported Precise BRep ON Part Options BRep data are exported Analytic output ON Part Options Analytic data are exported Tessellated Content Part Options All the four options under this category to be put OFF. OFF Facetted data will not be exported. Annotation Content ON/OFF Part and Assembly Annotation Options Put ON the options under this category if annotations are to be exported. Compress OFF File Options IDI file written is not zipped. Facetted Auxiliary attributes ON Part Options Auxiliary attributes are exported Precise BRep OFF Part Options BRep data are not exported Analytic output Part Options Analytic data are not exported OFF Tessellated Content Part Options All the four options under this category to be put ON. ON Facetted data will not be exported. Triangle Strips ON Advanced Options Facets made of Tristrips Triangle Fans ON Advance Options Facets made of Trifans Annotation Content ON/OFF Part and Assembly Annotation Options Put ON the options under this category if annotations are to be exported. Compress OFF File Options IDI file written is not zipped. IDEASIDIConv.exe IDEAS to IDI converter executable name is IDEASIDIConv.exe. IDEASIDIConv.exe converter will support reading of native IDEAS files. IDEAS to IDI converter will take the name of the IDEAS file and other user options as command line parameters. Converter will launch IDEAS modeler session. Input IDEAS file will be loaded in the modeler and IDEAS macros will be used to generate IDI file with appropriate options. Command line options supported are: -i Input IDEAS file name (.mf1,.pkg,.prt,.asm) -o Output IDI file name -type Asm for assembly and Prt for part( valid only for.pkg and.mf1 file) -facet To generate only facet output -brep To generate only BREP output with analytic data -all To generate both facet + BREP with analytic data output. -pro To specify the project name ( valid only for.asm,.pkg,.prt files) -lib To specify library name ( valid only for.asm,.pkg,.prt files) -a To specify name Assembly to be exported ( valid only for.asm ) -p To specify name of Part to be exported. ( valid only for.asm ) -rev To specify revision number of part to be exported ( valid only for.prt and.pkg)

11 IDEASIDIConv.exe will use IDEAS native modeler. Following environment variables need to be set to run the converter. Set SDRC_INSTL=E:\SDRC\I-DEAS9 ( location IDEAS software installation). set IONA=%SDRC_INSTL%\Iona set PATH=%PATH%;%SDRC_INSTL%\sec;%SDRC_INSTL%\ideas;E:\SDRC\Team\Master\Config\;%IONA%\bin;%SDRC_INSTL%\oirun\lib;%SDRC_INSTL%\bin; set SDRC_SOFTWARE=I-DEAS set SDRC_SEC=%SDRC_INSTL%\sec set LM_LICENSE_FILE=%SDRC_INSTL%\sec\Sdrc_Ms9.lic; ( if license is a node locked type) set LM_LICENSE_FILE=7609@octane ( if license is floating type ( IDEAS daemon license server name) set IDEAS_PARAM9=E:\SDRC\Team\Master\Config ( location of team configuration file.) set XKEYSYMDB=%SDRC_INSTL%\xfiles\Xkeysmdb set ORBIX_BIN=%SDRC_INSTL%\Iona\bin set SDRC_MPATHS=%SDRC_INSTL%\SDRCHelp set platform=winnt set SDRC_TEAM_SERVER_TYPE=FLEXLM set SETUPVARBS='1' set SystemDrive= D: set SystemRoot=C:\WINNT set QA_IDEAS_INSTALLDIR=%SDRC_INSTL% set QA_IDEAS_CURDIR=D:\tmp\test_dir ( location of folder where IDEAS temporary files are generated). Some examples of use of command line parameters are IDEASIDIConv.exe -i a.mf1 -o a_mf1.idi -type Asm -facet IDEASIDIConv.exe -i b.mf1 -o b_mf1.idi -type Prt -brep IDEASIDIConv.exe -i c.pkg -o c_mk1.idi -type Asm -all -pro system -lib idimport -a Engine_Cover IDEASIDIConv.exe -i d.pkg -o d_pkg.idi -type Prt -all -pro system -lib idimport -p PartName -rev 2 IDEASIDIConv.exe -i e.pkg -o e_pkg.idi -type Asm -all -pro system -lib idimport -p Part_1 -rev 2 IDEASIDIConv.exe -i f.asm -o f_asm.idi -facet -pro system -lib idimport -a Intake_manifold -rev 2 IDEASIDIConv.exe -i f.asm -o f_asm.idi -brep -pro system -lib idimport -p Bolt_2 -rev 1 IDEASIDIConv.exe -i g.prt -o g_prt.idi -all -pro system -lib idimport -p RH_DOOR -rev 12 Limitations of IDI To CATIA V5 Converter IDI-CGR Converter: converts IDI file with facet data to CATIA V5 CGR file. The generated CGR file does not have volume information: the input IDI file does not have connectivity information, hence CGR the file generated does not contain volume information. IDI-CATPart Converter: converts IDI file with BRep data to CATPart. It does not handle analytic surface/curve data. Harness Geom elements are not supported by the IDI converter. Therefore those elements will not be converted to V5. IDI files generated from IDEAS MS8 and containing isolated "&" characters are not supported as they are not XML compliant. if you want to read them properly, you need to replace all the occurrences of the isolated ""&" by "&" which is the correct XML syntax. IDI files generated with IDEAS MS10 are supported. The ideal working environment makes use of the following: Cache mode ON (set via Tools->Options->Infrastructure->Product Structure->Cache Management) File format: CGR for users that need better performance and do not require exact positioning (or exact measuring) CATPart for users that need the additional features provided by the CATPart format (such as exact measurement, exact positioning, kinematics, etc.)

12 Batch mode Using CATPart Geometry Mode vs Visu Mode The MULTICAx ID Plug-in supports CATPart mode, allowing for I-DEAS parts to be imported as CATPart data files. In this mode, I-DEAS part data contained by the solid body is transferred into a CATPart. Because CATPart files are large and take more time to convert, CATPart mode management is an optional feature. CATPart features and limitations The features and limitations of Multi-CAD CATParts are identical to those of all other V5 CATParts. When to use the exact geometry mode Exact geometry is used when exact positioning and exact measuring are required. The user should be aware that the conversion to the CATPart format requires more time than only generating the CGR (faceted) format. In addition, CATPart files are larger than their corresponding CGR files. Therefore, it is recommended that CATPart mode is only enabled if exact positioning, exact measurement or putting constraints is required.

13 Initializing the This section applies to DELMIA or ENOVIA DMU or ENOVIA 3d com When installing the MultiCAx media, all the references will be made to CATIA. This is not a problem and will not affect the product behavior. But it will create shortcuts and environment with CATIA names.

14 Initializing the for Indirect Mode Not available.

15 Initializing the for Direct Mode with 3d com This section applies to ENOVIA DMU or ENOVIA 3d com.

16 Importing I-DEAS Data Importing Files Interactively IDEAS data can be imported either interactively or from the command line. Native IDI data for direct mode See IDI data in V5

17 Importing Files Interactively This section shows you how to import I-DEAS parts and assemblies interactively into a product structure document. Direct mode.idi files generated from IDEAS native data are supported. The example below is given for one file extension. The operating mode is the same of all file extensions. Model file import 1. Open an existing or empty product structure document. 2. With the right mouse button, select the product under which the I-DEAS model is to be imported from the Product Structure. 3. From the Insert an Existing Component dialog box, set the Files of type field to mf1 and navigate to the directory where the I-DEAS model files are present.

18 4. Select the model file to be imported. The model will be imported under the selected product. 5. If the model file contains multiple top level assemblies, each assembly will be made the child of a dummy top level assembly, with the name of the input model file in the product structure. If the model file contains only parts, the converted CGR file will become the child of this dummy assembly.

19 Notes Instances (i.e., parts or subassemblies) that are hidden, suppressed, or pruned in the model file being imported are not converted. Therefore, such instances will not appear in the V5 Product Structure after the import.

20 Importing IDEAS Data Interactively in VPM Indirect mode Not available

21 Importing IDEAS Data Interactively in 3d com This section applies to ENOVIA DMU or ENOVIA 3d com.

22 3d com Interoperability: Interactively loading an I-DEAS file into DMU via 3d com This section applies to ENOVIA DMU or ENOVIA 3d com.

23 Translating Files from the Command Line This procedure describes how to run the CATDMUUtility batch program to import I-DEAS files from the command line. The CATDMUUtility is a batch process enabling the generation of.catproduct,.cgr and CATPart formats from I-DEAS files. Typical arguments and command switches passed to the CATDMUUtility batch are as follows : Converting a IDI file to a V5 CATProduct file : CATDMUUtility -f InputProductFile -product OutputCATProductFile Options Input and output options that can be used with CATDMUUtility are described below. Input Options -f Input file with appropriate extension. A path must follow this option. Output Options for IDI files the file extension should be.idi -product Output file for CATProduct corresponding to the input I-DEAS model file. Other Options The other options available for conversion are settings which correspond to the environment. These are defined in Tools -> Options -> General -> Compatibility -> External Formats. In particular, the use of cgr or CATPart can be customized in these options. For more information, see Customizing External Format Import in the Infrastructure User's Guide. How to run the batch In a command prompt window, the conversion batch is launched by entering the following command: Note that CATIA.V5R8.B08 is an example, the set of characters will vary according to the level of CATIA installed. On Windows "C:\<install_dir>\intel_a\code\bin\CATDMUUtility.exe" -env CATIA.V5R8.B08 -direnv "C:\Winnt\Profiles\All Users\Application Data\Dassault Systemes\CATEnv" -f E:\tmp\model_file.mf1 -product E:\tmp\prod1.CATProduct On UNIX <install_dir>/<os>_a/code/command/catstart -env CATIA.V5R8.B08 -direnv /CATEnv -run "CATDMUUtility -f /tmp/model_file.mf1 -product /tmp/prod1.catproduct"

24 Where -env... is the default environment and -direnv... is the directory path containing this environment. Please note that this conversion will take into account the settings in Tools -> Options -> General -> Compatibility -> External Formats. General Notes File paths must be absolute. Options may be specified in any order.

25 Improved Associativity Support on Multi-CAD Data This section describes how to import a layout file, as well as how to import files using the Exact Geometry mode. This section describes the concepts of improved associative support on Multi-CAD data in Batch mode, and discusses the conditions under which this associativity can be guaranteed. Note that: IDEAS data refer to indirect mode, idi data refer to direct mode, the operating mode is the same for indirect and direct mode How associative mode works When launching the Conversion Batch on Multi-CAD data, Multi-CAD files are converted and stored but this information (source or origin of the part files) cannot be visible by the user and CGR files are not stocked into Cache Memory. Only the 3D view can be seen by the user. By doing a batch conversion over a I-DEAS assembly, this assembly is transferred into a V5 format file: a CATProduct. All the Parts contained in this I-DEAS assembly are converted as a cgr or CATPart. During this transcription, we transfer all the assembly structure, geometrical information as well as original links. After this conversion, the CATProduct reproduces the 3D View of the original assembly and also stores a link onto the original files. The last information will enable the Multi-CAD Update Batch to check if V5 data are up to date compared with their original data. The following schema draws a parallel between the CAD System and CATIA V5. Step 3 corresponds to the modification or review of Imported CAD Data in CATIA V5. From the Import of CAD data to the Synchronization of V5 Session:

26 Launching the Update Batch means using the associative mode; the Batch operates on V5 data in order to update their structure or geometry according to the changes made by the I-DEAS designer onto the original data. On the one hand, if a I-DEAS part file has been modified, you can launch the update Batch on the CATProduct and the part file -not the whole assembly structure- is re-converted so that the V5 geometry of the I-DEAS part is always up to date. The part can be subsequently manipulated in V5. On the other hand, if only the I-DEAS assembly structure has been modified, you can launch the Batch on the CATProduct and the assembly file -not the part file- is re-converted so that the V5 product structure is updated. Here is a schema showing the conversion and update processes of an assembly structure when importing CAD data into CATIA V5. Multi-CAD Conversion and Update Processes:

27 The associative mode is the default mode. But if you do not launch the Batch, you will use what was called the nonassociative mode in the previous V5 versions. Associative mode is useful when a user wants to maintain synchronization with structure and/or geometry changes. But if you prefer to keep your assembly as it was at the moment of the conversion, you do not need to launch the Batch. Therefore, in this case, you will not do any synchronization between V5 data and original I-DEAS data. How to use the Update Batch for Multi-CAD Data This task shows you how to convert I-DEAS assemblies into V5 CATProducts and how to keep associativity between the modified CAD data and the converted product files, in V5. Note that CATIA.V5R8.B08 is an example, the set of characters will vary according to the level of CATIA installed. 1. On Windows, in a Command Prompt window, you can launch the conversion Batch by entering the following command: "C:\<install_dir>\intel_a\code\bin\CATDMUUtility.exe" -env CATIA.V5R8.B08 -direnv "C:\Winnt\Profiles\All Users\Application Data\Dassault Systemes\CATEnv" -f E:\tmp\sw.sldasm -product E:\tmp\prod1.CATProduct For information, "-env..." is the default environment (CATIA V5R8 for instance) and "-direnv..." is the directory path containing this environment. Please note that this conversion will take into account the settings in Tools -> Options -> General -> Compatibility -> External Formats. 2. In the original CAD system, modify a I-DEAS part contained in sw.sldasm. 3. Launch the update Batch by entering the command: "C:\<install_dir>\intel_a\code\bin\CATMCIReplace.exe" -env CATIA.V5R8.B08 -direnv "C:\Winnt\Profiles\All Users\Application Data\Dassault Systemes\CATEnv" - i E:\tmp\prod1.CATProduct -update If you open prod1.catproduct interactively in CATIA V5, you will be able to see the geometry modification. For more information about the launching of CATDMUUtility, please refer to Running CATDMUUitlity Batch Process, in DMU Navigator User Guide.

28 Checking and Updating the Status of Assemblies This task shows you how to check the Update Status of elements of an assembly. This command is available in CGR and CATPart modes. We strongly recommend that you save all documents before launching the command! Modified elements with a time stamp preceding that of the elements checked are not taken into account. 1. Open the Tools > Customize dialog box. Go to the Commands tab and select the All Commands category. 2. In the Commands list, select Update Status Checker and drag and drop the command into a toolbar.

29 3. Push the Update Status Checker icon and pick a node in the specification tree.

30 The Update Status Checker checks the status of the components at this node level. If the components are up to date, the light remains green and the message Nothing to update is displayed in the dialog box. If original elements have been modified and the imported elements are not up to date, the light turns red, the elements to update are listed in the dialog box (with their name, location of the original file and date of modification). A message explains how to update the elements.

31 If you select a line in the To update list, the corresponding element is highlighted in the specification tree. 4. Push the update button. All the elements listed in the To update field are updated. 5. Push Close to exit the action. You can repeat this control on different nodes of the same specification tree, i.e. at different levels of the assembly. The control will start at this level. Note that in CGR mode, as the assembly information are gathered at the root level of the assembly, any update information will refer to this root level whereas in CATPart mode the update information will refer to the actual level of the modification.

32 Replacing MultiCAD Links This procedure describes how to replace interactively broken MultiCAD links. This can also be done in batch mode, by launching the utility CATMCIReplace -i E:\path_to_product\top.CATProduct without the - update switch. It will automatically replace the broken link. Broken links can occur when : a MultiCAD conversion is launched in batch mode, impacting a document which is referenced by another V5 assembly. a MultiCAD update is performed on a part referenced by another assembly. The conversion changes the unique Id of the updated part, and the referenced document which have the Id saved in the aggregating product no longer exists. Broken links also occur when a file is replaced by another one in the file system, with the same file name (but different Id). The command looks for a document in the current directory which have the same file name as the one stored in the product structure. If the search succeeds, the command replaces all references to the old part by references to the new one in the aggregating product. 1. Open the Tools > Customize dialog box. Go to the Commands tab and select the All Commands category. 2. In the Commands list, select Remove link and drag and drop the command into a toolbar. 3. Push the Remove link icon

33 Nothing appears if there is no broken link. If a broken link is found and replaced, a dialog box like this appears: If a broken link is found but cannot be replaced, a dialog box like this appears:

34 Not available. Troubleshooting Configuration Errors

35 Customizing The quality and performances of your export or import data can be improved by choosing the most suitable settings. 1. Select the Tools -> Options command. The Options dialog box displays. 2. Choose the General category in the left-hand box, then Compatibility. 3. Use the arrow to navigate to the tab you need: External Formats

36 4. Set options in these tabs according to your needs. 5. Click OK when done.

37 Customizing External Formats Import If you have the SolidWorks, SolidEdge or Acis Plug-In license, the following categories of options will be available: visu format unit preferred conversion technology link mode others output of generated data Ideas ProEngineer Unigraphics You imported a CAD Part through the Insert ->Existing Component command. Visu Format Unit Millimeters per unit This setting allows you to specify the number of millimeters per unit of the model. For instance, if you have a file in inch, you need to enter 25.4 in this field. This option is taken into account when you have the following formats: SLP, STL, OBJ, BYU, IFF and _PS. Note: For a file of type _PS, the Visu Format Unit must be set to 10. Preferred Conversion Technology Indirect A CAD license will be used (available for DELMIA product line only). By default, this option is activated.

38 Direct No CAD license will be used. Support of ProE20 only. Support of UG data up to V18. For Solidworks, SolidEdge, Parasolid, ACIS, DXF 3D, Inventor and VDA-FS : use the direct mode on Windows. (Note: These formats are supported on Windows only.) Link Mode Visu Tesselated data. By default, this option is activated. Visu Snap Recovery of CAD's exact geometry to generate V5 CGR. Canonical shape properties are identified. The visualization mode enables part snapping capability. After selecting this option, this message appears: "Please, restart session to take modifications into account". CATPart Link with a V5 CATPart. Do not modify this CATPart in CATIA V5. Others Save Coorsys in Cgr Stores part coordinate systems in.cgr file. It is only supported in the indirect mode. This parameter determines whether coordinate systems present in imported ProE, UG or IDEAS parts will be imported into the resulting CGR files. Output of generated data

39 Output Path Lets you customize the Output File for generated data. It specifies the location where CGR, NCGM and CATParts will be generated. IDEAS (indirect mode only) If you have the IDEAS, ProEngineer or Unigraphics Plug-In licenses, additional options will appear in the External Formats tab. With the IDEAS Plug-In license, you obtain: IDI 3D Annotation (CATPart mode only) Select this option to convert IDI 3D Annotations to V5 (requires one of the following licenses): CATIA: FT1.prd or FTA.prd ENOVIA: DT1.prd DELMIA: MTR.prd or MFT.prd Tesselation Parameter Parameter of IDEAS chordal deviation. The Tesselation parameter holds the value tessellating the surfaces contained by the I-DEAS parts. Project Name This parameter is only used when converting data through the MS8 and MS9 based converter.this parameter must hold the name of the project under which the model file is being converted, and is registered, in the I-DEAS Data Management system. Library Name Pkg import (IDEAS package file) is the name of the library to transfer. Part or Assembly Name You can select any kind of data you want to read from the pkg file Part or Assembly and specify its name.

40 Part Number This setting is optional, you can specify the part number you want to transfer. Revision Number This setting is optional, you can specify the revision number you want to transfer. ProEngineer With the ProEngineer Plug-In license: Quilts Read Enables to activate the transfer of quilts surfaces inside CGR. This setting does not apply to NCGM or CATPart conversions. By default, this option is not activated. Simplified Representation Only part simplified representation is supported. To set the name of the part simplified representation to use before the Assembly conversion, check this box and enter the name. By default, this option is not activated. Instance Name When you want to import a specific instance of a generic assembly/part, check this button and specify the name of the instance of your choice. By default, this option is not activated. NOTE: For Simplified Representation and Instance Name, only upper case names are supported with the direct converter. Unigraphics (indirect mode only)

41 And with the Unigraphics Plug-In license: Layers String indicating the layers that need to be transferred during conversion. The syntax is: * : all layers are transferred by default 5, 8, 27 : only layers 5, 8, 27 are transferred : all layers from 8 up to 32 (including 8 and 32) are transferred. 2, 5, 8-32 : layers 2, 5 and all layers from 8 up to 32 (including 8 and 32) are transferred. Convert active layers only If this option is activated, it enables to transfer only active layers or to transfer all types of layers (active and inactive). It can be used together with the previous Layers setting, in that case only layers that are compliant with those two settings will be transferred. By default, this option is activated. Convert open surfaces If this option is activated, it enables to transfer UG Open Surfaces during the conversion. By default, this option is not activated. Drawing Name This setting is used in Batch mode only, while creating a CATDrawing. In this box you can specify the name of the drawing you want to transfer.

42 Glossary A assemblies Assemblies, assembly models, assembly files, assembly geometry, assembly hierarchies, and assembly data are terms used interchangeably throughout this documentation. These terms refer to a specific type of data that can be imported when it is created out of the V5 system. Assemblies consist of parts; assemblies make up products. C CGR file format CGR stands for CATIA Graphic Representation. This file format is the common format used for all V5 data. All MULTICAx Plug-in products convert native part data into CGR format. CGR files always have a.cgr extension. P parts Parts, part models, part files, part geometry, and part data are terms used interchangeably throughout this documentation. These terms refer to a specific type of data that can be imported when it is created out of the V5 system. Parts make up assemblies; assemblies make up products. product structure document The product structure document is a key component in V5. It provides users with a way to organize product creation in a hierarchical format. Each product structure document can contain parts, which make up assemblies, which, in turn, make up products.

43 Index Numerics 3d com importing data interactively importing I-DEAS data 3d com Interoperability A associative mode how it works using C Cache mode ON CAT_IDEAS_LEVEL CATDMUUtility command catstart command how to use command CATDMUUtility IDEASToNav D Differences between 3d com and V5

44 Direct mode Requirements E Editing the customized environment Cache mode ON CAT_IDEAS_LEVEL Differences between 3d com and V5 Editing the customized environment File format Initializing the for 3d com IT_CONFIG_PATH IT_DAEMON_PORT IT_ERRORS IT_IMP_REP_PATH IT_INT_REP_PATH IT_LOCATOR_PATH LD_LIBRARY_PATH LD_LIBRARYN32_PATH LIBPATH Main variables OPEN_IDEAS_CONNECT_ATTEMPTS Orbix requirements ORBIX_INSTL_DIR PATH Sample batch files SDRC_INSTL SDRC_MS_VERSION

45 SDRC_ORBIX_PORT SDRC_ORBIX_ROOT SDRC_ORBIX_SPOOL SHLIB_PATH Variables on UNIX Variables on Windows environment errors initializing troubleshooting F features supported File format FTA data Supported Features G Geometry Mode vs Visu Mode H How to run the batch I I-DEAS supported features

46 I-DEAS data importing I-DEAS Package Files Importing Data IDEASIDIConv.exe IDEASToNav command IDI data in V5 IDI file importing from the command line I-DEAS data Unigraphics data in 3d com Importing Data I-DEAS Package Files into VPM Model files Native IDEAS data Native IDI data Notes Prerequisites Importing data Interactively Indirect mode Requirements initializing in Windows on UNIX the environment Initializing the for 3d com Input Options Interactively Importing data into VPM

47 Importing Data IT_CONFIG_PATH IT_DAEMON_PORT IT_ERRORS IT_IMP_REP_PATH IT_INT_REP_PATH IT_LOCATOR_PATH L LD_LIBRARY_PATH LD_LIBRARYN32_PATH LIBPATH Licensing requirements Requirements Limitations Supported Features M Main variables Model files Importing Data

48 N Naming Conventions in CGR Native IDEAS data Importing Data Native IDI data Notes Importing Data Importing Data O OPEN_IDEAS_CONNECT_ATTEMPTS orbix requirements Orbix requirements ORBIX_INSTL_DIR Other Options Output Formats Output Options P Part Number PATH Requirements Prerequisites Importing Data Protocols and attributes - direct mode Requirements Protocols and attributes - indirect mode

49 Requirements R Requirements Direct mode Indirect mode Licensing requirements Part Number Protocols and attributes - direct mode Protocols and attributes - indirect mode S Sample batch files SDRC_INSTL SDRC_MS_VERSION SDRC_ORBIX_PORT SDRC_ORBIX_ROOT SDRC_ORBIX_SPOOL SHLIB_PATH step attributes support Supported Features FTA data Limitations

50 T troubleshooting configuration errors displaying the environment handling load errors handling specific errors prerequisites V Variables on UNIX Variables on Windows