Download - Patran 2008r1 Doc Release

8/3/2019 Patran 2008r1 Doc Release

1/68

Patran

2008 r1

Release Guide


2/68

Worldwide Webwww.mscsoftware.com

DisclaimerThis 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 2008 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 theUnited 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.

P3*2008R1*Z*Z*Z*DC-REL

Corporate Europe Asia Pacific

MSC.Software Corporation2 MacArthur PlaceSanta Ana, CA 92707 USATelephone: (800) 345-2078Fax: (714) 784-4056

MSC.Software GmbHAm Moosfeld 1381829 Munich, GermanyTelephone: (49) (89) 43 19 87 0Fax: (49) (89) 43 61 71 6

MSC.Software Japan Ltd.Shinjuku First West 8F23-7 Nishi Shinjuku1-Chome, Shinjuku-KuTokyo 160-0023, JAPANTelephone: (81) (3)-6911-1200Fax: (81) (3)-6911-1201


3/68

Con ten t s

Patran Release Guide

1 Patran 2008 r1 at a Glance

Key Highlights 2

CAD Access 2

InterOp R18 SP1/SP3 2Parasolid 19 2

Catia V5 R18 2

Automatic Feature Recognition 2

MD Nastran and MSC Nastran Support 2

Optimization (SOL 200) 2

Implicit Nonlinear Analysis (SOL 400) 3

Explicit Nonlinear Analysis (SOL 700) 3

Thermal-Structural Interaction (SOL 101) 3Results Access 3

Marc Support 3

New Physics Types 3

Results Access 3

General Enhancements 3

Batch Image Rendering 3

SimManager Integration 4

SimXpert Integration 4

MSC Sinda Preference 4

Laminate Modeler 4

Utilities 4

Customer Requests (CRs) 4

Supported OS/Hardware Platforms 5

Supported CADAccess 6

Analysis Preferences Tested 8

Technical Support 9

Web 9

Phone and Fax 10

Email 10

m~~


4/68

Patran Release Guide==iv

2 MD Nastran MSC Nastran Preference

Optimization (SOL 200) Enhancements 2

More Design Variables. 2

More Responses, Constraints, Objectives. 2

Optimization Parameters. 4

Design Variable Relations. 4

General (DLINK): 6

Implicit Nonlinear (SOL 400) Enhancements 8

Brake Squeal 8

Contact Improvements - BCONTACT = ALLBODY 8

Contact Detection - Shell Edge Contact. 8

Contact Detection - 3D Beam to Beam Contact 9

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 17

Nastran Thermal-Structural Chaining 22

Nastran Results 23

3 Marc Preference

Multi-Physics Support 2

Marc Results 4

Initial Contact 6

4 General Enhancements






5/68

vCONTENTS


Laminate Modeler 15

Import Layup File 15Save As 15

Create LM_Layup Add 15

Layup Definition Spreadsheet 16

Create LM_Layup Laminate 17

Create Results Failure Calc 18

Show LM_Ply Graphics 19

Delete LM_Layup Select 19

Import Plies File 19

Import Results ESAComp xml 20

Verify Laminate 20

Customer Requests 21

25

Patran Release Guide 25


6/68

Patran Release Guide==vi


7/68

Chapter 1: Patran 2008 r1 at a Glance Patran Release Guide

1Patran 2008 r1 at a Glance

Key Highlights 2

Supported OS/Hardware Platforms 5

Supported CAD Access 6

Analysis Preferences Tested 8

Technical Support 9


8/68

Patran Release GuideKey Highlights

2

1.1 Key Highlights

The following general enhancements are available in Patran 2008 r1:

CAD Access

InterOp R18 SP1/SP3

The Spatial InterOp, Parasolid based translators have been updated to the R18 SP1 and SP3 revisions.This gives CAD access support based on the table in Supported CADAccess, 6. MSC makes periodic

updates to CAD access and are available through download patches at:

http://www.mscsoftware.com/support/software_updates/#patran

Parasolid 19

Parasolid import now supports up to version 19. The Patran Parasolid kernel is based on Parasolid 19.

Catia V5 R18

Support for Catia V5 R18 is available through the Parasolid import method using the Spatial InterOptranslators.

Automatic Feature Recognition

This revamped feature recognizes geometric features and allows you to view, edit, and delete them. SeeAutomatic Feature Recognition, 2 for more details.

MD Nastran1 and MSC Nastran Support

Optimization (SOL 200)

The following enhancements are provided for support of optimization.

Design Variables: PCOMPG (Global Plys)

Responses/Constraints/Objectives:

Bush Forces

Acoustics

Fluid Modes

Objective Function Modification

Design Variable Relations

See Optimization (SOL 200) Enhancements, 2.1SOLs 400 and 700 are only available in MD Nastran and must be submitted using Patran running in

MD mode.


9/68

3Chapter 1: Patran 2008 r1 at a GlanceKey Highlights

Implicit Nonlinear Analysis (SOL 400)

The following enhancements are provided for support of implicit nonlinear analysis.

Brake Squeal

Contact Improvements

Solution Controls

Thermal Analysis

Analysis Chaining

See Implicit Nonlinear (SOL 400) Enhancements, 8.

Explicit Nonlinear Analysis (SOL 700)

The following enhancements are provided for support of explicit nonlinear analysis as detailed inExplicitNonlinear (SOL 700) Enhancements, 17.

Thermal-Structural Interaction (SOL 101)

Thermal-structural analysis chaining can be performed in a single SOL 101 run using the HEATSTATparameter. See Nastran Thermal-Structural Chaining, 22.

Results Access

Exterior acoustics results via the OP2 file and optimization results via the XDB file are now supported.See Nastran Results, 23.

Marc Support

New Physics Types

New physics types are added to the Coupled analysis type in an on-going effort to support Marcsmultiphysics capabilities. See Multi-Physics Support, 2.

Results Access

Output requests now include the ability to select layers of composites. SeeMarc Results, 4.

f~=`~K=It is now possible to define an initial contact table in the model definition section. SeeInitial Contact, 6.

General Enhancements

Batch Image Rendering

Graphical image files can be rendered and produced in batch mode. SeeBatch Image Rendering, 5 fordetails.


10/68

Patran Release GuideKey Highlights

4

SimManager Integration

Logon, publish, and retrieve Patran databases and related analysis files through this SimManager

client/server access. See SimManager Integration, 6 for details.

SimXpert Integration

Spawn SimXpert directly from Patran and transfer finite element model data to SimXpert. SeeSimXpertIntegration, 11 for details.

MSC Sinda Preference

A new thermal analysis preference has been added as a standard analysis preference. SeeMSC SindaPreference, 13.

Laminate Modeler

A number of enhancements have been add to the Laminate Modeler as detailed inLaminate Modeler, 15.

Utilities

Please review the Utilities/ What is New menu to see additions/updates made to the utilities.

Customer Requests (CRs)

A number of enhancements and defect correction have been made. The most significant ones are listedin Customer Requests, 21.


11/68

5Chapter 1: Patran 2008 r1 at a GlanceSupported OS/Hardware Platforms

1.2 Supported OS/Hardware Platforms

For a complete description of these configurations, seeRequired Hardware & Software Configurations(Ch. 5) in thePatran Installation and Operations Guide.

Vendor OS LevelsChipsetSupport HW Support Graphics Support

HP (PA-RISC)

HP-UX 11i (11.11) PA8000PA8200PA8500PA8600PA8700PA8800PA8900

PA8000: C160, C180, J280,J282,PA8200: C200, C240, J2240,PA8500: C360, B1000, B2000,C3000, J5000, J7000PA8600: C3600, J5600, J6000PA8700: C3700, C3750, J6700,J6750

PA8800: C8000, PA8900: C8022

Visualize: FX5 Pro, FXE,FX5 Pro, FX10 Pro, FireGL-UX, X3

SUN Solaris 10 UltraSPARC IIIUltraSPARC III+UltraSPARC IIIi

Ultra 30, 60, 80SunBlade 1000, 1500, 2000,2500

Creator3D, Elite3D,Expert3D, XVR 500, XVR600, XVR 1000, XVR 1200

Intel Windows XPWindows XP SP2Windows XP-x64

Windows Vista

Pentium IIIPentium 4XeonAMD Opteron

Compaq: W4000, W6000,W8000Compaq Laptops: N800c,N800wDell: Work. 410, 610, 220, 420,620, 330, 340, 350, 360, 370,380, 390, 450, 470, 530, 650, 670Dell Laptops: M50, M60, M70,M90HP: Visualize NT (p-class, x-class),xw4000/xw5000/xw6000/xw8000, xw3100/xw4100QOMMLSOMMLUOMM

HP Laptops: mw8240,

mw8440, mw9440IBM: IntelliStation Z-Pro, M-Pro, E-Pro,A-ProSUN: W1100z, W2100z

3DLabs: Wildcat IV 7110,7210, Realizm 100, 200, 800ATI:FireGL 8700/8800, FireGL E1, X1-128, Z1-128, T2-64, T2-128, X2-256,VS3100, V3350, V5000,V5100, V7100, V7300,

V7350, VS100, MobilityRadeon (N800 Laptops)HP: fx5+, fx10+NVIDIA: Quadro2 EX,Quadro4 700XGL/750XGL/900XGL/980XGL, Quadro4500/700 GoGL (M50/M60

Laptop), FX330, FX500,

FX1000, FX1100, FX1300,

FX3000, FX3400, FX4000

Intel LINUXRed Hat Enterprise 4.0

Pentium IIIPentium 4XeonAMD Opteron

Dell: 220, 420, 620, 330, 340,350, 360, 370, 450, 470n, 530,650, 670nHP: Visualize NT (pL-class, xL-class), x-classIBM: IntelliStation

SUN: W1100z, W2100z

ATI: FireGL 8700/8800,FireGL X1NVIDIA: FX500, FX1100,FX1300, FX3000, FX3400,FX3450 FX4000,

IBM AIX 5.3 POWER3POWER4POWER5

43P, 44P, IntelliStation Power265, 275, 285

GXT4500P, GXT6500P

P t R l G id6
http://../ops_manual/ops_print.pdfhttp://../ops_manual/ops_print.pdfhttp://../ops_manual/ops_print.pdfhttp://../ops_manual/ops_print.pdfhttp://../ops_manual/ops_print.pdfhttp://../ops_manual/ops_print.pdf


12/68

Patran Release GuideSupported CADAccess

6

1.3 Supported CADAccess

***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, therefore, the list ofplatforms supporting this import method is the Pro/ENGINEER supported machines.

Import to Parasolid which runs from within interactive Patran: does not

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. Existing Patran translator is still available for pre-

Pro/ENGINEER Wildfire release.

The following steps are necessary for customers to use the Patran Pro/ENGINEER translatorwith Pro/ENGINEER after January 10, 2004:

PTC Important System Notice - Timeout http://www.ptc.com/go/timeout/

PTC Technical Resource http://www.ptc.com/go/timeout/technical_resource.htm

For Pro/ENGINEER 2001:

Download NMSD.exe and follow PTC instructions.

HP(PA-RISC) SUN

IBMRS/6000

Windows2000 / XP /

Vista Linux

CATIA V4*

*A CATIA CATXPRES (.cat) file can be imported. On Windows and Linux, only the CATIA to Parasolid translatoris available and the CAT Direct Translator which runs CATIA in batch mode is not available.

4.2.4 4.2.4 4.2.4 4.2.4 4.2.4

CATIA V5 R18 R18 R18 R18

Pro/ENGINEER

The p3_ProE and p3_ProENGINEER executables are built using Pro/ENGINEER version 2000i and therefore willnot work with earlier versions of Pro/ENGINEER. p3_ProE and p3_ProENGINEER Access allows reading of.geogeometry transfer files generated from other OS installs of Pro/ENGINEER Access.

Wildfire

3.0***

Wildfire

3.0***

Wildfire

3.0***

Wildfire

3.0***Unigraphics

UG NX supports only 64 bit machines for HP and SUN Platforms.

NX5.0 NX5.0 NX5.0 NX5.0 XMT**

**Only Parasolid (transmit file) import is supported in this release. Parasolid transmit files generated on other OSplatforms can be imported on LINUX.

I-DEAS 11.0 12.0 11.0 12.0

Parasolid 19 19 19 19 19

ACIS 18.1 18.1 18.1 18.1 18.1

7Chapter 1: Patran 2008 r1 at a Glance


13/68

7Chapter 1: Patran 2008 r1 at a GlanceSupported CADAccess

For Pro/ENGINEER Wildfire:

Download NMSD.exe and follow PTC instructions.

Download wildfire datecode 2003490 and follow PTC instructions.

The Pro/ENGINEER Wildfire 2.0 release introduced the following platform changes:

HP-UX and SUNS supports 64-bit only. Patran translator compatible with pre-Pro/ENGINEERWildfire 2.0 and Pro/ENGINEER Wildfire 2.0 release. If running Pro/ENGINEER Wildfire 2.0,the HP-UX and/or SUNS platform must be a 64-bit capable machine to run the Patran translator

Pro/ENGINEER Wildfire 3.0

Linux is supported for Import to Parasolid

The p3_ProE and p3_ProENGINEER executables are built using Pro/ENGINEER version 2000iand therefore will not work with earlier versions of Pro/ENGINEER.

p3_ProE and p3_ProENGINEER Access allows reading of .geo geometry transfer files generated fromother OS installs of Pro/ENGINEER Access.

Patran Release Guide8


14/68

Patran Release GuideAnalysis Preferences Tested

8

1.4 Analysis Preferences Tested

Solver Platforms Solver Version

MD NastranMSC Nastran All

MD Nastran R3MSC Nastran 2008 r1

Marc All 2008 r1

Dytran All 2008 r1

Flightloads All 2008 r1

Thermal All 2008 r1

Fatigue All 2008 r1

MSC Sinda All 2008 r1

LS-DYNA3D All 970

PAMCRASH All 1995 / 1997

SAMCEF All 11 / 12

ABAQUS*

*ABAQUS discontinued platforms remain at the level of support at the time they were discontinued byHKS. For instance SUN support is frozen at 6.4.

All 6.6

ANSYS

Results access is enhanced to 11.0 (results import is frozen at 8.1).

All 11.0



15/68

9Chapter 1: Patran 2008 r1 at a GlanceTechnical Support

1.5 Technical Support

For help with installing or using an MSC.Software product, contact your local technical support services.

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.g., fatal messages)

Verification of code error.

If you have concerns about an analysis, we suggest that you contact us at an early stage.

You can reach technical support services on the web, by telephone, or e-mail:

Web

Go to the MSC.Software website at www.mscsoftware.com, and click on Support. Here, you can finda wide variety of support resources including application examples, technical application notes, available

training courses, and documentation updates at the MSC.Software Training, Technical Support, andDocumentation web page.



16/68

Patran Release GuideTechnical Support

Phone and Fax

United States

(800) 732-7284

(714) 784-4343

Frimley, CamberleySurrey, United Kingdom

(44) (1276) 67 10 00

(44) (1276) 69 11 11

Munich, Germany

(49) (89) 43 19 87 0

(49) (89) 43 61 71 6

Tokyo, Japan

(81) (3) 3505 02 66

(81) (3) 3505 09 14

Rome, Italy

(390) (6) 5 91 64 50

(390) (6) 5 91 25 05

Paris, France

(33) (1) 69 36 69 36

(33) (1) 69 36 45 17

Moscow, Russia

(7) (095) 236 6177

(7) (095) 236 9762

Gouda, The Netherlands

(31) (18) 2543700

(31) (18) 2543707

Madrid, Spain

(34) (91) 5560919

(34) (91) 5567280



17/68

pTechnical Support

Email

Send a detailed description of the problem to the email address below that corresponds to the product you

are using. You should receive an acknowledgement that your message was received, followed by anemail from one of our Technical Support Engineers.

Patran Support

MD Nastran Support

MSC.visualNastran Desktop 4D Support

Dytran Support

MSC Fatigue Support

Marc Support

MSC.Mvision Support

MSC.SuperForge Support

MSC Institute Course Information

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]



18/68

Technical Support


19/68

Chapter 2: MD Nastran MSC Nastran Preference Patran Release Guide

2MD Nastran MSC Nastran Preference

Optimization (SOL 200) Enhancements 2

Implicit Nonlinear (SOL 400) Enhancements 8

Explicit Nonlinear (SOL 700) Enhancements 17

Nastran Thermal-Structural Chaining 22

Nastran Results 23

Patran Release GuideOptimization (SOL 200) Enhancements

2


20/68

Optimization (SOL 200) Enhancements

2.1 Optimization (SOL 200) Enhancements

More Design Variables.Support for specifying composite shell thickness and orientation based on global ply layers as designvariables is now supported (PCOMPG - previously only PCOMP was supported). Design variablecreation has also been extended to PCOMPG property entries for values such as offset, non-structuralmass, reference temperature, etc.

More Responses, Constraints, Objectives.

The following are available to define as responses, constraints, and objectives (DRESP1 / DRESP2entries):

CBUSH Forces available as constraint or objective for linear statics, normal modes, frequencyand transient response.

Acoustic responses available as constraints or objectives for frequency response analysis.

3Chapter 2: MD Nastran MSC Nastran PreferenceOptimi ation (SOL 200) Enhancements


21/68


Fluid modes for normal modes analysis.


4


22/68


Optimization Parameters.

Objective Function Modification: This toggle is available on the Advanced Optimization Parameters

form under the Analysis (Action=Optimize) application when submitting the job. Turning this toggleON indicates to MD Nastran SOL 200 to modify the objective function such that it reports back in thesummary (F06 file) the relative change instead of the absolute change. For example if only one part ofthe model is being optimized and it changes by 0.2 lbs, then that is what is reported rather than sayingthe over all structural weight went from 100005.0 to 100004.8 lbs. This is written to the DOPTPRM(OBJMOD) entry.

Design Variable Relations.

This new Variable Relations feature allows you to define an expression which contains a number ofdesign variables linking them as dependent and independent. Once a variable relation has been definedit can be associated to a Design Study. A Design Study is a selection or grouping of the applicable designvariables, constraints, objective, and responses that the user wishes to employ in a particular

5Chapter 2: MD Nastran MSC Nastran PreferenceOptimization (SOL 200) Enhancements


23/68


optimization. The variable relations are also selected as part of a Design Study in order to activate themfor any particular optimization.

There are several ways to define an expression or variable relation:


6


24/68

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 designvariables and associating a coefficient to each. The following simple, general equation is used to definethe 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

7Chapter 2: MD Nastran MSC Nastran PreferenceOptimization (SOL 200) Enhancements


25/68

p ( )

IDVi = Independent design variable

Patran Release GuideImplicit Nonlinear (SOL 400) Enhancements

8


26/68

2.2 Implicit Nonlinear (SOL 400) Enhancements

Brake SquealSupport for Brake Squeal Analysis (BSQUEAL). Specific brake squeal parameters are set on the StaticSubcase Parameters form. The analysis is performed with a static step followed by with a complexeigenvalue step.

Contact Improvements - BCONTACT = ALLBODYThis is written to case control if:

1. There are contact bodies in the selected load case, AND

1. The user does not make any changes to the contact table (i.e., all entries are default values)

If the user wants the contact table written out, they can simply make any minor change and Patran willwrite the contact table.

Contact Detection - Shell Edge Contact.

Shell edge contact (with moment carrying glue) is supported on the Contact Detection form shown below.Moment carrying glue option is controlled globally via the Contact Detection form, by contact body, andvia the contact table per body pair. See the next section on beam to beam contact and the section oncontact table improvements.

9Chapter 2: MD Nastran MSC Nastran PreferenceImplicit Nonlinear (SOL 400) Enhancements


27/68

Contact Detection - 3D Beam to Beam Contact

Beam to beam contact can be turned on under the Contact Detection form. Beam contact radii are defined

on in the Element Properties application when defining beam properties. A standard default value definedby MD Nastran is used if not specified.


10


28/68

Contact Body Movement (BCMOVE) - approach step.

Under the Analysis form when setting up subcases or load steps, a body approach subcase can be

specified. In this subcase, active contact bodies are moved into place until one or all are just touching forthe beginning of the next subcase, or load step. The Synchronized toggle indicates to the analysis codeto move all bodies in sync with one another until the first contact is made at which point the movementis stopped for the load step. If this toggle is off, then bodies continue to move until all are in contact. Thisis controlled in Nastran using the BCMOVE entry.

Contact Body Definition (BCHANGE/UNGLUE)

The following improvements are available when defining deformable contact bodies:

Contact Area - When defining a deformable contact body, nodes which come into contact can bespecified using the Contact Area definition.

Exclusion Region - Edges and faces of deformable contact bodies that are to be excluded andignored in the contact detection algorithms can be defined using the Exclusion Region.

Glue Deactivation Certain areas of a contact body (that has been designated as glued) can beswitched to standard touching contact so not all nodes of a contact body need to be glued.



29/68

Note that Edge contact can be specified at the contact body level also.

Contact Table.

The following improvement have been made to the contact table such that the following can be specifiedper body pair:

Braking Glue (BKGL) Parameters - defines the threshold at which a glued node separates

Edge Contact - controllable at the body pair level as well as per body and globally


12


30/68

Moment Carrying Glue - can be turned on/off per body pair for those bodies that are defined asglued. This works in conjunction with the toggle to retain gaps.



31/68

Initial Contact

The initial contact table can now be defined for both the Nastran and Marc Preferences under the ContactParameters form.

Solution Controls.

More options to control the load incrementation have been opened up in the graphical interface. Forexample, the ability to specify automatic switching between displacement and residual forceconvergence criteria. Most items on the MD Nastran entries below are now accessible.

Load Increment Parameters form (NLAUTO)

Nonlinear Static and Transient Analysis Controls (NLPARM/TSTEPNL)

Additional Load Increment Parameters (NLADAPT)

Thermal Analysis.

SOL 400 thermal analysis is now supported under the MD Nastran Thermal preference for unchainedheat transfer analysis. Supported solution types are Steady State and Transient Heat Transfer analysis.


14


32/68

This includes specifying heat transfer contact bodies and the ability to control thermal properties perbody pair using the contact table.

Analysis Chaining.

This is the ability to create multiple subcases (load steps), select them in the order in which they shouldbe run and the analyses are chained together, meaning that the results from the last increment of theprevious load step become the starting point for the next load step. An example is a modal or a bucklingstiffening problem where a static linear or nonlinear analysis is performed first and then the modal or

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

15Chapter 2: MD Nastran MSC Nastran PreferenceExplicit Nonlinear (SOL 700) Enhancements


33/68

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

Patran Release GuideExplicit Nonlinear (SOL 700) Enhancements

16


34/68

Bird strike / Prestress & Impact on Rotating Fan Blade

SPH (smooth particle hydrodynamics) andDrop test of computer package



35/68

Rod penetration

Train barrier/pickup truck

This translates into support of the following MD Nastran SOL 700 entries which can be defined in thefollowing application areas of Patran:

Loads/BCs AIRBAG/BCSEG Defines an airbag; Loads/BC object is an Airbag; BCSEG entries are

created from the defined application region of the airbag

BCGRID Defines contact grids; available as a new Contact boundary condition option

BCPROP Defines contact based on element properties; available as a new Contact boundarycondition option

BCBOX - Another way of defining a contact body; available under Box Definition; all elements

inside the defined box are part of the contact body

SPCD2 Imposed nodal motion

Patran Release GuideExplicit Nonlinear (SOL 700) Enhancements

18


36/68

GRIA Grid point in a bag reference geometry; defined when creating an airbag

TICEUL1, TICREG, TICVAL, SPHERE Eulerian initial conditions

MESH Defines a mesh; this is done as a boundary condition under the Loads/BCs application FLOWDEF Eulerian flow boundary; defined as a boundary condition under the Loads/BCs

application

COUPLE, COUOPT General Euler-Lagrange coupling surface; defined in the Loads/BC as aCoupling LBC

TICD Transient analysis initial conditions; defined as a boundary condition in Loads/BCsapplication

HYDSTAT - Hydrostatic Preset of Density in Euler Elements; defined in the Loads/BCsapplication as Hydrostatic Preset

Materials

EOSGAM Eulerian Gas; defined under Materials application,

MATDUEL Eulerian material properties; defined under the Materials application

EOSPOL Polynomial equation of state; defined in the Materials application as a Eulerian-Solid

MATDERO Erosion material; defined under Materials application as Erosion model

MATRIG Rigid body properties; defined under the Materials application as a Rigidconstitutive model for an Isotropic(SOL700) material

EOSGRUN Gruneisen equation of state; defined under Materials application

MATD020 Rigid material

MATD014 Soil and foam with failure

Element Properties

PEULER1 - SOL 700 eulerian solid properties; defined under the Element Properties application

PSHELL1 SOL 700 shell element properties; defined under the Element Properties application

CSPH, PSPH Defines an SPH particle; done as a 0D element property under the ElementProperties application

Analysis

PRESTRS To perform a pre-stress run and determine the pre-stress state, which is used asinitial conditions; activated in the Analysis application under Solution Parameters

DYDEFAUL SOL 700 defaults settings; defined in the Analysis application under SolutionParameters

SPHDEF SPH analysis controls; set under the Analysis application under Solution Parameters

FEM (Finite Elements)

CSPOT, CFILLET, CBUTT Spot weld, fillet weld, and butt weld; defined as MPCs in the FEMapplication



37/68

Meshing - Because of lack of numerical grid, SPH processor requires some conditions in settinginitial particle masses and coordinates. The particle mesh needs to be regular, i.e., all particles ofgiven neighborhood need to have same mass. As a consequence, the particles of the same

material which has same initial density need to have same volume. To preserve this they need tobe distributed on a uniform mesh. When meshing a cylinder it is better to use regular mesh toguarantee stability and convergence of the method. To get a regular mesh, this is done under theFEM application: Create/Mesh/Regular

Patran Release GuideNastran Thermal-Structural Chaining

20


38/68

2.4 Nastran Thermal-Structural Chaining

It is now possible to set up a chained thermal-structural analysis in one run using SOL 101. The procedure

is to:

1. With the Preference set to Structural, create and set up your structural LBCs and load case

2. Change the Preference to Thermal, create and set up your thermal LBCs and load case

3. Set the Solution Type to STRUCTURAL HEAT ANALYSIS

4. Set up two Subcases, one referencing the structural load case and the other referencing the thermalload case.

5. Select the two Subcases in the order: Thermal, Structural6. Submit the job

The Nastran run is submitted as a SOL 101 with two Subcases. The first subcase is the heat transfer runto determine the temperature loading. The temperature results from the first subcase are used along withany other structural LBCs called out in the second subcase, which is a SOL 101 run. The PARAM,HEATSTAT, YES is written to the input deck.

This only works for SOL 101 presently. The model shown is a computer chip with temperature fringe

due to heating and convection and resulting (exaggerated) structural deformation.

Select STRUCTURAL HEAT ANALYSIS

Select the two Subcases

21Chapter 2: MD Nastran MSC Nastran PreferenceNastran Results


39/68

2.5 Nastran Results

OUTPUT2 File

Exterior acoustic results via the OP2 file can now be imported. Shown are results on a field point mesh.Results include Intensity, Acoustic Power, and Results on Field Point Meshes.

The following datablocks are now supported via the OP2 file for exterior acoustics analysis:

OARPWR1- Acoustic power

OAIG1- Acoustic Intensity

OUGFP1- Field point Mesh

OVGFP1 - Field point velocity

Patran Release GuideNastran Results

22


40/68

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.

Ch t 3 M P f P t R l G id


41/68

Chapter 3: Marc Preference Patran Release Guide

3Marc Preference

Multi-Physics Support 2

Marc Results 4

Initial Contact 5

Patran Release GuideMulti-Physics Support

2

3 1 Multi Physics Support


42/68

3.1 Multi-Physics Support

In the previous release, the following physics types were supported in addition to Structural, Thermal,

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.

3Chapter 3: Marc PreferenceMulti-Physics Support

Shown is a micro-thermal actuator / an electrical-thermal-mechanical coupling (Joule-structural)


43/68

Shown is a micro-thermal actuator / an electrical-thermal-mechanical coupling (Joule-structural).

The following enhancements have been made to the Materials, Element Properties, Fields, and Loads andBCs applications in support of Multiphysics:

Materials: Electrostatic, Electrodynamic, Magnetostatic, and Piezoelectric constitutive model forapplicable material types (Isotropic, Orthotropic, 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, body, vector, and wire current)

Charge (boundary and body)

Voltage

Potential (electrostatic, magnetostatic)

Magnetization (permanent magnet)

Patran Release GuideMarc Results

4

3 2 Marc Results


44/68

3.2 Marc Results

A significant new enhancement regarding requests for Marc results output is the ability to specify the

layers of composite results. The Results Output Format must be set to 2007 (POST code revision 13) onthe Translation Parameters form to access this functionality.

1. Set Results Output Format to 2007 (POST Code rev13) in Translation Parameters form

2. In Step Create form, go to Output Requests

3. In Output Requests form go to Element Results

4. In Element Results go to Layers form.

The default is not to specify any layers. Options are all layers, top/bottom/middle, layers only or a list oflayers.

5Chapter 3: Marc PreferenceInitial Contact

3 3 Initial Contact


45/68

3.3 Initial Contact

The initial contact table can now be defined for both the Nastran and Marc Preferences under the Contact

Parameters form.

Patran Release GuideInitial Contact

6


46/68

Chapter 4: General Enhancements Patran Release Guide


47/68

4General Enhancements






Laminate Modeler 15

Customer Requests 21

Patran Release GuideAutomatic Feature Recognition

2

4.1 Automatic Feature Recognition


48/68

g

Automatic feature recognition (AFR) has been removed from the Tools/Pre-Release menu and is now a

supported feature under Tools pull down menu. It works from parasolid geometry. Select the entity typeand entities of interest; set the controls; then right-mouse-click on the features you want to recognize

3Chapter 4: General EnhancementsAutomatic Feature Recognition

(holes, chamfers, blends) in the tree widget. This populates the tree widget with the recognized features.Right mo se click on the feat res to sho edit or delete them


49/68

Right mouse click on the features to show, edit, or delete them.

The Parasolid Kernel will fail to edit or delete a feature if there is a topological dependency on other

geometry. Multiple features can be deleted as long as all dependent features have also been selected fordeletion in the same operation.

Edited hole/feature.

1. Select Solid

1. Expand Feature Tree

1. Select Holes

1. Right-mouse-click: Recognize - Automatic (tree-

widget expands with recognized features)

1. Select feature (Hole 9, say)

1. Right-mouse-click: Edit

1. Make changes as required.

Patran Release GuideAutomatic Feature Recognition

4

The propagation controls get passed to the feature recognition API to control the type of recognition. Inother words if you select the Chain option for Blends and do interactive recognition then it will do the


50/68

other words, if you select the Chain option for Blends and do interactive recognition then it will do therecognition and then perform chaining so finally you will get Blend Chains. Each Blend Chain may

be a combination of several individual Blends. To recognize each blend individually you can select theSingle option.

For automatic recognition these propagation control options are not used. For automatic recognitionthese options have been set to default values of Hole:Single, Chamfer:Chain, Blend:Chain.

These options are valid for interactive recognition only and respective values get passed through thesecond argument in the API.

status = ifr_recognize_blends_list(entity_list, propagation, @topology, entity_type, number_of_features)

Recognize Automatic: works with Geometric Entity as Solid only.

Recognize Interactive: works with Geometric Entity as Face or Edge only.

Recognize Automatic does not need any input other that Solid ID in which the features need to berecognized. All other inputs are defaulted. It is available to provide user a convenience only. It willrecognize the features in the whole solid. Recognizing features in the whole solid may not always beuseful as there may actually only be the need of recognizing features in one particular region of the solid.In this case simply select the faces/edges where the need to recognize the features exists and useRecognize Interactive.

Recognize Interactive does not work with Solid geometric entities. Change the Geometric Entityoption to Face or Edge and select the faces or edges in the vicinity where the features are to berecognized. If you select all the faces of solid, this is equivalent to automatic recognition with additionalpropagation controls besides the default values. Edge Geometric Entity is available for holes only.

5Chapter 4: General EnhancementsBatch Image Rendering

4.2 Batch Image Rendering1


51/68

g g

The combined usage of the batch and graphics command line arguments for invoking Patran used to be

mutually exclusive. Now you can generate graphical images in batch mode by using both together toinvoke Patran via a session file (-sfpsession file name) as shown here:

patran -b -graphics -sfp test.ses

Batch mode does not know what the dpi resolution is and uses a default of 100. But you can set this inthe settings.pcl file with graphics_batch_dpi, e.g.,

pref_env_set_real( "graphics_batch_dpi", 92.5 )

This works for JPEG, MPEG, BMP, PNG and TIFF graphics file formats.

1Customer Request (CR) 40421

Patran Release GuideSimManager Integration

6

4.3 SimManager Integration


52/68

Publish and retrieve Patran databases and other related analysis files directly from within Patran with the

SimManager client, now directly accessible from the File pull down menu. Once the server connectionproperties and settings are established users can easily communicate with SimManager. Once logged on,the user may publish, retrieve, and browse as well view connection properties and access the Web Client.

Can retrieve and then opendatabases directly inPatran.

7Chapter 4: General EnhancementsSimManager Integration

The following variables need to be set or are asked to be set during installation in order to communicatewith the SimManager server. For more information on this, the user is directed to the SimManager


53/68

g gdocumentation.

SM_RICH_CLIENT_CONFIG_FILE

SM_RICH_CLIENT_IC_HOST

SM_RICH_CLIENT_IC_PORT

SM_RICH_CLIENT_IC_PROTOCOL http

SM_RICH_CLIENT_IC_WEBCONTEXT SimManager_R3

SM_RICH_CLIENT_ROOT

Client access to a SimManager server via Patran is only supported on Windows machines. For moreinformation on settings these environment variables, please see Patran Environment Variables (p. 48) inthePatran Installation and Operations Guide.

Patran Release GuideSimXpert Integration

8

4.4 SimXpert Integration
http://../ops_manual/ops_print.pdfhttp://../ops_manual/ops_print.pdfhttp://../ops_manual/ops_print.pdfhttp://../ops_manual/ops_print.pdfhttp://../ops_manual/ops_print.pdfhttp://../ops_manual/ops_print.pdf


54/68

SimXpert can be launched from Patran under the File pull down menu or from within the MD NastranPreference. Launching from the File menu only launches SimXpert with no data transfer. Launching fromthe Analysis application will transfer the finite element model to SimXpert. For this capability to beavailable, the user must set the environment variable MSC_SX_HOME to the top level directory of avalid, local installation of SimXpert. If an installation of SimXpert is detected at installation time, thiswill automatically be configured for the user.

9Chapter 4: General EnhancementsMSC Sinda Preference

4.5 MSC Sinda Preference

MSC Si d i th l l i ff i f MSC A h MSC Si d f i


55/68

MSC Sinda is now a new thermal analysis offering from MSC. As such a new MSC Sinda preference isavailable to give access to this state-of-the-art thermal analysis module. MSC Sinda must be installed inorder for the Preference to be able to submit analyses and retrieve results. However, Sinda database canbe created without an MSC Sinda installation. Besides setting up a model for thermal analysis, variousutilities are also available from an additional pull down menu to read in material data from Excelspreadsheets and other capabilities. You are referred to the MSC Sinda Preference User Guide for furtherin formation.

This Preference is only available on Windows. MSC Sinda solves problems using resistance-capacitance

network approach, coupled with fast finite difference numerical methods and including power FORTANprogramming. Very Powerful!

Patran Release GuideLaminate Modeler

10

4.6 Laminate Modeler

Laminate Modeler incorporates a number of enhancements to promote the effective modeling of


56/68

Laminate Modeler incorporates a number of enhancements to promote the effective modeling oflaminated composites structures. These are described below under the headings of the appropriatecommand.

The Laminate Modeler initialization form, which allows the user to begin the Laminate Modeler sessionnow has two new options:

Import Layup File

Available if no mesh exists in the current Patran database. This opens the selected Layup file AND

imports the shell mesh in the Layup file into the the database. This avoids the need to issue the ImportModel Layup File command manually after opening the Layup file.

Save As

Saves the Layup model to the selected Layup file AND updates the current file name. This is convenientwhen investigating multiple configurations.

Create LM_Layup AddWhen creating an analysis model (i.e., generating properties) at the same time as creating or modifyinga LM_Layup, the default laminate orientation method and additional options were used previously. Thismeant that for fine control of the property generation, the user would need to use the separate Create

11Chapter 4: General EnhancementsLaminate Modeler

Laminate LM_Layup command. Now, the user can set detailed options directly on the first form,increasing efficiency and promoting the use of the most appropriate orientation option.


57/68

For many problems, best practice is to use coordinate systems to define both the Reference Directions ofplies, and the orientation of the generated laminate materials. This maximizes correlation between plyand property definition, and means that the coordinate system is written to the analysis input deck anddirectly available to the solver.

Layup Definition Spreadsheet

The Layup spreadsheet allows the definition of the Ply Group and Sequence associated with each LayupPly instance as shown below. This is not used directly within the analysis environment but promotesinteroperability with composites design systems where plies are grouped hierarchically under theseheadings. Transferring a design model from CATIA Composites Design and Laminate Modeler using


12

Simulayt's Composites Link will transfer this information bi-directionally to ensure that designers andanalysts can communicate effectively.


58/68

The symmetry of the current Layup sequence is now reported as a label instead of the previousoptionmenu to emphasis that this is a result of the Layup sequence defined and not an option that can be

set by the user.

Create LM_Layup Laminate

This new command extracts ply and layup definitions stored in the Laminate Materials using global plyidentifiers (GPlyIds). The plies are namedgplyid.Xwhere X is the appropriate GPlyId value. The startpoint is arbitrarily set to the centroid of the element in the ply having the lowest Id, and the applicationdirection is set opposite its normal direction. The ply type is set to a Projected type based on rotation with

respect to the element datum, and the rotation is set to that for the start element. Please note that as theseare necessarily arbitrary assumptions, modifying a ply of this type will reset orientations so that thisshould be avoided.


The global plies are added to the LM_Layup in increasing order of GPlyId. Please note that while thisfollows recommended practice for the use of global ply identifiers, there is no guarantee that the orderon each element will be consistent and so this should be checked carefully.


59/68

on each element will be consistent and so this should be checked carefully.

Create Results Failure Calc

This command has been enhanced to work with results that have already been sorted by MD Nastran onthe basis of global ply identifiers (GPlyIds). The results are assumed to be sorted already if results layerids do not begin at layer 1 OR the results layer ids are not sequential OR the number of elements in aresult increases with results layer id OR an element in a result does not exist in a previous layered result.With this comprehensive checking, it is highly unlikely that sorted results will be identified as unsortedones.

The failure calculation in Laminate Modeler has traditionally supported custom failure criteria using aPCL function. Now, comprehensive support for custom failure criteria is provided by means of Add-Insdeveloped in C++ using Simulayt's Add-In architecture. The Add-Ins are simply placed in a directoryidentified by the environment variable SLTAddinPath, after which the Add-In becomes available forselection by the user as shown below. Both the Allowable values and the Results created are set by theselected criterion and are then respectively input and selected readily by the user.

The flexibility of the new Add-In failure criterion system will allow the creation of high performancefailure criterion able to model multiple failure criteria in a single compound criterion. And, as thecriterion's interface is well defined, these same criteria could be used consistently in other calculationenvironments, such as a spreadsheet for initial calculations.


14

Show LM_Ply Graphics

This command has been enhanced to allow the visualization of draped and flat patterns whereappropriate These are computed on the fly and can prove to be a most effective visualization tool


60/68

appropriate. These are computed on-the-fly and can prove to be a most effective visualization tool,

particularly when the Auto Execute option is used in the ply selection listbox.

Delete LM_Layup Select

As a Laminate Modeler model can only contain a single LM_Layup, the name of an exiting LM_Layupis now displayed in a databox and not a listbox to prevent confusion.

Import Plies FileWhen importing plies from a Layup file or FiberSIM data, the plies from the source file are mapped ontothe destination elements in Patran. If the source and destination elements are too widely separated, themapping is not initialized and it was difficult to identify the faulty element previously. Now, if selectedelements are unmapped, a warning is given and the unmapped elements are placed in a group calledLMImportUnmappedElements so they can be identified easily. This allows quicker identification andresolution of mapping problems.

Mapping was calculated using a line from the centroid of a destination element in the element normaldirection. Now, the option of defining an average normal direction based on the surface normals at eachnode of an element has been added. This can improve mapping where the destination surface containssharp creases as shown below. This is a common situation for frames and spars commonly used in theaerospace industry.


Import Results ESAComp xml

ESAComp is a laminate analysis tool that can generate failure criteria that are written in an xml file. Thisnew command reads the result data from the file and creates a Patran result that can be viewed in the usual


61/68

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 reflectthe requirements of the aerospace industry, such as symmetry, balance, taper ratio and so on. The userselects the element to be verified, a "main" direction (such as the trailing edge of a wing) and thicknessand angle tolerances required for some tests. The required test is then selected and applied. Elements

which fail the selected tests are highlighted in the viewport using the relevant color, and a spreadsheetlisting all failed elements and the test they have failed is displayed. The results of a symmetry check ona vertical tail plane model are shown as an example below.

Patran Release GuideCustomer Requests

16

4.7 Customer Requests

Many customer requests (CRs) were addressed in this release. These consist of defect corrections andh Th f ll i i ifi d f h dd d h


62/68

enhancement request. The following are significant customer requests or defects that were addressed thatmay be of interest to users in addition to those that have already been referenced in previouschapters/sections:

CR # Description

1-68705473 File / Open Recent - Allows you to select from a list of recently accessed database files.The number of files visible is controlled by settings.pcl file environment variable:

pref_env_set_integer("max_num_recent_files",num_files)

q========~==~=.Patran.RecentFiles=~=====K=l=tI======eljbaofsb=~=eljbm^qe=~~I=KKI=C:=~=\=Z=C:\.Patran.RecentFilesK=l=rkfuI===~~=eljb===I=KKI=/home/userK

1-66889951 Preselection Highlighting Entity Offset - A defect was corrected where if a group of nodesand/or elements was erased that caused a fit view to occur (Preferences->Graphics->AutoExtend), then pre-selection highlighting would display nodes offset from their trueposition.

1-64306194 OEFIT OP2 Datablock - A defect was corrected where failure indices from compositefailure analysis were not being processed correctly when reading the OEFIT datablockfrom a Nastran OP2 file.

1-66078121 Long Result Case Names - Result case names that exceeded 80 characters would result in

a PCL traceback if filtered. The character limit has been increased to 256 to avoid this.

1-15765121 $ Allowed in Group Names - Groups with $ symbols in the name now functionproperly when editing Global Subcase Output.

1-16900917 15 Noded CPENTA Results - Results for 15-noded CPENTA elements can now beaccessed via XDB files.

1-19052381 Material Stiffness Matrix Terms - The C44, C55 and C66 terms are now ordered correctlywhen converting 3D Orthotropic materials to 3D Anisotropic for MAT9 entries.

1-19730217 Jobname and Results Case Name Conflict - In cases where an existing jobname is activebut an XDB file is attached with subcases not associated to the active job, the results casespick up the jobname instead of the actual subcase name as defined in the Nastran job. Anewsettings.pcl variable has been implemented to control this.

pref_env_set_integer("RESULTS_TITLE_CHECK_LEVEL",level)

This is an integer value with the following meanings:

17Chapter 4: General EnhancementsCustomer Requests

0 (or not set at all) = current functionality is maintained

CR # Description


63/68

1 = If the jobname and the XDB filename differ, then ignore the jobname when creating theresult case titles. This would be just like the described work around of clearing the jobnamelistbox and attaching to an XDB file. Thus it will not append the jobname to the beginningof the results case title. No messaging it just does it.

2 = If the jobname and the XDB filename differ, then put up a message notifying the useras such and asking if he wishes to continue with the attachment. It is either a Yes or No. IfYes, then the attachment occurs. If no, then the attachment is abandoned.

3 = If the jobname and the XDB filename differ, then put up warning message with a simpleacknowledgement OK button. The attachment will still occur regardless.

In all cases, if the jobname and the XDB filename are the same, then the functionalityremains the same.

1-19960526 DB Import Changes Poissons Ratio Value - This corrected an incorrect rounding ofmaterial data occurring occasionally on import into another database, which slightly

changing the property value.1-23657326 Some Result Layers missing from XDB Attachment - XDB attachments were only

recognizing layers of the first results cases even though subsequent result cases had morelayers.

28974 Deletion of Multiple Load Cases - The ability to delete multiple load cases in one operationhas been implemented.

1-50872269 TET10 Stress Data using GAUSS on PSOLID - Incorrect fringe plots have been corrected

when the GAUSS field on the PSOLID entry is activated during a Nastran run and resultsaccessed from Patran via the XDB file.

1-32732851 MBOLTUS Import Support - MBOLTUS entries in the Nastran input deck are nowimported as Overclosure MPCs

1-52553651 Residual Vector Computation - In the Nastran preference, on the solution parameters form,the Residual Vector Computation toggle now writes RESVEC=YES or RESVEC=NO ifthe parameter is present in the database for that job no matter what. Previously only

RESVEC=NO was being written because RESVEC=YES is the default for most SOLsequences. But for SOL 103, no RESVEC entry defaults into RESVEC=COMPONENTwhere the desired default is RESVEC=YES or BOTH. So now RESVEC=YES is writtenif the toggle is ON.

1-64846211 Large Listbox Capability - There are number of places in the Element Properties,LoadsBCs, Materials, and Fields applications as well as Groups and Regions where thelarge listbox capability has been enabled without having to invoke Patran with the -loption for large listbox capability. A small icon appears next to the listbox that can be

expanded to a large listbox.


18

1-18201068 PLOAD4 Import - Importing Nastran files with PLOAD4 pressures that vary spatially nowimport correctly and a proper spatial field is created for each load set.

CR # Description


64/68

import correctly and a proper spatial field is created for each load set.

1-40919043 Significant Digit Control - More control for writing significant digits is given when writingNastran input decks. Individual control is now given under the Translation Parameter formfor grids, coordinate frames, MPCs, LBCs, materials and properties.

1-45336797 Mesh in Wrong Location after Surface Transformation - After transforming parasolidsurfaces to new locations using Group/Transform, subsequent meshes were being placed inthe wrong physical location using the Hybrid or Sheet Body meshers.

1-40918941 MPCs & Tools/List/Create - The ability to create lists of nodes associated to MPCs has

been implemented under the Tools/List/Create utility.

1-67076271 Fastener Results in Multiple XDB files - An issue where fastener results were notaccessible if multiple XDB files were attached has been corrected.

1-70170481 Significant Digits in Envelope Plots - It is now possible to control the number of significantdigits in envelope plots under the Tools / MSC.Explore utility.

1-19671064 SPOINT Import - SPOINTS associated with beam definitions of warping degrees-of-freedom from the Nastran input deck are now imported to retains those definitions in the

beam element properties.

1-18657123 Nodes/Grid Projection in Radial Direction - Nodes and grids can now be projected onto asurface in the radial direction when a cylindrical system is referenced. Spherical systemsare also supported and all other component directions.

1-9146004 Nodes Left Behind After Group/Transform - Nodes referenced as GO points for definingbeam orientations were not transformed during a Group/Transform operation. Now ifnodes in a group are referenced in properties, fields or MPC's, then during the transform

operation such nodes are copied.

1-25240879 SOL 600 TEMPD Support - Nastran case control TEMP(LOAD), TEMP(INIT), and bulkdata TEMPD entries now supported for SOL 600.

1-59220230 Torsional Constant J ofCross Cross-sections - The calculation of the torsional constant Jof a cross-type cross-section does not have a closed form solution. The beam section librarynow 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.1-17613229 Turn Spectrum Off with Constant Contours - When creating a contour plot, the user can set

the attributes to 'Constant', displaying all contour lines in a single color. Other results toolsautomatically turn off the spectrum and hide the option from the user, but the contour leavesthe spectrum in place with its varying colors. The user no longer must manually turn off thespectrum to see a correct plot.

19Chapter 4: General EnhancementsCustomer Requests

1-70358907 Automatic Spectrum Update - When a new spectrum is selected from theDisplay/Spectrums form, the spectrum is applied immediately without having to recreate

CR # Description


65/68

p y p , p pp y g

the results plot.

1-43797130 Imprinted Parasolid Geometry - It is now possible to mesh imprinted Parasolid geometry.


20


66/68

jp`Kc~=n=p~=d

I n dex



67/68

AACIS, 6

AIX, 5

C

CAD Access, 2, 6InterOp R16, 2

Parasolid 17, 2

CATIA V4, 6

CATIA V5, 6

EEase-of-use enhancements

Load/BCs, 5Enhancements, 2

CAD Access, 2

InterOp R16, 2

Parasolid 17, 2

H

Hardware, 5Highlights, 2

HP

Supported OS levels, 5

IIBM, 5

I-DEAS, 6

Intel, 5

KKey Highlights, 2

LLINUX, 5

Load/BCs enhancements, 5

OOperating systems, supported, 5

PParasolid, 6

Platforms, supported, 5Pro/ENGINEER, 6

RRed Hat, 5

S

Solaris, 5Sun, 5

Supported OS levels, 5

Supported platforms, 5

SuSE, 5

UUnigraphics, 6

WWildfire, 6

Windows, 5

m~

~

=o

~

=

d


26


68/68

Download - Patran 2008r1 Doc Release

Top Related