Embed Size (px)
Citation preview
Learn more at altairhyperworks.com
Technical Support
Altair provides comprehensive software support via web FAQs, tutorials, training classes, telephone, and e-mail.
Altair Support on the World Wide Web
The Altair web site is a valuable online companion to Altair software. Visit www.altairhyperworks.com for tips and tricks, training course schedules, training/tutorial videos, and other useful information.
Altair Training Classes
Altair training courses provide a hands-on introduction to our products, focusing on overall functionality. Courses are conducted at our main and regional offices or at your facility. If you are interested in training at your facility, please contact your account manager for more details. If you do not know who your account manager is, please send an e-mail to [email protected] and your account manager will contact you.
Telephone and e-mail
When contacting Altair support, please specify the product and version number you are using along with a detailed description of the problem. Many times, it is very beneficial for the support engineer to know what type of workstation, operating system, RAM, and graphics board you have, so please have that information ready. If you send an e-mail, please specify the workstation type, operating system, RAM, and graphics board information in the e-mail.
To contact an Altair support representative, reference the following table or the information available on the HyperWorks website:
http://www.altairhyperworks.com/ClientCenterHWSupportProduct.aspx
Location Telephone e-mail
Australia 64.9.413.7981 [email protected]
Brazil 55.11.3884.0414 [email protected]
Canada 416.447.6463 [email protected]
China 86.400.619.6186 [email protected]
France 33.1.4133.0992 [email protected]
Germany 49.7031.6208.22 [email protected]
India 91.80.6629.4500 1.800.425.0234 (toll free)
Italy 39.800.905.595 [email protected]
Japan 81.3.5396.2881 [email protected]
Korea 82.70.4050.9200 [email protected]
Mexico 55.56.58.68.08 [email protected]
New Zealand 64.9.413.7981 [email protected]
North America 248.614.2425 [email protected]
Scandinavia 46.46.460.2828 [email protected]
Spain 34.910.810.080 [email protected]
South Africa 27.21.8311500 [email protected]
United Kingdom 01926.468.600 [email protected]
For questions or comments about this help system, send an email to [email protected].
In addition, the following countries have resellers for Altair Engineering: Colombia, Czech Republic, Ecuador, Israel, Russia, Netherlands, Turkey, Poland, Singapore, Vietnam, Indonesia
Official offices with resellers: Canada, China, France, Germany, India, Malaysia, Italy, Japan, Korea, Spain, Taiwan, United Kingdom, USA
See www.altair.com for complete contact information.
Intellectual Property Rights Notice: Copyrights, Trademarks, Trade Secrets, Patents & Third Party Software Licenses HyperWorks Solvers 2017.2.3 A Platform for Innovation™ Altair Engineering, Inc. Copyright© 1986-2018. All Rights Reserved. HyperWorks® products: HyperMesh® ©1990-2018; HyperCrash® ©2001-2018; OptiStruct® ©1996-2018; RADIOSS® ©1986-2018; HyperView® ©1999-2018; HyperView Player® ©2001-2018; HyperMath® ©2007-2017; HyperStudy® ©1999-2018; HyperGraph® ©1995-2018; MotionView® ©1993-2018; MotionSolve® ©2002-2018; HyperForm® ©1998-2018; HyperXtrude® ©1999- 2018; Process Manager™ ©2003-2018; Templex™ ©1990-2018; TextView™ ©1996-2018; MediaView™ ©1999-2018; TableView™ ©2013-2018; BatchMesher™ ©2003-2018; HyperWeld® ©2009-2018; HyperMold® ©2009-2018; Manufacturing Solutions™ ©2005-2018; solidThinking Inspire® 2018 ©2009-2017; solidThinking Evolve®2017 ©1993-2017; Durability Director™ ©2009-2018; Suspension Director™ ©2009-2018; AcuSolve® ©1997-2018; AcuConsole® ©2006-2018; SimLab® ©2004-2018; Virtual Wind Tunnel™ ©2012-2018; FEKO® (©1999-2014 Altair Development S.A. (Pty) Ltd.; ©2014-2018 Altair Engineering, Inc.); ConnectMe™ ©2014-2018; Click2Extrude™ Polymer 2017 ©1996-2017; Click2Extrude™ Metal 2017 ©1996-2017; Click2Form™ 2017 ©1998-2018; FLUX 2018 © 1983-2018, FluxMotor 2018 © v2017-2018; WinProp v.2018 ©2000-2018. Additional Altair Products: Multiscale Designer™ ©2011-2017 ESAComp v.4.7 ©1992-2018 Altair Packaged Solution Offerings (PSOs): Automated Reporting Director™ ©2008-2018; GeoMechanics Director ©2011-2018; Impact Simulation Director™ ©2010-2018; Model Mesher Director™ ©2010-2018; NVH Director™ ©2010-2017; Squeak and Rattle Director™ ©2012-2018; Virtual Gauge Director™ ©2012-2018; Weight Analytics™ ©2013-2017; Weld Certification Director™ ©2014-2018; Multi-Disciplinary Optimization Director™ ©2012-2018. Altair Simulation Cloud Suite: Simulation Manager™ ©2003-2018; Compute Manager™ ©2003-2017; Display Manager™ ©2003–2017; and Process Manager™ ©2003-2018. Altair PBS Works™: PBS Professional® ©1994-2018; PBS Control™ © 2008-2018; PBS Access™ © 2008- 2018; Compute Manager™ ©2012-2017; Display Manager™ ©2013-2017; PBS Pro™ ©1994-2017; PBS Application Services™ ©2008-2017; PBS Analytics™ ©2008-2017; PBS Desktop™ ©2008-2012; and e-Compute™ ©2000-2010. Runtime 2017 © 1995 – 2018
Special Notice: Pre-release versions of Altair software are provided ‘as is’, without warranty of any kind. Usage of pre-release versions is strictly limited to non-production purposes.
solidThinking Inspire® 2018 ©2009-2018; solidThinking Evolve®2017 ©1993-2018; solidThinking Compose® 2018 ©2007-2018, solidThinking Activate® 2018 ©1989-2018, solidThinking Embed® 2018 ©1989-2018, solidThinking Embed® SE 2018 ©1989-2018; Click2Extrude® Metal 2018 ©1996-2018; Click2Extrude® Polymer 2018 ©1996-2018; Click2Cast® 4.1 ©2011-2018; Click2Form™ 2018 ©1998-2018; Envision® 4.0 ©2013-2017.
Altair intellectual property rights are protected under U.S. and international laws and treaties. Additionally, Altair software is protected under patent #6,859,792 and other patents pending. All other marks are the property of their respective owners.
ALTAIR ENGINEERING INC. Proprietary and Confidential. Contains Trade Secret Information.
Not for use or disclosure outside of Altair and its licensed clients. Information contained in Altair software shall not be decompiled, disassembled, “unlocked”, reverse translated, reverse engineered, or publicly displayed or publicly performed in any manner. Usage of the software is only as explicitly permitted in the end user software license agreement. Copyright notice does not imply publication.
Third party software licenses
AcuConsole contains material licensed from Intelligent Light (www.ilight.com) and used by permission.
Software Security Measures:
Altair Engineering Inc. and its subsidiaries and affiliates reserve the right to embed software security mechanisms in the Software for the purpose of detecting the installation and/or use of illegal copies of the Software. The Software may collect and transmit non-proprietary data about those illegal copies. Data collected will not include any customer data created by or used in connection with the Software and will not be provided to any third party, except as may be required by law or legal process or to enforce our rights with respect to the use of any illegal copies of the Software. By using the Software, each user consents to such detection and collection of data, as well as its transmission and use if an illegal copy of the Software is detected. No steps may be taken to avoid or detect the purpose of any such security mechanisms.
p.2
OptiStruct 2017.2.3 Release NotesWhat's new and changed in OptiStruct 2017.2.3.
HighlightsAltair OptiStruct is an industry proven, modern structural analysis solver for linear and non-linearmechanical problems under static, dynamic, and thermal loads. It is the market-leading solution forstructural design and optimization. Based on finite-element and multibody dynamics technology, andthrough advanced analysis and optimization algorithms, OptiStruct helps designers and engineersrapidly develop innovative, lightweight and structurally efficient designs. OptiStruct is used bythousands of companies worldwide to analyze and optimize structures and mechanical systems forstrength, durability, noise and vibrations, heat transfer, as well as impact.
The major items for the OptiStruct release are:
• Stabilization in Nonlinear Static Analysis
• Energy output for Small Displacement Nonlinear Analysis
• Contact pressure optimization response
• Gasket pressure optimization response
Stiffness, Strength and StabilityStabilization
Static stabilization can be activated in nonlinear static analysis thru NLADAPT, STABILIZ.Stabilization could help if the problem becomes unstable due to local buckling. The stabilizationcomes from the mass (if the density is not defined, an artificial mass is calculated based on unitdensity) and the velocity.
Energy output for Small Displacement Nonlinear AnalysisEnergy output is now supported for small displacement nonlinear analysis. Contact Stabilizationand the static stabilization, the strain energy of the model will be output in the e.nlm file if NLOUTis defined in case control/subcase section.
DMIG with large rotationsDMIGs can now undergo large rotations when the new DMIGROT Bulk Data Entry is utilized.
Noise and VibrationsEnhanced PARAM,AMSE4EFM support
PARAM,AMSE4EFM is now supported for frequency-dependent material (MATF#) and frequency-dependent bushing (PBUSHT).
Thermal Analysis• Composites (PCOMP(G)/PCOMPP) are now supported for Nonlinear Heat Transfer Analysis.
Composites• Gasket pressure optimization response
p.3
DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATTi
DRESP1 “ID#” “Label” GSKP “PGASKID”
PRES “PGASKID”
• CGAP force optimization response
DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATTi
DRESP1 “ID#” “Label” FORCE ELEM FAX “CGAPelem ID”
• CFAST force optimization response
DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATTi
DRESP1 “ID#” “Label” FORCE ELEM FXF, FYF,or FZF
“CFASTelem ID”
• Solid corner stress response for topology optimization
DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATTi
DRESP1 “ID#” “Label” STRESS PSOLID “StressItemCode”
CORNER “PSOLIDID”
• Grid point stress response for topology optimization
DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATTi
DRESP1 “ID#” “Label” GPSTR PSOLID “StressItemCode”
“PSOLIDID”
• Response spectrum optimization
RSDISP response for size. shape and topology optimization.
The TX, TY, TZ, RX, RY, RZ displacement item codes are supported for the ATTA field for RSDISP.
p.4
DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATTi
DRESP1 “ID#” “Label” RSDISP ResponseSpectrumDisplacementComponent
“Grid ID”
RSSTRESS response for size and shape optimization.
For ROD, BEAM, and BAR elements, all static stress item codes are available for RSSTRESS ATTAfield. For Shells and Solid elements, similarly static stress item codes are supported, except forSurface Stress (von Mises, Max Principal, and Minor Principal stresses), and Neuber correction (1,2).
DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATTi
DRESP1 “ID#” “Label” RSSTRESS “PTYPE orELEM”
ResponseSpectrumStressComponent
“PTYPE orELEM ID”
• Neuber optimization response in nonlinear subcase
Neuber optimization response was not available in NLSTAT subcase. This is now supported.
DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATTi
DRESP1 “ID#” “Label” STRESS “PTYPE” NEUB “PTYPEID”
• Sensitivity Output for 1D Topology
OUTPUT,H3DTOPOL is now supported for 1D Topology.
• Optimization with Local Centrifugal Force loading
Optimization is now supported for centrifugal force (RFORCE) for a set of elements (IDRF).
• DDM support for MMO
The number of DDM MPI cores for each model can be specified in the main MMO input file.
ASSIGN, MMO, Label, filename, <number of DDM cores>
Underlying Elemental Responses Output in .out File for NORM Response
The top N contributions (element ID, response value, constraint violation) are printed for eachnorm response below the norm response itself. This is controlled by PARAM,PRTNORM,N and thedefault value is 10.
p.5
• DRESPONSE output when more than one grids/elemental responses are involved in DRESP2/DRESP3
Each grid/element involved in the response is now given a value corresponding to the totalresponse, and an unlimited number of nested DRESP2/3 responses is supported.
General Updates• Filter option for DISPLACEMENT output request
Filter options (TM,T1/2/3 for translation and TR, R1/2/3 for rotation) are now supported fordisplacement output for static and buckling subcases. H3D and punch files are supported. Only theresults that satisfy the filtering criteria will be output in order to reduce the file size.
• Material damping definition from each ply
Prior to this release, damping was only supported via GE specified on PCOMP(G) and PCOMPP.New string entry “USEMAT” is now available as an option for the GE field on above mentionedproperties and once this is set, the damping specified on material card for each of the plies and thecorresponding thickness will be used to form the damping matrices.
• Property/Component based energy output (strain energy and strain energy density)
group argument (PROP/COMP or BYPROP/BYCOMP) has been supported for static, eigenvalue,frequency response and transient analysis for ESE, EKE, and EDE entries. This is for H3D and punchfiles. GROUP energy is available under Element Energy Results Type in the H3D file. In punch files,the prop IDs/comp IDs and the energy and corresponding energy density are available.
With PROP(or BYPROP) and COMP(or BYCOMP), the elemental energies are also output. If onlyGROUP strain energy is needed, OPROP/OCOMP options for the group argument should be used.
• Automatically fix invalid RBE3
PARAM,FIXRBE3,YES is now available to automatically fix invalid RBE3, such as:
◦ RBE3 attached to solids with rotational dofs defined on component fields for independent grids.
◦ RBE3 which is not attached to any structure
With this param activated, the fixed RBE3 will be printed in the .out file for the user to check.
• Surface stress extraction for Linear Analysis
Surface Stress extraction (INT0 on ISOP field in PSOLID) with GAUSS stress output is nowsupported for Linear Analysis.
• General table data (TABLEG)
Generic table data with tabular data format has been introduced and this table data can be used inthe following situations:
◦ TABLEG can replace TABLED1, referenced by RLOAD# and TLOAD# entries.
◦ TABLEG can replace TABLEM1, referenced by MATT# entries.
◦ TABLEG can replace TABLES1, referenced by MATS1 and PCONT entries.
◦ TABLEG can replace TABLES1, referenced by TABLEST entries which are in turn referenced byMATS1 entries.
• SPC/SPCD definition through GRID SET
SPC/SPCD bulk data can now be defined by set of GRID instead of individual GRID IDs.
p.6
Figure 1:
Figure 2:
• ERROR/WARNING for unrecognized case control and bulk entries
SYSSETTING(UNKNDATA=ERROR/WARN) has been added. WARN is the default.
• ERROR/WARNING for control cards with no corresponding IDs in bulk data
SYSSETTING(UNREFSID=ERROR/WARN) has been added. ERROR is the default.
Unreferenced control cards implies cards which do not have expected reference in the bulk section.For example, MPC=2 is defined in case control section but there is no MPC with ID=2 in bulksection.
Currently, MPC, SPC, NSM and NSGE are supported.
• New Subtype “DMIG” for GRID/ELEM bulk SET
SET,ID,GRID/ELEM,DMIG
This could be used for output requests including ERP output in superelement residual run.
Output• Strain at GAUSS point for solids is available
• GAUSS and Corner option for stress/strain in composites are supported
• Corner option for composite stress (CSTRESS) is now supported
• Corner option for strain in Transient Analysis is available
• GAUSS and corner option for Neuber in Linear Analysis is now supported
• Neuber stress/strain for Frequency Response and Transient Analysis
• PSD/RMS composite stress/strain (CSTRESS/CSTRAIN)
• Strain energy (ESE) recovery in superelement recovery run
• Strain energy recovery in superelement residual run
This is for normal mode, transient and frequency response. Stress and strains should be requestedin superelement (DMIG) generation run. Strain energy recovery is supported for H3D files.
• Stress/strain output from random response is in elemental system instead of material system
Solvers and Performance• Automatic memory expansion for FASTFR
p.7
Prior to this release, the number of CPUs specified for FASTFR (-nt, -nproc) could be reduced ifnot enough memory is allocated to accommodate all the CPUs. The enhancement in this release isto automatically expand the memory in order to use all the CPUs specified by the user.
• LFREQ support for FASTFR run
• DDM for Transient Analysis
DDM is now supported for Transient Response Analysis.
• -ddmngrps script option is added, which is equivalent to PARAM,DDMNGRPS
This is supported to activate multi-level DDM runs. In previous release, only PARAM,DDMNGRPSwas available. Now -ddmngrps is available as a run option.
Resolved Issues• APPLOD option for RESVEC had an issue and did not generate any residual vector. This is now fixed.
• DDM (Domain Decomposition method) with Infinite Element did not work properly and this is nowfixed.
• ALPHA field on RBE2/RBE3 was not working properly for some situations due to internal numbering.This is fixed.
• Nonlinear analysis (with many subcases) failed due to insufficient memory after the analysisconverged. This is now fixed.
• MPCF for modal transient could be wrong if AMSES/AMLS was used. This is fixed.
• Modal frequency response results could be wrong if FASTFR is used with PBUSHT and largevariation of material damping. This is now fixed.
• Sine sweep with SURFSTS on FATPARM caused error 251. This is fixed.
• PFPATH job would crash if the model has only fluid MPC but no structural MPC. This is fixed.
• 1st order axi-symmetry elements has a numerical issue that triggers unnecessary AUTOSPC. This isfixed.
• FATAL PROGRAMMING ERROR 8014 could happen if the stress responses for design (topology orfree-size) and non-design regions are included in the same DRESP1. This is now fixed.
• ROMAX recovery matrices could have an issue for certain scenarios and this is now fixed.
• Mode tracking feature for optimization has an issue in that it only tracks first 5 modes. This is nowfixed.
• Complex eigenvalue with AMSES using Material damping GE caused the programming error. This isnow fixed.
• Programming error for transient with DDM has been fixed.
• Contact pressure/force results for Node-to-Surface (N2S) contact in small displacement nonlinearanalysis was incorrect. This is now fixed.
p.8
RADIOSS 2017.2.3 Release NotesHighlightsVersion 2017.2.3 of RADIOSS fixes critical issues detected in 2017.2.2 release and includes someenhancements.
Finite Volume Airbag (/MONVOL/FVMBAG1)• New automatic FVM meshing method (kmesh=2) using external tetrahedron mesh libraries
◦ The tetrahedron meshing is performed in the Starter
◦ These libraries are provided on the install packages
• Automatic switch from Finite Volume Method to Uniform pressure
◦ The switch is activated at a specified time, Tswitch
◦ Or when only 1 finite volume remains
• Improvement of the initial velocity for the internal node of the finite volume mesh
• New option in the flag Iequi in order to reduce CPU cost
◦ With Iequi=1, RADIOSS performs simplified FVM Simulation before TTF to provide gas dynamicequilibrium inside of the airbag each cycle.
Time Step Control• /DT/INTER/AMS: compatibility with /DT/NODA and /DT/NODA/CST
• /DT/NODA/CST and /DT/INTER/CST: Enhancement of the constant nodal time step treatment
◦ /DT/NODA/CST1 or /DT/INTER/CST1 = same as /DT/NODA/CST or /DT/INTER/CST (default)
◦ /DT/NODA/CST2 or /DT/INTER/CST2 = improved formulation. The computation starts directlyfrom the target time step and it remains most often constant during the computation. The totalmass added in the model should be lower.
Contact Interface• /INTER/TYPE24: node to surface contact with edge treatment
◦ Stability improvement in double and single precision
◦ Behavior improvement with the Iedge and IdelDEL options.
• /INTER/TYPE2: tied contact
◦ If all the slave nodes are removed from the tied interface due to the project issues and theIgnore flag setting, the starter will delete the contact to avoid issue during the computation
◦ Result improvement with the option /PARITH/ON.
◦ Stability improvement with single precision and global time step (/DT/GTS).
Materials• /MAT/LAW5 (JWL): Pressure shift and initial pressure options
◦ The ability to define a pressure shift and initial pressure was added to LAW5.
p.9
Documentation• Update of the modified keywords:
◦ /MONVOL/FVMBAG1
◦ /DT/NODA/CST
◦ /MAT/LAW5
• Correction and improvement of the overall documentation
Resolved Issues• /ALE/GRID/SPRING: improvement of the input deck reading and starter listing message
• /ALE/GRID/STANDARD: improvement of the input deck reading and starter listing message
• /MAT/LAW42 (OGDEN): stability issue for the material using viscous parameter (Prony serie) directlydefined into the material law.
• /MAT/LAW70 (FOAM_TAB)
◦ Improvement of the unloading behavior for the formulation Iflag=0
◦ Stability improvement with the quadratic tetrahedron element (/TETRA10)
• /MAT/LAW93 (ORTH_HILL): now compatible with /PROP/TYPE51 and /PROP/PCOMPP
• /PROP/KJOINT2: improvement of the specific energy computation
• /PROP/TYPE17 (STACK): now compatible with /INISHE/ORTH_LOC and /INISH3/ORTH_LOC
• /PROP/TYPE14 (SOLID)
◦ Improvement of the computation stability with the solid 2 SPH option and the material /MAT/LAW24 (CONC).
• /RWALL/PARAL: parallelogram rigid wall
◦ Improved behavior in single precision computation. Slave nodes could remain attached to thewall after impact.
MotionSolve 2017.2.3 Release NotesWhat's new and changed in MotionSolve.
HighlightsMotionSolve is a state-of-the-art multibody solver available in HyperWorks. It has a complete set ofmodeling elements and powerful numerical methods to support a full set of analysis methods. Theaccuracy, speed and robustness of MotionSolve has been validated through extensive testing withcustomer models and test data. MotionSolve also offers unmatched compatibility with ADAMS/Solverinput.
In version 2017.2.3, MotionSolve brings enhancements and bug-fixes to the existing capabilities.
p.10
EnhancementsMemory usage improvements for 3D contact
The total amount of system memory used when simulating a model containing multiple 3D rigidbody contacts has been optimized with this release. By re-using contact mesh data and pre-processing data within the solver, the memory footprint has been reduced substantially for modelsthat contain a large number of contacts.
In practice, the reduction in memory usage will depend on both the number of contacts in themodel as well as the density and size of the meshes being used.
Retrieve joint friction results in any frameWith this release, you can use the FRICTION function to specify a third argument - rm. Thisargument lets you specify a custom frame of reference for retrieving joint friction results.
2D curve-curve contact supports matrix definitionsWith the current release, you can use data defined within the Reference_Matrix element to definethe curves used for 2D curve-curve contact.
Note: The matrix used must have exactly three columns, for the X, Y and Z data ofthe curve.
Control number of threads used by mspostWith this release, you can specify the maximum number of threads that mspost uses whenrunning in standalone mode. This is useful when you want to limit the CPU consumption bymspost for large result files.
Note: When running the model from MotionView or the Solver Run Manager, mspostwill “inherit” the number of threads specified for the overall job. That is, if youspecified “-nt 4” i.e. maximum number of threads allowed are 4, then mspost willalso limit itself to using a maximum of 4 threads.
Additional outputs available through CONTACT functionWith this release, you can now retrieve more contact related results using the 4-parameterCONTACT function. Additional results that are now available:
• Maximum penetration velocity
• Average penetration velocity
• Maximum slip velocity
• Average slip velocity
• Friction power
For more details on usage, please refer to the documentation for CONTACT.
Resolved IssuesResults file for MotionSolve - AcuSolve co-simulation
Previously, during a co-simulation with AcuSolve, MotionSolve may write result data into theoutput file (MRF) at a different frequency than specified. This has been corrected with this releasesuch that the frequency of output results matches the print_interval specified.
p.11
License error when using VSTIFF integrator during MotionSolve - AcuSolve co-simulationWith the previous release, if you selected any integrator except DSTIFF for MotionSolve during aMotionSolve - AcuSolve co-simulation, you were presented with a license error message. This wasdetermined to be a bug and is now fixed.
Note: You may still, only use DTSIFF for co-simulation with AcuSolve. Using any otherintegrator will halt the simulation with an appropriate error message.
Mismatch in graphics color between MotionView and HyperViewWith the previous release, some graphics in the model may appear in a different color inMotionView than in HyperView. This was determined to be a bug in the H3D writer and has beenfixed within MotionSolve.
Incorrect output result timesWhen dae_interpolation is set to FALSE and h_max is not the same as print_interval, MotionSolvemay write output results at incorrect times. This has been corrected with the current release.
PINVAL, POUVAL not working with SYSFNCPINVAL and POUVAL support within SYSFNC has been fixed with this release.
CONTACT function ignores RMThe 3 parameter CONTACT function ignored the RM argument while calculating the averagecontact point. This has been fixed with the current release.
User Written Tire Models now return non-zero wheel omegaFor user written tire models, MotionSolve outputs the wheel rotational velocity about the spinaxis (OMEGAR) that it inputs to the tire model rather than the value the tire model returns inVARINF(50). This mimics the behavior of the ADAMS implementation of the TYDEX Standard TireInterface, where OMEGAR is output even when the user written tire model returns VARINF(50) =0.0.
CDTire and OpenCRG now handle road data files larger than 2GBPreviously OpenCrg road files larger than 2 GB could not be loaded, causing simulations to fail.This was a known problem in OpenCrg version 1.0.6. To correct the problem, CDTire is updated touse OpenCrg version 1.1.1.
Multi-threaded execution of FTIRE and CDTire is now defaultWhen you use FTIRE or CDTire with MotionSolve, by default FTIRE and CDTire are multi-threadedto improve execution speed.
Altair Driver does not fail when started at times greater than zeroPreviously if simulated a vehicle model for some time and then started Altair Driver using theuser control command, the static simulations the Driver performs to identify the steering ratiowould fail because time was greater than zero. Altair Driver will now start successfully when timeis greater than zero.
Altair Driver does not maintain speed on hillsPreviously if you asked Altair Driver maintain a constant speed for a vehicle driving on a road withelevation gain or loss, the vehicle would speed up going downhill and slow down going up. Nowif the path data you give the Altair Driver contains height (z), Altair Driver’s feedforward speedcontroller will detect the gradient and apply more throttle when the vehicle is traveling uphill and
p.12
less throttle when traveling downhill. Alternatively you can tell Altair Driver to employ a secondaryPI controller to compensate road gradients.
HyperXtrude 2017.2.3 Release NotesWhat's new and changed in HyperXtrude.
HighlightsAltair HyperXtrude is a suite of finite element solvers for simulating metal extrusion, polymer extrusion,metal rolling, friction stir welding, billet forging, and resin transfer molding processes. It has processspecific features for each of these processes and supported with an easy use interface for setting upmodel data.
In version 2017.2.3, HyperXtrude brings enhancements and bug-fixes to the existing capabilities.
HyperXtrude for Metal ExtrusionResolved Issues
• Solver was not printing the computer hardware information correctly in the OUT file. This isresolved.
• Solver was not printing the CPU time statistics on Windows machines correctly. This issue isnow resolved.
HyperXtrude for Resin Transfer MoldingEnhancements to Automatic Time Step Computation
RTM solver will automatically adjust the time step in each iteration to ensure a small percentageof the mold volume is filled (1%-3%). This improves the accuracy of the solution and at the sametime reduces the computational time.
Permeability Tensor from Draping ComputationsSolver's local coordinate system module is enhanced to determine permeability tensor at anintegration point using the draping computations from HyperMesh. This enables to correctly mapthe permeability tensor from the lay-flat orientation to the orientation of the preform inside themold.
