MSC Nastran 2021 What's
Total Page:16
File Type:pdf, Size:1020Kb
MSC Nastran 2021 What’s New Al Robertson MSC Nastran Product Manager 1 | hexagonmi.com | mscsoftware.com Introduction and Agenda 2 | hexagonmi.com | mscsoftware.com Upcoming MSC Nastran Releases Timeline 2020 2021 Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2021 2021.1 2021.2 2021.3 2021.4 • Quarterly release cadence • Faster response to customer requests, new capabilities and error fixes • Change of release numbering • For greater simplicity and clarity 3 | hexagonmi.com | mscsoftware.com Feature Deprecation List • Notice of features to be removed from MSC Nastran in 2020: • In an effort to streamline the MSC Nastran program and simplify ongoing maintenance activity, some obsolete capabilities have been identified and tagged for removal in a future release of the program in 2021 and 2022, allowing for a reasonable notice period. Please review the list of features marked for deprecation below to ensure that there will be no disruption to your use of MSC Nastran. If you see a feature that you currently use and do not wish to lose, contact MSC Technical Support to report it. • Features tagged for removal: • P-elements • SOL 600 nonlinear solution sequence – migration plan through 2021 • Unstructured one- and two-digit solution sequences (e.g. SOL 3, SOL 24) • SOL 190 (DBTRANS) • TAUCS solver • MSGMESH • Obsolete DMAP modules • SSSALTERS 4 | hexagonmi.com | mscsoftware.com MSC Nastran Documentation 5 | hexagonmi.com | mscsoftware.com MSC Nastran 2020 Internal Webinar Agenda Introduction Dynamics Grid Point Forces in Frequency Response Rigid Elements TREF PEM Enhancements PEM Parallel Solution CDTire/NVH Linear Tire Model Coupled Modes for External Superelements Bent Rotor Modeling in Rotordynamics Fatigue CAEfatigue available in MSC Nastran Nonlinear SOL 400 Brake Squeal Enhancements Enhanced Segment to Segment Contact Settings ESE and EKE Output in SOL 400 Linear Perturbation Analysis HPC MUMPS Solver for SOL 101 Results Eigenvector Output with Lossy Compression SOL 700 DMP Support for Langrangian Solver 6 | hexagonmi.com | mscsoftware.com Dynamics 7 | hexagonmi.com | mscsoftware.com GPFORCE for Frequency Response Analysis 8 | hexagonmi.com | mscsoftware.com GPFORCE for Frequency Response Analysis Overview Introduction • Extended GPFORCE options for explicit types of dynamic force output Benefits • Important frequency dependent element data recovery feature • Element force/stress recovery only performed at Master Frequencies for frequency dependent elements • Thermal loading is correctly accounted for Use Case • Load path analysis of structures – new for frequency response analysis • Aerospace customer request • Also serves defense, transportation and security markets 9 | hexagonmi.com | mscsoftware.com GPFORCE for Frequency Response Analysis Usage • ALLDLDS outputs everything – elastic, inertia, damping forces • Implemented in SOL108, SOL111 or ANALYSIS=DFREQ or MFREQ for SOL 200 and linear SOL 400 • In general, for frequency response, the “*totals*“rows will not be zero, except when ALLDLDS is chosen • PARAM, BUSHNM, YES (default) required for GPFORCE. • GPFORCE is inherently a SORT1 output, SORT2 is suppressed 10 | hexagonmi.com | mscsoftware.com GPFORCE for Frequency Response Analysis Example Model: (..\tpl\gpf_frq\gpf108_wing.dat) GPFORCE(ALLDLDS)=2 GPFORCE=ALL option, large Grid IDs ≥ 101000001 are from CWELD or CFAST or CSEAM elements SWLDPRM, PRTSW,n: To see connector grids SET 2 = 27188,20273,14783,113645,101002153,101002154 11 | hexagonmi.com | mscsoftware.com GPFORCE for Frequency Response Analysis Example Output .f06 Elastic forces Damping forces (G) Structural damping forces Inertia forces (G) … Zero total (ALLDLDS requested) 12 | hexagonmi.com | mscsoftware.com GPFORCE for Frequency Response Analysis Example Output HDF5 – always stores in Real/Imaginary format Grid ID Element ID Source 13 | hexagonmi.com | mscsoftware.com TREF Support for Rigid Elements 14 | hexagonmi.com | mscsoftware.com TREF Support for Rigid Elements Overview Introduction • TREF support for rigid elements using TEMP(MATE) or TREF on elements (previously was zero) Benefits • TREF support removes a previous limitation (unwanted constraint) with modeling rigid elements in a temperature field • Now supported in all linear solutions sequences that allow thermal effects Use Case • In linear analysis with material dependency, rigid elements now reflect the local temperature field 15 | hexagonmi.com | mscsoftware.com TREF Support for Rigid Elements Usage 16 | hexagonmi.com | mscsoftware.com TREF Support for Rigid Elements Usage 17 | hexagonmi.com | mscsoftware.com TREF Support for Rigid Elements Usage 18 | hexagonmi.com | mscsoftware.com Porous Elastic Material Enhancements • Solid Shell using 3D Elements • Perforated Shell Elements • Simplified Biot Porous Material Models • Multiple Coupling Specifics for a Trim Component • TRMC Processing Scenarios • Rigid Elements for TRMC 19 | hexagonmi.com | mscsoftware.com Solid Shell Using 3D Elements 20 | hexagonmi.com | mscsoftware.com Solid Shell Using 3D Elements Overview Introduction • Solid shell is used to model transverse solid elements, with a thickness direction • One dimension of the structure should be small compared with the two others (~ 1/15) • Thickness (and thus compression effects) are accounted for using solid shells Benefits • New modeling feature • For trim component only • Isotropic materials only Usage • Hexa/Penta/Tetra/PYRAM element types can be used • PSOLID entry FCTN field set to new PSLDSHL option (for PEM only) • MID field points to MAT1 (not MATPE1) PSOLID PID MID CORDM IN STRESS ISOP FCTN PSOLID 1 1 PSLDSHL 21 | hexagonmi.com | mscsoftware.com Perforated Shell Elements 22 | hexagonmi.com | mscsoftware.com Perforated Shell Elements Overview Introduction • Perforated shells are common in many acoustic systems • Avoids fine meshing of holes • Not suitable for precision modeling of perforation Benefit • Reduce meshing effort • Minimize CPU time 23 | hexagonmi.com | mscsoftware.com Perforated Shell Elements Usage • New MSC Nastran trim component bulk data entry PSHLPF • MID: solid material • T: thickness • SPACEG: spacing • RADIUS: radius • TOPOLGY: grid pattern (SQUARE / TRIA / HEXA) • FRHO: fluid density (air) • FVIS: viscosity • HOMG: homogenization (hole processing 0 or 1) PSHLPF PID MID T SPACEG RADIUS TOPOLGY FRHO FVIS HOMG PSHLPF 1 2 8.1-4 1.132-2 1.245-3 SQUARE 1.225 1.71-5 24 | hexagonmi.com | mscsoftware.com Simplified Biot Porous Material Model 25 | hexagonmi.com | mscsoftware.com Simplified Biot Porous Material Models Overview Introduction • Lumped porous • Model a porous medium when the material skeleton is assumed to be very soft (E=0) • Rigid porous • Model a porous medium when the material skeleton is assumed to be rigid • Delany-Bazley & Miki Porous • Semi-empirical numerical method for modeling porous materials • Assumes porosity = 1 • Only valid in a specific range (frequency/resistivity) Benefits • Easier modeling process for skeleton conditions • One dof per node in TRMC, instead of 4 • Potential performance improvement on TRMC matrix generation 26 | hexagonmi.com | mscsoftware.com Simplified Biot Porous Material Models Usage • On the Nastran side for trim component • POROPT: porous options (LUMPED, RIGID, MIKI or DELANY) • MAT1 field must be left blank if POROPT is RIGID, MIKI or DELANY • MAT1 field can be used for POROPT=LUMPED to provide SRHO • MAT1 field must have valid input (integer>0) if POROPT is blank • SRHO: solid density for LUMPED porous only • VLE – Blank or 0.0 is acceptable(=>0.0, default=0.0) • TLE – Blank or 0.0 is acceptable(=>0.0, default=0.0) MATPE1 MID MAT1 MAT10 BIOT POROPT SRHO VISC GAMMA PRANDTL POR TOR AFR VLE TLE MATPE1 1 15 LUMPED 0.1 1.84-5 9.4-1 4.0+4 27 | hexagonmi.com | mscsoftware.com Multiple Coupling Settings for a Trim Component 28 | hexagonmi.com | mscsoftware.com Multiple Coupling Settings for a Trim Component Overview Introduction • Coupling specifics are provided on a set of ACPEMCP / TRMCPL entries • The distance between the structure or trim component and cavity can vary • A single set of ACPEMCP / TRMCPL may not be suitable for all regions of a trim component • REGION ID (RID) is implemented to handle diverse coupling conditions of a trim component Benefit • Coupling tolerances for a region of a trim component can be precisely defined • Better coupling between the structure or trim component and cavity without requiring model changes 29 | hexagonmi.com | mscsoftware.com Multiple Coupling Settings for a Trim Component Usage • On Nastran side, for trim component • RID – region ID for ACPEMCP/TRMCPL (default=0) • ACPEMCP and TRMCPL with same TID and RID will be paired together • New design has minimum disturbance with existing PEM decks • FATAL if following conditions exist • TID,RID pair must be unique (trim and region IDs) • SET ID on ACPEMCP with different (TID,RID) pair must be different • OOC and SPM fields for RID>0 must be blank ACPEMCP TID SGLUED SSLIDE SOPEN SIMPER OOC SPM SAIRGAP SCUX SCUY SCUZ SCRX SCRY SCRZ SCFP RID ACPEMCP 1 1002 1004 20 TRMCPL TID CTYPE PLTOL GAPTOL1 GAPTOL2 GAPTOL3 GAPTOL4 RID TRMCPL 1 SSLIDE 0.12 5 20 30 | hexagonmi.com | mscsoftware.com Trim Component Processing Scenarios 31 | hexagonmi.com | mscsoftware.com Trim Component Processing Scenarios Overview Introduction • Previously MSC Nastran supported: • Processing of all trim components whether referenced by TRIMGRP Case Control or not • MSC Nastran 2021 now supports ALLTRMC and SLTTRMC: • New keywords on the TRIMGRP Case