This action might not be possible to undo. Are you sure you want to continue?
MSC.Software Corporation 2 MacArthur Place Santa Ana, CA 92707 USA Telephone: (800) 345-2078 Fax: (714) 784-4056
MSC.Software GmbH Am Moosfeld 13 81829 Munich, Germany Telephone: (49) (89) 43 19 87 0 Fax: (49) (89) 43 61 71 6
MSC.Software Japan Ltd. Shinjuku First West 8F 23-7 Nishi Shinjuku 1-Chome, Shinjuku-Ku Tokyo 160-0023, JAPAN Telephone: (81) (3)-6911-1200 Fax: (81) (3)-6911-1201
This documentation, as well as the software described in it, is furnished under license and may be used only in accordance with the terms of such license. MSC.Software Corporation reserves the right to make changes in specifications and other information contained in this document without prior notice. The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not intended to be exhaustive or to apply to any particular engineering problem or design. MSC.Software Corporation assumes no liability or responsibility to any person or company for direct or indirect damages resulting from the use of any information contained herein. User Documentation: Copyright ©2009 MSC.Software Corporation. Printed in U.S.A. All Rights Reserved. This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this document, in whole or in part, without the prior written consent of MSC.Software Corporation is prohibited. The software described herein may contain certain third-party software that is protected by copyright and licensed from MSC.Software suppliers. Contains IBM XL Fortran for AIX V8.1, Runtime Modules, (c) Copyright IBM Corporation 1990-2002, All Rights Reserved. MSC, MSC/, MSC Nastran, MD Nastran, MSC Fatigue, Marc, Patran, Dytran, and Laminate Modeler are trademarks or registered trademarks of MSC.Software Corporation in the United States and/or other countries. NASTRAN is a registered trademark of NASA. PAM-CRASH is a trademark or registered trademark of ESI Group. SAMCEF is a trademark or registered trademark of Samtech SA. LS-DYNA is a trademark or registered trademark of Livermore Software Technology Corporation. ANSYS is a registered trademark of SAS IP, Inc., a wholly owned subsidiary of ANSYS Inc. ACIS is a registered trademark of Spatial Technology, Inc. ABAQUS, and CATIA are registered trademark of Dassault Systemes, SA. EUCLID is a registered trademark of Matra Datavision Corporation. FLEXlm is a registered trademark of Macrovision Corporation. HPGL is a trademark of Hewlett Packard. PostScript is a registered trademark of Adobe Systems, Inc. PTC, CADDS and Pro/ENGINEER are trademarks or registered trademarks of Parametric Technology Corporation or its subsidiaries in the United States and/or other countries. Unigraphics, Parasolid and I-DEAS are registered trademarks of UGS Corp. a Siemens Group Company. All other brand names, product names or trademarks belong to their respective owners.
Patran Release Guide
Patran 2008 r2 at a Glance
Key Highlights 2 CAD Access 2 InterOp R18 SP1/SP3 2 Parasolid 19 2 Catia V5 R18 2 NX 5 / NX 6 2 Automatic Feature Recognition 2 MD Nastran and MSC Nastran Support (Patran 2008 r2) Optimization (SOL 200) 2 Implicit Nonlinear Analysis (SOL 400) 3 Explicit Nonlinear Analysis (SOL 700) 3 Thermal-Structural Interaction (SOL 101) 3 Results Access 3 Marc Support 3 New Physics Types 3 Results Access 4 General Enhancements 4 Right Mouse Button (RMB) (Patran 2008 r2) 4 New GUI Skins (Patran 2008 r2 - Pre-Release) 4 Native 64 Bit Port (Patran 2008 r2 - Pre-Release) 4 Batch Image Rendering 4 SimManager Integration 4 SimXpert Integration 4 MSC Sinda Preference 4 Laminate Modeler 5 Utilities 5 Customer Requests (CRs) 5 Supported OS/Hardware Platforms Supported CAD Access 7 9 6
Analysis Preferences Tested Technical Support Web 10 Phone and Fax 11 10
iv Patran Release Guide
MD Nastran MSC Nastran Preference
Optimization (SOL 200) Enhancements 2 Topology, Topometry, Topography 2 General Optimization - More Design Variables. 5 More Responses, Constraints, Objectives. 5 Optimization Parameters. 7 Design Variable Relations. 7 General (DLINK): 9 Implicit Nonlinear (SOL 400) Enhancements 10 Brake Squeal 10 Contact Improvements - BCONTACT = ALLBODY 10 Contact Detection - Shell Edge Contact. 10 Contact Detection - 3D Beam to Beam Contact 11 Contact Body Movement (BCMOVE) - approach step. 12 Contact Body Definition (BCHANGE/UNGLUE) 12 Contact Table. 13 Initial Contact 15 Solution Controls. 15 Thermal Analysis. 15 Analysis Chaining. 16 Explicit Nonlinear (SOL 700) Enhancements Nastran Thermal-Structural Chaining Nastran Results 24 23 18
Multi-Physics Support Marc Results Initial Contact 30 31 28
Right Mouse Button (RMB) 34 Model Display Options 35 Node, Element or Geometric Entity Options 35
CONTENTS v RMButton – Entity Check Options 36 Right Mouse Button Customization 37 New GUI Skins 39 Overview 39 Application Icon Ribbons Native 64 Bit Port 43 44 39 Automatic Feature Recognition Batch Image Rendering SimManager Integration SimXpert Integration MSC Sinda Preference 49 50 46 47 Laminate Modeler 51 Import Layup File… 51 Save As… 51 Create LM_Layup Add 51 Layup Definition Spreadsheet 52 Create LM_Layup Laminate 53 Create Results Failure Calc 54 Show LM_Ply Graphics 55 Delete LM_Layup Select 55 Import Plies File 55 Import Results ESAComp xml 56 Verify Laminate 56 Customer Requests 61 n 57 Patran Release Guide 61 .
vi Patran Release Guide .
Chapter 1: Patran 2008 r2 at a Glance Patran Release Guide 1 Patran 2008 r2 at a Glance Key Highlights 2 6 Supported OS/Hardware Platforms Supported CAD Access 7 9 Analysis Preferences Tested Technical Support 10 .
edit. The legacy Spatial InterOP translators can be installed and run in conjunction with the Connect API version if necessary. 1 SOLs 400 and 700 are only available in MD Nastran and must be submitted using Patran running in MD mode. NX 5 / NX 6 Support for NX 5 is available on most platforms and NX 6 on Windows is now available. 7. and delete them. Parasolid based translators. After installing 2008r2. Automatic Feature Recognition This revamped feature recognizes geometric features and allows you to view. have been updated to the R18 SP1 and SP3 revisions. both the new Connect API and the old legacy versions of the InterOp translators are accessible from the Patran user interface. 44 for more details.mscsoftware. When this is done. MSC makes periodic updates to CAD access and are available through download patches at: http://www. the user can download the old legacy InterOp translators from the above web site that are compatible with 2008r2. See Automatic Feature Recognition. This gives CAD access support based on the table in Supported CAD Access.2 Patran Release Guide Key Highlights 1. Instructions to do this are included with the download. MD Nastran1 and MSC Nastran Support (Patran 2008 r2) Optimization (SOL 200) The following enhancements are provided for support of optimization. Parasolid 19 Parasolid import now supports up to version 19.com/support/software_updates/#patran Note that MSC has converted to the new Connect API version of the Spatial InterOp translators. The Patran Parasolid kernel is based on Parasolid 19. .1 Key Highlights The following general enhancements are available in Patran 2008 r2: CAD Access InterOp R18 SP1/SP3 The Spatial InterOp. Catia V5 R18 Support for Catia V5 R18 is available through the Parasolid import method using the Spatial InterOp translators.
2. 10. Implicit Nonlinear Analysis (SOL 400) The following enhancements are provided for support of implicit nonlinear analysis. Explicit Nonlinear Analysis (SOL 700) The following enhancements are provided for support of explicit nonlinear analysis as detailed in Explicit Nonlinear (SOL 700) Enhancements. Thermal-Structural Interaction (SOL 101) Thermal-structural analysis chaining can be performed in a single SOL 101 run using the HEATSTAT parameter.Chapter 1: Patran 2008 r2 at a Glance 3 Key Highlights • Design Variables: PCOMPG (Global Plys) • Responses/Constraints/Objectives: • Bush Forces • Acoustics • Fluid Modes • Objective Function Modification • Design Variable Relations • Topology. See Multi-Physics Support. 23. Topometry & Topography See Optimization (SOL 200) Enhancements. Marc Support New Physics Types New physics types are added to the Coupled analysis type in an on-going effort to support Marc’s multiphysics capabilities. • Brake Squeal • Contact Improvements • Solution Controls • Thermal Analysis • Analysis Chaining See Implicit Nonlinear (SOL 400) Enhancements. See Nastran Thermal-Structural Chaining. Results Access Exterior acoustics results via the OP2 file and optimization results via the XDB file are now supported. 18. 24. See Nastran Results. 28. .
See New GUI Skins. publish. Initial Contact. 47 for details.Pre-Release) A pre-release version of Patran for Windows 64 bit machines is available for testing in this release. See MSC Sinda Preference.4 Patran Release Guide Key Highlights Results Access Output requests now include the ability to select layers of composites. General Enhancements Right Mouse Button (RMB) (Patran 2008 r2) The menus accessible via the RMB have been enhanced and the ability to customize has been added. 30. This is a pre-release capability. 34. See SimManager Integration. 49 for details. SimXpert Integration Spawn SimXpert directly from Patran and transfer finite element model data to SimXpert. See Marc Results. 50. MSC Sinda Preference A new thermal analysis preference has been added as a standard analysis preference. 43. This version is meant for “beta” testing and is not recommended for full production work. See Initial Contact. 31. Details can be found in section New GUI Skins. SimManager Integration Logon. This is described in detail in Right Mouse Button (RMB). Some details of the 64 bit port are listed in Native 64 Bit Port. 39. It is now possible to define an initial contact table in the model definition section. Please report any issues to your MSC representative so we can solidify this port into a future production release. New GUI Skins (Patran 2008 r2 . See SimXpert Integration. . Native 64 Bit Port (Patran 2008 r2 . Batch Image Rendering Graphical image files can be rendered and produced in batch mode. The production 32 bit version of Patran can still be run on 64 bit Windows machines.Pre-Release) A pre-release capability to change the Patran graphical user interface (GUI) skin is available in this release. 39 for details. Please report any issues and/or enhancement requests to your MSC representative. and retrieve Patran databases and related analysis files through this SimManager client/server access.
Chapter 1: Patran 2008 r2 at a Glance 5 Key Highlights Laminate Modeler A number of enhancements have been add to the Laminate Modeler as detailed in Laminate Modeler. 57. Utilities Please review the Utilities/ What is New menu to see additions/updates made to the utilities. 51. The most significant ones are listed in Customer Requests. . Customer Requests (CRs) A number of enhancements and defect correction have been made.
81) in the Patran Installation and Operations Guide. For more information on Operating Systems and Hardware support. HP (PA-RISC) SUN (Solaris) Intel (Windows) Intel (Linux) IBM (AIX) For a complete description of these configurations. please see IBM AIX Requirements (p. please see Hewlett-Packard HP-UX (PA-RISC) Requirements (p. 80) in the Patran Installation and Operations Guide.6 Patran Release Guide Supported OS/Hardware Platforms 1. please see Microsoft Windows Requirements (p. 78) in the Patran Installation and Operations Guide. please see Sun Solaris Requirements (p. .2 Supported OS/Hardware Platforms Vendor Description For more information on Operating Systems and Hardware support. see Required Hardware & Software Configurations (Ch. For more information on Operating Systems and Hardware support. For more information on Operating Systems and Hardware support. please see Linux Requirements (p. 85) in the Patran Installation and Operations Guide. 76) in the Patran Installation and Operations Guide. 5) in the Patran Installation and Operations Guide. For more information on Operating Systems and Hardware support.
2.0 11.4 R18 Wildfire 3. ‡ UG NX supports only 64 bit machines for HP and SUN Platforms.2.1 18.4 R18 Wildfire 3.0 19 IBM RS/6000 4.0 11.1 18.1 *A CATIA CATXPRES (. Parasolid transmit files generated on other OS platforms can be imported on LINUX.cat) file can be imported. only the CATIA to Parasolid translator is available and the CAT Direct Translator which runs CATIA in batch mode is not available. Existing Patran translator is still available for pre- Pro/ENGINEER Wildfire release.4 R18 Wildfire 3.4 CATIA V4* CATIA V5 Pro/ENGINEER† Unigraphics‡ I-DEAS Parasolid ACIS 18.ptc.com/go/timeout/ • PTC Technical Resource http://www.0 NX5.1 18. See more notes below.0 NX5.2.0 19 SUN 4. • Import to Parasolid which runs from within interactive Patran: does not does not require a Pro/ENGINEER license to run. The following notes are applicable to the Import to Native Patran Geometry method: The Pro/ENGINEER Wildfire release introduced the following platform changes: • IBM AIX platform unsupported. Patran has two methods for importing Pro/ENGINEER models: • Import to Native Patran Geometry which runs from within interactive Patran: requires a Pro/ENGINEER license to run on the machine where Patran is installed.1 18. the list of platforms supporting this import method is the Pro/ENGINEER supported machines.htm .ptc. † The p3_ProE and p3_ProENGINEER executables are built using Pro/ENGINEER version 2000i and therefore will not work with earlier versions of Pro/ENGINEER.0 NX6.0 19 19 XMT** Linux 4.3 Supported CAD Access HP (PA-RISC) 4.0 12. 2004: • PTC Important System Notice .geo geometry transfer files generated from other OS installs of Pro/ENGINEER Access.com/go/timeout/technical_resource.Chapter 1: Patran 2008 r2 at a Glance 7 Supported CAD Access 1. p3_ProE and p3_ProENGINEER Access allows reading of . The following steps are necessary for customers to use the Patran Pro/ENGINEER translator with Pro/ENGINEER after January 10. therefore.0 NX5.2. On Windows and Linux.Timeout http://www.2.0 12.0 19 Windows 2000 / XP / Vista 4.4 R18 Wildfire 3. **Only Parasolid (transmit file) import is supported in this release.
p3_ProE and p3_ProENGINEER Access allows reading of .0 release introduced the following platform changes: • HP-UX and SUNS supports 64-bit only. . the HP-UX and/or SUNS platform must be a 64-bit capable machine to run the Patran translator Pro/ENGINEER Wildfire 3. If running Pro/ENGINEER Wildfire 2.exe and follow PTC instructions. • Download wildfire datecode 2003490 and follow PTC instructions.0 release.0 and Pro/ENGINEER Wildfire 2.0.geo geometry transfer files generated from other OS installs of Pro/ENGINEER Access.8 Patran Release Guide Supported CAD Access For Pro/ENGINEER 2001: • Download NMSD.0 • Linux is supported for Import to Parasolid • The p3_ProE and p3_ProENGINEER executables are built using Pro/ENGINEER version 2000i and therefore will not work with earlier versions of Pro/ENGINEER. The Pro/ENGINEER Wildfire 2.exe and follow PTC instructions. Patran translator compatible with pre-Pro/ENGINEER Wildfire 2. For Pro/ENGINEER Wildfire: • Download NMSD.
0 (results import is frozen at 8.4. For instance SUN support is frozen at 6.0 *ABAQUS discontinued platforms remain at the level of support at the time they were discontinued by HKS. †Results access is enhanced to 11. .Chapter 1: Patran 2008 r2 at a Glance 9 Analysis Preferences Tested 1.4 Analysis Preferences Tested Solver MD Nastran MSC Nastran Marc Dytran Flightloads Thermal Fatigue MSC Sinda LS-DYNA3D PAMCRASH SAMCEF ABAQUS* Platforms All All All All All All All All All All All Solver Version MD Nastran R3 MSC Nastran 2008 r2 2008 r1 2008 r1 2008 r1 2008 r1 2008 r1 2008 r1 970 1995 / 1997 11 / 12 6.1).8 ANSYS† All 11.
or e-mail: Web Go to the MSC. Technical Support.10 Patran Release Guide Technical Support 1. If you have concerns about an analysis. by telephone. Here.. fatal messages) • Verification of code error. available training courses.5 Technical Support For help with installing or using an MSC.Software Training. and documentation updates at the MSC.com. you can find a wide variety of support resources including application examples.mscsoftware. Our technical support provides the following services: • Resolution of installation problems • Advice on specific analysis capabilities • Advice on modeling techniques • Resolution of specific analysis problems (e.Software product. technical application notes. .g. You can reach technical support services on the web.Software website at www. and click on Support. we suggest that you contact us at an early stage. and Documentation web page. contact your local technical support services.
Italy Telephone: (81) (3) 3505 02 66 Fax: Paris. The Netherlands Telephone: (7) (095) 236 6177 Fax: (7) (095) 236 9762 Telephone: (31) (18) 2543700 Fax: (31) (18) 2543707 Madrid. Germany Telephone: (49) (89) 43 19 87 0 Fax: Rome. Camberley Surrey. Spain Telephone: (34) (91) 5560919 Fax: (34) (91) 5567280 . France (49) (89) 43 61 71 6 (81) (3) 3505 09 14 Telephone: (390) (6) 5 91 64 50 Fax: (390) (6) 5 91 25 05 Telephone: (33) (1) 69 36 69 36 Fax: (33) (1) 69 36 45 17 Moscow. United Kingdom Telephone: (800) 732-7284 Fax: (714) 784-4343 Telephone: (44) (1276) 67 10 00 Fax: Tokyo. Russia Gouda.Chapter 1: Patran 2008 r2 at a Glance 11 Technical Support Phone and Fax United States Frimley. Japan (44) (1276) 69 11 11 Munich.
firstname.lastname@example.org mscsuperforge.com msctraining.support@mscsoftware.Marc Support MSC.Fatigue Support MSC. You should receive an acknowledgement that your message was received.12 Patran Release Guide Technical Support Email Send a detailed description of the problem to the email address below that corresponds to the product you are using.Dytran Support MSC.com email@example.com@mscsoftware.com firstname.lastname@example.org mscnastran.support@mscsoftware. Patran Support MD Nastran Support MSC.support@mscsoftware. followed by an email from one of our Technical Support Engineers.support@mscsoftware.SuperForge Support MSC Institute Course Information mscpatran.com .Mvision Support MSC.com mscmvision.com mscmarc.
Chapter 2: MD Nastran MSC Nastran Preference Patran Release Guide 2 MD Nastran MSC Nastran Preference Optimization (SOL 200) Enhancements 2 10 18 Implicit Nonlinear (SOL 400) Enhancements Explicit Nonlinear (SOL 700) Enhancements Nastran Thermal-Structural Chaining Nastran Results 24 23 .
Combined topology and sizing optimization is still available under the Optimize action. or volume Enhancements over the previous release include: • Addition of topometry and topography design variables (TOMVAR. All the functionality of the Customized Solution form is now available under the Toptomize action. this is not necessary.1 Optimization (SOL 200) Enhancements Topology. objective and constraints are defined directly within the Toptomize form and subordinate forms. All the design variables. With the Toptomize action. a user can quickly set up and run a topology. objective.2 Patran Release Guide Optimization (SOL 200) Enhancements 2. To use the standard optimization (Optimize action) a user must first create the design variables. Using this Action. Define the design domain by selecting existing property sets and defining the parameters associated with each. • Run the Analysis. or topography optimization is allowed. topometry. weight. weight. the objective of the optimization (minimize compliance or maximize frequency) and the target constraint (mass fraction. . • B. no combinations or combined sizing optimization is possible • Supported objectives are limited to minimizing compliance or maximizing frequency or a combination of both (represented as an equation) • Constraint targets are limited to mass fraction. Set any optimization controls such as the maximum number of design cycles and other necessary items to properly define the problem using the Optimization Control form. Topography A new Action has been added to the Analysis form to encompass topology. and constraint functions and combine them into a valid Design Study using the Tools / Design Study / Preprocessing utility. these being: • Only separate topology. topometry. Naturally this subjects it to certain limitations. This replaces the “quick” topology optimization that used to be available under the Optimize action by using the Customized Solution form. topometry. and topography optimization jobs. and BEADVAR) • Combined objective as mentioned above • Weight and volume target constraints as mentioned above • Ability to designate portions of design domain with different manufacturing and other constraints A typical setup scenario is (see picture below): • A. topometry. • C. The new Action is called Toptomize. or volume) using the Objective & Constraints form. or topography optimization job. such as manufacturing constraints under the Design Domain form. Topometry. or topography). Define the optimization type (topology. That Design Study must then be selected for the optimization analysis.
. C.Chapter 2: MD Nastran MSC Nastran Preference 3 Optimization (SOL 200) Enhancements A. B.
4 Patran Release Guide Optimization (SOL 200) Enhancements Topology job showing original and optimized (non-smoothed) geometry determined using multiple design domain regions to preserve the connection and bolt holes. SOL 200 produces an element thickness distribution file *. The objective is to minimize structural compliance and keep weight unchanged. Topometry optimization job: A real complex example car body is used here to demonstrate topometry optimization for graphical postprocessing. please see Toptomize (p. This example also shows that SOL 200 is able to deal with very large optimization problems. 462) in the Patran Interface to MD Nastran Preference Guide. . and a combined objective of minimizing compliance / maximizing frequency and a mass target constraint Topography optimization job showing the shape change from a flat plate to maximize the first frequency. For more details on the usage of this new functionality.des that can be used by Patran to view topometry optimization results.
Chapter 2: MD Nastran MSC Nastran Preference 5 Optimization (SOL 200) Enhancements General Optimization . reference temperature. normal modes. frequency and transient response. The following are available to define as responses. Design variable creation has also been extended to PCOMPG property entries for values such as offset. . Constraints. More Responses. and objectives (DRESP1 / DRESP2 entries): • CBUSH Forces – available as constraint or objective for linear statics.previously only PCOMP was supported). constraints. non-structural mass. • Acoustic responses available as constraints or objectives for frequency response analysis. Objectives. etc.More Design Variables. Support for specifying composite shell thickness and orientation based on global ply layers as design variables is now supported (PCOMPG .
6 Patran Release Guide Optimization (SOL 200) Enhancements • Fluid modes for normal modes analysis. .
and responses that the user wishes to employ in a particular . objective. Objective Function Modification: This toggle is available on the Advanced Optimization Parameters form under the Analysis (Action=Optimize) application when submitting the job. constraints.2 lbs.Chapter 2: MD Nastran MSC Nastran Preference 7 Optimization (SOL 200) Enhancements Optimization Parameters. For example if only one part of the model is being optimized and it changes by 0. A Design Study is a selection or grouping of the applicable design variables. Turning this toggle ON indicates to MD Nastran SOL 200 to modify the objective function such that it reports back in the summary (F06 file) the relative change instead of the absolute change.0 to 100004. This is written to the DOPTPRM (OBJMOD) entry.8 lbs. Design Variable Relations. Once a variable relation has been defined it can be associated to a Design Study. This new Variable Relations feature allows you to define an expression which contains a number of design variables linking them as dependent and independent. then that is what is reported rather than saying the over all structural weight went from 100005.
The variable relations are also selected as part of a Design Study in order to activate them for any particular optimization.8 Patran Release Guide Optimization (SOL 200) Enhancements optimization. There are several ways to define an expression or variable relation: .
general equation is used to define the relationship between the selected design variables: DDVID = C0 + CMULT *(C1*IDV1 + C2*IDV2 + … + Cn*IDVn) DDVID = Dependent design variable C0 = Constant offset value CMULT = Constant multiplier Ci = Constant multiplier for each independent design variables IDVi = Independent design variable . The following simple.Chapter 2: MD Nastran MSC Nastran Preference 9 Optimization (SOL 200) Enhancements General (DLINK): A number of design variables are linked by the DLINK card in MD Nastran. The dependent design variable is selected on the main form and the subordinate form is for selecting the independent design variables and associating a coefficient to each.
. they can simply make any minor change and Patran will write the contact table. Moment carrying glue option is controlled globally via the Contact Detection form. Contact Improvements . AND 1. The analysis is performed with a static step followed by with a complex eigenvalue step. Shell edge contact (with moment carrying glue) is supported on the Contact Detection form shown below. There are contact bodies in the selected load case.Shell Edge Contact.2 Implicit Nonlinear (SOL 400) Enhancements Brake Squeal Support for Brake Squeal Analysis (BSQUEAL).. See the next section on beam to beam contact and the section on contact table improvements.e.10 Patran Release Guide Implicit Nonlinear (SOL 400) Enhancements 2. Contact Detection . and via the contact table per body pair. Specific brake squeal parameters are set on the Static Subcase Parameters form. all entries are default values) If the user wants the contact table written out. by contact body. The user does not make any changes to the contact table (i.BCONTACT = ALLBODY This is written to case control if: 1.
Chapter 2: MD Nastran MSC Nastran Preference 11 Implicit Nonlinear (SOL 400) Enhancements Contact Detection . . Beam contact radii are defined on in the Element Properties application when defining beam properties. A standard default value defined by MD Nastran is used if not specified.3D Beam to Beam Contact Beam to beam contact can be turned on under the Contact Detection form.
• Glue Deactivation – Certain areas of a contact body (that has been designated as glued) can be switched to standard touching contact so not all nodes of a contact body need to be glued. This is controlled in Nastran using the BCMOVE entry. Contact Body Definition (BCHANGE/UNGLUE) The following improvements are available when defining deformable contact bodies: • Contact Area . nodes which come into contact can be specified using the Contact Area definition. then bodies continue to move until all are in contact. If this toggle is off.12 Patran Release Guide Implicit Nonlinear (SOL 400) Enhancements Contact Body Movement (BCMOVE) .When defining a deformable contact body. In this subcase. a body approach subcase can be specified.Edges and faces of deformable contact bodies that are to be excluded and ignored in the contact detection algorithms can be defined using the Exclusion Region. • Exclusion Region . The Synchronized toggle indicates to the analysis code to move all bodies in sync with one another until the first contact is made at which point the movement is stopped for the load step.approach step. or load step. Under the Analysis form when setting up subcases or load steps. . active contact bodies are moved into place until one or all are just touching for the beginning of the next subcase.
defines the threshold at which a glued node separates • Edge Contact . The following improvement have been made to the contact table such that the following can be specified per body pair: • Braking Glue (BKGL) Parameters . Contact Table.Chapter 2: MD Nastran MSC Nastran Preference 13 Implicit Nonlinear (SOL 400) Enhancements • Note that Edge contact can be specified at the contact body level also.controllable at the body pair level as well as per body and globally .
14 Patran Release Guide Implicit Nonlinear (SOL 400) Enhancements • Moment Carrying Glue .can be turned on/off per body pair for those bodies that are defined as glued. . This works in conjunction with the toggle to retain gaps.
For example. More options to control the load incrementation have been opened up in the graphical interface.Chapter 2: MD Nastran MSC Nastran Preference 15 Implicit Nonlinear (SOL 400) Enhancements Initial Contact The initial contact table can now be defined for both the Nastran and Marc Preferences under the Contact Parameters form. Solution Controls. SOL 400 thermal analysis is now supported under the MD Nastran Thermal preference for unchained heat transfer analysis. Most items on the MD Nastran entries below are now accessible. the ability to specify automatic switching between displacement and residual force convergence criteria. • Load Increment Parameters form (NLAUTO) • Nonlinear Static and Transient Analysis Controls (NLPARM/TSTEPNL) • Additional Load Increment Parameters (NLADAPT) Thermal Analysis. . Supported solution types are Steady State and Transient Heat Transfer analysis.
select them in the order in which they should be run and the analyses are chained together.16 Patran Release Guide Implicit Nonlinear (SOL 400) Enhancements This includes specifying heat transfer contact bodies and the ability to control thermal properties per body pair using the contact table. Analysis Chaining. This is the ability to create multiple subcases (load steps). meaning that the results from the last increment of the .
The following analysis types are available to be chained: • Linear and Nonlinear Static Analysis • Normal Modes Analysis • Buckling Analysis • Transient Dynamic Analysis • Direct Complex Eigenvalue • Modal Complex Eigenvalue • Body Approach . An example is a modal or a buckling stiffening problem where a static linear or nonlinear analysis is performed first and then the modal or buckling step.Chapter 2: MD Nastran MSC Nastran Preference 17 Implicit Nonlinear (SOL 400) Enhancements previous load step become the starting point for the next load step.
3 Explicit Nonlinear (SOL 700) Enhancements New support is best illustrated by case study problems in which those shown below and like problems can now be prepared as run-ready input to MD Nastran: • Airbags and multi-compartmental airbags • Blasts and Sloshing .18 Patran Release Guide Explicit Nonlinear (SOL 700) Enhancements 2.
Chapter 2: MD Nastran MSC Nastran Preference 19 Explicit Nonlinear (SOL 700) Enhancements • Bird strike / Prestress & Impact on Rotating Fan Blade • SPH (smooth particle hydrodynamics) and Drop test of computer package .
BCSEG entries are created from the defined application region of the airbag • BCGRID – Defines contact grids. all elements inside the defined box are part of the contact body • SPCD2 – Imposed nodal motion . available under Box Definition.20 Patran Release Guide Explicit Nonlinear (SOL 700) Enhancements • Rod penetration • Train barrier/pickup truck This translates into support of the following MD Nastran SOL 700 entries which can be defined in the following application areas of Patran: Loads/BCs • AIRBAG/BCSEG – Defines an airbag. Loads/BC object is an Airbag. available as a new Contact boundary condition option • BCBOX . available as a new Contact boundary condition option • BCPROP – Defines contact based on element properties.Another way of defining a contact body.
defined in the Loads/BC as a Coupling LBC • TICD – Transient analysis initial conditions. defined under the Element Properties application • CSPH. which is used as initial conditions. defined under Materials application • MATD020 – Rigid material • MATD014 – Soil and foam with failure Element Properties • PEULER1 . PSPH – Defines an SPH particle. defined when creating an airbag • TICEUL1. CFILLET. CBUTT – Spot weld. defined as a boundary condition under the Loads/BCs application • COUPLE. defined under the Materials application as a Rigid constitutive model for an Isotropic(SOL700) material • EOSGRUN – Gruneisen equation of state. defined under Materials application as Erosion model • MATRIG – Rigid body properties. • MATDUEL – Eulerian material properties.Chapter 2: MD Nastran MSC Nastran Preference 21 Explicit Nonlinear (SOL 700) Enhancements • GRIA – Grid point in a bag reference geometry. done as a 0D element property under the Element Properties application Analysis • PRESTRS – To perform a pre-stress run and determine the pre-stress state. SPHERE – Eulerian initial conditions • MESH – Defines a mesh. set under the Analysis application under Solution Parameters FEM (Finite Elements) • CSPOT. defined in the Materials application as a Eulerian-Solid • MATDERO – Erosion material. and butt weld. activated in the Analysis application under Solution Parameters • DYDEFAUL – SOL 700 defaults settings. this is done as a boundary condition under the Loads/BCs application • FLOWDEF – Eulerian flow boundary.Hydrostatic Preset of Density in Euler Elements. defined under the Materials application • EOSPOL – Polynomial equation of state.SOL 700 eulerian solid properties. defined in the Analysis application under Solution Parameters • SPHDEF – SPH analysis controls. TICREG. defined as a boundary condition in Loads/BCs application • HYDSTAT . defined under the Element Properties application • PSHELL1 – SOL 700 shell element properties. fillet weld. COUOPT – General Euler-Lagrange coupling surface. defined as MPCs in the FEM application . defined under Materials application. TICVAL. defined in the Loads/BCs application as Hydrostatic Preset Materials • EOSGAM – Eulerian Gas.
SPH processor requires some conditions in setting initial particle masses and coordinates. the particles of the same material which has same initial density need to have same volume.e. i.22 Patran Release Guide Explicit Nonlinear (SOL 700) Enhancements • Meshing . To preserve this they need to be distributed on a uniform mesh. When meshing a cylinder it is better to use regular mesh to guarantee stability and convergence of the method.. As a consequence. The particle mesh needs to be regular. all particles of given neighborhood need to have same mass. To get a regular mesh.Because of lack of numerical grid. this is done under the FEM application: Create/Mesh/Regular .
The model shown is a computer chip with temperature fringe due to heating and convection and resulting (exaggerated) structural deformation. . 5. YES is written to the input deck. The temperature results from the first subcase are used along with any other structural LBCs called out in the second subcase. Set up two Subcases. The procedure is to: 1. Select STRUCTURAL HEAT ANALYSIS Select the two Subcases This only works for SOL 101 presently. Structural 6. Select the two Subcases in the order: Thermal. With the Preference set to Structural.4 Nastran Thermal-Structural Chaining It is now possible to set up a chained thermal-structural analysis in one run using SOL 101. create and set up your structural LBCs and load case 2. create and set up your thermal LBCs and load case 3. one referencing the structural load case and the other referencing the thermal load case.Chapter 2: MD Nastran MSC Nastran Preference 23 Nastran Thermal-Structural Chaining 2. The first subcase is the heat transfer run to determine the temperature loading. Submit the job The Nastran run is submitted as a SOL 101 with two Subcases. HEATSTAT. The PARAM. which is a SOL 101 run. Set the Solution Type to STRUCTURAL HEAT ANALYSIS 4. Change the Preference to Thermal.
Acoustic power • OAIG1. Results include Intensity.Field point velocity .24 Patran Release Guide Nastran Results 2.Acoustic Intensity • OUGFP1. Shown are results on a field point mesh. Acoustic Power. and Results on Field Point Meshes.Field point Mesh • OVGFP1 .5 Nastran Results OUTPUT2 File Exterior acoustic results via the OP2 file can now be imported. The following datablocks are now supported via the OP2 file for exterior acoustics analysis: • OARPWR1.
Chapter 2: MD Nastran MSC Nastran Preference 25 Nastran Results XDB File Topology element density results can now be imported via the XDB file under Tools / Design Study -> Post-Process… Shown is the element density as imported via the XDB file for a topology optimization job. .
26 Patran Release Guide Nastran Results .
Chapter 3: Marc Preference Patran Release Guide 3 Marc Preference Multi-Physics Support Marc Results Initial Contact 30 31 28 .
and Thermal-Mechanical coupling: • Electrostatic • Joule Heating (Electrodynamic-Thermal coupling) This release now supports: • Electrostatic-Structural coupling • Joule-Structural coupling • Magnetostatics • Electromagnetics • Induction Heating (Electromagnetic-Thermal coupling) • Piezoelectric The physics selection is done under the Analysis application from the Step Select form as shown below.28 Patran Release Guide Multi-Physics Support 3. Thermal. the following physics types were supported in addition to Structural.1 Multi-Physics Support In the previous release. .
Fields. and Piezoelectric constitutive model for applicable material types (Isotropic. The following enhancements have been made to the Materials. Magnetostatic. and wire current) • Charge (boundary and body) • Voltage • Potential (electrostatic. body. and Anisotropic) • Fields: Magnetic material fields to define B-H relations • Element Properties: Support for the following Marc elements: • 109 – Hex/8 3D Magnetostatics • 110 – Hex/12 3D Semi-infinite Magnetostatics • 111 – Quad/4 Planar Electromagnetic • 112 – Quad/4 Axisymmetric Electromagnetic • 113 – Hex/8 3D Electromagnetic • 160 – Quad/4 Plane Stress Piezoelectric • 161 – Quad/4 Plane Strain Piezoelectric • 162 – Quad/4 Axisymmetric Piezoelectric • 163 – Hex/8 3D Piezoelectric • 164 – Tet/4 3D Piezoelectric • 181 – Tet/4 3D Magnetostatic • 182 – Tet/10 3D Magnetostatic • 183 – Bar/2 3D Magnetostatic • Loads and BCs: The following are supported for the above mentioned physics types • Current (boundary. magnetostatic) • Magnetization (permanent magnet) . Electrodynamic.Chapter 3: Marc Preference 29 Multi-Physics Support Shown is a micro-thermal actuator / an electrical-thermal-mechanical coupling (Joule-structural). vector. and Loads and BCs applications in support of Multiphysics: • Materials: Electrostatic. Orthotropic. Element Properties.
30 Patran Release Guide Marc Results 3. In Output Requests form go to Element Results 4. top/bottom/middle. In Element Results go to Layers form. 1. go to Output Requests 3. . Options are all layers.2 Marc Results A significant new enhancement regarding requests for Marc results output is the ability to specify the layers of composite results. In Step Create form. The Results Output Format must be set to 2007 (POST code revision 13) on the Translation Parameters form to access this functionality. The default is not to specify any layers. layers only or a list of layers. Set Results Output Format to 2007 (POST Code rev13) in Translation Parameters form 2.
3 Initial Contact The initial contact table can now be defined for both the Nastran and Marc Preferences under the Contact Parameters form. .Chapter 3: Marc Preference 31 Initial Contact 3.
32 Patran Release Guide Initial Contact .
Chapter 4: General Enhancements Patran Release Guide 4 General Enhancements Right Mouse Button (RMB) New GUI Skins Native 64 Bit Port 39 43 34 Automatic Feature Recognition Batch Image Rendering SimManager Integration SimXpert Integration MSC Sinda Preference Laminate Modeler Customer Requests 51 57 49 50 46 47 44 .
Patran Release Guide
Right Mouse Button (RMB)
Right Mouse Button (RMB)
Additional context-dependent functionality has been added to the right mouse button to reduce the “mouse travel” required to manipulate the display or obtain simple model information.
• RMB Display Control – right click on an open area of the viewport to perform operations such
as: clean up the display or refresh the graphics, “tile” the viewport and menus in the Patran window, or do a “fit view” to see the entire model.
• RMB Viewport Control – right click on an open area of the viewport to change the model
orientation, render style, reverse the background, or show the cycle picking labels.
• RMB Model Information – right click on an entity to find information or attributes of that entity.
Picking filter controls entity selection.
Right click on a node or element to obtain information such as location, attributes, verification options or associations. Right click on a geometry entity to obtain information such as surface area, curve length or arc dimension, and FEM association such as mesh seeds or associated nodes / elements. The right mouse button menu is completely customizable so you can add your favorite viewport or display function to the menu. The customization procedure is described below.
Chapter 4: General Enhancements 35
Right Mouse Button (RMB)
Model Display Options
Many of the most commonly used display control commands are available through the RMB menu. This shows the Viewport Display and Model Orientation menu options.
Node, Element or Geometric Entity Options You can use the right mouse button in conjunction with the select filter to get information on FEM entities without navigating the Action-Object-Method (AOM) menus. Clicking the right mouse button when over an entity will bring up the RMB menu where you can choose from a long list of options.
Patran Release Guide
Right Mouse Button (RMB)
Some of the options available from the right mouse button apply to individual entities, such as the transform, modify, show or sweep options.
RMButton – Entity Check Options Many of the options available from the right mouse button apply to all posted entities in the model, such as Verify – Element - Boundaries, Verify – Hex – Aspect Ratio, etc.
Chapter 4: General Enhancements 37
Right Mouse Button (RMB)
Right Mouse Button Customization
Through the customization capability you can add a menu-item to a particular RMB menu. To do this you must specify:
• Name of the menu where the item needs to be added • Callback function for the menu-item (PCL) • Condition function for the menu-item (PCL) – This decides if the menu-item is activated or
• Label for the menu-item (optional)
Consider the case of adding a menu-item to set the color of all selected geometric entities. Let us name the menu-item as AsmSetColor. Let us also specify the callback function as asm_set_color_cb, the condition function as asm_set_color_cond, and the label as “Set Color.” Once selected the icon will take the user to the same application menu form he or she is used to seeing, thus there is no learning curve required.
• There are 2 types of xml files. One containing the information regarding the menu layout and the
callback of menu-items. The other contains the “resource” related information for the menus and menu-items.
• The file containing the definition (p3_user_menu.xml) starts with the tag <RMBMAP>. The one
containing the resource information (p3_user_menu_res.xml) starts with the tag <RMBRESOURCEMAP>. These 2 files are kept in the Patran installation directory ($P3_HOME) by default, but can be anywhere in the PCL path and are read after all other default menu-definition files, which also reside in the $P3_HOME/rmb_menu directory. The menu-items defined in these files appear at the bottom of the menu.
• Add the following definition in p3_user_menu.xml within the <RMBMAP> tags:
<MENU> <NAME>NoEntityMenu</NAME> <ADDMENUITEM>AsmSetColor</ADDMENUITEM> </MENU> <MENUITEM> <NAME>AsmSetColor</NAME> <CALLBACK>asm_set_color_cb</CALLBACK> <CONDITION>asm_set_color_cond</CONDITION> </MENUITEM> • Add the following in p3_user_menu_res.xml within the <RMBRESOURCEMAP> tags: <MENUITEM> <NAME>AsmSetColor</NAME> <LABEL>Set Color</LABEL> </MENUITEM> • Implement the callback function in any .pcl file (note the function input arguments): FUNCTION asm_set_color_cb( sel_entities, entity_type ) STRING sel_entities STRING entity_type
This means that there are no limits on what the call back functions do as long as the argument list is matched.pcl. you will find that the “Set Color” option will only appear at the bottom of the RMB menu after you have selected multiple types of geometry. Users can also modify these files to change the default behavior of the RMB. Thus if you put the functions in the text file test_rmb. Specifically they must use the format and arguments identical to those of the example: two string variables as arguments. Load the PCL file containing the callback and condition function definition using !!input command in the Patran command window. you would type !!input test_rmb. or even change the functions called by the call backs. The XML files that control the default RMB menu are in the Patran installation directory under the rmb_menu subdirectory. Users can examine these files to see how the submenu structures are set up if they wish to create their own. entity_type ) STRING sel_entities STRING entity_type RETURN TRUE END FUNCTION /* Activate this menu item */ • Run Patran. click on the RMB in the viewport to see that “Set Color” was added at the bottom: A slightly more complex example can be performed by replacing the name NoEntityMenu in the <NAME>NoEntityMenu</NAME> line of the p3_user_menu.xml file with ASM_MENU. New and more complex call back functions can be created by the user. however. these call back functions must all have argument lists that follow the same format.38 Patran Release Guide Right Mouse Button (RMB) dump sel_entities dump entity_type END FUNCTION • Implement the condition function in any .pcl file (note the function input arguments): FUNCTION asm_set_color_cond( sel_entities. . If you do this and carry through with the rest of the example. The above examples show how users can add functionality to the RMB.pcl Once the functions are input (compiled).
To close an application.Chapter 4: General Enhancements 39 New GUI Skins 4. please revert back to the legacy Patran skin and report problems to your MSC representative so they can be corrected. Once selected the icon takes the user to the same application menu form they are accustomed to seeing. click on the tab. This capability is only available on Windows. 1This is a pre-release capability. including the legacy Patran skin (no -skin option used) and so it is acceptable to switch skins on the same database between Patran sessions.2 New GUI Skins1 Overview A pre-release capability has been added to Patran’s graphical user interface (GUI) for the Windows platform. Future plans will continue to improve this enhanced interface. Application Icon Ribbons The new GUI skins provide for application icon ribbons allowing the user to avoid the normal permutation of pull-down menus by providing easy-access ribbon toolbars populated with icon buttons. See picture below. . These options are available using the -skin command line argument: %patran -skin <skin> where the available skins are: office2007 (default) xproyale xpluna le5 vista xptunes The database content is independent of which GUI skin option is used. thus there is no learning curve required. Used in conjunction with the new right mouse button (RMB) capabilities. these new GUI skins provide the user with an exceptional experience. The tabs in the ribbon are equivalent to the legacy Patran GUI skin’s applications. select another tab. The Home tab will close any application currently open and show no tab application. Additional options are available to streamline user interaction. To open an application. If you encounter problems.
40 Patran Release Guide New GUI Skins Application Menu Ribbon Groups Menus (tabs) .
Chapter 4: General Enhancements 41 New GUI Skins Application Menu Ribbons Provide Easy Access to Functions Without Searching the Pull-Down Menus Click on the Application Ribbon Icon to Bring up the Application Form Icons Pull Up Familiar Action – Object – Method / Type Menus .
42 Patran Release Guide New GUI Skins Some Ribbons Have Application Menu Ribbon Group Sub-Menus With Pull-Down Options .
The following functionality is available in the Windows 64 bit port. This port is made available as pre-release to facilitate testing and gather feed back to MSC. • Patran (core application) • MSC Nastran Preference • MD Nastarn Preference • MSC Marc Preference • ABAQUS Preference • ANSYS Preference • Laminate Modeler • Patran Thermal (P/Thermal) • UG NX Access • CAD Interfaces (Spatial InterOP access only) • CATIA V4 / V5 • ACIS • STEP AP203/209 • IGES • I-DEAS Future plans are to support all Patran supported platforms with native 64 bit ports. Databases from other platforms should first be converted up to the 2008r2 level on the original platform and then ported to the Windows 32 bit version of Patran and finally ported to 64 bit. On 32 bit machines. If you encounter problems. the memory limitation is 2 gigabytes. The 32 bit production version is still available for both 64 and 32 bit Windows machines as well as all other supported platforms. A 64 bit database can also be taken back to 32 bit via the porting process. The native 64 bit version of Patran can be installed from the installation disk.Chapter 4: General Enhancements 43 Native 64 Bit Port 4. MSC advises against using this port for production work until it is officially released. please report problems to your MSC representative so they can be corrected. . Anything not listed here is not yet available. Advantages of a native 64 bit Patran mainly include access to all available memory. The only limitation on 64 bit is the available memory of the machine.3 Native 64 Bit Port1 A native port to Windows 64 bit machines is available for testing in a pre-release status. 1This is a pre-release capability on Windows only. An existing database created from a 32 bit version of Patran on Windows will go through a porting process to enable it to be opened from the 64 bit version of Patran. It is possible to work with existing databases. This allows for the user to work with larger models in many aspects of the finite element modeling process such as meshing and other modeling aspects.
chamfers. say) 1. set the controls. or delete them. 1. Make changes as required. Select feature (Hole 9. Edited hole/feature. Expand Feature Tree 1. It works from parasolid geometry. then right-mouse-click on the features you want to recognize (holes. Select “Holes” 1.4 Automatic Feature Recognition Automatic feature recognition (AFR) has been removed from the Tools/Pre-Release menu and is now a supported feature under Tools pull down menu. Select the entity type and entities of interest.Automatic (treewidget expands with recognized features) 1.44 Patran Release Guide Automatic Feature Recognition 4. Select Solid 1. edit. Right mouse click on the features to show. . Right-mouse-click: Edit 1. This populates the tree widget with the recognized features. Right-mouse-click: Recognize . blends) in the tree widget.
For automatic recognition these options have been set to default values of Hole:Single. “Recognize – Interactive:” works with Geometric Entity as “Face” or “Edge” only. The propagation controls get passed to the feature recognition API to control the type of recognition.Chapter 4: General Enhancements 45 Automatic Feature Recognition The Parasolid Kernel will fail to edit or delete a feature if there is a topological dependency on other geometry. Recognizing features in the whole solid may not always be useful as there may actually only be the need of recognizing features in one particular region of the solid. Blend:Chain. number_of_features) “Recognize – Automatic:” works with Geometric Entity as “Solid” only. Multiple features can be deleted as long as all dependent features have also been selected for deletion in the same operation. propagation. if you select the “Chain” option for Blends and do interactive recognition then it will do the recognition and then perform chaining so finally you will get “Blend Chains”. It will recognize the features in the whole solid. entity_type. . Chamfer:Chain. These options are valid for interactive recognition only and respective values get passed through the second argument in the API. It is available to provide user a convenience only. To recognize each blend individually you can select the “Single” option. If you select all the faces of solid. Each “Blend Chain” may be a combination of several individual Blends. status = ifr_recognize_blends_list(entity_list. @ topology. this is equivalent to automatic recognition with additional propagation controls besides the default values. In this case simply select the faces/edges where the need to recognize the features exists and use “Recognize – Interactive. Change the Geometric Entity option to “Face” or “Edge” and select the faces or edges in the vicinity where the features are to be recognized.” “Recognize – Interactive” does not work with “Solid” geometric entities. In other words. “Edge” Geometric Entity is available for holes only. For automatic recognition these propagation control options are not used. “Recognize – Automatic” does not need any input other that “Solid ID” in which the features need to be recognized. All other inputs are defaulted.
g.46 Patran Release Guide Batch Image Rendering 4. e.pcl file with graphics_batch_dpi. BMP. 1Customer Request (CR) 40421 .5 Batch Image Rendering1 The combined usage of the batch and graphics command line arguments for invoking Patran used to be mutually exclusive. But you can set this in the settings. PNG and TIFF graphics file formats.ses Batch mode does not know what the dpi resolution is and uses a default of 100. Now you can generate graphical images in batch mode by using both together to invoke Patran via a session file (-sfp session file name) as shown here: patran -b -graphics -sfp test.5 ) This works for JPEG. 92. MPEG.. pref_env_set_real( "graphics_batch_dpi".
the user may publish.Chapter 4: General Enhancements 47 SimManager Integration 4. now directly accessible from the File pull down menu. Once the server connection properties and settings are established users can easily communicate with SimManager. Can retrieve and then open databases directly in Patran. . and browse as well view connection properties and access the Web Client.6 SimManager Integration Publish and retrieve Patran databases and other related analysis files directly from within Patran with the SimManager client. retrieve. Once logged on.
SM_RICH_CLIENT_CONFIG_FILE <location of SmRichClt. For more information on this. 48) in the Patran Installation and Operations Guide. . please see Patran Environment Variables (p. For more information on settings these environment variables.48 Patran Release Guide SimManager Integration The following variables need to be set or are asked to be set during installation in order to communicate with the SimManager server. the user is directed to the SimManager documentation.properties file> SM_RICH_CLIENT_IC_HOST <host_name> SM_RICH_CLIENT_IC_PORT <port number> SM_RICH_CLIENT_IC_PROTOCOL http SM_RICH_CLIENT_IC_WEBCONTEXT SimManager_R3 SM_RICH_CLIENT_ROOT <path> Client access to a SimManager server via Patran is only supported on Windows machines.
For this capability to be available. the user must set the environment variable MSC_SX_HOME to the top level directory of a valid. this will automatically be configured for the user. Launching from the File menu only launches SimXpert with no data transfer.7 SimXpert Integration SimXpert can be launched from Patran under the File pull down menu or from within the MD Nastran Preference. local installation of SimXpert. If an installation of SimXpert is detected at installation time. .Chapter 4: General Enhancements 49 SimXpert Integration 4. Launching from the Analysis application will transfer the finite element model to SimXpert.
However. Besides setting up a model for thermal analysis. various utilities are also available from an additional pull down menu to read in material data from Excel spreadsheets and other capabilities. As such a new MSC Sinda preference is available to give access to this state-of-the-art thermal analysis module. This Preference is only available on Windows.8 MSC Sinda Preference MSC Sinda is now a new thermal analysis offering from MSC. Sinda database can be created without an MSC Sinda installation. Very Powerful! .50 Patran Release Guide MSC Sinda Preference 4. MSC Sinda solves problems using resistance-capacitance network approach. MSC Sinda must be installed in order for the Preference to be able to submit analyses and retrieve results. coupled with fast finite difference numerical methods and including power FORTRAN programming. You are referred to the MSC Sinda Preference User Guide for further in formation.
This meant that for fine control of the property generation. Create LM_Layup Add When creating an analysis model (i.9 Laminate Modeler Laminate Modeler incorporates a number of enhancements to promote the effective modeling of laminated composites structures. This is convenient when investigating multiple configurations. the user would need to use the separate Create . These are described below under the headings of the appropriate command. This opens the selected Layup file AND imports the shell mesh in the Layup file into the database. the default laminate orientation method and additional options were used previously.e.Chapter 4: General Enhancements 51 Laminate Modeler 4. The Laminate Modeler initialization form.. This avoids the need to issue the Import Model Layup File command manually after opening the Layup file. which allows the user to begin the Laminate Modeler session now has two new options: Import Layup File… Available if no mesh exists in the current Patran database. generating properties) at the same time as creating or modifying a LM_Layup. Save As… Saves the Layup model to the selected Layup file AND updates the current file name.
Now. best practice is to use coordinate systems to define both the Reference Directions of plies. and the orientation of the generated laminate materials. Transferring a design model from CATIA Composites Design and Laminate Modeler using . and means that the coordinate system is written to the analysis input deck and directly available to the solver. increasing efficiency and promoting the use of the most appropriate orientation option. For many problems. Layup Definition Spreadsheet The Layup spreadsheet allows the definition of the Ply Group and Sequence associated with each Layup Ply instance as shown below.52 Patran Release Guide Laminate Modeler Laminate LM_Layup command. This is not used directly within the analysis environment but promotes interoperability with composites design systems where plies are grouped hierarchically under these headings. This maximizes correlation between ply and property definition. the user can set detailed options directly on the first form.
Create LM_Layup Laminate This new command extracts ply and layup definitions stored in the Laminate Materials using global ply identifiers (GPlyIds). and the rotation is set to that for the start element.Chapter 4: General Enhancements 53 Laminate Modeler Simulayt's Composites Link will transfer this information bi-directionally to ensure that designers and analysts can communicate effectively. and the application direction is set opposite its normal direction. modifying a ply of this type will reset orientations so that this should be avoided. The start point is arbitrarily set to the centroid of the element in the ply having the lowest Id. The symmetry of the current Layup sequence is now reported as a label instead of the previous option menu to emphasize that this is a result of the Layup sequence defined and not an option that can be set by the user.X where X is the appropriate GPlyId value. The ply type is set to a Projected type based on rotation with respect to the element datum. . Please note that as these are necessarily arbitrary assumptions. The plies are named gplyid.
Create Results Failure Calc This command has been enhanced to work with results that have already been sorted by MD Nastran on the basis of global ply identifiers (GPlyIds). Please note that while this follows recommended practice for the use of global ply identifiers. as the criterion's interface is well defined. Both the Allowable values and the Results created are set by the selected criterion and are then respectively input and selected readily by the user. these same criteria could be used consistently in other calculation environments. The failure calculation in Laminate Modeler has traditionally supported custom failure criteria using a PCL function. The results are assumed to be sorted already if results layer ids do not begin at layer 1 OR the results layer ids are not sequential OR the number of elements in a result increases with results layer id OR an element in a result does not exist in a previous layered result.54 Patran Release Guide Laminate Modeler The global plies are added to the LM_Layup in increasing order of GPlyId. after which the Add-In becomes available for selection by the user as shown below. comprehensive support for custom failure criteria is provided by means of Add-Ins developed in C++ using Simulayt's Add-In architecture. such as a spreadsheet for initial calculations. The Add-Ins are simply placed in a directory identified by the environment variable SLTAddinPath. Now. it is highly unlikely that sorted results will be identified as unsorted ones. . The flexibility of the new Add-In failure criterion system will allow the creation of high performance failure criterion able to model multiple failure criteria in a single compound criterion. And. With this comprehensive checking. there is no guarantee that the order on each element will be consistent and so this should be checked carefully.
Mapping was calculated using a line from the centroid of a destination element in the element normal direction. . Now. Delete LM_Layup Select As a Laminate Modeler model can only contain a single LM_Layup. the option of defining an average normal direction based on the surface normals at each node of an element has been added. Import Plies File When importing plies from a Layup file or FiberSIM data. a warning is given and the unmapped elements are placed in a group called LMImportUnmappedElements so they can be identified easily. the mapping is not initialized and it was difficult to identify the faulty element previously. the name of an exiting LM_Layup is now displayed in a databox and not a listbox to prevent confusion. if selected elements are unmapped. particularly when the Auto Execute option is used in the ply selection listbox. If the source and destination elements are too widely separated. This can improve mapping where the destination surface contains sharp creases as shown below. Now. This is a common situation for frames and spars commonly used in the aerospace industry.Chapter 4: General Enhancements 55 Laminate Modeler Show LM_Ply Graphics This command has been enhanced to allow the visualization of draped and flat patterns where appropriate. This allows quicker identification and resolution of mapping problems. These are computed on-the-fly and can prove to be a most effective visualization tool. the plies from the source file are mapped onto the destination elements in Patran.
56 Patran Release Guide Laminate Modeler Import Results ESAComp xml ESAComp is a laminate analysis tool that can generate failure criteria that are written in an xml file. Elements which fail the selected tests are highlighted in the viewport using the relevant color. The user selects the element to be verified. The required test is then selected and applied. The results of a symmetry check on a vertical tail plane model are shown as an example below. balance. and a spreadsheet listing all failed elements and the test they have failed is displayed. a "main" direction (such as the trailing edge of a wing) and thickness and angle tolerances required for some tests. This new command reads the result data from the file and creates a Patran result that can be viewed in the usual way. . Verify Laminate This new command allows the user to verify that the laminate created satisfies general rules that reflect the requirements of the aerospace industry. taper ratio and so on. such as symmetry.
Patran. then pre-selection highlighting would display nodes offset from their true position. “$” Allowed in Group Names . A new settings. Material Stiffness Matrix Terms .. These consist of defect corrections and enhancement request.RecentFiles. On UNIX.num_files) The list of recent files is found in a file called . pref_env_set_integer("RESULTS_TITLE_CHECK_LEVEL". OEFIT OP2 Datablock . Jobname and Results Case Name Conflict .g.Results for 15-noded CPENTA elements can now be accessed via XDB files.Patran. C55 and C66 terms are now ordered correctly when converting 3D Orthotropic materials to 3D Anisotropic for MAT9 entries. Long Result Case Names . On Windows.A defect was corrected where failure indices from composite failure analysis were not being processed correctly when reading the OEFIT datablock from a Nastran OP2 file. The number of files visible is controlled by settings. e.RecentFiles located in the users’ home directory.Result case names that exceeded 80 characters would result in a PCL traceback if filtered.The C44.A defect was corrected where if a group of nodes and/or elements was erased that caused a fit view to occur (Preferences->Graphics->Auto Extend). /home/user. 15 Noded CPENTA Results .level) This is an integer value with the following meanings: 1-64306194 1-66078121 1-15765121 1-16900917 1-19052381 1-19730217 .pcl file environment variable: pref_env_set_integer("max_num_recent_files".10 Customer Requests Many customer requests (CRs) were addressed in this release. e.Allows you to select from a list of recently accessed database files. The following are significant customer requests or defects that were addressed that may be of interest to users in addition to those that have already been referenced in previous chapters/sections: CR # 1-68705473 Description File / Open Recent .g. the environment variable HOME must be set. the results cases were picking up the jobname instead of the actual subcase name as defined in the Nastran job. “C:” and “\” = C:\.Groups with “$” symbols in the name now function properly when editing Global Subcase Output. 1-66889951 Preselection Highlighting Entity Offset .pcl variable has been implemented to control this.In cases where an existing jobname is active but an XDB file is attached with subcases not associated to the active job. this is determined by the HOMEDRIVE and HOMEPATH variables. The character limit has been increased to 256 to avoid this..Chapter 4: General Enhancements 57 Customer Requests 4.
In the Nastran preference. then the functionality remains the same as the default behavior.user is prompted for default behavior (NO) or to use previous behavior.Incorrect fringe plots have been corrected when the GAUSS field on the PSOLID entry is activated during a Nastran run and results accessed from Patran via the XDB file. A small icon appears next to the listbox that can be expanded to a large listbox. MBOLTUS Import Support . and Fields applications as well as Groups and Regions where the large listbox capability has been enabled without having to invoke Patran with the “-l” option for large listbox capability.There are number of places in the Element Properties. Some Result Layers missing from XDB Attachment . 2. 1-19960526 DB Import Changes Poisson’s Ratio Value .user is warned that the jobname and results file name differ but the default behavior still occurs In all cases.users is notified that jobname and results file name differ and given the choice to continue or not.Default behavior: not set or zero or >3 .XDB attachments were only recognizing layers of the first results cases even though subsequent result cases had more layers. LoadsBCs.Importing Nastran files with PLOAD4 pressures that vary spatially now import correctly and a proper spatial field is created for each load set. Materials. 1-23657326 1-50872269 1-32732851 1-52553651 1-64846211 1-18201068 .MBOLTUS entries in the Nastran input deck are now imported as Overclosure MPCs Residual Vector Computation . Continuing will give the default behavior. TET10 Stress Data using GAUSS on PSOLID . the Residual Vector Computation toggle now writes RESVEC=YES or RESVEC=NO if the parameter is present in the database for that job no matter what. PLOAD4 Import . Previously only RESVEC=NO was being written because RESVEC=YES is the default for most SOL sequences. results case names do not get associated to load case names of the existing jobname 1 . which is to put the loadcase names associated to the current jobname into the result case names (NOT RECOMMENDED .if results (XDB) file name and jobname do not match for Nastran Preference only. So now RESVEC=YES is written if the toggle is ON. on the solution parameters form. But for SOL 103.but the use can do it if he wants) 2 . which slightly changing the property value. no RESVEC entry defaults into RESVEC=COMPONENT where the desired default is RESVEC=YES or BOTH. 3 . or 3 only have effect if the jobname and the XDB file name differ. Values of 1. Large Listbox Capability .This corrected an incorrect rounding of material data occurring occasionally on import into another database.58 Patran Release Guide Customer Requests CR # 1-19730217 Description 0 . if the jobname and the XDB filename are the same.
and bulk data TEMPD entries now supported for SOL 600. Other results tools automatically turn off the spectrum and hide the option from the user. Turn Spectrum Off with Constant Contours . Now if nodes in a group are referenced in properties.The calculation of the torsional constant J of a cross-type cross-section does not have a closed form solution. Imprinted Parasolid Geometry . Nodes/Grid Projection in Radial Direction . fields or MPC's. Individual control is now given under the Translation Parameter form for grids.It is now possible to mesh imprinted Parasolid geometry.It is now possible to control the number of significant digits in envelope plots under the Tools / MSC. MPCs.When creating a contour plot. the user can set the attributes to 'Constant'.The ability to create lists of nodes associated to MPCs has been implemented under the Tools/List/Create utility. Nodes Left Behind After Group/Transform . subsequent meshes were being placed in the wrong physical location using the Hybrid or Sheet Body meshers.SPOINTS associated with beam definitions of warping degrees-offreedom from the Nastran input deck are now imported to retains those definitions in the beam element properties.Explore utility. Torsional Constant J of Cross Cross-sections . SPOINT Import . Spherical systems are also supported and all other component directions.More control for writing significant digits is given when writing Nastran input decks. TEMP(INIT). Mesh in Wrong Location after Surface Transformation . coordinate frames. The beam section library now calculates J and the shear stiffness factors of this standard cross section by using the routines for calculating these properties for arbitrary beams cross sections. displaying all contour lines in a single color. The user no longer must manually turn off the spectrum to see a correct plot.Chapter 4: General Enhancements 59 Customer Requests CR # 1-40919043 Description Significant Digit Control . Significant Digits in Envelope Plots . MPCs & Tools/List/Create . the spectrum is applied immediately without having to recreate the results plot.Nodes and grids can now be projected onto a surface in the radial direction when a cylindrical system is referenced. 1-45336797 1-40918941 1-67076271 1-70170481 1-19671064 1-18657123 1-9146004 1-25240879 1-59220230 1-17613229 1-70358907 1-43797130 . LBCs.Nodes referenced as GO points for defining beam orientations were not transformed during a Group/Transform operation.After transforming parasolid surfaces to new locations using Group/Transform. Fastener Results in Multiple XDB files . but the contour leaves the spectrum in place with its varying colors. materials and properties.When a new spectrum is selected from the Display/Spectrums form.Nastran case control TEMP(LOAD). SOL 600 TEMPD Support .An issue where fastener results were not accessible if multiple XDB files were attached has been corrected. then during the transform operation such nodes are copied. Automatic Spectrum Update .
Correction of assembly meshes of some parasolid models that were incorrectly offset. Correction to Shear Area Factor K for tube cross sections.60 Patran Release Guide Customer Requests CR # 28974 1-75970050 1-77244825 1-54421399 Description Deletion of Multiple Load Cases . when equivalencing nodes you can now do the boundary verify operation on the same form rather than having to change the Action / Object to Verify / Boundaries Direct Text Input for the MSC Nastran Preference now allows you to specify if you want the text input at the start or the end of the specified section of the input file.The ability to delete multiple load cases in one operation has been implemented. Large listbox capability has been implemented for portions of the Tools / Design Study / Preprocessing application. In the FEM application. 1-77359861 1-78080878 1-50781738 1-62817224 1-67083505 . RSPINR entry for Nastran rotor dynamics has been updated to support both Nastran 2007 and pre 2007 formats. Connector elements are now erased in a deformation plot if the user requests the undeformed shape to be hidden.
18 O Operating systems. 6 Automatic Feature Recognition. 2 Parasolid. 6 Pro/ENGINEER. 10. 51 LINUX. 3. 7 AIX. 3. 4.Fatigue Quick Start Guide Index Patran Release Guide Numerics P atr an R el ea se G ui 64 Bit Port. 7 Platforms. 1 MSC Marc Preference. 7 Contact. 4. 4. 6 Optimization. 39 R Hardware. 34 I S IBM. 3. 44 Laminate Modeler. 2 A ACIS. 4. 7 Catia V5. 7 CATIA V5. supported. 5. 6 I-DEAS. 39 . 47 SimXpert Integration. 30 Right Mouse Button. 4. 6 SimManager Integration. 2 UG NX. 6 B C M Batch Image Rendering. 1 MSC Sinda Preference. 6 Highlights. 2. 4.MSC. 7 Intel. 28 MD Nastran Preference. 2 P G H Parasolid. 6 Results. supported. 46 CAD Access. 57 Marc. 3. 4. 5. 50 Skins. 4. 2. 7 GUI Skins. 2 HP. 50 N Nastran. 43 K L Key Highlights. 2 CATIA V4. 1 Nonlinear Analysis. 2. 2. 2. 24. 2 InterOp. 31 Customer Requests. 28 MSC Nastran Preference. 49 Sinda. 2 E Enhancements. 4. 6 Red Hat.
23 Topography. 6 T Thermal Analysis. 3. 2 Topometry.62 Patran Release Guide Solaris. 6 Supported OS levels. 5 W Wildfire. 6 Sun. 6 Supported platforms. 7 Windows. 7 Utilities. 2 U Unigraphics. 2 Topology. 6 .