Beruflich Dokumente
Kultur Dokumente
Administrator
Laura Boyle,
Lockheed Martin Aeronautics
CAD Development & Support
Software Engineer
This is the true story of what life is like for the Lockheed
Martin Aeronautics (LM Aero) CATIA V5 CATSettings ADMIN.
Lets follow the ADMIN as they
Give an overview of the CATIA V5 CATSettings hierarchical
Game
LM Aero Startup
creates CATIA V5
Environment file
based on user inputs
CATReferenceSettingPath=P:\Is\Apps\Catia\LM\v5r17\prod\CATSettings\LMAeroBase;
P:\Is\Apps\Catia\LM\v5r17\prod\CATSettings\F35;
P:\Is\Apps\Catia\LM\v5r17\prod\lmapps\CATSettings;
P:\Is\Apps\Catia\LM\v5r17\prod\CATSettings\cmi
CATUserSettingPath=U:\catv5\v5r17\CATSettings
CATReferenceSettingPath=P:\Is\Apps\Catia\LM\v5r17\prod\CATSettings\LMAeroBase;
P:\Is\Apps\Catia\LM\v5r17\prod\CATSettings\F35;
P:\Is\Apps\Catia\LM\v5r17\prod\lmapps\CATSettings;
P:\Is\Apps\Catia\LM\v5r17\prod\CATSettings\cmi
CATUserSettingPath=U:\catv5\v5r17\CATSettings
Administratively
Locked
Not
Locked
PRODUCTION Environment
Notify CATIA V5 production users affected by the ADMIN
CATSettings modifications
found that only the customized attribute values were exported to XML files
6 attributes
V5R17 To V5R18
LineTypeRepository
(V5R18)
CATBatGenXML Output
EMPTY
6 attributes
Detail Information
CATSettings files store attribute values customized during session of CATIA V5.
CATSettings are stored when user accesses Tools->Options panel or when they set default paths and data when using
any of workbenches or CATIA V5 functions.
These variables are set in the CATIA V5 Environment Start file and define location of customized CATSettings files
CATReferenceSettingPath variable is used to set the ADMIN level customized CATSettings directory paths
CATUserSettingPath variable is used to set the users customized CATSettings directory path
At LM Aero, we use an in-house developed Startup application to customize the CATIA V5 Environment Start file
with LM Aero CATIA V5 environment paths based on users choice of Site, Program ,CATIA V5 Release,
License/Discipline, and 3rd Party Application choice prior to CATIA start
CATReferenceSettingPath=P:\
CATReferenceSettingPath=P:\Is\
Is\Apps\
Apps\Catia\
Catia\LM\
LM\v5r16\
v5r16\prod\
prod\CATSettings\
CATSettings\LMAeroBase;
P:\
P:\Is\
Is\Apps\
Apps\Catia\
Catia\LM\
LM\v5r16\
v5r16\prod\
prod\CATSettings\
CATSettings\F35;
P:\
P:\Is\
Is\Apps\
Apps\Catia\
Catia\LM\
LM\v5r16\
v5r16\prod\
prod\lmapps\
lmapps\CATSettings;
P:\
P:\Is\
Is\Apps\
Apps\Catia\
Catia\LM\
LM\v5r16\
v5r16\prod\
prod\CATSettings\
CATSettings\cmi
CATUserSettingPath=U:\
CATUserSettingPath=U:\catv5\
catv5\v5r16\
v5r16\CATSettings
1st level : Dassault Hard Coded Defaults which are superseded by any customized attribute value
defined in Start file
One BIG PROBLEM for LM Aero: The default settings units are metric, not English units. There is NO WAY
to permanently alter the Dassault default values and if customized attribute value is not found, metric will be
used.
2nd thru N levels: ADMIN Paths set to define location of customized CATSettings files
CATSettings values defined at the N level supersede N-1 level, N-1 supersede N-
CATSettings values defined at the N level supersede N-1 level, N-1 supersedes N-2etc
Last level: User CATSettings found in CATUserSettingPath directory location supersede all ADMIN
level CATSettings values UNLESS LOCKED in ADMIN CATSettings
Example:
hoices
Example: Paths
Paths defined
defined based
based on
on Program,
Program, 3rd
3rd party
party application
application cchoices
CATReferenceSettingPath=P:\
CATReferenceSettingPath=P:\Is\
Is\Apps\
Apps\Catia\
Catia\LM\
LM\v5r16\
v5r16\prod\
prod\CATSettings\
CATSettings\LMAeroBase;
P:\
P:\Is\
Is\Apps\
Apps\Catia\
Catia\LM\
LM\v5r16\
v5r16\prod\
prod\CATSettings\
CATSettings\F35;
P:\
P:\Is\
Is\Apps\
Apps\Catia\
Catia\LM\
LM\v5r16\
v5r16\prod\
prod\lmapps\
lmapps\CATSettings;
P:\
P:\Is\
Is\Apps\
Apps\Catia\
Catia\LM\
LM\v5r16\
v5r16\prod\
prod\CATSettings\
CATSettings\cmi
CATUserSettingPath=U:\
CATUserSettingPath=U:\catv5\
catv5\v5r16\
v5r16\CATSettings
200 files x avg 5 attributes per file customized = 1000 customized attributes!
CATSettings directories
FOR PROD MODE
Administratively
Locked
Not Locked
Create XML files of CATSettings files using earlier CATIA Release(e.g. - v5r17)
Create .CATSettings files from XML files using later CATIA Release (e.g. v5r18)
Per CATIA V5R18 Help Documentation, the following files can not
be exported or imported via these utilities
What happened when LM Aero ADMIN used the migrate tools? (CATIA V5R17 to CATIA
V5R18 migration)
Started with the COMMON LM Aero ADMIN Settings (used by all users) = 114 .CATSettings files
Created simple MS DOS Scripts to run the CATBatGenXMLSet and CATBatImpXMLSet utilities on
directory of files
CATBatGenXMLSet Errors -> Setting X is Empty errors on 2 files (CATProduct.CATSettings and
VRCommands.CATSettings)
CATBatImpXMLSet Errors->None reported from utility and all 114 CATSettings files created
During verification of the migrated CATSettings, found some attributes values that did not get
migrated correctly
First signs of invalid migration discovered in the form of missing locks when looking at the V5R17ToV5R18
file in interactive session Tools->Options panel vs. the V5R17 file interactive session Tools->Options panel.
15 Locks missing out of 90 total locked attributes (same results for CATIA V5R16 To CATIA V5R17)
Locks missing were on Dassault default attribute values
Used V5R17 To V5R18 migrated CATSettings files to test generation of XML files for future migrations
We created XMLs of the migrated files and got Set X is Empty Errors on 24 files (including
CATProduct and VRCommands file)
Upon examination of V5R17 To V5R18 CATSettings in XML format, we found that only the
customized attribute values were exported to XML files
Beware workbench flags that may override user and ADMIN settings
Tubing workbench in V5 R17 had flag that overrode CATSetting value