Site Map - Catia Design

Transcript

V4 Integration Version 5 Release 14 Page 1 V4 Integration Overview Conventions What's New? Getting Started Opening a CATIA Version 4 Model in CATIA Version 5 Copying CATIA Version 4 Model Data to CATIA Version 5 Saving CATIA Version 5 CATPart Documents as CATIA Version 4 Models User Tasks Warning Prerequisites V418 Model Mandatory Cleaner Version 4 About Copying V4 Models to V5 Checking V4 Model Data Before Copying It to V5 : Interactive Checker Manipulating V4 Models in V5 Opening V4 Models in V5 Selecting Geometric Elements on V4 Models Selecting Federators and Sub-Federators in CATIA Version 4 Models Improved Design in Context: Access to Solid Edges Multi-Selecting V4 Components within the Specification Tree Managing V4 Models, PRJ Files, Library Objects in V5 Having Access to V4 Model Comment Alphanumerical Reorder of DETAILS Using the Workspaces Navigator for Model Editor Extract V4 Model From Sequential File Renaming Version 4 Documents regarding Windows File System Compatibility in Batch Mode Capability to identify a Model coming from CATIA V5 Copying 3D from CATIA V4 to CATIA V5 Partial Paste: Diagnosis Feature Main PartBody is no longer used in conversion AS SPEC Conversion of SolidM entities as Result (migrated as a PartBody) Migration of a DETAIL with only Geometry Migration of DETAILS with only DITTOS Migration of DETAILS with several Bodies Comparison of Result Option in Batch: V4/V5 BREP Info Checker Migrating from V4 To V5 in Batch Mode How to launch the Migration Batch intugbt0203.htm Converting CATIA Version 4 Models into CATIA Version 5 with the DataLifeCycle Batch Automatic Transfer of a Version 4 Model Comment into a Version 5 CATProduct or CATPart V4 Integration Version 5 Release 14 Automatic Transfer of a Version 4 Detail Comment into a Version 5 CATProduct or CATPart Converting a V4 Session to CATIA V5 with the V4 To V5 Migration Batch V4/V5 Associative Migration of Solid MML Structures and Mapping Opening a V4 Session in CATIA V5 Opening a CATIA V4 Session referencing CDM Models Having Access to PRJ Files on Windows Optimizing V4 Migration Optimizing V4 Family Migration: Deactivation of the No Show Filter Optimizing V4 Family Migration: Deactivation of the Solids' Parents Filter Copy/Paste Details and Dittos: Force Detail to Explode Copy/Paste Solids: Use of the Multi-Copy/Paste As Result With Link within CATIA V5 Evaluation of the V4 Sketch before applying Constraints Sweep Migration Optimization Sewing Migration on a New Sewing Feature Cleaning and Simplification of V4 Data V4/V5 Application Data Migration V4/V5 Part Design Data Migration Canonics Close and Offset Primitives Rolling Edge Fillet Face-Face Fillet Variable Radius Fillet Tritangent Fillet Fillet Sweep Pyramids, Volumes and Project Primitives Multi-Edge Fillets with Propagation Draft from Reflect Line Basic Draft Pipe Draft Both Sides Multi-Neutral Draft V4/V5 Manufacturing Data Migration V4/V5 AEC and Tubing Data Migration V4/V5 SheetMetal Design Data Migration V4/V5 Electrical Data Migration Methodology Migrating Step by Step... V4 - V5 Mapping Reference Information Frequently Asked Questions Migration of 2D Draw Elements and Views Accessing V4 Drawings within a model in CATIA V5 Copying 2D from CATIA Version 4 to CATIA V5 Migration of AUXVIEW2 Layout: Associativity with 3D Migration Converting V4 AUXVIEW2 Views to V5 Generative Drafting Views in Batch Mode Managing Standards for Migration Before You Begin Dimension Numerical Display Dimension Tolerances Page 2 V4 Integration Version 5 Release 14 Page 3 Dimension and Text Properties Arrows Frames & Balloons Fonts Line Thickness Filters Line Types Pattern Cells Managing AUXVIEW2 Defaults for Migration Reading Version 5 Data in Version 4 Format Saving CATIA Version 5 CATPart Documents As CATIA Version 4 Models Saving As Model: Saving CATPart "Product Description Property" As V4 Model Comment Saving CATIA V5 Text Annotation as CATIA V4 3D Text Saving CATIA Version 5 CATProduct Documents As CATIA Version 4 Sessions Saving a V5 Parabola as a V4 Parabola Saving a V5 Hyperbola as a V4 Hyperbola Saving a V5 Torus as a V4 Torus Saving a V5 Revolution Surface as a V4 Revolution Surface Supporting non-synchronized Elements in Save As Model (Associative Mode) Writing Axis Systems From a V5 track to a V4 Model V5/V4 File-based Migration Batch Optimizing V5/V4 Migration Workbench Description V4 Integration Menu Bar Geometry and Specification Toolbar Customizing Settings V4 Data Reading Saving as V4 Data V4/V5 DRAW V4/V5 SPACE V4/V5 SPEC Migration Batch Reference Information V5 Introduction versus Industrial Processes V4 / V5 Equivalences Using V4 Libraries Opening V4 Library Objects in V5 on Windows Opening V4 Library Objects in V5 on UNIX Displaying V4 Library Keywords in V5 Applying Filters to V4 Library Families Converting V4 Library Objects into V5 CATParts Converting V4 Libraries into V5 Catalogs Managing Layer Filters on V4 Models V4 / V5 Entities Wireframe and Surface Elements Axis Transfer of SPACE Entities: Visualization of V4 Support Edge for Broken Contextual Features Split V4 Integration Version 5 Release 14 Converting Version 4 Kinematics Data into Kinematics Version 5 Data Reading a V4 Route in a V5 Session Geometric Set Detail / Ditto Macro-Primitive Show / No Show Layer Filters Color Tables Model Naming Draw Elements Text Detail Raster Insertion Transparent View View Framing Glossary Index Page 4 Version 5 Release 14 V4 Integration Page 5 Overview V4 Integration in a Nutshell V4 Integration Version 4 data. is a product which includes two-way interoperability between CATIA Version 5 and CATIA It allows you to use Version 5 new applications and to get advantage of CATIA Version 4 legacy. As an open solution, it includes interfaces with the most commonly used data exchange industry standards. This means that: ● ● V4 designs can be accessed, exchanged and processed thus ensuring continuity and protecting V4 customer investment while taking advantage of Version 5's full functionalities. Using an integration tool called the CATIA Site Navigator in CATIA Version 5, CATIA Version 4 data can be read. If actual editing is required inside CATIA Version 5 application workbenches, this data can also be converted into V5 format. CATIA Version 5 data can be loaded and processed in a CATIA Version 4 session enabling V5 data to benefit from the breadth of the CATIA Solutions Version 4 portfolio. You will learn how to use V4/V5 Interoperability: ● ● ● What are the main functionalities What is the most appropriate methodology for your industrial needs: distinction between Interoperability and Translation What are the main equivalences between CATIA Version 4 and Version 5 from a software point of view. Before Reading this Guide Before reading this guide, you should be familiar with basic Version 5 concepts such as document windows, standard and view toolbars. Therefore, we recommend that you read the Infrastructure User's Guide that describes generic capabilities common to all Version 5 products. It also describes the general layout of V5 and the interoperability between workbenches. V4 Integration Version 5 Release 14 Page 6 Getting the Most out of this Guide To get the most out of this guide, we suggest you start reading and performing the step-by-step tutorial Getting Started. This tutorial will show you how to manipulate a V4 Model in CATIA V5. Once you have finished, you should move on to the next sections dealing with the handling of CATIA V4 data, then the different types of migration (Copy / Paste As Spec or As Result, Migration Batch) into CATIA V5. This guide also presents other interoperability capabilities allowing you to convert a CATProduct / CATPart into a .model or a .session. You can also take a look at the sections describing the V4 Integration Workbench at the end of the guide. Accessing Sample Documents To perform the scenarios, you will be using sample documents contained in the online/intug/samples folder. When samples belong to capabilities common to different products, those samples will be found in the online/cfyug/samples folder. For more information about this, refer to Accessing Sample Documents in the Infrastructure User's Guide. Conventions Used in this Guide To learn more about the conventions used in this guide, refer to the Conventions section. Version 5 Release 14 V4 Integration Page 7 Conventions Certain conventions are used in CATIA, ENOVIA & DELMIA documentation to help you recognize and understand important concepts and specifications. Graphic Conventions The three categories of graphic conventions used are as follows: ● Graphic conventions structuring the tasks ● Graphic conventions indicating the configuration required ● Graphic conventions used in the table of contents Graphic Conventions Structuring the Tasks Graphic conventions structuring the tasks are denoted as follows: This icon... Identifies... estimated time to accomplish a task a target of a task the prerequisites the start of the scenario a tip a warning information basic concepts methodology reference information information regarding settings, customization, etc. the end of a task Version 5 Release 14 V4 Integration functionalities that are new or enhanced with this release allows you to switch back to the full-window viewing mode Graphic Conventions Indicating the Configuration Required Graphic conventions indicating the configuration required are denoted as follows: This icon... Indicates functions that are... specific to the P1 configuration specific to the P2 configuration specific to the P3 configuration Graphic Conventions Used in the Table of Contents Graphic conventions used in the table of contents are denoted as follows: This icon... Gives access to... Site Map Split View mode What's New? Overview Getting Started Basic Tasks User Tasks or the Advanced Tasks Workbench Description Customizing Reference Methodology Glossary Page 8 Version 5 Release 14 V4 Integration Page 9 Index Text Conventions The following text conventions are used: ● The titles of CATIA, ENOVIA and DELMIA documents appear in this manner throughout the text. ● File -> New identifies the commands to be used. ● Enhancements are identified by a blue-colored background on the text. How to Use the Mouse The use of the mouse differs according to the type of action you need to perform. Use this mouse button... Whenever you read... ● ● Select (menus, commands, geometry in graphics area, ...) Click (icons, dialog box buttons, tabs, selection of a location in the document window, ...) ● Double-click ● Shift-click ● Ctrl-click ● Check (check boxes) ● Drag ● Drag and drop (icons onto objects, objects onto objects) ● Drag ● Move ● Right-click (to select contextual menu) Version 5 Release 14 V4 Integration Page 10 What's New? New Functionalities: From CATIA V4 to CATIA V5 Warning Prerequisites Checking V4 Model Data Before Copying It to V5: Migration As Result of V4 Draft Reflect Line Keep Edges V4 Draft Reflect Line Keep Edges that are copied / pasted As Spec in CATIA V5, are migrated As Result, with their branches. No error is detected during the Check. Migrating from V4 To V5 in Batch Mode Converting CATIA Version 4 Models into CATIA Version 5 with the DataLifeCycle Batch This migration tool provides an interactive interface working on a different application from CATIA Version 5. Like the V4 To V5 Migration Batch, this tool allows you to convert CATIA Version 4 models into CATIA Version 5 models and have access to databases as well. With a V4/V5 Migration via the DatalifeCycle Batch, there is a new kind of document structure. Migrating V4 3D Texts into V5 Annotations If you check the Keep 3D Text option in the Tools -> Options -> General -> Compatibility -> V4/V5 SPACE, V4 3D Text will be transferred into a CATPart and the Text's position is kept. But there are some cases when a 3D Text, set on particular features, is not converted in CATIA V5. Optimizing V4 Migration Copy/Paste Details and Dittos: Use of the Interactive Multi-Copy/Paste As Result With Link within CATIA V5 The interactive Multi-Copy / Paste As Result With Link is now the default mode. It is done without the setting. It saves CPU, memory place and time. Migrating from V5 To V4 in Batch Mode V5/V4 File-based Migration Batch Converting CATIA Version 5 documents into CATIA Version 4 documents with the DataLifeCycle Batch: This tool allows you to convert CATIA Version 5 documents into CATIA Version 4 documents. The CATIA Version 5 documents can be retrieved from files and from databases as well (ENOVIA VPM, ENOVIA LCA). Customizing Saving As v4 Data Associativity Mode A new button "No Solid Creation" is available and If one checks this button, no V4 solid will be created; only V4 volumes will be generated in the .model. Small Edges and Faces Cleaning V4 Integration Version 5 Release 14 Page 11 The parameter entered in the Small Edges And Faces Cleaning frame is used in order to choose a maximum gap that may be generated when a small element (Face or Edge) is cleaned in V4 model. Enhanced Functionalities Migrating from V4 To V5 in Batch Mode Manipulating CATIA Version 4 Documents in CATIA Version 5 Using the Workspaces Navigator for Model Editor Multi-selection is possible: if you select two Dittos in *MASTER, the workspaces in which they are contained are highlighted in the last column of the Workspace Navigator panel. In the last column of this panel, you can visualize the Detail's comment if there are any. V4 Integration Version 5 Release 14 Page 12 Getting Started Before getting into the detailed instructions for using CATIA Version 4 Interoperability, the following tutorial aims at giving you a feel as to what you can do with the product. It provides a step-by-step scenario showing you how to use key functionalities. The main tasks described in this section are: Opening a CATIA Version 4 Model in CATIA Version 5 Copying CATIA Version 4 Model Data to CATIA Version 5 Saving CATIA Version 5 CATPart Documents as CATIA Version 4 Models Version 5 Release 14 V4 Integration Page 13 Opening a CATIA Version 4 Model in CATIA Version 5 This task shows you how to open a CATIA Version 4 model in CATIA Version 5. 1. Click the Open icon or select the File->Open command. The File Selection dialog box appears. 2. In this box, find the directory specified above then either select XWINGS.model and click the Open button or double-click it. (Where there are many different types of files, it may be useful to click the Files of type list and specify model as the document type.) The following document will appear: V4 Integration Version 5 Release 14 Page 14 For other ways of opening existing Version 4 models, see "Opening Existing Documents" and "Opening Most Recently Used Documents" in the CATIA - Infrastructure User's Guide. V4 Integration Version 5 Release 14 Page 15 Copying CATIA Version 4 Model Data to CATIA Version 5 This task shows you how to copy the specifications or geometry of a CATIA Version 4 model to CATIA Version 5. The following data can be copied from CATIA Version 4 to CATIA Version 5: ● surfaces (both polynomial and BSpline) ● clouds of points ● faces ● edges ● volumes ● parabolas ● skins and exact solids ● hyperbolas ● curves (both polynomial and BSpline) ● CCVs ● mockup solids (see remarks regarding copy/pasting mockup solids below) ● polyhedral surfaces and solids ● NURBs (curves and surfaces) ● circles ● PIP elements (Tubing) ● ellipses ● GPR elements (AEC Primitives) ● points ● ● lines ● planes STR elements (planar structures, linear structures) The following task describes how an entire model is pasted from Version 4 to Version 5. You can also select the geometric elements listed above and insert them into an already existing Version 5 document. Open the document LAMP.model. You should have already completed the task Checking CATIA Version 4 Model Data Before Copying It to CATIA Version 5. You may want to customize certain settings before proceeding with this task. For more information, see Customizing Compatibility Settings. Page 16 Version 5 Release 14 V4 Integration 1. Open a new CATIA Version 5 CATPart document. To do this, refer if necessary to "Creating New Documents" in the CATIA - Infrastructure User's Guide. 2. In the specification tree or geometry area where the Version 4 model is displayed, select the geometrical element or elements you wish to convert. 3. If you intend to copy the geometry you can either: ● drag and drop the element(s) onto the appropriate location in the CATIA Version 5 document. The cursor changes slightly i.e. the symbol drop is allowed. If the cursor changes to the symbol location. ● appears indicating where a , the drop is not allowed in that or: a. Put the element(s) you have selected in the clipboard by clicking the Copy icon , select the Edit->Copy command or select the Copy command in the contextual menu. b. In the specification tree of the CATIA Version 5 document, select the appropriate item (for example, PartBody or Body.1, Body.2, etc. in the PartDesign workbench). c. Click the Paste icon or select the Edit->Paste command or select the Paste command in the contextual menu. This operation recovers the specifications previously put in the clipboard. 4. If you intend to copy the specifications: a. Put the element(s) you have selected in the clipboard by clicking the Copy icon , selecting the Edit->Copy command or selecting the Copy command in the contextual menu. b. In the specification tree of the CATIA Version 5 document, select the appropriate item (for example, PartBody or Body.1, Body.2, etc. in the PartDesign workbench). c. Select the Edit->Paste Special... command or select the Paste Special... command in the contextual menu. The dialog box below appears: V4 Integration Version 5 Release 14 Page 17 d. Select CATIA_SPEC and click OK. This operation recovers the specifications previously put in the clipboard. 5. Click the Update icon to view the copied data or use Edit -> Update. 6. You may want to click the Fit All In icon to fit all data in the window. Notice that the toolbars change depending on whether a CATIA Version 4 model or a CATIA Version 5 document is selected. If you copied the geometry the result should look something like this (using the Window->Tile Horizontally command): V4 Integration Version 5 Release 14 Page 18 If you copied the specifications the result should look something like this (using the Window->Tile Horizontally command): V4 Integration Version 5 Release 14 Page 19 Bear in mind the following when copy/pasting: ● The migration of V4 model data to a V5 document generates a report (.rpt) file named after the model migrated: ● ● on Windows: in C:\Documents and Settings\user\Local Settings\Application Data\DassaultSystemes\CATReport on UNIX: in /u/users/username/CATReport , but this depends on the path setting in env file. If you used the CATIA_SPEC option mentioned above note that only the paste operation is included in the report i.e. the actual update of the CATPart document is not taken into account. For more information about the usage of the V4/V5 BREP Info Checker, please refer to Comparison of Result Option in Batch: V4/V5 BREP Info Checker. V4 Integration ● ● Version 5 Release 14 Page 20 When copy/pasting mockup solids : If the solid has a history then the V5 specifications are created. However, if the solid has no history or if the CATIA_RESULT option is selected (using the Paste Special... command) then a cgr file is generated containing the visualization information of the solid. The name of this file is "mymodel_SOLMxxx" and is located in the same directory as the V4 CATIA model. This file can be inserted into the Product Structure application. When copy/pasting sets of surfaces : If you want to get a unique surface in V5, it is more efficient to perform the join in V4 before the migration than in V5 on the resulting surfaces. V4 Integration Version 5 Release 14 Page 21 Saving CATIA Version 5 CATPart Documents As CATIA Version 4 Models This task shows you how to save CATIA Version 5 CATPart documents as CATIA Version 4 models. Open the document MultiBodyAssembly.CATPart It looks like this: V4 Integration Version 5 Release 14 Page 22 You will remember that in Version 4 the declaration parameter catsite.WRITING_CODE_PAGE declares the code page to be stored in the CATIA data to be written. Such information such as the writing code page was specified in V4 by means of the parameter settings in the declaration files. These declaration parameters are no longer supported in CATIA Version 5. Such information must therefore be provided by means of the dialog boxes described below, before attempting to save a V5 CATPart document as a V4 model. If you want to use the writing code page ISO-8859-1 go straight to step 4. It is the default value so normally, unless another code page was already specified, you can go ahead with the save. However, if you want to use a writing code page other than ISO-8859-1 start with step 1. 1. Select the Tools->Options... command. The Options dialog box appears, choose the General -> Compatibility category in the left-hand column. 2. Click the V4 Data Reading tab. The following dialog box appears: 3. Open the Reading Code page list (indicated by the arrow above), select the appropriate code page: V4 Integration Version 5 Release 14 Page 23 4. You can modify the V4 Model Dimension in order to be consistent with the V4 destination site value. 5. Select the File->Save As... command. 6. In the Save As dialog box, select the location of the .model document to be saved and rename it (or not) as required. 7. Click the Save as type: list and select model in the list displayed as shown below: 8. In the same box, click on Save. The MultiBodyAssembly.model just created can now be opened, in CATIA Version 4 and will look something like this: V4 Integration Version 5 Release 14 Page 24 V4 Integration Version 5 Release 14 Page 25 User Tasks Two-way interoperability between CATIA Version 5 and CATIA Version 4 data is treated in this chapter User Tasks. It is divided into two sub-chapters: Migrating from CATIA V4 to CATIA V5 These scenarios show you what can be done in CATIA V5: reading CATIA V4 data in CATIA V5, copying/pasting As Result or As Spec from CATIA V4 to a V5 Document, migrating V4 data into V5 with the CATV4ToV5Migration Batch. Migrating from CATIA V5 to CATIA V4 This section explains you that CATIA V5 data can be loaded and processed in a CATIA V4 session enabling V5 documents to benefit from the features of CATIA V4 Solutions. Migrating from CATIA V4 to CATIA V5 Before migrating: Warning Prerequisites Manipulating V4 Models in V5 Copying/Pasting AS RESULT or AS SPEC a V4 Document into CATIA V5: Copying 3D Data from CATIA V4 to V5 Document Partial Paste: Diagnosis Feature Main PartBody is no longer used in conversion AS SPEC Conversion of SolidM entities as Result (migrated as a PartBody) Copy/Paste Solids: Use of Interactive Multi Copy/Paste As Result With Link within CATIA V5 Migrating a V4 DETAIL: Migration of a DETAIL with only Geometry Migration of a DETAIL with only Dittos Migration of a DETAIL with several Bodies V4 Integration Version 5 Release 14 Having access to V4 and V5 properties: Comparison of Result Option in Batch: V4/V5 BREP Info Checker Migrating in Batch Mode: Migrating from V4 to V5 in Batch Mode Opening a V4 Session in CATIA V5: Opening a CATIA Version 4 Session in CATIA Version 5 Opening a CATIA Version 4 Session referencing CDM Models V4/V5 Infrastructure: Having Access to PRJ Files on NT Using CATIA Version 4 Libraries in CATIA Version 5 Optimizing V4V5 Migration: Optimizing V4V5 Migration How to migrate Application Data Migrating 2D Elements into CATIA V5: Migration of 2D Draw Elements and Views Managing AUXVIEW2 Defaults for Migration Migrating from CATIA V5 to CATIA V4 Reading: Reading Directly V5 Data in V4 Page 26 V4 Integration Version 5 Release 14 Saving As Model: Saving a V5 Part as a V4 Model Saving As Model: Saving CATPart "Product Description Property" As V4 Model Comment Saving CATIA V5 Text Annotation as CATIA V4 3D Text Saving a V5 Product As a V4 Session Saving a V5 Parabola as a V4 Parabola Saving a V5 Hyperbola as a V4 Hyperbola Saving a V5 Torus as a V4 Torus Saving a V5 Revolution Surface as a V4 Revolution Surface Supporting non-synchronized Elements in Save As Model (Associative Mode) Writing Axis Systems from a V5 Track to a V4 Model Migration in Batch Mode: V5/V4 File-based Migration Batch Optimizing V5V4 Migration: Optimizing V5/V4 Migration Page 27 V4 Integration Version 5 Release 14 Warning Prerequisites V418 Model Mandatory Cleaner V4 Before Migrating a Mock-Up Solid into CATIA V5 Checking V4 Model Data Before Copying It to V5: Interactive Checker Page 28 V4 Integration Version 5 Release 14 Page 29 V418 Model mandatory If you encounter any difficulty copying CATIA V4 models to CATIA Version 5, there are a certain number of precautions you should take prior to the copy operation. Precautions to be taken in CATIA Version 4 prior to the copy operation ● ● ● If the model to be copied is an exact solid it must be processed using the Force Update option in the Smart Solid mode. This operation must be done on CATIA 418 or higher. It is also recommended to run the CATCLN utility on the model to be copied. Again, this operation must be done on CATIA 418 or higher. For more information see Cleaner Version 4. Remember to run the specification check on all the V4 models you wish to copy to CATIA Version 5 as it provides you with the following invaluable information: ❍ identification of the primitives which are converted to datums, indicating loss of canonical information (see the Restrictions section below for the complete list). This is shown in the Message column of the Check Validity dialog box, for example: 2 primitives checked as geometry only. ❍ ❍ identification of the operations which are not supported in V5R2 and MUST BE DELETED before proceeding with the copy operation (see the Restrictions section below for the complete list). This is shown in the Message column of the Check Validity dialog box, for example: 2 operations not implemented. identification of the non-supported primitives (see the Restrictions section below for the complete list). For more detailed information, you only have to double-click on the appropriate message in the rightmost column of the Check Validity dialog box. This displays the contents of the model in the form of a specification tree (see Checking CATIA Version 4 Model Data Before Copying It to CATIA Version 5). ● ● ● If, in CATIA Version 5, you intend to make only cosmetic changes to a Version 4 solid with no impact on the specification tree you can simply copy the solid's geometry. However, if your modifications are major and will considerably alter the specification tree you would be better advised to copy the solid's specifications (see Copying CATIA Version 4 Model Data to CATIA Version 5). Make sure that the update option selected in the General tab of the Options dialog box (displayed using the Tools->Options command) is NOT set to Automatic. When updating, make sure that you select the Inactivate option in the Update Diagnosis dialog box to deactivate any troublesome operations or primitives in CATIA Version 4. Do NOT delete them as such data, although not copied, can, once the rest of the model has been successfully copied, be recreated in CATIA Version 5 in a more satisfactory way. In a future version of CATIA Version 5, this requirement will no longer apply. V4 Integration Version 5 Release 14 Page 30 Restrictions As mentioned above, certain restrictions apply when copying models from CATIA Version 4 to CATIA Version 5: The primitives converted to datums are: ● pyramids ● sweep spines, sweeps with a non-close profile, until a sweep ● import primitives (linked to a solid in another model). The non-supported operations are: ● certain draft types, for example, keep edges with more than two neutrals ● certain fillet types, for example, rolling edges. The non-supported primitives are: ● macroprimitive multibodies ● non-isometric transformations. The elements copied as geometry only i.e. not as history are: ● all elements (including SKD) with the exception of exact and mockup solids. Page 31 Version 5 Release 14 V4 Integration Cleaner Version 4 This task shows you how to make a diagnostic, and eventually a healing, of V4 Model Data validity before copying it to CATIA Version 5. Open the document DEMO_UNSMART_1.model. It is also advisable to run the CATCLN (Cleaner) utility on the model to be copied. Again, this operation must be done on CATIA 418 or higher. If you encounter this kind of message: when checking elements of CATIA V4 models (or copying it to CATIA Version 5), there are a certain number of precautions you should take prior to do the copy operation (again), to manage it successfully as possible. The meaning of this message: ● This message appears when a problem in the reading of V4 model data has been detected by Catgeo. ● Then, you need to ask yourself if the V4 model is following operations: ● Tape < /cln > in the text field ● FORCE UPDATE (YES) the solids ● Save the model model - valid into CATIA V4 and proceed to the - if there are some in the A second screen exposes a Model analysis by listing the number of detected invalid elements: V4 Integration Version 5 Release 14 Page 32 Click on the four buttons : Delete (invalid elements), Modify (invalid elements), Pack (memory) and All (to see all the messages and results of the checking). Click YES to Execute and the invalid elements are turned into valid components to be migrated. If you click on YES again the"events" number may have turn to 0. FORCE UPDATE then the solids into the model, if there are some. Save the model. Then you can migrate the elements of this model from CATIA V4 to CATIA V5. ● If during a migration from CATIA V4 to CATIA V5, you have both messages: ❍ ❍ < The CATIA V4 solid XXX has not been pasted <$DRAFT.1 ko...etc>, it is due to the bad data structure of the solid, detected into the Draft V4.$DRAFT.1. The next step is to tape /cln in the text field. The Cleaner's manipulations have modified the V4 Model Data Structure. If the model contains solids and they depend on modified data. Therefore, it is important to force the solid to compute again, to FORCE UPDATE (YES) in order to check that every element is coherent and finally Save the Model before translating it. If you do not FORCE UPDATE the solid, you may translate an unstable solid. V4 Integration Version 5 Release 14 Page 33 Before Migrating a Mock-Up Solid into CATIA V5 After the Copy/Paste AS SPEC of a V3 SolidM in CATIA V5, the update fails because the contour of the primitive is not closed. For the migration of a V3 Mock-Up Solid into CATIA V5, you first need to migrate it into CATIA V4 by using the /m solm34 function on the model in CATIA V4. This function allows you to convert the model into format V4 and then, create a good contour of the primitive. After this operation, the migration forward CATIA V5 is successful. This task shows you how to launch the macro before migrating and how this tool makes a Mock-Up Solid validity (on contours) before copying it to CATIA Version 5. You can get all the specifications of the Solid in CATIA V5. Before migrating, to improve resolution (on contours), it is recommended to launch the solm34 macro: ● Tape < /m solm34 > in the text field ● UPDATE (YES) the solids - in the model - ● Save the model An automatic compatibility check has occurred on the V3 Solids to be transferred into CATIA V4 and they can be migrated into CATIA V5. You obtain a Solid Exact or a Part with all its specifications in CATIA V5. If you do not UPDATE the Solid, you may translate an unstable Solid. V4 Integration Version 5 Release 14 Page 34 Checking V4 Model Data Before Copying It to V5: Interactive Checker The following sections describe the usage of the Interactive Checker. The first task explains how to check CATIA V4 Model data before copying it to CATIA V5. The second task gives the user the example of a Check KO with a Skin Offset. And the third task explains why a Check validity operation on a V4 model may be OK and the document's geometry is invalid in CATIA V5. Checking CATIA Version 4 Model Data Before Copying It to CATIA Version 5: This first task shows you how to check CATIA Version 4 model data before copying it to CATIA Version 5. Open the document DRAFT_REFLECT_KEEP_EDGE.model. Before checking either the geometry or specifications of Version 4 data, you should understand the distinction between the two: ● The geometry is just the three-dimensional representation of the elements contained in the data. An example would be the set of faces that make up a solid. It is roughly equivalent to the Boundary Representation (BRep) used in CATIA Version 4. ● ● ● Geometry Check is a check by transferring the solid's geometry only through copy - paste special As a Result. The specifications are made up of the entire history of the actions performed to obtain the data. They are shown in the form of a tree and are roughly equivalent to the CSG tree used in CATIA Version 4. Specification Check consists in transferring the solid with Geometry and the History tree : copy paste special - As SPEC. Note that a specification check is only meaningful when applied to exact and mockup solids. 1. Select one or more geometrical elements in the geometry area: Version 5 Release 14 V4 Integration This activates the Geometry Check toolbar. and Specification Check Page 35 icons in the Version 4 model 2. In the Version 4 model toolbar, click the Check Specifications or Check Geometry icon. The Check Validity dialog box appears: V4 Integration Version 5 Release 14 Page 36 In our example, the Check Validity box shows that: V4 Draft Reflect Line Keep Edges that have been copied / pasted As Spec in CATIA V5, are migrated As Result, with their branches. No error is detected during the Check. Messages for the solid's transfer with history tree can be: ● "Geometry check only": you can transfer the solid's geometry only through Copy - Paste Special - As Result. When you transfer the solid as geometry only, it is transferred as datum (BRep). You can only perform operations on the geometry. ● ● "0 operations not implemented": all the operations (Fillet, Union, Intersection,...) of this solid's tree are implemented, which means that you can start the migration and the same operations will available in CATIA V5. "1 primitives checked as geometry only": one primitive cannot be migrated As Specs, but only As Result. Certain types of primitives will be converted as datum: ● Pyramids ● Sweep Spines, Sweep with non closed profiles, Until a Sweep ● Projects ● Import Solids (Link to a solid in another model) ● ● If the solid contains one of the above primitives, unsupported solids are transferred as BRep only. The V5 body is based on both specifications and datum features. Draft Reflect Line Keep Edges. This feature is not a terminal leaf into the tree of feature. So all the branch standing before must be migrated As Result. In the Check Validity dialog box there are four columns: ● the first column showing the overall result, color-coded as follows: ❍ G (green): will be copied as is to CATIA Version 5. The check is OK. ❍ ❍ R (red): will NOT be copied to CATIA Version 5 as is. This is a KO Check. Y (yellow): will NOT be copied to CATIA Version 5 because of a link to a red-coded item. This is KO Check due to the element supporting by the solid. Version 5 Release 14 V4 Integration ● the Version 4 identifier, ● the format i.e. Specifications, ● the Message column providing the number and type of problems. Page 37 3. To view the results of a specification check, double-click on the contents of any of the columns in the Check Validity dialog box. The tree structures of some models are very large. Use the scrollbars to locate any red elements. There are several in the model shown below. Here is just one example: 4. If one element is red, right-click it to find out exactly what the problem is: The $ symbol means that the Pipe item is an unresolved feature in V4 (same symbol in the V4 tree). If you click the background and not an element, a menu containing two options is displayed: ● Reframe graph, which centers the tree structure ● Print whole, which prints it (for details, see "Printing Documents" in the CATIA - Infrastructure User's Guide). If you make an Interactive Checker and encounter a reading problem of V4 elements (not updated solid), the copy / paste operation is locked by the Check, the solid cannot be pasted. Then it is advisable to run the CATIA Cleaner utility on the model to be copied. It is also possible to perform a batch Check using the new batch conversion tool. For more information see Converting CATIA Version 4 Models to CATIA Version 5 in Batch mode. V4 Integration Version 5 Release 14 Page 38 A CHECK operation on a Version 4 model containing a SKIN OFFSET that cannot be converted into CATIA Version 5 This second task shows you how to convert a V4 model despite the invalid geometry of its Skin Offset. Open the V4 model document : SKIN-OFFSET.model. 1. Apply a Check validity operation on a V4 model, the model's Skin Offset cannot be converted into CATIA V5 because there is no image of a Skin Offset in CATIA V5. In CATIA V4, the Skin Offset is valid but this element cannot be migrated into CATIA V5 and it is systematically KO at the Check operation. You can however copy As Result and paste the V4 model into CATIA V5. But it will have the same defective quality in V5 as in V4. The Geometry Check operation allows to analyze the geometry quality of the V4 model's components. 2. You cannot copy / paste the V4 model into CATIA V5 otherwise a warning message is displayed : the V4 element could not be converted properly. V4 Integration Version 5 Release 14 Page 39 There is an advice in this message : "Clean the model". Indeed, you can resort to the Cleaner to repair some anomalies. The Cleaner will check the structural data of the model before migrating it in CATIA V5. The user has access to the V4 model geometry (except the Skin Offset) in V5: V4 Integration Page 40 Version 5 Release 14 For more information about how to use the Cleaner, refer to Cleaner Version 4. A CHECK operation on Version 4 model data may be OK, but this migrated document has however invalid geometry in CATIA Version 5 This third task explains how the V4 model can be migrated despite a KO Check result (on Surfaces). The Geometry Check may be valid, but sometimes V4 Geometry cannot be supported in CATIA V5: design is tolerated in CATIA V4 but not in CATIA V5. Therefore, it is necessary to solve this incident during the migration. Open the V4 Model entitled ANOMALIES.model. 1. Apply the Specifications Check on this model : select one or more geometrical elements in the geometry area and click the Check Specifications icon . The Check Validity dialog box appears; the Geometry check is OK for the Faces: The Geometry of some Surfaces (*SUR1-> *SUR8; *SUR10, 11 and 13) is invalid but the Faces Check is OK. The Face geometry is valid whereas the Surface geometry is not, because the Face is an element, a restriction of the Surface and it was created separately. V4 Integration Version 5 Release 14 Page 41 2. Copy / Paste the V4 model into a V5 document, a CATPart for example. 3. Update the CATPart document. You can visualize the model in CATIA V5 but there are anomalies in Surface 3 and Surface 4 for instance. This component has not always the same shape as in CATIA V4, before the Copy / Paste operation. SUR 3 and SUR 4 (enclosed in red) have no longer the same quality, both elements are twisted and have X shaped Faces. V4 Integration Version 5 Release 14 Page 42 It is possible for you to transform the invalid geometry in the Shape Design workbench. And in the Freestyle workbench, you can display the control points in order to analyze the surfaces and modify them. V4 Integration Version 5 Release 14 Page 43 Manipulating CATIA Version 4 Documents in CATIA Version 5 Opening V4 Models in V5 Selecting Geometric Elements in V4 Models Selecting Federators and Sub-Federators in V4 Models Improved Design in Context: Access to Solid Edges Multi-Selecting Components within the Specification Tree (to use Hide/Show) Managing CATIA Version 4 Models, PRJ Files and Library Objects in CATIA Version 5 Having Access to V4 Model Comment Alphanumerical Reorder of DETAILS Workspaces Navigator for Model Editor Extract V4 Model from Sequential File in Batch Mode Rename Version 4 Documents regarding NT File System Compatibility in Batch Mode Capability to identify a Model coming from CATIA V5 Version 5 Release 14 V4 Integration Page 44 Opening CATIA Version 4 Models in CATIA Version 5 This task shows you how to open a CATIA Version 4 model in CATIA Version 5. You may want to customize certain settings before proceeding with this task. For more information, see Customizing Compatibility Settings. Click the Open icon or select the File->Open command. The File Selection dialog box appears. In this box, find the directory specified above then either select XWINGS.model and click on the Open button or double-click it. (Where there are many different types of files, it may be useful to click the Files of type list and specify model as the document type.) The following document will appear: V4 Integration ● Version 5 Release 14 If, in CATIA Version 4, you defined specific views for a model by means of IMAGE/WINDOW+DEFINE, you can still use these views by clicking the ● ● Page 45 View->Defined Views... command. For other ways of opening existing CATIA Version 4 models, see "Opening Existing Documents" and "Opening Most Recently Used Documents" in the CATIA - Infrastructure User's Guide. V4 models residing on UNIX can be accessed from Windows using the http protocol. (Make sure beforehand that an http server has been installed on the machine where the models reside.) The address to be specified should look something like this: http://UNIXserver: port/V4modellocation Version 5 Release 14 V4 Integration Page 46 Selecting Geometric Elements on CATIA Version 4 Models This task shows you how to display a CATIA Version 4 model workspace and select its geometric elements in CATIA Version 5. Open the document XWINGS.model. 1. Above the geometry area where the Version 4 model is displayed, click the workspace tab you wish to display (the FUSELAGE workspace in the model shown below, for example), the tab selected then "rises" relative to the other tabs. Version 5 Release 14 V4 Integration Page 47 2. If you then wish to select a geometric element, expand the specification tree by clicking on the FUSELAGE item and then on one of the items with a plus sign, *SET5, for example. The specification tree will then look like this: A set is made up of subsets each containing lines, curves, surfaces, solids, dittos, etc. In the specification tree shown above these are easily identifiable (LN, CRV, SUR, etc.). A subset can be selected just like any other item for copy/paste, show/no-show operations, etc. However, you can of course select one or more of the lines, curves, solids, etc. contained in the subsets. 3. Click on the plus sign of the DIT subset and select the contents, *DIT13. Notice that the corresponding part of the model in the geometry area is highlighted as shown below: V4 Integration Version 5 Release 14 Page 48 You can of course select an element by clicking on it in the geometry area. Note that if you select a Ditto (DIT) in the Specification Tree, you select all the components within the Ditto. For instance, if you hide a Ditto by transferring it to the No Show space, all the objects under Ditto will no longer be displayed in the Geometry area. 4. Click on the central part of the fuselage (not on the blue component shown above). The corresponding solid is highlighted in the specification tree: V4 Integration Version 5 Release 14 Page 49 As you can see above, in the specification tree, double-clicking boxes with a plus sign shows the component elements of that particular workspace or set. Clicking the minus sign hides the elements contained in the workspace or set. V4 Integration Version 5 Release 14 Page 50 Selecting Federators and Sub-Federators in CATIA Version 4 Models This task explains how you can select either the Federator or the Sub-Federator within a V4 Model. In a V4 Model containing Federative and Sub-Federative elements like Skins and Faces, a new switch allows you to choose between two modes of selection. In the Sub-Federative Elements Mode, the user highlights and selects the Faces (*FAC) whereas in the Federative Element Mode, he selects the Skin (*SKI) as a whole. The Hide/Show is made according to the selection. Open a V4 Model containing a Federator and Sub-Federator such as Skin *SKI and Faces *FAC in CATIA V5, for instance: FedEltsMode.model. V4 Integration Version 5 Release 14 Page 51 The workshop of CATIA V4, V3, V2 (Start menu -> Infrastructure -> CATIA V4, V3, V2) contains two new icons corresponding to the two modes. The highlight and selection are made according to the icon which is pressed. In the Sub-Federative Element Mode, the sub-federative element is highlighted and selected. The icon Sub-Federator is grayed out and becomes unavailable: V4 Integration Version 5 Release 14 The default mode is: ● the Federative Elements Mode In CATIA V4, V3, V2 ● the Sub-Federative Elements Mode in a "DMU" context or in a "CGR" (see picture below). Federative Element Mode: Page 52 V4 Integration Version 5 Release 14 1. Press the Federative Elements Mode icon Page 53 (or press the corresponding item either in the contextual menu or in the View menu). In the Federative Element Mode, the Federative Element is highlighted and selected as a whole. The icon is grayed out and becomes unavailable. 2. Select the Skin in the Geometry of the Model. The whole Skin is highlighted and selected. Version 5 Release 14 V4 Integration Page 54 3. Right-click the contextual menu of the Skin and press the item Hide/Show. As the selection was global, the whole Skin is hidden: Version 5 Release 14 V4 Integration Page 55 Sub-Federative Element Mode: 1. Press the Sub-Federative Elements Mode icon (or press the corresponding item either in the contextual menu or in the View menu). 2. Select a Face in the geometry of the Model. Only the Face is highlighted and selected. V4 Integration Version 5 Release 14 Page 56 3. Right-click the contextual menu and press the item Hide/Show. Only the Face is hidden/shown: The Federative Element Mode does not allow to select Federative elements like volumes *VOL. Moreover, the switch is only available in the CATIA V4, V3, V2 workbench. V4 Integration Version 5 Release 14 Page 57 Improved Design in Context: Access to Solid Edges This task consists in applying constraints (an offset constraint on the Dittos' Edges in our example) between two models' Edges, in a CATProduct. Open the Ditto_Edges.CATProduct document. Version 5 Release 14 V4 Integration Page 58 1. Select the Edges to be constrained, for instance: an Edge in the cube in TST_DITTOS_SOLIDES.model and another Edge in the cube in TST_DITTOS_SOLIDES_2.model. 2. Click the Offset Constraint icon in the Constraints toolbar. This command is also available from the Insert menu. For more information about constraints, refer to Using Assembly Constraints, in CATIA - Assembly User's Guide. 3. Enter the properties of the constraint in the dialog box: 550 mm, for instance, in the Offset field. 4. Click OK to create the offset constraint. As the offset constraint is created, the cubes are moved so as to adopt its new position. A green arrow is displayed in the geometry area to indicate that this constraint has been defined. The offset value is displayed too. V4 Integration Version 5 Release 14 Page 59 Associativity is maintained between the V4 models and the CATProduct in which the models have been inserted and constraints have been set. Therefore, if you modify the models (for instance, change the cube's position, add a fillet,...) in CATIA V4, these modifications can be seen in the CATProduct and the constraints adapt themselves to the new parameters. In our example, a cube's position has been modified and the constraints have not changed: V4 Integration Version 5 Release 14 Page 60 Thus, you can link Solids by constraints on Edges, but you can also set constraints on Edges between a model and a CATPart. Note that this functionality is also available in the Drafting workbench. V4 Integration Version 5 Release 14 Page 61 Multi-Selecting V4 Components within the Specification Tree (for Hide/Show) In the previous task, the elements of a subset can be selected for copy/paste, Hide/Show operations, etc. And this task shows you how to select a V4 subset in CATIA Version 5 for Hide/Show. The Hide/Show functionality can be activated in the contextual menu of the subset. Open the document AllV4ElementTypes_NoShow.model and zoom in on this geometrical figure: 1. In the Specification Tree, select the elements *FAC3, *FAC4, *FAC5 and *FAC6 in the Subset FAC by keeping the Ctrl key pressed. 2. And select the Hide/Show contextual command. V4 Integration Version 5 Release 14 As a consequence, these Faces disappear and they are now visible only in the Hide area. Page 62 Version 5 Release 14 V4 Integration Page 63 3. If you want to display the Faces in the Geometry area, select them again in the Specification Tree and select the Hide/Show contextual command. For more information about the Hide/Show functionality, please refer to Hiding and Showing Objects in the CATIA - Infrastructure User's Guide. Open the document AllV4ElementTypes_NoShow.model and zoom in on the same geometrical figure. 1. If you select the Subset FAC in the Specification Tree, all the sub-elements will be selected as well: V4 Integration Version 5 Release 14 2. You can apply the Hide function on this group of elements: Page 64 V4 Integration Version 5 Release 14 And all the Faces under the subset FAC disappear from the Geometry area: Page 65 V4 Integration Version 5 Release 14 Page 66 3. If you want to display the Faces in the Geometry area, select the subset FAC again in the Specification Tree and select the Hide/Show contextual command. V4 Integration Version 5 Release 14 Page 67 Managing CATIA Version 4 Models, PROJECT Files and Library Objects in CATIA Version 5 To ensure CATIA Version 4->CATIA Version 5 interoperability, CATIA Version 5 provides the CATIA Site Navigator allowing you to read, in a CATIA Version 5 session, CATIA Version 4 models on both Windows and UNIX and both PROJECT files and library objects on UNIX. Any geometric element (whether the model involved has an internalized PROJECT file or is linked to an external PROJECT file) can be read and copied to a CATIA Version 5 document. In a CATIA Version 5 session, CATIA Version 4 models can be displayed on both Windows and UNIX and library objects can be displayed on UNIX. Basic read-only operations can then be performed, such as: ● displaying and selecting geometric elements and workspaces, in the geometry area and/or the specification tree (except for the HLR mode) ● displaying graphic properties (color, show/hide, layers, filters, pick/no pick) ● zooming, rotating and panning ● printing (except for the HLR mode) ● applying, creating, deleting, and modifying layer filters ● verifying the geometry (and, in the case of exact solids, the specifications) of one or more Version 4 elements prior to copy-pasting it into a CATIA Version 5 workbench. In CATIA Version 5, you cannot edit CATIA Version 4 models or library objects but you can paste all or part of a model or library object into a CATIA Version 5 document and then edit it. Once this has been done, it is of course no longer a Version 4 model, but a CATIA Version 5 document. Version 5 Release 14 V4 Integration Page 68 Having Access to V4 Model Comment From CATIA Version 5, you can have access to V4 Model Comment. For this, you need to follow these steps: ● Select File -> Open the Model of your choice ● Select one or more geometrical elements in the geometry area ● Select Edit -> Properties ● Choose the Comment Tab, and you can visualize the Comment of the V4 Model. For more information about V4 Model Transfer, refer to Transfer of a V4 Model Comment into a V5 CATProduct or a CATPart. V4 Integration Version 5 Release 14 Page 69 Alphanumerical Reorder of DETAILS In CATIA Model Editor, DETAILS are not alphanumerically ordered. This new functionality consists in restoring V4 behavior, that is to say the alphanumerical reorder of DETAIL tabs. By this means, you will be able to quickly find a given DETAIL in a large list. Here is an example when the Model Editor Details tabs were not alphanumerically ordered: The new behavior is illustrated by the following picture: Only DETAILS tabs are ordered, *MASTER and *DRAFT tabs always remain in the first positions. The reorder operation is automatically activated when opening a model. This reorder is used in two workbenches: ● CATIA V5 Model Editor ● DMU Navigator (only 2D workspaces are shown). V4 Integration Version 5 Release 14 Page 70 Using the Workspaces Navigator for Model Editor The objective of this new functionality is to make workspace selection in Model Editor easier and faster. By this means, you will be able to quickly find a given DETAIL in a large list. The command Change Workspace can only be used in Model Editor workbench. Open a model containing a Detail and several Dittos. 1. Holding the Shift key, select two Dittos (*DIT1 and *DIT8) under *MASTER. 2. In the CATIA V5 menu bar (Model Editor workbench), select the command View -> Change Workspace. It can also be reached from the workbench toolbar (vertical toolbar on the right). The following panel appears: V4 Integration Version 5 Release 14 Page 71 *DIT1 and *DIT8 are contained in the current and active workspace and they have been selected in *MASTER. The workspaces SOLID_1 and SOLID_4 are highlighted in the Workspace List because they are Details pointed by these Dittos: *DIT1 and *DIT8. If you do not select any component in the specification tree or if you select any component except Dittos, by default this is the active workspace that is highlighted in the Workspace Navigator panel. This panel is modal: as far as it is not closed, the user can only interact with it. All workspaces appear in alphabetical order except *MASTER and *DRAFT which are always in first positions. The Current Workspace is displayed in a small window under the selection frame. The Type column informs you that the workspace type is 2D or 3D. The Comment column allows you to see if a Detail has a Comment. Here is another example with a Comment associated to a Detail: V4 Integration Version 5 Release 14 Page 72 Filter Behavior This Filter provides workspace pre-selection. The "star" meta-character is available in this filter, for instance: *UB*. Version 5 Release 14 V4 Integration Page 73 By clicking a workspace name (in the list) and the OK button, the user makes the selection panel disappear and the workspace is displayed in CATIA. By clicking a workspace and the Activate button or by double-clicking a workspace name, it is displayed in CATIA. The Close button allows to quit the command. The Help command allows you to get help on the Filter functionality. Click the Help button, the cursor takes on the shape of the What's This? icon and select the Filter button to obtain more information about it: V4 Integration Version 5 Release 14 Page 74 Extract Version 4 Models from Sequential File in Batch Mode This task shows you how to extract CATIA Version 4 Models from CATIA Version 4 sequential files (.dlv3 or .exp). This extract tool provides an interactive interface on a different application from CATIA Version 5 or a Batch command. Select Sequential.exp from the samples directory and save it in your own directory. The sample documents are installed in user guide-specific sample folders. In the online documentation filetree, there is one samples folder for each users guide, in the following location: C:\Program Files\Dassault Systemes\B07doc\online\xxxug\samples where "xxx" represents the three-letter code for the product. For example, the folder: C:\Program Files\Dassault Systemes\B06doc\online\intug\samples contains the sample documents for the V4Integration User's Guide. Before launching the batch tool, you have to make sure that your environment is correctly set up. On Windows, the Batch's environment is installed during CATIA's installation. On UNIX, you have to set up this environment before starting the session. For more information about this, see CATIA Infrastructure User's Guide - Starting a session on UNIX. How to launch the Extract V4 Models from Sequential File Batch You can use different methods to launch the Batch: ● via the DataLifeCycle platform, ● via the Batch Monitor (CATUTIL), ● in a pure Batch mode, ● in interactive mode, in a CATIA session. Launching the batch through the DataLifeCycle platform: You launch the batch by using the DataLifeCycle platform. For more information about DataLifeCycle, please refer to CATIA - Infrastructure User's Guide - Running Batches Using the Batch Monitor. Launching the batch through the Batch Monitor: You launch the batch by using the Batch Monitor. For more information about CATUTIL, please refer to CATIA Infrastructure user's Guide, Running the Data Life Cycle Batch. Launching the Extract tool in a pure Batch mode You can then launch the Extract tool in a pure Batch mode by entering the command: ● CATExtractModelFromSequential -arg For instance: CATExtractModelFromSequential [-h / -id inputDirectory [-if inputfile/-il inputlist] -od outputDirectory -report reportFile] Version 5 Release 14 V4 Integration Arg Page 75 Description Online help of the command. Writes in the standard output the list of valid arguments. CATExtractModelFromSequential [-h / -id inputDirectory -if inputfile / -il inputlist -od outputDirectory -report reportFile -h : help -id : Intput Sequential Directory (or DLNAME) -if : Input text File containing a list of Sequential Files to process with appropriate file extension (ie .dlv3 or .exp). -il : Input list of sequential Files to process with appropriate file extension (ie .dlv3 or .exp). -od : Output Model Directory (or DLNAME) -report : Report File name -h If -h parameter is defined, others parameters are ignored. -id Input Sequential Directory Define the pathname or the DLNAME containing the sequential files to process. This parameter is not mandatory. It is useful if all sequential files are extracted from the same directory. It is used only as concatenation to document to process. Selection criteria Input text File containing a list of sequential files to process with appropriate file extension (ie .dlv3 or .exp). If a sequential file defined in the text file is a concatenation of path (or DLNAME) and name, the input directory is ignored. -if At least one of the (-il/-if) parameters is mandatory, (-il/-if) parameters can be defined several times. The batch aborts if no selection criteria is defined. Selection criteria Input list of sequential files to process with appropriate file extension (ie .dlv3 or .exp). If a sequential file is a concatenation of path (or DLNAME) and name, the input directory is ignored. -il At least one of the (-il/-if) parameters is mandatory, (-il/-if) parameters can be defined several times. The batch aborts if no selection criteria is defined. -od Output Model Directory Define the pathname or the DLNAME where the extracted .models are written. This parameter is mandatory. The batch aborts if no output Model Directory is defined. Report File name Give the possibility to Save the "Extract report" in the file and directory of your choice : In this report, you can find information about the generated models that belonged to the Sequential Files (.dlv3 or .exp): ● Sequential File path ● Name of the model(s) ● Creation Date of the model(s) ● Last Modification Date -report ● A Return Code (success scale): ReturnCode = 0 : The batch ended successfully ReturnCode = 4 : at least one sequential file could not be processed ReturnCode = 8 : The batch aborted. The Report File can be a concatenation of path (or DLNAME) and name. It is automatically '.txt' suffixed. This parameter is optional. If no Report File is defined, the report is written in the standard output. V4 Integration Version 5 Release 14 Page 76 Using the Extract batch in interactive mode, in a CATIA session: You can also launch the Extract tool in an interactive interface by entering the command: ● On Windows: CNEXT -batch -e ExtractModelFromSequential ● On UNIX: catstart -run "CNEXT -batch -e ExtractModelFromSequential". 1. Select Sequential Documents (for instance Sequential.exp) in the File Box by clicking the Browse File button: You can enter the file name (70 characters maximum) or select directly the file by clicking in the FileBox list. Before using the ExtractModelFromSequential batch, if you had renamed a .exp file with any other extension, .titi for instance, and then you want to select it in the batch, you will see .titi in the File Selection window (using the "All Files" option) But this document .titi will not appear in the (Sequentials To Process) list of the ExtractModelFromSequential batch. Only .exp files can be migrated by the Extract batch. V4 Integration Version 5 Release 14 Page 77 You can remove a file from your list: Select a file (the Remove button becomes active) and click the Remove button. 2. Press this button to specify the directory name in which the data will be created (by default the data are created in the same place where the first selected V4 document is stored). Click Open. V4 Integration Version 5 Release 14 Page 78 3. Press the Extract button in order to extract CATIA V4 Models from sequential file. Extract report will be displayed in another dialog box at the end of the operation: As a consequence, you will have access, in CATIA V5, to the V4 CATIA Models that belonged to the Sequential Files (in V4). 4. You have the possibility to Save the Report. In the Extract report window, if you click on the Save As Text button, the Save As dialog box appears and the report can be saved in the file and directory of your choice: V4 Integration Version 5 Release 14 Page 79 In this report, you can find information about the generated models that belonged to the Sequential Files (.dlv3 or .exp): ● Sequential File path ● Name of the model(s) ● Creation Date of the model(s) ● Last Modification Date ● A Return Code (success scale): 0=The transfer was successful -> 4=half of the transfer took place -> 8=nothing was written. 5. Exit the Report panel by clicking the cross in the top right corner or the OK button. A few rules about Batch Conversion: A sequential file is known by the extension .dlv3 or .exp. The extract process takes into account all the sequential files structures. According to its content, a sequential file is exploded into several CATIA V4 models. Other data structures than .model (for instance, library, project tables,...) are ignored. If the output directory already contains a .model with the same name as one of the models contained in the sequential file, the corresponding .model is not written and the process goes on. The batch aborts if at least one model cannot be written. If one of the models contains a character which is not compatible with the Windows file system (i.e "*,",.."), it will be automatically renamed in a compatible name using the 'Windows compatible table'. Version 5 Release 14 V4 Integration Page 80 Renaming Version 4 Documents regarding Windows File System Compatibility in Batch Mode This task shows you how to rename a Version 4 document which is not compatible with Windows file system (i.e the name of the document contains forbidden characters) into a document which can be read on Windows. Then on Windows, renamed documents will be used while opening session, and decode of multi-model links with "on the fly conversion" will be available. Batch tool will rename those V4 documents and their dependencies, according to definition of the characters mapping (See conversion table). Consequences of Migration on Filenames On Windows, it is extremely important to be aware of the consequences of migration on filenames. Before reading any further see "About Filenames" in the CATIA - Infrastructure User's Guide. Select a Session document containing characters. Before launching the batch tool, you have to make sure that your environment is correctly set up. On Windows, the Batch's environment is installed during CATIA's installation. On UNIX, you have to set up this environment before starting the session. For more information about this, see CATIA Infrastructure User's Guide - Starting a session on UNIX. Note that due to Windows forbidden characters, it is strongly recommended to launch the batch on UNIX only (batch will abort on Windows if the document contains invalid Windows characters). You can then launch the Extract tool in a pure Batch mode by entering the command: ● CATV4ToV5NTCompatibilityName -arg CATV4ToV5NTCompatibilityName [-h / -id inputDirectory [-if inputfile/-il inputlist] -od outputDirectory -report reportFile -depth level] Arg Description Online help of the command. Writes in the standard output the list of valid arguments. -h CATV4ToV5NTCompatibilityName [-h / -id inputDirectory -if inputfile -il inputlist -od outputDirectory -report reportFile -depth level -h : help -id : Intput document Directory (or DLNAME) -if : Input text File containing a list of V4 documents to process with appropriate file extension (ie .session, .model, .exp, .dlv3). -il : Input list of V4 documentss to process with appropriate file extension (ie .session, .model, .exp, .dlv3). -od : Output Directory (or DLNAME) -depth : level of Multi Model Link structure taken in account -report : Report File name If -h parameter is defined, others parameters are ignored. -id Input V4 document Directory Define the pathname or the DLNAME containing the V4 documents to process. This parameter is not mandatory. It is useful if all V4 documents are extracted from the same directory. It is used only as concatenation to document to process. Selection criteria Input text File containing a list of V4 documents to process with appropriate file extension (ie .dlv3 or .exp). If a V4 document defined in the text file is a concatenation of path (or DLNAME) and name, the input directory is ignored. -if At least one of the (-il/-if) parameters is mandatory, (-il/-if) parameters can be defined several times. The batch aborts if no selection criteria is defined. Version 5 Release 14 V4 Integration Page 81 Selection criteria Input list of V4 documents to process with appropriate file extension (ie .dlv3 or .exp). If a V4 document is a concatenation of path (or DLNAME) and name, the input directory is ignored. -il At least one of the (-il/-if) parameters is mandatory, (-il/-if) parameters can be defined several times. The batch aborts if no selection criteria is defined. -od -depth Output Model Directory Define the pathname or the DLNAME where the extracted .models are written. This parameter is mandatory. The batch aborts if no output Model Directory is defined. Dependency Level This parameter is optional. By default, Maximum depth is taken. Report File name Give the possibility to Save the "Rename report" in the file and directory of your choice : In this report, you can find information about the renamed documents : ● V4 document path ● ● -report Name of the model(s) A Return Code (success scale): ReturnCode = 0 : The batch ended successfully ReturnCode = 4 : at least one V4 document could not be processed ReturnCode = 8 : The batch aborted. The Report File can be a concatenation of path (or DLNAME) and name. It is automatically '.txt' suffixed. This parameter is optional. If no Report File is defined, or if access to the Report File is denied, the report is written in the standard output. A few rules about Batch Conversion: A V4 document is known by the extension .session, .model, .dlv3 or .exp. A selected V4 document will be written in the output directory even if not renamed. V4 Integration Version 5 Release 14 Page 82 Capability to identify a Model from CATIA V5 This task shows you that it is possible to know that a model has been created in CATIA V5. When V4 models are created in V5 by the Save As Model functionality, they have a version flag (like every model built in V4). Permanent identification of a .model coming from V5 Previously, any V4 utility overwrote this flag with its V4 level. When models were used in a V4 batch, the CATIA version of this batch replaced the version flag of the model. So it was impossible to know that a model was coming from CATIA V5. Now in CATIA V5, we will add a new information on the model, to keep the building version: the flag is kept even if a 4 utility is used. Therefore, information will be added to models during the Save As Model operation in CATIA V5. To access to this information, a V4 code integration has to be done. So a V4 PTF should be installed to support this capability. You can convert any CATPart document into a V4 model. Interactive "save as model" or CATV5ToV4 batch can be used. New information will be added to the created model. To get this additional information on the created version, a V4 CATGEO will be used. Add-value: ● helps the customer to track the data coming from V5 ● allows the customization of the model checks if a .model has been done in V4 or in V5. V4 Integration Version 5 Release 14 Page 83 Copying 3D from CATIA Version 4 to CATIA Version 5 This task shows you how to copy the specifications or geometry of a CATIA Version 4 model to CATIA Version 5. The following data can be copied from CATIA Version 4 to CATIA Version 5: ● surfaces (both polynomial and BSpline) ● clouds of points ● faces ● edges ● volumes ● parabolas ● skins and exact solids ● hyperbolas ● curves (both polynomial and BSpline) ● CCVs ● NURBs (curves and surfaces) ● PIP elements (Tubing) ● GPR elements (AEC Primitive) ● STR elements (planar structures, linear structures) ● mockup solids (see remarks regarding copy/pasting mockup solids below) ● polyhedral surfaces and solids ● circles ● ellipses ● points ● lines ● planes The following task describes how an entire model is pasted from Version 4 to Version 5. You can also select the geometric elements listed above and insert them into an already existing Version 5 document. Open the document LAMP.model. You should have already completed the task Checking CATIA Version 4 Model Data Before Copying It to CATIA Version 5. You may want to customize certain settings before proceeding with this task. For more information, see Customizing Compatibility Settings. 1. Open a new CATIA Version 5 CATPart document. To do this, refer if necessary to "Creating New Documents" in the CATIA Infrastructure User's Guide. 2. In the specification tree or geometry area where the Version 4 model is displayed, select the geometrical element or elements you wish to convert. 3. If you intend to copy the geometry you can either: ● drag and drop the element(s) onto the appropriate location in the CATIA Version 5 document. The cursor changes slightly i.e. the symbol appears indicating where a drop is allowed. If the cursor changes to the symbol the drop is not allowed in that location. ● , or: a. Put the element(s) you have selected in the clipboard by clicking the Copy icon , select the Edit->Copy command or select the Copy command in the contextual menu. b. In the specification tree of the CATIA Version 5 document, select the appropriate item (for example, PartBody or Body.1, Body.2, etc. in the PartDesign workbench). or select the Edit->Paste command or select the Paste command in the c. Click the Paste icon contextual menu. This operation recovers the specifications previously put in the clipboard. Page 84 Version 5 Release 14 V4 Integration 4. If you intend to copy the specifications: ❍ Put the element(s) you have selected in the clipboard by clicking the Copy icon , selecting the Edit->Copy command or selecting the Copy command in the contextual menu. ❍ In the specification tree of the CATIA Version 5 document, select the appropriate item (for example, PartBody or Body.1, Body.2, etc. in the PartDesign workbench). ❍ Select the Edit->Paste Special... command or select the Paste Special... command in the contextual menu. The dialog box below appears: ● Select CATIA_SPEC and click OK. This operation recovers the specifications previously put in the clipboard. 5. Click the Update icon to view the copied data. 6. You may want to click the Fit All In icon to fit all data in the window. Notice that the toolbars change depending on whether a CATIA Version 4 model or a CATIA Version 5 document is selected. If you copied the geometry the result should look something like this (using the Window->Tile Horizontally command): V4 Integration Version 5 Release 14 If you copied the specifications the result should look something like this (using the Window->Tile Horizontally command): Page 85 V4 Integration Version 5 Release 14 Page 86 Bear in mind the following when copy/pasting: ● The migration of V4 model data to a V5 document generates a report (.rpt) file named after the model migrated: ❍ on Windows: in C:\Documents and Settings\username\Local Settings\Application Data\DassaultSystemes\CATReport ❍ ● ● on UNIX: in /u/users/username/CATReport If you used the CATIA_SPEC option mentioned above note that only the paste operation is included in the report i.e. the actual update of the CATPart document is not taken into account. If you want to manipulate the data in this CATProduct, you will not be able to Copy/Paste features belonging to different V4 Models (within the CATProduct) in the same transaction, at the same time, otherwise a Warning appears. For instance: V4 Integration ● ● ● Version 5 Release 14 Page 87 When copy/pasting mockup solids : If the solid has a history then the V5 specifications are created. However, if the solid has no history or if the CATIA_RESULT option is selected (using the Paste Special... command) then a cgr file is generated containing the visualization information of the solid. The name of this file is "mymodel_SOLMxxx" and is located in the same directory as the V4 CATIA model. This file can be visualized separately or inserted into the Product Structure application. When copy/pasting sets of surfaces : If you want to get a unique surface in V5, it is more efficient to perform the join in V4 before the transcript than in V5 on the resulting surfaces. When copying/pasting the *MASTER of a Model in a CATPart, the Model's comment is taken into account. The Model's comment will be added to the properties of the destination CATPart as it is already done in the V4 to V5 Migration batch. V4 Integration Version 5 Release 14 Page 88 Partial Paste: Diagnosis Feature This task shows you how to visualize the V4->V5 migration errors when using the option CATIA_RESULT and to understand why the copy/paste operation failed. And, in some cases, you can work on the design of the V4 models. 1. Copy / Paste As Result a .model document into a CATPart. If there is an error during this transfer, you can visualize it in the Specification tree: there is an error feature (External References) containing the error text and the associated Geometry. Here is an example with the Surface migration. The error message is: "Invalid BRep Geometry of *SUR55 wsp *MASTER - (Too closed control points are detected)". Control Points can be visualized and the feature displays the error message that you could find in the Warning dialog box (after the migration). V4 Integration Version 5 Release 14 Page 89 2. Another example with the migration of Faces with Z-Edges. The error message is: "Invalid BRep Geometry of *FAC23 -wsp *MASTER - (A Z shaped edge is detected. This configuration is not supported.)". The feature delivers the error message and the points allow the user to precisely localize the geometry problem. If the automatic repair cannot take place, a diagnosis feature appears in the Specification tree and three cases can be detected: ● the Surface support of the Edge is self-intersected ● confusion zone of the Z-Edge is superior to intersection curve tolerance ● confusion cannot be detected by C1 discontinuity V4 Integration Version 5 Release 14 Page 90 Main PartBody is no longer used in conversion AS SPEC This task shows you that the copy/paste As Result or As Spec of Solids requires to create several Bodies, and the main PartBody in CATIA V5 is no longer used. When copy/pasting a model containing several Solids into a void CATPart, the first Solid to be migrated generates V5 PartDesign specifications in the main PartBody. This can be a problem in several cases: ● ● ● Using the main PartBody introduces a specific role to one migrated Solid, even when this specificity does not exist in the V4 model. If the first migrated Solid is a DETAIL used in a Macro-Primitive, it is not possible to perform Boolean operations of the main Body under other Bodies. V4 CSG first primitive may be inactive. However in a main PartBody, the first specification can not be inactive or deleted whereas this restriction does not exist on next Bodies. If only one Body has to be generated, we still use the main Partbody. If there are several of them, the Partbody is not used. First example: when a DETAIL is used by a DITTO. 1. Open DITTOS-BOULON.model. In this sample, there is a DETAIL (*SOL 62 in the BOULON tab) used by a DITTO (*DIT25 for example): V4 Integration Version 5 Release 14 2. Copy / Paste AS SPEC *DIT25 into a CATPart. 3. Update the CATPart: Page 91 V4 Integration Version 5 Release 14 Page 92 In Geometrical Set.1, there is the geometry of DIT25 which has been copied only once. The DETAIL is the first migrated element; you can visualize it in the Specification Tree, it is called Body.2(*SOL62-wsp BOULON-). The DITTO appears further down in the Specification Tree; it is called CARWL of Body.2 (*SOL62-wsp BOULON-). The DETAIL BOULON (*SOL62-wsp BOULON-) remains its reference. In the Specification Tree, the Body of the DETAIL appears before the DITTO because it is a reference for the DITTO. The DETAIL is not the main object of the CATPart which explains why the PartBody is empty. Second example: when a DETAIL is used by a Solid or a Macro-Primitive. 1. Open ASSEMBLE_SUBSTRACT_WITH_MACRO_PRIM.model. V4 Integration Version 5 Release 14 Page 93 In this sample, there is a DETAIL (*SOL3 in the GUIDA SUP tab) used by a Solid (*SOL370). This DETAIL plays the role of a Macro-Primitive. 2. Copy / Paste AS SPEC *SOL370 into a CATPart. The DETAIL is the first migrated element (Body.2 (*SOL3 -wsp GUIDA SUP- Non Smart-) because it is then used by the Solid. The DETAIL is not meant to be the main Body of the CATPart which explains why the PartBody is empty. In the Specification Tree, the copy of the Solid is represented by: CARWL of Body.2(Body.2 (*SOL3 -wsp GUIDA SUPNon Smart-) (*SOL370 -wsp *MASTER-) further down in the Tree. CARWL of Body.2 keeps a link with the Body of the DETAIL that has been migrated. In the Specification Tree, the copy of the DETAIL always appears before the copy of the DITTOS or the Solids. The DETAIL is the first migrated entity into CATIA V5. V4 Integration Version 5 Release 14 Page 94 Conversion of SolidM entities as Result (migrated as a PartBody) This task shows how a V4 Mock-Up Solid can be converted (As Result) into a V5 Exact Solid, into a PartBody and therefore, it can be modified by V5 Operators. To obtain this result, there are two means: ● ● an environment variable is provided to activate the conversion: set/export CATMigrSolidMUV4AsPart=1 you can activate the "as PartBody" option, by selecting the Tools -> Options... command, by clicking Compatibility in the list of objects to the left of the Options dialog box and by choosing the V4/V5 SPACE tab. Open SOLIDEV4_PRIMITIVEV3isole.model. V4 Integration Version 5 Release 14 Page 95 What is the behavior by default, without activating this variable: 1. Copy/Paste (As Result) SOLIDEV4_PRIMITIVEV3isole.model into a CATPart and a Warning is displayed: This Warning informs you that a cgr document has been created after the copy/paste operation; it is stored in the same directory as the .model. 2. Click Close. The CATPart is empty. V4 Integration Version 5 Release 14 Page 96 3. If you open the cgr file, you only have access to Visualization (Mesh) and you cannot modify any data. V4 Integration Version 5 Release 14 Page 97 What is the behavior when you activate the migration of the Solid MockUp into a V5 PartBody? Launching the "As PartBody" migration mode: 1. On Windows, enter the following command: set CATMigrSolidMUV4AsPart=1 On UNIX, enter the following command: export CATMigrSolidMUV4AsPart=1 2. Or activate the setting "as PartBody" in the option entitled "Isolated Solids Mock-Up Migration Feature Result" in Tools -> Options -> General -> Compatibility -> V4/V5 Space (by default, the "as CGR" option is checked): If you do not the use the variable nor the setting, the SolidM will be migrated as CGR. V4 Integration Version 5 Release 14 Page 98 For more information about CATIA V4/V5 Settings, please refer to Customizing V4/V5 Space in CATIA Infrastructure User Guide. 3. Copy/Paste SOLIDEV4_PRIMITIVEV3isole.model into a CATPart and a Warning is displayed. If you select the "as PartBody" option or use the variable, you will also have the following message after the copy/paste of the SolidM into a CATPart: In this message, you know that the variable is activated, that *SOL4 is migrated As Result and no cgr is created. And you obtain a PartBody in the CATPart: V4 Integration 4. Update your document: Version 5 Release 14 Page 99 V4 Integration Version 5 Release 14 Page 100 Limitations: We advise customers against converting huge V4 Mock-up Solid, which can lead to: ● High CPU time consuming ● Important CATPart size Improvements: ● ● ● Improvements in Naming Management (Face selection): if one Face is selected, all the other ones belonging to the same Volume will be selected as well. Improvements in the migration As Spec: isolated solidM are migrated are migrated As Result. As a consequence, no .cgr file is created. Color Management: previously, a global color was transferred onto the migrated solid. Now, the Faces' color is the color of the V4 sub-volume they belong to. V4 Integration Version 5 Release 14 Page 101 V4 Integration Version 5 Release 14 Migration of a DETAIL with only Geometry Page 102 If you want to copy/paste AS SPEC or AS RESULT a DETAIL containing only Geometry (with no Solid) into CATIA V5, a warning panel appears explaining that the data structure is not adapted for a complete migration. And this task shows you that the whole Geometry of the DETAIL is copied only once in the NO SHOW space and there is no instance of the DITTO in the CATPart. Open DITTOS-BOULON_FAC.model and select the DETAIL tab: BOULON. This DETAIL contains only Geometry (Lines, Curves, Surfaces and Faces), with no Solids. 1. In the *MASTER tab, copy the DITTO *DIT25. 2. Paste it in a CATPart. A Warning panel appears: V4 Integration Version 5 Release 14 Page 103 In this message, you can find: ● the following advice: "Use rather the batch CATV4ToV5Migration. The CATIA V4 detail BOULON contains only geometry. It is migrated once, without the ditto(s) *DIT25 because the migration into a CATPart is inappropriate to it." ● the results are: "The CATIA V4 detail BOULON has been partially pasted. The CATIA V4 ditto *DIT25 -wsp *MASTER- has been partially pasted because of detail BOULON." The V4 DETAIL and DITTO have been partially pasted because the model's data structure is inappropriate: there is only geometry in the DETAIL. The best way to migrate all the V4 elements (with fewer restrictions) is to use the V4 to V5 Migration Batch. For more information about the V4 to V5 Migration Batch, please refer to Converting CATIA Version 4 Models into CATIA Version 5 in Batch Mode. 3. Click Close. The copy of the DITTO cannot be visualized in the Geometry space; there is no instance of the DITTO. The Geometry of the DETAIL is in Open_body.1 and it has been copied in the NO SHOW space. There is only one instance of the DETAIL: V4 Integration Version 5 Release 14 Page 104 4. If you use the V4 to V5 Migration Batch, the assemblies are correctly transferred and no data is lost. The V4 structure is perfectly translated into CATIA V5. You obtain a Part for the DETAIL and a Product using the references of the DETAIL's Part. Here is the migration of DETAIL BOULON: and the migration of *MASTER: V4 Integration Version 5 Release 14 Page 105 V4 Integration Version 5 Release 14 Migration of a DETAIL with only Dittos Page 106 If you want to copy/paste AS SPEC or AS RESULT a DETAIL containing only Dittos into CATIA V5, a warning panel appears explaining that the data structure is not adapted for a complete migration. And this task shows you that the DETAIL is copied only once in the NO SHOW space and there is no instance of the DITTO in the CATPart. Open DITTOS_WITHIN_DITTOS_SPACE.model and select the DETAIL tab: SPHERE. This DETAIL contains only one Solid. If you look at the other tabs, you can visualize some DETAILS containing other DETAILS. Within each DETAIL, the DITTOS are duplicated and they have a link with another DETAIL. In this model, you have several embedded DETAILS. The DITTOS of DETAIL2 use the DETAIL called SPHERE: The DITTOS of DETAIL4 use DETAIL2: V4 Integration The DITTOS of DETAIL8 use DETAIL4: Version 5 Release 14 1. In the *MASTER tab, copy the DITTO *DIT7. 2. Paste it AS SPEC or AS RESULT in a CATPart. A Warning panel appears: Page 107 V4 Integration Version 5 Release 14 Page 108 In this message, you can learn that the V4 DITTO and associated DETAIL have been partially pasted because the model's data structure is inappropriate: the embedded structure is not adapted to this copy/pasting migration. These restrictions are also reflected on the other DETAILS since they all use the reference of another DETAIL. Therefore, the advice is to use the V4 to V5 Migration Batch. For more information about the V4 to V5 Migration Batch, please refer to Converting CATIA Version 4 Models into CATIA Version 5 in Batch Mode. 3. Click Close in the Warning panel. And in the CATPart, you obtain: V4 Integration Version 5 Release 14 Page 109 The V4 structure of Detail - Dittos is maintained into the same Part thanks to the V5 CopyAsResultWithLink functionality (it is named in the Part tree as CARWL). 4. Before launching CATIA V5, if you use the environment variable, set ForceDetailToAssemble=1, to force the assembly operation, and you try to copy/paste DITTO *DIT7 into a CATPart, the following panel is displayed: And you will obtain this: V4 Integration Version 5 Release 14 Page 110 The copy of *DIT7 can be visualized in the geometry space (in SHOW space), in Solid.19. The embedded structure is reflected in: CARWL of CARWL of Body.2 (*SOL -wsp SPHERE-). The other DETAILS have been copied in the NO SHOW space: ● The Geometry of SPHERE is in Body.2 (*SOL1 -wsp SPHERE). ● The Geometry of DETAIL2 is in CARWL of Body.2 (*SOL1 -wsp SPHERE) ● The Geometry of DETAIL4 is in CARWL of CARWL of Body.2 (*SOL1 -wsp SPHERE) ● The Geometry of DETAIL8 is in CARWL of CARWL of Body.2 (*SOL1 -wsp SPHERE) (*SOL1 -wsp SPHERE) shows that all these DETAILS keep a link with SPHERE which was the DETAIL used in DETAIL2. 5. If you use the V4 to V5 Migration Batch, the assemblies are correctly transferred and no data is lost. The V4 structure is perfectly translated into CATIA V5. You obtain a Part for each DETAIL and a Part for *MASTER. Here are the Batch results for the DETAILS and the *MASTER: DETAIL SPHERE: DETAIL 2: DETAIL 4: DETAIL 8: V4 Integration *MASTER: Version 5 Release 14 Page 111 V4 Integration Version 5 Release 14 Migration of a DETAIL with several Bodies Page 112 If you want to copy/paste AS SPEC or AS RESULT a DETAIL containing several Bodies into CATIA V5, a warning panel appears explaining that the data structure is not adapted for a complete migration. Open DITTOS_WITHIN_DITTOS_SPACE.model and select the DETAIL tab: SPHERE. This DETAIL contains several Bodies. If you look at the other tabs, you can visualize some DETAILS containing other DETAILS. Within each DETAIL, the DITTOS are duplicated and they have a link with another DETAIL. In this model, you have several embedded DETAILS. 1. In the *MASTER tab, copy the DITTO *DIT7 and paste it AS SPEC or AS RESULT in a CATPart. A Warning panel appears and the advice is to use the V4 To V5 Migration Batch: For more information about the V4 to V5 Migration Batch, please refer to Converting CATIA Version 4 Models into CATIA Version 5 in Batch Mode. V4 Integration Version 5 Release 14 Page 113 2. Click Close in the Warning panel. And in the CATPart, you obtain: The V4 structure of Detail - Dittos is maintained into the same Part thanks to the V5 CopyAsResultWithLink functionality (it is named in the Part tree as CARWL). 3. Before launching CATIA V5, if you use the environment variable, set ForceDetailToAssemble=1, to force the assembly operation, and you try to copy/paste DITTO *DIT7 into a CATPart, the following panel is displayed: And you will obtain this: V4 Integration Version 5 Release 14 Page 114 It is not recommended to use this variable to migrate your V4 data because you do not get the exact V4 structure. However, the advice is to use the V4 to V5 Migration Batch. 4. If you use the V4 to V5 Migration Batch, the assemblies are correctly transferred and no data is lost. The V4 structure is perfectly translated into CATIA V5. You obtain a Part for each DETAIL and a Product for *MASTER. Here are the Batch results for the DETAILS and the *MASTER: DETAIL SPHERE: DETAIL 2: V4 Integration DETAIL 4: DETAIL 8: Version 5 Release 14 Page 115 V4 Integration *MASTER: Version 5 Release 14 Page 116 Version 5 Release 14 V4 Integration Page 117 Comparison of Result Option in Batch: V4/V5 BREP Info Checker The following section describes the usage of the V4/V5 BREP Info Checker. During the copy/paste of a SOLIDE, a migration report is delivered containing the geometry values: the Volume, Wet Surfaces and Gravity Center properties of the V4 model and the V5 CATPart. The V5 unit is chosen. 1. The calculation of BRep properties can be done only if the V5 part is updated. These properties cannot be exposed if the V5 update operation fails. 2. The accuracy of calculation depends on V4 Modeler for V4 models and on V5 Modeler for V5 parts. 3. During the copy/paste the cpu consumption increases proportionally to the size of the model because of the calculation of properties and the update of the V5 part. This functionality is activated by the setting: On UNIX: export REPORT_BREP_INFO= 1 On Windows: set REPORT_BREP_INFO= 1 The report looks like this (new lines are red colored): V4 Integration Version 5 Release 14 Page 118 In the field "Input values", you have access to the values calculated on the V4 Model. In the field "Output values", you have access to the values calculated on the V5 CATPart after the migration and the update operation. V4 Integration Version 5 Release 14 Page 119 Migrating from V4 To V5 in Batch Mode How to launch the Migration Batch Converting CATIA Version 4 Models into CATIA Version 5 with the V4 To V5 Migration Batch Converting CATIA Version 4 Models into CATIA Version 5 with the DataLifeCycle Batch Automatic Transfer of a Version 4 Model Comment into a Version 5 CATProduct or CATPart Automatic Transfer of a Version 4 Detail Comment into a Version 5 CATProduct or CATPart Converting a V4 Session to CATIA V5 with the V4 To V5 Migration Batch V4/V5 Associative Migration of Solid MML Structures and Mapping V4 Integration Version 5 Release 14 Page 120 How to launch the V4 To V5 Migration Batch This task shows you how to launch the V4 To V5 Migration Batch. You can use different methods to launch the Batch: ● in interactive mode, ● from the Command Line (no batch interface), ● via the Batch Monitor, ● via the DataLifeCycle Batch. For more information about the Migration Batch settings, please refer to Migration Batch, in CATIA - Infrastructure User's Guide. Using V4 To V5 Migration in interactive mode, in a CATIA session Before launching the migration tool, you have to make sure that your environment is correctly set up. On Windows, the Batch's environment is installed during CATIA's installation. On UNIX, you have to set up this environment before starting the session. For more information about this, see CATIA Infrastructure User's Guide: Starting a session on UNIX. Launch the CATV4ToV5Migration Batch by entering the following command: On Windows: CNEXT -batch -e CATV4ToV5Migration On UNIX: catstart -run "CNEXT -batch -e CATV4ToV5Migration" The Migration batch dialog box appears: V4 Integration Version 5 Release 14 Page 121 Running the V4/V5 File-based Migration Batch from the Command Line, with no batch interface This task shows you how to convert CATIA Version 4 documents into CATIA Version 5 from a command line (not with the interactive batch). By this means you can migrate one or several V4 documents in a unique action, with the opportunity to make a shell to automate a great number of treatments without any human action. Before launching the batch tool, you have to make sure that your environment is correctly set up. On Windows, the Batch's environment is installed during CATIA's installation. On UNIX, you have to set up this environment before starting the session. For more information about this, see CATIA - Infrastructure User's Guide - Starting a session on UNIX. Only V4 documents already managed by the interactive batch can be migrated with this command. It means V4 .model, .session and .asm. V4 Integration Version 5 Release 14 Page 122 On Windows and UNIX, you can launch the migration by entering the command: ● CATV4ToV5 [ -h / -if input file / -il input list [ -od output directory ] [-report] ] -h: help (if -h parameter is defined, other parameters are ignored) -if: specify a file containing a list of V4 documents (full path). If no -il parameter. Warning: Before launching the Migration Batch, you need to specify in this file the whole path of these models. -il: following by a list of V4 documents (full path). If no -if parameter. Warning: Before launching the Migration Batch, you need to specify in this file the whole path of these models. (One of these last two parameters is mandatory.) -od: specify the directory, all V5 resulting documents will be created in. If not defined, V5 documents will be created in V4 document's directory. -report: no default value. If no report file is specified, the report is displayed in the standard process output. Else the report will be stored in the specified file, which can be either an absolute file path, or a relative name. Relative names will be interpreted from the directory where CATV5ToV4 command was launched. Examples: CATV4ToV5 -il inputFile -report reportFile: Before launching the Migration Batch, you need to specify in this file the whole path of these models. This batch command performs the migration of inputFile. Resulting V5 documents will be created in inputFile directory. Report's information are stored in reportFile. CATV4ToV5 -il inputFile1 inputFile2: Before launching the Migration Batch, you need to specify in this file the whole path of these models. This batch command performs the migration of both inputFile1 and inputFile2 V4 documents. V5 documents resulting of inputFile1's migration will be placed in inputFile1 directory, and V5 results of inputFile2's migration will be created in inputFile2 directory. Report appears in the standard process output. CATV4ToV5 -if inputFile -od outputDirectory: Before launching the Migration Batch, you need to specify in this file the whole path of these models. This batch command performs the migration of all V4 Documents listed in inputFile. All resulting V5 documents are created in outputDirectory. Report appears in the standard process output. As a consequence you can open the V5 generated document(s) in CATIA V5. Settings: V5 Settings are taken into account, more particularly Migration Batch settings like "Conversion mode", "Format", "Characters Equivalence Table Path". V4 Integration Version 5 Release 14 Page 123 A few rules about Batch Conversion: The conversion rules are the same as that of the interactive Migration Batch. For more information about these rules, please refer to Converting CATIA Version 4 Models into CATIA Version 5 in Batch Mode. Using V4 To V5 Migration Batch via the Batch Monitor (from Version 5 Session) For more information about the Batch Monitor, please refer to Using the Batch monitor in CATIA - Infrastructure User's Guide. 1. Start a Version 5 Session. 2. Select the Tools->Utility commands. The Batch Monitor panel opens. A list of Version 5 batches along with their description will be displayed in the Type column. 3. Select MigrateV4ToV5: this tool allows you to convert CATIA Version 4 models into CATIA Version 5 models. And the V4 To V5 Migration Batch is available: V4 Integration Version 5 Release 14 Page 124 If you compare with the Migration batch dialog box launched in interactive mode, there is an additional setting: The Batch can be used: ● on your local machine ● or on a remote machine. And you can check your licensing by clicking on the Licensing Setup button. Using the DataLifeCycle Batch via the Batch Monitor (from Version 5 Session) V4 Integration Version 5 Release 14 Page 125 1. Start a Version 5 Session. 2. Select the Tools->Utility commands. The Batch Monitor panel opens. A list of Version 5 batches along with their description will be displayed in the Type column. 3. Select DataLifeCycle: like the V4 To V5 Migration Batch, this tool allows you to convert CATIA Version 4 models into CATIA Version 5 models and have access to databases as well. And the DataLifeCycle Batch is displayed: V4 Integration Version 5 Release 14 Page 126 For more information about this launching mode, please refer to: Converting CATIA Version 4 Models into CATIA Version 5 with the DataLifeCycle Batch. V4 Integration Version 5 Release 14 Page 127 Converting CATIA Version 4 Models into CATIA Version 5 with the V4 To V5 Migration Batch This task shows you how to convert CATIA Version 4 models to CATIA Version 5 in batch mode. V4 Data conversion through Copy / Paste is useful but contains a few restrictions. Therefore, the batch's technique allows you to treat several V4 documents in one shot, in a global way. This migration tool provides an interactive interface working on a different application from CATIA Version 5. Open the document: WAGON.model. CATV4ToV5Migration Batch 1. Launch the CATV4ToV5Migration Batch. For more information about launching the V4 To V5 Migration batch, please refer to How to launch the V4 To V5 Migration Batch. 2. Select V4 Documents in the File Box by clicking on: The Migration batch dialog box appears. . Version 5 Release 14 V4 Integration 3. Click the Page 128 button to specify the directory name in which the data will be created (by default the data are created in the same place where the first selected V4 document is stored). Click on Open. 4. Perform Specification Check on the V4 documents. For more information, see Checking V4 Model Data Before Copying It to V5: Interactive Checker. 5. Press the Migrate button in order to convert V4 Documents into V5 Documents. The migration is progressive when you select one or several models, and a progress bar appears, giving the user an insight in the migration time. The screen is not frozen during the migration process. V4 Integration Version 5 Release 14 Page 129 The migration report will be displayed in another dialog box at the end of the operation. Double-click on the line of your choice to have more information. In the Migration Report box, the message is OK : the .models and their components can be converted into CATIA V5. V4 Integration Version 5 Release 14 Page 130 For information, if you have checked the Work with the cache system option (by default, the cache is not activated.) in Tools -> Options -> Infrastructure -> Product Structure, the Migration Batch will automatically download the V4 documents in Design Mode. Therefore, the first Report information is: "Swapping in Design Mode"; double-click the line to have more details about the migration. As a consequence you have access to the V4 document, WAGON.CATProduct, in CATIA V5: V4 Integration Version 5 Release 14 Page 131 If you had migrated by Copy / Paste you may not have the same result. Batch reduces the number of interactions and offers possibilities to make more relevant migrations for complex V4 data structures. 6. You have the possibility to Save the Migration Report As Text File. In the Migration report window, you can expand the elements' list under WAGON.model by a double-click on WAGON.model. If you click on the Save As Text button, these data will be saved in the file and directory of your choice. V4 Integration Version 5 Release 14 Page 132 When you open the .txt file containing migration information about the .model, the .model's identifiers are automatically expanded in a list. V4 Integration Version 5 Release 14 Page 133 A few rules about Batch Conversion: The Batch Migration of a model takes into account V4 data structure. Compared to the Copy / Paste process, the Batch process generates more pertinent V5 data. According to its content, a model is migrated into several documents: a CATPart and / or a CATProduct and / or a CATDrawing. To separate the treatment of SPACE data and DRAW data, click on the Options button and the Tools -> Options -> V4 / V5 Infrastructure panel is displayed : you can select Space And Draw, or Space or Draw. For more information, refer to Customizing V4/V5 DRAW and Customizing V4/V5 SPACE in CATIA Infrastructure User's Guide. Page 134 Version 5 Release 14 V4 Integration Batch Migration of DRAW data: When a model contains DRAW data, they are migrated as a unique document : a CATDrawing. Some entities undergo a few changes during the V4 to V5 conversion : ● V4 DRAFT -> V5 Sheet ● V4 Detail -> V5 Detail Sheet ● V4 Views -> V5 Views In the Batch Mode, all Draw and Detail workspaces are migrated in CATIA V5. On the contrary, if you Copy / Paste a Draft or a View interactively, only referenced Details are migrated. If you have checked the setting Open in Light Mode: 2 Data is not taken into account in Tools->Options->V4/V5 Infrastructure, the batch will not be able to migrate V4 Drawing data. Therefore, if you want to convert V4 drawing elements in CATIA V5, it is necessary to uncheck this setting. Batch Migration of SPACE data: The "V4 Part" definition is the Geometric Set: the subsets will be migrated into a V5 CATPart document. The "V4 Part" definition can also be a Solid: the Solids will be migrated into CATParts and the non-solid elements (for instance: Wireframe) into a CATPart as well. 1. Every Geometric Set contained in a model generates a CATPart (only Dittos are managed separately). 2. Every Workspace containing several Dittos or Set instances is converted as a CATProduct. Under this CATProduct, there are as many components as Dittos (Part or Product instances) and Sets (Part instances only). The impacts of the V4 to V5 conversion on the entities: ● V4 Set -> V5 Part ● V4 Detail -> V5 Part or Product ● V4 Ditto -> V5 Product component ● V4 Model (.model) -> V5 Part or Product and/or CATDrawing ● V4 Session (.session) -> V5 Product ● V4 Assembly (.asm) -> V5 Product When you convert a .asm through the migration batch, you obtain a CATProduct. The result is the same when you read (File/Open) a .asm in CATIA V5; for more information about Opening a .asm Document in CATIA V5, please refer to the CATIA - Assembly User's Guide. This table shows you what you can get in CATIA V5 after the Batch conversion: V4 V5 .asm Product a .asm referencing one or more .asm documents a Product referencing one or more Products a .asm referencing a .model a Product referencing a Model V4 Integration Version 5 Release 14 Page 135 Take the example of the WAGON.model and look at the conversion results. The model has been converted into a CATProduct containing two Dittos (of AXLE) plus a Geometric Set (the red box). AXIS and WHEEL are two Details, the one contains two Dittos of WHEEL and the other has a ditto of AXIS. ● AXLE -> CATProduct ● AXLETREE -> CATPart ● WHEEL -> CATPart ● SET -> CATPart V4 Integration Version 5 Release 14 Page 136 Converting CATIA Version 4 Models into CATIA Version 5 with the DataLifeCycle Batch This task shows you how to convert CATIA Version 4 models to CATIA Version 5 with the DataLifeCycle Batch. The documents, target, directory and report name can be selected in the DataLifeCycle panel. This migration tool provides an interactive interface working on a different application from CATIA Version 5. DataLifeCycle Batch 1. Start a Version 5 Session. 2. Select the Tools->Utility commands. The Batch Monitor panel opens. A list of Version 5 batches along with their description will be displayed in the Type column. 3. Select DataLifeCycle: like the V4 To V5 Migration Batch, this tool allows you to convert CATIA Version 4 models into CATIA Version 5 models and have access to databases as well. The DataLifeCycle Batch is displayed: Version 5 Release 14 V4 Integration 4. In the Selected Operation field, click MigrateV4ToV5 and the Migration Mode panel appears: 5. Choose different settings: Selection Mode: There are two modes to launch the Batch: ● ● Complete: you can migrate Sets, Solids and/or Layers As Result or As Spec. or User defined: you can select *SOL and/or *LAY and/or *SET, or you can select specific names SOL1, SOLxx, LAY2, LAYyy, etc... Objects and Format: In Complete mode, select a line, SOLID for instance, and choose a Format: by clicking one of these buttons: . You can also Delete elements in the List. In User defined mode, select a line in the Objects list, which activate the same AsResult, AsSpec and Delete buttons. Page 137 Version 5 Release 14 V4 Integration Page 138 Option: ● ● Check: for simulation. For more information about this option, please refer to Checking V4 Model data before Copying it to V5. or Migrate: V4 To V5 Migration will be applied. In User defined mode, identifiers can written in upper or lower case in the empty box entitled Objects because the case is not taken into account. But once you have selected the Add icon, the names are always reported in upper case. Moreover, the element name can appear only once in the Objects list. 6. Click Next. Another panel Migration Outputs is displayed (customizing settings for both modes Complete and User defined). Structuring Element: Depending on the combinations, you can select 0 or 1 or several boxes (Layer, Solid, Set, Ditto). By this way, you define a document per entity type. According to configurations, you can also explode Dittos. But some combinations are not not supported and a Warning appears if you have selected wrong combinations. The following table shows you what is supported (X): Page 139 Version 5 Release 14 V4 Integration What is supported (X) LAYER SOLID SET DITTO X 1 X 2 X 3 4 X X 5 X X X 6 X X 7 X X 8 X X X 9 To have information about the following options, you can refer to the documentation Customizing Migration Batch: ● Conversion Mode, ● Drawing Parameters, ● Projection of space for transparent views, ● Mapping files location for saving, ● Mapping Files for Retrieving. 7. Click Finish. A new panel, Current Options, is displayed; it is a summarize of the selected options: V4 Integration Version 5 Release 14 8. Click OK and the DataLifeCycle panel appears. 9. Select the Save button in the DataLifeCycle panel and the Check or Migrate operation is launched. Page 140 V4 Integration Version 5 Release 14 Page 141 Automatic Transfer of a Version 4 Model Comment into a Version 5 CATProduct or CATPart (during a V4 to V5 Migration) This task shows you how the transfer of CATIA Version 4 model comment into CATIA Version 5 operates automatically during a V4 to V5 Migration and how you can have access to it in CATIA Version 5. The automatic transfer of a V4 Model Comment into CATIA V5 occurs when: Opening or migrating a Model into CATIA V5 Copying/Pasting a Model Comment into CATPart Properties For more information about Manipulating V4 Models in V5 and especially V4 Model comment, refer to Having Access to V4 Model Comment. Opening / migrating a Model into CATIA V5 Open the document: MODEL_COMMENT.model in CATIA Version 5. The maximum length of a V4 comment is 70 characters per line. If you exceed this number, a new line -with date- is created. When you save a .model in CATIA V4, the comment(s) (plus dates) you have added to the document is/are kept in memory. 1. To have access to the V4 Model comment, select any component in the .model and the Edit -> Properties command. The Properties dialog box appears. The V4 comments and their date of creation are available in the Comment tab: V4 Integration Version 5 Release 14 Page 142 2. Open the document PART_COMMENT.CATPart. After a migration, the .model turned into a CATPart. The comment is saved on the highest level of a document: on a CATProduct or a CATPart, but not on a CATDrawing. Note that the Properties dialog box is a little different but the access to this information is quite the same, select any component of the CATPart (or CATProduct) and Edit -> Properties. Press the Product Tab and the comments are in the Description field: You can now compare, the original comments have been transferred from CATIA Version 4 to CATIA Version 5. Moreover, in the Properties dialog box, in the Description field you can add information or modify the content of a CATPart / CATProduct's comment, then click on OK. When closing the CATPart or CATProduct, this message appears : The new comment can be saved in the CATPart's properties when you close and save the document. Copying / Pasting a V4 Model into a CATPart V4 Integration Version 5 Release 14 Page 143 1. To have access to the V4 Model's comment, select any component in the .model and the Edit -> Properties command. The Properties dialog box appears. The V4 comments and their date of creation are available in the Comment tab: 2. Copy / Paste As Result or As Spec the Model into a CATPart. 3. To read the Model's Comment, select Part1 of the CATPart and the contextual command Edit -> Properties. Press the Product Tab and the comments are in the Description field: V4 Integration Version 5 Release 14 Page 144 During the copy / paste operation, the Model's Comment has been transferred into the CATPart. The Comment is extracted from the Model and copied into the CATPart Description. If the target CATPart already contains a Description, the Model's Comment is concatenated, added to this description. In the Properties dialog box, in the Description field you can add information or modify the content of a CATPart / CATProduct's comment, then click on OK. When closing the CATPart or CATProduct, this message appears: The new comment can be saved in the CATPart's properties when you close and save the document. V4 Integration Version 5 Release 14 Page 145 Automatic Transfer of a Version 4 Detail Comment into a Version 5 CATProduct or CATPart (during a V4 to V5 Migration) This task shows you how the transfer of a CATIA V4 Detail comment into CATIA Version 5 automatically operates during a V4 to V5 Migration and how you can have access to it in CATIA Version 5. Open the document: DETAIL_WITH_COMMENT.model in CATIA Version 5. This model contains a Detail ( SPHERE) with a comment and 4 Dittos. The maximum length of a V4 comment is 48 characters per line. When you save a Model with a Detail in CATIA V4, the comment you have added to the Detail is kept in memory. 1. Open the documentS DETAIL_WITH_COMMENT.CATProduct and DETAIL_WITH_COMMENT_SPHERE_xSET2.CATPart. After a migration, the .model turned into a CATProduct: And the Detail (SPHERE) into a CATPart: V4 Integration Version 5 Release 14 Page 146 The comment is saved on the highest level of a document : on a CATProduct or a CATPart, but not on a CATDrawing. In our example, the Detail comment is saved in a CATPart. In the CATProduct, there are 4 instances of the CATPart which corresponds to the V4 Dittos and you have access to the same comment within each Ditto. Note that the Properties dialog box is a little different but the access to this information is quite the same. 2. Select any component of the CATProduct (SPHERE (*DIT1) for instance) and click in the contextual Menu on Edit -> Properties. 3. Press the Product Tab and the comments are in the Description field : V4 Integration Version 5 Release 14 Page 147 Moreover, in the Properties dialog box, in the Description field you can add information or modify the content of a CATPart / CATProduct's comment, then click on OK. 4. When closing the CATPart or CATProduct, this message appears: The new comment can be saved in the CATPart's properties when you close and save the document. V4 Integration Version 5 Release 14 Page 148 V4 Integration Version 5 Release 14 Page 149 Converting a Version 4 Session into CATIA Version 5 with the V4 To V5 Migration Batch This task shows you how to convert a CATIA Version 4 Session into CATIA Version 5. In order to allow the Batch to operate properly and to find the models within the .session document, you need to specify the path, to follow these steps to activate the Search Order operation: ● Selecting the Tools->Options... command. The Options dialog box appears with the category tree in the left-hand column. ● In the General category of the Options Tree, select General and click the Document tab: ● Select Other folders in the Linked Document Localization box and press the Configure... button. ● The Other folders dialog box is displayed: V4 Integration ● Version 5 Release 14 Page 150 Select the file path in which the .model documents are stored and click OK. If you forget to set the Search Order and you launch the Batch, the migration report will contain the following message: "Error during migration". V4 Integration Page 151 Version 5 Release 14 For more details about the error type, double-click the first line. Here is a list about the models' path that could not be found by the Batch. SESSION.session document that will be migrated, in our example, looks For information, the CART like this: It is not necessary to open this Session before the Batch migration. Keep in mind that the Batch's result is different from opening a Session in CATIA V5. For more information about this operation, refer to Opening a CATIA Version 4 Session in CATIA Version 5. Only a V4 Session saved "References only" can be read or migrated in CATIA V5. Before launching the batch tool, you have to make sure that your environment is correctly set up. On Windows, the Batch's environment is installed during CATIA's installation. On UNIX, you have to set up this environment before starting the session. For more information about this, see CATIA Infrastructure User's Guide - Starting a session on UNIX. You can then launch the Batch by entering the command : ● CNEXT -batch -e CATV4ToV5Migration 1. Select a .session document (in our example CART SESSION.session): V4 Integration Version 5 Release 14 Page 152 2. Specify the directory name in which the data will be created (by default the data are created in the same place where the first selected V4 document is stored) by clicking on the button . Then click Open. V4 Integration Version 5 Release 14 Page 153 3. Perform Specification Check on the V4 documents. For more information, see Checking V4 Model Data Before Copying It to V5 : Interactive Checker. 4. Press the Migrate button in order to convert the V4 Session into V5 Documents. The Migration Report will be displayed in another dialog box at the end of the operation. Double-click on the line of your choice to have more information. In the Migration Report box, the message is OK : the .models and their components can be converted into CATIA V5. V4 Integration Version 5 Release 14 Page 154 Double-click the first line in order to have more details about the models contained in the .session document. As a consequence, you have access to the V4 data (CART chosen above: The CATProduct looks like this: SESSION.CATProduct), in CATIA V5 in the directory you had V4 Integration Version 5 Release 14 Page 155 V4 Integration Version 5 Release 14 Page 156 V4/V5 Associative Migration of Solid MML Structures and Mapping This task shows you how Associative Migration of Solid MML Structures and Mapping can take place when converting a CATIA Version 4 model into CATIA Version 5 in batch mode. For more information about the V4->V5 Migration Batch, see Converting Version 4 Model Data into Version 5 in Batch Mode. Open Cone-0.model and Cone-1.model. V4 Integration Version 5 Release 14 Page 157 1. Launch the CATV4ToV5Migration Batch by entering the following command: On UNIX: catstart -run "CNEXT -batch -e CATV4ToV5Migration" On Windows: CNEXT -batch -e CATV4ToV5Migration 2. Select the V4 Documents (Cone-0.model and Cone-1.model.) in the File Box by clicking on: dialog box appears. . The Migration batch V4 Integration Page 158 Version 5 Release 14 3. If you do not specify the directory name in which the data will be created (by clicking the button), by default the document are created in the same place where the first selected V4 document is stored. Click on Open. 4. Press the Migrate button in order to convert V4 Documents into V5 Documents. In the Migration Report box, the message is OK: the .models and their components can be converted into CATIA V5. You can close this dialog box. V4 Integration Version 5 Release 14 And you obtain: CONE-0_xxSET1.CATPart and CONE-1_xxSET1.CATPart in CATIA V5: Page 159 V4 Integration Version 5 Release 14 *SOL1 from CONE-1_xxSET1.CATPart points to *SOL1 in CONE-0_xxSET1.CATPart. If you select CONE1_xxSET1.CATPart, you can check this information using the Edit->Links command: Page 160 V4 Integration Version 5 Release 14 Page 161 The Links of document dialog box appears, confirming that two links have been found to the documents *SOL1 from CONE_0.model is migrated AS SPEC in the CATPart (the pointed Part). The Specifications of the Solid are in a tool. The pointing model (CONE_1.model) is migrated as a Part (pointing Part), and the pointing solid (*SOL1) is migrated as a Tool with a copy/paste AsResult With Link from the Tool of the Pointed Part. The result of the paste is placed after the current feature of the pointing Part. The internal name of the components of the model, and their migrated v5 objects internal names, are listed in a Map Table, to keep the association between a V4 object and a V5 object. The necessary condition to have a link between the migrated pointing Part and the migrated pointed part, is that the pointed Part must be updated when the pointing model is migrated. If not, no link will be created, and the migrated solid will be a datum, in the pointing part. MML Solids must always be up-to-date so that the batch migration into V5 can succeed. 5. Modify the EdgeFillet in the pointed model CONE_0.model and the Solid of CONE_1.model is no longer up-to-date: V4 Integration Version 5 Release 14 Page 162 6. Update the CONE-1_xxSET.CATPart. The Specifications of CONE-1_xxSET1.CATPart adapts to the pointed Part's modifications. V4 Integration Version 5 Release 14 Page 163 After the migration in Batch mode, associativity is maintained between the two Parts. If the pointed model was renamed the link is broken in CATIA V4, so if the model name is manually changed (for instance, replace by space), the link will not be migrated. The link can be migrated but an conflict may occur: ● ● if the pointed model was renamed with the CATV4ToV5NTCompatibilityName batch and the result name already exists in the paths where models looked for. or if another model exists with the same name in the paths where models looked for. V4 Integration Version 5 Release 14 Page 164 Opening a CATIA Version 4 Session in CATIA Version 5 This task shows you how to open a CATIA Version 4 Session in CATIA Version 5 on Windows or Unix. This procedure allows you to translate V4 data (document structure) into V5 Format. Opening a CATIA V4 session generates a CATIA V5 CATProduct. This CATProduct contains the .model documents linked to the .session document. A V4 Session document is a document structure containing several CATIA V4 models. If you open a V4 Session in CATIA V5, it is converted into a CATProduct. The models contained in the Session are automatically transferred into the CATProduct. The impacts of opening a V4 Session in CATIA V5: ● V4 Session => CATProduct ● a V4 Session referencing Models => a CATProduct containing several Models If you encounter any problems to open a V4 Session, please refer to Opening a V4 Session referencing CDM Models. Only V4 Sessions saved "References only" can be read in CATIA V5. 1. Click the Open icon or select the File -> Open... command. 2. In the File Selection box, select the file location. 3. In the "Files of type" list and select session as document type. V4 Integration Version 5 Release 14 4. Select the .session document of your choice and click OK. In our example the Session document looks like this in CATIA V5: Page 165 V4 Integration Version 5 Release 14 Page 166 V4 Session documents containing models that are stored in databases can be opened in CATIA V5. 5. Before opening the .session document, you need to make a connection between CATIA V5 and the databases (VPM, CDMA) in which the .models are stored. For more information about: ● interoperability between CATIA V5 and VPM, please refer to CATIA V5 / ENOVIA VMP Interoperability in VPM User Guide. ● interoperability between CATIA V5 and CDMA, please read Using CDMA Data in a CATIA V5 Assembly (on UNIX only) in VPM User Guide. 6. You also need to customize Document settings: Select the Tools->Options... command and the General category of the Options Tree, and click the Document tab. The ENOVIA VPM Database option must be active (Yes) and click OK to close the dialog box. V4 Integration Version 5 Release 14 Page 167 The result in CATIA V5 is the same: the CATProduct contains the .models documents. It keeps its links with the models referenced in the session and stored in the databases. V4 Session documents can be accessed from Windows with the http protocol. Make sure that an http server has been installed on the machine where the V4 data is stored. The address to be specified should look like this: http://UNIXserver:port/V4datalocation. If the links on the models are unresolved, the following dialog box appears : V4 Integration Version 5 Release 14 Page 168 Use the Search Order environment to specify the directories in which your linked documents are saved. For more information about the Search order environment, refer to Document in CATIA - Infrastructure User's Guide. If CATIA Version 4 Session has been saved with a DLName (for instance, SESSION_DIR), and not with an UNIX path, you can specify the DLName into the Search Order list. For more information about saving a .session document in a DLName environment, read Saving CATIA Version 5 CATProducts As CATIA Version 4 Sessions. You can also convert a .session document into CATIA V5 in Batch mode. As a consequence, the V4 Session is converted into a CATProduct and the CATProducts contained in the Session are converted into CATProducts or CATParts. You can convert a .session referencing Models stored in a database into CATIA V5 in Batch mode. For more information about this type of conversion, refer to Converting a Version 4 Session into Version 5 in Batch Mode. V4 Integration Page 169 Version 5 Release 14 Opening a CATIA V4 Session referencing CDM Models V4 Session documents containing models stored in databases can be opened in CATIA V5. Precisely, this task shows you how to open a V4 session referencing CDM models. Have your CATIA Version 5 environment prepared to open CDMA data and have a CATProduct document open. For more information about Connecting an ORACLE or DB2 Database to your CATIA V5 Environment, please read VPM User Guide. In CATIA V5, on UNIX, you need to connect to the CDM database, by selecting the dialog box appears: button in the Enovia VPM toolbar. A Connection Complete the fields, then click OK. Note that the string to be entered in the Server field is the logical name of your CDM database (the one declared by means of the Database Administration utility). For more information about Adding a CDM Representation to a Product on UNIX, please refer to VPM User Guide. If you have not performed the connection, an Incident Report dialog box will be displayed: The connection to the CDM database will allow you to open Sessions referencing CDM Models. V4 Integration Version 5 Release 14 Page 170 By the same way, you can also open a CATIA V4 session referencing models stored in VPM. The impacts of opening a V4 Session in CATIA V5: ● V4 Session => CATProduct in CATIA V5 ● a V4 Session referencing Models stored in a database => a CATProduct containing the referenced Models ● V4 Model => V4 Model in CATIA V5 For more information about the migration of a session, please refer to Converting a V4 Session in CATIA V5 in Batch Mode. Version 5 Release 14 V4 Integration Page 171 Having Access to PRJ Files on Windows This task shows you that you can have access to the PRJ Files installed on the Windows disk. You need to bring these Project files referenced by the model into an Windows directory and rename these files according to the conversion table. In the PROJECT File path, you refer to the directory containing the Project Files. For more information about character conversion, refer to the Conversion Table in Model Naming. Project File directory cannot be copied natively on Windows: the table file names generally contain Windows forbidden characters. CATIA V5 now uses a character map to retrieve the tables under a different name: ● " character is replaced with string "_Inch" ● * character is replaced with character "x" ● is replaced with character "_" ● Other forbidden Windows ( / \ < > : ? | ) characters are replaced with character "_" ● Non standard ISO characters are replaced with character "_" Renaming the Project File tables according to these specifications will allow the referencing of a Project File stored on Windows. You can use the following methodology to copy your Project File on Windows: 1. Duplicate your Project File directory on UNIX: cp -r 2. Go to the new directory: cd 3. Rename the table files adequately: V4 Integration mv mv mv mv mv Version 5 Release 14 .TEXTCOT : DESCRIPTIONS.project .TEXTCOT : STANDARDS.project PATTERN : DESCRIPTION.project PATTERN : IDENTIFICATEURS.project PATTERN : MOTIFS.project Page 172 .TEXTCOT_ _ _DESCRIPTIONS.project .TEXTCOT_ _ _STANDARDS.project PATTERN_ _ _DESCRIPTION.project PATTERN_ _ _IDENTIFICATEURS.project PATTERN_ _ _MOTIFS.project 4. Perform the same conversion for all table names when needed. 5. Once all the tables have been renamed, you can transfer this directory on Windows workstation and reference it in your compatibility setting. DO NOT modify your directory V4 Project File tables. CATIA V4 would no longer recognize them. On UNIX CATIA V5 is still able to retrieve Project File tables under their standard name> For more information about Customizing the File Project path, refer to V4 Data Reading in CATIA Infrastructure User's Guide. V4 Integration Version 5 Release 14 Page 173 Optimizing V4 Migration Optimizing V4 Family Migration: Deactivation of the No Show Filter Optimizing V4 Family Migration: Deactivation of the Solids' Parents Filter Copy/Paste Details and Dittos: Force Detail to Explode Copy/Paste Details and Dittos: Use of the Multi-Copy/Paste As Result With Link within CATIA V5 Evaluation of the V4 Sketch before applying Constraints Sweep Migration Optimization Sewing Migration on a New Sewing Feature Simplification and Cleaning of V4 Data Version 5 Release 14 V4 Integration Page 174 Optimizing V4 Migration: Deactivation of the No Show Filter When copy/pasting V4 space data, duplication of geometries inside a same family is avoided. The main reason is that some elements such as Faces require the migration of underlying entities such as Surfaces, but the Surfaces may also have been migrated explicitly. The purpose is to analyze the set of objects migrated and extract the representative entities. Thanks to filters, the following elements will no longer be converted: 1. Border curves of migrated Faces (since they would duplicate face edges). 2. Surfaces that are support of migrated faces (since they are already migrated as support of the faces). 3. Faces included in a migrated Skin or Volume ( since they have been migrated through the skin or the volume and are accessible through those federating elements). 4. Volumes and Skins used in migrated solids (solids containing Volume or Skin/split primitives for instances) since they are already migrated through the solid primitive. 5. Elements in Hide, except Solids (SOLIDE or SOLIDM): The management of Hide/Show should be independent from families. However some border effects have convinced us the two behaviors should be associated: for instance if the model contains a Skin in Hide, whereas its faces are in Show space, migrating the Skin and not the Faces separately would not provide the required result. This can result in dramatic improvements in terms of conversion performance, memory consumption and CATPart size. The conversion can be operated on those representative entities only. But these tasks show you that environment variables allow the user to deactivate these filters and to migrate all the V4 features: CATIA V5 behavior without the environment variables (when the filter is activated) CATIA V5 behavior with the environment variables (when the filter is deactivated) Note that the element can still be copy-pasted when selected individually, or if the element it belongs to is not migrated in the same transaction. This enhancement is automatically in use when copy/pasting V4 space data into a CATPart. CATIA V5 behavior without the environment variable (when the filter is activated): Open SURFACE_ISOLATED_UNDERFACE_INSKIN_NOSHOW.model in CATIA V5: V4 Integration Version 5 Release 14 Page 175 Environment variables are provided to disable this behavior (filters): ● set KEEP_HIDDEN_ELEMENT=1 : disables point 5. above ● set INACTIVE_QUICK_PASTE=1 : disables point 1. to 3. The following scenarios deal with the first environment variable (set KEEP_HIDDEN_ELEMENT=1). For more information about the second environment variable, please refer to Optimize V4 Family Migration: Deactivation of the Solids' Parent Filter. 1. Click the Swap visible space icon to visualize the No Show space: V4 Integration Version 5 Release 14 The elements CRV17 and SUR1 contained in the *MASTER are in the No Show space. 2. Copy *MASTER and paste it AS SPEC in a CATPart. 3. Update the CATPart. Page 176 V4 Integration 4. Click the Swap visible space icon: Version 5 Release 14 Page 177 V4 Integration Page 178 Version 5 Release 14 CRV17 and SUR1 which were in the No Show space in the model have not been migrated in CATIA V5. When you have a Skin containing a Face, only one feature "Skin" without Curve borders and Face is migrated. This is a means to avoid duplication of similar features. Functionality scope: V4 model With Filter V5 CATPart 1 Skin in Show + 1 Face in No Show 1 Skin in Show no Border Curve no Face 1 Skin in No Show + 1 Face in Show Face in Show 1 Face + 1 Surface + Border Curves in Show 1 Face no Border Curve no Surface 1 Face in No Show + Border Curves in Show 1 Surface in No Show + Curves in No Show Border Curves in Show no Surface in No Show no Curves in No Show Page 179 Version 5 Release 14 V4 Integration 1 Surface in No Show + Curves in Show 1 Skin in Show + 1 Face in No show 1 Skin in No Show + 1 Face in show When the No Show Filter is deactivated 1 Face + 1 Surface + Border Curves in Show 1 Face in No Show + Border Curves in Show 1 Surface in No Show + Curves in No Show 1 Surface in No Show + Curves in Show Curves in Show 1 Skin in Show + 1 Face in No show Skin in No Show No element in No Show 1 Face no Border Curve no Surface 1 Face in No Show + Border Curves in Show 1 Surface in No Show + Curves in No Show 1 Surface in No Show + Curves in Show CATIA V5 behavior with the environment variables (when the filter is deactivated): On Windows, you can deactivate the No Show Filter by entering the following command: set KEEP_HIDDEN_ELEMENT=1 And on UNIX: export KEEP_HIDDEN_ELEMENT=1 1. Open SURFACE_ISOLATED_UNDERFACE_INSKIN_NOSHOW.model in CATIA V5. 2. Copy *MASTER and paste it AS SPEC in a CATPart. 3. Update the CATPart. V4 Integration 4. Click the Swap visible space icon: Version 5 Release 14 Page 180 V4 Integration Version 5 Release 14 It is now possible to visualize the Curve and Surface in the No Show space. Page 181 Version 5 Release 14 V4 Integration Page 182 Optimizing V4 Migration: Deactivation of the V4 Elements' Parents Filter When copy/pasting V4 space data, duplication of geometries inside a same family is avoided. The main reason is that some elements such as Faces require the migration of underlying entities such as Surfaces, but the Surfaces may also have been migrated explicitly. The purpose is to analyze the set of objects migrated and extract the representative entities. Thanks to filters, the following elements will no longer be converted: 1. Border curves of migrated Faces (since they would duplicate face edges). 2. Surfaces that are support of migrated faces ( since they are already migrated as support of the faces). 3. Faces included in a migrated Skin or Volume ( since they have been migrated through the skin or the volume and are accessible through those federating elements). 4. Volumes and Skins used in migrated solids (solids containing Volume or Skin/split primitives for instances) since they are already migrated through the solid primitive. The deactivation of the No Show filter upon Volumes and Skins is automatic during the copy/paste AS SPEC (no environment variable is needed). 5. Elements in Hide, except Solids (SOLIDE or SOLIDM): The management of Hide/Show should be independent from families. However some border effects have convinced us the two behaviors should be associated: for instance if the model contains a Skin in Hide, whereas its faces are in Show space, migrating the Skin and not the Faces separately would not provide the required result. This can result in dramatic improvements in terms of conversion performance, memory consumption and CATPart size. The conversion can be operated on those representative entities only. But these tasks show you that environment variables allow the user to deactivate these filters and to migrate all the V4 features: CATIA V5 behavior without the environment variables (when the filter is activated) CATIA V5 behavior with the environment variables (when the filter is deactivated) Version 5 Release 14 V4 Integration Page 183 Note that the element can still be copy-pasted when selected individually, or if the element it belongs to is not migrated in the same transaction. This enhancement is automatically in use when copy/pasting V4 space data into a CATPart. Environment variables are provided to disable this behavior (filters): ● set KEEP_HIDDEN_ELEMENT=1 : disables point 5. above ● set INACTIVE_QUICK_PASTE=1 : disables point 1. to 3. The following scenarios deal with the second environment variable (set INACTIVE_QUICK_PASTE=1). For more information about the first environment variable, please refer to Optimize V4 Family Migration: Deactivation of the No Show Filter. CATIA V5 behavior without the environment variables (when the filter is activated): Open SOLID_PARENTS.model in CATIA V5: Click the Swap visible space icon to visualize the No Show space: Version 5 Release 14 V4 Integration Page 184 The Exact Solid, *SOL7, belongs to a Volume, *VOL1. A Volume is the parent of a Solid. If you copy/paste a *MASTER containing a Volume and a Solid into CATIA V5, only the Solid is copied. As a consequence there are fewer features and there is more geometry. Volumes, Faces and Solids are in the Show space. Volumes, Faces and Border Curves are not migrated because they are filtered, but it is possible to select equivalent features such as Edges, Boundary Curves. 1. Copy *MASTER and paste it AS SPEC in a CATPart (in this mode the BREP of the Solid is migrated). 2. Update the CATPart. V4 Integration 3. Click the Swap visible space icon: Version 5 Release 14 Page 185 V4 Integration Version 5 Release 14 Page 186 The copy of the Solid, Solid.1 (*VOL1 -wsp *MASTER-) (VOLM1) is not duplicated but the Solid is still referencing the VOL1. CATIA V5 behavior with the environment variables (when the filter is deactivated): On Windows, you can deactivate the No Show Filter by entering the following command: set INACTIVE_QUICK_PASTE=1 And on UNIX: export INACTIVE_QUICK_PASTE=1 V4 Integration Version 5 Release 14 Page 187 1. Open SOLID_PARENTS.model in CATIA V5. 2. Copy *MASTER and paste it AS SPEC in a CATPart. 3. Update the CATPart. The Faces allowing the creation of the Volume are migrated into CATIA V5. They are independent features and they are the copies of the ones contained in the PartBody's BREP. As a consequence, this Part is bigger than the first one above. V4 Integration Version 5 Release 14 Page 188 Copy/Paste Details and Dittos: Force Detail to Explode This task shows you how the Details and Dittos can be migrated into CATIA V5 without link. All the V4 workspaces are put together within the same CATPart and the Detail no longer exists (no link). If you want everything to be migrated without CARWL, like the explode of a V4 model, you can select this option "Like V4 explode mode" in Tools -> Options... -> Compatibility -> V4/V5 SPACE tab and click OK: Open V4V5ForceDetailToExplode_ODT.model. The following screenshots show the links between the model's components. The SPHERE is used by DETAIL2: DETAIL2 is used by DETAIL4: V4 Integration DETAIL4 is used by DETAIL8: DETAIL8 is used by *MASTER: Version 5 Release 14 Page 189 V4 Integration Version 5 Release 14 *DIT9 and *DIT10 are in No Show: 1. Copy/Paste (As Spec or As Result) *MASTER into a V5 CATPart. And you obtain: Page 190 V4 Integration Version 5 Release 14 Page 191 V4 Integration Version 5 Release 14 Page 192 2. Update the Part. The elements of the model have been pasted with the No Show and family filter (in our example, the Dittos in No Show *DIT9 and *DIT10 have not been pasted). All the Geometry is gathered in a single Part. The Detail no longer exists and the links between the Detail and the Dittos have disappeared as if you were doing an explode action in CATIA V4 and migrating the results in CATIA V5. For information, with the Batch Migration, all the Geometry of the Details and Dittos is gathered in a CATProduct. Note: ● Be careful with the Explode and Isolated functionalities because memory size incidents may occur during the Paste operation or during the Save of the CATPart. When you have finished, do not forget to uncheck this option. To do it, just check the Usual optimized mode. ● ● Use one or the other setting, but not both at the same time. If you choose one of these settings, be careful because it will be also activated in the interactive mode and in the Batch mode (CATV4ToV5Migration). For information, the batch offers another way to migrate workspaces. V4 Integration Version 5 Release 14 Page 193 Copy/Paste Solids: Use of the Interactive Multi-Copy/Paste As Result With Link within CATIA V5 This task shows you how Solids can be migrated into CATIA V5 and then copied / pasted within CATIA V5 into different CATParts. If you modify the Detail within a Part, you need to synchronize the other Part containing the same Detail (initially copied from another Part). Before, on Windows and UNIX, you needed to edit CATIA V5 with the variable before opening CATIA V5: set InteractivMultiCpARWL=1 Now, the interactive Multi-Copy / Paste As Result With Link is the default mode. It is done without the setting. It saves CPU, memory place and time. If you want to avoid this management, the by-pass is to close the .model after every Paste, and to re-open it if you want to do another Paste. Open MACRO-PRIM.model and create 2 new Parts: Part1 and Part2. 1. Copy / Paste As Spec *SOL7 into a new Part (Part1). 2. Update Part1. V4 Integration Version 5 Release 14 Page 194 3. Copy *SOL7 again and paste it As Spec into Part1 again. 4. Update Part1. Body.6 is the result of the first copy / paste operation and it is used to make a Copy / Paste As Result With Link (CPARWL) within Part1. No transcription is made again but the last result is used. V4 Integration Version 5 Release 14 Page 195 5. Copy / Paste As Spec *SOL7 into Part2. 6. Update Part2. Body.6 (result in Part1) is used to make a CPARWL from Part1 into Part2. No transcription is made but the last paste result is used. 7. Put Solid.4 in No Show in order to have a better visibility. 8. Define in work object Body.6 in Part1. 9. Add a Fillet: EdgeFillet.1. Solid.4 within the same Part1 is automatically updated. However, Part.2 is not synchronized (no associativity between the Parts). V4 Integration Version 5 Release 14 10. Update Part.2 11. Put Solid.4 in Show View. You can note that the Fillet creation is taken into account in Part2 as well as in Part1.. Page 196 V4 Integration Version 5 Release 14 Using the Copy / Paste As Result with Link (CPARWL) method Whenever it is possible, it is recommended to work in CATIA V5. This method (Copy / Paste As Result with Link) allows to save time and provide fast rendering and manipulation for assemblies. Page 197 V4 Integration Version 5 Release 14 Page 198 Evaluation of the V4 Sketch before applying Constraints This task shows how V4 Degree tolerance is automatically calculated in order to keep the edges' specifications (smooth or sharp) in V5 and constraints can be applied on edges. Open Sketch_Cst_2.model and create a new Part: Part1. 1. Copy / Paste As Spec *MASTER into the CATPart (Part1). 2. Update Part1. V4 Integration Version 5 Release 14 Page 199 After the conversion, tangency is maintained because there is an evaluation of the Sketch before. V4 Integration Version 5 Release 14 Page 200 Constraints can be applied when: ● there is a line-circle or circle-line sequence ● and the angle in-between has a vivicity tolerance from 0.5 to 2.5 degrees Therefore, there is an evaluation of the deformations made upon the Sketch according to the V4 vivicity tolerance (2.5) and the V5 vivicity tolerance (0.5). An edge (already smooth for CATIA V5) will not be taken into account. For instance: ● ● if the first V4 angle <=2.5 and the resulting V5 angle is >0.5, therefore vivicity is changed: it was smooth becomes sharp. or if the first angle >=2.5 and the next angle is <0.5, therefore vivicity is changed: it was sharp becomes smooth. This process is called "variation" and it is not recommended to apply constraints because there are too many movings. When there is no constraint to be applied, there is no evaluation of the sketch. V4 Integration Version 5 Release 14 Page 201 Sweep Migration Optimization The purpose of this functionality is to improve quality for Sweep Migration (especially 3D Sweeps that can be migrated AS SPEC) from V4 to V5, by taking into account their specifications during the migration. A Sweep is migrated as a V5 Rib (or Slot), a better representation of the original Sweep in CATIA V5. Open the document SWEEP_surface_ref.model. 1. Copy and Paste Special the Model into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Version 5 Release 14 Page 202 Part Design offers some options for Rib/Slot creation: ● Keep Angle ● Reference Element (plane or surface) With this development, some of these options will be taken into account for V4/V5 migration and will be visible in the "Rib/Slot Definition" panel. Until now, the "Keep Angle" option had always been chosen by default. However, some specifications are not taken into account: ● sweeps with pulling direction V4 Integration Version 5 Release 14 Page 203 2. Double-click Rib.1, for instance, to edit it and see its specifications: you can select the Reference Surface in the Rib Definition dialog box. 3. Click OK and the Reference Surface is Surface.1. V4 Integration Version 5 Release 14 Page 204 The geometry of Rib.1 now depends on the Reference Surface (Surface.1); this reference element is reused in CATIA V5 for the Sweep building. Therefore the migrated Solid exactly corresponds to what you had in CATIA V4, to the V4 Specifications. V4 Integration Version 5 Release 14 Page 205 Sewing Migration on a New Sewing Feature This task will show you how to use the new interface of sewing without intersection. The creation of a SewSurface in PartDesign offers 2 modes: ● Intersection (IntersectSewing mode) ● No Intersection (NoIntersectSewing mode) if topology simplification has been chosen. The goal of this functionality is to advise the user that the "No Intersection" mode is the only one for sewing creation, with an export. In previous version, an environment variable was also provided to activate this mode: ● set SewingNoIntersect=1 (on NT) ● export SewingNoIntersect=1 (on UNIX). It is no more useful now, because it is the default mode. Open the document Sewing_No_Intersection.model. V4 Integration Version 5 Release 14 Page 206 1. You can apply a Check AS SPEC on the model and double-click on the Solid in the Check validity dialog box to see the Sewing component: 2. Copy and Paste Special the Model into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Version 5 Release 14 Page 207 3. SewSurface.1 is present in the Specification Tree in CATIA V5. If you double-click it, you can edit this component. By default, the Intersection option is not checked. V4 Integration Version 5 Release 14 Page 208 Version 5 Release 14 V4 Integration Page 209 Cleaning and Simplification of V4 Data In order to get optimization during the V4/V5 Migration, a variable is active: V5V4CleanTolerance. This variable has the same behavior on V4 or V5 topology. This can result in dramatic improvements in terms of conversion performance, memory consumption and CATPart size. V4V5 Topology cleaning During V4/V5 conversion, V4 objects are cleaned and the Brep is adapted to the V5 containing Part. Those cleaning actions are applied: ● automatically, ● only on V4 entities without specifications, that are transferred as BREP only. Validity checks and cleaner actions: ● cleans invalid objects and migrate all the V4 features (geometry only), ● eliminates small edges, ● merge ● solves the configuration of too large gap between adjacent faces, ● correct inconsistencies of face or edge orientation. confused edges, Add-value: ● ● improve the success ratio of V4/V5 migration without any V4 corrective action, improve the quality and performance of data conversion. Drawbacks: ● gaps between adjacent faces can be increased. Version 5 Release 14 V4 Integration Page 210 How to manage V4V5 Topology Cleaning: It is possible to set a geometric tolerance in order to control the maximum gap allowed by cleaning actions, by activating the V5V4CleanTolerance setting as described below: ● ● default value for this setting is V4 Identical Curves Tolerance (see V4 documentation about: V4 Identical Curves Tolerance Value). a user value can be specified. Example: 1. On Windows, enter the following command: set V5V4CleanTolerance=.01(*) 2. On UNIX, enter the following command: export V5V4CleanTolerance=.01(*) (*) tolerance value: .01 for instance (.01 for 100th mm) Small elements (Edges, Faces) are cleaned inside this tolerance (in our case, tolerance=.01). We guarantee that the gaps created between these cleaning actions are less than this tolerance. Add-value: ● clean small objects according to the specified tolerance, ● better control of V5 topology quality. V4 Integration Version 5 Release 14 Page 211 How to Migrate Application Data In this section, you will find the list of the Application data that can be migrated. It also explains how this conversion is performed according to the application. V4/V5 Part Design Data Migration V4/V5 Manufacturing Data Migration V4/V5 AEC and Tubing Data Migration V4/V5 SheetMetal Design Data Migration V4/V5 Electrical Data Migration V4/V5 Kinematics Data Migration V4 Integration Version 5 Release 14 Page 212 V4 / V5 Part Design Data Migration In this section, you will find the list of the Part Design data that can be migrated. It also explains how this conversion is performed according to the application. Canonics Close and Offset Primitives Rolling Edge Fillet Face-Face Fillet Variable Radius Fillet Tritangent Fillet Fillet Sweep Pyramids, Volumes and Project Primitives Multi-Edge Fillets with Propagation Draft from Reflect Line Basic Draft Pipe Draft Both Sides Multi-Neutral Draft V4 Integration Version 5 Release 14 Page 213 Canonics This task shows you how cuboids but also prisms, spheres, tori, cones, revolutions and cylinders are copied using the option CATIA_SPEC into CATIA V5. Open the document CANONICS.model in CATIA V5. 1. Apply a Check AS SPEC on the .model. V4 Integration Version 5 Release 14 Page 214 2. Copy and Paste Special the Model into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 215 Version 5 Release 14 You have access to the model's geometry and specifications. Therefore, you can now modify each feature of the V5 CATPart document. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove Torus Shaft / Groove V4 Integration Version 5 Release 14 Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface Close Close Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep Edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Angle Fillet Tritangent Fillet Tritangent Fillet Basic Draft Basic Draft Draft Reflect Line Draft Reflect Line Import (with MML link) Solid Datum Macro-Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) Page 216 Version 5 Release 14 V4 Integration Page 217 Close and Offset Primitives This task shows you how standard close and offset primitives are migrated into CATIA V5 using the option CATIA_SPEC. At the end of the task you will find a table presenting restrictions. Open the document CLOSE+OFFSET.model in CATIA V5. 1. Apply a Check AS SPEC on *SET1. V4 Integration Version 5 Release 14 Page 218 2. Copy and Paste Special *SOL1 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 219 Version 5 Release 14 You have access to the model's geometry and specifications. Therefore, you can now modify each feature of the V5 CATPart document. Restrictions Under certain conditions, Close and Offset primitives are converted into solid datum: Note the following restrictions: V4 to V5 Migration Primitives Conditions CATIA_SPEC Offset *SKD as parent Solid Datum Close open *SUR as parent Solid Datum Close *FAC as parent Solid Datum V4 Integration Page 220 Version 5 Release 14 To sum up: V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep Edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Angle Fillet V4 Integration Version 5 Release 14 Tritangent Fillet Tritangent Fillet Basic Draft Basic Draft Draft Reflect Line Draft Reflect Line Import (with MML link) Solid Datum Macro-Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) Page 221 Version 5 Release 14 V4 Integration Page 222 Rolling Edge Fillets This task shows you how a rolling edge fillet is migrated into CATIA V5 using the option CATIA_SPEC. Open the document FILLETROLLING.model in CATIA V5. 1. Apply a Check AS SPEC on *SET1. V4 Integration Version 5 Release 14 Page 223 2. Copy and Paste Special *SOL1 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 224 Version 5 Release 14 You have access to the model's geometry and specifications. CATIA V5 has created an edge fillet feature. If you double-click this feature, you can note that the option "Keep edge" is on in the Edge Fillet Definition dialog box. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove V4 Integration Version 5 Release 14 Page 225 Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) V4 Integration Version 5 Release 14 Page 226 Face-Face Fillet This task shows you how a face-face fillet is migrated into CATIA V5 using the option CATIA_SPEC. Open the document FILLET-FACEFACE.model in CATIA V5. 1. Apply a Check AS SPEC on *SET1. V4 Integration Version 5 Release 14 Page 227 2. Copy and Paste Special *SOL1 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 228 Version 5 Release 14 You have access to the model's geometry and specifications. CATIA V5 has created a face-face fillet feature. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove V4 Integration Version 5 Release 14 Page 229 Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Angle Fillet Tritangent Fillet Tritangent Fillet Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) Version 5 Release 14 V4 Integration Page 230 Variable Radius Fillet This task shows you how a variable radius fillet is migrated into CATIA V5 using the option CATIA_SPEC. Open the document FILLET-VARIABLE.model in CATIA V5. 1. Apply a Check AS SPEC on *SET1. V4 Integration Version 5 Release 14 Page 231 2. Copy and Paste Special *SOL1 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 232 Version 5 Release 14 You have access to the model's geometry and specifications. CATIA V5 has created a variable radius fillet feature. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove V4 Integration Version 5 Release 14 Page 233 Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Radius Fillet Tritangent Fillet Tritangent Fillet Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) V4 Integration Version 5 Release 14 Page 234 Tritangent Fillet This task shows you how a tritangent fillet is migrated into CATIA V5 using the option CATIA_SPEC. Open the document FILLET-TRITGT.model in CATIA V5. 1. Apply a Check AS SPEC on *SET1. V4 Integration Version 5 Release 14 Page 235 2. Copy and Paste Special *SOL1 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 236 Version 5 Release 14 You have access to the model's geometry and specifications. CATIA V5 has created a tritangent fillet feature. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove V4 Integration Version 5 Release 14 Page 237 Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Angle Fillet Tritangent Fillet Tritangent Fillet Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) V4 Integration Version 5 Release 14 Page 238 Fillet This task shows you how a fillet operation performed on different edges using distinct constant radius values are migrated into CATIA V5 using the option CATIA_SPEC. Open the document CONSTANTFILLETMULTIVALUE01.model in CATIA V5. 1. Apply a Check AS SPEC on *SET1. V4 Integration Version 5 Release 14 Page 239 2. Copy and Paste Special *SOL1 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 240 Version 5 Release 14 You have access to the model's geometry and specifications. CATIA V5 has created a variable angle fillet feature. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove Torus Shaft / Groove V4 Integration Version 5 Release 14 Page 241 Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) V4 Integration Version 5 Release 14 Page 242 Sweep This task shows you how sweeps are migrated into CATIA V5. When migrating a sweep, you can use three different options to control the profile. These options are: ● Keep angle ● Pulling direction ● Reference surface (default option) Open the document SWEEP_WITH_REFERENCE_SURFACE.model in CATIA V5. 1. Apply the Check AS SPEC command on *SET1. V4 Integration Version 5 Release 14 Page 243 2. Copy and Paste Special *SOL1 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. In CATIA version 5, the sweep is migrated as a rib. V4 Integration Version 5 Release 14 The profile control option used is "Reference surface". Since CATIA version 5 release 10, "Reference surface" is the default option used for migrating sweeps. Now, if you prefer to sweep the profile using the Keep angle option, you will obtain this rib: Page 244 V4 Integration Version 5 Release 14 To see an example of a sweep migrated using the Pulling direction option, open the document SWEEP_WITH_PULLING_DIRECTION.model in CATIA V5. Perform the steps as described in the above scenario. You obtain this rib: Page 245 V4 Integration Version 5 Release 14 Page 246 The pulling direction used is Line.1, that is the blue line in front of the part (see picture). Now, if you prefer to sweep the profile using the Reference surface option, you will obtain this rib: V4 Integration Page 247 Version 5 Release 14 The reference surface used is Plane.1, that is the blue plane. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket V4 Integration Version 5 Release 14 Page 248 Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Angle Fillet Tritangent Fillet Tritangent Fillet Basic Draft Basic Draft Draft Reflect Line Draft Reflect Line Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) V4 Integration Version 5 Release 14 Page 249 Pyramids, Volumes and Project Primitives This task shows you how pyramids but also volumes and project primitives are migrated into CATIA V5 using the option CATIA_SPEC. Open the document PYRAMID+VOLUME+PROJECT.model in CATIA V5. 1. Apply a Check AS SPEC on the solid. V4 Integration Version 5 Release 14 Page 250 2. Copy and Paste Special *SOL40 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 251 Version 5 Release 14 You have access to the model's geometry only. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove V4 Integration Version 5 Release 14 Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface Close Close Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep Edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Angle Fillet Tritangent Fillet Tritangent Fillet Basic Draft Basic Draft Draft Reflect Line Draft Reflect Line Import (with MML link) Solid Datum Macro-Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) Page 252 Version 5 Release 14 V4 Integration Page 253 Multi-Edge Fillets with Propagation In CATIA V4, it is possible to create a Fillet by selecting several Edges. But in CATIA V5, the process is not the same, there are different propagation modes (tangency and manual) and several Fillet Features. This task shows you how V4 Multi-propagation Fillets can be migrated into several V5 Fillet Features (one per propagation type). Open FILLET_MULTI_PROPAGATION_2_MANUAL_PUIS_2_AUTO.model. 1. Apply a Check AS SPEC on *SET1. V4 Integration Version 5 Release 14 2. Double-click one of the three messages to have more details about the components: This solid contains 2 Fillet Features. FILL3 is defined by 2 Edges with 2 propagation modes. 3. Copy/Paste AS SPEC the .model into a CATPart. Page 254 V4 Integration Version 5 Release 14 Page 255 In the Specification Tree, there is a Feature per propagation mode. In this example, you can see 2 Features corresponding to FILL3 in CATIA V4 and representing 2 modes of propagation (Tangency and Minimal): ● EdgeFillet.2 (FILL3) ● EdgeFillet.3 (FILL3) The sequential order in which the user had selected the Edges for propagation in CATIA V4 is respected in the Specification Tree in CATIA V5. EdgeFillet.3 has two results (2 EdgeFillets) in CATIA V5. Double-click EdgeFillet.3 to edit it: V4 Integration Page 256 Version 5 Release 14 To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) V4 Integration Version 5 Release 14 Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Page 257 Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Angle Fillet Tritangent Fillet Tritangent Fillet MultiEdge Fillets with Propagation a Feature per propagation mode in the Specification Tree Basic Draft Basic Draft Draft Reflect Line Draft Reflect Line Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) Version 5 Release 14 V4 Integration Page 258 Draft from Reflect Line This task shows you how a reflect line draft is migrated into CATIA V5 using the option CATIA_SPEC. Open the document DraftReflectLine_KeepFace.model in CATIA V5. 1. Apply a Check AS SPEC on *SET1. V4 Integration Version 5 Release 14 Page 259 2. Copy and Paste Special *SOL1 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 260 Version 5 Release 14 You have access to the model's geometry and specifications. CATIA V5 has created a draft reflect line feature. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Face-Face Fillet Face-Face Fillet V4 Integration Version 5 Release 14 Variable Angle Fillet Variable Angle Fillet Tritangent Fillet Tritangent Fillet Basic Draft Basic Draft Draft Reflect Line Draft Reflect Line Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) Page 261 V4 Integration Version 5 Release 14 Page 262 Basic Draft This task shows you how a basic draft is migrated into CATIA V5 using the option CATIA_SPEC. Open the document SheerDraft.model in CATIA V5. 1. Apply a Check AS SPEC on *SET1. V4 Integration Version 5 Release 14 Page 263 2. Copy and Paste Special *SOL1 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 264 Version 5 Release 14 You have access to the model's geometry and specifications. CATIA V5 has created a draft feature. Note that the "Square mode" is the default draft form: Note: In the following example, the solid contains four drafted faces. Two faces have been drafted using the same angle value, the other two faces with distinct angle values. After migrating this data into CATIA V5, we obtain three drafts. Both drafts using the same angle value have been converted into one Draft feature (Draft.2). If you wish to perform the migration, open DraftMultiAngle2.model. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove V4 Integration Version 5 Release 14 Page 265 Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Angle Fillet Tritangent Fillet Tritangent Fillet Basic Draft Basic Draft Draft Reflect Line Draft Reflect Line Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) Version 5 Release 14 V4 Integration Pipe This task shows you how a pipe is migrated into CATIA V5 using the option CATIA_SPEC. Open the document PIPE_SPLINE3D.modelin CATIA V5. 1. Apply a Check AS SPEC on *SET1. Page 266 V4 Integration Version 5 Release 14 Page 267 2. Copy and Paste Special *SET1 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. In CATIA version 5, the pipe is migrated as a rib. V4 Integration Page 268 Version 5 Release 14 The profile control option used is "Keep angle". To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) V4 Integration Version 5 Release 14 Page 269 Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Angle Fillet Tritangent Fillet Tritangent Fillet Basic Draft Basic Draft Draft Reflect Line Draft Reflect Line Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) V4 Integration Version 5 Release 14 Page 270 Draft Both Sides This task shows you how a draft both sides primitive is migrated into CATIA V5 using the option CATIA_SPEC. Open the document DRAFT_BOTH_SIDES_2_ANGLES_NEUTRAL.model in CATIA V5. Two faces are drafted using two distinct neutral elements and a parting element. 1. Apply a Check AS SPEC on *SET1. V4 Integration Version 5 Release 14 Page 271 2. Copy and Paste Special *SET1 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 272 Version 5 Release 14 The Draft Definition (Advanced Draft) dialog box clearly shows that two faces were drafted (1st Side and 2nd side tabs) using a parting element. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove V4 Integration Version 5 Release 14 Page 273 Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Angle Fillet Tritangent Fillet Tritangent Fillet Basic Draft Basic Draft Draft Reflect Line Draft Reflect Line Draft Both Sides Draft Both Sides Draft Multi-Neutral Draft Multi-Neutral Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) Version 5 Release 14 V4 Integration Page 274 Multi-Neutral Draft This task shows you how a draft both sides primitive is migrated into CATIA V5 using the option CATIA_SPEC. Open the document DRAFT_MULTI_NEUTRAL.model in CATIA V5. The purple draft is created using nine faces determining the neutral element. 1. Apply a Check AS SPEC on *SET1. V4 Integration Version 5 Release 14 Page 275 2. Copy and Paste Special *SOL3 into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Page 276 Version 5 Release 14 The Draft Definition dialog box clearly shows that the purple face was drafted using nine faces to determine the parting element. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot V4 Integration Version 5 Release 14 Page 277 Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum Offset Thick Surface (or Solid Datum under certain conditions) Close Close (or Solid Datum under certain conditions) Project Solid Datum Volume Solid Datum Constant Edge Fillet Edge Fillet Constant Edge Fillet (several edges, distinct values) Variable Angle Fillet Rolling Edge Fillet Edge Fillet (option Keep edge on) Face-Face Fillet Face-Face Fillet Variable Angle Fillet Variable Angle Fillet Tritangent Fillet Tritangent Fillet Basic Draft Basic Draft Draft Reflect Line Draft Reflect Line Draft Both Sides Draft Both Sides Draft Multi-Neutral Draft Multi-Neutral Import (with MML link) Solid Datum Macro Primitive Copy with Link of a Body Not Supported Primitive Solid Datum (if the solid is smart) V4 Integration Version 5 Release 14 Page 278 V4/V5 Manufacturing Data Migration What can be migrated from CATIA V4 to CATIA V5 in Manufacturing: ● ● Browse a V4 NC Mill Model: how to Browse the tool path Browse a V4 NC Mill Operation: how to Browse V4 Specifications, visualization of the .model (sets NC Mill) in CATIA V5. The tool path is not recalculated. You can select the V4 Sets you need to get back into CATIA V5. ● Import NC Data: how to import NC data in the NC Manufacturing Review workbench. ● Tool Path Replay and Simulation: replay of the tool path and material removal simulation. For detailed information about the migration of V4 Manufacturing Entities into CATIA V5, please refer to the CATIA - NC Manufacturing Review User Guide. V4 Integration Version 5 Release 14 Page 279 V4/V5 AEC and Tubing Data Migration These chapters explain how you can migrate your V4 models to V5: ● V4/V5 Tubing Data Migration ❍ ● V4/V5 Piping Data Migration ❍ ● For more information, please refer to the "Migrating V4 Models to V5" section, in the CATIA - Equipment Arrangement User' Guide. V4/V5 HVAC Data Migration ❍ ● For more information, please refer to the "Migrating V4 Models to V5" section, in the CATIA - Piping Design User' Guide. V4/V5 Equipment Data Migration ❍ ● For more information, please refer to the "Migrating V4 Models to V5" section, in the CATIA - Tubing Design User' Guide. For more information, please refer to the "Migrating V4 Models to V5" section, in the CATIA - HVAC Design User' Guide. V4/V5 Structures Data Migration ❍ For more information, please refer to the "Migrating V4 Structures Elements" section, in the CATIA - Structure Design User' Guide. Version 5 Release 14 V4 Integration Page 280 V4/V5 SheetMetal Data Migration This task explains how to convert data from a CATIA V4 sheetmetal model into a CATIA V5 sheetmetal part. Open the MigratingModelV4.model document in CATIA V4 from the Samples directory. 1. In your CATIA V4 session, use the Merge option in the Solid function to merge the whole model into one solid. 2. Save the changes. 3. Open your V4 model in a CATIA V5 session. 4. Right-click the *MASTER and select Copy from the contextual menu. 5. Open a new .CATPart document in the SheetMetal Design workbench using the New -> Part commands from the File menu bar. 6. Right-click Part1 and select Paste from the contextual menu. V4 Integration Version 5 Release 14 Page 281 Here is the result: Now you need to recognize the thin part shapes of the part as it was created from a CATIA Version 4 Solid for example. Walls, bends, cutouts, corner relieves are recognized. Version 5 Release 14 V4 Integration 6. Click the Walls Recognition icon Page 282 . 7. Select the solid in the 3D geometry. The Walls Recognition Definition dialog box displays. 8. Select Part body recognition so that the whole solid is processed and walls are created wherever possible. ● ● The Reference wall is indicated in the Walls Recognition Definition dialog box for information only (it is grayed out). The Generate Bends check button allows the automatic creation of bends as the walls are being created, wherever applicable. 9. Click OK to generate the features. If the case certain features cannot be recognized, or there is a tolerance problem , you can manually complete the part. Version 5 Release 14 V4 Integration Page 283 V4/V5 Electrical Data Migration This section explains how an existing CATIA V4 Electrical model is converted into V5 documents. The conversion of the V4 data is performed using the migration batch. It is divided into the following chapters: Methodology Migrating Step by Step... V4 - V5 Mapping Reference Information Frequently Asked Questions Version 5 Release 14 V4 Integration Methodology To perform the migration of the electrical data (geometry and technology), you first need to set up options: ● for the migration batch ● for the bundle segment migration mode ● for the isolated mock-up solids migration. These options can also be defined using: ● the Tools -> Options... -> General -> Migration Batch tab ● the Tools -> Options... -> General -> Electrical tab ● and the Tools -> Options -> General -> Compatibility -> V4/V5 Space. Refer to the Infrastructure User's Guide (Customizing Settings - General - Compatibility category). Using Copy/Paste only copies the geometry and does not migrate the technology. To do so, you need to access to the Batch Monitor: 1. Open the Tools -> Utility... menu item: The Batch Monitor window opens. 2. Double-click the MigrateV4ToV5 utility: Page 284 V4 Integration The MigrateV4ToV5 dialog box opens. Version 5 Release 14 Page 285 Version 5 Release 14 V4 Integration Setting up the Electrical Migration Batch a. Click the Options... button. The Batch Options dialog box opens. b. Select the Migration Batch tab. At the bottom of this dialog box, in the Interface Name field, enter CATIE3DMigration: Page 286 Version 5 Release 14 V4 Integration Page 287 c. Click OK to validate the entry made, otherwise the Electrical tab options won't be activated. Setting up the Bundle Segment Migration Mode a. Still in the Batch Options dialog box, select the Electrical tab. This tab lets you define if you want: ❍ each V4 BNS of the GBN migrated to a separate CATPart: in this case, select Bundle segments. ❍ all the V4 BNSs of the GBN migrated to a single CATPart: in this case, select Multi-branchable bundle segments. Multi-branchable bundle segments is the default value. It is recommended to use this option as it reduces the number of CATPart documents generated during the migration. Version 5 Release 14 V4 Integration Page 288 b. Select the option of interest. Setting up Isolated Mock-Up Solids migration This option is only necessary if you have isolated mock-up solids to migrate. a. Still in the Batch Options dialog box, select the V4/V5 SPACE tab. This tab lets you define an option for the Isolated Mock-up Solids migration: Isolated Mock-Up Solids (SolidM) means that they have no history nor specifications stored. For the migration two options are available: ❍ as CGR: the SolidM conversion as CGR means that you will only get the meshing view (visualization mode). as CGR is the default value. ❍ as PartBody: the SolidM conversion as PartBody means that you will be able to see the geometry of the solid to edit it. Refer to V4/V5 SPACE tab in Infrastructure User's Guide. (Customizing Settings - General - Compatibility category). b. Select as PartBody in the context of the electrical migration to be able to add technology. V4 Integration Version 5 Release 14 3. Once you have selected your options, click OK to validate. You are back in the MigrateV4ToV5 dialog box. 4. Select a target directory (where the V5 documents will be created). 5. Select the V4 documents to be converted. You are ready to migrate your V4 electrical data. An alternative to launch the Migration Batch is as follows: 1. Enter the following command: CNEXT -batch -e CATV4ToV5Migration. 2. Select a target directory (where the V5 documents will be created). 3. Select the V4 documents to be converted. Page 289 Version 5 Release 14 V4 Integration Page 290 The Options... button lets you define if you want: ❍ each V4 BNS of the GBN migrated to a separate CATPart: in this case, select Bundle segments ❍ all the V4 BNSs of the GBN migrated to a single CATPart: in this case, select Multi-branchable bundle segments. It is recommended to use this option as it reduces the number of CATPart documents generated during the migration. Multi-branchable bundle segments is the default value. You can now migrate your V4 data according to your choice. For more information, refer to the V4 Integration documentation - User Tasks - Converting CATIA Version 4 Models into CATIA Version 5 in Batch Mode. Version 5 Release 14 V4 Integration Page 291 Migrating Electrical Data Step by Step Once the options are set up, you can launch the migration batch. For more information on the Migration Batch, refer to the V4 Integration User's Guide - User Tasks - Migration in Batch Mode. 1. Open the Tools -> Utility... menu item: The Batch Monitor window opens. 2. Double-click the MigrateV4ToV5 utility: The MigrateV4ToV5 dialog box opens. V4 Integration Version 5 Release 14 3. Click Browse File to navigate to the sample model: it is located in .../online/cfysm_C2/samples/ElectricalMigration/migration.model 4. Click the ... button to select the target directory. Make sure you have set up the correct options. The window looks like this: Page 292 Version 5 Release 14 V4 Integration Page 293 5. Click Run. When the migration is performed, you get the migration.CATProduct in your target directory, as well as CATParts and other documents. 6. Open the migration.CATProduct in CATIA V5. If the Update All icon is activated, you need to update your document. 7. Click the Update All button if need be. You may have a message indicating a problem on the geometry such as: ❍ a twisted configuration on a bundle segment See Reference Information. ❍ ❍ a fillet which needs to be modified Refer to Part Design User's Guide. etc. 8. Then you need to complete the information for a certain number of V5 components. Select the reference so the modification will be performed on all the instances. Version 5 Release 14 V4 Integration a. Page 294 For single insert connectors On V5 single insert connectors, the Representation of the connector connection point and the Contact constraint correspond to the migrated point of the CPP of the V4 SIC. Coincidence and Orientation constraints must be added, using Electrical Library. ■ ■ ■ Select the single insert connector as shown above: GLY-002 See the specification tree below. Using the right-mouse button, select Open in New Window to open the CATPart reference. Double-click the *CPP4 in the Electrical container The Connector Connection Point Definition opens: . Refer to Electrical Library User's Guide - User Tasks - Defining Electrical Connection Points. ■ Select the face as Contact Version 5 Release 14 V4 Integration ■ Page 295 Select the axis as Coincidence The result looks like this: ■ ■ To use the Orientation constraint on this sample, you would need to create the geometry (such as a notch). Refer to Generative Shape Design User's Guide. Click OK to validate the entry made. The publication have been generated. Version 5 Release 14 V4 Integration Specification Tree Repeat these steps for the other single insert connector: Page 296 Version 5 Release 14 V4 Integration ■ Page 297 Select ELEC2 See the specification tree below. ■ Add the placement constraints to the *CPP5. ■ Using Electrical Library: then re-connect the single insert connectors to create the mechanical constraints. Disconnect Refer to Electrical Library User's Guide - User Tasks - Connecting/Disconnecting Devices. Specification Tree b. To connect a single insert connector to an equipment or connector shell Version 5 Release 14 V4 Integration Page 298 You need to add a cavity connection point to the single insert connector and add or complete the definition of a cavity to the equipment or connector shell. ■ adding a cavity connection point to the single insert connector ■ ■ With the same methodology, select migration_ECP-GLY-001_xxSET2 for example and open it in new window. Using Electrical Library, click Define Cavity Connection Point . Select the face for the Representation and the Contact, and the axis for the Coincidence. Refer to Electrical Library User's Guide - User Tasks - Defining Electrical Connection Points. The cavity connection point is created: ■ completing the definition of a cavity to the equipment or connector shell: here a connector shell. Version 5 Release 14 V4 Integration ■ ■ Page 299 Select the connector shell: SHELL-GLY-002 and open it in new window. The cavities exist, but information is missing: you need to define the geometry of a pocket for example. Refer to Part Design User's Guide. Then using Electrical Library, select GLY-01 and click Define Cavity . Select the pocket for the Representation, the face for the Contact, and the axis for the Coincidence. Repeat the operations for GLY-02 Refer to Electrical Library User's Guide - User Tasks - Defining Electrical Connection Points. The cavity definition is completed: Version 5 Release 14 V4 Integration ■ You now need to connect the single insert connector to the connector shell: Click Connect Electrical Devices Select the single insert connector then the connector shell cavity. Page 300 Version 5 Release 14 V4 Integration Page 301 c. For information about other elements to be added to complete the electrical data in V5, refer to About Device Migration. Also refer to Electrical Library User's Guide. Page 302 Version 5 Release 14 V4 Integration V4-V5 Mapping The V4 architecture philosophy is quite different from the V5 Product Structure one. As a consequence, the V4 objects are quite different from the V5 ones. A mapping between V4 and V5 objects can be established. Object definition V4 element V5 element GBN ElecGeoBundle Comment No attributes Object definition BNS circular only ElecBundleSegment a CATPart for each V4 BNS (Bundle segments) or a CATPart for all the V4 BNSs under a V4 GBN (Multi-branchable bundle segments) Attributes of BNS MODE Elec_Creation_Mode BENDRAD Elec_Bend_Radius DISLACK Elec_Di_Slack if MODE is set to SLACK TLENGTH Elec_Length if MODE is set to LENGTH SEGREG Elec_Segreg Separation code Associated objects Object definition Page 303 Version 5 Release 14 V4 Integration BPP ElecBundleSegmentExtremity Point used to create the curve Point for extremity BPP for other BPP for standalone BPP BSJ Connection No geometry associated SIC<> ElecSingleConnector Standard migration for geometry A cavity connection point must be added in the context of an electrical assembly. ETN Electrical Termination ES External Splice Standard migration for geometry A cavity connection point must be added in the context of an electrical assembly. IS Internal Splice No geometry BPP ElecBundleConnectionPoint CPP Connector Connection Point Need to be enhanced manually. See Migrating Step by Step... Attributes Object definition PARTNUM Product Structure Part Number IDNUM Valuated on the parent Cavity NUMPIN Electrical Terminal number CSL ElecConnectorShell Standard migration for geometry A cavity must be added in the context of an electrical assembly. Attributes of CSL PARTNUM Product Structure Part Number IDNUM Valuated on the parent Cavity Associated object Object definition BPP ElecBundleConnectionPoint EQT ElecEquipment Standard migration for geometry A cavity must be added in the context of an electrical assembly. Attribute Object definition PARTNUM Product Structure Part Number SPT Mechanical Part linked to bundle segments SPS a point and two planes Attribute Standard migration for geometry Version 5 Release 14 V4 Integration Object definition PARTNUM Product Structure Part Number BSF ElecProtection (Tape type) Page 304 Attribute PARTNUM Product Structure Part Number The electrical behavior is added to the geometry of the converted equipments, connector shells and single insert connectors. The BSJs become connections between bundles segments. The supports (SPT) are converted into mechanical parts to which the bundle segments are linked through publications. The bundle surface (BSF) becomes a protection of tape type. The terminal block (TB) and the terminal strip (TS) are not migrated. Only the geometry appears with no electrical behavior. The external splice (ES) is migrated as a connector of external splice type. The internal splice (IS) is migrated as a connector of internal splice type. The geometry of the bundle junction (BSJ) is migrated as is. Version 5 Release 14 V4 Integration Page 305 Reference Information This section gives general information about the V4 to V5 electrical migration. To know more about V5 devices, refer to Electrical Library User's Guide. V4 to V5 Document Structure The V4 MASTER workspace becomes the main V5 CATProduct document while: ● each geometrical SET becomes a CATPart, ● each DETAIL workspace becomes a CATPart, ● each GBN becomes a CATProduct, ● according to the selected option: ❍ each BNS becomes a CATPart, if Bundle segments is chosen ❍ all the BNSs of a GBN are stored in the same CATPart, if Multi-branchable bundle segments is chosen. The root document is a CATProduct named: .CATProduct. The V5 documents created by migration of V4 electrical models are named as follows: _ for example: TEST_MODEL1_ECP1.CATPart The CATPart documents resulting of DETAIL workspaces are instantiated as many times as there are DITTOS in the main document. In this V4 model, the SIC comes from a V4 library: each SIC instance (DITTO) has the same reference (DETAIL). In V5, the same structure is created: each connector is an instance of the CATPart. If a device has been created in V4, using more than one ditto to define its geometry, a CATPart will be created for each original detail. Library Migration Even though the electrical applications use catalogs, the migration batch migrates only the components in the models, not in the libraries. However it is possible to store the devices migrated from V4 model to a V5 catalog. Refer to How to migrate a V4 library. Note that it is recommended to limit the number of V4 devices to one hundred per model. Simultaneous Device Migration When migrating several models at a time, if they contain the same device, a CATPart will be generated for each V5 document (i.e. two models using the same SIC will be migrated as two V5 documents with two CATPart documents). V4 Integration Version 5 Release 14 Page 306 Known Restrictions About Bundle Segment Migration ● The rectangular section BNS is migrated as a circular section bundle segment. ● The V4 BNS created in BEND mode ends in a slightly different shape: The V4 BNS is shown in yellow, the corresponding V5 bundle segment is shown in red. ● ● The bundle segment shape in general might be different because of the algorithm differences. The number of points on which the curve is built also is different: the supports in CATIA V4 use three points while only two are used in CATIA V5. If the V4 BNS bend radius is smaller than the V4 BNS diameter, the bend radius value taken into account will be equal to the diameter. However, under certain circumstances, you may have a message informing you that the migration of such bundle segments leads to a "twisted configuration". The resulting V5 bundle segments have an unusable geometry. Bypass: In this case, modify the radius or the bend radius to be able to create the rib. About Device Migration Once the migration is performed, the following modifications have to be done manually to get the correct device behavior: ● Single Insert Connector ❍ On V5 single insert connectors, the Representation of the connector connection point and the Contact constraint correspond to the migrated point of the CPP of the V4 SIC. Coincidence and Orientation constraints must be added, using Electrical Library. V4 Integration ❍ ● Version 5 Release 14 Page 307 To connect a single insert connector to an equipment or a connector shell, a cavity connection point must be added to the single insert connector, using Electrical Library. Equipment ❍ To connect a connector or connector shell to an equipment, a cavity must be added to the equipment for each connector or connector shell, using Electrical Library. V4 Integration ❍ ● Version 5 Release 14 Page 308 To connect an equipment to a mounting equipment, a cavity connection point must be added to the mounting equipment, using Electrical Library. Connector Shell ❍ ❍ To connect a connector to a connector shell, a cavity must be added to the connector shell for each connector, using Electrical Library. To connect a connector shell to a mounting equipment or an equipment, a cavity connection point must be added to the mounting equipment or the equipment for each connector shell, using Electrical Library. V4 Integration Version 5 Release 14 Page 309 About Support Migration ● Multi-section supports are supported. However supports with multi-directional sections do not exist in CATIA V5. As a consequence, only the first created section will be linked to a bundle segment as well as all other sections that have the same direction. The bundle segments using other support section direction in the original V4 model are not linked to the support in the V5 document. About Session Migration For the time being, the V4 sessions (.session) are not migrated. This evolution is under development. Interoperability with ENOVIA V5 In the context of ENOVIA V5, you must first clear Use root context in assembly, which is located in the Part Infrastructure -> General -> External References frame. If not, the links will be created to the root of the assembly and it will not be possible to save the geometrical bundle in ENOVIA: By default, this option is selected. For more information, refer to the V4 Integration Documentation - User Tasks - Converting CATIA Version 4 Models into CATIA Version 5 in Batch Mode. V4 Integration Version 5 Release 14 Page 310 Frequently Asked Questions This section gives you information about questions you may have when migrating Electrical V4 data. Copy/Paste The electrical technology is not migrated The bundle segment migration mode is deactivated The geometry is partially migrated How to migrate a V4 library How to limit the number of CATPart documents CPP information is missing How multi-directional support are migrated Unusable geometry for V5 bundle segment: "twisted configuration" What happens when migrating at the same time several models containing the same device I cannot migrate the .session V4 document Copy/Paste Using Copy/Paste only copies the geometry and does not migrate the technology. Use the Migration Batch to take advantage of the electrical technology. The electrical technology is not migrated Check you have fill up the correct value (CATIE3DMigration) for the migration interface name. Note that if the spelling is incorrect, the Bundle Segment Migration Mode options will be grayed out in the Electrical tab. Refer to Methodology. The bundle segment migration mode is deactivated Check you have fill up the correct value (CATIE3DMigration) for the migration interface name. Refer to Methodology. V4 Integration Version 5 Release 14 Page 311 The geometry is partially migrated Check you have set up the correct option for the isolated mock-up solids. Refer to Methodology. How to migrate a V4 Library ● ● ● Place the V4 devices and/or supports in the model. Migrate the model: the CATProduct with the CATParts are created. the CATProduct is named: .CATProduct each CATPart is named: _.CATPart. Save the CATParts in V5 catalogs using Electrical Library. Note that it is recommended to limit the number of V4 devices to one hundred per model. How to limit the number of CATPart documents If you use the Bundle segments mode, a CATPart is created for each BNS in the model. Choose the Multibranchable bundle segments mode to reduce the number of documents and have all the bundle segment of the geometrical bundle in the same CATPart. Refer to Methodology. CPP information is missing The CPP is migrated as a point. Information is missing in V5 to ensure the connection. Refer to Migrating Step by Step... Multi-directional support Multi-section supports are supported. However supports with multi-directional sections do not exist in CATIA V5. As a consequence, only the first created section will be linked to the bundle segment as well as all other sections that have the same direction. The bundle segments using other support section direction in the original V4 model are not linked to the support in the V5 document. V4 Integration Version 5 Release 14 Page 312 Unusable geometry for V5 bundle segment After the migration, a message informed you that the migration of such bundle segment leads to a twisted configuration. In this case, modify the radius or the bend radius to be able to create the rib for the bundle segment. Refer to Reference Information. What happens when migrating at the same time several models containing the same device They are migrated as two/as many V5 reference documents. Refer to Reference Information. I cannot migrate the .session V4 document The V4 sessions (.session) are not migrated. Refer to Reference Information. V4 Integration Page 313 Version 5 Release 14 Migration of 2D Draw Elements and Views Accessing V4 Drawings within a model in CATIA V5 Copying 2D from CATIA Version 4 to CATIA V5 Migration of AUXVIEW2 Layout: Associativity with 3D Migration Converting V4 AUXVIEW2 Views to V5 Generative Drafting Views in Batch Managing Standards for Migration Mode V4 Integration Version 5 Release 14 Page 314 Accessing V4 Drawings within a Model in CATIA V5 This task shows you how to access to several drawings within the same model (*DRAFT tab) that you have opened in CATIA Version 5. You have the possibility to visualize, to overlay the Draft of one or several models upon a model's draft. This task will also show you how to visualize transparent views (AUXVIEW or AUXVIEW2 views) either in Hidden Line Removal (HLR) mode or in NHR mode. Accessing V4 Drawings Open the AUXVIEW2.model document and click the *DRAFT tab: 1. Select the View -> Add 2D Overlay command: Version 5 Release 14 V4 Integration The Add 2D Overlay dialog box is displayed: 2. Click the browse button in order to choose the models, the Draft of which will be visualized. 3. Select one or several models, for instance ANGLES.model and ARROW.model: Page 315 V4 Integration Version 5 Release 14 The selected documents appear in the Add 2D Overlay dialog box: 4. Click OK. You can visualize 3 Drafts within the same document: Page 316 V4 Integration Version 5 Release 14 5. Whenever you want to modify the document selection, click the Restore button Page 317 . This lets you remove/add models from/in the initial draft. ● ● Add2DOverlay is only applied to the current workspace. For instance, if the selected tab is *DRAFT, the *DRAFT contained in different models will be overlaid. But the other 2D workspaces' visualization is no longer guaranteed if there are Details in the model for instance. However, the 3D workspaces' visualization is not impacted and you can easily go back to the *MASTER tab: the visualization remains correct. If Add2DOverlay has been applied to one of the workspace, a warning is displayed whenever the user wants to go to another tab corresponding to a 2D workspace. This Warning is: Remember that, since overlay is not supported in Catia V5, you can only visualize models and no migration of links or data is available. Visualizing Transparent Views You can visualize Transparent Views either in Hidden Line Removal (HLR) mode or in NHR mode. Visualizing Transparent Views in HLR Mode V4 Integration Version 5 Release 14 Page 318 Open the CUBOID_HLR.model document. 1. Notice that the V4 model is in HLR representation mode. 2. Click the *DRAFT tab. You can notice that the HLR mode is applied to the transparent view (i.e. the same mode as that of the V4 model). Visualizing Transparent Views in NHR Mode Open the CUBOID_NHR.model document. 1. Notice that the V4 model is in NHR representation mode. 2. Click the *DRAFT tab. You can notice that the NHR mode is applied to the transparent view (i.e. the same mode as that of the V4 model). V4 Integration ● Version 5 Release 14 The HLR representation mode is applied to space elements on transparent views: SolidE, SolidM, Face, Surface, Volume and the Ditto 3D. The specific attributes of 3D elements (color, line-type, thickness), the Show/No-Show mode and 3D filters are taken into account. ● You can copy/paste as result transparent views with NHR or HLR representation. ● You can migrate transparent views with NHR or HLR representation in Batch Mode. ● Page 319 When the V4 model is saved in NHR representation mode, the tubing elements are not displayed. This includes the harness elements. V4 Integration Version 5 Release 14 Page 320 Copying 2D from CATIA Version 4 to CATIA Version 5 The following task shows how drafting data is pasted As Result from an existing Version 4 model to a new Version 5 document. Of course, you can also insert the V4 data into an existing Version 5 document alongside existing V5 drafting data by using the same procedure. The following data can be copied from CATIA Version 4 to CATIA Version 5: ● circles ● dittos, symbols (exploded in V5 geometry) ● ellipses ● points ● lines ● parabolas ● hyperbolas ● curves ● AUXVIEW2 views As Result i.e. as geometry only with no associativity with 3D ● V4 texts are migrated as V5 texts ● V4 dimensions are migrated as V5 dimensions V4 text thickness is migrated in V5 texts according to the following parameters: ● if the thickness of V4 texts is superior to 0.2mm, V5 texts are displayed with a bold style, ● if the thickness of V4 texts is inferior or equal to 0.2mm, V5 texts are displayed with a regular style. Additionally, the following V3 data can now be migrated directly from CATIA Version 3 to CATIA Version 5: ● ● V3 texts are migrated as V5 texts. V3 dimensions are migrated as graphical elements. However, you can migrate V3 dimensions as V5 dimensions by using the following methodology: migrate V3 dimensions to V4 first using the V4 process, and then migrate these to V5. Refer to Managing standards for V4 to V5 migration of 2D Draw elements for more information on what data can be copied from V4 to V5 and on how to do this. Version 5 Release 14 V4 Integration Page 321 Open the DraftingInterop.model document and select the DRAFT tab. 1. Open a CATDrawing document. 2. In the specification tree or geometry area where the Version 4 drawing is displayed, select the view you wish to copy into CATIA Version 5. You can select several views if you prefer. 3. Put the view(s) you have selected in the clipboard. To do this, either click the Copy icon select the Edit->Copy command or select the , Copy command in the contextual menu. 4. In the specification tree of the CATIA Version 5 CATDrawing document, select the appropriate sheet. 5. Now either click the Paste icon , select the Edit->Paste command or select the Paste command in the contextual menu. This operation recovers the view previously put in the clipboard. 6. You may want to click the Fit All In icon to fit all data in the window. Notice that the toolbars change depending on whether a CATIA Version 4 model or a CATIA Version 5 document is selected. The result should look something like this (using the Window -> Tile Horizontally command): V4 Integration Version 5 Release 14 Page 322 When copying V4 drawing data to V5, bear the following in mind: ● Whatever the standard of the V4 view was prior to being copied into CATIA Version 5, once in V5 its standard is that selected when you open the CATDrawing document. ● ● ● The smallest unit that you can copy is the view. All the elements that go to make up this view are included in the copy. In the V5 Drafting mode Working Views (Edit -> Working Views), the copy described above creates a V5 view with the same name as in V4. In the V5 Drafting mode Background (Edit -> Background), the V4 elements are copied into the background view of the V4 view. The migration of V4 drawing data to a V5 document generates a report (.rpt) file named after the model migrated: ❍ on Windows: in C:\Documents and Settings\username\Local Settings\Application Data\DassaultSystemes\CATReport ❍ on UNIX: in /u/users/username/CATReport Version 5 Release 14 V4 Integration Page 323 This reports contains different types of information regarding the migration results: ❍ location and name of the input and output files, ❍ kind of migration performed (e.g. V4 to V5 CATDrawing), ❍ mode of migration performed (AS SPEC or AS RESULT) ❍ ❍ ● ● ● ● status of migration for each V4 element: - Correctly/OK: migration successful - KO: migration failed - NOT: migration could not be performed for lack of a CATIA V5 equivalent V4 attributes of V4 elements. If, when importing 2D geometry, you want to create circle centers and curve end points, select Tools->Options, select the Drafting category in the left-hand column and click the V4->V5 tab. In the Geometry Import section of the window that appears, check the Create centers and end points box. If you want to define dimension conversion as a graphic, select the Tools->Options... command, select the Drafting category in the left-hand column and click the V4->V5 tab. In the Dimension Conversion Mode section of the window that appears, check the Convert dimension as a graphic box. The V4 structure of Detail/Ditto is migrated in a V5 structure of Detail (2D component reference) /Ditto (2D component instance). If you want to use the previous behavior (Explode Ditto) select Tools -> Options to specify the conversion mode of Dittos. You can copy/paste as result V4 transparent views with NHR or HLR representation (the projection mode is retrieved from the browsing). V4 Integration Version 5 Release 14 Page 324 Migrating AUXVIEW2 Views: Associativity with 3D Migration This task shows you how to convert the specifications of an AUXVIEW2 View into a Generative Drafting View. It is possible to copy/paste AS RESULT V4 Drafting entities into CATIA V5, but this functionality allows you to copy/paste AS SPEC an AUXVIEW2 View into CATIA V5. As a consequence, you can get a V5 Generative Drafting View. AUXVIEW2 Defaults: In AUXVIEW2 DEFAULT, a number of dress-up parameters on specific elements (clipping edges, cut edges, breakout limit) are pre-defined. Refer to Managing AUXVIEW2 Defaults for Migration for information on what you need to do before migrating AUXVIEW2 views from V4 to V5 to ensure that your migration results will be equivalent to your AUXVIEW2 defaults. 3D Reference Document: V4 AUXVIEW2 Views reference 3D models. V5 Generative Drafting Views also reference a CATPart or a CATProduct. Therefore, prior to migrating AUXVIEW2 Views, you need to convert 3D models into CATIA V5 parts or products to have this reference available. When the V4 Drawing is referencing several 3D models, you need to migrate all the models into CATParts and create a CATProduct referencing these CATParts. During the V4 To V5 Migration (AS SPEC), different types of views are taken into account: ● AUXVIEW2 Views are converted into Generative Drafting Views. ● AUXVIEW Views converted into Interactive Drafting Views. The behavior is the same when you copy/paste (AS RESULT) these entities. Transparent Views are converted into Interactive Drafting Views. Moreover, non-generative geometry will be migrated AS RESULT. That is to say, an AUXVIEW2 View containing interactive entities such as a line, a circle,... will be converted into a line, a circle. And, dimensions and texts will be also migrated AS RESULT in the same way you can copy/paste (AS RESULT) these elements in CATIA V5. For more information about the 3D Migration, please refer to Copying 3D from CATIA Version 4 to CATIA Version 5. 1. Open the AUXVIEW2.model document and the AUXVIEW2.CATPart document. The latter will serve as the 3D reference document for the V5 Drawing. 2. In the AUXVIEW2.model document, click the *DRAFT tab (projection view): Version 5 Release 14 V4 Integration 3. Click the New Page 325 icon and select Drawing from the New dialog box, to open a .CATDrawing document. 4. In the New Drawing dialog box, click OK. 5. In the AUXVIEW2.model document, right-click *DRAFT in the specification tree, and select Copy from the contextual menu. 6. Activate the Drawing document, and select the Edit-> Paste Special command. The Paste Special dialog box is displayed. Choose the paste CATIA_SPEC option. V4 Integration Version 5 Release 14 Page 326 Right after you select CATIA_SPEC, a dialog box is displayed in which you can define the 3D Reference necessary for the V5 Drawing. This dialog box contains two sections: ● ● a list of all the CATParts (for instance, AUXVIEW2.CATPart) and CATProducts currently open in the CATIA V5 session. a Browse button giving access to a File/Open dialog box to let you specify a 3D reference other than the currently open CATParts or CATProducts. 7. Select the AUXVIEW2.CATPart document and click OK. 8. Click OK in the Paste Special dialog box. The Views are generated in the CATDrawing: Associativity: Only SPECIFICATIONS of the Views are migrated; therefore, the profiles of Section Views and Detail Views are not associative to 3D. V4 Integration Page 327 Version 5 Release 14 Details about V4 Drafting Entity conversion: The following V4 View Parameters are migrated AS SPEC: DRAW Elements V4 to V5 Migration AS SPEC Views AUXVIEW2 View Generative Drafting View AUXVIEW View Interactive Drafting View View Types Projection Projection Section Cut / Section View Section Cut / Section View Detail View Detail View Auxiliary View Auxiliary View Specific Behavior of the View Simple Breakout Simple Breakout Breakout Backclipping View Parameters Hidden Lines Hidden Lines Generation of Axis Generation of Axis Fillets Fillets Same/Standard 3D Color Inheritance View Name Representation View Name Representation Callout Representation Callout Representation The following specifications are not yet migrated AS SPEC: ● Specific Behavior of the Views ❍ Unspec Breakout ● ❍ Filter on Views: UnCut/UnUse/UnHlr ❍ Filter on Layer, Box, View View Parameters: ❍ Representation Types of Hidden Lines ❍ Pattern Representation ❍ Lock of the generated geometry ❍ Old generated elements: Scratch/choose Layer ❍ Autolayering V4 Integration Version 5 Release 14 Page 328 However, you can migrate the following specifications using the migration batch (for more information, refer to Converting V4 AUXVIEW2 Views to V5 Generative Drafting Views in Batch Mode): ● ● Specific Behavior of the Views ❍ Filter on Views: UnCut/UnUse/UnHlr View Parameters: ❍ Pattern Representation Migration report: The migration of V4 drawing data to a V5 document generates a report (.rpt) file named after the model migrated: ● ● on Windows: in C:Documents and Settings/username/Local Settings/Application Data/DassaultSystemes/CATReport on UNIX: in /u/users/username/CATReport This reports contains different types of information regarding the migration results: ● location and name of the input and output files, ● kind of migration performed (e.g. V4 to V5 CATDrawing), ● migration mode performed (AS SPEC or AS RESULT) ● status of migration for each V4 element: - Correctly/OK: migration successful - KO: migration failed - NOT: migration could not be performed for lack of a CATIA V5 equivalent. Page 329 Version 5 Release 14 V4 Integration Converting V4 AUXVIEW2 Views to V5 Generative Drafting Views in Batch Mode This task shows you how to convert CATIA Version 4 AUXVIEW2 views to CATIA Version 5 Generative Drafting views with full 2D/3D associativity (i.e. AS SPEC migration). About AUXVIEW2 Defaults In AUXVIEW2 DEFAULT, a number of dress-up parameters on specific elements (clipping edges, cut edges, breakout limit) are pre-defined. Refer to Managing AUXVIEW2 Defaults for Migration for information on what you need to do before migrating AUXVIEW2 views from V4 to V5 to ensure that your migration results will be equivalent to your AUXVIEW2 defaults. About AUXVIEW2 view conversion in batch mode There are a few things you need to remember when converting AUXVIEW2 views in batch mode: ● ● V4 SPACE models must be converted before DRAW models in order to ensure associativity between the V5 CATProduct/ CATPart and CATDrawing documents. You can either convert V4 SPACE models in a session, and then convert DRAW models in a later session, or you can convert both V4 SPACE and DRAW models during the same migration session. For the purpose of this scenario, you will learn how to convert the models during the same session. When converting both SPACE and DRAW models during the same session, pay attention to the order in which you select the documents to convert: the SPACE models must be listed first in the Migration Batch dialog box, before the DRAW models. This ensures that they are converted first. SPACE models will be migrated first and converted to CATPart and/or CATProduct document(s). The CATDrawing is generated from the CATPart or from the CATProduct. The various possibilities are listed in the table below: In the case of... The SPACE element(s) is(are) migrated first and converted to... The CATDrawing is then generated from... V4 SPACE and DRAW elements contained in the same model A CATPart or CATProduct document This CATPart or CATProduct A V4 DRAW model linked to a single SPACE model A CATPart or CATProduct document This CATPart or CATProduct V4 DRAW model linked to several SPACE models CATPart documents; a CATProduct document containing these CATPart documents is also created automatically The CATProduct (and not from the CATPart documents) For more information on converting SPACE data and on batch migration, see Converting CATIA Version 4 Models into CATIA Version 5 in Batch Mode. For more information on AS SPEC migration of AUXVIEW2 views, see Migration of AUXVIEW2 views. You will practice with three V4 SPACE documents: CUBE-0-100.model, CYLINDRE.model and SPHERE.model, and with a V4 DRAW document: DRAW-CUBE-CYL-SPHERE.model. Go to Tools -> Options -> General -> Compatibility, and click the V4 Data Reading tab. Make sure the Open in Light Mode: 2D data are not taken into account option is unselected. Additionally, select the Convert SPACE and DRAW conversion mode and the As SPEC format. V4 Integration Version 5 Release 14 Page 330 Before launching the batch tool, you have to make sure that your environment is correctly set up. On NT, the Batch environment is installed during CATIA's installation. On UNIX, you have to set up this environment before starting the session. For more information about this, see Starting a session on UNIX in the Infrastructure User's Guide. 1. Launch the Migration Batch by entering the appropriate command, depending on whether you are on UNIX or on NT: ● On UNIX, enter: catstart -run "CNEXT -batch -e CATV4ToV5Migration" ● On Windows, enter: CNEXT -batch -e CATV4ToV5Migration 2. Click the Browse File button to launch the File Selection dialog box. 3. Select the V4 SPACE documents: CUBE-0-100.model, CYLINDRE.model and SPHERE.model, and click Open. 4. Click the Browse File button to launch the File Selection dialog box again. 5. This time, select the V4 DRAW document: DRAW-CUBE-CYL-SPHERE.model, and click Open. The SPACE models are listed before the DRAW model in the Migration Batch dialog box. V4 Integration Version 5 Release 14 Page 331 V4 Integration Version 5 Release 14 Page 332 6. Optionally, click the Options button to define your batch options. On the Migration Batch tab, you can select a .CATDrawing document in the Initial Drawing path field: this drawing will serve as a template, and the standard used by this document will be used during the migration. If you leave this field blank, the standard used by default during the migration will be the last one you used when creating a drawing. 7. Optionally, click the browse button next to the Target Directory field to specify the name of the directory in which the data will be created (by default the data are created in the directory which contains the first selected V4 document). 8. Perform Specification Check on the V4 documents. For more information, see Checking V4 Model Data Before Copying It to V5 : Interactive Checker. 9. Select the Migrate option in order to convert V4 documents to V5 documents. 10. Leave the Run Local option selected to run the migration batch locally on your computer. Your migration batch parameters are now defined. 11. Click the Save button to specify where you want to save your batch parameters. A dialog box is displayed. 12. Browse to the directory in which you want to save the batch parameters file, specify a file name in the appropriate field, and click Save. Your parameters are saved in an xml file. 13. Click Run to run the batch immediately. A progress bar appears. When the migration process is over, the migration report is displayed in another dialog box. The message is OK, which means that the .models and their components can be converted to CATIA V5. You can double-click the line of your choice for more information. V4 Integration Version 5 Release 14 Page 333 14. Optionally, save the migration report as a text file by clicking the Save As Text button. 15. Close the Migration Report dialog box, and then the Migration Batch dialog box. 16. You can now access the converted documents in CATIA V5. The V4 AUXVIEW2 views have been converted to V5 Generative Drafting views, and the CATDrawing document is fully associative with the CATProduct document. V4 Integration Page 334 Version 5 Release 14 About Batch Migration of DRAW data: When a model contains DRAW data, they are migrated as a unique document: a CATDrawing. Some entities undergo a few changes during the V4 to V5 conversion: ● V4 DRAFT -> V5 Sheet ● V4 Detail -> V5 Detail Sheet ● V4 Views -> V5 Views In the Batch Mode, all Draw and Detail workspaces are migrated in CATIA V5. On the contrary, if you Copy / Paste a Draft or a View interactively, only referenced Details are migrated. Details about V4 Drafting Entity conversion: The following V4 View Parameters are migrated AS SPEC using the migration batch: DRAW Elements V4 to V5 Migration AS SPEC Views AUXVIEW2 View Generative Drafting View AUXVIEW View Interactive Drafting View View Types Projection Projection Section Cut / Section View Section Cut / Section View Detail View Detail View Auxiliary View Auxiliary View Specific Behavior of the View Simple Breakout Simple Breakout Filter on Views: UnCut/UnUse/UnHlr Filter on Views: UnCut/UnUse/UnHlr Backclipping Breakout View Parameters Hidden Lines Hidden Lines Generation of Axis Generation of Axis Fillets Fillets Same/Standard 3D Color Inheritance View Name Representation View Name Representation Callout Representation Callout Representation Pattern Representation Pattern Representation V4 Integration Version 5 Release 14 Page 335 To make sure that you obtain proper results when migrating UnCut/UnUse/UnHlr Filter on Views, make sure that the A CATPart by Solid option is selected in Tools -> Options -> General -> Compatibility -> V4 Data Reading tab. The following specifications are not yet migrated AS SPEC: ● Specific Behavior of the Views ❍ Unspec Breakout ❍ ● Filter on Layer, Box, View View Parameters: ❍ Representation Types of Hidden Lines ❍ Lock of the generated geometry ❍ Old generated elements: Scratch/choose Layer ❍ Autolayering V4 Integration Version 5 Release 14 Managing Standards for Migration Before You Begin Dimension Numerical Display Dimension Tolerances Dimension and Text Properties Arrows Frames & Balloons Fonts Line Thickness Filters Line Types Pattern Cells Page 336 V4 Integration Version 5 Release 14 Page 337 Before You Begin When a V4 2D Model is migrated from V4 to V5, the elements that referenced 2D standards in V4 (dimensions, texts, etc.) sometimes need to reference 2D standards in V5. V5 standard parameters need to be properly defined (as in V4) in order for the migration result to be equivalent to the original V4 2D Model. This section explains the methodology for managing V5 standards for V4 to V5 migration of 2D Draw elements, based on the existing V4 standards. You will learn: ● how the migration of 2D Draw elements (dimensions, texts, arrows, lines and patterns) is carried out, ● and what you need to pre-define concerning the V5 standard parameters before starting the migration process. For detailed information regarding the mapping of V4 and V5 2D Standard parameters, refer to V4V5_Standards_Mapping_V05.pdf. This document is available on the PDF CD-ROM shipped with CATIA documentation, in the catpdfwhitepaper folder. About V4 to V5 Standards Management When managing standards for V4 to V5 migration, you will need to bear the following information in mind: ● As in V4, it is a CATIA administrator who manages V5 standards definition. ● In V5, standards are defined via the Standards Editor: Tools -> Standards, Drafting category. ● ● ● A complete standard definition is stored in a XML file. For example, ANSI.xml defines the ANSI standard. In V4, a .Model can mix different standards whereas in V5, a .CATDrawing is mono-standard: when a new .CATDrawing is created, only one standard defined in the Standards Editor (and stored in a single XML file) can be referenced and is embedded in the .CATDrawing. Whatever the standard of the V4 view was prior to being copied into CATIA Version 5, once in V5, the standard is that selected when you open the .CATDrawing document. For more information, refer to the Administration Tasks chapter in the Interactive Drafting User's Guide. Referencing the Project File (PRJ) Before starting the migration process, you need to reference in V5 the project file (PRJ) used to create the V4 2D model. To do this, go to Tools -> Options -> General -> Compatibility -> V4/V5 Infrastructure tab, and fill in the PROJECT File Patch and DLNAME fields. The PRJ files must be renamed on UNIX before being installed on a Windows system: all the "±" (plus or minus sign) must be replaced by "_" (underscore) in PRJ filenames. For example, my±filename.prj on Unix must be renamed my_filename.prj V4 Integration Version 5 Release 14 Page 338 About 2D Migration Methodology The methodology which is applied when migrating 2D Interactive and 2D Generative drawings is shown in the charts below. V4 to V5 2D Interactive Drawing Migration V4 to V5 2D Generative Drawing Migration V4 Integration Version 5 Release 14 Page 339 Standard Parameters You can manage the following V5 standard parameters in preparation for V4 to V5 migration of 2D Draw elements: Dimensions Numerical Display Dimensions Tolerances Dimensions & Texts Properties Arrows (Markup) Frames & Balloons V4 Integration Fonts Line Thickness Filters Version 5 Release 14 Page 340 Version 5 Release 14 V4 Integration Page 341 Dimension Numerical Display The following task explains the methodology for managing V5 Dimension Numerical Display standards for V4 to V5 migration. You will learn: ● how the migration of Dimension Numerical Display is carried out, ● and what you need to pre-define concerning the V5 standard parameters before starting the migration process. V4 Numerical Displays are known as Value Display Formats in V5. Migration mechanism The migration engine tries to map the name of the V4 Numerical Display used by the dimension to migrate to the name of a V5 Value Display Format: ● ● If a V5 Value Display Format bearing the same name as the V4 Numerical Display is found, then this Value Display Format will be applied to the new dimension in V5. If not, all existing V5 Value Display Formats will be scanned and the closest description will be used. However, the result will not be exactly the same. Pre-definition There are two possibilities: ● ● If you used a standard PRJ (delivered by DS), you do not have to customize anything in particular before migrating the V4 2D Models. If you created a specific Numerical Display in V4, you need to re-create it in V5. If you don't, dimensions which use this Numerical Display will not be mapped during the migration and the result will be different than in V4. In V4, the Numerical Display (including all its parameters and values) is defined in the DRWSTD function, under Annotations -> Description -> Visualization -> Numerical Display. In V5, the Value Display Format is defined in the Standards Editor, under Standard -> name_of_standard -> ValueFormats. Some of the pre-defined Value Display formats which are provided by default in V5 cannot be modified: for example, NUMM.DIMM, DISTINCH, etc. Since they cannot be edited, these formats do not appear in the Standards Editor. For detailed information regarding the mapping of V4 and V5 Numerical Display parameters, refer to the "Dimensions: Numerical Display" section in V4V5_Standards_Mapping_V05.pdf. This document is available on the PDF CD-ROM shipped with CATIA documentation, in the catpdfwhitepaper folder. Version 5 Release 14 V4 Integration Page 342 Dimension Tolerances The following task explains the methodology for managing V5 Dimension Tolerance standards for V4 to V5 migration. You will learn: ● how the migration of Dimension Tolerances is carried out, ● and what you need to pre-define concerning the V5 standard parameters before starting the migration process. One has to distinguish between single tolerances and multi-tolerances. Single Tolerances Migration mechanism The migration engine tries to map the name of the V4 Tolerance used by the dimension to migrate to the name of a V5 Tolerance Format: ● ● If a V5 Tolerance Format bearing the same name as the V4 Tolerance is found, then this Tolerance will be applied to the new dimension in V5. If not, all existing V5 Tolerance Formats will be scanned and the closest description will be used. However, the result will not be exactly the same. Pre-definition There are two possibilities: ● ● If you used a standard PRJ (delivered by DS), you do not have to customize anything in particular before migrating the V4 2D Models. If you created a specific Tolerance in V4, you need to re-create it in V5. If you don't, dimensions which use this Tolerance will not be mapped during the migration and the result will be different than in V4. In V4, the Tolerance (including all its parameters and values) is defined in the DRWSTD function, under Annotations -> Description -> Visualization -> Tolerance. In V5, the Tolerance Format is defined in the Standards Editor, under Standard -> name_of_standard > ToleranceFormats. ● ● Most of the pre-defined Single Tolerance formats which are provided by default in V5 cannot be modified: for example, TOL_NUM2, ISONUM, etc. Since they cannot be edited, these formats do not appear in the Standards Editor. The detailed mapping between V4 and V5 Tolerance parameters is explained in 2D Standard Mapping for V4 to V5 migration. V4 Integration Version 5 Release 14 Page 343 Multi-Tolerances In V4 as well as in V5, two default Multi- Tolerances are available: MTL_A1N2 and ISOCOMB. However, whereas it is possible to create user-defined tolerances in V4, this is not the case in V5. Migration mechanism ● ● If a dimension has been created in V4 using one of the 2 default Multi-Tolerances, its specifications will be migrated and the V5 definitions will be used. If a dimension has been created in V4 using a user-defined Multi-Tolerance, it is not migrated and can only be seen in graphic mode. Pre-definition In V4, user-defined multi-tolerances are defined in the DRWSTD function, under Annotations -> Description -> Create -> Multi-Tolerancing. In V5, by default, the numerical definition of a multi-tolerance is associative to the dimension value (in which case it is automatically updated when the dimension value is changed). This was not the case in V4. As a result, if you want multi-tolerances to be migrated to V5 with the same value as in V4, you need to make the numerical definition of a multi-tolerance not associative to the dimension value. To do this, in the Standards Editor, under Standard -> name_of_standard -> Dimensions, set the DIMTolMultiAuto parameter to No. In V5, it is not possible to create user-defined multi-tolerances. As for the two default Multi-Tolerances (MTL_A1N2 and ISOCOMB), since they cannot be edited, these formats do not appear in the Standards Editor. For detailed information regarding the mapping of V4 and V5 Dimension Tolerance parameters, refer to the "Dimensions: Tolerancing" section in V4V5_Standards_Mapping_V05.pdf. This document is available on the PDF CD-ROM shipped with CATIA documentation, in the catpdfwhitepaper folder. Version 5 Release 14 V4 Integration Page 344 Dimension and Text Properties The following task explains the methodology for managing V5 Dimension and Text Properties for V4 to V5 migration. You will learn: ● how the migration of Dimension and Text Properties is carried out, ● and what you need to pre-define concerning the V5 standard parameters before starting the migration process. Migration mechanism During V4 to V5 migration, a number of V4 dimension and text properties are migrated as V5 properties and keep their V4 value, while others are re-defined as V5 standard embedded in the new V5 .CATDrawing. The detailed mapping of these values is explained in 2D Standard Mapping for V4 to V5 migration. Pre-definition If you used a standard PRJ (delivered by DS), you do not have to customize anything in particular before migrating the V4 2D Models. In V4, dimension and text properties can be modified with the DRWSTD, DIMENS2 and TEXTD2 functions: ● ● Text leaders and dimension symbols are defined by the same parameters, in the DRWSTD function, under Annotations -> Description -> Symbol. For those dimensions whose parameters have been changed in V4 through the DIMENS2 and TEXTD2 functions, the V5 dimension or text result can differ if the modified parameter is only defined as a standard parameter in V5. In V5, most parameters (dimension lines, symbols, text leaders, etc.) are defined in the Standards Editor, under Standard -> name_of_standard -> Dimension. A number of specific text leader parameters are defined in the Standards Editor, under Standard -> name_of_standard -> Annotation -> Text. For detailed information regarding the mapping of V4 and V5 standard dimension and text parameters, refer to the "Dimensions & texts properties" section in V4V5_Standards_Mapping_V05.pdf. This document is available on the PDF CD-ROM shipped with CATIA documentation, in the catpdfwhitepaper folder. V4 Integration Version 5 Release 14 Page 345 Arrows The following task explains the methodology for managing V5 arrow/symbol standards for V4 to V5 migration. You will learn: ● how the migration of arrows is carried out, ● and what you need to pre-define concerning the V5 standard parameters before starting the migration process. V4 arrows are known as symbols in V5. Migration mechanism During the migration from V4 to V5, the new V5 symbol is re-defined as a V5 standard embedded in the target V5 .CATDrawing. Pre-definition In V4, arrows are defined in the Arrow function, under Markup -> Arrow. In V5, symbols are defined in the Standards Editor, under Standard -> name_of_standard -> DressUp -> Symbols. Version 5 Release 14 V4 Integration Page 346 Frames & Balloons The following task explains the methodology for managing V5 frame and balloon standards for V4 to V5 migration. You will learn: ● how the migration of frames and balloons is carried out, ● and what you need to pre-define concerning the V5 standard parameters before starting the migration process. Migration mechanism Whereas you can define several sizes for a given type of frame in V4, for the moment, it is only possible to define one size per type of frame in V5. During the migration, this pre-defined size will be used. Pre-definition In V4, frames are defined in the DRWSTD function, under Annotations -> Description -> Visual TN -> Framing. In V5, frame and balloon sizes are defined in the Standards Editor, under Standard -> name_of_standard -> Frames. Version 5 Release 14 V4 Integration Page 347 Fonts The following task explains the methodology for managing V5 Font standards for V4 to V5 migration. You will learn: ● how the migration of fonts is carried out, ● and what you need to pre-define concerning the V5 standard parameters before starting the migration process. Migration mechanism The migration engine maps V4 and V5 fonts. This mapping is managed by a file called V4FontInteroperability. Pre-definition There are two possibilities: ● ● If you used the standard V4 fonts, you do not have to customize anything in particular before migrating the V4 2D Models. If you created specific fonts in V4, before starting the migration, you need to install the V4 FONT and FONTDATA files in the V5 installation folders, and you need to reference the V4FontInteroperability file. Here is what you need to do: 1. If you have not migrated the V4 FONDATA files to FONT and FONTCODE files, do so in V4 using the CATFONT utility. 2. Install the V4 FONT files in installation_folder \resources\fonts\Stroke. 3. Install the FONTCODE files in installation_folder\reffiles\NLS\fontcode. 4. Rename the FONTCODE files using the following rule: XXXX.fontcode (where XXXX.fontcode represents the V4 font code file) should be renamed FCUSERn.fontcode (where n represents the increment, 16 being the maximum number). 5. Edit the V4FontInteroperability file in installation_folder\resources\fonts to add your V 4 FONTLIB names to the list. This file maps to a V 4 FONTLIB name, the FONT and FONT CODE that are associated with it. The example below shows two fonts (ABBK and TIME) added to the V4FontInteroperability file with their corresponding font code: V4 Integration Version 5 Release 14 Page 348 Version 5 Release 14 V4 Integration Page 349 Line Thickness The following task explains the methodology for managing V5 line thicknesses for V4 to V5 migration. You will learn: ● how the migration of line thicknesses is carried out, ● and what you need to pre-define concerning the V5 standard parameters before starting the migration process. Migration mechanism When a line is migrated from V4 to V5, the closest existing V5 thickness will be taken into account to create the new line. Therefore, the V4 existing thicknesses have to be re-defined in V5. Pre-definition You need to re-create line thicknesses in V5, based on the existing V4 line thicknesses. In V4, line thicknesses are defined in the STANDARD function, under DRAW ELT. In V5, line thicknesses are defined in the Standards Editor, under Standard -> name_of_standard -> LineThickness. The following fields should be referenced: ● Availability (defines if the line is available to create new elements), ● Thickness for browsing (in pixels), ● Thickness for plotting (in mm). V4 Integration Version 5 Release 14 Page 350 Filters The following task explains the methodology for managing V5 filters (layer filters, view filters and ditto filters) for V4 to V5 migration. For each type of filter, you will learn: ● how the migration of filters is carried out, ● and what you need to pre-define concerning the V5 standard parameters before starting the migration process. Layer Filters Migration mechanism Layers are migrated from V4 to V5 but regarding filters, only the visualized elements are migrated: the filter configuration has to be defined in V4 prior to migrating the 2D model. V4 browsing with V4 browsing with proper all the layers configuration Result after migration Definition Once the layers have been migrated, you can recreate the filters structure in V5. You can define the filters (and also the layers) in in the Standards Editor. Select the General category, and the CATDftStdlayersAndFilters.xml file. Users can create new layer filters, using Tools -> Visualization Filters. Users can also create new layers using the Other Layers option available from the Layer list in the Graphic Properties toolbar. View Filters Migration mechanism During the migration, only the visualized elements are migrated. V4 Integration V4 browsing with V4 browsing with proper all the layers on configuration the views Version 5 Release 14 Page 351 Result after migration Pre-definition You need to define the filter configuration in V4 before migrating the 2D model. Ditto Filters Migration mechanism In V5R10, it is possible to migrate ditto filters either in a structural mode or in a visualization mode. If the structural mode is used, a multiple details structure is created: one detail is generated per ditto filter. The migration instantiates the detail as is visualized in V4 as the ditto to be seen. The visualization mode migrates only the visualized elements in the master without the detail / dittos structure. Structural mode The dittos structure is kept but not the filters structure. Visualization mode The visualized elements are migrated but the dittos are exploded. V4 browsing with proper configuration Version 5 Release 14 V4 Integration Page 352 Line Types The following task explains the methodology for managing V5 Line Type standards for V4 to V5 migration. You will learn: ● how the migration of line types is carried out, ● and what you need to pre-define concerning the V5 standard parameters before starting the migration process. Migration mechanism The following mapping is used to migrate a line type (line font) from V4 to V5 (n represents the line type number): General rule V4 line type n = V5 line type n Exception An exception applies when n equals 6 or 7: V4 line 6 = V5 line 7 V4 line 7 = V5 line 6 This mapping is also used when browsing V4 models in V5. Pre-definition You need to reference the V5 user-defined line types in V5 as there were in V4. In V4, line types are defined in the STANDARD/LINETYPE function. In V5, when migrating a V4 model, it is the lines defined in the Standards Editor, under Standard -> name_of_standard -> Linetypes which are referenced. However, when browsing a V4 model, it is the lines defined in Tools -> Options -> General -> Display -> Linetypes tab which are referenced. Version 5 Release 14 V4 Integration Page 353 Pattern Cells The following task explains the methodology for managing V4 pattern cells to V5 image patterns. You will learn: ● how the migration of pattern cells is carried out, ● and what you need to pre-define concerning the V5 standard parameters before starting the migration process. Migration mechanism The migration engine needs to map the name of the V4 pattern cell to the name of a V5 image pattern. Pre-definition In V4, each pattern cell is identified by its name. In V5, image patterns are defined in the Standards Editor, under Standard -> name_of_standard -> Patterns -> Image. Make sure that the name you enter for the pattern in the Name field corresponds exactly to the name of the V4 pattern cell. Do not forget to specify the file that you want to use for this image pattern (use the Browse button). V4 Integration Version 5 Release 14 Page 354 Managing AUXVIEW2 Defaults for Migration When migrating AUXVIEW2 views from V4 to V5, there are several things you need to do to ensure that your migration results will be equivalent to your AUXVIEW2 defaults. What you need to do depends on whether you want to use generative view styles or settings (defined via Tools -> Options). ● Customize V5 generative view styles XML files: these make it possible to customize the appearance and behavior of a V5 generative view via a set of pre-defined parameters and options, and customize V4 to V5 DRAW settings via Tools -> Options -> Compatibility. OR ● Customize V5 Drafting settings via Tools -> Options -> Mechanical Design -> Drafting. Generative view styles offer more customization possibilities than settings. This section explains the methodology for managing AUXVIEW2 defaults for V4 to V5 migration. About AUXVIEW2 Defaults Management for V4 to V5 Migration When managing AUXVIEW2 defaults for V4 to V5 migration, you will need to bear the following information in mind: ● ● ● ● ● It is a CATIA administrator who manages V5 generative view styles definition. In V5, generative view styles are defined via the Standards Editor: Tools -> Standards, generativeparameters category. A complete standard definition is stored in a XML file. For example, DefaultGenerativeStyle.xml defines the default Drafting generative view styles. In V5, a .CATDrawing uses only one generative view style: when a new .CATDrawing is created, only one generative view style defined in the Standards Editor (and stored in a single XML file) can be referenced and is embedded in the .CATDrawing. Whatever the defaults of the AUXVIEW2 view were prior to being copied into CATIA Version 5, once in V5, they are those defined either in the selected generative view style or in the settings (Tools -> Options -> Mechanical Design -> Drafting). For more information, refer to the Administration Tasks chapter and to the Customizing chapter in the Generative Drafting User's Guide. Referencing the Project File (PRJ) Version 5 Release 14 V4 Integration Page 355 Before starting the migration process, you need to reference in V5 the project file (PRJ) used to create the V4 2D model. To do this, go to Tools -> Options -> General -> Compatibility -> V4/V5 Infrastructure tab, and fill in the PROJECT File Patch and DLNAME fields. The PRJ files must be renamed on UNIX before being installed on a Windows system: all the "±" (plus or minus sign) must be replaced by "_" (underscore) in PRJ filenames. For example, my±filename.prj on Unix must be renamed my_filename.prj Preparing for AUXVIEW2 Migration with Generative View Styles The procedure below describes what you need to do before migrating AUXVIEW2 views from V4 to V5 if you use generative view styles: 1. Start a V5 session. Note: step 2 must be performed with a session running in administrator mode, but the following steps can be performed with a session running in normal mode. 2. Customize the V5 generative view styles XML file that you want to use when migrating AUXVIEW2 views from V4 to V5. For more information on customizing generative view styles, refer to the Administration Tasks chapter in the Generative Drafting User's Guide. For detailed information regarding the parameters that you need to modify in the generative view styles XML files, refer to DefaultAUX2V4ToV5withGVS.pdf. This document is available on the PDF CD-ROM shipped with CATIA documentation, in the catpdfwhitepaper folder. 3. Go to Tools -> Options -> Mechanical Design -> Drafting -> Administration tab and make sure that the Prevent generative view style creation setting is not selected. 4. Go to Tools -> Options -> General -> Compatibility -> V4/V5 DRAW tab, and, from the Default generative view style list, select the XML file that you just customized to specify that this generative view style should be used when migrating AUXVIEW2 views from V4 to V5. V4 Integration Version 5 Release 14 Page 356 Preparing for AUXVIEW2 Migration with Settings The procedure below describes what you need to do before migrating AUXVIEW2 views from V4 to V5 if you use settings: 1. Start a V5 session (you do not necessarily need to be running the session in administrator mode). 2. Go to Tools -> Options -> Mechanical Design -> Drafting and on the various tabs, define the settings that you want to be applied when migrating AUXVIEW2 views from V4 to V5. For detailed information regarding the V5 Drafting settings that you need to modify via Tools -> Options -> Mechanical Design -> Drafting, refer to DefaultAUX2V4ToV5withOptions.pdf. This document is available on the PDF CD-ROM shipped with CATIA documentation, in the catpdfwhitepaper folder. Version 5 Release 14 V4 Integration Page 357 Reading Version 5 Data in Version 4 Format Warning Prerequisites In order to read and use CATIA Version 5 CATPart documents in CATIA Version 4, the following steps must be carried out: 1. From Version 4.23 R1, CATIA Version 4.23 R1 must be installed on a UNIX machine. 2. You must then install a CATIA V5Rn configuration corresponding to the CATPart's level and it must includes the V4 Integration product (V4I), for example the MD2 configuration (Mechanical Design 2) and set up the appropriate licenses. 3. In order to be able to access the CATIA Version 5 software from a CATIA Version 4 session you must add to the USRENV.dcls file, both in the user and administrator environments, the following (n: is the release number): CATIA.ENVTV5 : STRING; CATIA.ENVTV5 = `$HOME/CATENV/CATIA.V5Rn.Bn.sh'; CATIA.MACHV5 : STRING; CATIA.MACHV5 = 'my_server_machine'; where $HOME is the root $HOME and where CATIA.V5R4.B04.sh is the shell downloaded to $HOME/CATEnv/ using the CATIA Version 5 installation procedure. 4. Make sure that: ● ● the path used to access the CATPart document is the same and the file system containing the CATPart and the file system containing the CATPart is shared between the V4 and V5 machines the user $HOME is the same on the V4 and V5 machines and is shared between both. Version 5 Release 14 V4 Integration Page 358 5. Once the above statement is added to the USRENV.dcls file it is possible to use Version 5 data in a Version 4 session within a client/server environment with the appropriate V5 license set up on the server machine. However, if the last two lines of the declaration above are not specified it is assumed by the system that both V4 and V5 are installed on a local machine. This avoids the error message "Dynamic storage cannot be allocated" displaying when you attempt to read CATIA Version 5 data. 6. You are now ready to manipulate CATIA Version 5 data in CATIA Version 4. You can, for example: ● ● browse V5 documents as passive models using FILE/OPEN read a V5 CATPart document and copy exact solids and surface entities into CATIA Version 4 using MODELS/COPY. Reading directly Version 5 Data in Version 4 You have the possibility to read directly CATIA Version 5 Data in Version 4. For more information, refer to CATIA V4 Documentation, in : CAA Infrastructure Solutions Data Administration and Interoperability Guide Part II : Understanding Different Data Interoperability Issues Manipulating CATIA Version 5 in a CATIA Version 4 Session. Version 5 Release 14 V4 Integration Page 359 Saving CATIA Version 5 CATPart Documents As CATIA Version 4 Models This task shows you how to save CATIA Version 5 CATPart documents as CATIA Version 4 models. This procedure allows you to translate V5 data into native V4 Format. Generative data can be natively introduced into all V4 processes. Sometimes, some entities are degenerated during the transfer. Therefore, when the transfer of some elements is incomplete, a report is available. During the process of saving a V5 CATPart as a V4 Model, the colors of the Faces and the Identificators of the Part Body and Open Body are automatically maintained in the model. During this V5/V4 translation, G1 concatenation takes place in order to get as few Surfaces as possible. You will find a demonstration in: Saving a V5 CATPart as a V4 Model: Report of Identificators Saving a V5 CATPart as a V4 Model: G1 Concatenation Saving a V5 CATPart as a V4 Model: Keep V5 Face Color Once the Save As Model operation is completed, the resulting .Model file can be manipulated like any other existing .Model files. Only the V5 elements in SHOW mode can be translated into V4 format : The V5 visualized geometry is transferred into V4 setting. You can work with V5 entities within the V4 environment. The Save As Model Operation generates V5 geometry and topology into V4 and keeps canonical shapes : ● V5 part bodies and volumes will be translated into V4 Solids without history. ● a V5 Surface is translated into a Face or a Skin in V4. ● V5 Wireframes are transformed into V4 Curves, Planes, Lines, ... ● V5 Axis Systems are transferred into V4 Axis Systems. Open the document MultiBodyAssembly.CATPart. It looks like this: V4 Integration Version 5 Release 14 Page 360 You will remember that in Version 4 the declaration parameter catsite.WRITING_CODE_PAGE declares the code page to be stored in the CATIA data to be written. Such information such as the writing code page was specified in V4 by means of the parameter settings in the declaration files. These declaration parameters are no longer supported in CATIA Version 5. Such information must therefore be provided by means of the dialog boxes described below, before attempting to save a V5 CATPart document as a V4 model. If you want to use the writing code page ISO-8859-1 go straight to step 4. It is the default value so normally, unless another code page was already specified, you can go ahead with the save. However, if you want to use a writing code page other than ISO-8859-1 start with step 1. 1. Select the Tools->Options... command. The Options dialog box appears with the General category selected in the left-hand column. 2. Click the Saving As V4 Data tab. The following dialog box appears: 3. Open the WRITING_CODE_PAGE list in the V4 Declarations part of the dialog box (indicated by the arrow above). Select the appropriate code page and click OK. 4. You can modify the V4 Model Dimension in order to be consistent with the V4 destination site value. 5. Select the File->Save As... command. 6. In the Save As dialog box, select the location of the .model document to be saved and rename it (or not) as required. 7. Click the Save as type: list and select model in the list displayed as shown below: V4 Integration Version 5 Release 14 Page 361 8. In the same box, click on Save. The MultiBodyAssembly.model just created can now be opened, in CATIA Version 4 and will look something like this: Here is a summary of the translation of V5 Features into V4 Elements: Version 5 Release 14 V4 Integration V5 Features (in the CATPart) => Page 362 V4 Elements (in the model) 1 Surface 1 Face (*FAC) 1 Face 1 Face (*FAC) Several Faces (contained in a Surface) Skin (*SKI) Sketches, Wireframe Curves (*CRV), Lines (*LN) Several Curves and Lines Composite Curves (*CCV) Part Body Volumes (*VOL) (SolidE entity) Open Body Curves, Lines, Points, ... 9. If some elements cannot be correctly transferred, the migration of V5 data into native V4 format generates a report file (.rpt). Therefore, V5 CATPart documents are translated into V4 Models with an enhanced report of errors and problems. This report has the same name as the CATPart document and its location is: ● on Windows: in C:Documents and Setting/Username/Local settings/Application Data/DassaultSystemes/CATReport ● on UNIX: in /u/users/username/CATReport By this way, the message lets the user know which element could not be translated in V4. Additional information about the error cause is provided as well. The supplied information (error cause) can be: ● Detection of a gap greater than the maximum allowed value ● Detection of an element with a dimension smaller than the minimum allowed value ● Detection of a shell which cannot be closed into a volume or of faces which cannot be joined into a shell ● A surface which is too small. Here is the content of a report file: INFORMATIONS Report File Name C:/Documents and Setting/$Username/Local settings/Application Data/DassaultSystems/CATReport/MultiBodyAssemble.rpt Originating Files Data Input File Output File Information for the Feature Diagnosis Information for the Feature E:\V5ToV4PartMigr.tst\FunctionTests\NonManifoldAndOpenVolume.CATPart E:\V5ToV4PartMigr.tst\FunctionTests\NonManifoldAndOpenVolume.model There is one or several non manifold edges Diagnosis The shell cannot be closed into a volume Result of migration 0 of the 197 faces have not been migrated. The successful rate for the faces is 100 2 of the 2 volumes have not been migrated. The successful rate for the volumes is 0 Result of migration Saving a V5 CATPart As a V4 Model: Report of Identificators This task shows that you can save a CATIA Version 5 CATPart as CATIA Version 4 models with the reporting of V5 Identificators (names) in the V4 Model. The report of V5 Identificators in the V4 Model can be applied on Part Bodies and Open Bodies. V4 Integration Version 5 Release 14 Page 363 Part Body features are converted as volumes. The Save As Model operation creates a SolideE entity (Exact Volume). During the Save As Model operation, the identificator of the solid is no longer " *SOLn " and it automatically becomes the same identificator as the Part Body feature. Open Body features and Sketches are converted as follows: ● ● V5 surface features are converted as faces (*FAC). If the V5 feature consists in several faces, the Save As Model operation automatically creates a federating Skin (*SKI). V5 Identificators are reported on the V4-generated Skin elements. V5 Sketches and Wireframe features are converted as V4 curves (*CRV) and lines (*LN). If the V5 feature consists in several curves or lines, the Save As Model operation automatically creates a federating composite curve (*CCV). V5 Identificators of Open Body features are reported on V4 elements contained in the model. For more information about the results of the V5 to V4 translation, please refer to the table above. To illustrate this behavior, please look at the following image: The identificator of the Part Body, Feat1, is kept and transferred into the .model. The attributes of V5 Points (*PT) and Lines (*LN) are not taken into account during the Save as Model operation. You can compare this CATPart and the results of its conversion: V4 Integration Version 5 Release 14 Page 364 Points and Lines have lost their type attributes (thickness, dotting, star, cross, plus,...) during the V5 -> V4 Migration. Saving a V5 CATPart As a V4 Model: G1 Concatenation In CATIA V4, surface of good quality are G1-continuous. In CATIA V5, the surfaces must be C2-continuous. It means that a surface already continuous in tangency must be continuous in curvature for the V5. So copying a V4-surface and paste it into a CATPart often requires to split it in several surfaces. Thus, in order to reduce the topology and geometry complexity when going back to the V4 by saving a part as a model, surfaces are concatenated when the G1-continuity can be kept during their transfer. The number of faces lying on these surfaces are concatenated when possible. The result is : simplification of the geometry and topology by reducing the number of elements. It is also a means to retrieve a V4 topology similar to the one that would be used to generate a V5 Part. Open the SIMPLIF-EXAMPLE-1.model document. V4 Integration Version 5 Release 14 Page 365 1. Copy/Paste the .model document into a V5 CATPart in order to be able to add geometric elements in the CATPart in CATIA V5 (in the FreeStyle workbench). During the transfer into CATIA V5, the initial V4 Surfaces, copied As Result, are splitted into several Surfaces in order to keep a C2 continuity. They are still NUBS Surfaces. When going back into CATIA V4, you must be able to find the same original Surfaces, when they have not been modified in CATIA V5. This is why there is a reconcatenation if a G1 continuity with V4 tolerances is detected between Surfaces originating from the same V4 initial Surfaces. The faces lying on the concatenated Surfaces are simplified with an elimination of the shared Edge chains. 2. Save this CATPart As a V4 model to go back into CATIA V4 and be able to use a V4 application. V4 Integration Version 5 Release 14 Page 366 Note that the number of Surfaces have been reduced. During the V5 to V4 translation, Surfaces are concatenated when the G1continuity can be kept during their transfer. It allows a de-synchronization of the migration of the Geometric Modeler's applications, in CATIA V5. In CATIA V4, to be able to retrieve the concatenation of the whole initial V4 Surface, you must have migrated either all this Surface into CATIA V5 or a topology containing all the G1 cuttings. Saving a V5 CATPart as a V4 Model: Keep V5 Face Color During the process of saving a V5 CATPart as a V4 Model, the colors of the Solids, Faces and Skins are automatically maintained in the model: Version 5 Release 14 V4 Integration Page 367 Save as model with face color kept Previously, only one color -the color of the PartBody- was reported onto the .model. Now, it is possible to transfer the colors of different Faces belonging to the same Surface. As there are more colors in V5 than in V4, V4 color is the "nearest" color defined in the V4 color table. During the V5->V4 translation, this is the color of the V5 document that is associated to the model but not the color eventually associated to a Layer in Standard/Color/Layer in CATIA V4. During the migration, the following window may appear: This window means that memory usage has reached its limit. The process has not enough memory to migrate volume into solid. You can try the same operation in associative mode or in not associative mode with "No solid creation" option (refer to Tools Options -> Compatibility -> Saving as V4 Data). If it still does not work, you should try to reduce the size of the CATPart. V4 Integration Version 5 Release 14 Page 368 Saving As Model: Saving CATPart "Product Description Property" As V4 Model Comment (during a V5 to V4 Migration) This task shows you when saving a V5 CATPart document as a model, the Product Description property of the part will be reported into the V5 model comment. Product Description Property is available on any CATPart or CATProduct document and represents the only consisting correspondence to V4 Model/Detail comment functionality. It can be used to add text based information to pure 3D geometry data. When migrating V4 models the Product Description property is the target for the conversion of V4 Model/Detail comments. The reverse translation when saving V5 Parts as models is now possible. For more information about the V5 to V4 Migration, please refer to Saving a V5 Part as a V4 Model. Open the document PART_COMMENT.CATPart. 1. Select any component of the CATPart (or CATProduct) and Edit -> Properties. Press the Product Tab and the comments are in the Description field: The maximum length of a V4 comment is 70 characters per line. If you exceed this number, a new line -with date- is created. When you save a CATPart into a .model, the comment(s) (plus dates) you have added to the document is/are kept in memory. 2. To save this CATPart as a .model, select the File->Save As... command. 3. In the Save As dialog box, select the location of the .model document to be saved and rename it (or not) as required. 4. Click the Save as type: select model in the list displayed. And you obtain: MODEL_COMMENT.model. After a migration, the CATPart turned into a .model. Note that the Properties dialog box is a little different but the access to this information is quite the same. 5. To have access to the V4 Model comment, select the File->Information command. The Properties dialog box appears. V4 Integration Version 5 Release 14 Page 369 You can also have access to the V4 Model comment by selecting the File->Comment command. The following dialog box appears: You can now compare, the original comments have been transferred from CATIA Version 5 to CATIA Version 4. Moreover, in the Comment dialog box you can add information or modify the content of the model's comment. The new comment can be saved in the model's properties when you close and save the document. V4 Integration Version 5 Release 14 Page 370 Saving CATIA V5 Text Annotation as CATIA V4 3D Text This task shows you how it is possible to migrate CATIA V5 Text Annotation (Text With Leader) into CATIA V4 3D Text. Only text annotations attached to 3D geometry are migrated. It means that annotations which are attached to Points, Lines, or Surfaces are not migrated in the model. In CATIA V5, you can create 3D annotations or 3D Text by selecting Insert -> Annotations -> Text with Leader. Open MigrAnnotation.CATPart. This CATPart contains 3D Text and arrows: 1. Save MigrAnnotation.CATPart As a .model. 2. Open MigrAnnotation.model in CATIA V5. The Annotations have been transferred into the model. The positions of the texts have been kept. You can notice that the arrows have not been reported. Indeed in V4, 3D Text descriptions do not support arrows. V4 Integration It is possible to edit V4 3D Text in CATIA V4. Version 5 Release 14 Page 371 V4 Integration Version 5 Release 14 Page 372 Saving CATIA Version 5 CATProduct Documents As CATIA Version 4 Sessions This task shows you how to save CATIA Version 5 CATProducts as CATIA Version 4 Sessions. This procedure allows you to translate V5 data into native V4 Format. Generative data can be natively introduced into all V4 processes. Note that the first component in the CATProduct will be the Active Model in the Session and the other components will be downloaded in the passive mode. There are a few prerequisites for this kind of operation : ● the CATProduct must have .models and / or .CATParts ● the characters' number in the path of the session or of the CATProduct's components must not exceed 44 characters ● the characters' number in the name of the session must not exceed 80 characters ● the characters' number in the name of the CATProduct's components must not exceed 64 characters. Open the plane.CATProduct document. It looks like this: V4 Integration Version 5 Release 14 Page 373 1. Select the File -> Save As command. The Save As dialog box appears. In the Format list, select session and select the location / path of the .session document to be saved and enter a name for this document (for example, Sample1). Finally, click on Save As. If you do not enter any name for the document you are saving, it is automatically saved under the original CATProduct and the extension is .session, for example : plane Note that you can save the .session document with a DLName. DLNames must be in uppercase characters (for instance, SESSION_DIR). In this situation, the Save As dialog box looks like this: V4 Integration Page 374 Version 5 Release 14 A DLName is a name which stands for a folder. In other words, it may be defined as a logical name used for paths. Any modification of a path impacts the DLName once, thus avoiding to search for and modify manually any occurrence of this path. For more information about the DLName environment, refer to Document in CATIA Infrastructure User's Guide. 2. When the CATProduct contains one or several CATParts, they are saved as .model into the same directory as the session file. Only the V5 elements in SHOW mode can be translated into V4 format. For more information about the Save As Model functionality, refer to Saving CATIA Version 5 CATPart Documents as CATIA Version 4 Models. 3. The Sample1 Version 4 and will look something like this: just created can now be opened in CATIA V4 Integration ● Version 5 Release 14 Page 375 If you save the V5 CATProduct as a CATIA V4 Session on Windows and you want to read it on Unix: ❍ use the DLName environment to save as session the product. This operation generates a .session and . model documents. The DLName environment enables to create links which can be recognized in CATIA V4. If you do not use the DLNAME the links between session and models will be unreadable in CATIA V4. ❍ ❍ transfer the documents generated by save as session (.session and . model documents ) from DLNAME Windows directory to Unix directory : /u/SessionDirectoy for instance. add in the USRENV.dcls file: catia.MODEL = ' "/u/SessionDirectoy", "SESSION_DIR" ' ; catia.SESSION = ' "/u/SessionDirectoy", "SESSION_DIR" ' ; "SESSION_DIR" corresponds to the DLname used during the saving operation on Windows. V4 Integration ● Version 5 Release 14 Page 376 If the V5 CATProduct has been saved as a CATIA V4 session on UNIX, no need to change the USRENV.dcls file to read the session in CATIA V4. V4 Integration Version 5 Release 14 Page 377 Saving a V5 Parabola as a V4 Parabola This task shows you how to save a CATIA Version 5 Parabola as a CATIA Version 4 Parabola. A V4 Parabola is created if there is a parabola in the CATPart the customer wants to save as model. The customers, who want to use V5 Parts (with Parabola) in the V4 are all concerned, and the customers who want to transfer their V4 models to the V5 and to transfer the created Part back to the V4 are also interested. To be correctly transferred and to keep the canonicity of the parabola, these conditions (represented in the screen shot below) must be checked: ● The distance between the center and the focus must be lower than the V4 infinite and higher than half the V4 point tolerance ● Each point of the hyperbola must be in V4 validity domain. ● The surface under the V5 parabola must be a plane ● The parabola must have distinct beginning and ending points. A parabola degenerated in one point won't be translated with its canonicity. If one of these conditions is not checked, the transfer will be done, but canonicity will be lost. It means that one parabola would be transferred as a generic curve. V4 Integration Version 5 Release 14 Page 378 V4 Integration Version 5 Release 14 Page 379 Saving a V5 Hyperbola as a V4 Hyperbola This task shows you how to save a CATIA Version 5 Hyperbola as a CATIA Version 4 Hyperbola. A V4 Hyperbola is created if there is a Hyperbola in the CATPart the customer wants to save as model. The customers, who want to use V5 Parts (with Hyperbola ) in the V4 are all concerned, and the ones who want to transfer their V4 models to the V5 and to transfer the created Part back to the V4 are also interested. To be correctly transferred and to keep the canonicity of the hyperbola, these conditions (represented in the screen shot below) must be checked: ● The distance between the center and the vertex must be lower than the double of V4 infinite and higher than the V4 point tolerance ● Each point of the hyperbola must be in V4 validity domain ● The surface under the V5 hyperbola must be a plane ● The hyperbola must have distinct beginning and ending points. An hyperbola degenerated in one point won't be translated with its canonicity. If one of these conditions is not checked, the transfer will be done, but canonicity will be lost. It means that one hyperbola would be transferred as a generic curve. V4 Integration Version 5 Release 14 Page 380 Saving a V5 Torus as a V4 Torus This task shows you how to save a CATIA Version 5 Torus as a CATIA Version 4 Torus . A V4 Torus is created if there is a Torus in the CATPart the customer wants to save as model. The customers, who want to use V5 Parts (with a Torus surface) in the V4 are all concerned, and the ones who want to transfer their V4 models to the V5 and to transfer the created Part back to the V4 are also interested. To be correctly transferred and to keep the canonicity of the torus, these conditions (represented in the screen shot below) must be checked: ● ● ● ● ● ● The radius of the generator circle must be higher than V4 point tolerance but lower than V4 infinite tolerance The distance between the torus center and the generator circle center must be higher than V4 point tolerance and lower than V4 infinite tolerance The distance between the center and any point of the torus must be lower than V4 infinite tolerance The center and any point of the torus must be in V4 domain. Any point of the torus must have coordinates lower than V4 infinite tolerance The radius of the generator circle must be lower than the distance between the torus center and the generator circle center If there is some surface concatenation, the canonicity may be lost. This restriction is true for all canonic surfaces. If one of these conditions is not checked, the transfer will be done, but canonicity will be lost. V4 Integration Version 5 Release 14 Page 381 V4 Integration Version 5 Release 14 Page 382 Saving a V5 Revolution Surface as a V4 Revolution Surface This task shows you how to save a CATIA Version 5 Revolution Surface as a CATIA Version 4 Revolution Surface. A V4 Revolution Surface is created if there is a Revolution Surface in the CATPart the customer wants to save as model. The customers, who want to use V5 Parts (with a Revolution Surface) in the V4 are all concerned, and the ones who want to transfer their V4 models to the V5 and to transfer the created Part back to the V4 are also interested. To be correctly transferred and to keep the canonicity of the revolution surface, these conditions (represented in the screen shot below) must be checked: ● ● Any point of the created surface must be in V4 validity domain and the minimum distance between any point and the axis of revolution must be lower than the double of V4 infinite tolerance. The angle of rotation must be lower or equal to 2*PI and higher than 0.The angle must be higher than the V4 point tolerance divided by the maximum distance between curve and axis. If one of these conditions is not checked, the transfer will be done, but canonicity will be lost. V4 Integration Version 5 Release 14 Page 383 Saving a CATPart as a model in associative mode (V5/V4 Synchronization) This task shows you that you can create a model in associative mode: ● during the Batch migration ● interactively Applying a Save As Model operation on a Volume or a Surface means that the model keeps in memory the path of the Part and you can resynchronize the model after modifying the Part. For Batch migration, you can choose either the Associative Mode or the Non-Associative Mode. For more information about it, please refer to V5/V4 File-based Migration Batch (from the Command Line). Previously, associativity could be maintained only on the PartBody (on volumic components). A message was displayed whenever the migration could not take place for non-volumic elements (lines, points, curves). Now, you can launch the associative mode whatever the CATIA components' nature is (volumic or not). Therefore, a nonassociative Save as Model can be applied on non-volumic or non-surfacic elements. These elements are migrated but there is no link between the migrated components and the CATPart. In fact, they are recreated in the V4 model. How to create a model in associative mode with the Batch migration On Windows and UNIX, you can launch the migration by entering the command: CATV5ToV4 -if input Part -of output model -mod ASSO -if : specify the CATPart to be processed -of : output directory in non-associative mode or explicit model 1. Creation of the model in associative mode Both types of elements are created into the geometrical set, the associative ones and the non-associative ones: ● ● migration in associative mode for Solids, Wireframes and Surfaces non-associative migration for all the other types of geometrical elements (called non-associative elements): pints, lines, curves, faces. V4 Integration Version 5 Release 14 Page 384 2. Synchronization of the model The Following actions are operated: ● migration of the non-associative elements of the current CATPart document into the geometrical Set ● moving of the previous non-associative elements into a layer called " bin " layer ● synchronization of the associative elements (2D: Surfaces; 3D:Volumes) on the current geometry of the CATPart. At each stage of synchronization, the non-associative elements created during the previous migration are added in the "bin" layer. And the non-associative elements of the current CATPart's geometry are entirely re-created. In this way, the user, if he wants, can delete all the old non-associative geometry by selecting the "bin" layer in CATIA V4. The non-synchronized elements are supported during the V5 to V4 migration because despite the selection of the Associative Mode, a non-associative Save As Model is applied to the non-volumic elements in order to allow their migration into V4. The Associative Mode offers better performances because only the last modifications are recalculated, which is not the case with the Non-Associative Mode. The size of the generated models is different if you choose one mode or the other: ● ● with the Associative mode, the sub-elements are not migrated because a link is kept with the CATPart. Therefore, the size of the model is less important. with the Non-Associative mode, the resulting model is bigger because the historical data (buidling elements) are recreated in V5. 3. Number of the layer for non-associative data The number of layer can be specified by the user thanks to the Tools->Option->Compatibility Settings. Note that in V4 model, a number of layer can have a value between 0 and 254. If this setting is not informed, a default layer number is used: layer number 254. If you enter 255 for instance, a warning is displayed. V4 Integration Version 5 Release 14 Page 385 The layer is visible in the model. The user can put it in the No Show space or delete it if he wants. 4. Identifiers of the non-associative elements During the stage of synchronization, non-associative elements issued from the previous migration are moved into the "bin" layer and their identifiers are modified in order to know which migration number they come from. Each identifier is modified in that way: RxxxIDENT, where xxx is the migration number. For instance, the identifier LINE.1 becomes R001LINE.1 at the first synchronization of the model. If we make two synchronizations, the model contains LINE.1 and the following identifiers R001LINE.1 and R002LINE.1. For more information about V4/V5 Compatibility Settings, please refer to Saving As V4 Data in CATIA - Infrastructure User's Guide. How to create a model in associative mode interactively Open the SaveAsModel.CATPart document. V4 Integration Version 5 Release 14 This CATPart contains: ● 3D components: volume ● 2D: surface ● 1D: line, curve ● 0D: point 1. Select the Associative mode in the Tools->Options->Compatibility Settings. This option is kept in memory; if you reopen CATIA V5, the Associative Mode will be the active mode. 2. Save the CATPart As a Model: Page 386 V4 Integration Version 5 Release 14 Page 387 After the V5 to V4 migration, the non-volumic or non-surfacic elements are re-created (point, line, curve and face). In the Specification Tree, OP....1 indicates the name of the newly created component in V5 and its container: OPEN_BODY.1_POINT.1 for instance. However, the volumic or surfacic components appear differently in the Specification Tree: you only have the container information of the migrated Solid because a link is kept with the CATPart. 3. In the CATPart, modify the Solid for instance. Then save the CATPart as model with the same name (SaveAsModel.model) in order to update the model. V4 Integration Version 5 Release 14 Page 388 4. Close the Solid and re-open it. Associativity is kept between the CATPart and the model: The modifications made in V5 are reported in the model. V4 Integration Version 5 Release 14 Page 389 For instance, the Point identifier becomes R00....1 (R001 OPEN_BODY.1_POINT.1) at the first synchronization of the model, this is the "old" version before the synchronization. The new one is symbolized by OP....1. The Surface contains 4 Curves (or Edges) and a Face. This is why the CRVs container has 4 Curves which are the building elements for the *SUR1. But OP....1 in CRVs corresponds to Curve.1 (non-volumic element), a feature belonging to Open_body.1. In spite of the fact that Curve.1 has not been modified, you can see that it has been recreated because the "old" version is represented by R00....1 (R001 OPEN_BODY.1_CURVE.1) and the new one by OP....1 (OPEN_BODY.1_CURVE.1). The non-associative data (R00....1 elements) is referenced in a bin layer which the user can delete if he wants. In our exemple, only Solid.1 has been synchronized because it is an associative element and its geometry and specifications have been recalculated. Version 5 Release 14 V4 Integration Page 390 Writing Axis Systems from a V5 Track to a V4 Model This task shows how to export a V5 track definition in V4. Each V5 recorded position is exported as an Axis in one V4 model document. It is then possible to rebuild a V4 track from these positions. This functionality is very useful when you are designing products in CATIA V4 and reviewing your DMU in Fitting V5. You can easily retrieve information from your V5 review to perform modifications in CATIA V4. Note: The user needs to rebuild a route in V4 from the exported axis systems. In the DMU Fitting Simulator workbench, open the EXPORT_V5_TRACK.CATProduct document. 1. Double-click Track.2 in the specification tree. 2. Click the arrow within the Clash Detection icon toolbar if necessary. 3. Set the Clash detection to on 4. Play your track simulation using the Player from the DMU Check toolbar. Undock the V4 Integration Version 5 Release 14 5. There is a collision detected at recorded position 3. You need to modify your design. 6. Select the track.2 either in the geometry area or in the specification tree . 7. Select Tools->Simulation->Track File Export Page 391 V4 Integration Version 5 Release 14 Page 392 The Track File Export dialog box automatically appears: 8. Enter a meaningful name and select .model format from the Save as Type drop-down list: Version 5 Release 14 V4 Integration Page 393 9. Open the EXPORT_V5_TRACK.model document you have just created This is what you obtain: Note: Double-click Master node to display the specification tree 10. In this V4 model document we selected axis system 3 (highlighted) which corresponds in the dismounting review to the position 3 where a collision was detected. You are now ready to modify your design using this information. V4 Integration Version 5 Release 14 Remember though: There isn't any V4 Fitting entities created. V4 tracks do not exactly share the same behaviors with V5 tracks (such as interpolation, etc.). Page 394 Version 5 Release 14 V4 Integration Page 395 V5/V4 File-based Migration Batch This task shows you how to convert CATIA Version 5 documents into CATIA Version 4 from a command line (not with the interactive batch). You can launch the V5 / V4 Batch from: ● ● the DataLifeCycle Batch, for more information about DataLifeCycle, please refer to Running the DataLifeCycle Batch in the Infrastructure User's Guide. the Command Line. You can choose between 2 modes: ● ● Non-Associative Save As Model: no link with the CATPart Associative Save As Model: the part's path is kept in memory and you can re-synchronize the model after modifying the part. Each non-volumic and non-surfacic V4 element keeps a link with its equivalent in the CATPart in order to use its own data that allowed its construction. Before launching the batch tool: ● you have to make sure that your environment is correctly set up. ❍ On Windows, the Batch's environment is installed during CATIA's installation. ❍ ● On UNIX, you have to set up this environment before starting the session. For more information about this, see CATIA - Infrastructure User's Guide - Starting a session on UNIX. you must have the x Server installed on the machine on which you are executing the Batch. Then, you must enter the command: xhost+ (on UNIX) allowing you to get back the V5 colors. On Windows and UNIX, you can launch the migration by entering the command: ● CATV5ToV4 -if inputPart -of outputmodel [ -mod savingmode] [ -report ] -if: The -if parameter is mandatory; this parameter can be either a CATPart path or a Text file path. If it is a CATPart, it specifies the document to be processed. The migration result is stored in the same directory of the part and it acquires the same name as the part's if you do not specify the -of parameter. For instance: -if Directory1/Part1.CATPart. If it is a Text file, it should have the .txt extension and contain CATPart paths. For instance: -if xx.txt. xx.txt should contain some things like: Directory1/Part1.CATPart Directory2/Part2.CATPart -il: this option allows you to specify an enumeration of input CATPart paths. For instance: -il Directory1/Part1.CATPart Directory2/Part2.CATPart -of: output directory parameter. This parameter can be either a model's path or a directory path. If it is a directory, the model will take the name of the Part. For instance: CATV5ToV4 -if inputPart\Part1.CATPart -of outputPartDir The generated model will be saved in outputPartDir\Part1.model. V4 Integration Version 5 Release 14 Page 396 -mod: saving mode, the value can be ASSO (for associative model creation or synchronization) or NO_ASSO for standard Save As Model. If this parameter is not valuated, it is read in the Associativity mode CATSetting (in the General category of the Options Tree, select Compatibility and click the Saving as V4 Data tab). -report: output directory. If no report directory is specified, the report is stored in the standard process output directory: CATReport. Else the report file (.rpt) is stored under the specified directory. When you are in Associative Mode, all these references (-if/-il, -of, -mod) must be specified. Examples: CATV5ToV4 -if inputPart -of outputdirectory: Performs standard Save As model on input Part document and stores the resulting model named automatically in the output directory. CATV5ToV4 -if inputText -of outputdirectory: Performs standard Save As model on input Parts referenced in the inputText. They are stored in the output directory. For instance: -il Directory2/xx.txt. CATV5ToV4 -if inputPart -of outputmodel: Performs standard Save As Model on input Part and names the resulting model according to the -of option. For instance: -of Directory2/model1.model. CATV5ToV4 -il inputPart1 inputPart2 -of outputmodel: Performs standard Save As Model on input Parts and names the resulting models according to the -of option. CATV5ToV4 -if inputPart -of outputmodel -mod ASSO: Creates or synchronizes the associative model specified by the -of option. Note that the -of option is mandatory in this case. For information, in these examples, ● ● inputparts can be: ❍ on UNIX: /u/Parts/Part1.CATPart ❍ on Windows: E:\Parts\Part1.CATPart outputdirectory can be: V4 Integration ❍ on UNIX: /u/Models ❍ on Windows: E:\Models Version 5 Release 14 Page 397 Settings: V5 Settings are taken into account, more particularly Interoperability settings like Model Dimension, Model Unit or Initial Model. For more information about the non-associative Save As Model operation, please refer to Saving a V5 Part As a V4 Model. Version 5 Release 14 V4 Integration Page 398 Optimizing V5/V4 Migration In order to get optimization during the V5/V4 Migration, two variables can be activated: ● V5V4CleanTolerance: to clean small V5 elements ● V5V4MaxSimplif: to extrapolate small V5 adjacent faces This can result in dramatic improvements in terms of conversion performance, memory consumption and Model size. How to launch V5V4CleanTolerance 1. On Windows, enter the following command: set V5V4CleanTolerance=.01(*) 2. On UNIX, enter the following command: export V5V4CleanTolerance=.01(*) (*) tolerance value: .01 for instance (.01 for 100th mm) During the V5/V4 import, when this variable is activated, small elements (Edges, Faces) are cleaned inside this tolerance (for instance, tolvalue=.01). The usability of the resulting model is increased , for example if the V4 model must be reworked, using limit2 or form tool V4 function. We guarantee that the gaps created between these cleaning actions are less than this tolerance. Add-value: ● clean small objects ● better control of V4 topology quality If this setting is not activated, the same cleaning actions will be done, using the V4 Identical Curves tolerance. How to launch V5V4MaxSimplif In complement to the previous cleaning actions, the program tries to concatenate the small faces next to the large adjacent ones. V4 Integration Version 5 Release 14 Page 399 1. On Windows, enter the following command: set V5V4MaxSimplif=1 2. On UNIX, enter the following command: export V5V4MaxSimplif=1 The goal is to eliminate these small Faces without creating a gap in the resulting topology. Thanks to this variable, the V5/V4 Migration is improved because simplification of the V5 components takes place. Add-value: ● better usability of the V4 Model because small Faces are eliminated ● in this case, no gap creation when small defaults are cleaned. Version 5 Release 14 V4 Integration Workbench Description The V4 Integration user interface looks like this: The section is organized as follows: Menu Bar Geometry and Specification Toolbar Page 400 Page 401 Version 5 Release 14 V4 Integration V4 Integration Menu Bar This section presents the V4 Integration menu bar available whenever you open a Version 4 model: Start File Edit View Insert Tools Window Filter Help Note that the V4 Integration menu bar is only slightly different from the main menu bar described in the CATIA - Infrastructure User's Guide. Filter For... See... Layer Filter Managing Layer Filters on CATIA Version 4 Models V4 Integration Version 5 Release 14 Page 402 Geometry and Specification Toolbar The only toolbar specific to the V4 Integration workbench is the Geometry and Specification Check toolbar: For more information about either of these icons, see Checking CATIA Version 4 Model Data Before Copying It to CATIA Version 5. V4 Integration Version 5 Release 14 Customizing V4/V5 Infrastructure Saving as V4 Data V4/V5 DRAW V4/V5 SPACE V4/V5 SPEC Migration Batch Page 403 V4 Integration Version 5 Release 14 Page 404 V4 Data Reading This task shows you how to customize Compatibility settings. 1. Select the Tools -> Options... command. The options dialog box appears with the category tree in the left-hand column. 2. In the General category of the Options Tree, select Compatibility and click the V4 Data Reading tab. The following dialog box appears: In CATIA Version 4, certain information was specified by means of the parameter settings in the declaration files. These declaration parameters are no longer supported in Version 5 and there is no way to transfer them automatically to Version 5. Such information must be provided by means of the Options dialog box shown above, before attempting to read Version 4 data. The Options dialog box lets you: ● display faces and surfaces visible in shading mode in CATIA Version 4. ● open CATIA Version 4 models referencing an external PROJECT file. ● ● ● specify the Initial Model File Path: to translate V5 CATPart documents into V4 Models using V4 standards defined in the V4 Initial Model. specify the writing code page identifying unlabeled data. declare the code page to be stored in the CATIA data to be written when saving Version 5 CATPart documents as CATIA Version 4 models. ● declare the Model Dimension when saving V5 CATPart documents as V4 Models. ● declare the Model Unit when saving V5 CATPart documents as V4 Models. ● declare the location of a character equivalence table. ● choose options for Migration Batch: Conversion Mode and Format. V4 Integration Version 5 Release 14 Page 405 Reading V4 Data ● Display only elements with Sensitive Attribute: In CATIA V4, the "Display only elements with Sensitive Attribute" mode enables you to decide whether to display the faces and surfaces sensitive to the shading mode in CATIA Version 4. To display only the faces and surfaces that were sensitive to the shading mode in Version 4, you must therefore activate this option. In CATIA Version 5, by default, this box is deactivated. ● Display 3D elements labels This option is checked by default. It means that when you download a model in CATIA V5, the visualization of the V4 elements' Id or 3D text is recalculated. For instance, the Id *FAC can appear near the 3D Face in the 3D space. If you do not check this option, the 3D text associated to the V4 elements will not be built. They will not appear in the 3D space in CATIA V5. ● Open in Light Mode: Open a V4 Model without DRAW Data If you activate this setting, you can disable the reading of DRAW data. The integration of V4 models in V5 applications generally uses only the 3D Master representation of the model. On the other hand, the management of V4 DRAW data brings several critical issues: - Stability issue: PRJ has to be referenced correctly, else CATIA may crash - Performance issue: data conversion (CATAIX/CATUNIT) of DRAW data is very expensive. - Memory consumption. Skipping DRAW data when opening the model will not bring any restriction when working in Assembly or DMU workbenches for instance. On the contrary, it will be a major stability / performance / memory cost upgrade. The DRAW data is suppressed before any operation (internal or external) can be performed on the model. However the DRAFT tab page is still available, but swapping to this tab page will generate a warning message indicating that the model has been opened in light mode: V4 Integration Version 5 Release 14 Page 406 You only get SPACE elements in the *MASTER tab; the *DRAFT tab is empty: This setting can also be effective with CATProducts and Sessions containing V4 models. Note: - the warning is displayed only once per tab page. - some functionalities open directly the models in 2D mode (for example: ENOVIA DMU / Send to V5 2D Viewer). The warning should be sent in that case too. If a user wants to reread a model and browse V4 geometry, it is necessary to uncheck the setting ant to reopen the model. If this setting is activated, the V4-V5 Migration Batch will not be able to migrate V4 Drawing data. Therefore, if you want to convert V4 drawing elements in CATIA V5, it is necessary to uncheck this option. For more information about the Migration Batch, please refer to the CATIA - V4Integration User's Guide. If the model has an external PRJ File which is not specified in the Tools-Options, a second message appears (even if the PRJ File Path is not necessary when you choose the Light Mode). However, this warning is useful when the user decides to go back to the normal mode (not the Light Mode), at the same time he can also specify the PRJ File Path in the Tools-Options. This mode is also available in PDM Application when sending a model from PDM Application into CATIA V5. V4 Integration ● Version 5 Release 14 Page 407 Specifying the code page identifying unlabeled data In V4, the declaration parameter catsite.DEFAULT_DS_CODE_PAGE declares the language to identify the data read if this data is not labeled (i.e. if it is just labeled EBCDIC or ASCII, and not labeled with a standard code page such as ISO8859-x, IBM-392, EUC-KR, EUC-CN, and so forth). In Version 4, information such as the language used to identify unlabeled readable data was specified by means of the parameter settings in the declaration files. These declaration parameters are no longer supported in Version 5 and there is no way to transfer them automatically to Version 5. Such information must be provided by means of the dialog boxes described below, before attempting to read Version 4 data. For Version 4 data that is not labeled with a standard code page (for example, ASCII-DS-xxx or EBCDIC-DS-xxx) other than US English, you must specify the appropriate language from the list provided. To do this, click on the DS_DEFAULT_CODE_PAGE list in the V4 Declarations part of the dialog box and select the appropriate language. ● PROJECT File Path: Opening CATIA Version 4 models referencing an external PROJECT File In V4, certain model data must be contained in a PROJECT file which can either be internal to the model or external. If it is external, the only way to access such data is to provide Version 5 with precise information about the PROJECT file's whereabouts. Enter, in the PROJECT File Path field, the location of the PROJECT file referenced by the V4 model you wish to display. Make sure you complete this field before displaying a Version 4 model. Bear in mind the following: ● If you do not specify the PROJECT file path before opening the model, a warning message will appear. ● There are no restrictions as regards the PROJECT file's code page. However, you must make sure that the code pages of the model and the PROJECT file are compatible. The following reference tables in the PROJECT files can now be accessed in Version 5: ● attribute and class tables ● annotations/dimensions. V4 Integration Version 5 Release 14 Page 408 On UNIX and Windows, you can reference an external PROJECT File using the http protocol, the address to be specified should be like this: http://serverName/path/PRJDirName Make sure beforehand that an http server has been installed on the machine where the V4 data resides. For more information, you can refer to About Data Sharing between Windows and UNIX, in CATIA - Infrastructure User's Guide. On UNIX only, you can also reference PRJ files with a UNIX path: /u/path/PRJDirName On Windows only, if you have access to PRJ files installed on the Windows disk, you can reference it with an Windows path: E:pathPRJDirName In that case, you need to bring these Project files referenced by the model into an Windows directory and rename these files according to the conversion table. In the PROJECT File path, you refer to the directory containing the Project Files. For more information about character conversion, refer to the Conversion Table in the Model Naming chapter in CATIA V4Integration User's Guide. Thus, in the PROJECT File path you refer to the directory containing the Project Files. For more information about the methodology of coping your Project File on Windows, refer to Having Access to PRJ File on Windows in CATIA V4Integration User's Guide. ● DLNAME In the V4/V5 Infrastructure settings, the only way to locate a PROJECT File physically is to fill in the PROJECT File Path. The DLNAME setting does not allow this functionality. This setting only allows to compare the Model DLNAME (when the Model references a DLNAME instead of a PRJ File Path) with the specified one within the setting. When the user has only specified the PRJ File Path (User_PRJ) and not the DLNAME, whereas the model references only a DLNAME (User_dlname), the following Warning message appears: Page 409 Version 5 Release 14 V4 Integration Whatever the value of the DLNAME field is, the PROJECT File Path is taken into account (reference to locate the PROJECT File). This is the reason why the DLNAME option is automatically deleted when the PROJECT File Path is not specified and when you click OK to close the window. Conversion V4/V5 ● Characters Equivalence Table Path: The Characters Equivalence Table is taken into account when using the following functionalities: 1. File / Open a Session or a .asm document (documents are read with V5 compliant names). For more information about this functionality, read Opening a CATIA V4 Session in CATIA V5, in CATIA V4Integration User's Guide. 2. V4 to V5 Migration Batch (documents are migrated with V5 compliant names). The Characters Equivalence Table allows to convert characters contained in CATIA V4 documents. It is mainly used to generate V5 compliant names from V4 names by replacing special characters (", *, /, etc...) by standard characters. A default table exists (table path empty) but the user can choose a different table by specifying its Windows or UNIX path in the option box: The table file is a .txt document. By default, the conversion table will be applied to special characters: ASCII Code of the Original Character 0x22 0x2a 0xB1 0x2f 0x3a 0x3c 0x3e 0x3f 0x5c 0x7c Character to be Replaced New Character String " * / : < > ? \ | _Inch x _ _ _ _ _ _ _ _ For instance, the double-quotes (0x22 in ASCII code) will be replaced by "_Inch". If you want to display it on Windows, the address to be specified should look something like this: home/path/table.txt. CATIA V4 documents, containing the special characters space and slash, are saved with a name which does not have the space or slash character. The space is automatically Version 5 Release 14 V4 Integration converted in (0xB1) and the slash is automatically converted in (0XB4). Page 410 In CATIA V4, if a pointed document is renamed or moved, the multi-model link is broken. If a document name contains a space, it is a result of a manual renaming procedure, so the pointed document is considered to be not the same as the one corresponding to the link name. When V4 documents dependencies are scanned for renaming, V4 links (if exist) are analyzed, and the CATV4ToV5CompatibilityName try to find the pointed documents. If their name must be changed, they are added to the list of documents to rename. But, if the name of the pointed document does not match the saved pointed document (with and ') the dependency is not taken into account. And the pointed documents are considered as not found. In the multi-model links, the conversion table is applied on: ● the document name (in the link) for the slash ● the saved name for the space. If the conversion table is not defined, the default character for space and slash for the CATV4ToV5CompatibilityName is underscore. If the conversion table is defined, it is used to convert the V4 documents. Here is an example with a pointed document or a model name: ● ● ● Link name with space and slash ❍ Sample ZZZ/ZZZ.model Pointed document on disk: ❍ Sample ZZZ ZZZ.model With no conversion table: ❍ ● new name: Sample_ZZZ_ZZZ.model (and ' become _ ) With Conversion table: (if converted into A and / converted into B) ❍ new name: SampleAZZZBZZZ.model. For more information about this functionality, read Migration in Batch Mode, in CATIA - V4 Integration User's Guide. Click OK to confirm. V4 Integration Saving as V4 Data Version 5 Release 14 Page 411 This task shows you how to customize Compatibility settings, and more particularly for the V5 to V4 Migration (Save As Model). 1. Select the Tools->Options... command. The Options dialog box appears with the category tree in the left-hand column. 2. In the General category of the Options Tree, select Compatibility and click the Saving as 4 Data tab. The following dialog box appears: Saving as V4 Data ● Declaring the writing code page when saving Version 5 CATPart documents as CATIA Version 4 models V4 Integration Version 5 Release 14 Page 412 For a full scenario illustrating this functionality see "Saving Version 5 CATPart Documents As CATIA Version 4 Models" in the CATIA - V4 Integration User's Guide. In Version 4, the declaration parameter catsite.WRITING_CODE_PAGE declares the code page to be stored in the Version 5 data to be written. The writing code page ISO-8859-1 is the default value so normally, unless another code page was already specified, you can go ahead with the save. However, if you want to use a writing code page other than ISO-8859-1, open the WRITING_CODE_PAGE list in the V4 Declarations part of the dialog box (indicated by the arrow above), select the appropriate code page and click OK. ● Declaring the Model Dimension when saving Version 5 CATPart documents as CATIA Version 4 models It is possible to customize Model Dimension for V4 models generated in V5. V4 tolerances will be computed according to V4 recommended values from this Model Dimension. In V4, model tolerances can be modified through Standards -> Model Function. The Model Dimension Parameter, which can be modified in CATIA V4, has an impact upon the precision of geometrical calculation. The value by default is 10000mm and it corresponds to the V4 value. Before saving a V5 Part as a Model, you can change the Model Dimension parameter to fit your V4 standards. The whole set of tolerances will be computed from this Model Dimension according to the V4 recommended values. Be aware that modifying this value without consideration can affect dangerously the V4 geometry. The modification of the Model Dimension parameters should only be used to respect the V4 standards. The management of the resolution is different in V5 and in V4: In V5 the main concept for tolerances is the Resolution which defines the minimum length of a valid object. It is fixed to 10-3mm. The management of confusions ("Do two objects have the same geometry?") is a direct consequence of the resolution: if the distance between to geometric points is less than the resolution, the two points are considered to be geometrically at the same location. In V4, tolerances are driven by the Model dimension. The most appropriate value to fit V5 resolution is 10000mm. Note that this is also the V4 default value. Page 413 ● Declaring the Model Unit when saving Version documents as CATIA Version 4 models: Version55CATPart Release 14 V4 Integration You can apply a scale factor between the imported file and what you want to get from the original Model. You can choose a V4 Unit in this list: ● Writing the Initial Model File Path With this option, you have the possibility to translate V5 CATPart documents into V4 Models using V4 standards defined in the V4 Initial Model. You may use an Initial Model; this means that you define a reference model which includes default values. To customize the environment (initialization values to modal parameters and management parameters), you need to create an Initial Model. Such a Model is often used to ensure that everyone in a company works with the same predefined standard values. The Save As Model operation is able to take into account a V5 setting: a V4 Initial Model file path. Before saving a V5 CATPart as a V4 model, you can specify an initial Model file path in this setting Tools->Options...->General->Compatibility->V4/V5 Infrastructure. The "Initial Model file path" setting can replace the following settings: ● The "WRITING_CODE_PAGE" setting ● The "Model Dimension" setting ● The "Model Unit" setting. And the "Initial Model file path" setting defines other V4 standards: ● The layer filters, ● The colors, ● Standards for SPACE elements: GENERAL and HLR standards can be taken into account. SPEC ELEMENTS standards cannot be defined, ● Standards for DRAW elements. This information will be extracted from the Initial Model and added to the V5-generated model. Version 5 Release 14 V4 Integration Page 414 Initial Models referenced in CATIA V5 should not contain: ● any geometry, SPACE or DRAW, ● any applicative data, ● Internalized Project File. Therefore, Initial Models used in CATIA V4 will not always be reusable directly in V5, and it will be generally easier to recreate a dedicated Initial Model for CATIA V5. If the Initial Model contains elements that are not supported, the Save As Model operation will be aborted. Associativity ● Associativity mode You can create a model in associative mode during the Batch migration or interactively. Applying a Save As Model operation on a Volume or a Surface means that the model keeps in memory the path of the Part and you can resynchronize the model after modifying the Part. You can choose either the Associative Mode or the Non-Associative Mode. You can launch the associative mode whatever the CATIA components' nature is (volumic or not). Therefore, a standard Save as Model can be applied on non-volumic or non-surfacic elements. ● There is a new button: No Solid Creation 1. In the Associativity mode frame, a first choice has to be made between Associative mode and Not Associative mode 2. If the Associative mode has been chosen, there is no access to the No Solid Creation button because this option is only available with the Not Associative mode. 3. If the Not Associative mode has been chosen, the button No Solid Creation can be checked or unchecked. By default, it is not checked, which means that V4 solids will be created in V4 model. If you check this button, no V4 solid will be created; only V4 volumes will be generated in the .model. 5 Release 14 V4 Integration Since the V4 solid is necessary for associativity, Version this option is only available for non-associativity. Page 415 It is advised to use this option only when high memory is required in order to create a V4 model. ● Synchronization of the model: At each stage of synchronization, the non-associative elements created during the previous migration are added in the "bin" layer. And the non-associative elements of the current CATPart's geometry are entirely re-created. In this way, the user, if he wants, can delete all the old non-associative geometry by selecting the "bin" layer in CATIA V4. Number of the layer for non-associative data: The number of layer can be specified by the user thanks to the Tools->Option->Compatibility Settings. Note that in V4 model, a number of layer can have a value between 0 and 254. If this setting is not informed, a default layer number is used: layer number 254. If you enter 255 for instance, a warning is displayed. The layer is visible in the model. The user can put it in the No Show space or delete it if he wants. Identifiers of the non-associative elements: During the stage of synchronization, non-associative elements issued from the previous migration are moved into the "bin" layer and their identifiers are modified in order to know which migration number they come from. Each identifier is modified in that way: RxxxIDENT, where xxx is the migration number. For instance, the identifier LINE.1 becomes R001LINE.1 at the first synchronization of the model. If we make two synchronizations, the model contains LINE.1 and the following identifiers R001LINE.1 and R002LINE.1. V4 Integration Version 5 Release 14 Page 416 Create an error feature in CATPart if saving is incomplete When some V5 elements cannot be migrated into CATIA V4, a warning message can be displayed and an error feature appears in the CATPart's Specification Tree. Never: if the user does not want to see this message and the error feature, he can click this option. After user agreement: if he chooses this option, a warning appears, asking if he wants to see the corresponding error feature in the Specification Tree. If the user click Yes, an error feature indicates the V5 component that could not be migrated: "Invalid BRep Geometry.1 (This face is too small)". In the Geometry, the face is highlighted in red and the user can modify it. V4 Integration Version 5 Release 14 Always: no warning is displayed and the error feature automatically appears in the CATPart's tree. Click OK to confirm. V4 Model File Name ● File name in Capital Letters Page 417 V4 Integration Version 5 Release 14 Page 418 Before migrating a CATPart into a .model, you can specify in the Saving as V4 Data settings that the resulting .model must have Capital Letters. 1. Check the option: File Name in Capital Letters. 2. Open a CATPart in CATIA V5. 3. Save the CATPart as a .model. 4. Open the .model in CATIA V5. In the File Selection dialog box and in then in CATIA V5, the model's name is in Capital Letters: V4 Integration Click OK to confirm. Small Edges and Faces Cleaning ● Maximum Gap: Version 5 Release 14 Page 419 V4 Integration Version 5 Release 14 Page 420 The parameter entered in the Small Edges And Faces Cleaning frame is used in order to choose a maximum gap that may be generated when a small element (Face or Edge) is cleaned in V4 model. 1. In the Small Edges And Faces Cleaning frame, a first choice can be activated or not. 2. If it is not checked, the value used will be the V4 tolerance for Curves. This value appears in the grey editor. 3. If it is checked, it is possible to enter another tolerance which must be lower than V4 tolerance for Curves and higher than 0. The value of maximum gap must be positive. If it is not the case, a warning is displayed until a positive value is entered. If the value chosen by the customer is higher than the V4 tolerance for curves, then this parameter won't be taken into account and the default value will be used. Click OK to confirm. Version 5 Release 14 V4 Integration V4 / V5 DRAW You can customize given options when using interoperability from version 4 to version 5. 1. Select the Tools -> Options... command. 2. Click Compatibility in the list of objects to the left of the Options dialog box. 3. Select the V4/V5 DRAW tab. ● Geometry import When importing geometry, you can decide that you do or do not create centers and end points. ● Dimension conversion mode When converting dimensions, the resulting dimensions can or cannot be edited (modified). Page 421 V4 Integration ● Version 5 Release 14 Explode mode When importing a ditto (or component), this ditto is automatically exploded. As result each element in that ditto can be modified separately. By default, you can convert the V4 Symbolo into Ditto in CATIA V5, but when this setting is activated you can keep the former mode, Explode symbolo mode. ● Blink element When this setting is activated, you obtain a red element in CATIA V5 corresponding to the V4 Blink element. If you do not activate this option, the migrated Blink element is displayed in highlight. ● Generative View style This setting specifies the generative view style that should be used when migrating AUXVIEW2 views from V4 to V5. Select an XML file from the list. The generative view style parameters defined in this file will be used for the migration. If this setting is unavailable, you need to uncheck the Prevent generative view style creation setting from Tools -> Options -> Mechanical Design -> Drafting -> Administration tab. For more information on generative view styles, refer to the Generative Drafting User's Guide. 5. Click OK to confirm the operation. Page 422 V4 Integration Version 5 Release V414/ V5 SPACE Page 423 You can customize given options when using interoperability from CATIA Version 4 to CATIA Version 5. You can choose different parameters for pasted Surfaces/Curves Continuity and Segmentation. In order to optimize Continuity, this window offers you 3 settings allowing you to control the deformation of V4 Geometry in CATIA V5. Concepts: Controlling the Deformation of V4 Geometry and the Migration of Details in CATIA V5. Gap Healing How to use Gap Healing Curvature Improvement (Maximum Deformation) How to use Curvature Improvement Surface and Curve Sub-elements (Segmentation) How to keep Segmentation Migrating DETAILS SPACES used by Dittos Copying /Pasting Details and Dittos: Migration of unused Geometry from Details Migrating Isolated Mock-Up Solids Migrating V4 3D Text CATIA V5 requires its geometry to be C2-continuous. When non C2-continuous geometry must be imported from CATIA V4 to V5, this geometry (Curves, Surfaces) is first optimized and then broken down into a set of contiguous geometries (Faces, Edges), each of them being C2-continuous. This window allows you to optimize and control the quality of the geometry and to obtain C2 Continuity (deformation is possible). Open the .model of your choice. 1. Select the Tools -> Options... command. 2. Click Compatibility in the list of objects to the left of the Options dialog box. 3. Select the V4/V5 SPACE tab. You can customize V4->V5 SPACE settings. V4 Integration Version 5 Release 14 Gap Healing Gap Healing has an impact on External Control Points and not on Inner Control Points. External Control Points are modified according to the following options. In this category you have the choice between two options: ● Model relative value (corresponding to the Identical Curves Value defined by the model) External Control Points are modified according to the model's value or tolerance. ● User defined value (External Control Point Maximum Deformation) Here is a schema to explain the position of the External Control Points, before activating this option: Page 424 V4 Integration Version 5 Release 14 Page 425 And the displacement of the External Control Points after activating this option: When this option is activated, it allows you to fill in the gaps between two arcs/patches, and therefore to optimize the geometry. Both patches are joined because the External Control Points have merged. There is however a deformation tolerance and this process can give the Surfaces a C0 Continuity. The examples in How to use Gap Healing will help you to understand the results. How to use Gap Healing Open SURFACE_NON_C0_WITH_CURVE.model. In all these examples, the option Keep Segmentation is not activated. Example 1: 1. Select the following settings: 2. Copy / Paste the .model document into a CATPart. V4 Integration 3. Update the CATPart. External Control Points are modified according to the model's value or tolerance. Example 2: 1. Select the following settings: Version 5 Release 14 Page 426 V4 Integration 2. Copy / Paste the .model document into a Version 5 Release 14 CATPart and press the Update button. The number of cells is reduced because there is an optimization of the geometry. Example 3: 1. Select the following settings: 2. Copy / Paste the .model document into a CATPart and press the Update button. The patches are joined because the External Control Points have merged. Page 427 V4 Integration Version 5 Release 14 Page 428 Curvature Improvement (Maximum Deformation) For a Surface/Curve, the number of generated V5 Faces/Edges varies according to another parameter: the maximum value allowed for Control Point deformation. Curvature Improvement has an impact on Inner Control Points. Inner Control Points are modified (displaced) according to the value defined by the following options. If you select the Inner Control Point Maximum Deformation option, the Curvature Improvement value can be modified. ● Use the default value (corresponding to the Projection Point tolerance defined by the model) If you choose this option, the value which is taken into account is the maximum value between the V5 resolution value (10-3) and the Projection Point tolerance value (10-3 for instance, in V4) for a model dimension of 10 000m. For a model dimension of 10m, the standard value of the Curvature Improvement is 0.001mm (corresponding to the V4 model's value). In CATIA V4, the geometric standards are listed in the following dialog box: In order to understand the Curvature Improvement results, please refer to the paragraph entitled How to use Curvature Improvement. ● Inner Control Point Maximum Deformation (User Value) V4 Integration Version 5 Release 14 Page 429 If the Inner Control Point Maximum Deformation value is equal to 0, the geometry is broken and an edge is created for each patch limit. To decrease the number of cells/patches in the geometry, you need to select this option (default value) and to increase the tolerance/curvature improvement. The unit is the millimeter (V4 model unit in general). How to use Curvature Improvement Open SURFACE_CURVATURE.model Enter the parameters in the Curvature Improvement (Maximum Deformation) area, according to the maximum value allowed for deformation. In all these examples, the option Keep Segmentation is not activated. If the Curvature Improvement value is positive or equal to 0, the value appearing in the V4/V5 SPACE window is recommended as Maximum Deformation. These examples reveal the influence of Curvature Improvement variations. Example1: 1. Select the following settings: 2. Copy / Paste the .model document into a CATPart and press the Update button. V4 Integration Example2: 1. Select the following settings: 2. Copy / Paste the .model document into a CATPart and press the Update button. Version 5 Release 14 Page 430 Example3: V4 Integration Version 5 Release 14 1. Select the following settings: 2. Copy / Paste the .model document into a CATPart and press the Update button. The higher the Curvature Improvement value is, the fewer Faces there are. Tolerance is more important when Curvature Improvement is high, which means that a slight variation is allowed between the original document and the new one. Surface and Curve Sub-elements (Segmentation) When V4 Surfaces/Curves are migrated into CATIA V5, some Faces/Edges are created in V5. In order to keep a C2 continuity with the geometric objects, Surface and Curve subelements may be deformed and cut into several pieces (where they are not C2). Page 431 V4 Integration ● Version 5 Release 14 Page 432 Keep Segmentation By default, the Keep Segmentation option is not selected, the simplification of the geometry is active. If you want to reduce the geometry data size, select this option. If you want to keep the same number of sub-elements, deselect this check-box. For instance, two arcs and two surfaces with a C2 Continuity can be transformed into a single patch or arc in order to simplify the geometry. But if you keep the patch segmentation, these arcs and surfaces are not simplified. You can find an example in the section entitled How to Keep Segmentation. How to Keep Segmentation Open SURFACE_C2_WITH_3_PATCHES.model and copy / paste it into a V5 CATPart and update the V5 CATPart. Here are two examples illustrating the behavior of this setting: 1. When the Keep Segmentation option is not activated and the Curvature Improvement (Maximum Deformation) is 0.1mm, go into the FreeStyle Shaper workbench and copy/paste *SUR5 into a new Part. Select Surface.1 (*SUR5) and click the Geometric Information icon . The Geometric Analysis dialog box appears: V4 Integration Version 5 Release 14 Page 433 Geometry Analysis delivers the following information: Number of components U: 1 Number of components V: 1 -> only one component because you do not have selected the Keep Segmentation option. The default value of this option is taken into account and the Surface has been simplified. Without selecting the Keep Segmentation option, the nodes are removed and geometry is simplified within the tolerance. 2. When the Keep Segmentation option is activated and the Curvature Improvement (Maximum Deformation) is 0.1mm, go into the FreeStyle Shaper workbench and copy/paste *SUR5 into a new Part. Select Surface.1 (*SUR5) and click the Geometric Information icon . The Geometric Analysis dialog box appears: V4 Integration Version 5 Release 14 Page 434 Number of components U: 1 Number of components V: 3 -> 3 components because you have selected the Keep Segmentation option and it forces the numbers and boundaries of the arcs and patches to be kept. Migrating DETAILS SPACES used by Dittos If you want to make a special migration for Dittos, you can select one of the following settings: ● Usual optimized mode: corresponds to the normal and advised mode. You can select this option if you want to see the geometry (curves, lines, surfaces) non-used by the Solid and contained in the Detail's area. This is what we call "Isolated Wireframe Geometry". ● Like V4 explode mode: if you want everything to be migrated without CARWL, like the explode of a V4 model, you can select this setting. For more information about the Explode mode, please refer to Copy/Paste Details and Dittos: Force Detail to Explode in the V4 Integration User's Guide. Version 5 Release 14 V4 Integration ● Page 435 In order to have both isolated wireframe migration mode, you can check this option: Note: ● Be careful with the Explode and Isolated functionalities because memory size incidents may occur during the Paste operation or during the Save of the CATPart. When you have finished, do not forget to uncheck this option. To do it, just check the Usual optimized mode. ● ● Use one or the other setting, but not both at the same time. If you choose one of these settings, be careful because it will be also activated in the interactive mode and in the Batch mode (CATV4ToV5Migration). For information, the batch offers another way to migrate workspaces. Copy/Paste Details and Dittos: Migration of unused Geometry from Details This functionality allows you to get round the constricted migration of isolated Geometry from Details. The result is the same for the Geometry as if you had exploded all the Dittos in CATIA V4 and then migrated the *MASTER, but in our example below everything is made in CATIA V5. The Copy / Paste As Result With Link (CPARWL) is not used for the Geometry. And the process is unchanged for the Solids. Isolated Geometry or unused Geometry is not Geometry in use for Geometry or family building. For more information, please refer to: Optimizing V4 Migration: Deactivation of the V4 Parents' Filter in CATIA V4 Integration. For more information about the different modes of Detail Migration, please refer to one of the first sections above: Migrating DETAILS SPACES used by Dittos. Note: ● Be careful with the Explode and Isolated functionalities because memory size incidents may occur during the Paste operation or during the Save of the CATPart. When you have finished, do not forget to uncheck this option. To do it, just check the Usual optimized mode. ● ● Use one or the other setting, but not both at the same time. If you choose one of these settings, be careful because it will be also activated in the interactive mode and in the Batch mode (CATV4ToV5Migration). For information, the batch offers another way to migrate workspaces. V4 Integration 1. Select the Tools -> Options... Version 5 Release 14 command. 2. Click Compatibility in the list of objects to the left of the Options dialog box. 3. Select the V4/V5 SPACE tab. You can customize the following settings: 4. Check the option: Both isolated wireframe migration mode. 5. Open V4ToV5DetailGeomRequired_ODT.model in CATIA V5: 6. Copy/Paste (As Spec or As Result) *MASTER into a V5 CATPart. And you obtain: V4ToV5DetailGeomRequired.CATPart. Page 436 V4 Integration Version 5 Release 14 Page 437 Thanks to this option, all the Geometry of the Dittos is migrated, it is gathered under the corresponding OpenBody: for instance, the isolated Geometry of DIT12 is under OpenBody from DITTO *DIT12 in CATIA V5. If you do not use the option, the isolated Geometry of the Dittos is not migrated within a single Part but under the Detail. When you have finished, do not forget to uncheck this option. Migrating Isolated Mock-Up Solids Isolated Mock-Up Solids (SolidM) means that they do not have any history, any specifications. They can be converted (as Result) into CATIA V5 as CGR or as PartBody. Page 438 Version 5 Release 14 V4 Integration For the Isolated Mock-Up Solids' migration into CATIA V5, you can choose between: ● the SolidM conversion "as CGR" ● the SolidM conversion "as PartBody" 1. If you want to get only the meshing view (visualization mode), activate the setting "as CGR" in the option entitled "Isolated Solids Mock-Up Migration - Feature Result" in Tools -> Options -> General > Compatibility -> V4/V5 Space (by default, the "as CGR" option is checked): 2. If you want to be able to see the Geometry of the Solid, to edit it and obtain an exact Solid, you need to select the SolidM conversion "as PartBody". If you select the "as PartBody" option, you will also have the following message after the copy/paste of the SolidM into a CATPart: If you do not use the setting, the SolidM will be migrated as CGR. For more information about the Conversion of SolidM, please refer to the scenario entitled Conversion of SolidM entities as Result (migrated as a PartBody) in CATIA - V4 Integration User's Guide. Migrating V4 3D Text This task explains that you can choose to migrate or not CATIA V4 3D Text into CATIA V5 (V5 Annotatinos) via the Tools -> Options -> General -> Compatibility -> V4/V5 SPACE. There are some features containing 3D Text that are not migrated in CATIA V5. These exceptions are listed at the end of this scenario. After the migration, if you want to create 3D Annotations in CATIA V5, you can select Insert -> Annotations -> Text with Leader. ● In Tools -> Options -> General -> Compatibility -> V4/V5 Space, at the end of this tab, check this option Keep 3D Text: V4 Integration ● Version 5 Release 14 Open Annotation.model. This model contains two Annotations: 1. Copy *MASTER and Paste it As Special in a new CATPart. 2. Update the CATPart and you obtain: Page 439 V4 Integration Version 5 Release 14 Page 440 If the Keep 3D Text button is checked, the V4 3D Text is migrated as an Annotation in the CATPart. The Annotation is visible in the 3D Space and in the Specification Tree (a node called Annotation Set.1 appears). 3. If you did not check the Keep 3D Text option, you would have add this result: no Annotation in the 3D Space and a Geometrical Set node instead of an Annotation Set node. Limitations: V4 Integration Version 5 Release 14 Page 441 If the Keep 3D Text button is checked, the migration of V4 3D Texts into V5 Annotations is possible when they are associated to the following features: ● All geometrical objects: Points, Curves, Surfaces. ● Solids, Volumes and Skins if the Text is set on the Solid, on the Volume or on the Skin. If for instance, a solid is migrated and one of its Faces has an associated Text, this Text will not be migrated. ● Only Faces are migrated that is is to say out of the Solid's context, Skin's context, etc...). Concerning other elements (Dittos, Axis, etc...), the migration of V4 3D Text cannot occur. Version 5 Release 14 V4 Integration Page 442 V4 / V5 SPEC You can customize given options when using interoperability from version 4 to version 5. Open the .model of your choice. 1. Select the Tools -> Options... command. 2. Click Compatibility in the list of objects to the left of the Options dialog box. 3. Select the V4/V5 SPEC tab. Use of Step-by-step Update and Reroute: ● Step-by-step Update: If you select this option, you do not need to update your document after the copy/paste of a .model into a CATPart or a CATProduct. The update operation is automatic and you no longer need to press the update button: ● . Automatic Reroute: it is a means to use the geometry in order to recover the Edges and Faces. This functionality is applicable only with updated EXACT or SMART Solids. In interactive mode, this option is deselected by default. In batch mode, this check-box is selected by default. What is the reroute mechanism? When a contextual primitive (a Fillet, a Chamfrain, a Support or a Feature Draft) is unsolved in V5, the Modeler (in Part Design) is able to visualize the former geometric shape and the Fillet's Specifications. Draft feature migration mode: The V4 propagation edges for draft is done with SQUARE mode: In order to get the best V5 results (close to CATIA V4) from copying / pasting As Spec a model containing Drafts into CATIA V5, it is advisable to choose the Square mode. Indeed, this is the mode used in CATIA V4. Version 5 Release 14 V4 Integration Page 443 Open DRAFT_4_FACES.model. 1. Select the Square option and click OK, all the migrated Drafts (during the copy / paste As Spec from CATIA V4 to CATIA V5) will be migrated in this mode. 2. Select *MASTER and copy / paste it in a CATPart. 3. In the CATPart, DRAFT_4FACES_SQUARE.CATPart, double-click Draft.1 in order to see the Draft Definition window. In the Draft Definition window, you can see the property "Square" in the Draft Form field. Version 5 Release 14 V4 Integration Page 444 4. If the paste of a Draft or the update of the resulting Draft goes wrong, select the Cone mode. It will allow you to paste the Draft: 5. Select *MASTER and copy / paste it in a new CATPart. 6. In the CATPart, DRAFT_4FACES_CONICAL.CATPart, double-click Draft.1 in order to see the Draft Definition window. This time, the Draft Form is "Cone". V4 Integration Version 5 Release 14 Page 445 However, after you have copied / pasted the Draft in Cone mode and before leaving your CATIA V5 session, you should not forget to re-select the Square mode so that the Cone mode is not chosen by default in further sessions. V4 Integration Version 5 Release 14 Page 446 Migration Batch This task shows you how to customize Migration Batch settings. 1. Select the Tools -> Options... command. The Options dialog box appears with the category tree in the left-hand column. 2. In the General category of the Options Tree, select Compatibility and click the Migration Batch tab. Or when the Migration Batch window is open: 1. Select the Options button. The Batch Options dialog box appears with five tabs. 2. Click the Migration Batch tab. Migration Batch The following options are only useful in the Migration Batch context, not with interactive CATIA V5. V4 Integration ● Version 5 Release 14 Page 447 Format: Selecting the format of Migration in Batch Mode (AS SPEC or AS RESULT) By default, the format of this migration is AS SPEC, but the user can select the AS RESULT option. With the AS SPEC format, you can get the model's specifications in a first place and the geometry in a second place (after updating the document). Then you can modify the elements you have converted into CATIA V5. The AS RESULT format allows you to migrate the V4 elements that cannot be converted AS SPEC. And this operation is more efficient in terms of performance. ● V4 Part Definition A CATPart by Geometric Set: if you check this option, the "V4 Part" definition is the Geometric Set. Therefore, the subsets will be migrated into a V5 CATPart document. A CATPart by Solid: The "V4 Part" definition can also be a Solid. The Solids will be migrated into CATParts and the nonsolid elements (for instance: Wireframe) into a CATPart as well. ● Conversion Mode: Selecting the Migration of SPACE / DRAW data in Batch Mode: According to its content, a model is migrated into several documents : a CATPart and / or a CATProduct and / or a CATDrawing. It is possible to separate the treatment of SPACE data and DRAW data. In the Batch window, there is an Options button giving you access to this Tools-Options window and you can choose between Space And Draw, Space, and Draw. When a model contains DRAW data, they are migrated as a unique document : a CATDrawing. Some entities undergo a few changes during the V4 to V5 conversion: ● V4 DRAFT -> V5 Sheet ● V4 Detail -> V5 Detail Sheet ● V4 Views -> V5 Views In the Batch Mode, all Draw and Detail workspaces are migrated in CATIA V5. On the contrary, if you Copy / Paste a Draft or a View interactively, only referenced Details are migrated. Batch Migration of SPACE data: There are 2 Part definitions; the migration of each Set respects the definition determined by the "V4 Part definition" a few lines above. Every Workspace containing several Dittos or Set instances is converted as a CATProduct. Under this CATProduct, there are as many components as Dittos (Part or Product instances) and Sets. The impacts of the V4 to V5 conversion on the entities: ● V4 Set -> V5 Part ● V4 Detail -> V5 Part or Product ● V4 Model -> V5 Part or Product and/or CATDrawing ● V4 Ditto -> V5 Product component V4 Integration Version 5 Release 14 Page 448 Display Report Attribute: This functionality allows the visualization of 3D elements attributes in the Migration Report. For each element, the list of its attributes is displayed with the following data: ● The name of the attributes ● The value of the attributes The CATV4ToV5Migration interface is unchanged. The Report window displays attributes information. There are some limitations: ● Display of geometrical elements' attributes (2D and 3D elements) only. You can find the information about the 3D elements in the interactive report and about the 2d elements in the .rpt file. ● ● Display of only the attributes which have a value. For example, empty words that is to say words with no number are not displayed. Drawing Parameters Initial Drawing Path: Select a .CATDrawing document which will serve as a template. The standard used by this document will be used during the migration. If you leave this field blank, the standard used by default during the migration will be the last one you used when creating a drawing. Projection of Space for transparent views: Specify what kind of projection mode you want to use for transparent views during the migration: the NHR V4 mode, the HLR V4 mode or the same projection mode as the V4 model. Version 5 Release 14 V4 Integration ● Page 449 Mapping Files Location for Saving (to retrieve Multi Model Links) This functionality allows you to find pointed entities in V4 MML Solids and to retrieve associativity in CATIA V5. You can store them in the following directories: - Batch Target Directory - Model Directory: a mapping table per model is available; it is stored at the same place where the associated model is. - Source Directory: you can specify the directory path of your choice. ● Mapping Files Location for Retrieving When you migrate the pointing model, you need to know where the mapping table is, in order to retrieve the V5 entities. The mapping table has the same name as the model; this is why it is important not to change the name of the mapping table. It is also not recommended to rename V5 documents otherwise you will not be able to find them in the next migrations, and therefore to recreate the V5 associativity. If you cannot find the mapping table, a Migration As Result will take place: first, the pointed models are migrated and then the pointing models (asynchronous migration). If you cannot find the pointed element, the link between the models cannot be reproduced. Click Add repository to find the mapping table location. With the arrows (Up and Down), you can move in the list and with the rubber button , you can erase a file location. Migration Interface: V4 Integration ● Version 5 Release 14 Page 450 Interface Name: This option allows you to customize Applications' migration from CATIA V4 to CATIA V5. You can specify a particular behavior for this migration. You can choose how your applicative data will be migrated by writing source code (the name of the interface) in this empty field. Click OK to confirm. V4 Integration Version 5 Release 14 How to Manage V5 Introduction... V5 Introduction versus Industrial Processes V4 V5 Equivalences Page 451 Version 5 Release 14 V4 Integration Page 452 V5 Introduction versus Industrial Processes Different cases How can CATIA V4 data and applications operate in a CATIA V5 environment and vice versa? Interoperability or data transfer covers the following aspects : V4 data usage in V5 context : V4 to V5 Interoperability This business case can be used by firms introducing CATIA Version 5 in supplemental mode by using V5 for downstream activities based on V4 modeling. For instance, a design department has developed its whole project with CATIA V5 and they need to work on V4 elements in a V5 context . In this situation there is no conversion from CATIA V5 to CATIA V4 because of V4 models visualization and usability with downstream applications in V5 environment. Therefore, they can use simultaneously V4 Master Geometry and V5 workbenches (DMU and Analysis). This Direct Interoperability is illustrated in the following chart : V5 data usage in V4 context : V5 to V4 Interoperability For instance, an enterprise is not yet working with CATIA V5, and it is however using V5 documents (Master Geometry) in the context of V4 applications. This reverse Interoperability is nowadays used by Manufacturing. Migration or transformation covers the following aspects : a V4 environment to be converted into V5 : V4 to V5 Translation Having acquired CATIA V5 recently, a design department has to launch a new project based on legacy data for modification. For this reason they need to convert former V4 data into V5 data. This Direct Transformation can take place with the Copy As SPEC (Boundary Representation + Specifications) and Copy As Result (Boundary Representation) mechanisms. a V4 environment without any methodology in the use of V5 data : V5 to V4 Translation A downstream activity still working in V4 (Covering or Manufacturing) and receiving Master geometry from design office working in V5. This action is called Reverse Transformation : V4 Integration Version 5 Release 14 Page 453 V4 Integration Version 5 Release 14 Page 454 V4 / V5 Equivalences 1. Comparison of CATIA V4 and CATIA V5 This sketch allows you to make a comparison between CATIA Version 4 and CATIA Version 5. CATIA V4 made up of Configurations, Products, Functions, Articles and Entities whereas CATIA V5 is made up of Configurations, Workbenches, Toolbars, Icons and Objects. Mapping V4 to V5 based on software definition: 2. Equivalence between V4 Functions and V5 Toolbars V4 V5 Functions Icons and Toolbars In Sketcher Workbench SKETCHER A PROFILE MADE OF LINES AND ARCS A KEYHOLE PROFILE CURV2 CIRCLE V4 Integration LINE SPLINE CONIC AN AXIS BY USING TWO POINTS POINT SKETCHER LIMIT1 and TRANSFOR TRANSFOR CURV1 SOLIDE AND SOLIDM SOLIDE OPERATN Version 5 Release 14 Page 455 Page 456 Version 5 Release 14 V4 Integration 3. How to use CATIA V4 Libraries See: Using CATIA Version 4 Library 4. How to manage Layer Filters on CATIA Version 4 Models See: Managing Layer Filters on CATIA Version 4 Models 5. V4 V5 Files V4 V5 Solid .model 3D .CATPart Body Surface .model 3D .CATPart Open Body Wireframe .model 3D or 2D .CATPart Open Body FEM .model 3D .CATAnalysis 2.5 NC .model 3D CATProcess Drawing .model DR .CATDrawing .model Ditto Part Positioning .session .CATProduct .asm Positioning Constraint .asm .CATProduct Kinematics .model Set .CATProduct Application Library .lib .catalog PRJ Native Data Description 6. V4 / V5 Entities : Click on the V4 / V5 Entities document. This document will help you to recognize and understand important concepts about the migration of the V4 entities into CATIA V5. It is an introduction to the tasks illustrating the results of V4 Interoperability. V4 Integration Version 5 Release 14 a. V4 Data Browsing Open the Table about V4 Data Browsing. This table offers you some results about the possibility to read V4 data into V5. b. V4 Data Conversion Open the Table about V4 Data Conversion. In this table you can see the results of the V4 to V5 Migration. Page 457 V4 Integration Version 5 Release 14 Using CATIA Version 4 Libraries Opening V4 Library Objects in V5 on Windows Opening V4 Library Objects in V5 on UNIX Displaying V4 Library Keywords in V5 Applying Filters to V4 Library Families Converting V4 Library Objects into V5 CATParts Converting V4 Libraries into V5 Catalogs Page 458 Version 5 Release 14 V4 Integration Page 459 Opening CATIA Version 4 Library Objects in CATIA Version 5 on Windows This task shows you how to open a CATIA Version 4 library object in CATIA Version 5 on Windows. Make sure that an http server has been installed on the machine where the objects reside. A CATIA Version 4 library is a means of storing objects such as details, symbols, NC mill and lathe tools and beam sections. A library is made up of a number of families each of which contains objects. Keywords are attributed to these families to enable classification and easy retrieval of the objects contained in them. For more information about V4 libraries, see the CATIA.Library Reference Manual Version 4. Just like Version 4 models, Version 4 library objects cannot be edited as such. However, it is possible to convert the library objects into CATPart documents. Read-only operations are of course allowed. Accessing CATIA Version 4 library objects does not modify these objects. Only SPACE details can be read in CATIA Version 5. Other library objects such as DRAW details, symbols, sections and tools cannot be read in CATIA Version 5. A SPACE detail that points to external library objects can be read only if all the objects pointed to are SPACE details. This means, for example, that no detail containing structure pointing to a section can be read. 1. Click the Open icon or select the File->Open command. 2. In the File Selection dialog box, enter, in the field File name, the whole address of the library object you want to open, including the library name, as shown below. If you enter the wrong location or if the library name cannot be found, exit the dialog box and start over. The address to be specified should look something like this: http://UNIXserver:port/libraryobjectlocation/libraryname Version 5 Release 14 V4 Integration Page 460 The name of the library appears. 3. Double-click on the library name to display the library families. Then double-click on one or more of the objects belonging to these families, SCREWS and NUTS in the example shown below, to see the whole structure of the library. A dialog box similar to this is then displayed: V4 Integration Version 5 Release 14 Page 461 4. To open a library object, double-click on it. Alternatively, select the library object, right-click and select Open. The result, providing you with CATIA Site Navigator capabilities, is as follows: V4 Integration Version 5 Release 14 Page 462 Library objects residing on UNIX can of course also be accessed from UNIX. To see how, refer to Opening CATIA Version 4 Library Objects in CATIA Version 5 on UNIX. Version 5 Release 14 V4 Integration Page 463 Opening CATIA Version 4 Library Objects in CATIA Version 5 on UNIX This task shows you how to open a CATIA Version 4 library object in CATIA Version 5 on UNIX. Just like Version 4 models, Version 4 library objects cannot be edited as such. However, it is possible to convert the library objects into CATPart documents. Read-only operations are of course allowed. Accessing CATIA Version 4 library objects does not modify these objects. Only SPACE details can be read in CATIA Version 5. Other library objects such as DRAW details, symbols, sections and tools cannot be read in CATIA Version 5. A SPACE detail that points to external library objects can be read only if all the objects pointed to are SPACE details. This means, for example, that no detail containing structure pointing to a section can be read. 1. Click the Open icon or select the File->Open command. 2. In the File Selection Box, select the file location. 3. Click the Files of type: list, select library as the document type. The File Selection dialog box is displayed: V4 Integration Version 5 Release 14 Page 464 Note that the items displayed in this dialog box do not correspond to the hierarchical structure of the library. Families and library objects are displayed at the same level. For more information about this, refer to the CATIA.Library Reference Manual Version 4. 4. To access the library family list, double-click on either *LISFAM.library or *MASTER.library. Both these files are required for library management purposes. The name of the library appears. Double-click on the library name to display the library families. Then double-click on the objects belonging to these families, SCREWS and NUTS in the example shown below, to see the whole structure of the library. The following dialog box is then displayed: V4 Integration Version 5 Release 14 Page 465 5. To open a library object, double-click on it. Alternatively, select the library object, right-click and select Open. The result, providing you with CATIA Site Navigator capabilities, is as follows: Version 5 Release 14 V4 Integration Page 466 6. To access a family directly, double-click one of the following: ● family_name_____ FAMILY______DESCRIPTOR.library ● family_name______FAMILY______ELEMENT.library. Both these files are required for library management purposes. A dialog box appears showing the name of the family. Double-click on this family name to display the whole structure of the family then double-click on a library object to open it. Alternatively, select the library object, right-click and select Open. The result is the same as above. 7. To access a library object directly, select it in the File Selection dialog box. The result is the same as above. Library objects residing on UNIX can also be accessed from Windows using the http protocol. To see how this is done, refer to Opening CATIA Version 4 Library Objects in CATIA Version 5 on Windows. V4 Integration Version 5 Release 14 Page 467 Displaying CATIA Version 4 Library Keywords in CATIA Version 5 This task shows you how to display CATIA Version 4 library keywords in CATIA Version 5. Remember that in CATIA V4, some properties associated with a family, called keywords, can be assigned to objects of the given family. Have a library structure open in CATIA Version 5 showing the families and objects it contains as shown below: Version 5 Release 14 V4 Integration Page 468 1. Select the library object whose keywords you want to display (FHC M03*05, for example) and right-click. 2. In the menu that appears, select Show Keyword... 3. There appears a list of the keywords for the library object selected: 4. Click OK to close the list. If a family's keywords are linked to PROJECT file attributes make sure you specify the PROJECT file path in the Compatibility tab of the Options dialog box (displayed using the Tools->Options command). V4 Integration Version 5 Release 14 Page 469 Applying Filters to CATIA Version 4 Library Families This task shows you how to apply a filter to a CATIA Version 4 Library family in CATIA Version 5. Have a Version 4 library and its contents open as shown below. Version 5 Release 14 V4 Integration Page 470 1. In the dialog box above, display all the objects contained within one or families, SCREWS and NUTS for example, by clicking on the plus sign opposite the family name, select the family name and right-click. 2. Select Filter... in the menu that appears: 3. The dialog box below is displayed: V4 Integration Version 5 Release 14 4. Complete the fields, then click Apply to redisplay the whole family structure. 5. Click Reset to display the whole family structure as it was prior to the filter application. Page 471 V4 Integration Version 5 Release 14 Page 472 Converting CATIA Version 4 Library Objects into CATIA Version 5 CATPart Documents This task shows you how to convert a CATIA Version 4 library object into a CATIA Version 5 Part document. Have a library structure open in CATIA Version 5 showing the families and objects it contains. 1. Select the library object and right-click. 2. In the menu that appears, select either: Version 5 Release 14 V4 Integration ● Page 473 Convert to Part As Spec... to convert the object into a V5 CATPart document as specifications (identical to the operation described in Copying CATIA Version 4 Model Data to CATIA Version 5). Or: ● Convert to Part As Result... to convert the object into a V5 CATPart document as geometry(identical to the operation described in Copying CATIA Version 4 Model Data to CATIA Version 5). A new window is displayed showing the converted object. The selected library object is now displayed as a new Part (equivalent to creating a Part and performing a copy/paste operation) and you are provided with all the Part Design workbench capabilities. You may now want to click the Fit All In icon Alternatively, you can of course: to fit all data in the window. 1. open the library object 2. copy/paste it into a Part already open in your CATIA session. However, before pasting any V4 elements into a Part document be sure to read "About Copying CATIA Version 4 Models to CATIA Version 5". If details reference other subdetails the whole of the geometry is exploded in one single CATPart document. Version 5 Release 14 V4 Integration Page 474 Converting CATIA Version 4 Libraries into CATIA Version 5 Catalogs This task shows you how to convert a CATIA Version 4 library into a CATIA Version 5 catalog. Before embarking on any conversion make sure you are familiar with the concepts described in "About Catalogs" in the CATIA - Component Catalog Editor User's Guide. It would also be instructive to read "Converting CATIA Version 4 Library Objects into CATIA Version 5 CATPart Documents". Migrating the Data Structure The batch operation creates a catalog chapter for each DETAIL type library family (see Creating a Catalog in the CATIA - Component Catalog Editor User's Guide). Other types of families (SYMBOL, SECTION, NCMILL, NCLATHE) cannot be converted. The keywords relating to the library family are converted into catalog keywords as shown in the table below. These keywords define the associated chapter. V4 Keyword Type V5 Keyword Type Discrete String Alphanumeric String Numeric Real (no unit retrieval) Boolean Boolean The Library structure is migrated into a catalog structure, with the following architecture: ● one root catalog file containing the root chapter ● one catalog file for each migrated family and specific files (CATParts and CATDrawings) for the actual data (see below: Migrating the Actual Data). The multi-file catalog has the following benefits: ● ● ● enhanced migration performance because of reduced catalog file size enhanced catalog usage, for only the necessary subset of the catalog files will be loaded in the catalog browser for browsing and/or instantiation the generated catalog families can easily and independently be reused to build other new catalogs. Migrating the Actual Data Bear in mind the following: ● ● No link is kept between the V4 library and the new V5 catalog. SPACE details can be migrated to CATIA Version 5 i.e. converted into CATPart documents. Other library objects such as symbols, sections and tools cannot be migrated. ● ● ● ● ● Page 475 Version 5 Release 14 V4 Integration DRAW details can be migrated to CATIA Version 5 i.e. converted into CATDrawing documents. If details reference other subdetails the whole of the geometry is exploded in one single CATPart document. Only DETAIL type families are converted into a catalog chapter. Regarding Solid Mockup copy/paste: when copying as CATIA_RESULT or when the solid mockup is isolated, it is stored in a .cgr format in the directory where the catalog is generated. When the copy/paste of a solid is partial, an open body is created in the part. For more information about the copying of V4 data to V5, see Copying CATIA Version 4 Models to CATIA Version 5. Consequences of Migration on Filenames In Windows, it is extremely important to be aware of the consequences of migration on filenames. Before reading any further see "About Filenames" in the CATIA - Infrastructure User's Guide. In view of the restrictions described in this section, the following default conversion table will apply to new CATPart documents converted from library objects: ASCII Code of the Original Character Character to be Replaced New Character String 0x22 0x2a 0x2f 0x3a 0x3c 0x3e 0x3f 0x5c 0x7c " * / : < > ? \ | _Inch x _ _ _ _ _ _ _ National characters will be replaced by default by _xxx where xxx is the ASCII code of the character replaced. The default correspondence table can be modified but you cannot avoid the replacement of these characters. If, for example, you delete the line l''*' the table will be declared invalid. The two characters most likely to occur are: ● 0xb1 ● 0xb4 which correspond to the characters used in V4 model names as replacements for the blank character " " and slash character "/" respectively. To avoid excessively long document names it is advisable to modify the default conversion table. Only national characters and those characters not supported by Windows can be declared in the correspondence table. For example, you cannot decide that you want to change all characters from "a" to "w". Page 476 Version 5 Release 14 V4 Integration If you have declared all the national characters not supported by Windows, you can replace the national characters supported by Windows as follows: ASCII Code of the Original Character Character to be Replaced New Character String 0x61 a A As a consequence, "a" will be replaced by "A". The scenario described below shows the consequences of: ● data structure migration ● actual data migration ● consequences of migration on filenames. Conversion of very large V4 Libraries The conversion of very large V4 libraries uses a lot of resources (memory, CPU and disk space for generated files). In case the batch fails before the end of the conversion due to any reason (lack of memory, individual detail conversion failure, disk full, …) you can restart it using the Rattrap mode that will continue the job starting from where it was just before the failure. Following are guidelines regarding this special process mode: ● first, launch your CATIA V4 library conversion as usual (using MIGRATION mode) ● if it fails, modify the script so that the new mode is RATTRAP ● start the script again: the conversion will continue from where it stopped ● if it fails again for the same reason, start the script again until the whole library is converted Take care not using this RATTRAP mode for any other reason. At any time, you are able to check the converted catalog, using the File / SaveAs… capability on the generated catalog file. Choosing "txt" format will output a printable text file that dumps the catalog structure, enabling to quickly identify missing converted details, for example. Before, to be able to use the CATScript file in order to run the batch operation, you had to make sure that the CclTypeLib library was loaded. You had to select the Tools->Options->General command manually and click the Automation tab. But now the CclTypeLib library is automatically declared. Version 5 Release 14 V4 Integration Page 477 1. Open the document ConvertLibrary.CATScript It looks like this: Abstract: Conversion batch of V4 Libraries in V5 Catalogs. The generated report file (*.report) is located in the same catalog directory with the same catalog name. Language="VBSCRIPT" Sub CATMain() ' The following valuated parameters (AS_SPEC = 0 ' and AS_RESULT = 1) define the conversion format ' option of the space details in parts. DO NOT MODIFY ' these values; they are mandatory and reserved for ' the running application. AS_SPEC = 0 AS_RESULT = 1 ' Choose a conversion format by specifying the value ' AS_SPEC or AS_RESULT ' (e.g. CONVERSION_FORMAT = AS_SPEC). CONVERSION_FORMAT = AS_SPEC ' The following valuated parameters (MIGRATION = 0 ' and SIMULATION = 1 and RATTRAP = 2) define the batch mode option. ' DO NOT MODIFY these values; they are mandatory ' and reserved for the running application. MIGRATION = 0 SIMULATION = 1 RATTRAP = 2 ' Choose the desired batch mode by specifying ' the value MIGRATION or SIMULATION ' (e.g. BATCH_MODE = MIGRATION). V4 Integration Version 5 Release 14 BATCH_MODE = MIGRATION ' Specify the absolute UNIX directory of the V4 ' library. In Windows, use the http protocol and ' take care of the / separator on UNIX ' (e.g. libraryDirectory ' = "http://machine_name/../../FASTENERS"). libraryDirectory = "http://../../FASTENERS" ' ' Specify the catalog name (with its extension) ' the catalog filename correspond to the name of the ' sub-directory containing the V4 libraries. ' This parameter is used to open the catalog in RATTRAP ' mode ' It will not be used in the others (MIGRATION or ' SIMULATION) modes ' e.g: ' if libraryDirectory is set to '/u/users/xxx/LIB' ' then, catalogName has to be set as 'LIB.catalog' catalogName = "LIB.catalog" ' Specify the absolute directory of the catalog. In ' Windows, take care of the \ separator ' (e.g. catalogDirectory = "E:\..\..\catalog") ' All catalog files will be generated in this directory (one per family). catalogDirectory = "E:\..\..\Catalog" ' Specify the absolute UNIX directory of the V4 project ' if the V4 library needs one ' (e.g. projectDirectory ' = "http://machine_name/../../project"), ' otherwise, you have to specify an empty one ' (e.g. projectDirectory = " "). projectDirectory = "http://../../Interop" 'projectDirectory = " " ' Specify the absolute path of the character ' conversion table to convert V4 file names of details Page 478 V4 Integration Version 5 Release 14 Page 479 ' and families in V5 file names of parts and chapters ' (e.g. tablePath = "E:\..\..\table.txt"), or indicate an ' empty one if you want to use the default installation ' (e.g. tablePath = ""). tablePath = "E:\..\..\table.txt" ' Creates a CatalogDocument type document. DO ' NOT MODIFY the following declaration and valuated ' parameters ' (Dim Catalog As Document and ' Set Catalog = ' CATIA.Documents.Add("CatalogDocument")). Dim Catalog As Document if ( BATCH_MODE = RATTRAP ) then Set Catalog = CATIA.Documents.Open(catalogDirectory & "/" & catalogName) else Set Catalog = CATIA.Documents.Add("CatalogDocument") end if ' Calls CreateCatalogFromLibrary method on Catalog. ' DO NOT MODIFY the following declaration related to ' previous variables ' (Catalog.CreateCatalogFromLibrary ' libraryDirectory, ' projectDirectory, ' catalogDirectory, ' tablePath, ' CONVERSION_FORMAT, ' BATCH_MODE). Catalog.CreateCatalogFromLibrary libraryDirectory, projectDirectory, catalogDirectory, tablePath, CONVERSION_FORMAT, BATCH_MODE ' To perform automatically the close of the newly created ' catalog, decomment the Catalog.close command, ' otherwise put the command in comments. Catalog.Close End Sub Version 5 Release 14 V4 Integration Page 480 2. Adapt the CATScript file to your needs by selecting the settings you want to use (for CONVERSION_FORMAT and BATCH_MODE) and by providing the different paths required for the batch (libraryDirectory, catalogDirectory, projectDirectory and tablePath). The comments relating to these settings and paths are shown above in red. As you can see, this file, written in the VBScript language, contains the information required to batch-convert a V4 library into a V5 catalog file in the location you specify. It can be used on both Windows and UNIX. (Do not forget to use the http protocol on Windows to access the library and the PRJ file.) In the example above the CATScript file contains just one set of instructions to batch-convert a single library. However, a CATScript file can of course include several series of instructions for the conversion of several libraries. 3. Close the file when you have finished. 4. If you now wish to act on the information above and modify the string to replace one of the characters in the default conversion table, open the file table.txt and make the changes required. 5. You are now ready to run the batch operation. Select the Tools ->Macro->Macros command. 6. In the dialog box that appears, select the external file and the appropriate ConvertLibrary.CATScript file. Make sure that at the bottom of the box External File is selected indicating the location of the macro. Click on Run. Example Let us suppose you have a V4 library called FASTENERS on your UNIX machine. This library has two DETAIL type families: SCREWS and NUTS. The migration will now create a chapter called FASTENERS in the document FASTENERS.catalog. For each DETAIL type family an end chapter will be created i.e. a chapter called SCREWS in the document SCREWS.catalog and a chapter called NUTS in the document NUTS.catalog. These end chapters are both referenced by the FASTENERS chapter which is the highest-level entry point in the catalog. The migration does several things one of which is the conversion of the keywords of each V4 family to keywords in V5 that define the end chapters SCREWS and NUTS. The library family SCREWS, for example, has four keywords that are converted as follows: Existing V4 Library Family Keywords Created V5 Catalog Keywords Version 5 Release 14 V4 Integration REFERENCE an alphanumeric keyword REFERENCE a string keyword TYPE a discrete keyword with the possible values: CHC, FHC, H and HC TYPE a string keyword Page 481 DIAMETER DIAMETER a numerical keyword with millimeter (mm) as the unit a real keyword LENGTH LENGTH a numerical keyword with millimeter (mm) as the unit a real keyword It should be noted that discrete keywords are converted to strings and that units are NOT converted. The migration then assigns the chapters as many descriptions as there are converted objects, retrieves the values of the keywords related to the object and establishes a reference to the Part resulting from the migration of the detail. For example, the object CHC M05*06 has the following characteristics: REFERENCE CHC M05*06 TYPE CHC DIAMETER 5,0 LENGTH 6,0 The description in the chapter will have the same values. The migration also converts the geometry of the detail into a Part whose name must be made up of V5-compliant characters (see Consequences of Migration on Filenames above). The asterisk is a character that is not supported by Windows and not available in V5 and so the Part cannot be named CHC M05*06.CATPart. The V4->V5 correspondence table is therefore applied. If you had already supplied a conversion table containing: 0x2a * x the part created will be given the name CHC M05x06.CATPart. Version 5 Release 14 V4 Integration Page 482 If, in the CATScript file, you chose SIMULATION the batch operation will: ● generate a report in the same location as the catalog file, allowing you to verify whether migration would be successful or not ● detect errors in data migration ● detect possible occurrences of V5 names following the conversion of V4 names into V5 names. If more than one occurrence of the same V5 name is detected the older CATPart documents are overwritten. You are therefore strongly advised to modify the conversion table so that CATParts are not created with the same name. If, in the CATScript file, you chose MIGRATION the batch operation will generate: ● a report in the same location as the catalog file, allowing you to verify successful migration ● a catalog with the name of the library. If a library is migrated to the same directory twice the catalog (both catalog and CATParts) generated by the previous migration is overwritten by the new one. If, in the CATScript file, you chose RATTRAP the program locates the last converted objects then continues with the next ones. It will generate: ● a report in the same location as the catalog files, allowing you to verify successful migration. ● a catalog with the name given as input The library is migrated to the same directory and the catalog files generated by the previous migration is overwritten by the new one. 7. If you want to open the catalog you have just created see "Navigating Through a Catalog" in the CATIA - Component Catalog Editor User's Guide. Version 5 Release 14 V4 Integration Page 483 Managing Layer Filters on CATIA Version 4 Models This task shows you how to apply, create, modify and delete layer filters on a CATIA Version 4 model. Once you have assigned objects to layers, you then create visualization filters (refer to "Using Visualization Filters" in CATIA - Infrastructure User's Guide) which allow you to display only those objects located on specific layers referenced by the visualization filter. Open the document LAYER_FILTER.model. 1. Open the model. You should see this. 2. To apply, create, modify or delete an existing filter that was defined in Version 4, select the Filter->Layer Filter... command The Layer Filter dialog box appears: Version 5 Release 14 V4 Integration Page 484 The first two filters in the Available Filters list are always ALL and LAYCUR (current layer). If you select ALL in the Available Filters list and click the OK or Apply button, the cube object, on which Layer2 is applied, becomes visible because its geometry was assigned to Layer2. ALL takes into account all the layers on which the objects are located. 3. To apply an existing filter, select the filter ALL EXCEPT LAYER 2 in the Available Filters list and click the OK or Apply button: Version 5 Release 14 V4 Integration Page 485 4. In the Layer Filter dialog box, click the Apply button if you have other operations to perform. If not, click the OK button. The model then looks like this: Version 5 Release 14 V4 Integration Page 486 5. To create a new filter, select, in the Layer Filter dialog box, the Create button. The Create Filter dialog box appears: 6. In the Create Filter dialog box, select one or more of the layers in the list displayed. If you want to give the new filter a name you can enter it in the Name field: Version 5 Release 14 V4 Integration Page 487 7. Click the OK button. The filter created is added to the Available Filters list in the Layer Filter dialog box: If you create (/ obtain) or modify a Filter that already exists in the Filter list, the Filter cannot be created or modified and a Warning appears telling you that: "This filter already exists in the existing file". 8. In the Layer Filter dialog box, click the Apply button if you have other operations to perform. If not, click the OK button. 9. To modify a filter, select, in the Layer Filter dialog box, a filter that you have created. 10. Click the Modify button. The Modify Filter dialog box appears: V4 Integration Version 5 Release 14 Page 488 11. Make the changes. You may wish to change the name of the filter(s) and/or modify filter selection. Bear in mind that you cannot modify filters defined in CATIA Version 4 (the Modify button is grayed out). Only those filters defined in CATIA Version 5 using the Create button can be modified. 12. Click the OK button. 13. The modified filter is added to the Available Filters list in the Layer Filter dialog box. Version 5 Release 14 V4 Integration Page 489 14. In the Layer Filter dialog box, click the Apply button if you have other operations to perform. If not, click the OK button. 15. To delete a filter, select one or more filters in the Layer Filter dialog box. 16. Click the Delete button. Bear in mind that you cannot delete filters defined in CATIA Version 4 (the Delete button is grayed out). Only those filters defined in CATIA Version 5 using the Create button can be deleted. 17. In the Layer Filter dialog box, click the Apply button if you have other operations to perform. If not, click the OK button. If you copy / paste AS RESULT or AS SPEC this model containing layer filters into a CATPart, in both cases the layers' numbers and the Filters are transferred into CATIA V5. Then you have the possibility to create additional filters in CATIA V5. Page 490 Version 5 Release 14 V4 Integration V4 / V5 Entities This document provides information for users on interoperability prerequisites and migration results. It aims at illustrating the several stages of migration the user may encounter. Through the different tasks placed at your disposal, you can learn how to re-use V4 Data into CATIA V5. Concept Definitions : ● ● Copy AS RESULT : you copy the V4 entity's Geometry (but not its Specifications). Copy AS SPECIAL : You copy the Geometry and the Specifications, you create another entity thanks to the Geometric Modeler. The V4 Specifications are generated in CATIA V5. Depending on the V4 entities' characteristics, you can: ● browse the V4 model (Read only) and/or ● edit its semantic characteristics and/or ● associate that is to say modify a model's geometry in CATIA V4 and find back the modifications in CATIA V5 (Links between V4 data will be transferred as links between V5 data). Click on the hyperlinks (light blue color) in order to access to the tasks illustrating the V4 entities' migration. Some entities belonging to one category are gathered within the same scenario. Others, belonging to the same category, are not present within the same sample, but it is specified when they have the same behavior in the V4 to V5 Migration. SPACE Elements Wireframe: Point Parabola Clouds of Points Hyperbola Line Composite Curve Curve NURBS Curve Circle Planes Ellipse Z-Edges Surfaces: Patch Face Multi-Patches Surfaces Skin NURBS Surfaces Procedural Skin Page 491 Version 5 Release 14 V4 Integration Net Volume Solids: Primitives In order to see the corresponding scenario (Cuboid, etc...), please refer to V4/V5 Part Design Data Migration. Cuboid 3D Sweep Cylinder Sweep Until Sphere Sweep non close Cone Offset Torus Close Revolution Project Prism Volume Pipe Macro-Primitive Pyramid Support Edge Sweep Sweep Spine Contextual and Transformation Primitives In order to see the corresponding scenario (Fillet, etc...), please refer to V4/V5 Part Design Data Migration. Split Constant Edge Fillet Fillet Rolling Edge Fillet Face-Face Fillet Variable Radius Fillet Tritangent Fillet MultiEdge Fillet Rolling Edge Fillet Basic Draft Draft from Reflect Line Draft Both Sides Draft Multi-Neutral 2D / 3D Kinematics: Revolute joint pt/sur Actuator joint u joint Page 492 Version 5 Release 14 V4 Integration PT / PT cv joint Planar gear Prismatic rack Rigid cable pt/crv screw roll/crv command slid/crv fixed part Law Fitting Entities: Route (track +shuttle) Infrastructure / Structural Entities Model Detail / Ditto Session (Reference mode) Macro-Primitive Library (SPACE Details) Color Tables Show / No Show Models Naming Layers (Layer Filters) Models Comments Geometric Sets Tolerances DRAW Elements Wireframe: Point Parabola (PARD) Line Hyperbola (HYPD) Curve Spline Circle (CIRD) Shape > Open Page 493 Version 5 Release 14 V4 Integration > Closed > Closed / Approximated Ellipse (ELLD) Annotations and Dress-up: Dimensions >Distance > Length on line > Length on circle > Angle between lines > Angle on circular arc > Radius / TGT > Radius / CNT > Radius / Edge > Radius / cylinder > Radius on curve > Diameter / TGT > Diameter / CNT > Diameter / Edge > Diameter / Cylinder > Diameter on curve > Diameter on cone > Chamfer > Slope > Coordinate dimension > Distance dim. System Text > Simple Text > Note (text with leaders) > GD&T > Datum target > Datum Feature > Ballon > Roughness symbols Text detail Arrow Pattern Raster Insertion Infrastructure: Ditto PRJ Model Detail PRJ File Symbol Occurrence PRJ (T&C Table) View PRJ (Pattern Table) Transparent View PRJ (Attribute Table) View Framing Back Up Version 5 Release 14 V4 Integration Page 494 Wireframe and Surface Elements This task shows you how the V4 Entity is copied As Result into CATIA V5. Open the document WIREFRAME.model in CATIA V5. It contains a number of Wireframe elements, such as points, lines, curves, circles, and so forth, as well as Surface elements (net surface, for example). 1. Visualize the Wireframe and Surface elements The V4 Model is in the No SHOW space : 2. Apply a Check As Spec on the .model. The Check Validity dialog box appears : Version 5 Release 14 V4 Integration 3. Click OK in the Check Validity dialog box. 4. Select the *SET entity and choose the Copy contextual menu. 5. Click the New icon and select Part from the New dialog box, to open a .CATPart document. 6. Click OK. 7. Select the Part1 from the specification tree and choose the Paste Special contextual menu. Page 495 V4 Integration Version 5 Release 14 8. The Paste Special dialog box is displayed. Choose the paste AS_RESULT option and click OK. All the Wireframe and Surface elements are copied into the .CATPart document. Page 496 Page 497 Version 5 Release 14 V4 Integration 9. Update the document, either using the Update icon, or the Edit -> Update menu. The copied elements cannot be edited, however they can now be used as input for CATIA V5 elements. To sum up : V4 to V5 Migration As Result As Spec SPACE Elements Wireframe *PT Point Point Datum N/A *CPT Clouds of Points V5 Clouds of Points N/A *LN Line Line Datum N/A Page 498 Version 5 Release 14 V4 Integration *CRV Curve Curve Datum N/A Circle (CIR) Curve Datum N/A Ellipse (ELL) Curve Datum N/A Parabola (PAR) Curve Datum N/A Hyperbola (HYP) Curve Datum N/A *CCV Composite Curve Curve Datum N/A *NRBC NURBS Curve Curve Datum N/A *PLN Planes Plane Datum N/A V4 Integration Version 5 Release 14 Page 499 Axis This task shows you how different Axes or trihedrons (Reference Axis and Relative Axis) are copied using the option CATIA_SPEC into CATIA V5. Open the document TEST_AXIS.model in CATIA V5. Slightly turn the geometry elements to be able to see 4 axes. This model contains 4 axes: ● 1 Reference Axis: *AXS4 ● 3 Relative Axes (fixed and unfixed trihedrons): *AXS1, *AXS2, *AXS3. 1. Apply a Check AS SPEC on the .model. V4 Integration Version 5 Release 14 Page 500 2. Copy and Paste Special the Model into another CATPart document using the CATIA_SPEC option and update your document to compute the geometry. V4 Integration Version 5 Release 14 Page 501 Axis System.2 corresponds to the Reference Axis *AXS4. The Relative Axes (fixed and unfixed axes) have been migrated into: Axis System.1, Axis System.3 and Axis System.4 in CATIA V5. You have access to the model's geometry and specifications. Therefore, you can now modify each feature of the V5 CATPart document. Double-click an axis in the Specification Tree or in the Geometry space and the following dialog box appears: V4 Integration Page 502 Version 5 Release 14 You can modify the axis parameters in CATIA V5. To sum up : V4 to V5 Migration CATIA_SPEC SPACE Elements Primitives Axis (Reference Axes, Relative Axes) Axis or Trihedron Cuboid Pad/Pocket Cylinder Pad/Pocket Sphere Shaft / Groove Cone Shaft / Groove Torus Shaft / Groove Revolution Shaft / Groove Prism Pad / Pocket Pipe - Center Curve Rib / Slot Pyramid Solid Datum Sweep Rib / Slot Sweep Spine Solid Datum 3D Sweep Rib / Slot Sweep Until Solid Datum Sweep non close Solid Datum V4 Integration Version 5 Release 14 Offset Thick Surface Close Close Project Solid Datum Volume Solid Datum Import (with MML link) Solid Datum Not Supported Primitive Solid Datum (if the solid is smart) Page 503 V4 Integration Version 5 Release 14 Page 504 Transfer of SPACE Entities: Visualization of V4 Support Edge for Broken Contextual Features This task shows you how to visualize a V4 Support Edge that was not transferred in V5 geometry during the conversion of CATIA Version 4 models into CATIA Version 5. V4 Data conversion through Copy / Paste is useful but contains a few restrictions, only V4 geometry is migrated and cannot be edited. In the following example, the Copy As Special process is used; therefore the Specifications are generated in V5. Open the document : DEMO_MANUAL_REROUTE.model in CATIA V5: 1. Create a new document in CATIA V5, a new part, Part1. Both documents can be open in the same CATIA window : V4 Integration Version 5 Release 14 Page 505 2. Copy / Paste As Special the .model in Part1. A Paste Special dialog box appears, select CATIA_SPEC and click on OK : At this step, only specifications or definitions have been built; they are visible in the Specification Tree of Part1. Here is a part of the Specification Tree : V4 Integration Version 5 Release 14 Page 506 3. Update the document, Part1, so that the geometry calculation operates. When the update is finished, an Update Diagnosis dialog box is displayed : V4 Integration Version 5 Release 14 Page 507 The error is in definition of the Edge.Fillet.6 corresponding to the V4 Fillet ($FILL14) and it cannot be placed into the geometry. 4. Press the button Edit in order to modify the Fillet and the error is explained in a new dialog box entitled Feature Definition Error. Click on OK to delete the Edge. 5. Select the object (highlighted with yellow dots) to be filleted in the Edge Fillet Definition dialog box. The radius (R3 in green) and Propagation correspond to the V4 data that have been kept during the transfer. Before you select the Edge : V4 Integration Version 5 Release 14 After the selection : 6. Click on OK : the calculation of the fillet geometry is launched. The result in V5 is : Page 508 V4 Integration Version 5 Release 14 Page 509 Both objects in V4 and V5 are similar and you can now modify the V5 CATPart in CATIA Version 5. At the same time there is an additional element, Pad.3 ($CYLN18) present in the geometry space. In this transfer, the V4 geometric curve is migrated into V5 and it is visualized in yellow. This is what we call the reroute mechanism : a contextual primitive (a Fillet, a Chamfrain, a Support or a Feature Draft) is unsolved and the Modeler (in Part Design) is able to visualize the former geometric shape and the Fillet's Specifications when they are not solved in V5. V4 Integration Version 5 Release 14 Split This task shows you how the V4 Split entity is copied As Result into CATIA V5. Open the document SPLIT_FACE.model in CATIA V5. 1. Copy / Paste AS RESULT the V4 document into a CATPart. Page 510 V4 Integration And update the new V5 CATIA document: Version 5 Release 14 Page 511 V4 Integration Version 5 Release 14 Page 512 You can visualize the model's geometry but you cannot modify it. You are however able to add new entities such as Fillet or Chamfer, etc... 2. Apply a Check AS RESULT on the .model only when you notice that an entity cannot be pasted. 3. Apply a Check AS SPEC on the V4 solid. The Check validity dialog box appears: V4 Integration Version 5 Release 14 ' All the primitives can be transferred into CATIA V5. 4. Copy / Paste AS SPEC the Model into a CATPart. Page 513 V4 Integration And update your document: Version 5 Release 14 Page 514 V4 Integration Version 5 Release 14 Page 515 You have access to the model's geometry and specifications. Therefore, you can now modify the V5 CATPart document. The Split's specifications can be transferred into CATIA V5 only if the SKD has no link with an external model. Therefore, there is an exception: if the SKD has an external Reference with another model. To sum up: V4 Integration Version 5 Release 14 V4 to V5 Migration AS SPEC SPACE Elements Unary Operations Fillet Edge Constant Constant Fillet Fillet Edge Variable Variable Fillet Fillet Tritangent Tritangent Fillet Fillet Rolling Edge Fillet Keep Edge Thickness Thickness Draft Draft Draft two pulling directions 2 Drafts created Draft Reflect Line > Keep Face Draft Reflect Line > Keep Face Shell Shell Chamfer Chamfer Transfor Mirror Mirror Transfor Scaling Scaling Translation Translate Rectangular Pattern Transfor Rotation Circular Pattern Split Split Sewing Sewing Page 516 V4 Integration Version 5 Release 14 Page 517 Converting Version 4 Kinematics Data into Kinematics Version 5 Data This task shows how to convert CATIA Version 4 kinematics data into DMU Kinematics Simulator Version 5.Data Insert the KIN_EX17* .model files from the samples folder. If you work with the Cache System, please make sure you are in Design mode (select Edit->Representations>Design Mode.). For more detailed information, please refer to the DMU Navigator User Guide - Task: Viewing the Cache Content. The following task shows how kinematics data are pasted from an existing Version 4 model to an existing Version 5 document alongside V5 data. You can also insert the V4 data into a new Version 5 document. 1. Open the model containing the kinematics mechanism. And open the Kinematics Simulator workbench if necessary. The model containing the kinematics mechanism should only be a stick model (that is, Wireframe plus the definition of the mechanism). 2. In the specification tree or in the geometry area where the Version 4 kinematics model is displayed, select the mechanism you wish to copy into the Kinematics Simulator Version 5. In our example, select KIN_EX_00_F1_ACTIVE and LANDING GEAR. V4 Integration Version 5 Release 14 Page 518 V4 Integration Version 5 Release 14 Page 519 3. You can also use the drag &drop capability. 4. Put the data you have selected in the clipboard. To do this, either click the Copy icon, select the Edit->Copy command or select the Copy command in the contextual menu. 5. Select Application in the specification tree. Version 5 Release 14 V4 Integration Page 520 6. Now either click the Paste icon, select the Edit->Paste command or select the Paste command in the contextual menu. This operation recovers the data previously put in the clipboard. You may want to click the Fit All In icon Click on the to fit all data in the window. symbol next to Applications to see its components (Mechanisms -> Landing Gear -> Joints,...). V4 Integration Version 5 Release 14 Page 521 The dress up is maintained when you perform a copy/paste within the same document as it is the case below: Notice that the toolbars change depending on whether a Version 4 model or a DMU Kinematic Version 5 document is selected. The result should look something like this: V4 laws are converted in a V5 mechanism. Page 522 Version 5 Release 14 V4 Integration Kinematics Simulator fully supports V4 mechanisms (2D/3D) conversion into 3D mechanisms version 5. What About the Elements You Convert? To make sure the elements you need to handle in your session are those you expected, here is a list presenting the CATIA V4 Kinematics data supported when converted into a Kinematics Version 5 document: V4 to V5 Migration As Result SPACE Elements - 2D / 3D Kinematics Mechanism Structure 2D / 3D Result 3D Mechanism V5 Mechanism Joint V5 Joint Revolute joint Revolute joint Actuator joint Cylindrical joint PT/PT Spherical joint Planar Planar joint Prismatic Prismatic Rigid Rigid Version 5 Release 14 V4 Integration PT/CRV PT/CRV Roll/CRV Roll/CRV Slid/CRV Slid/CRV PT/SUR PT/SUR U joint U joint Gear Gear Rack Rack Cable Cable Screw Screw Command V5 Command fix V5 fixed part model CATProduct sub-product + associated part set Geometry contained in the set V5 Dressup V4 dressup Outputs numerical (angle/distances) equivalent functionality (no conversion) speed, acceleration are not converted traces (swept volume) equivalent functionality ( no conversion) clashes equivalent functionality ( no conversion) distances equivalent functionality ( no conversion) Laws numeric laws Knowledgeware rules geometrical laws are not converted Page 523 Version 5 Release 14 V4 Integration Page 524 Reading a V4 Route in a V5 Session This task shows how to read a V4 route (track +shuttle) in DMU Fitting V5. When inserting a V4 model in V5 product, if the model contains V4 routes and shuttles, the routes and shuttles will be read. They will be selectable in the navigation tree under the *MASTER container. A copy/paste operation from the V4 Master container to the V5 Tracks container will convert the V4 Routes in V5 tracks. A V4 Route is the association of: 1 Shuttle, 1 Home position and n Trajectories. A V5 Track is the association of: 1 Shuttle or 1 Product, and 1 Trajectory. The conversion will concatenate the positions in the V4 Home and Trajectories to generate a single V5 path. Insert the following .model files in the samples folder: ● FITTING_DATA.model ● FUEL_TUBE.model ● NAVIGATION_BOX.model ● OVERALL_STRUCTURE.model ● SUPPORT_BEAM.model 1. In the specification tree where the Version 4 model is displayed, select the item you wish to copy into the Fitting Simulator Version 5. In our example, expand FITTING_DATA and *MASTER items and multi-select 3-TUBE REMOVAL 2-BOX REMOVAL 1-BEAM REMOVAL V4 Integration Version 5 Release 14 Page 525 2. Put the data you have selected in the clipboard. To do this, either click the Copy icon, select the Edit->Copy command or select the Copy command in the contextual menu. Version 5 Release 14 V4 Integration Page 526 3. Select Application in the specification tree. 4. Now either click the Paste icon, select the Edit->Paste command or select the Paste command in the contextual menu. Version 5 Release 14 V4 Integration Page 527 This operation recovers the data previously put in the clipboard The result appears as shown below: 5. Open the READ_V4_ROUTE.CATProduct to check your result 6. For instance, select 1- BEAM REMOVAL in the specification tree and click the Player icon Simulate the track using the DMU player buttons: . V4 Integration Version 5 Release 14 Page 528 V4 Integration Version 5 Release 14 Geometric Set This task shows you how V4 Geometric Sets is copied As Result or AS SPEC into CATIA V5. Open the document AllV4ElementTypes.model in CATIA V5. 1. Copy / Paste AS RESULT the model into CATIA V5. All these elements are stored in a Set (*SET), which is a structural entity. 2. Copy / Paste AS RESULT the *SET into a CATPart. And update your document: Page 529 V4 Integration Version 5 Release 14 All the elements stored under *SET are migrated. 3. Apply a Check AS SPEC on the .model. Page 530 V4 Integration Version 5 Release 14 The Set and all its elements can be copied AS SPEC into CATIA V5. 4. Copy / Paste AS SPEC the *SET into a CATPart. And update your document: Page 531 V4 Integration Version 5 Release 14 You have access to the specifications of the Set's components (Primitives and Solid). Page 532 Page 533 Version 5 Release 14 V4 Integration To sum up : V4 to V5 Migration As Result As Spec SPACE Elements Infrastructure - Structural Entities Model CATProduct, CATPart and/or CATDrawing Session CATProduct Library (SPACE Detail) Catalogs of Parts Assembly Files CATProduct & Assembly Constraints Detail used for Ditto In the interactive mode, with the copy / paste AS RESULT of Dittos, the elements of the linked Detail are copied AS RESULT, updated, and put into the No Show space. In the interactive mode, with the copy / paste AS SPEC of Dittos, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. In the Batch Mode, the elements of the linked Detail are copied AS RESULT. In the Batch Mode, you get a V5 Part or a Product. In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the Copy AS SPEC of the Detail elements. Ditto In the Batch Mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. Detail for MacroPrimitives N/A In the Batch Mode, you get a V5 Part or a Product. In the interactive mode, for the copy / paste AS SPEC of a solid using MacroPrimitives, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. Macro-Primitives In the interactive mode, the solid who contains the Macro-Primitive is copied AS RESULT: it means that only its BRep is copied, without specifications. Layers The layer's numbers are transferred but not the filters. The layer's numbers are transferred but not the filters. Geometric sets You get a V5 Part. All the elements of the Set are migrated. You get a V5 Part. All the elements of the Set are migrated. Transformation N/A Affects Specifications The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. Show/No Show Color Tables Color Tables Display Types (graphic) N/A In the interactive mode, the MacroPrimitives are represented within the specifications tree of the body by links with the copy AS SPEC of the Detail elements. Version 5 Release 14 V4 Integration Models Naming V5 document Names Models Comments Product Description Property Tolerances N/A Page 534 V4 Integration Version 5 Release 14 Page 535 Detail / Ditto This task shows you how: ● to have access to more information about the Ditto' s properties (DETAIL's name) ● to copy / paste V4 Dittos and Details into CATIA V5. Open the document DITTOS-BOULON.model in CATIA V5. This model contains a Detail and several Dittos. For Dittos, there is the possibility to Check and Copy AS RESULT or AS SPEC. The first part of this scenario deals with the Check and Copy AS RESULT operation and the second part with the Check and Copy AS SPEC process. More information about the Ditto's Properties To read more information about the Ditto's properties: 1. Right-click *DIT26: V4 Integration Version 5 Release 14 Page 536 2. Select the Properties contextual command. There is a new tab called Ditto containing information about the Ditto and you can know the Name of the Detail. V4 Integration Version 5 Release 14 Page 537 Copying / Pasting V4 Dittos and Details into CATIA V5 1. Apply a Check AS RESULT on the .model before copying it in CATIA V5: Click *MASTER and the Geometry Check icon . The Check validity dialog box is displayed: V4 Integration Version 5 Release 14 Page 538 Dittos are not checked for the moment, which explains the existence of this message "Not supported Geometry check Error". If you want to check AS RESULT their underlying components: click the BOULON tab. You can also visualize the Detail and check it. If the Check AS RESULT is valid for the Detail, it is also valid for its copies, the Dittos. Soon, the Check of the Dittos will automatically take place on the linked Detail. V4 Integration Version 5 Release 14 Page 539 2. Copy and Paste Special the *MASTER of the .model into another CATPart document using the CATIA_RESULT option: 3. Click OK. You obtain the following result: Version 5 Release 14 V4 Integration Page 540 4. To be usable by links in the CATPart, the bodies from the Details are automatically updated in CATIA V5 after their Paste AS RESULT operation. If an error is detected, a warning message appears at the end of the paste operation: "CATIA V4 elements must be locally updated before its CopyAsResultWithLink for Dittos. One CATIA V4 element XXX from the Detail YYY presents errors during its local update." The features affected by the error are locally deactivated within the Specifications Tree. However, it is necessary to update your Part in order to compute all the other elements. Click the Part and the Update icon to compute the geometry: V4 Integration Version 5 Release 14 Page 541 The V4 structure of Detail - Dittos is maintained into the same Part thanks to the V5 CopyAsResultWithLink functionality (it is named in the Part tree as CARWL). The content of the Detail is copied / pasted AS RESULT once: (*SOL) (BOULON) and the geometry (Point, Line,...) into Open_body.1. These elements are put in the NO SHOW space, and the Dittos are maintained through links (called CopyAsResultWithLink) on them. If you modify the body Solid.1 from the Detail in the No Show space, all the Dittos will be modified. 5. Apply a Check AS SPEC on the .model before copying it in CATIA V5. The following messages indicate that you can copy / paste AS SPEC this model: V4 Integration Version 5 Release 14 Page 542 As it was seen above, Dittos are not checked for the moment. If you want to check AS SPEC their underlying components: click the BOULON tab. You can also visualize the Detail and check it. If you double-click on one of the messages, you have access to the structure of the Detail's solid (*SOL62). 6. Copy and Paste AS SPEC the *MASTER into a CATPart. The body of the Detail (*SOL62) (BOULON) is copied / pasted AS SPEC: V4 Integration Version 5 Release 14 Page 543 To be usable by links, in the CATPart, the Details' bodies are automatically updated in CATIA V5 after their Paste AS SPEC operation. If an error is detected, a warning message appears at the end of the Paste operation : "CATIA V4 elements must be locally updated before its CopyAsResultWithLink for Dittos. One CATIA V4 element XXX from the Detail YYY presents errors during its local update." The features affected by the error are locally deactivated within the Specifications Tree. However, it is necessary to update your Part in order to compute all the other elements. 7. Update your document: V4 Integration Version 5 Release 14 Page 544 The V4 structure is maintained through the V5 functionality of CopyAsResultWithLink into the same Part. The content of the Detail is copied / pasted AS SPEC once: it creates the body, PartBody (*SOL62) (BOULON), and the geometry into Open_body.1. The elements are put into the No Show space, and the Dittos are maintained through links (called "CopyAsResultWithLink" and also named CARWL in the Part tree) on them. The geometric elements contained in the Detail (workspace) have been copied in the NO SHOW space of the CATPart: V4 Integration Version 5 Release 14 Page 545 If you modify some features of the body Part Body (*SOL62) (BOULON) from the Detail in the No Show space (for instance Sketch.1), all the Dittos will be modified. 8. Specific cases for the Copy / Paste As Spec or As Result of Details/Dittos: The migration from a Model into a CATPart is inappropriate for some entities. If you try to Copy / Paste these entities, there is a Warning Panel which advises to use the CATV4ToV5Migration Batch. These specific cases are: ● Detail with only Geometry ● Detail with only Dittos ● Detail with several Bodies V4 Integration Version 5 Release 14 Page 546 9. Convert this CATIA Version 4 model into CATIA Version 5 in Batch mode. For more information about launching the Migration Batch, refer to Converting CATIA V4 Models into CATIA V5 in Batch Mode. The results in CATIA V5 are as follows: Migration AS RESULT in Batch mode (Update your document): Migration AS SPEC in Batch mode (Update your document): Page 547 Version 5 Release 14 V4 Integration With the migration AS SPEC, you have access to the Dittos' specifications. Therefore, you can modify them. To sum up: V4 to V5 Migration As Result SPACE Elements Infrastructure - Structural Entities Model CATProduct, CATPart and/or CATDrawing Session CATProduct As Spec Library (SPACE Detail) Catalogs of Parts Assembly Files CATProduct & Assembly Constraints Detail used for Ditto Page 548 Version 5 Release 14 V4 Integration In the interactive mode, with the copy / paste AS RESULT of Dittos, the elements of the linked Detail are copied AS RESULT, updated, and put into the No Show space. In the Batch Mode, the elements of the linked Detail are copied AS RESULT. In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. Ditto In the interactive mode, with the copy / paste AS SPEC of Dittos, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. In the Batch Mode, you get a V5 Part or a Product. In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the Copy AS SPEC of the Detail elements. In the Batch Mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. In the Batch Mode, you get a V5 Part or a Product. Detail for MacroPrimitives N/A In the interactive mode, for the copy / paste AS SPEC of a solid using Macro-Primitives, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. Macro-Primitives In the interactive mode, the solid who contains the Macro-Primitive In the interactive mode, the Macro-Primitives are is copied AS RESULT: it means that only its BRep is copied, represented within the specifications tree of the body by without specifications. links with the copy AS SPEC of the Detail elements. Layers The layer's numbers are transferred but not the filters. The layer's numbers are transferred but not the filters. Geometric sets You get a V5 Part. All the elements of the Set are migrated. You get a V5 Part. All the elements of the Set are migrated. Transformation N/A Affects Specifications Show/No Show The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. Color Tables Color Tables Display Types (graphic) N/A Models Naming V5 document Names Models Comments Product Description Property Tolerances N/A V4 Integration Version 5 Release 14 Page 549 Macro-Primitive This task shows you how V4 Macro-Primitives are copied into CATIA V5. In CATIA V4, Dittos can be used within the CSG Tree of a solid as features. They are no longer called Dittos but Macros Primitives. For more information about the migration of V4 Dittos into CATIA V5, refer to Ditto / Detail. Open the document UNION_of_MACROPRIMITIVES.model in CATIA V5. The model looks like this: The V4 Detail is placed in the CIL.SLIT.M tab: 1. Apply a Check As Result on the .model. *SOL370 and all its components can be copied AS RESULT into CATIA V5: "Geometry Check is OK". 2. Copy / Paste AS RESULT the .model into a CATPart: And update the CATPart (click the Part and the Update icon compute the geometry: ) to V4 Integration Version 5 Release 14 Page 550 Through this copy / paste AS RESULT operation, only the BRep of the solids are copied (refer to the Copy / Paste AS RESULT operation of a Solid); there is no more specifications (no Detail) for the body. 3. Apply a Check AS SPEC on the model. If you double-click one of the messages (*SOL370), you have access to the structure of the Solid of *MASTER: V4 Integration 4. Copy / Paste AS SPEC the Model into a CATPart: 5. And update your document: Version 5 Release 14 Page 551 V4 Integration Version 5 Release 14 Page 552 In the CATPart, there are 2 PartBodies: ● ● the first one contains the specifications of the Detail, CIL.SLIT.M the second one corresponds to the copy of the solid of *MASTER (CopyAsResultWith Link) that is to say a copy of the MacroPrimitive. It contains the specifications of the solid, *SOL370, with the Macro-Primitives translated into links (called CopyAsResult WithLink) with the body coming from the Detail. The Detail's solid has been pasted As Spec and the geometric elements (Macro-Primitives) have been copied As ResultWithLink in the CATPart, which means that the Macro-Primitive keeps a link with the copy of the Detail, PartBody (*SOL4)(CIL.SLIT.M) in our example. If you modify the structure of the Detail in CATIA V5, the Dittos acquire this new structure. 6. To be usable by links, in the CATPart, the Details' bodies are automatically updated in CATIA V5 after their Paste AS SPEC operation. If an error is detected, a warning message appears at the end of the Paste operation : "CATIA V4 elements must be locally updated before its CopyAsResultWithLink for Macro-Primitives. One CATIA V4 element XXX from the Detail YYY presents errors during its local update." The features affected by the error are locally deactivated within the Specifications Tree. However, it is necessary to update your Part in order to compute all the other elements. 7. The V4 structure of Macro-Primitives is maintained through the V5 functionality of CopyAsResultWithLink into the same Part. The content of the Detail is copied / pasted AS SPEC once: it creates the body, PartBody (*SOL4) (CIL.SLIT.M), in the No Show space, and the Macro-Primitives are maintained through links (called CopyAsResultWithLink) with them. The geometric elements contained in the Detail (workspace) have been copied in the NO SHOW space of the CATPart: If you modify some features of the body Part Body (*SOL4) (CIL.SLIT.M) from the Detail in the No Show space (for instance, Sketch.1), all the Macro-Primitives will be modified. To sum up : Version 5 Release 14 V4 Integration V4 to V5 Migration As Result As Spec SPACE Elements Infrastructure - Structural Entities Model CATProduct, CATPart and/or CATDrawing Session CATProduct Library (SPACE Detail) Catalogs of Parts Assembly Files CATProduct & Assembly Constraints Detail used for Ditto In the interactive mode, with the copy / paste AS RESULT of Dittos, the elements of the linked Detail are copied AS RESULT, updated, and put into the No Show space. In the interactive mode, with the copy / paste AS SPEC of Dittos, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. In the Batch Mode, the elements of the linked Detail are copied AS RESULT. In the Batch Mode, you get a V5 Part or a Product. In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. Ditto In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the Copy AS SPEC of the Detail elements. In the Batch Mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. In the Batch Mode, you get a V5 Part or a Product. Detail for MacroPrimitives N/A In the interactive mode, for the copy / paste AS SPEC of a solid using Macro-Primitives, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. Macro-Primitives In the interactive mode, the solid who contains the MacroPrimitive is copied AS RESULT: it means that only its BRep is copied, without specifications. In the interactive mode, the Macro-Primitives are represented within the specifications tree of the body by links with the copy AS SPEC of the Detail elements. Layers The layer's numbers are transferred but not the filters. The layer's numbers are transferred but not the filters. Geometric sets You get a V5 Part. All the elements of the Set are migrated. You get a V5 Part. All the elements of the Set are migrated. Transformation N/A Affects Specifications Show/No Show The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. Color Tables Color Tables Display Types (graphic) N/A Models Naming V5 document Names Models Comments Product Description Property Tolerances N/A Page 553 V4 Integration Version 5 Release 14 Page 554 Show / No Show This task shows you how to copy As Result or AS SPEC V4 entities placed in the No Show space into CATIA V5. Open the document AllV4ElementTypes_NoShow.model in CATIA V5. All the elements (Points, Lines, Curves,...) contained in the *MASTER are in the No Show space. 1. Copy / Paste AS RESULT the model into a CATPart (there are no anomalies at the Geometry Check). V4 Integration Update your document: Version 5 Release 14 Page 555 V4 Integration Version 5 Release 14 Page 556 All the elements that were stored in the No Show space in the V4 document have been copied in the No Show space of the CATPart. The transfer of this characteristic (No Show) has been correctly transferred. You have only the geometry (and not the specifications) of *SOL1 and *SOL2 with the copy / paste AS RESULT operation. 2. Apply a Check AS SPEC on the .model. V4 Integration Version 5 Release 14 3. Copy / Paste AS SPEC the Model into a CATPart: Page 557 V4 Integration Version 5 Release 14 And update your document to compute the geometry: Page 558 Page 559 Version 5 Release 14 V4 Integration All the V4 elements are transferred with their specifications in CATIA V5, in the No Show space. If there is a Ditto (*DIT) in the No Show space of your model, it will not be migrated in CATIA V5. As for the Macro-Primitives, only the Solids in the Show space can be migrated. To sum up : V4 to V5 Migration As Result As Spec SPACE Elements Infrastructure - Structural Entities Model CATProduct, CATPart and/or CATDrawing Session CATProduct Library (SPACE Detail) Catalogs of Parts Assembly Files CATProduct & Assembly Constraints Detail used for Ditto In the interactive mode, with the copy / paste AS RESULT of Dittos, the elements of the linked Detail are copied AS RESULT, updated, and put into the No Show space. In the interactive mode, with the copy / paste AS SPEC of Dittos, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. In the Batch Mode, the elements of the linked Detail are copied AS RESULT. In the Batch Mode, you get a V5 Part or a Product. In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the Copy AS SPEC of the Detail elements. Ditto In the Batch Mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. In the Batch Mode, you get a V5 Part or a Product. In the interactive mode, for the copy / paste AS SPEC of a solid using Macro-Primitives, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. Detail for MacroPrimitives N/A Macro-Primitives In the interactive mode, the Macro-Primitives In the interactive mode, the solid who contains the MacroPrimitive is copied AS RESULT: it means that only its BRep is are represented within the specifications tree copied, without specifications. of the body by links with the copy AS SPEC of the Detail elements. Layers The layer's numbers are transferred but not the filters. The layer's numbers are transferred but not the filters. Geometric sets You get a V5 Part. All the elements of the Set are migrated. You get a V5 Part. All the elements of the Set are migrated. Transformation N/A Affects Specifications The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. Show/No Show Version 5 Release 14 V4 Integration Color Tables Color Tables Display Types (graphic) N/A Models Naming V5 document Names Models Comments Product Description Property Tolerances N/A Page 560 Version 5 Release 14 V4 Integration Page 561 Layer Filters This task shows you how: ● the V4 layer filter entity is copied As Result and As Spec into CATIA V5, ● the V4 layer filters are migrated into CATIA V5 with the V4 To V5 Migration Batch. When opening Version 4 documents containing layers, all existing layers are preserved as is: the layers are stored in the Version 4 document. Note: Version 5 does not manage Version 4 layers on which dittos are located. If you want to know how to apply, create, modify and delete layer filters on a CATIA Version 4 model, in CATIA V5, please refer to Managing Layer Filters on CATIA V4 models. Copying/pasting the V4 layer filter entity into CATIA V5 Open the document LAYER_FILTER.model. 1. Apply a Check As Result on the V4 solid: All the primitives can be transferred into CATIA V5. 2. Copy / Paste AS RESULT the model into a CATIA V5 CATPart. V4 Integration Then update the new CATIA V5 document: Version 5 Release 14 Page 562 V4 Integration Version 5 Release 14 Page 563 The solid elements have been correctly migrated, their geometry is visible in V5 and the object (cube) is displayed. In CATIA V4, this object was assigned to Layer 2 and it was filtered. By default, during the migration, all the layers are taken into account and, therefore no filter is applied. If you copy / paste AS RESULT or AS SPEC this model containing layer filters into a CATPart, in both cases the layer numbers and the Filters are transferred into CATIA V5. Then, you have the possibility to create additional filters in CATIA V5. 3. Select the View -> Toolbars -> Graphic Properties command... V4 Integration Version 5 Release 14 ... to look at the Graphic Properties toolbar: 4. Click the arrow on the Layer icon box in order to see the layers' name or number: Page 564 Version 5 Release 14 V4 Integration Page 565 5. Select the root object Part1 in the tree, click the Layer box and you will see the layer number: . The root object is assigned to the layer number "0". Select Body.3 (*SOL5 - wsp *MASTER -) in the tree, click the arrow on the Layer box and the layer number appears in the Layer box: . Select PartBody (*SOL1 - wsp *MASTER -) in the tree, click the arrow on the Layer box and the layer number appears in the Layer box: . Select Body.2 (*SOL3 - wsp *MASTER -) in the tree, click the arrow on the Layer box and the layer number appears in the Layer box: 6. If you want to create a new layer, select the 0ther Layers... command from the list: . Click New in the Named Layers dialog box: Version 5 Release 14 V4 Integration The Layer box also contains the "Other Layers..." command which lets you create your own named layers. Refer to "Creating New Layers" in CATIA - Infrastructure User's Guide for more details. Page 566 If you want to rename a layer when creating it, after clicking the New button, slowly click twice the line containing the layer name to make the field editable. This enables you to set up named layers to comply with your company's layer conventions. 7. You then create filters to visualize (or not) only those objects located on the layers in the filter. In order to use visualization filters, select Tools -> Visualization Filters... command: V4 Integration Version 5 Release 14 Page 567 And the following dialog box appears: The default current filter "All visible" is applied automatically (filters are not transferred during the V4 to V5 Migration): it lets you see all the contents of the document. This filter cannot be deleted. If you create (/ obtain) or modify a Filter that already exists in the Filter list, the Filter cannot be created or modified and a Warning appears telling you that: "This filter already exists in the existing file". 8. You can create filters by clicking the NEW button and the following dialog box is displayed: Version 5 Release 14 V4 Integration Page 568 For more information about the building blocks (Criterium,...) allowing you to build the filter, please refer to Using Visualization Filters in CATIA - Infrastructure User's Guide. 9. Click in the Filter field, delete "0" then type "2" so that the filter syntax now looks like this: layer=2, which corresponds to the cube's layer number. In the Criterium: Layer field, select the comparison operator "!=" so that the cube object may be filtered and only the cylinder and the sphere will appear in the geometry space. 10. Select PartBody (*SOL1 - wsp *MASTER -) in the tree and click OK in the Visualization Filter Editor dialog box. In the Visualization Filters dialog box: this creates a new filter "Filter001" (with the default filter syntax) on the Cube object: V4 Integration Version 5 Release 14 Page 569 11. Select Filter001 in the Visualization Filters dialog box and click OK. The cube object is no longer displayed, and the filter remains active. V4 Integration Version 5 Release 14 Page 570 To see all the objects again, select the "All visible" filter in the Visualization Filters dialog box, then click OK. 12. Copy / Paste AS SPEC the .model document into a V5 CATPart... V4 Integration Version 5 Release 14 Then update the new CATIA V5 document: Page 571 V4 Integration Version 5 Release 14 Page 572 All the elements of the model are migrated and you have access to the model's geometry and specifications. Therefore, you can now modify each feature of the V5 CATPart document. Migrating V4 layer filters into CATIA V5 with the V4 To V5 Migration Batch It is possible to migrate layers and layer filters through the Migration Batch. After the migration, you can have access to the filter in the resulting CATPart. For this, you need to select Tools->Visualization Filters, and the Visualization Filters panel appears: the list of the filters is available. Then, you can select a filter and click the Apply button to apply the filter to the document. You can also select a filter and click the Edit button to modify the filter's characteristics. V4 Integration Version 5 Release 14 Page 573 V4 Integration Version 5 Release 14 Color Tables This task shows you how the V4 Color Table entity is copied As Result and As Spec into CATIA V5. Open the document COLORED_RSUR.model in CATIA V5. 1. Copy / Paste AS RESULT the model into a CATIA V5 CATPart... Page 574 V4 Integration Version 5 Release 14 ... then update the new CATIA V5 document: Page 575 V4 Integration Version 5 Release 14 Page 576 The solid elements seem to have lost their specific colors. Let's check this by following the steps 2 and 3 detailed hereafter. 2. Select any solid element as shown below: 3. Select Properties from the contextual menu then click the Graphic tab. As the Properties dialog box opens, the whole .model document is highlighted and the Fill Color displayed corresponds to the color of the .model viewed as a whole and not to the selected element which was initially pink: The Copy / Paste AS RESULT copies the overall color and not the color (whether standard or user-defined) applied individually to each element. 4. Copy / Paste AS SPEC the .model document into a CATIA V5 CATPart... V4 Integration Version 5 Release 14 ...then select any colored element, the pink sphere for instance: Page 577 V4 Integration Version 5 Release 14 Page 578 5. Select Properties from the contextual menu then click the graphic tab: The Fill Color displayed matches the one of the selected element since the Copy / Paste AS RESULT lets you copy the color applied individually to each V4 model element. To sum up : Page 579 Version 5 Release 14 V4 Integration V4 to V5 Migration As Result As Spec SPACE Elements Infrastructure - Structural Entities Model CATProduct, CATPart and/or CATDrawing Session CATProduct Library (SPACE Detail) Catalogs of Parts Assembly Files CATProduct & Assembly Constraints Detail used for Ditto In the interactive mode, with the copy / paste AS RESULT of Dittos, the elements of the linked Detail are copied AS RESULT, updated, and put into the No Show space. In the interactive mode, with the copy / paste AS SPEC of Dittos, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. In the Batch Mode, the elements of the linked Detail are copied AS RESULT. In the Batch Mode, you get a V5 Part or a Product. In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the Copy AS SPEC of the Detail elements. Ditto In the Batch Mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. In the Batch Mode, you get a V5 Part or a Product. In the interactive mode, for the copy / paste AS SPEC of a solid using Macro-Primitives, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. Detail for MacroPrimitives N/A Macro-Primitives In the interactive mode, the Macro-Primitives In the interactive mode, the solid who contains the MacroPrimitive is copied AS RESULT: it means that only its BRep is are represented within the specifications tree copied, without specifications. of the body by links with the copy AS SPEC of the Detail elements. Layers The layer's numbers are transferred but not the filters. The layer's numbers are transferred but not the filters. Geometric sets You get a V5 Part. All the elements of the Set are migrated. You get a V5 Part. All the elements of the Set are migrated. Transformation N/A Affects Specifications The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. Show/No Show Color Tables Color Tables Display Types (graphic) N/A Models Naming V5 document Names Models Comments Product Description Property Version 5 Release 14 V4 Integration Tolerances N/A Page 580 Version 5 Release 14 V4 Integration Page 581 Model Naming This task shows you how V4 Model Naming is transferred into CATIA V5. When you copy / paste AS SPEC a model containing special characters, only the name of the PartBody is transferred into CATIA V5 (for example, *SOL1). Only the Geometry (content) is transferred and not the structure such as *MASTER and *SET names. With the migration Batch, some special characters within the *MASTER are migrated, others are converted into different characters. In this scenario, we will show what is the action of the Batch on V4 model names. To be able to read the SET name for instance, place the If your model contains this kind of characters: cursor near this component and the name appears in a , you can open it in CATIA V5. little box: 1. Launch the Batch by entering the command: ● CNEXT -batch -e CATV4ToV5Migration For more information about Migration in Batch Mode, refer to Converting Version 4 Model Data into Version 5 in Batch Mode. 2. Select the V4 model and specify the directory name in which the data will be created (by default the data are created in the same place where the V4 documents are stored). V4 Integration Version 5 Release 14 3. Press the Migrate button in order to convert V4 Documents into V5 Documents. 4. The migration report will be displayed in another dialog box at the end of the operation. Double-click on the line of your choice to have more information. In the Migration Report box, the message is OK : the .models and their components can be converted into CATIA V5. Page 582 V4 Integration Version 5 Release 14 As a consequence you have access to the V4 document, converted into: SPECIALCHARACTER _SET_x____'_`__ .CATPart. Page 583 V4 Integration Version 5 Release 14 Here is an illustration of the name conversion that took place in our example: Page 584 Version 5 Release 14 V4 Integration Page 585 The Batch offers possibilities to make more relevant migrations for complex V4 data structures. *SET is converted into a CATPart and some of its special characters have been replaced by others allowed in CATIA V5 on Windows. Precisely, the following characters are not supported on Windows: ● > (greater than) ● < (less than) ● * (asterisk) ● : (colon) ● " (quotation mark) ● ? (question mark) ● \ (backslash) ● | (vertical bar) What About the migration of a V4 model with special characters in its name The following table specifies the conversion of some characters in Batch mode: V4 (on UNIX) * / (slash) \ (backslash) _ (underscore) ' (apostrophe) ` (accent) " (quotation mark) V5 (on NT) _ (underscore) x _ (underscore) _ (underscore) _ (underscore) ' apostrophe ` (accent) _ (underscore) Page 586 Version 5 Release 14 V4 Integration all the remaining special characters To sum up : _ (underscore) V4 to V5 Migration As Result As Spec SPACE Elements Infrastructure - Structural Entities Model CATProduct, CATPart and/or CATDrawing Session CATProduct Library (SPACE Detail) Catalogs of Parts Assembly Files CATProduct & Assembly Constraints Detail used for Ditto In the interactive mode, with the copy / paste AS RESULT of Dittos, the elements of the linked Detail are copied AS RESULT, updated, and put into the No Show space. In the interactive mode, with the copy / paste AS SPEC of Dittos, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. In the Batch Mode, the elements of the linked Detail are copied AS RESULT. In the Batch Mode, you get a V5 Part or a Product. In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. In the interactive mode, the Dittos are represented in the Part by a link on the bodies managed by the Copy AS SPEC of the Detail elements. Ditto In the Batch Mode, the Dittos are represented in the Part by a link on the bodies managed by the copy AS RESULT operation of the Detail elements. In the Batch Mode, you get a V5 Part or a Product. In the interactive mode, for the copy / paste AS SPEC of a solid using Macro-Primitives, the elements of the linked Detail are copied AS SPEC, updated, and put in the No Show space. Detail for MacroPrimitives N/A Macro-Primitives In the interactive mode, the solid who contains the MacroIn the interactive mode, the Macro-Primitives Primitive is copied AS RESULT: it means that only its BRep is are represented within the specifications tree of the body by links with the copy AS SPEC of copied, without specifications. the Detail elements. Layers The layer's numbers are transferred but not the filters. The layer's numbers are transferred but not the filters. Geometric sets You get a V5 Part. All the elements of the Set are migrated. You get a V5 Part. All the elements of the Set are migrated. Transformation N/A Affects Specifications The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. The Show / No Show characteristic is respected. Dittos (*DIT) in No Show are not migrated. Macro-Primitives in No Show are not migrated. Show/No Show Color Tables Color Tables Display Types (graphic) N/A Models Naming V5 document Names Version 5 Release 14 V4 Integration Models Comments Product Description Property Tolerances N/A Page 587 V4 Integration Version 5 Release 14 Page 588 Draw Elements This task shows you how V4 Draw elements are copied As Result into CATIA V5. The following model contains 2D geometry (Point, Line,...) as well as Annotations and Dress-up (Text, Dimensions,...). Open the document MDL_DEMO_INTERACTIVE_DRAFTING.model in CATIA V5. 1. Copy / paste the model into a CATDrawing document. V4 Integration Version 5 Release 14 Page 589 You can edit and modify elements. ● ● Three dimension types are copied as graphic because they do not exist in V5: ❍ angle on circular arc, ❍ diameter on curve, ❍ diameter on cone. Symbol occurrence are exploded when migrating to V5. You can set options to: Optimize migration: ● ● ● ● ● reference external PRJ via an http server. For this, in V5, go to Tools -> Options -> Compatibility -> V4/V5 Infrastructure > V4 Declarations Tab and complete PROJECT File Path go to Tools -> Standards -> Drafting -> Line Thickness node, and create six V5 line thickness styles equivalent to six standard V4 thickness styles. To do this, you must be in administrator mode. For more information, refer to "Managing Standards" in the Interactive Drafting User's Guide. create centers and end points in geometry import. For this check the Create centers and end points option in CATIA V5 Tools > Options -> Compatibility ->V4/V5 Draw tab, to convert dimensions as graphic (when you want dimensions to look like in V4). For this, check the Convert dimensions as a graphic option in CATIA V5 Tools -> Options -> Compatibility ->V4/V5 Draw tab, explode ditto when migrating to V5. For this check the Explode ditto when migrating to V5 elements option in CATIA V5 Tools -> Options -> Compatibility ->V4 /V5 Draw tab, Version 5 Release 14 V4 Integration Page 590 When copying V4 drawing data to V5, bear the following in mind: ● Whatever the standard of the V4 view was prior to being copied into CATIA Version 5, once in V5 its standard is that selected when you open the CATDrawing document. ● ● In the V5 Drafting mode Working Views (Edit->Working Views) the copy described above creates a V5 view with the same name as in V4. In the V5 Drafting mode Background (Edit->Background) the V4 elements are copied into the background view of the V4 view. The migration of V4 drawing data to a V5 document generates a report (.rpt) file named after the model migrated: ❍ on Windows: in C:Winnt/Profiles/username/Local Settings/Application Data/DassaultSystemes/CATReport ❍ on UNIX: in /u/users/username/CATReport 2. Apply a Check As Result on the .model only when you notice that an entity cannot be pasted. V4 to V5 Migration - Summary Tables Migration of .model structure The table below sums up how the various elements which make up the structure of .model documents are migrated from V4 to V5, both As Result and As Spec. .model structure V4 to V5 Migration As Result As Spec Draft Sheet Sheet AUXVIEW View Interactive view Interactive view AUXVIEW2 view Interactive view Generative view Detail workspace Detail sheet Detail sheet Migration of DRAW elements The table below sums up how the various DRAW elements are migrated from V4 to V5 As Result. DRAW Elements V4 to V5 Migration 2D geometry As Result Point Point Line Line Curve Curve Circle (CIRD) Circle Ellipse (ELLD) Ellipse Parabola (PARD) Parabola Hyperbola (HYPD) Hyperbola Spline NURBS Annotations & Dress-up V4 Integration Shape > Open > Closed > Closed / Approximated Text > Simple Text > Note (text with leaders) >GT&T > Datum Target > Datum Feature > Balloon > Roughness Symbols Version 5 Release 14 Shape Shape Shape Shape Text Text Text detail Text Detail Dimensions >Distance > Length on line > Length on circle > Angle between lines > Angle on circular arc > Radius / TGT > Radius / CNT > Radius / Edge > Radius / cylinder > Radius on curve > Diameter / TGT > Diameter / CNT > Diameter / Edge > Diameter / Cylinder > Diameter on curve > Diameter on cone > Chamfer > Slope > Coordinate dimension > Distance dim. System Dimension Dimension Dimension Dimension Graphical Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Graphical Dimension Graphical Dimension Dimension Dimension Dimension > Curvilinear dimension > Dimension along a reference direction Dimension Dimension Pattern Pattern Raster Image Raster Image Arrow Arrow Symbol Occurrence Geometry Ditto Ditto Detail Detail Transparent View Polyline, Line (SPACE elements: a model with Transparent View) (DRAW elements) View Framing View Framing Page 591 V4 Integration Version 5 Release 14 Text Detail This task shows you how V4 Text Detail are copied As Result into CATIA V5. Open the document DITTOSYMBOL.model in CATIA V5. And press the *DRAFT tab to visualize the Drawing view of the Text Detail: Page 592 V4 Integration Version 5 Release 14 1. Copy / Paste the model into a CATDrawing document. Page 593 V4 Integration Version 5 Release 14 Page 594 V4 Text Details are converted into V5 Text Details in CATIA V5. You can edit and modify the Text Detail in the V5 CATDrawing; it is represented by the broken lines around the Text Detail: . The broken lines turn green when you double click this text to modify it and the Text Editor dialog box appears: V4 Integration Version 5 Release 14 You cannot modify the Ditto called "texte" in this *DRAFT View: Page 595 V4 Integration Version 5 Release 14 Page 596 If you double click "texte" in the *DRAFT tab, the DETPBU becomes active and you can modify the text. Page 597 Version 5 Release 14 V4 Integration 2. Apply a Check As Result on the .model only when you notice that an entity cannot be pasted. To sum up : V4 to V5 Migration As Result As Spec Point Point N/A Line Line N/A Curve Curve N/A Circle (CIRD) Circle N/A DRAW Elements Wireframe Page 598 Version 5 Release 14 V4 Integration Ellipse (ELLD) Ellipse N/A Parabola (PARD) Parabola N/A Hyperbola (HYPD) Hyperbola N/A Spline NURBS N/A Shape > Open > Closed > Closed / Approximated Shape Shape Shape Shape N/A Annotations & Dress-up Text > Simple Text > Note (text with leaders) >GT&T > Datum Target > Datum Feature > Balloon > Roughness Symbols Text Text N/A Text Detail Text Detail Dimensions >Distance > Length on line > Length on circle > Angle between lines > Angle on circular arc > Radius / TGT > Radius / CNT > Radius / Edge > Radius / cylinder > Radius on curve > Diameter / TGT > Diameter / CNT > Diameter / Edge > Diameter / Cylinder > Diameter on curve > Diameter on cone > Chamfer > Slope > Coordinate dimension > Distance dim. System Dimension Dimension Dimension Dimension Graphical Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Graphical Dimension Graphical Dimension Dimension Dimension Dimension Dimension Pattern Pattern N/A Raster Image Raster Image N/A Arrow Arrow N/A Ditto Ditto N/A Detail Detail N/A Symbol Occurrence Geometry N/A View View N/A N/A N/A Page 599 Version 5 Release 14 V4 Integration Transparent View (SPACE elements: a model with Transparent View) Polyline, Line (DRAW elements) N/A View Framing View Framing N/A V4 Integration Version 5 Release 14 Page 600 Raster Insertion This task shows you how V4 Raster images contained in a model are copied/pasted As Result into CATIA V5. These images created with the V4 Raster functionality can be migrated into a CATDrawing. Open a .model document in CATIA V5 containing Raster data (an associated V4 image, a Studio image for instance): In CATIA V5, you can browse a V4 model containing Raster data. 1. Copy / Paste the model into a CATDrawing document. Page 601 Version 5 Release 14 V4 Integration The Raster elements contained in the V4 model are migrated into a V5 CATDrawing. They keep the same data structure and you can edit and modify these images in CATIA V5. You also have the possibility to insert another picture in this CATDrawing by selecting the Insert command in the File menu and the Browse dialog box appears. 2. Apply a Check As Result on the .model only when you notice that an entity cannot be pasted. To sum up : V4 to V5 Migration As Result As Spec Point Point N/A Line Line N/A Curve Curve N/A Circle (CIRD) Circle N/A DRAW Elements Wireframe Page 602 Version 5 Release 14 V4 Integration Ellipse (ELLD) Ellipse N/A Parabola (PARD) Parabola N/A Hyperbola (HYPD) Hyperbola N/A Spline NURBS N/A Shape > Open > Closed > Closed / Approximated Shape Shape Shape Shape N/A Annotations & Dress-up Text > Simple Text > Note (text with leaders) >GT&T > Datum Target > Datum Feature > Balloon > Roughness Symbols Text Text N/A Text Detail Text Detail Dimensions >Distance > Length on line > Length on circle > Angle between lines > Angle on circular arc > Radius / TGT > Radius / CNT > Radius / Edge > Radius / cylinder > Radius on curve > Diameter / TGT > Diameter / CNT > Diameter / Edge > Diameter / Cylinder > Diameter on curve > Diameter on cone > Chamfer > Slope > Coordinate dimension > Distance dim. System Dimension Dimension Dimension Dimension Graphical Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Graphical Dimension Graphical Dimension Dimension Dimension Dimension Dimension Pattern Pattern N/A Raster Image Raster Image N/A Arrow Arrow N/A Ditto Ditto N/A Detail Detail N/A Symbol Occurrence Geometry N/A N/A N/A Page 603 Version 5 Release 14 V4 Integration View View N/A Transparent View (SPACE elements: a model with Transparent View) Polyline, Line (DRAW elements) N/A View Framing View Framing N/A V4 Integration Version 5 Release 14 Page 604 Transparent View This task shows you how V4 Transparent Views are copied/pasted As Result into CATIA V5. V4 models with Transparent Views can be migrated as DRAW elements into CATIA V5. Open the document TransparentView.model in CATIA V5. And press the *DRAFT tab to visualize the Drawing view: In CATIA V5, you can browse a V4 model containing Transparent Views. 1. Copy / Paste the model into a CATDrawing document. V4 Integration Version 5 Release 14 Page 605 V4 SPACE elements with Transparent Views are converted into DRAW elements (DRAW view): Polylines and Lines in CATIA V5. And you can edit and modify these elements (Polylines and Lines): Version 5 Release 14 V4 Integration 2. Apply a Check As Result on the .model only when you notice that an entity cannot be pasted. To sum up : V4 to V5 Migration As Result As Spec Point Point N/A Line Line N/A Curve Curve N/A Circle (CIRD) Circle N/A Ellipse (ELLD) Ellipse N/A Parabola (PARD) Parabola N/A Hyperbola (HYPD) Hyperbola N/A Spline NURBS N/A Shape > Open > Closed > Closed / Approximated Shape Shape Shape Shape N/A DRAW Elements Wireframe Annotations & Dress-up Text > Simple Text > Note (text with leaders) >GT&T > Datum Target > Datum Feature > Balloon > Roughness Symbols Text Detail Text Text N/A Text Detail N/A Page 606 Version 5 Release 14 V4 Integration Dimensions >Distance > Length on line > Length on circle > Angle between lines > Angle on circular arc > Radius / TGT > Radius / CNT > Radius / Edge > Radius / cylinder > Radius on curve > Diameter / TGT > Diameter / CNT > Diameter / Edge > Diameter / Cylinder > Diameter on curve > Diameter on cone > Chamfer > Slope > Coordinate dimension > Distance dim. System Dimension Dimension Dimension Dimension Graphical Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Graphical Dimension Graphical Dimension Dimension Dimension Dimension Dimension Pattern Pattern N/A Raster Image Raster Image N/A Arrow Arrow N/A Ditto Ditto N/A Detail Detail N/A Symbol Occurrence Geometry N/A View View N/A Transparent View (SPACE elements: a model with Transparent View) Polyline, Line (DRAW elements) N/A View Framing View Framing N/A N/A Page 607 V4 Integration Version 5 Release 14 Page 608 View Framing This task shows you how V4 View Framing are copied/pasted As Result into CATIA V5. V4 models with View Framing can be migrated as DRAW elements into CATIA V5. Open the document VIEWFRAMING.model in CATIA V5. And press the *DRAFT tab to visualize the Drawing view: In CATIA V5, you can browse a V4 model containing View Framing. 1. Copy / Paste the model into a CATDrawing document. V4 Integration Version 5 Release 14 Page 609 During the V4 to V5 Migration, the same definition of the V4 View reframe is kept. The same frame is reapplied in CATIA V5. View Framing is converted into a DRAW element: *VUI. And you can edit and modify *VUI: Page 610 Version 5 Release 14 V4 Integration 2. Apply a Check As Result on the .model only when you notice that an entity cannot be pasted. To sum up: V4 to V5 Migration As Result As Spec Point Point N/A Line Line N/A Curve Curve N/A DRAW Elements Wireframe Page 611 Version 5 Release 14 V4 Integration Circle (CIRD) Circle N/A Ellipse (ELLD) Ellipse N/A Parabola (PARD) Parabola N/A Hyperbola (HYPD) Hyperbola N/A Spline NURBS N/A Shape > Open > Closed > Closed / Approximated Shape Shape Shape Shape N/A Annotations & Dress-up Text > Simple Text > Note (text with leaders) >GT&T > Datum Target > Datum Feature > Balloon > Roughness Symbols Text Text N/A Text Detail Text Detail Dimensions >Distance > Length on line > Length on circle > Angle between lines > Angle on circular arc > Radius / TGT > Radius / CNT > Radius / Edge > Radius / cylinder > Radius on curve > Diameter / TGT > Diameter / CNT > Diameter / Edge > Diameter / Cylinder > Diameter on curve > Diameter on cone > Chamfer > Slope > Coordinate dimension > Distance dim. System Dimension Dimension Dimension Dimension Graphical Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Dimension Graphical Dimension Graphical Dimension Dimension Dimension Dimension Dimension Pattern Pattern N/A Raster Image Raster Image N/A Arrow Arrow N/A Ditto Ditto N/A Detail Detail N/A N/A N/A Page 612 Version 5 Release 14 V4 Integration Symbol Occurrence Geometry N/A View View N/A Transparent View (SPACE elements: a model with Transparent View) Polyline, Line (DRAW elements) N/A View Framing View Framing N/A V4 Integration Version 5 Release 14 Page 613 Glossary A active active object active window application window apply The state when an object is the focus of user input and its operations are available. Object currently being edited. The window in which a user is currently working or directing input. An active window is typically at the top of the Z order and is distinguished by the color of its title bar. Window containing the CATIA Version 5 application. To commit a set of changes or pending transactions made in a secondary window, typically without closing that window. C cancel To halt an operation or process and return to the state before it was invoked. CATIA Site Navigator A viewer allowing you to display CATIA Version 4 data in the CATIA Version 5 environment. click (v.) To position the pointer over an object and then press and release a mouse button. (n.) The act of clicking. clipboard The area of storage for objects, data or their references after a user carries out a Cut or Copy command. close To remove a window. character set A character is any symbol used for the organization, control, or representation of data. A group of such symbols used to describe a particular language. Each language (or group of languages) has its character set code page A collection of characters that make up a character set. code set A code page (or code set) is a table mapping a given character (from a given character set) to a hexadecimal code position, or code point, for that code page. It contains the encoding values for a character set or several character sets. The encoding values in a code set provide the interface between the system and its input and output devices. current State of an object when selected. cursor A generic term for the visible indication of where a user's interaction will occur. D default An operation or value that the system or application assumes, unless a user makes an explicit choice. V4 Integration dialog box document document window double-click Version 5 Release 14 Page 614 A secondary window that gathers additional information from a user. A dialog box usually contains one or more controls, such as buttons, list boxes, combo boxes, and edit boxes, with which the user enters text, chooses options, or directs the action of the command. A common unit of data (typically a file) used in user tasks and exchanged between users. When saved on disk, a document is given a unique filename by which it can be retrieved. A window that provides a primary view of a document (typically its content). (v.) To press an release a mouse button twice in rapid succession. (n.) The act of double-clicking. E edit field enter See text box. (v.) To type a character from the keyboard. (n.) A classification of an object based on its characteristics, behavior, and attributes. G geometry geometry area Three-dimensional representation of the elements contained in the data. An example would be the set of faces that make up a solid. Roughly equivalent to the Brep representation used in CATIA Version 4. Area of a document window in which application data are displayed and edited. H hold down To continue pressing a keyboard key, or mouse button. I icon inactive inactive window insertion point interoperability A pictorial representation of an object. The state of an object which it is not the focus of a user's input. A window in which a user's input is not currently being directed. An inactive window is typically distinguished by the color of its title bar. The location where text or graphics will be inserted (also referred to as the caret). Also used for text box controls to indicate input focus. Ability to exchange data between CATIA Version 4 and CATIA Version 5. Ability to exchange CATIA Version 5 data between CATIA Version 5 workshops Ability to exchange data between CATIA Version 5 and OLE-compliant applications. L V4 Integration link Version 5 Release 14 Page 615 (v.) To form a connection between two objects. (n)) A reference to an object that is linked to another object. M menu menu menu menu menu bar button item title message box modal mode model model document modeless mouse A list of textual or graphical choices from which a user can choose. A horizontal bar at the top of a window, below the title bar, that contains menus. A command button that displays a menu. A choice on a menu. A text or graphic label that designates a particular menu. For drop-down menus, the titles is the entry in the menu bar; for cascading menus the menu title is the name of its parent menu item. A secondary window that is displayed to inform a user about a particular condition. A restrictive or limiting interaction because of operating in a mode. Modal often describes a secondary window that restricts a user's interaction with other windows. A secondary window can be modal with respect to its primary window or to the entire system. Compare modeless. A particular state of interactions, often exclusive in some way to other forms of interactions. CATIA Version 4 model. Document containing a CATIA Version 4 model. Not restrictive or limiting interaction. Modeless often describes a secondary window that does not restrict a user's interaction with other windows. Compare modal. A commonly used input device that has one or more buttons used to interact with a computer. It is also used as a generic term to include other pointing devices that operate similarly (for example, trackballs and headpointers). O object operation option button An entity or component identifiable by a user that can be distinguished by its properties, operations, and relationships. A generic term that refers to the actions that can be done to or with an object. A standard Windows control that allows a user to select from a fixed set of mutually exclusive choices (also referred to as a radio button). P point pointer press PROJECT file (v.) To position the pointer over a particular object an location. (n.) A unit of measurement for type (1 point equals approximately 1/72 inch). A graphic image displayed on the screen that indicates the location of a pointing devices (also referred to as a cursor). To press and release a keyboard key. A CATIA Version 4 entity containing project standards. This is the heart of the CATIA Version 4 site without which no significant operations can be carried out. The "building blocks" of a project are stored in the form of tables, each of which corresponds to a member of the PROJECT file. V4 Integration property Version 5 Release 14 Page 616 Attribute or characteristic of an object that define its state, appearance, or value. R right-click Click using the right mouse button (to display contextual menu). S scroll scroll bar select selection settings specifications specification tree status bar stop To move the view of an object or information to make a different portion visible. A standard Windows control that supports scrolling. To identify one or more objects upon which an operation can be performed. An object or set of objects hat have been selected. Set of setup parameters and user preferences stored in non-editable files. Made up of the entire history of the actions performed to obtain the data. Shown in the form of a tree and roughly equivalent to the CSG tree used in CATIA Version 4. Area of the document window reserved for viewing the design specifications of a part, presented in the form of a tree structure. An area that allows the display of state information of the information being viewed in the window, typically places at the bottom of a window. To halt a process or actions, typically without restoring the state before the process began. T text box title bar toolbar A standard Windows control in which a user can enter an edit text (also referred to as the edit field). The horizontal area at the top of a window that identifies the window. The title bar also acts as a handle for dragging the window. A frame or special area that contains a set of other controls. U unavailable undo The state of a control or data whose normal functionality is not presently available to a user (also referred to as dimmed). To reverse one operation performed on an object. W window workbench A standard Windows object that displays information. A window is a separately controllable area of the screen that typically has a rectangular border. Set of tools for completing specific tasks. Each type of document can be edited with a document-specific set of tools. V4 Integration Version 5 Release 14 Page 617 V4 Integration Version 5 Release 14 Index Numerics 2D geometry import 2D Views migrate 3D from CATIA V4 to CATIA V5 A access model comment AEC and Tubing Data Migration AEC primitive alphanumerical reorder Details application data migration applied to CATIA V4 Library families filter arrows standards associative migration solid MML associative mode Save As Model automatic transfer detail comment model comment AUXVIEW2 convert in batch mode AUXVIEW2 Defaults Page 618 V4 Integration Version 5 Release 14 manage V5 generative view styles for migration Axis System from a V5 Track to a V4 Model B batch convert a V4 Session into V5 in batch mode convert V4 AUXVIEW2 Views to V5 Generative Drafting Views in Batch Mode DataLifeCycle Batch extract a V4 Model From Sequential File in batch mode migrating from V4 to V5 in Batch mode rename V4 documents regarding Windows file system compatibility in batch mode V5/V4 File-based Migration Batch between V4 Functions and V5 Toolbars equivalence Bsplines surfaces C CATIA Site Navigator CATIA Version 4 libraries CATPart Product Property As V4 Model Comment Save As Model catsite.DEFAULT_DS_CODE_PAGE CCVs checking V4 model data (geometry and specifications) circles Cleaner V4 cleaning V4 data Page 619 V4 Integration Version 5 Release 14 close primitives converted to datum clouds of points code page standard command V4/V5 SheetMetal data migration commands copy defined views... filter options paste paste special... comparison of CATIA V4 and CATIA V5 compatibility settings conversion AS SPEC PartBody convert session Version 4 library objects into V5 Part documents convert a V4 Session into V5 in batch mode batch convert As Result solidM entities convert in batch mode AUXVIEW2 convert V4 AUXVIEW2 Views to V5 Generative Drafting Views in Batch Mode batch copied as drawing data from V4 to V5 curves copy commands V4 drawing data to V5 V4 model data (geometry and specifications) to V5 Page 620 V4 Integration V5 model data to V4 copy As Result layer filters copy As Spec layer filters curves copied as drawing data from V4 to V5 D DataLifeCycle utility DataLifeCycle Batch batch deactivate No Show Filter deactivation V4 elements parents filter declaring parameters in V4 defined views... commands detail comment automatic transfer DETAIL with only Dittos migration DETAIL with only Geometry migration Details alphanumerical reorder DETAILS with several Bodies migration diagnosis feature partial paste dimension conversion mode dimension numerical display standards Version 5 Release 14 Page 621 V4 Integration Version 5 Release 14 dimension properties standards dimension tolerances standards dimension value formats Drafting standards dimensions displaying V4 Federators and Sub-Federators in V5 V4 geometric elements in V5 V4 model workspaces displaying V4 library keywords in V5 ditto dittos DLName Save As Session Windows Drafting manage generative view styles for migration manage standards for migration migrate from V5 Drafting standards dimension properties dimension value formats filter fonts line thickness line types symbols text properties tolerances draft-type operations DRAW details DRAW elements Page 622 V4 Integration Version 5 Release 14 manage V5 Drafting standards for migration migrate E edges electrical data migration migrating step by step setting options V4-V5 mapping ellipses equivalence between V4 Functions and V5 Toolbars V4/V5 Entities V4/V5 Files exact solids external library objects extract a V4 Model From Sequential File in batch mode batch Extract Model From Sequential utility F faces fillet-type operations filter applied to CATIA V4 Library families commands Drafting standards standards fonts Page 623 V4 Integration Drafting standards standards from a V5 Track to a V4 Model Axis System G generative view styles V4 AUXVIEW2 Defaults to V5 GPR element H hierarchical structure library HLR mode hyperbolas I identify model coming from V5 import 2D geometry improved design in context solid edges Industrial Processes Initial Drawing Path K keywords Version 5 Release 14 Page 624 V4 Integration library Kinematics data L layer filters copy As Result copy As Spec V4 To V5 Migration batch level displayed of families library hierarchical structure keywords opening in V5 on UNIX opening in V5 on Windows line thickness Drafting standards standards line types Drafting standards standards linear structure lines M macroprimitive multibodies Manage Layer Filter manage standards for migration Drafting manage V5 Drafting standards for migration DRAW elements manage V5 generative view styles for migration Version 5 Release 14 Page 625 V4 Integration AUXVIEW2 Defaults managing V5 Introduction manufacturing data menu bar V4 Integration migrate 2D Views DRAW elements migrating from V4 to V5 in Batch mode batch migrating in Batch mode utility migrating V4 data to V5 migrating step by step setting options V4-V5 mapping migration application data DETAIL with only Dittos DETAIL with only Geometry DETAILS with several Bodies mock-up solid migration report V4 drawing data V4 model data mock-up solid migration mockup solids model coming from V5 identify model comment access automatic transfer model editor workspaces navigator Version 5 Release 14 Page 626 V4 Integration N NHR mode No Show Filter deactivate non-isometric transformations non-synchronized elements Save As Model not readable in V5 O offset primitives converted to datum open session session referencing CDM Models opening in V5 on UNIX library opening in V5 on Windows library optimize V5/V4 Migration optimize V4 Migration options commands P parabolas PartBody conversion AS SPEC Version 5 Release 14 Page 627 V4 Integration Version 5 Release 14 partial paste diagnosis feature paste commands paste special... commands PIP element planar structure planes points polyhedral solids polyhedral surfaces polynomial curves polynomial surfaces primitives converted to datum close offset PRJ file PROJECT file R read V5 data in V4 format readable in V5 rename V4 documents regarding Windows file system compatibility in batch mode batch report file rolling edges S save Page 628 V4 Integration Version 5 Release 14 V5 CATProduct As a V4 Session V5 Part as a V4 Model Save As Model associative mode CATPart Product Property As V4 Model Comment non-synchronized elements Save As Session DLName sequential file session convert open session referencing CDM Models open sewing feature skins solid solid edges improved design in context solid MML associative migration solidM entities convert As Result SPACE details spines sweep standard code page standards arrows dimension numerical display dimension properties dimension tolerances filter fonts Page 629 V4 Integration line thickness line types text V4 drawing data to V5 STR element support of non-synchronized Elements surfaces Bsplines sweep spines until a sweep symbols Drafting standards T text standards texts and dimensions toolbar V4 Integration transparent views tubing U until a sweep sweep utility DataLifeCycle Extract Model From Sequential migrating in Batch mode Version 5 Release 14 Page 630 V4 Integration Version 5 Release 14 V4 To V5 Windows Compatibility Name V5 To V4 Migration Batch V V4 AUXVIEW2 Defaults to V5 generative view styles V4 data cleaning V4 data browsing V4 data conversion V4 Draw to V5 CATDrawing convert in batch mode V4 drawing data migration report V4 drawing data to V5 copy standards V4 drawings, accessing V4 elements parents filter deactivation V4 Federators V4 Federators and Sub-Federators in V5 displaying V4 geometric elements in V5 displaying V4 Integration menu bar toolbar V4 model data migration report V4 model data (geometry and specifications) checking V4 model data (geometry and specifications) to V5 copy Page 631 V4 Integration V4 model workspaces displaying V4 Sub-Federators V4 To V5 Migration batch layer filters V4 To V5 Windows Compatibility Name utility V4/V5 BREP Info Checker V4/V5 Entities equivalence V4/V5 equivalences V4/V5 Files equivalence V4/V5 SheetMetal data migration command V418 Model Mandatory V4-V5 migration migrating step by step setting options V4-V5 mapping V5 CATProduct As a V4 Session save V5 data in V4 format read V5 model data to V4 copy V5 Part as a V4 Model save V5 To V4 Migration Batch utility V5/V4 File-based Migration Batch batch V5/V4 Migration optimize Version 4 library objects into V5 Part documents convert Version 5 Release 14 Page 632 V4 Integration W Windows DLName workspaces navigator model editor Version 5 Release 14 Page 633