patran 2020 · 2020. 9. 23. · patran release guide supported cad access 6 12. take care as there...

30
Patran 2020 Release Guide

Upload: others

Post on 25-Jan-2021

8 views

Category:

Documents


1 download

TRANSCRIPT

  • Patran 2020

    Release Guide

  • Worldwide Webwww.mscsoftware.com

    Supporthttp://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx

    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 2020 MSC Software Corporation. 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.This software may contain certain third-party software that is protected by copyright and licensed from MSC Software suppliers. Additional terms and conditions and/or notices may apply for certain third party software. Such additional third party software terms and conditions and/or notices may be set forth in documentation and/or at http://www.mscsoftware.com/thirdpartysoftware (or successor website designated by MSC from time to time). The MSC Software Logo, MSC, MSC Nastran, Marc, Patran, Dytran, and Laminate Modeler are trademarks or registered trademarks of MSC Software Corporation in the United States and/or other countries. Hexagon and the Hexagon logo are trademarks or registered trademarks of Hexagon AB and/or its subsidiaries.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. FLEXlm and FlexNet Publisher are trademarks or registered trademarks of Flexera Software. PostScript is a registered trademark of Adobe Systems, Inc. PTC 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 Siemens Product Lifecycle Management, Inc. All other brand names, product names or trademarks belong to their respective owners. Revision 0. September 14, 2020

    P3:V2020:Z:Z:Z:DC-REL-PDF

    Corporate Europe, Middle East, AfricaMSC Software Corporation MSC Software GmbH4675 MacArthur Court, Suite 900 Am Moosfeld 13Newport Beach, CA 92660 81829 Munich, GermanyTelephone: (714) 540-8900 Telephone: (49) 89 431 98 70Toll Free Number: 1 855 672 7638 Email: [email protected]: [email protected]

    Japan Asia-PacificMSC Software Japan Ltd. MSC Software (S) Pte. Ltd.Shinjuku First West 8F 100 Beach Road23-7 Nishi Shinjuku #16-05 Shaw Tower1-Chome, Shinjuku-Ku Singapore 189702Tokyo 160-0023, JAPAN Telephone: 65-6272-0082Telephone: (81) (3)-6911-1200 Email: [email protected]: [email protected]

    mailto:[email protected]:[email protected]:[email protected]:[email protected]://www.mscsoftware.com/thirdpartysoftware

  • Documentation FeedbackAt MSC Software, we strive to produce the highest quality documentation and welcome your feedback. If you have comments or suggestions about our documentation, please write to us at [email protected].

    Please include the following information with your feedback:

    Document name Release/Version number Chapter/Section name Topic title (for Online Help) Brief description of the content (for example, incomplete/incorrect information, grammatical errors, information

    that requires clarification or more details and so on.) Your suggestions for correcting/improving documentation

    You may also provide your feedback about MSC Software documentation by taking a short 5-minute survey at:

    http://msc-documentation.questionpro.com.

    Note: The above mentioned e-mail address is only for providing documentation specific feedback. If you have any technical problems, issues, or queries, please contact Technical Support.

    https://simcompanion.mscsoftware.com/infocenter/index?page=content&id=KB8019304https://simcompanion.mscsoftware.com/infocenter/index?page=content&id=KB8019304https://simcompanion.mscsoftware.com/infocenter/index?page=content&id=KB8019304mailto:[email protected]://msc-documentation.questionpro.com

  • Con t en t sPatran Release Guide

    Contents

    1 Patran 2020 at a GlanceKey Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

    General Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Supported OS/Hardware Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

    Supported CAD Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Known limitations in current release: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

    Supported Analysis Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

    Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

    2 General EnhancementsNastran Embedded Fatigue (NEF) Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

    Nastran Dynamic Analysis Using Channel Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

    Enhanced HDF5 Results Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

    MSC Fatigue Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

    Index

  • Patran Release Guidevi

  • Chapter 1: Patran 2020 at a Glance. MSC Nastran Implicit Nonlinear (SOL 600) User’s GuidePatran Release Guide

    1 Patran 2020 at a Glance

    Key Highlights 2

    Supported OS/Hardware Platforms 3

    Supported CAD Access 5

    Supported Analysis Preferences 7

    Technical Support 8

  • Patran Release GuideKey Highlights

    2

    Key Highlights

    General EnhancementsThe following general enhancements have been implemented in the Patran 2020 version. Please see Chapter 2 for details.

    Nastran Embedded Fatigue (NEF) Support, 11

    Nastran Dynamic Analysis Using Channel Files, 14

    Enhanced HDF5 Results Support, 17

    MSC Fatigue Enhancements, 22

  • 3Chapter 1: Patran 2020 at a GlanceSupported OS/Hardware Platforms

    Supported OS/Hardware Platforms

    For a complete description of these configurations, see Required Hardware & Software Configurations (Ch. 5) in the Patran Installation and Operations Guide.

    Vendor Description

    Windows For information on Operating Systems and Hardware support, please see Microsoft Windows Requirements (p. 67) in the Patran Installation and Operations Guide

    Linux For information on Operating Systems and Hardware support, please see Linux Requirements (p. 83) in the Patran Installation and Operations Guide.

  • Patran Release GuideSupported OS/Hardware Platforms

    4

    Important: 1. The default Patran installation directory on Windows has been changedFrom:

    C:\MSC.Software\Patran_x64\20xx

    To:

    Possible issues one may encounter when using the default installation path:

    P3_TRANS.INI file in P3_HOME: Editing or modifying any file located in C:\Program Files\ requires your application to be run as Administrator. If you are already logged in as Administrator, you can start Notepad or any other text editor with the “Run as Administrator” option. This allows you to browse and open P3_TRANS.INI for editing. Notepad++ automatically understands this requirement and gives an option to start another instance of the application as Administrator. For other applications like Notepad, you must decide to start the application with “Run as Administrator” beforehand by using the Right Mouse Button on the application’s icon to select this run option. Do not start the editor with a double click of the Left Mouse Button. This is a security feature of Windows to prevent accidental or unauthorized changes to your installation.

    During installation, the Configuration Tool to edit the P3_TRANS.INI file may be used. But once the installation is done, the P3_TRANS.INI file cannot be edited using the Configuration Tool (i.e. Configuration Utility). A message shown as 'SELECTED FILE IS READ-ONLY' will be displayed.

    2. The FLEXlm license server has been upgraded to Helium.

    3. When Nastran 2020 Service Pack 1 and Marc 2020 are installed in their default installation directory locations (e.g., ), Analysis Manager does not work in combination with Patran on the Windows operating system. If you need to run Analysis Manager, it is required to install Patran, Nastran, and/or Marc in directories names that do not contain a space.

    4. The Patran help system does not support Mozilla Firefox version 68 or higher. Please use Mozilla Firefox version 67 or lower.

    5. Patran 2020 complies with IPv6 specification with the following exception:

    Analysis Manager (expected to be compliant in a subsequent release)6. To meet user expectations and maintain Patran current with the latest technology, the

    following feature of Patran 2020 may not be available in future releases. Please plan accordingly.

    Express Neutral Files import/export

  • 5Chapter 1: Patran 2020 at a GlanceSupported CAD Access

    Supported CAD AccessThe following CAD systems are supported using the new CAD import methods.

    Known limitations in current release:1. Occasionally closed surfaces are not converted to solids on import of IGES, ACIS, and CATIA V4.

    Instead of solids, surfaces are imported.

    2. There is no support for import of nodes/elements from IGES files using the “Import to Parasolid” toggle.

    3. Export of IGES files may result in loss of some surfaces/solids - not all entities are exported.

    4. Some IGES and Pro/ENGINEER parts import unexpected surfaces.

    5. Some IGES, STEP, and ACIS parts import a broken or incomplete model.

    6. The global element length (GEL) that gets set and used during import is different than previously supported import methods.

    7. Certain files may import using the default import method but may not import using other (non-default) methods or vice-versa (using the “Import to Parasolid” toggle).

    8. Editing/updating features using automatic feature recognition leads to different geometry as compared to previously supported import methods.

    9. Mid-surfaces are different compared to previously supported import methods.

    10. The naming of groups is different than previous supported import methods for all CAD geometry types.

    11. Unigraphics (UG) parts containing defined features do not recognize features like the deprecated UG import in Patran.

    Windows Linux

    ACIS Up to R27 Up to R27

    CATIA V4 All 4.xx All 4.xx

    CATIA V5 R10 to R29 R10 to R29

    IGES 3, 5, 5.2, 5.3 3, 5, 5.2, 5.3

    Pro/ENGINEER / Creo (.prt/.asm) WF 4, WF5, to Creo 6 WF 4, WF5, to Creo 6

    SolidWorks Up to 2019 Up to 2019

    STEP 203, 209, 214, 242 203, 209, 214, 242

    Unigraphics NX 5.0, 6.0, 7.0, 7.5, 8.0, 9.0, 10, 11, 12, 1847

    NX 5.0, 6.0, 7.0, 7.5, 8.0. 9.0, 10, 11, 12, 1847

    Parasolid 30.1 30.1

  • Patran Release GuideSupported CAD Access

    6

    12. Take care as there may be a mismatch of the native CAD geometry units and Patran model units, with no informative message.

    13. Exported files that are subsequently imported back into Patran may not contain the same exact entities as sometimes solids are imported as surfaces.

    14. CATIA V5 import notes:

    • Hidden entities are imported by default. Turn OFF the "Import Attributes" option on the Catia Options form if this is not desired.

    • Import of hidden entities may make the model appear "zoomed out."

    • Only Entities from the Master Workspace are imported.

    • Planes are ignored and not imported.

    • Occasionally axes import as curves.

  • 7Chapter 1: Patran 2020 at a GlanceSupported Analysis Preferences

    Supported Analysis Preferences

    Solver Platforms Solver Version

    MSC Nastran*†

    *MSC Nastran has discontinued support of i4 databases. All output results produced by MSC Nastran 2017 or later are only available as i8 databases (DBALL/MASTER). Support for result access via DBALL/MASTER file has been discontinued. Result access through Output2 (PARAM,POST,1), XDB, and HDF5 should be used as an alternative with HDF5 as the standard default.

    †MSC Nastran 2017 and higher does not convert INTEGER input to REAL if entered as an integer in a real input field. Instead, a fatal message is issued. To bypass this, specify system cell NASTRAN SYSTEM(444)=9 as first line in the FMS section. It is recommended that users import input files that run through MSC Nastran with no fatal errors. When importing files with this system cell, no fatal messages are issued due to integer to real conversion. In general, when importing detects a FATAL error message, Patran issues this message:Problem detected while importing the MSC.Nastran input file using

    SOL nifimp_v22

    All 2020 Service Pack 1

    Marc All 2020

    Dytran All 2019 Service Pack 1

    Flightloads All 2020

    Thermal All 2020

    Fatigue All 2020

    MSC Sinda All 2017.1

    LS-DYNA3D All 971

    PAMCRASH All 1995 / 1997

    Abaqus(.odb) All 2017

    ANSYS‡

    ‡Results access is enhanced to ANSYS 19.2 (results import is frozen at ANSYS 8.1).

    All 19.2

  • Patran Release GuideTechnical Support

    8

    Technical SupportFor technical support phone numbers and contact information, please visit: http://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx

    Support Center (http://simcompanion.mscsoftware.com)The Support Center provides technical articles, frequently asked questions and documentation in a single location.

    Online Resources (www.mscsoftware.com)MSC Software corporate site with information on the latest events, products and services for the CAD/CAE/CAM marketplace.

    http://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspxhttp://simcompanion.mscsoftware.comwww.mscsoftware.com

  • 9Chapter 1: Patran 2020 at a GlanceTechnical Support

  • Chapter 2: General Enhancements. MSC Nastran Implicit Nonlinear (SOL 600) User’s GuidePatran Release Guide

    2 General Enhancements

    Nastran Embedded Fatigue (NEF) Support 11

    Nastran Dynamic Analysis Using Channel Files 14

    Enhanced HDF5 Results Support 17

    MSC Fatigue Enhancements 22

  • 11Chapter 2: General EnhancementsNastran Embedded Fatigue (NEF) Support

    Nastran Embedded Fatigue (NEF) SupportMSC Nastran 2020 has implement support for the following new features for fatigue analysis. Listed here are the actual Nastran entries and new field or case control values.

    FTGPARM NANGLE - this is the ability of a fatigue analysis that has requested a critical plane analysis to define the number of angles in the plane to compute the principals and determine fatigue life. The default is 36 angles, but can be defined from anywhere between 10 to 360 angles. In actuality, only half the angles are computed since the principals are the same 180 degrees opposite any computed angle.

    FTGDEF NENTS - this is the ability to designate how many entities to return from the fatigue analysis based on either the most damaging entities or the entities with the greatest stress ranges.

    FATIGUE(STROUT=) - this is the ability to request additional output associated with a fatigue analysis, specifically the input and out output stresses or strains used or computed by the fatigue analysis at only the locations designated or returned by the fatigue analysis. See Enhanced HDF5 Results Support, 17 for details of these specific output requests.

    MSC Patran 2020 now supports these features in the following ways:

    Set the number of angles for critical plane analysis:

    • Enter the Analysis application for MSC Nastran preference

    • Set the Solution Type for to either LINEAR STATIC (SOL 101), NORMAL MODES (SOL 103) or TRANSIENT RESPONSE (SOL112) with Formulation: Modal

    • Open the Solution Parameters Form

    • Open the Fatigue Parameters Form

    • Set the Stress Combination to Critical Plane

    • Set the # of Angles to the desired setting

    The number of angles can be set to any value that divides evenly into 360 from 10 to 360. This can be done with the slider bar or typing in a value in the corresponding data box. On translation, a FTGPARM NANGLE entry is written to the Nastran input file.

    Set the number of entities to retain from the fatigue analysis:

    • Again from the Analysis application, Solution Parameter form, Fatigue Parameter form for SOL 101, 103, or 112

    • Set the Number of Entities to Retain

    • Set whether the criterion is Based on: Damage or Range

    The number of entities to retain is written to the FTGDEF NENTS field on translation to a Nastran input file. This can be used in conjunction with the Top Stress Percentage and Top Damage Percentage filters. If using these two settings result in less than the number of retained entities requested, then only those entities are returned.

  • Patran Release GuideNastran Embedded Fatigue (NEF) Support

    12

    Figure showing how to set the number of angles and number of retained entities:

  • 13Chapter 2: General EnhancementsNastran Embedded Fatigue (NEF) Support

    Request various stress or strain outputs associated with the fatigue analysis:

    • Again from the Analysis application

    • Open the Subcases form

    • Open the Output Requests form

    • Select Fatigue Life as an Output Request

    • Set the desired Fatigue Stress/Strain Requests (STROUT)

    Figure showing how to set the stress or strain output requests from a fatigue analysis:

    Import of Nastran input files that contain FTGDEF NENTS, FTGPARM NANGLE, and FATIGUE(STROUT=) case control is supported and for the imported input file a job is created and sets the various widgets for the job as shown in the above figures.

  • Patran Release GuideNastran Dynamic Analysis Using Channel Files

    14

    Nastran Dynamic Analysis Using Channel FilesMSC Nastran 2020 has implement support for the following new feature for defining or applying dynamic loads in a modal transient analysis (SOL 112):

    Typically dynamic loads are set up in Nastran with the time variations defined via a TABLED1 entry. The TABLED1 entry can be very long and time consuming to create. In many cases the dynamic loading is from measurements in the field. Certain industry standard files are used to store measured and/or computed loading and are referred to here as channel files. These files are sometimes referred to as RPC files or multi-channel files. They are multi-channel because they can contain loading input at various locations from a test specimen that act simultaneously. These files typically have .rpc, .rsp, .dac, and .s3t file extensions.

    It is a chore to convert data from these file into corresponding TABLED1 entries that can be used in Nastran. The TABLRPC entry eases this burden by allowing the user to associate one of these files and a channel from the designated file as a dynamic load in place of a TABLED1 entry. Internally Nastran converts the channel file data to TABLED1 entiries when it sees a TABLRPC entry of the same ID. Practically speaking, any Nastran entity or field that references a TABLED1 ID (TID) should actually be able to use a TABLRPC entry, thus it is not limited to dynamic analysis, but it has been implement specifically for SOL 112 dynamic analysis.

    TID - a unique table ID; a corresponding TABLED1 of the same ID is produced by Nastran XAXIS/YAXIS - this defines the x and y-axes as LINEAR or LOGarithmic - same as a TABLED1

    entry UID - the ID of a UDNAME entry that specifies the channel file TYPE - RPC, DAC, or S3T for .rsp/.rpc, .dac, or .s3t file designation (RPC is default) CHAN - channel number of the channel file to extract (uses first channel if left blank) TOTIM - total time of the signal used to create the x-value time points - if left blank the time points

    from the actual channel file are used PUNCH - set to YES to place the TABLED1 entries produced in the punch file xii,xji - these are value ranges to extract or exclude from the internally produced TABLED1 - to

    exclude, set the UID to a negative number

    MSC Patran 2020 now supports this feature in the following way:

    Open the Load Case application Set the Action to Create or Modify Select the Load Case of interest (or create a new one) Set it to Time Dependent - press Apply Open the Loads/BCs application Set the Object to the load type of interest, i.e., Force

    1 2 3 4 5 6 7 8 9 10TABLRPC TID XAXIS YAXIS UID TYPE CHAN TOTIM PUNCH

    xi1 xj1 xi2 xj2 xi3 xj3 -etc.- "ENDT "

  • 15Chapter 2: General EnhancementsNastran Dynamic Analysis Using Channel Files

    Make sure the Current Load Case is the time dependent load case you created Open the Input Data form Enter some non-zero values as you normally would for a typical LBC Turn on the Use Channel File toggle Enter a Channel # or leave blank to use first channel Put focus in the Time/Freq. Dependence data box Select the Channel File from the list box

    At this point the data box fills with a coded string that looks like: c:: where c: designates that this is a channel file, is the designated channel number, and is the selected file name. When you press Apply, a general field is created with this information. On restoration of an LBC, the field is read and the data box containing this information is once again filled with the select channel file information.

    On translation a TABLRPC entry is created along with its corresponding UDNAME entry to designate the channel file, channel number, and file type.

    Limitation:

    • The channel files must be located in the Patran working directory

    • The XAXIS/YAXIS setting is always set to LINEAR (default)

    • If you wish to produce the TABLED1 entries, designate a negative channel number - this triggers the translation to write PUNCH=YES

    • It is not possible to set the xii,xij y-values ranges for inclusion or exclusion when creating the TABLED1

    For the unsupported features of TABLRPC, the user must intercept the input file before submission to Nastran and edit the input file with the appropriate settings.

  • Patran Release GuideNastran Dynamic Analysis Using Channel Files

    16

    Figure shows mechanism to use a channel file for dynamic loading.

    On import of a Nastran input deck with TABLRPC entries, one can expect the LBC to be created with the dynamic, time dependent loading restored in this manner:

    If only the channel file, channel number, and file type are designated in the TABLRPC entry, then a general field is produced as explained above - a circle test of import/export works in this case only. The channel file name cannot have a path designated.

    If any of the unsupported fields of the TABLRPC are present or the file name has a path, then the circle test will not pass. However, the equivalent time-dependent field is created from the internally created TABLED1 entry and associated to the LBC. This is a convenient mechanism if one wishes to actually have the time dependent data (as a non-spatial field) in Patran. Any inclusions or exclusions of the channel file data are also reflected in the imported non-spatial field.

  • 17Chapter 2: General EnhancementsEnhanced HDF5 Results Support

    Enhanced HDF5 Results SupportA number of new results are available from the HDF5 database file that can be requested from an MSC Nastran run. Additional results that can now be accessed from Patran include:

    Nastran Embedded Fatigue (NEF) stress output requests. Note that for a combination of output requests, the designated code is additive, e.g. STROUT=3 is STROUT=1+2. For all of these requests, the output entities are only those determined, designated, and returned or filtered by the fatigue analysis.

    • FATIGUE(STROUT=1) Case Control - this request outputs the actual stress or strain tensor (physical or modal) that is passed to the fatigue analysis. This is comparable to a STRESS or STRAIN output request and is identical if the stress recover parameters are the same.

    • FATIGUE(STROUT=2) Case Control - this request outputs the maximum stress or strain range from the scalar stress or strain response history computed by the fatigue analysis. If the stress combination requested is a critical plane analysis, the output is a vector, at the critical angle, transformed into the Patran global coordinate system (Nastran basic system) for elemental results or in the defined surface system for grid point stresses/strains. For other stress/strain combinations, such as von Mises or absolute maximum principal, the output is scalar (meaning the y- and z-direction are zero and only x-direction contains the response).

    • FATIGUE(STROUT=4) Case Control - this request outputs the actual scalar stress or strain response history computed by the fatigue analysis, which is used to rainflow cycle count and ultimately compute damage. If the fatigue analysis is a critical plane analysis, the scalar response is that from the critical angle only.

    • FATIGUE(STROUT=8) Case Control -this request outputs the actual stress or strain tensor transient responses at the locations requested by the fatigue analysis for SOL 112. This is comparable to a STRESS or STRAIN output request and is identical if the stress recover parameters are the same.

    :

    Primary Name

    Secondary Name Result Type

    Associated Data Block

    Patran Output Request Nastran Output Request

    Stress/Strain Tensor

    Screened Tensor OES1FSOES1MS

    Fatigue Life w/ Tensor Input

    FATIGUE(STROUT=1)

    Stress/Strain Range Vector OEFTG Fatigue Life w/ Max Range Vector Output

    FATIGUE(STROUT=2)

    Response :

    Scalar OEFTGRH Fatigue Life w/ Combined Response History

    FATIGUE(STROUT=4)

    Stress/Strain Tensor

    Screened Tensor OES1FS Fatigue Life w/ Tensor Response History

    FATIGUE(STROUT=8)

  • Patran Release GuideEnhanced HDF5 Results Support

    18

    This is a plot of 2nd-mode modal stress contribution to a fatigue analysis using modal transient (SOL 112) solution. This plot is comparable to a STRESS output request if all stress recovery parameters are the same. This plot is of von Mises for visualization; all six tensor components for all modes are passed to the fatigue analysis and can be visualized with STROUT=1. For a SOL 101 analysis, these are the physical stresses for each SUBCASE. For SOL 112 they are the modal stresses for each mode. The result type name is Screened because the result set only contains the elements analyzed and returned by the fatigue analysis. This is simply a mechanism to return stress results at only the locations of interest based on the fatigue analysis results and to verify the stress input to the fatigue analysis.

  • 19Chapter 2: General EnhancementsEnhanced HDF5 Results Support

    These are plots of the maximum stress range vector determined by a critical plane analysis using STROUT=2 from a fatigue analysis. Vectors are plotted in the Patran global (Nastran basic) system for element center and element nodal results. For grid point stresses, the vectors are in the designated surface system (Patran global or Nastran basic system by default). These types of plots can be useful in determining where and in which direction strain gauges can or should be applied for testing purposes. The maximum stress range is determined from the scalar response history computed by the fatigue analysis at each entity and for each angle in the case of critical plane analysis.

  • Patran Release GuideEnhanced HDF5 Results Support

    20

    This plot shows the fatigue life of a duty cycle (multi-event) analysis and the actual scalar response history for one of the events at the most critical location from which damage is computed after rainflow cycle counting. Damage from each event is summed to compute the total damage as shown in the plot. The response histories are available for plotting when STROUT=4 is selected. The number of entities should be limited when requesting scalar response histories because this can/will produce a lot of data.

  • 21Chapter 2: General EnhancementsEnhanced HDF5 Results Support

    Finally, this is a plot of transient stress tensor (reduced to von Mises) from a modal transient (SOL 112) solution at the critical location. This plot is comparable to a STRESS output request if all stress recovery parameters are the same. The result type name is Screened because the result set only contains the elements analyzed and returned by the fatigue analysis. This is simply a mechanism to recover the stresses only at the locations of interest based on the fatigue analysis results.

  • Patran Release GuideMSC Fatigue Enhancements

    22

    MSC Fatigue EnhancementsThe MSC Fatigue 2020 release includes an update of the third party code libraries. This update contains the following enhancements:

    Dependency on Python is removed for material curve plotting, supported for standard materials. MSC Fatigue 2020 in the vibration load provider ComplexAlgorithm=Exact was made the default

    option instead of ComplexAlgorithm= Fast. This improves the result accuracy of vibration fatigue compared to previous versions.

    Additionally, the following issues have been fixed in MSC Fatigue 2020:

    SN analysis (SN analysis with certain settings results in a software termination). Critical SineOnRandom issue. Critical Multi PSD vibration issues.

  • MSC.Fatigue Quick Start Guide

    I n d e xPatran Release Guide

    Index

    AAbaqus, 7ACIS, 5ANSYS, 7

    CCAD Access, 5CATIA, 5channel files, 14critical plane, 11

    DDAC files, 14DBALL, 7dynamic analysis, 14Dytran, 7

    Eenhancements, 2

    Ffatigue, 7, 11, 22Flightloads, 7FTGDEF, 11FTGPARM, 11

    HHardware, 3HDF5, 7HDF5 Support, 17highlights, 2

    IIGES, 5

    Kkey highlights, 2

    Llimitations, 5LS- DYNA3D, 7

    MMarc, 7MASTER, 7MSC Fatigue, 7, 22multi-channel files, 14

    NNastran, 7, 11NEF, 11

    OOperating systems, supported, 3output requests, 13Output2, 7

    PPAMCRASH, 7Parasolid, 5Pro/ENGINEER, 5Punch file, 15

    Rresults, 13, 17RPC files, 14

    SS3T files, 14Sinda, 7Solid Works, 5STEP, 5STROUT, 13, 17Supported OS levels/Hardware Platforms, 3

  • Patran Release Guide

    24

    TTABLED1, 14TABLRPC, 14Thermal, 7

    UUnigraphics, 5

    XXDB, 7

    ContentsChapter 1: Patran 2020 at a GlanceKey HighlightsGeneral Enhancements

    Supported OS/Hardware PlatformsSupported CAD AccessKnown limitations in current release:

    Supported Analysis PreferencesTechnical Support

    Chapter 2: General EnhancementsNastran Embedded Fatigue (NEF) SupportNastran Dynamic Analysis Using Channel FilesEnhanced HDF5 Results SupportMSC Fatigue Enhancements