Overview of the Migration of Applicative Profiles

This section describes how the migration of Applicative Profiles are handled in V6.

This page discusses:

Explanation

Applicative profiles are traditionally profiles that you create as a user. In addition to user-created profiles, certain DELMIA apps (such as Realistic Robot Simulation and Offline Programming) also create applicative profiles. A V5 applicative profile has a feature dictionary associated with it. In V6, the profiles are distinguished between Applicative profiles (those that have a corresponding CATFct file) and User profiles (those that do not have corresponding CATFct file).

Importing RRS and OLP Applicative Profiles

Applicative profiles created by Realistic Robot Simulation and Offline Programming in V5 are automatically imported into V6 as Applicative profiles. Each instance of a V5 applicative profile is imported as V6 Applicative profile instance. Since V5 and V6 applicative profiles may have different formats (due to obsolete and/or new attributes), attributes are imported according to a predefined mapping specification provided by RRS and OLP. No special tasks need to be performed to import RRS/OLP applicative profiles.

Importing a User Profile

A V5 user profile can be imported into V6 in either of two different ways. A default implementation of the applicative profile is provided that imports the V5 applicative profile as a user profile in V6. If you do not want to use the default implementation and prefer to modify the user profile structure, or if you want to import the V5 applicative profile as user profile in V6, you must perform the mapping via the CAA interface implementation (DNBIApplicativeProfileFBDI).

To import user applicative profiles you must store the corresponding V5 feature dictionary (.CATFct file) in a framework CNext\resources\graphic folder.

If the feature dictionary file is missing in the V6 <installation directory>\resources\graphic folder, a warning is displayed in the Import Report dialog box. and the applicative profile is not imported.

Importing Weld Time Tables

Applicative profiles created in DELMIA V5 Spot Welding are automatically imported into V6 as Controller Specific Applicative profiles. Each instance of a V5 applicative profile is imported as a V6 Applicative profile instance. Since V5 and V6 applicative profiles may have different formats (due to obsolete or new attributes), attributes are imported according to a predefined mapping specification provided by the Spot Welding app.

Import of the V5 WSUWeldTimeTable applicative profile is mapped to the V6 FanucWeldTimeTable controller specific profile as shown in the following table:

V5 Parameter NameV5 Value TypeDescriptionV5 Attribute TypeV6 Implementation
WeldTimeTable user profile

-Index

IntegerWeld Condition NumberUser profile Attributes Controller specific DNBSpotFanucWeldTable

-WeldConditionNumber

WeldTimeTable user profile

-OpenTime

RealWeld gun open timeUser profile Attributes Controller specific DNBSpotFanucWeldTable

same attribute

WeldTimeTable user profile

-HoldTime

RealWeld gun weld timeUser profile Attributes Controller specific DNBSpotFanucWeldTable

same attribute

WeldTimeTable user profile

-CloseTime

RealWeld gun close timeUser profile Attributes Controller specific DNBSpotFanucWeldTable

same attribute

Importing Device Attributes

All relevant OLP device attributes are migrated to the controller applicative profile, and all obsolete OLP device attributes are ignored. All user device attributes are migrated in a user profile instance labeled ImportedDeviceAttributes.

Note: RRS Device attributes are not migrated towards any profile, but are instead mapped to attributes on Motion Controller Attributes.

For example, in the figure above, the attributes PulseValue.1, PulseValue.2, PulseValue.3, ZeroValue.1, ZeroValue.2, and ZeroValue.3 are OLP Device Attributes that are migrated to Motoman Controller Profile.1 in the figure below.

UserAttrDouble, UserAttrBool, UserAttrString, UserAttrLENGTH, and UserAttrInt.1 are not OLP Device Attributes and are instead migrated towards ImportedDeviceAttributes.



You can access the imported values by double-clicking on the profiles.