V4 Integration Site Map Preface What's New?

Getting Started Functionality Description Workbench Description Customizing How to manage Version 5 Introduction Glossary Index

Dassault Systmes 1994-2001. All rights reserved.

Site Map
Preface Where to Find More Information 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 Functionality Description Warning Prerequisites V418 Model Mandatory Cleaner V4 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 Managing V4 Models, PRJ Files, Library Objects in V5 Having Access to V4 Model Comment Copying 3D from CATIA V4 to CATIA V5 Copying 2D from CATIA V4 to CATIA V5 Having Access to one or several V4 Drawings within a model in CATIA V5 Migration in Batch Mode Converting CATIA V4 Model into CATIA V5 in Batch Mode Extract V4 Model From Sequential File Automatic Transfer of a V4 Model Comment Automatic Transfer of a V4 Detail Comment Converting a V4 Session to CATIA V5 in Batch mode Transfer of SPACE Entities Improved Design in Context: Access to Solid Edges Opening a V4 Session in CATIA V5 Reading V5 Data in V4 Format

Saving a V5 Part As a V4 Model Saving V5 CATProducts As V4 Sessions Workbench Description Menu Bar Toolbars Workbench Customization How to manage V5 Introduction V5 Introduction versus Industrial Processes V4 V5 Equivalences Using CDMA in V5 (on UNIX Only) Connecting an ORACLE or DB2 Database to V5 Mapping CDMA and Assembly Attributes Adding a CDM Representation to a Product Adding a CDM Product to a Product Using VPM Data in V5 (on UNIX Only) Preparing the VPM and CATIA Environments for VPM/CATIA V5 Interoperability CATIA V5 / ENOVIAVPM Interoperability 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 Point Cuboid Pyramid Close and Offset Primitives Split

2D / 3D Kinematics Geometric Set Detail / Ditto Macro-Primitive Show / No Show Color Tables Model Naming DRAW Elements Glossary Index

Where to Find More Information

Prior to reading this book, we recommend that you read: CATIA - Infrastructure User's Guide Conventions

Preface
The V4 Integration product includes unique two-way interoperability between CATIA Version 5 and CATIA Version 4 data. 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. In this Guide, 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.

Where to Find More Information

What's New?
V4 Model support: Transfer of Infrastructure Information Batch Option: SPACE migration as Spec or As Result Batch: Progress Bar A New Batch: Extract V4 Model from Sequential File Automatic Transfer of a Version 4 Detail Comment during a V4 to V5 Migration

V4 Data Interoperability: Improved Design in Context: Access to Solid Edges 2DOverlay: Having Access to one or several V4 Drawings within a Model in CATIA V4 Having Access to PRJ Files installed on NT

V4 to V5 Interoperability: Save As Model: Customize V4 Unit Save Product As Session: DLNAMEs support Equivalences between CATIA Version 4 and CATIA Version 5 V4 / V5 Entities: Illustration of the V4 to V5 Migration

Having Access to PRJ Files on NT

This task shows you that you can have access to the PRJ Files installed on the NT disk. You need to bring these Project files referenced by the model into an NT 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 NT: the table file names generally contain Windows NT 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" Other forbidden NT ( / \ < > : ? | ) 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 NT. You can use the following methodology to copy your Project File on NT: 1. Duplicate your Project File directory on UNIX: cp -r <native_V4_PRJ> <NT_compliant_PRJ> 2. Go to the new directory: cd <NT_compliant_PRJ> 3. Rename the table files adequately: mv .TEXTCOT : DESCRIPTIONS .TEXTCOT___DESCRIPTIONS mv .TEXTCOT : STANDARDS .TEXTCOT___STANDARDS mv .PATTERN : DESCRIPTION .PATTERN___DESCRIPTION mv .PATTERN : IDENTIFICATEURS .PATTERN___IDENTIFICATEURS mv .PATTERN : MOTIFS .PATTERN___MOTIFS 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 NT 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 / V5 Infrastructure in CATIA - Infrastructure User's Guide.

How to Manage V5 Introduction...

V5 Introduction versus Industrial Processes V4 V5 Equivalences

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 is composed 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. How to use CDMA Data in a CATIA Version 5 Assembly See : Using CDMA Data in a CATIA Version 5 Assembly (on UNIX Only) 3. How to use VPM Data in CATIA Version 5 See : Using VPM Data in CATIA Version 5 (on UNIX Only) 4. How to convert CATIA V4 Kinematic Data into DMU Kinematic V5 Data See : Converting CATIA V4 Kinematic Data into DMU Kinematic V5 Data

5. 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

LINE

SPLINE

CONIC AN AXIS BY USING TWO POINTS POINT

SKETCHER

LIMIT1 and TRANSFOR

TRANSFOR

CURV1

SOLIDE AND SOLIDM SOLIDE OPERATN 6. How to use CATIA V4 Libraries See : Using CATIA Version 4 Library 7. Equivalence between V4 Items and V5 Icons (equivalence table will be described for next releases) 8. How to manage Layer Filters on CATIA Version 4 Models See : Managing Layer Filters on CATIA Version 4 Models 9. V4 V5 Files

V4

V5

Solid Surface Wireframe FEM 2.5 NC Drawing Part Positioning

.model 3D .model 3D

.CATPart Body .CATPart Open Body

.model 3D or 2D .CATPart Open Body .model 3D .model 3D .model DR .model Ditto .session .asm .asm .model Set .lib .CATAnalysis CATProcess .CATDrawing .CATProduct

Positioning Constraint Kinematics Library

PRJ

.CATProduct .CATProduct Application .catalog Native Data Description

10. 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. 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.

Using CDMA Data in a CATIA Version 5 Assembly (on UNIX Only)

Connecting an ORACLE or DB2 Database to Your CATIA Version 5 Environment (on UNIX Only) Mapping CDMA and Assembly Attributes on UNIX Adding a CDM Representation to a Product on UNIX Adding a CDM Product to a Product on UNIX

Connecting an ORACLE or DB2 Database to Your CATIA Version 5 Environment (on UNIX Only)
This task shows you how to connect an ORACLE or DB2 database to your CATIA Version 5 environment, so that you can later use CDMA data as representations or products in a CATIA Version 5 assembly. Have your CATIA Version 5 environment prepared for receiving Version 4 CDMA data. Bear in mind the following: Before importing CDMA data residing on ORACLE databases, you should check that these databases are properly described in the tsnames.ora UNIX file and export the TNS_ADMIN variable by specifying the path of the tsnames.ora file directory. When using ORACLE8, you must export the ORA_NLS33 variable by specifying the path of the directory containing the lx... .nlb files (normally located in /$ORACLE_HOME/common/nls/admin/data). Before importing CDMA data residing on a DB2 database, you should check that the client DB2 database installation has been performed for the database you plan to use. For further information, see the appropriate CDMA, Assembly, ORACLE or DB2 documentation. Only data from CDMA databases in the RAW_COID = TRUE mode (binary COID type attributes) and the NEW_MATRIX = 'YES' mode (positioning matrices in FLOAT format) can be imported. Models intended to be used as representations should have been stored by using the: DBLFCAT DBLFAIX DBLFCDM access methods. CATIA Version 5 cannot access models stored by means of any other method. The product generated by adding some CDM representations and/or models can be modified just like any CATProduct document in CATIA Version 5. However, modifications cannot be written back to the CDMA database.

1. Select the Tools->Options... command. The Options dialog box appears. 2. Select the Infrastructure/Product Structure category in the left-hand column and click on the EnoviaVPM tab.

3. In the CDMA Interoperability Administration section of the dialog box, click on the ellipsis to the right of the Database Administration option to declare the logical name of your database in your Version 5 environment. This step is intended to define the parameters for connecting to the CDMA databases you wish to use. The Database Server Administration dialog box is displayed:

The Known Servers frame should initially be empty. 4. Click on New to declare a new server. The dialog box below is displayed:

5. In this dialog box, enter the server's logical name in the Name field:

6. In the Connection String field, enter the connection string declared in the tsnames.ora file (ORACLE) or the database alias declared by the configuration utility (DB2). 7. In the Dictionary field, enter the CDMA dictionary name and click OK. The updated Database Server Administration dialog box is displayed. The name of the server you have just declared should appear in the Known Servers box as well as the description of the server in the Selected Server box:

8. Click on Save to save your new server configuration. 9. Click on Test to see whether the required server can be properly connected. The following dialog box is displayed:

10. Complete the User Name and Password Name fields. Click OK. The following dialog box is displayed:

11. Click OK to terminate the Database Administration dialog. You have just completed the first administration step. All the declarations required to connect your database have been made.

Workbench Description
The V4 integration user interface looks like this:

The section is organized as follows: Menu Bar Geometry and Specification Toolbar

Geometry and Specification Toolbar

The only toolbar that is 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

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) faces volumes skins and exact solids mockup solids (see remarks regarding copy/pasting mockup solids below) polyhedral surfaces and solids circles ellipses points lines planes clouds of points edges parabolas hyperbolas curves (both polynomial and BSpline) CCVs NURBs (curves and surfaces). 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 where a appears indicating

, the drop is drop is allowed. If the cursor changes to the symbol not allowed in that location. or: a. Put the element(s) you have selected in the clipboard by clicking the , select the Edit->Copy command or select the Copy Copy icon 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 c. Click the Paste icon 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 , selecting the Edit->Copy command or selecting the Copy Copy icon 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:

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.

to fit all data in the window. 6. You may want to click the Fit All In icon 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):

If you copied the specifications the result should look something like this (using the Window->Tile Horizontally command):

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 NT: in C:Winnt/Profiles/username/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.

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.

Functionality Description V4 to V5
Warning Prerequisites Manipulating V4 Models in V5 Copying 3D Data from CATIA V4 to V5 Document Copying 2D from CATIA V4 to CATIA V5 Having Access to one or several V4 Drawings within a model in CATIA V5 Migration in Batch Mode Transfer of SPACE Entities : Visualization of Version 4 Support Edge for Broken Contextual Features Improved Design in Context: Access to Solid Edges Opening a CATIA Version 4 Session in CATIA Version 5 Having Access to PRJ Files on NT

V5 to V4
Reading Directly V5 Data in V4 Saving a V5 Part as a V4 Model Saving a V5 Product As a V4 Session

Warning Prerequisites
V418 Model mandatory Cleaner V4 Checking V4 Model Data Before Copying It to V5 : Interactive Checker

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. 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.

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. First of all, CATIA Version 4.23 R1 must be installed on a UNIX machine. 2. You must then install a CATIA V5R4 configuration which 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:
CATIA.ENVTV5 : STRING; CATIA.ENVTV5 = `$HOME/CATENV/CATIA.V5R4.B04.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.

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. 5. 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.

Migration in Batch Mode

Converting Version 4 Model Data into Version 5 in Batch Mode Automatic Transfer of a Version 4 Model Comment during a V4 to V5 Migration Automatic Transfer of a Version 4 Detail Comment during a V4 to V5 Migration Extract V4 Model from Sequential File in Batch Mode Converting a Version 4 Session into Version 5 in Batch Mode

Converting a Version 4 Session into CATIA Version 5 in Batch Mode

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:

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".

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.

For information, the CART

SESSION.session document that will be migrated looks 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. Before launching the batch tool, you have to make sure that your environment is correctly set up. On NT, 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 the CART

SESSION.session document in the File Box by clicking on :

2. 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) by clicking on the button . Then click Open.

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.

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 directory you had chosen above: SESSION.CATProduct), in CATIA V5 in the

The CATProduct looks like this:

The impacts of the V4 to V5 conversion on the entities: V4 Session => CATProduct V4 Models => CATProducts or CATParts You have access to the Geometry and Specifications of the Session's Models and you can modify them in CATIA V5 (if you had chosen the AS SPEC Option).