MSC.Patran 2005 R2 SOL 600 Gasket Element February, 2005. - презентация

1 MSC.Patran 2005 R2 SOL 600 Gasket Element February, 2005

2 S1-2 Preference support for Nastran SOL 600 Gasket material, MATG, has been implemented SOL 600 Gasket Element

3 S1-3 SOL 600 Gasket Element

4 S1-4 SOL 600 Gasket Element

5 S1-5 SOL 600 Gasket Element Unloading Path Loading Path

6 S1-6 SOL 600 Gasket Element BEGIN BULK PARAM LGDISP 1 NLPARM 1 10 AUTO 1 25 P YES. MATG MAT MAT $ Displacement Dependent Table : loading TABLES ENDT $ Displacement Dependent Table : unloading TABLES ENDT GRID GRID GRID SPCADD FORCE SPCD SPCD $ Displacement Constraints of Load Set : fix_bottom SPC $ Displacement Constraints of Load Set : load_top SPC $ Deform Body Contact LBC set: steel_top BCBODY 3 3D DEFORM 3 0 BSURF 3 1 $ Deform Body Contact LBC set: gasket_bottom BCBODY 4 3D DEFORM 4 0 BSURF 4 2 ENDDATA

7 MSC.Patran 2005 r2 Bolt Preload and Gaskets May, 2005

8 S1-8 Bolt Preload Capabilities Bolt Preloads shareware utility has been implemented in 2005 r2

9 S1-9 Bolt Preload Capabilities Bolt Preloads Have 2 Types… Force The load is distributed to all node pairs such that the applied force is the net load between the sections Displacement The specified displacement value is imposed between each node pair – often a zero value is imposed to lock the bolt after the preload force is applied The applied force or displacement is applied to a single control node

10 S1-10 Bolt Preload Capabilities What it Does… Called from Shareware Menu Split the Mesh This typically means separating the existing mesh and creating duplicate nodes Match up the Node Pairs The specified load/constraint is imposed between node pairs – these node pairs are required Create the MPCs Create the Control Node Create the Applied Force or Displacement

11 S1-11 Bolt Preload Capabilities Mesh Topologies… 1D Beam Select the beam element where the mesh is to be split 2D Tria or Quad – Solids or Shells Select the element edges where the mesh is to be split 3D Solid – Hex, Wedge, Tet Select the element faces where the mesh is to be split Alternatives – see next page

12 S1-12 Bolt Preload Capabilities Mesh Topologies - Alternatives Delete Elements Select the element(s) where the mesh is to be separated and the elements will be deleted and the MPCs applied between nodes congruent to within the global model tolerance (requires that you select a vector giving the axial direction of the bolt) Vector Base Plane Select a vector (typically a base node and 2 nd node giving the direction) and the element edges/faces where the mesh is to be split will be selected automatically – very useful for tet meshes

13 S1-13 Bolt Preload Capabilities Supported Analysis Codes… MSC.Nastran or MSC.Marc MBOLTUS entries will be created for SOL 600 Tying Type 69 MPCs will be created for MSC.Marc Others Generic explicit mpcs will be created that will work for any analysis code For MSC.Nastran Solution Sequences other than SOL 600 change the analysis preference before creating the mpcs

14 S1-14 Example Simulation of a Cylinder Head Joint Bolt preload Preload with F on Control Node Lock with on Control Node Gasket material Contact

15 S1-15 Example Gasket Portion of Cylinder Head Portion of Cylinder Head Bolts Cylinder Head Cover Cylinder Head Cover

16 S1-16 Support for Gasket Materials How Gasket Materials Work… Gasket materials are designed to provide a seal and prevent gas leakage between components These components are typically bolted together They are orthotropic layered materials of varying thickness How Gasket Materials Work… Gasket materials are designed to provide a seal and prevent gas leakage between components These components are typically bolted together They are orthotropic layered materials of varying thickness

17 S1-17 Support for Gaskets How Data Is Input… Behavior is highly nonlinear, particularly in the thickness direction The loading and unloading curves are not the same and are described using a pressure vs. closure distance How Data Is Input… Behavior is highly nonlinear, particularly in the thickness direction The loading and unloading curves are not the same and are described using a pressure vs. closure distance

18 Sol 700 MSC.Patran 2005 r2 Support

19 S1-19 Nastran Input MSC.Patran with Nastran Preference MSC.Patran with Nastran Preference MSC.Nastran SOL 700.OP2, xdb,ARC,THS d3plot How Does It Work ? Dytran LS-DYNA MODULE

20 S1-20 Sol700 is the Explicit Nonlinear capability of MSC.Dytran LS-Dyna solver delivered in the MSC.Nastran user interface MSC.Nastran Preference SOL700

21 S1-21 Materials Support some of the MSC.Nastran Pref structural materials Support all the LS-Dyna Pref materials MSC.Nastran Preference SOL700 Same as in MSC.Nastran Pref Structural Same as in LS-Dyna Pref

22 S1-22 Materials MSC.Nastran Preference SOL700 CategoryMSC.Nastran materials MSC.Dytran LS-Dyna materials IsotropicMAT1, MATS1, MATHP MATD001, MATD003, MATD005, MATD006, MATD007, MATD012, MATD014, MATD015, MATD019, MATD020, MATD024, MATD027, MATD028, MATD030, MATD031, MATD057, MATD062, MATD063, MATD064, MATD100 2D Orthotropic MAT8MATD032 3D Orthotropic MAT3MATD022, MATD026, MATD057 2D Anisotropic MAT2, MATS1MATD103 3D Anisotropic MAT3, MATS1MATD103

23 S1-23 Elements & Properties MSC.Nastran Preference SOL700 DimensionElementsProperties 0DCELAS1, CELAS1D, CDAMP1, CDAMP1D, CONM2 PELAS, PDAMP 1DCBAR, CBEAM, CROD, CONROD, CELAS1, CELAS1D, CDAMP1, CDAMP1D, CVISC PBAR, PBARL, PBEAM, PBEAML, PROD, PELAS, PDAMP, PVISC 2DCTRIA3, CTRIAR, CQUAD4, CQUADR, CSHEAR PSHELL, PCOMP, PSHEAR 3DCTETRA, CPENTA, CHEXAPSOLID

24 S1-24 Loads/BCs MSC.Nastran Preference SOL700 Same as in MSC.Dytran Pref Same as in MSC.Marc Pref

25 S1-25 Analysis Solution Parameters of SOL700 SOL700 Parameters in other solutions SOL700,101 – Linear Static SOL700,106 – NonLinear Static SOL700,109 – Direct Transient Response SOL700,129 – NonLinear Transient Subcase Parameters Contact Table Access Results MSC.Nastran Preference SOL700

26 S1-26 Solution Parameters of SOL700 MSC.Nastran Preference SOL700

27 S1-27 MSC.Nastran Preference SOL700 FormParameters Execution Control Parameters DYSTATIC, DYBLDTIM, DYINISTEP, DYTSTEPERODE, DYMINSTEP, DYMAXSTEP, DYSTEPFCTL, DYTERMNENDMAS, DYTSTEPDT2MS General Parameters DYLDKND, DYCOWPRD, DYCOWPRP, DYBULKL, DYHRGIHQ, DYHRGQH, DYENERGYHGEN, DYSHELLFORM, DYSHTHICK, DYSHNIP Contact Parameters DYCONSLSFAC, DYCONRWPNAL, DYCONPENOPT, DYCONTHKCHG, DYCONENMASS, DYCONECDT, DYCONIGNORE, DYCONSKIPTWG Binary Output Database File Parameters DYBEAMIP, DYMAXINT, DYNEIPS, DYNINTSL, DYNEIPH, DYSTRFLG, DYSIGFLG, DYEPSFLG, DYRLTFLG, DYENGFLG, DYCMPFLG, DYIEVERP, DYDCOMP, DYSHGE, DYSTSSZ, DYN3THDT Entry DAMPGBL

28 S1-28 SOL700 Parameters in other solutions MSC.Nastran Preference SOL700

29 S1-29 Subcase Parameters MSC.Nastran Preference SOL700 Same as in MSC.Nastran Pref Sol600 TSTEPNL Same as in MSC.Nastran Pref Sol129

30 S1-30 Subcase Parameters - Contact Table MSC.Nastran Preference SOL700 Only in MSC.Nastran Pref Sol700

31 S1-31 Access Results MSC.Nastran Preference SOL700

32 Stop and Complete Workshop 1 Rigid Ball Penetration

33 Stop and Complete Workshop 2 Tapered Beam

34 MSC.Patran Quick Topology Optimization February, 2005

35 S1-35 Topology Optimization A new topology optimization has been introduced in MSC.Nastran This new topology optimization enhancement in SOL 200 finds an optimal distribution of material, given the package space, loads, and boundary conditions

36 S1-36 Topology Optimization MSC.Patrans Nastran preference was also enhanced to support the quick topology optimization in SOL 200 Derived from OPTISHAPE preference Retain some key features of OPTISHAPE preference More consistent look & feel More robust infrastructural support Analysis types, element properties, …

37 S1-37 Topology Optimization Customized Solution option has been added in the Analysis form Main entry to quick topology optimization

38 S1-38 Topology Optimization Use Customized Solutions option can be used to activate the quick topology optimization runs Default is off – normal SOL 200 optimization run Default – Normal SOL 200 run Quick topology optimization run

39 S1-39 Topology Optimization Design Domain option can be used to define the intent design domain Using element properties

40 S1-40 Topology Optimization Objective Constraints option can be used to define the optimization objectives and constraints

41 S1-41 Topology Optimization Optimization Control option can be used to define the optimization control parameters

42 S1-42 Case Study A Pump Lid HEXA8 elements Minimize compliance with 5% mass target

43 S1-43 Case Study A Bicycle Frame 2442 CQUAD4 elements Minimize compliance with 30% mass target

44 S1-44 Post Processing 2D result visualization

45 S1-45 Post Processing Import optimization results

46 S1-46 Post Processing Plot Element Density Distribution Each element has an normalized density as a design variable Xi i=1, n, n is the total number of elements If an element is important and need to be retained, the element density = 1.0 If an element is not important and need to be removed, the element density = 0.0 Ideal goal is to have Xi be 1.0 or 0.0 Discrete optimization problem (Xi = 1 or 0) is very hard to solve due to the large model size

47 S1-47 Post Processing Threshold Value (TV) is set to identify which elements should be retained If Xi>=TV, the element is retained Otherwise this element is removed Threshold Value could be an important factor when there are many semi- density values For example Xi=0.3, 0.4, 0.5 …

48 S1-48 Post Processing HIGH_DENS_GRP group is created automatically to store and track the retained elements

49 S1-49 Post Processing W/ Threshold = 0.0, all elements are retained

50 S1-50 Post Processing Automatic algorithm is now available to smooth the analytical results

51 S1-51 Post Processing Smoothing

52 S1-52 Post Processing 3D Smoothing

53 S1-53 Post Processing 3D Smoothing

54 Stop and Complete Workshop 3 Topology Optimization

55 Stop and Complete Workshop 4 Solid Topology Optimization

56 MSC.Patran 2005 R2 Arbitrary Beam January, 2005

57 S1-57 Over the years, the capability of beam element has grown steadily from constant cross section of PBAR to variable cross section of PBEAM However, users are required to compute the sectional properties in order to utilize BAR and/or BEAM elements in the analysis PBARL and PBEAML were added for popular cross sectional profiles Arbitrary Beam

58 S1-58 Users are still left to search for modeling alternatives for 1D structural component with arbitrary cross sectional shape A new user interface for describing the shape of cross section for CBAR and CBEAM element types is now available Create an arbitrary cross section Select dimension instead of properties PBRSECT or PBMSECT will be created automatically Arbitrary Beam

59 S1-59 This is a licensed feature in MSC.Nastran No additional license is required in MSC.Patran Arbitrary Beam

60 S1-60 User Scenario [-.1,0] [.1,0] [.5,.6] [.1,.5] [-.1,3] [.5,.5] [.1,.6] [.1,2.5] [.1,2.4] [.1,3] [.5,2.4] [.5,2.5] [-.1,2.5] [-.1,2.4] [-.5,2.4] [-.5,2.5] [-.5,.6] [-.1,.5] [-.5,.5] [-.1,.6] Analysis of cantilever beam w/ arbitrary cross sectional shape

61 S1-61 User Scenario

62 S1-62 User Scenario Patran will compute the sectional properties in order to utilize BAR and/or BEAM elements Only Properties option is allowed The following warning message will be issued when Dimensions option is selected Beam Section "Section_1" is an Arbitrary Shape. Value Type "Dimensions" is not supported for Arbitrary Beam Sections. You must use Value Type "Properties"

63 S1-63 User Scenario. CBAR CBAR CBAR CBAR CBAR CBAR CBAR CBAR CBAR CBAR PBAR* * * *.

64 S1-64 User Scenario Select Dimensions instead of Properties PBRSECT or PBMSECT will be created automatically PBMSECT & PBRSECT only reference SET3 IDs following OUTP/INP SET1 reference is not supported

65 S1-65 User Scenario. BEGIN BULK. $ SET3 1 POINT PBRSECT 1 1 GS OUTP=1 $ CBAR CBAR $ GRID GRID $. $ POINT POINT POINT POINT POINT POINT POINT POINT POINT POINT POINT POINT POINT POINT POINT POINT POINT POINT POINT POINT

66 Stop and Complete Workshop 5 Arbitrary Beam Section

67 MSC.Patran 2005 r2 BEAM Offsets and Orientations April, 2005

68 S1-68 Patran 2004 added the "Element" option to beam element offset input Using the "Element" option does not change the offset definition input within Patran It is merely a convenience that offers the option of having the offset transformed to the element coordinate system in the bdf for ease in reading or review Beam Offsets and Orientations

69 S1-69 Per request, there is a design change in Patran 2005 r2 to enhance the usability of this implementation Specifying the "Element" option implies that the input offsets are in the element coordinate system 3D beam display options including the offsets would interpret the offsets in the element system Properties/Show of beam offsets would interpret the offsets in the element system Beam Offsets and Orientations

70 S1-70 Previous behavior CP and CD of GRIDs are defined in the cylindrical coordinate system Beam Offsets and Orientations Offset Interpretation flag Offset defined in r direction of coord 1 in Patran The default Analysis interpretation option is used

71 S1-71 Beam Offsets and Orientations. GRID GRID GRID CBAR CBAR CBAR CBAR CBAR CBAR CBAR CBAR Offset was originally defined in r direction of coord 1 in Patran Offset was written in r direction in coord 1 (CD of GRIDs)

72 S1-72 Previous behavior But w/ Element offset interpretation flag Beam Offsets and Orientations Offset defined in r direction of coord 1 in Patran The use of Element option does not change the Patran input definition Offset Interpretation flag

73 S1-73 Beam Offsets and Orientations. GRID GRID GRID CBAR GEE CBAR GEE CBAR GEE CBAR GEE CBAR GEE CBAR GEE CBAR GEE CBAR GEE Offset was originally defined in r direction of coord 1 in Patran Offset was written in y direction in element coord in Nastran

74 S1-74 New in 2005 r2 Beam Offsets and Orientations Offset defined in y direction of element coordinate system in Patran In the new implementation, the "Element" option implies that the input offsets are in the element coordinate system Offset Interpretation flag

75 S1-75 Beam Offsets and Orientations. GRID GRID GRID CBAR GEE CBAR GEE CBAR GEE CBAR GEE CBAR GEE CBAR GEE CBAR GEE CBAR GEE Offset was originally defined in y direction of element coordinate system in Patran Offset was written in y direction in element coord in Nastran

76 S1-76 Advantage of the new design One property set (offset vector) can be use for complex non-planar surfaces Great for surfaces where orientation vectors are not consistent Minimize the need to derive orientation vector based on Displacement (Analysis) or user-defined coordinate system Beam Offsets and Orientations

77 S1-77 Previous behavior Unable to use one consistent offset vector within a geometric entity Nearly impossible to define offset vectors Beam Offsets and Orientations

78 MSC.Patran 2005 R2 Nastran Preference Enhancements Nested Coordinate Systems December, 2004

79 S1-79 Coordinate Systems in MSC.Patran have been enhanced to better support the coordinate system definitions in MSC.Nastran The default behavior for coordinate systems in Patran does not change The new capability is exposed only when indicated by the user within the Translation Parameters form Nested Coordinate Systems

80 S1-80 Coordinate system definitions have been expanded to allow a coordinate system to be defined relative to a reference coordinate system In MSC.Nastrans case, this enables the use of the RID field of the CORD2x formats The coordinate system origin and rotation matrix are now stored relative to the reference frame Nested Coordinate Systems

81 S1-81 No changes are required for the Create forms Except Create:Coord:Normal The existing user interface for the creation of coordinate frames is already adequate for creating coordinate frames that calls a reference coordinate frame Nested Coordinate Systems

82 S1-82 The coordinate system Show spreadsheet has the new data added to it Nested Coordinate Systems Origins in reference coordinate system Axes in reference coordinate system

83 S1-83 A new Coord Frame Coordinates control has been added to the Translation Parameters forms for each applicable analysis system Indicating whether or not to use the reference frame in the coordinate system definitions within the analysis input deck Nested Coordinate Systems

84 S1-84 Nested Coordinate Systems Coord 101 was created relative to Coord 0 Coord 102 was created relative to Coord 0 Coord 103 was created relative to Coord 102

85 S1-85 Nested Coordinate Systems. GRID GRID GRID GRID GRID CORD2R CORD2R CORD2R Circular support of nested coordinate system - Forward translation - Input file reader

86 S1-86 Nested Coordinate Systems Coord 1 - Cord2x format - Created relative to Coord 0 Coord 2 - Cord1x format - Created relative to 3 existing nodes * Node 101 * Node 103 * Node 102 Coord 1 Coord 2

87 Stop and Complete Workshop 6 Nested Coordinate Systems

88 MSC.Patran 2005 R2 Nastran Preference Enhancements Cord1x Support December, 2004

89 S1-89 Coordinate systems have been enhanced to support the CORD1x (CORD1C, CORD1R, and CORD1S) cards in MSC.Nastran Node references from the coordinate system definitions are now preserved Cord1x Support

90 S1-90 No changes are required for the Create forms The existing user interface for the creation of coordinate frames is already adequate for creating coordinate frames that reference nodes Cord1x Support

91 S1-91 References to the nodes are stored in the coordinate frame data Cord1x Support If a reference frame other than Coord 0 is specified, then that reference shall persist in the database, along with the local origin and rotation matrix If nodes are specified on input for the 3Point option, then the node references shall be stored, such that they may be output to CORD1x cards, if the user so chooses

92 S1-92 The coordinate system Show spreadsheet has the new data added to it Cord1x Support Prior Behavior New Behavior Axes in Reference Coordinate System

93 S1-93 A new Coord Frame Coordinates control has been added to the Translation Parameters forms for each applicable analysis system Indicating whether or not to use the reference nodes in the coordinate system definitions within the analysis input deck Cord1x Support

94 S1-94 Options include: Global (default) Reference Frame Instructs the use of the RID field in the CORD2x Reference Nodes Instructs the use of CORD1x where applicable Reference Frame and Nodes Cord1x Support

95 S1-95 Coord Frame Coordinates control The default value for the new control is Global Can be overridden by a settings.pcl entry analysis_coord_coordinates, set to either global reference frame reference nodes both Cord1x Support

96 Stop and Complete Workshop 7 Cord1x Support

97 MSC.Patran 2005 R2 SUBCOM/SUBSEQ Support February, 2005

98 S1-98 Load Case definitions have been enhanced to support Nastran SUBCOM/SUBSEQ Define load case as a linear combination of a set of static load cases e.g. case3 = a * case1 + b * case2 Load Case form will now allow loadcases to be combined Using a linear combination of previously existing loadcases SUBCOM/SUBSEQ Support

99 S1-99 The Nastran forward translator will generate the appropriate SUBCOM/SUBSEQ entries for these special loadcases The input file reader is also updated to create these combination loadcases from SUBCOM/SUBSEQ entries during import The database import operation has been modified to transfer these combination loadcases appropriately SUBCOM/SUBSEQ Support

100 S1-100 User Interface A new Combination type has been added to Load Case:Create and Load Case:Modify Modification of combination loadcases allows an existing combination loadcase to be specified Rename capability is also supported Combination loadcases can be deleted through Load Case:Delete Sub-loadcases will not be deleted in the same operation Referential integrity is preserved when deleting regular loadcases An error will be generated when it is referenced by a combination loadcase SUBCOM/SUBSEQ Support

101 S1-101 SUBCOM/SUBSEQ Support Previous releases The Assign/Prioritize Loads/BCs button is now replaced by a new, more generic name.

102 S1-102 User Scenario 1 3 subcases -Case_1 -Pinned displacement & pressure loading -Case_2 -Pinned displacement & one concentrated force -Case_3 -Pinned displacement & 1g grav load 2 Combined subcases -Subcom_1 -Combination of Case_2 & Case_3 -Subcom_2 -Combination of Case_1, Case_2 & Case_3 -W/ subcase sequence coefficient of 3. for Case _3

103 S1-103 Create 3 load cases first User Scenario 1

104 S1-104 Create combined case 1 Using coefficient of 1.0 for both load cases User Scenario 1

105 S1-105 Create combined case 2 Using coefficient of 3.0 for Grav load case User Scenario 1

106 S1-106 User Scenario 1..SUBCASE 1 $ Subcase name : Force SUBTITLE=Force SPC = 2 LOAD = 2 DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCASE 2 $ Subcase name : Grav SUBTITLE=Grav SPC = 2 LOAD = 4 DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCOM 3 $ Subcase name : combined_1 SUBTITLE=combined_1 SUBSEQ = 1., 1. DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCASE 4 $ Subcase name : Pressure SUBTITLE=Pressure SPC = 2 LOAD = 6 DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCOM 5 $ Subcase name : combined_2 SUBTITLE=combined_2 SUBSEQ = 1., 3., 1. DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL. Case_3 – Grav Loading Case_2 – Force Loading Case_1 – Pressure Loading Combined_1 – Force & Grav combination Combined_2 – Pressure, Force & Grav combination

107 S1-107 User Scenario 2 3 subcases -Case_1 -Pinned displacement & pressure loading -Case_2 -Pinned displacement & one concentrated force -Case_3 -Pinned displacement & 1g grav load 3 Combined subcases -Subcom_1 -Combination of Case_2 & Case_3 -Subcom_2 -Combination of Case_1, Case_2 & Case_3 -W/ subcase sequence coefficient of 3 for Case _3 -Subcom_3 -Combination of Case_1 & Case_2 Combined case 3 was selected first Combined case 1 was selected second

108 S1-108 SUBCASE 1 $ Subcase name : Force SUBTITLE=Force SPC = 2 LOAD = 2 DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCASE 2 $ Subcase name : Pressure SUBTITLE=Pressure SPC = 2 LOAD = 4 DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCOM 3 $ Subcase name : combined_3 SUBTITLE=combined_3 SUBSEQ = 1., 1. DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCASE 4 $ Subcase name : Grav SUBTITLE=Grav SPC = 2 LOAD = 6 DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCOM 5 $ Subcase name : combined_1 SUBTITLE=combined_1 SUBSEQ = 1., 0., 1. DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCOM 6 $ Subcase name : combined_2 SUBTITLE=combined_2 SUBSEQ = 1., 1., 3. DISPLACEMENT(SORT1,REAL)=ALL. User Scenario 2 Case_2 – Force Loading Case_3 – Grav Loading Combined_3 – Pressure & Force combination Case_1 – Pressure Loading Combined_1 – Pressure & Grav combination Combined_2 – Pressure, Force & Grav combination

109 S1-109 User Scenario 3 3 subcases -Case_1 -Pinned displacement & pressure loading -Case_2 -Pinned displacement & one concentrated force -Case_3 -Pinned displacement & 1g grav load 3 Combined subcases -Subcom_1 -Combination of Case_2 & Case_3 -Subcom_2 -Combination of Case_1, Case_2 & Case_3 -W/ subcase sequence coefficient of 3 for Case _3 -Subcom_3 -Combination of Case_1 & Case_2 All 3 combined cases were selected Only 2 out of 3 subcases were selected

110 S1-110 User Scenario 3 SUBCASE 1 $ Subcase name : Force SUBTITLE=Force SPC = 2 LOAD = 2 DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCASE 2 $ Subcase name : Grav SUBTITLE=Grav SPC = 2 LOAD = 4 DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCOM 3 $ Subcase name : combined_1 SUBTITLE=combined_1 SUBSEQ = 1., 1. DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCASE 4 $ Subcase name : combined_3 SUBTITLE=Pressure SPC = 2 LOAD = 6 SUBCOM 5 $ Subcase name : combined_3 SUBTITLE=combined_3 SUBSEQ = 1., 0., 1. DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL SUBCOM 6 $ Subcase name : combined_2 SUBTITLE=combined_2 SUBSEQ = 1., 3., 1. DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL Case_2 – Force Loading Case_1 – Pressure Loading Combined_1 – Force & Grav combination Case_3 – Grav Loading Combined_3 – Pressure & Force combination Combined_2 – Pressure, Force & Grav combination Pressure subcase was not selected in the Subcase Select by the user. Since it is referenced in combined subcase 3, Patran will automatically insert this subcase in the case control, but with no output request.

111 S1-111 User Scenario 3 Input file reader has also been updated to support the combined cases

112 MSC.Patran 2005 R2 MSC.Nastran Optimization Support Subcase Dependent Constraints January, 2005

113 S1-113 The underlying architecture of the MSC.Nastran optimization analysis support has been updated Support the definition of MSC.Nastran Subcase dependent constraints and objectives More user friendly Consistent with other Nastran preference layouts Subcase Dependent Constraints

114 S1-114 In the previous releases, design constraints defined in the current design study are automatically selected Restrict subcases to use same set of design constraints DESSUB = 1 for all subcases In 2005 R2, Subcase Create form has been modified to enable the selection of unique design constraints for each individual subcase Subcase Dependent Constraints

115 S1-115 General design objectives, DRESP1 & DRESP2, are also supported in R2 New design objectives can be treated as subcase dependent variables New design objectives can also be selected from the Subcase Create form (same as design constraints) Subcase Dependent Constraints

116 S1-116 Subcase Dependent Constraints Analysis Set Up Design Study Creation

117 S1-117 Subcase Dependent Constraints Analysis Set Up Design Study Creation

118 S1-118 Subcase Dependent Constraints

119 S1-119 Subcase Dependent Constraints. SUBCASE 1 … DESOBJ = 1 DESSUB = 1000 … SUBCASE 2 … DESSUB = 2000 … /* Objective for subcase 1*/ DRESP1 1 WEIGHT /* Constraints for subcase 1*/ DCONADD DCONSTR DCONSTR DCONSTR DRESP1 101 DRESP1 102 DRESP1 103 /* Constraints for subcase 2*/ DCONADD DCONSTR DCONSTR DCONSTR DRESP1 201 DRESP1 202 DRESP Sample Nastran deck w/ 3 constraints in subcase 1 2 constraints in subcase 2 Objective is defined in subcase 1

120 MSC.Patran 2005 R2 Optimization Support Min/Max January, 2005

121 S1-121 The MinMax design task is now supported Commonly used in MSC.Nastran optimization analysis Parameters associated with the MinMax design task definition are stored in the database Both forward translator and input file reader have been enhanced accordingly Min/Max

122 S1-122 New MinMax option has been added in the Design Study form Min/Max

123 S1-123 A new Select Min/Max… option has been added in the Design Study creation form Min/Max

124 S1-124 MinMax option can be selected and associated with each subcase Min/Max

125 S1-125 Sample Nastran input deck for the MinMax design task Min/Max SUBCASE 1. DESOBJ = 10. /* Bulk Data Section*/ DRESP1 100 DISP FRDISP DRESP1 200 DISP FRDISP DRESP1 300 DISP FRDISP DRESP2 10 beta BETA Min C1 C2 C3 DRESP

126 MSC.Patran 2005 R2 Nonstructural Mass Properties January, 2005

127 S1-127 Nonstructural Mass Properties MSC.Nastran non-structural mass (NSM & NSML) are now supported NSM and MSML are used to define masses that affect the behavior of specific element types but are not directly part of the structure of the model

128 S1-128 Nonstructural Mass Properties NSM & NSML support the following line element types CBAR, CBEAM, CBEND, CROD, CTUBE, CONROD NSM & NSML support the following surface element types CQUAD4, CQUAD8, CQUADR, CTRIA3,CTRIA6, CTRIAR, CSHEAR, CRAC2D, CCONEAX NSM & NSML support the following property types PSHELL, PCOMP, PBAR, PBARL, PBEAM, PBEAML, PBCOMP, PROD, CONROD, PBEND, PSHEAR, PTUBE, PCONEAX, PRAC2D, PCONEAX

129 S1-129 Nonstructural Mass Properties NSM & NSML forms are implemented as part of the Tools pull down menu NSM Properties forms are Nastran preference specific

130 S1-130 Nonstructural Mass Properties NSM mass can applied as Lumped vs. Distributed The applied mass for a distributed NSM will be applied directly to each element in the application region The applied mass for a lumped NSM will be spread evenly over all of the elements in the application region

131 S1-131 Nonstructural Mass Properties Nonstructural mass can be applied to elements or property set Applying to elements Applying to properties

132 S1-132 Nonstructural Mass Properties The Select form has been added to allow for the selection of NSM properties Multiple sets of NSMs can be defined in the model Only the selected sets will be used in the analysis

133 S1-133 Nonstructural Mass Properties Example: A lumped mass value of 20 Applied to 10 elements SOL 101 $ CEND NSM = 1 ECHO = NONE $ Direct Text Input for Global Case Control Data SUBCASE 1 $ Subcase name : Default SUBTITLE=Default DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL BEGIN BULK PARAM POST 0 PARAM AUTOSPC YES PARAM PRTMAXIM YES $ PSHELL $ CQUAD CQUAD CQUAD CQUAD $ Nonstructural Mass entries NSML1 2 ELEMENT NSMADD 1 2 $ MAT $ Nodes of the Entire Model GRID GRID GRID GRID $

134 S1-134 Nonstructural Mass Properties Example: A distributed mass value of 20 Applied to 10 elements SOL 101 $ CEND NSM = 1 ECHO = NONE $ Direct Text Input for Global Case Control Data SUBCASE 1 $ Subcase name : Default SUBTITLE=Default DISPLACEMENT(SORT1,REAL)=ALL SPCFORCES(SORT1,REAL)=ALL STRESS(SORT1,REAL,VONMISES,BILIN)=ALL BEGIN BULK PARAM POST 0 PARAM AUTOSPC YES PARAM PRTMAXIM YES $ PSHELL $ CQUAD CQUAD CQUAD CQUAD $ Nonstructural Mass entries NSM1 2 ELEMENT NSMADD 1 2 $ MAT $ Nodes of the Entire Model GRID GRID GRID GRID $

135 S1-135 Nonstructural Mass Properties Example: A distributed mass value of 50. Applied to property set PROP_2 PROP_1 PROP_2

136 S1-136 Nonstructural Mass Properties $ SOL 101 $ CEND. NSM = 1. BEGIN BULK. $ PSHELL $ Pset: "Prop_1" will be imported as: "pshell.1" CQUAD CQUAD $ Elements and Element Properties for region : Prop_2 PSHELL $ Pset: "Prop_2" will be imported as: "pshell.2" CQUAD CQUAD CQUAD CQUAD CQUAD CQUAD CQUAD CQUAD CQUAD $ Nonstructural Mass entries NSM1 2 PSHELL NSMADD 1 2 $ MAT $ GRID GRID GRID GRID $

137 MSC.Patran 2005 r2 CFAST Property Enhancement March, 2005

138 S1-138 An option has been added to automatically calculate the stiffness values of fastener connectors Minimize the need for manual calculation Translational stiffness calculations are based on Douglas and Huth formulas CFAST Properties

139 S1-139 CFAST Properties Previous releases Elements : Create : Connector : Fastener

140 S1-140 CFAST Properties Previous releases Element Properties : Create : 1D : Fastener Connector

141 S1-141 CFAST Properties Elements : Create : Connector : Fastener

142 S1-142 CFAST Properties Element Properties : Create : 1D : Fastener Connector

143 S1-143 CFAST Properties Element Properties : Forward Translation A single Patran Property is translated into many Nastran Properties depending on the connected shell thickness and material No more laborious hand calculation

144 S1-144 CFAST Properties Element Properties : Input file reader With the comments in the BDF, the original Patran Property is restored. Many BDF Properties are compressed into ONE property with a formula

145 MSC.Patran 2005 r2 Large XDB Support May, 2005

146 S1-146 As users model sizes have steadily increased, MSC.Access database objects have exceeded their entry capacity due to use of a single word access key for keyed objects especially in transient analysis. A multi-key storage method has been implemented to support ever increasing database sizes. A companion MSC.Patran modification has also been implemented in the upcoming 2005 r2 release. Large XDB Support

147 S1-147 A new NASTRAN system cell DBCFACT is introduced for creating a XDB file using the new multi-key data format The new multi-key data format is still NOT the default Setting DBCFACT=4 will force the new multi-key access method In the site RC file, or As a NASTRAN entry in the input file MSC.NASTRAN will automatically use the multi-key data format if needed to accommodate data storage in the XDB. Large XDB Support

148 S1-148 Note the following limitations apply: MSC.Explore now supports the multi- key access method Large XDB Support

149 MSC.Patran 2005 r2 Integrated Random Solution April, 2005

150 S1-150 Integrated random solution has been implemented as a core feature This utility was previously available as a shareware utility in Patran 2005 The same shareware utility from Patran 2005 release is still available in 2005 r2 No update or maintenance to the shareware utility going forward This offering is a licensed option Significant enhancements will follow in future releases Integrated Random Solution

151 S1-151 Integrated Random Solution

152 S r2 enhancements Support of large xdb Default RECL=1024 Supported by both (shareware/core) version Larger RECL Supported by both (shareware/core) version BBBT (Nastran 2005+) Shareware will crash where as Tools menu version will issue message that bbbt is not supported Integrated Random Solution

153 S r2 enhancements Nastran input deck extension no longer hard wired to.bdf Chose.dat or.bdf extensions Fixed random input form overwrite problem when using auto correlation. Added separate file input form for external ranps.inp files to prevent other graphics problems Fixed crashed caused by xyplot bug in Patran Commented out old defaults while creating jobs This will let Patran's job defaults be used where not specifically required by msc.random Integrated Random Solution

154 S1-154 Planned enhancements for future releases Complete new user interface Full documentation & HELP Add capabilities XDB Capabilities Allow record length larger than 1024 Allow xdb created by new BBBT method (virtually unlimited XDB size) Frequency Response Analysis Support new SPCD method Support both Real/Imag and Mag/Phase results Future Enhancements

155 S1-155 Add capabilities (Cont.) Random Input Unlimited number of RANDPS entries Log and Linear interpolation and extrapolation Random Response Calculation XY Plot Von Mises for plate/solid elements PSDF at Center as well as at Corner Cross Spectral Density and Cross Auto Correlation Plot Relative response (calculation on fly without MPC) RMS within band-width RMS Fringe Von-Mises for plate/solid (center and corners) Log-Log and Linear integration Scale factor for fringe plots (e.g. 3 * RMS) Import result as scalar rather than tensor to prevent improper use Future Enhancements

156 S1-156