01 excite release notes

8/16/2019 01 EXCITE Release Notes

1/92

Release Notes

AVL EXCITEVERSION 2014.1


2/92


3/92

Release Notes EXCITE v2014.1

AVL LIST GmbHHans-List-Platz 1, A-8020 Graz, Austriahttp://www.avl.com

AST Local Support Contact: www.avl.com/ast-worldwide

Revision Date Description Document No.

A 30-Apr-2009 EXCITE v2009 - Release Notes 06.0101.2009B 17-Jul-2009 EXCITE v2009.1 - Release Notes 06.0101.2009.1C 30-Nov-2009 EXCITE v2009.2 - Release Notes 06.0101.2009.2D 30-Mar-2010 EXCITE v2009.3 - Release Notes 06.0101.2009.3E 19-Nov-2010 EXCITE v2010 - Release Notes 06.0101.2010F 25-Mar-2011 EXCITE v2010.1 - Release Notes 06.0101.2010.1G 29-Jul-2011 EXCITE v2011 - Release Notes 06.0101.2011H 02-Dec-2011 EXCITE v2011.1 - Release Notes 06.0101.2011.1

I 16-May-2012 EXCITE v2011.2 - Release Notes 06.0101.2011.2J 20-July-2012 EXCITE v2011.2.1 - Release Notes 06.0101.2011.2.1K 25-Jan-2013 EXCITE v2013 - Release Notes 06.0101.2013L 17-June-2013 EXCITE v2013.1 - Release Notes 06.0101.2013.1M 15-Nov-2013 EXCITE v2013.2 - Release Notes 06.0101.2013.2N 15-May-2014 EXCITE v2014 - Release Notes 06.0101.2014O 28-Feb-2015 EXCITE v2014.1 - Release Notes 06.0101.2014.1

Copyright © 2015, AVL

All rights reserved. No part of this publication may be reproduced, transmitted, transcribed,stored in a retrieval system, or translated into any language or computer language in any form orby any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, withoutprior written consent of AVL.

This document describes how to run the EXCITE software. It does not attempt to discuss all theconcepts required to obtain successful solutions. It is the user’s responsibility to determine ifhe/she has sufficient knowledge and understanding of structural dynamics to apply this softwareappropriately.

This software and document are distributed solely on an "as is" basis. The entire risk as to theirquality and performance is with the user. Should either the software or this document provedefective, the user assumes the entire cost of all necessary servicing, repair, or correction. AVLand its distributors will not be liable for direct, indirect, incidental or consequential damagesresulting from any defect in the software or this document, even if they have been advised of the

possibility of such damage.The names of the software and hardware products used in this manual are mostly the respectivetrademarks or registered trademarks of their companies.

http://www.avl.com/http://www.avl.com/http://www.avl.com/ast-worldwidehttp://www.avl.com/ast-worldwidehttp://www.avl.com/ast-worldwidehttp://www.avl.com/


4/92


5/92


AST.06.0101.2014.1 - 28-Feb-2015 i

Table of Contents

1. Service Pack v2014.1 _____________________________________________ 1-1

1.1. EXCITE Power Unit __________________________________________________________ 1-1

1.1.1. New Features ____________________________________________________________ 1-1

1.1.1.1. Turbocharger Analysis ________________________________________________ 1-1

1.1.1.2. Map Based Torque Converter Joint _____________________________________ 1-2

1.1.1.3. Planetary Gearset Phasing Utility ______________________________________ 1-3

1.1.1.4. New Utility – Fretting Analysis ________________________________________ 1-4

1.1.1.5. Mount Layout Tool: Damped Modal Analysis ____________________________ 1-5

1.1.1.6. Equivalent Speed Dependent Stiffness of Viscous Damper ________________ 1-5

1.1.1.7. FE Interface Enhancements ___________________________________________ 1-5

1.1.2. Enhancements ___________________________________________________________ 1-6

1.1.3. Resolved Issues __________________________________________________________ 1-9

1.1.4. Installation Examples ___________________________________________________ 1-21

1.2. EXCITE Designer ___________________________________________________________ 1-24

1.2.1. New Features ___________________________________________________________ 1-24

1.2.1.1. Mount Layout Tool: Damped Modal Analysis ___________________________ 1-24

1.2.1.2. Mount Layout Tool: Other GUI Viewer Enhancements __________________ 1-27

1.2.1.3. Torsion: Equivalent Speed Dependent Stiffness of Viscous Damper (for use inEXCITE Power Unit) ________________________________________________________ 1-28

1.2.2. Enhancements __________________________________________________________ 1-29

1.2.3. Resolved Issues _________________________________________________________ 1-29


1.3. EXCITE Piston&Rings ______________________________________________________ 1-31

1.3.1. 3D Piston Ring __________________________________________________________ 1-31

1.3.1.1. Basic Description ____________________________________________________ 1-31

1.3.1.2. 3D Ring Modeler _____________________________________________________ 1-33

1.3.1.3. 3D Piston Ring Simulation ____________________________________________ 1-34

1.3.1.3.1. Result files used by IMPRESS Chart _______________________________ 1-34

1.3.1.3.2. Result files used by IMPRESS (3D Animation) ______________________ 1-35

1.3.2. Enhancements __________________________________________________________ 1-37

1.3.3. Resolved Issues _________________________________________________________ 1-37


1.4. EXCITE Timing Drive _______________________________________________________ 1-39

1.4.1. Enhancements __________________________________________________________ 1-39

1.4.2. Resolved Issues _________________________________________________________ 1-39


1.5. EXCITE Acoustics __________________________________________________________ 1-41

1.5.1. Enhancements __________________________________________________________ 1-41

1.5.2. Resolved Issues _________________________________________________________ 1-42

1.6. EXCITE Pre-processing Tools ________________________________________________ 1-43

1.6.1. Shaft Modeler: New Features _____________________________________________ 1-43

1.6.1.1. Gyroscopic Modal Analysis of Rotating Shafts: Main Application Case -Turbocharger _______________________________________________________________ 1-43


6/92

EXCITE v2014.1 Release Notes

ii AST.06.0101.2014.1 - 28-Feb-2015

1.6.1.2. Enhancement _______________________________________________________ 1-47

1.6.1.3. Resolved Issue _______________________________________________________ 1-47

1.6.2. AutoSHAFT ____________________________________________________________ 1-47

1.6.2.1. Resolved Issue _______________________________________________________ 1-47

1.7. GUI (Graphical User Interface) _______________________________________________ 1-48

1.7.1. Enhancement ___________________________________________________________ 1-48

1.7.2. Resolved Issue __________________________________________________________ 1-48

2. Release v2014 ___________________________________________________ 2-1

2.1. EXCITE Acoustics ___________________________________________________________ 2-1

2.1.1. Highly Efficient Sound Radiation Calculation _______________________________ 2-1

2.1.2. Capabilities and Features _________________________________________________ 2-2

2.2. EXCITE Power Unit __________________________________________________________ 2-4

2.2.1. New Features ____________________________________________________________ 2-4

2.2.1.1. Map based Dual Mass Flywheel Joint (DMFM) __________________________ 2-4

2.2.1.2. Elasto Plastic Clutch Joint (EPCL) _____________________________________ 2-6

2.2.1.1. Electric Machine Joint Extensions ______________________________________ 2-7

2.2.1.2. EHD Contacts – Non-stationary Thermal Boundary Conditions ___________ 2-8

2.2.1.3. Engine-Mount Joint Extensions (EMO1) ________________________________ 2-9

2.2.1.4. Mount Layout Tool Extensions ________________________________________ 2-10

2.2.1.5. Other Enhancements ________________________________________________ 2-10

2.2.1.5.1. Section Forces/Moments for Condensed Bodies ______________________ 2-10

2.2.1.5.2. FE Interface Enhancements _______________________________________ 2-11

2.2.1.6. Additional New Features _____________________________________________ 2-12

2.2.2. Enhancements __________________________________________________________ 2-12

2.2.3. Resolved Issues _________________________________________________________ 2-14

2.2.3.1. Resolved Issues Provided as Patches for v2013 __________________________ 2-20


2.3. EXCITE Designer ___________________________________________________________ 2-25

2.3.1. New Feature – Extended Mount Layout Tool _______________________________ 2-25

2.3.1.1. Mount Non-Linear Properties _________________________________________ 2-25

2.3.1.2. Mount Non-Linear Static Analysis _____________________________________ 2-25

2.3.1.3. Mount Modal Analysis in Static Equilibrium Position ___________________ 2-26

2.3.1.4. Mount Basic Vibration Analysis in Static Equilibrium Position ___________ 2-26

2.3.2. Enhancements __________________________________________________________ 2-27

2.3.3. Resolved Issues _________________________________________________________ 2-28


2.4. EXCITE Piston&Rings ______________________________________________________ 2-30

2.4.1. Enhancement ___________________________________________________________ 2-30

2.4.2. Resolved Issues _________________________________________________________ 2-30


2.5. EXCITE Timing Drive _______________________________________________________ 2-31

2.5.1. Enhancements __________________________________________________________ 2-31

2.5.2. Resolved Issues _________________________________________________________ 2-32

2.5.2.1. Resolved Issue Provided as Patches for v2013 __________________________ 2-33


2.6. EXCITE Pre-processing Tools ________________________________________________ 2-35


7/92


AST.06.0101.2014.1 - 28-Feb-2015 iii

2.6.1. AutoSHAFT ____________________________________________________________ 2-35

2.6.1.1. Enhancements ______________________________________________________ 2-35

2.6.1.2. Resolved Issue _______________________________________________________ 2-35

2.7. GUI (Graphical User Interface) _______________________________________________ 2-35

2.7.1. Resolved Issues _________________________________________________________ 2-35

2.7.1.1. Resolved Issues Provided as Patches for v2013 __________________________ 2-36


8/92


9/92


10/92


1-2 28-Feb-2015

A specific turbocharger solution pack is offered. Nevertheless licensing thecrankshaft dynamics + EHD solution packs allow to perform turbochargeranalysis without any restrictions, too.

1.1.1.2. Map Based Torque Converter Joint

A new joint called Hydraulic Torque Converter (hereafter referred to as HTCM joint) hasbeen implemented in order to support the modeling of automatic transmissions (ATs).

Based on measured converter performance characteristics/maps, the transmissionbehavior of the torque converter can be simulated. A mechanical connection like a Lock-Up clutch can be additionally taken into account by a clutch joint in parallel to HTCM-

joint. In this way a complete torque converter can be modelled.

The user can specify 4 types of maps within the HTCM joint, depending on the availabledata material. More specifically, λ-, cf- and k-curve is supported, as well as the torquewhich is operating on the pump side. The values have to be specified over the speed rationturbine / npump with respect to a defined reference speed of the pump.


11/92


28-Feb-2015 1-3

The HTCM joint can be used as a connecting element between the engine and gearbox(see picture below).

The hydraulic part of the torque converter is used for the vehicle launch. The TC providesa multiplied torque, which helps to take-off the vehicle. When the turbine and the pumpreach the same speed (speed ratio = 1) the converter acts as a usual hydraulic clutch.

1.1.1.3. Planetary Gearset Phasing Utility

Modelling planetary gearsets by using the Advanced Cylindrical Gear Joint (ACYG)

requires that the angular position - the so called phasing - of the individual gear meshesbetween sun and planets as well as planets and ring is set up in a consistent manner.


12/92


1-4 28-Feb-2015

Otherwise unrealistic uneven load distribution between the different planet-branches willtake place.

In order to compute phasing angles according to the global design parameters of thegearset a small tool is now provided as an EXCITE-Utility. It can be called up throughthe AWS-EXCITE GUI’s drop down menu: ‘Utilities | Python Scripts … | Planetary

Gearset Phasing’ In addition to the phasing angles of the individual ACYG-joints within the gearset, theUtility also provides visualization geometries of sun, planets and ring gears in form of

Abaqus input files. These geometries are derived from the ACYG-Joint visualization tool(‘Generate Profiles’) and can be attached to corresponding bodies in order to obtain adetailed gearset visualization within the 3D-view.

1.1.1.4. New Utility – Fretting Analysis

To fill the gaps for performing a fretting analysis on e.g a bearing shell 2 new utilities

have been implemented:- Redefine Node Coordinates

- Evaluate Fretting Results

Redefine Node Coordinates will just read the deformations from an Abaqus .odb file aftera bolt preload step and apply the inverted displacements to the nodal coordinates of the

bore nodes.


13/92


28-Feb-2015 1-5

Evaluate Fretting Results will read contact results from a detailed contact analysis froman Abaqus .odb output database for defined steps, perform a special fretting calculationand output fretting results either to text (Gidas or ASCII) or Excel (csv) files. In additionfretting results can be written to an Abaqus .odb file for 3D visualization in e.g. AbaqusCAE/Viewer.

1.1.1.5. Mount Layout Tool: Damped Modal Analysis

Refer to section 1.2.1.1 for details.

1.1.1.6. Equivalent Speed Dependent Stiffness of Viscous Damper

Refer to section 1.2.1.3 for details.

1.1.1.7. FE Interface Enhancements

Abaqu s 6.14

Native Abaqus 6.14 is now supported throughout AWS. In particular:

All FE Analysis tasks have been adjusted.

Utility ‘Convert FE Data’ can convert an Abaqus 6.14 .sim file to .exb file.

Utility ‘Modal Data Recovery’ is able to perform a modal stress recovery readingmodal stress data from an Abaqus 6.14 .sim database.

Due to inconsistent compiler versions, the EXCITE FEA Solver based on Abaqus 6.14Standard Solver still cannot be offered. Also IMPRESS 3D will not be able to accessresults from an Abaqus 6.14 .odb output database.

Ans ys 16.0

The latest version of Ansys – 16.0 is already fully supported.In addition, there are 2 main new features in Ansys 16.0:

1. Generation of the inertia invariants internally and output the .exb file directlyusing new EXB API

Ansys 16.0 is the first version, that will generate an .exb file directly at CMSgeneration pass which will contain all relevant body properties for an flexiblebody in AVL EXCITE for:

a. a body w/o global motion (SMOT) using command:

CMSOPT,fix,,,,,,exb

b. a body w/ global motion (CON6) using commands:CMSOPT,fix,,,,,,exb

EXBOPT,1 creates and stores all inertia invariants

This first version does not support the output of geometry (mesh data) as well asa recovery matrix to .exb file. A separate recovery matrix (.tcms) can be requestedby command:

EXBOPT,,1

Nevertheless the Data Recovery utilities have been extended to read the meshdata from an Ansys .cdb file and recovery matrix from .tcms file.

2. Recovery of EXCITE results in Ansys via DSUB file

Therefore a new APDL macro is available which prepares all necessary data foran expansion pass in Ansys and convert the EXCITE results stored in Nastran


14/92


1-6 28-Feb-2015

INPUTT4 file format to Ansys DSUB file format provided by an appropriatePython script.

NX Nastran 9.x

New DMAP alter files have been introduced (AVL_alter_nxn.v9) to support latestreleases – NX Nastran 9.0 and 9.1 – for condensation jobs. In addition all case based

tasks have been updated to write proper input files for data recovery for the new NXversions.

OptiStru ct 13.0

OptiStruct 13.0 is the first version which will generate the inertia invariants internallyand generate an .exb directly during a condensation job.

Therefore parameter PARAM,EXCEXB,YES has to be defined in solver input file.

This first version does not support the direct output of geometry (mesh data) to .exb file,yet. To overcome this issue the users can either simply add the geometry with utility“Convert FE Data” to the existing .exb file or define a mesh input file to read thegeometry from a .bdf Bulk Data file at utility “(Modal) Data Recovery”.

1.1.2. Enhancements

AXHD joint: new oil outflow resultsCRQ_134490For the AXHD joint the following oil outflow results at boundaries have been added:- Flow At Inner Diameter- Flow At Outer Diameter- Flow At Flange Start- Flow At Flange End

Create model stepCRQ_132756

The memory management of excitepre (Create model step) was extended so that morethan 2GB of memory can be used in particular on LINUX systems.

Data recovery at MSC Nastran superelementsCRQ_133477

An additional parameter "PARAM,SPARSEDR,NO" has been added for performing asuperelement recovery using SOL111 or SOL112.

Datacheck for new jointsCRQ_135473Datacheck messages are more readable now for several new joints (Clutch joint, DualMass Flywheel, Torque Converter).

EHD bearing data properties

CRQ_103714The description of option 'FE-mesh at B.C. of oil supply is modeled using a different


15/92


28-Feb-2015 1-7

material type' has been updated and an appropriate figure has been added forexplanation .

EHD2: endless loop bug during integrating pressureCRQ_134098, CRQ_134478In some rare cases in EHD2 calculations, it could happen that the calculation stopped due

to an endless loop during pressure integration. Now only a warning will be given and thealgorithm will continue with a recalculation of the last time step.

EHD2: modified EHD2 divergence criteriaCRQ_137480The joint divergence criteria were slightly modfied such that a few more model loops arecomputed before a time step reduction is applied. This can lead sometimes to a few moreloops but enhances the stability of the overall algorithm.

Enhance EHDT performance by improved temperature initializationCRQ_133421Joints of type EHD2: As oil film temperature behaves inert compared to the rest of thedynamic system, the number of cycles, which is required to get cyclic converged results incase of steady state calculations, strongly depends on the inertially set temperatures.

This initial temperature setting was enhanced.

Enhanced description of Mass Props panel in Crank Train GlobalsCRQ_135880Some hints have been added to describe for which load generation the crank pin masseswill be used in Crank Train Globals as well as a best practice modeling recommendationof connecting rod and piston assembly for EXCITE Power Unit.

Enhanced Jacobi update controlCRQ_132151Joints of type EHD2, AXHD, EPIL and ENHD use an adapted Newton-Raphsonalgorithm to couple the multi-body dynamics with the hydrodynamics. This iterationstrategy was enhanced so less iterations are required per time step.

Enhanced Newton damping algorithm for joint iterationCRQ_132150The iterative coupling between bodies and joints of type EHD2, AXHD, EPIL and ENHDis done using a Newton-Raphson strategy. The strategy considers a damping algorithm tobring each time step to convergence. The damping algorithm was enhanced so that lessiterations are required per computed time step. The result quality remains unchanged.

Enhanced treatment of clearance time derivative for low speed applicationsCRQ_132152Instabilities may occur in low speed applications when hydrodynamic boundaryconditions run through high pressure areas. The instability mainly is related to the timederivative of the clearance height (hp), which may be excited to oscillate in this case. Asmoothing of hp stabilizes the behavior significantly.

FE Analysis Task - Linear Static Stress Analysis: consideration of shear loadCRQ_115752, CRQ_130257Shear (friction) load can now be applied in a similar manner as pressure load forperforming fretting analysis at bearing shells. Solid surface sets are required for applyingshear data and storage of shear stress data should be requested in EHD properties of the

joint before performing the EXCITE simulation.

Flow factor tableCRQ_131302

A description for the parameters required at user defined input for the Flow Factor Tablehas been added to Users Guide.

Heat balance enhancedCRQ_135103


16/92


1-8 28-Feb-2015

Joints of type AXHD, EHD2 and EPIL: storage therms are considered in heat balancenow. This improves the understanding of the overall thermal balance within a joint.

IMPRESS 3D: support of Ansys .rst format added for structure borne noise evaluationCRQ_133792IMPRESS 3D is now able to read complex velocities from an Ansys .rst results file and

perform appropriate structure borne noise evaluations like generation of normal velocitylevels on outer surface for octave bands, etc.

Improved output of Initial Conditions at input fields that are intentinally left emptyCRQ_122828The GUI now writes 0.0 value (instead of outputting the highest possible value) to thesimulation kernel, when the user provides an empty input field at Initial Conditionsspecification for a body.

Installation model for piston analysisCRQ_133381

At the piston installation model (105_Piston) the asperity table as well as flow factortable have been updated and appropriate files - 'asppresstable.dat' and 'flowfactable.dat' -added to the ./excite folder.

Kernel option: EHD (MB)CRQ_133470In "Kernel Options | Memory Allocation" the option "EHD (MB)" has been removed.

Lumped mass matrix (MFF) now generated when no QSET/SPOINT cards are definedCRQ_135816In the past condensation of a flexible body prepared for global motion without modalDOF's did not work properly, as the lumped mass matrix was empty at the end of theanalysis. With the corrected AVL alter include file (AVL_alter_acms.v2013) this problemhas been fixed.

Utility - Modal Data Recovery / Modal Contribution FactorCRQ_137071

A new flag is available at Modal Data Recovery / Modal Contribution Factor that allowsskipping of DOFs not available in the Recovery Matrix.

Nodal resultsCRQ_129097

A description of obtained nodal results for each degree-of-freedom has been added to theUsers Guide.

Note for applying predefined motion at flexible bodiesCRQ_136097When applying a predefined motion on a flexible body, it must be guaranteed that thebody is constraint in at least one node by a single point constraint (SPC) or groundedspring. An appropriate note has been added in Users Guide.

Parallelization of body force applicationCRQ_135207The parallel performance was slightly increased by code restructuring. No difference ofobtained results compared to previous versions were caused.

Prepare Load Steps for Static/Transient Stress Analysis in Ansys: FE model file selectionCRQ_117725FE Analysis task - Prepare Load Steps for Static/Transient Stress Analysis - does notrequire to select any Ansys FE Model File, as this task just generates appropriate inputfiles which are used later in Ansys environment by APDL macros to setup the FEanalysis. An appropriate note has been added in Users Guide.

Print both time and angular reference information into simulation log file

CRQ_135517


17/92


28-Feb-2015 1-9

Both time and angle information is printed into the simulation log file no matter if timeor angle based simulation timing is chosen by the user.

Result creation process and report creation processCRQ_111163Task 'Create Results' has been split into two separate tasks: 'Create Results' and 'Create

Reports'. For more information see CRQ_122525.Rotation Axis setting preserved after re-opening of utility dialogCRQ_132195In Utilities->Misc->Generate Bearing Journal/Pin, the Rotation Axis setting was notpreserved (on the contrary to all other inputs), i.e. it was always reset to the defaultrotation axis from FE Preferences after re-opening. This has been changed now and theselected axis setting is also kept.

Stabilization of hydrodynamic couplingCRQ_130644With the changes of CRQ_132150 and CRQ_132151 the hydrodynamic coupling wasenhanced. Due to this enhancement problems like the reported "NAN or INF" messagesdo not occur any more. Note that "NAN or INF" messages were reported due to viscosity,

which was not possible to be evaluated. This happened due to the bodies of the multi-bodydynamics have had diverged in the iterative procedure before.

OptiStruct 13.0 – support of partial transformation matrix outputCRQ_133877User can define now an appropriate node set and request a partial transformation matrixin .exb file with OptiStruct 13.0 by defining DISP = in I/O options section.

Utilities - Modal Stress Recovery - conversion modal stress to FEMFAT .fms formatCRQ_134726The modal stress data can be converted from an Abaqus .sim file to FEMFAT .fms files.For each mode a separate FEMFAT .fms file will be generated containing the direct gridpoint stresses, which have been requested at the condensation job. These files can be later

imported in FEMFAT together with the model scale factors to perform a fatigueevaluation.

Utilities - Modal Stress Recovery: text output improvedCRQ_134364Modal Data Recovery output of modal stress/strain data to text file has been reformattedto be more readable. Additionally, two sorting options are supported: sorted by steps andsorted by nodes. Finally the user can specify an individual set file containing nodes and/orelements for which text output should be made.

Utility - Data Recovery: alternative input of mesh dataCRQ_133254The data recovery tool supports now alternatively an input of mesh data also from nativeFE input and results files, instead of importing them just from an .exb file. Currently thefollowing formats are supported:

Abaqus: .inp and .odb Ansys: .cdbNastran/OptiStruct: .bdf and .op2

Utility - Prepare Section Forces: additional messages written to log fileCRQ_134387The user will get informed that the original .exb file will be backed up at first call. Inaddition statement 'END OF UTILITY' is written again to log file.

1.1.3. Reso lved Issues

2D Percentage Results: fringe color bar for clearance heightCRQ_132517


18/92


1-10 28-Feb-2015

For 2D percentage results the used inverted color bar has been changed to the AVLstandard color bar to show percentage values from blue (minimum) to red (maximum)also for clearance height quantities.

ACYG general results + GESP/OVCO results for run-up now availableCRQ_132032

ACYG overall contact (OVCO) as well as gearing specific (GESP) results for run-up arenow available. Appropriate results in frequency domain are not supported currently.

Advanced Cylindrical Gear Joint: log-output to aws_session.log might cause quota to beexceededCRQ_136947For models with multiple ACYG-Joints and enabled geometry modifications/correctionsthe aws_session-log file may grow in size significantly. Consequently, disk quota maybecome exceeded and jobs cannot be submitted. The problem has now been resolved bycleaning up the log-output.

Advanced Cylindrical Gear Joint: Root shape definition base on real gear incorrectCRQ_136148For the root bending stress calculation, if the root shape has been defined with reference

to the real gear (alternative to the default virtual spur gear), the 'Location (Y)'-valueexported to the solver was incorrect. On the solver side this was manifested by wrongbending arm distances h_Fyn. The problem has now been solved.

Advanced Cylindrical Gear Joint: Unit of tangent angle resultsCRQ_136149For the result-group 'Stress Results' for tangent angle output which defines the inspectedsections of the root curve is output in unit (deg). This output is incorrect since it must bein unit (rad). This issue has been corrected now.

ANCH body type as speed controller for run-upCRQ_130801When using a ANCH body type as speed controller for a run-up calculation, the depicted

reference time/angle did not start at the starting time/angle but with an offset. Asperity calculation did not consider surface layer deformation.CRQ_137093Hydrodynamic joints of type AXHD/EHD2/EPIL/TEHD: asperity calculation did notconsider surface layer deformation. This has been corrected.

Automatic setting of Load Reference and Interpolation/Extrapolation MethodCRQ_133144User defined Load Reference, Interpolation Method and Extrapolation Method are nowautomatically modified according to Load Item settings. For example, if user defined LoadItem is modified from non-constant to constant, Load Reference will be set to NONE andInterpolation/Extrapolation Methods will be empty. Reverse Load Item modification aresetting previous settings.

AVL Workspace GUI refresh extremely slow on some LINUX distributionsCRQ_137832Some of the latest NVIDIA Linux drivers cause a very slow refresh of dialogs in AVLWorkspace GUI. The problems have been observed under Red Hat Enterprise Linux, butit is possible that the problem is also visible in other Linux distributions. AVL Workspacehas been fixed now to avoid those problems.

AWS startup delayCRQ_102080Occasionally, AVL Workspace startup on Linux took several minutes. This problem wascaused by a discouraged usage of the FlexNet licensing API. The API is now usedproperly and the occasional very long startup times cannot be observed anymore.


19/92


28-Feb-2015 1-11

AXHD: oil supplyCRQ_134775Oil Supply definition check for the AXHD joint has been removed.

AXHD: thrust body profile motionCRQ_133134

Joints of type AXHD: when defining a profile on the thrust body surface, the profile didnot move correctly in circumferential direction with the thrust body during dynamicsimulation. This bug was fixed.

AXHD open flange: force integrationCRQ_134459In AXHD open flange applications, it was possible that the FE-nodes were not correctlysorted for the pressure-to-force integration. This led to forces which were applied on thewrong nodes. The bug was fixed.

AXHD: angle definition for open flange and boundary conditionsCRQ_136063For the AXHD flange definition, the angle direction for the open flange and the boundaryconditions should be dependent on the flange axis direction (given by "General->Flange

Geometry->Direction-Axis"), which was not the case up to now.Note: resolving this bug leads in some cases to a compatibility problem. If non-symmetricboundary conditions were used and the AXHD flange axis was given by a negative main-axis direction (e.g.: (0, -1, 0)) then the angle definition of the boundary conditions (andopen flange) has to be adjusted.

AXHD: assignment of boundary conditions on the HD-gridCRQ_134779In some cases it could happen, due to an internal calculation bug, that boundaryconditions of AXHD joints were one HD-element too small/large. Especially for thinboundary conditions this could lead to incorrect results. The bug was fixed.

AXHD: circumferential volume flow results are calculated in wrong coordiante

CRQ_133579Circumferential oil flow rates were calculated in the coordiante of the hydrodynamicmesh. The oil flow has to be mapped to the real coordiante. This bug is repaired.

AXHD: incorrect flange B.C. positioning if thrust body had an angular offsetCRQ_138568If the thrust body had an anuglar offset ('Body->Initial conditions->Initial Position andOrientation of Body Coordinate System') around the joint rotation axis, then this offsetwas also applied (in opposite direction) on the boundary conditions of the flange body.This bug is now fixed.

AXHD: crash at mean temperature modeCRQ_133989Joints of type AXHD using the "Mean Temperature" approach: the calculation crashed inv2014. The bug was fixed.

AXHD: open flange boundary condition discontinuityCRQ_136390If an AXHD open flange was defined from 0 to xx degrees, it could happen that theboundary condition was not continous at the 360/0 degree transition. Usually this hadonly a minor influence on other results than the boundary condition data. The bug wasfixed.

AXHD: options for parallel oil grooveCRQ_123489In general the description for all oil groove boundary conditions at AXHD joint has beenupdated. To explain the options - mirroring and through-going groove - for a parallel oil

groove, an appropriate figure has been added.


20/92


1-12 28-Feb-2015

Body Load Items tableCRQ_132506In the Load Data dialog, under tree node "Other: User defined", Load Items can beassigned to a body in a table. After removing the last item in this table, the simulationcould not be started or would produce wrong results since the loads were not preparedproperly for the related body. The problem is solved now.

Case set diagrams will work properly with negative speedsCRQ_134644Since speed was set to negative values, the generation of case set reports failed. The issuehas been fixed and x-axis shows now proper negative speed values in appropriatediagrams like e.g. for "Peak hold" and "peak firing pressure" results.

Case set report generationCRQ_134328Due to unification of log files all logging in Excite Res now uses excite_logfile module. Theobsolete function has been renamed accordingly.

CON6 reference rotation calculationCRQ_136325

If using loads which depend on a CON6-reference body with a defined reference node, theobtained angular reference was not continuous in some cases. As a result the appliedloads had a slight shift in phase, which caused sharp peaks. These influenced NVHinvestigations in particular . The specific bug was fixed.

Condensation w/ OptiStruct: no mass information available in .exb fileCRQ_122452Since OptiStruct v13.0, besides all property data for a flexible body, which are written toan .exb file directly, also the mass properties like total mass, center of gravity and inertiatensor are output, too. These values are helpful for model information and can be used fordefining a rigid body in EXCITE. Flexible bodies do not use these data at all. Note: as perconvention in OptiStruct the MASS MOMENTS OF INERTIA TABLE is output, the off-diagonal components have opposite signs compared to written inertia tensor in .exb filefor EXCITE.

Constant Load Items are now included in .L filesCRQ_132669Constant Load Items are now included in .L files, if the "Use Previous Load Files (.L)"option is used.

Co-simulation with more than 3 bodiesCRQ_135320Co-simulation with MATLAB or EXCITE Timing Drive: when connecting more than 3bodies, EXCITE Power Unit transferred the wrong position/velocity data to the other co-simulation program. In particular data of the 4th and all following bodies were wrongpopulated. The bug has been fixed.

Create flow tensor reportCRQ_133058The create flow tensor report crashed due to the big memory demand of the new Pythonscript. The Python script memory allocation is enhanced and the memory requirementsare not a problem anymore.

Create Model step wrongly countedCRQ_138146The number of warnings of the "Create model" step were always reported to be equal tozero. The counting did not work properly. The bug was fixed.


21/92


28-Feb-2015 1-13

Create ReportsCRQ_122525

A new task 'Create Reports' has been introduced to separate the report generation fromtask 'Create Results'. In addition the report generation for single cases is internally splitfrom the case set report generation, which will be submitted at the end as a separate jobonly after all case reports have been completed successfully. The Results Control settings

still control whether case or case set reports should be carried out. Finally it is possiblenow also to perform a case set evaluation on selected cases and not automatically for allcases defined in a case set. And progress is set to 100%, if the case and/or case set reporthas been completed successfully.

Define Node Connection dialog shows initial node connection sequenceCRQ_131610Node Connection Sequence shows node IDs when Define Node Connection dialog isopened. In previous versions this information was not available.

DMFM: execution stops after reading in from simulation.asix-fileCRQ_135827When using a DMFM joint with the torque generation unit 'Mean Torque' defined

dependent on engine speed, the solver stops right after reading in the joint data from thesimulation.asix file giving the following error-message:“ ASIX: set DMFM%meanTorqueInterpolationType to linear interpolation FORTRANPAUSE PAUSE prompt> To continue from background, execute 'kill -15 '” This problem has been solved now.

EHD contacts: 2D result data storageCRQ_132658The missing quantity - heat flux - has been added at description of storage of 2D EHDdata in the Users Guide.

EHD joints: sliding speed in analysis reportCRQ_126087For joints of type EHD2/TEHD the sliding speed in analysis report was wrong. The valuehas been corrected by a factor of 1/2.

EHD2: shell reference cylinder definitionCRQ_130389If the '0-deg shell angle' in the reference cylinder definition of an EHD2 joint was notgiven by a normalized vector, then a wrong geometry setup was possible.

EHD2+T: 2D results for lubricant temperatureCRQ_134495The problem was related to storing 2D data for a defined extra range with separateincrements incorrectly. The issue has been resolved in EXCITE kernel (CRQ 135268).

EHD2: transition velocity calculation for asperity contactsCRQ_133337If the 'Start transition velocity' (in the EHD2 - surface contact tab) was not equal to zero,then in some cases the computed transition factor was incorrect. This bug has beencorrected.

EHD2: friction force time step shiftCRQ_134297

A bug in the friction force extrapolation (if applied on bodies) implied a higher number ofrequired model loops. Hence EHD calculations which apply friction forces on bodiesshould be faster now. This has no influence on the results of a calculation.


22/92


1-14 28-Feb-2015

EHD2: increased accuracy of oil flow resultsCRQ_130517The 2D results for axial and circumferential oil flow as well as the flow over boundaryresults are now evaluated with increased numerical accuracy. This strongly reduces theinbalance between inflow and outflow at stationary operation. Hydrodynamic pressureresults are not affected by the changes.

EHD2: oil flow evaluation for bearings with non-cylindrical FE mesh correctedCRQ_106232The evaluation of oil flow over edges was incorrect for bearings with non-cylindircal FEmesh. This led to wrong outflow results and resulted in a notable disrepancy betweeninflow and outflow. The evaluation of flow over edges as well as outflow evaluation wascorrected. The sign convention was changed to that of the regular bearing. Positive signfor flow over edge meaning flow into the bearing. Hence, positive outflow means that oilis flowing into the bearing over its edges. Furthermore, slight modifications in the flowevaluation for boundary conditions improve result accuracy. There is now influence onpressure distribution or distributed flow results from these changes.

EHD2: orbital path angular offset corrected for unrecomended FE mesh configurations

CRQ_123714For EHD2 joints with center-surface coupling and regular structure mesh on the shellside the angular orientation of the orbital path was incorrect, if there were no shell nodeson the upper side of the bearing (0-deg direction). This was corrected. Now, orbital path isevaluated with respect to the 0-deg definition in the joint dialog for all configurations.

EHD2: removed bug for EXCITE FEA post processingCRQ_136799Some parts of the EHD2 joint direction information output, used by EXCITE FE Analysis,was incorrect. This could have lead to wrong results in e.g. generating a shell membranein EXCITE FE Analysis task – Linear Static Stress Analysis.

EHD2: shear term modification disregarded for 'Shear and Pressure Term Modification'CRQ_136139The shear term modification was disregarded when the option 'Shear and Pressure TermModification' in 'Consideration of Cell Inclination in HD Mesh' was selected. Instead, thestandard approach was used in the Reynolds Solver. With this release, modifications forboth terms are now considered which improves axial and circumferential flow results incase of strong inclinations. Pressure results are only mildly affected.

EMC: correction of inductive load in genset applicationCRQ_133226The inductive load description was corrected in the electric network of the EMC-joint. Incase of genset applications for the electrically excited synchronous machine (EESM) theinductance of the 'Load' element gave incorrect transient behavior and has beencorrected.

EMC: EESM in genset configuration gave wrong results in unit system other than SICRQ_133722The sensor for excitation and output voltage gave wrong values if the unit system was notSI. This is now corrected, identic results are obtained regardless of the FEM-preferences.

EMC: evaluation of forces for machine models considering eccentricityCRQ_131521For permanent-magnet synchronous machines (PMSM) considering eccentricity thecircumferential part of the machine force was incorrect. This caused a small shift of thedominant radial contribution. The evaluation of the circumferential force was correctedand verified with a reference FE simulation.


23/92


28-Feb-2015 1-15

EMC: FE based model for double-fed induction machine (DFIM)CRQ_132380Evaluation of the FE based model for the double-fed induction machine (DFIM) did notwork properly. An error message was issued in initialization phase. This issue wasresolved and results compared to a reference FE simulation, which showed very goodcorrelation.

EMC: restriction on data size removed for FE based electric machine modelsCRQ_130470The restriction on the size of data from FE simulation of approx. 10000 sampling pointswas removed. With this version the possible amount of sampling points is only restrictedby the hardware memory.

EMC: wrong behavior of the machine observer for the PMSM-torque controllerCRQ_134067For permanent-magnet synchronous machines (PMSM) the machine observer of thetorque controller was wrong in EXCITE Power Unit v2014 and v2014.0.1. The voltagerequest was strongly overestimated which resulted in an offset of the delivered torque tothe torque demand in case of acceleration and deceleration. This problem has been fixed.

The torque controller now follows the command much more precisely.ENHD: enhanced stabilityCRQ_125547For joints of type ENHD in some rare cases sudden sharp force peaks occurred, whichresulted in instable convergence behaviour. The force peaks were caused by a bug, whichappeared at very low journal eccentricities with respect to the shell center. The bug wasfixed.

Error message on externally loaded nodes addedCRQ_133959EXCITE v2014 did not deliver an error message if a load was applied to a node, whichwas not part of the model. This was corrected.

EHD contacts: error message text enhancedCRQ_132279Hydrodynamic joints of type AXHD, EHD2, EPIL, TEHD: the error message outlininginconsistent initial positions of connected body nodes with respect to the calculation gridwas enhanced. The enhancement should direct the user more directly to the critical partof the model.

Utility - Data Recovery: modal contribution factors calculation failsCRQ_132804

A side effect in resolving another bug in utility program 'exciteRecover' caused a failurein calculation of the modal contribution factors in v2014.0. The issue has been fixed.

Utility - Data Recovery: modal stress recovery for node sets failsCRQ_134484Due to side effects of resolving some enhancements the modal stress recovery for nodesets failed. The issue has been resolved.

FE Analysis - Linear Static Stress Analysis: input file for submodelCRQ_129378File '.ls' containing the load step information from the global model analysishas been wrongly deleted during the initialization cleanup. The appropriate file has nowbeen excluded from the deletion list.

FEA task Thermal Load Analysis - Add Temperature B.C. on FE SurfacesCRQ_133558When using the FEA task Thermal Load Analysis to create thermal B.C., under "AddTemperature B.C. on FE Surfaces", the temperature was interpreted in K but Abaqus

Thermal Analysis requires deg Celsius as input. This has been corrected now.


24/92


1-16 28-Feb-2015

FEA task Thermal Load AnalysisCRQ_133559When using the FEA task Thermal Load Analysis to create thermal BC, there is anoption to use data directly from file under "Add Temperature BC Include File". Afterclicking on the Add button there is an option Select, but it did not open file selectiondialog. The problem is solved now.

Flow factor calculations crahses when HD Grids Nx is less than NyCRQ_134485Flow factor calculations crahses if the number of HD Grids in x-direction is less than thenumber in y-direction. The bug is repaired.

Flowmaster bearing maps not generated in batch processCRQ_127304The utility did not handle the information of bearing dimensions for more than onebearing properly. Instead of using file 'bearingDimensions.dat' the information is nowhanded over via the parameter list at calling the utility script.

Flywheel whirl pre-processing scriptCRQ_134494

Due to restructuring the standard report functions and modules, the pre-processing scriptfor flywheel whirl evaluation failed. The Python script has been updated and works againproperly.

Flywheel whirl pre-processing scriptCRQ_136052The evaluation failed on Windows when the path names exceeded a certain length. Thepre-processing script has been updated to also work with such long file and directorynames.

FTAB: model creation fails if 3 DOFs are considered at onceCRQ_127298When 3 DOFs are considered at once in the FTAB joint, the internal joint name becomes

too long for the calculation kernel (example: 3@abc00) . The naming scheme has beenslightly improved now to better handle the situation when 3 DOFs are considered at once.Note: it still can happen that the internal name gets too long, for example if the index ofthe joint gets into two or three digit area.

FTAB: correct units displayed on Y axis for momentsCRQ_127834The units of the torque results were read as N.m instead of N.mm from the files whichlead to wrong axis scaling. This has been corrected and now proper units are shown.

GEAR: inconsistent initial angular velocitiesCRQ_137399With some models using a GEAR-joint, the simulation terminated with the error message5020004 right after the initialization phase. This was caused by an incorrect computationof teeth number ratio and distance to contact point ratio used for the indicatedcheck/error. The problem has now been resolved.

GEAR: 'Mesh' results not availableCRQ_134489Due to a problem with the binary database result channel storage no 'Mesh' results areextracted and shown in IMPRESS Chart. The problem has been solved now.

GUID: reference body for joint axisCRQ_119512In some cases GUID joint axis was not valid because the reference body for joint axis wasnot selected. After explicitly setting this in GUI, the problem disappears.

Hydrodynamics result data storage controlCRQ_135268Joints of type AXHD/EHD2/EPIL/TEHD: a bug in the hydrodynamics result data storage


25/92


28-Feb-2015 1-17

control was fixed. When referring to model.exc, in particular all definitions of kind JOINTOUT2 ... did not work in v2013 versions as well as in v2014.0.

Import Thermal Deviation & Temperature ProfileCRQ_133561If there was any error when using the "Import Thermal Deviation & Temperature

Profile" feature, the error messages were wrong. The correct messages are now shown.IMPRESS 3D: face selections in EXB filesCRQ_134773In some cases, IMPRESS 3D failed to read body result data reliably when face selectionswere stored in EXB files. IMPRESS 3D data checks have been extended regarding faceselection data and prevents loading of data if invalid.

Inconsistency between scalar results and EHD 2D resultsCRQ_131848When setting results storage increment less than 1 deg, EHD bearing scalar results areavailable for e.g. every 0.5 deg, but 2D results are available only for every 1 deg. It wasnot possible to plot EHD 2D results for increment below 1 degree. This has beencorrected.

Increase accuracy of outflow calculation for upper/lower shell applicationsCRQ_130513Joints of type EHD2/TEHD: when using upper/lower shell separately, the summedoutflow of the two edge parts did not exactly match the outflow of the complete edge. Insome cases differences of approximately 1% were seen. This was fixed by integrating bothresult data quantities by applying the same method, which is trapezoidal rule.

Information message for initial rotation of crank train systemCRQ_032828The information message for initial rotation of crank train system has been corrected inthe Users Guide.

Initial condition input remain disabled when unselecting calculation from Crank TrainGlobals (CTG)CRQ_132974The initial conditions (position and orientation) input fields are disabled when the initialcondition calculation from cranktrain is activated. When the CTG based calculation isdeactivated again the intital condition inputs remained disabled. This has been fixednow.

Internal Forces at Node available for ResultsCRQ_133794Internal Forces at Node check-box is enabled in Results for Selected Node depending onthe existence of element dictionary and element stiffness matrices in the referenced bodyproperty file (exb).

Interpolated, Constant Load ItemsCRQ_131594If an interpolated Load Item was defined as "constant" it has been omitted from thecalculation. The problem is solved now.

LCV loads wrong after switching to new load definition fileCRQ_133456With the new load definition in the file "simulation.asix", LCV loads were not consideredproperly. The following improvements are made:1. Interpolation type input in simulation.asix for the LCV loads is corrected. It could belinear or cubic, according to selection in Simulation Control|Advanced|LoadInterpolation within the Kernel.2. LCV load specification according time or angle is corrected. Selection is in Simulation

Control|Reference Body|[ ] Angle-Based Simulation Timing.


26/92


1-18 28-Feb-2015

Liner results for EPIL jointCRQ_124398

All EPIL 2D joint results related to liner including averaged results like heat flux arenow represented consistently over the entire liner height.

Load Item 'Acceleration (Translation)'

CRQ_134376Load Item of type 'Acceleration (Translation)' is removed from GUI, since it is not yetfully supported.

Load Reference selection for the Load ItemsCRQ_134227

Available load references and extrapolation modes are now adjusted to fit to the type andcharacteristics of the defined load table. If a wrong or unsupported load reference hasbeen specified in an existing EXCITE model (saved with previous excite versions), theload specification is automatically corrected after the model is loaded.

Loading Driveline joints from command lineCRQ_137711There was a problem when starting aws and loading EXCITE Power Unit models directly

from the command line, if that model file name was specified as a relative path.Specifically, the models containing Torque Converter, Dual Mass Flywheel or ClutchJoint were affected. Loading the same model using File->Open was working properly.

Also loading the model from the command line was possible if an absolute file path wasprovided as an argument. This problem has been fixed now.

MATLAB with EPCL/DMFM linkCRQ_132766When using a MATLAB joint in combination with the EPCL/DMFM joint a solverinternal error message "PINFO2: Internal error due to jType" was issued. This bug wasfixed.

Memory leak at GIDAS file handling module

CRQ_134481Memory leaks at the GIDAS file handling module have been fixed. This should avoidPython crashes especially when requesting huge amount of result data like e.g. run-upresults.

Micro-Contact Analysis report generation fails on WindowsCRQ_132803When processing large amounts of data, Micro-Contact Analysis report generation mayfail on Windows platforms. Appropriate issues related to report generation with largeamount of data in Micro-Contact Analysis have been resolved.

Microslide Analysis: wrong flow factors calculatedCRQ_135457In v2014 the Miocroslide analysis did not calculate the Patir & Chen flow characteristiscorrectly. The mean square root roughness / orientation was not stored in the right waytherefore the values were missing later, which leads to zero values for the flow and stressfactors. This problem is solved.

MSC Nastran interface: ASET dofs will be removed from USET listCRQ_134839For a partial recovery matrix an USET1 entry is used to define the subset of omitteddegrees-of-freedom. Since the list also contains already defined dofs from the ASET, MSCNastran will remove the appropriate dof internally but only when using LANCZOS aseigenvalue solver and not for ACMS domain solver. To overcome the problem, EXCITEFEA now eliminates the appropriate ASET dofs from USET list before writing to thecondensation input file.

MSC Nastran interface: no mass information available using option 'mode=i8'CRQ_132706


27/92


28-Feb-2015 1-19

When running MSC Nastran 64-bit code using command line option 'mode=i8', the bodymass properties are not available in the body property file. All DMAP files have beenupdated accordingly to get proper mass information in the bpdy property file (exb).

Non-constant Load Item tableCRQ_133567

If Load Item is non-constant, the definition table must contain at least two rows. If thetable has only one row, Load Item is undefined and is not considered during simulation.

Non-interpolated CONSTANT Load ItemsCRQ_132673Constant Load Items were not displayed when the "View All" button was selected for theLoad Items table. The problem is corrected now.

AXHD: oil in/out flow are to be caclulated in the real coordinatesCRQ_133581Oil in/out flow were calculated with respect to the joint coordinate system (HD grid)coordinates. A coordinate transformation was missing, which has been added now.

Oil Properties Database: application crash on "View in Impress Chart" with dummy input

valuesCRQ_121256If some dummy values are entered for oil properties, the application would crash afterusing "View in Impress Chart" function.

AXHD: oil side leakage results is restructuredCRQ_133768

A bug in calculating the oil flow of axial thrust bearing at inner and outer raduis wasrepaired.

Orbital path evaluationCRQ_135290The description as well as figure and formulas for the orbital path evaluation have beenupdated.

Order legend will no longer have any unit listed in case set reportsCRQ_131447Generally case set results as order cuts like e.g flywheel motion got now a clean legenddescription without any unit.

OSL: angle based calculationCRQ_135458When an oil supply line was used in combination with an angle based simulation, somequantity updates were weighted with the angle step size instead of the time step size,which in turn led to wrong results.

Piston skirt profile generation from FE thermal analysisCRQ_137721

As a piston skirt usually has a large no-contact area, any FFT filtering did not workproperly and delivered strange thermal deviation profiles. This is resolved now byapplying averaged values in the no-contact area and using a surface smoothing algorithmin contact areas to smoothen the profile data. Both features can be controlled via GUI.

Predefined motion for a bodyCRQ_120579If a predefined motion was used for a body and at the same time the initial conditionswere defined with empty input fields, the models would not run, even if the initialconditions should actually be ignored. The problem has been fixed now.

Result organization in IMPRESS Chart corrected for EMC jointCRQ_134323

In the result tree of IMPRESS Chart the electric component results were not organizedproperly. Results of all electric components connected to one electric machine (EMC joint)


28/92


1-20 28-Feb-2015

were grouped in one common sub-folder of the electric machine. Now results are arrangedin sub-folders for each electric component, hence making accessibility and recognition ofresults easier. This corresponds to the arrangement used in versions v2013.x.

Results: wrong unit group for peak thermal loadCRQ_129679

For EHD result quantity 'Peak Thermal Load' the unit group has been changed frompower to thermal load.

SCIM Squirrel Cage Induction MachineCRQ_124717When 'Electric Machine Type' is 'Squirrel Cage Induction Machine' and 'Help' is selected,an error message saying "Undefined Help Item" appears. The issue has been resolved.

Speed controllerCRQ_130794Models without any applied external loads but with enabled speed controller (for instancefor a run-up ramp): in such cases the controller did not influence the controller body. Sono control happened. The bug was fixed.

Standard Reports (Case Set) - correct unit for torsional vibrationsCRQ_115495Units for torsional vibration results in case set reports are now set properly to radians.

Standard Reports (Case Set): legend labels corrected for torsional vibrationsCRQ_115496Legend has been corrected for torsional vibration results in case set reports and shownow correct bodyname/node combination for each graph.

Standard Reports: oil outflow resultsCRQ_134443Due to enhancements of oil inflow and outflow results in v2014 the Gidas file andChannel names were changed but were not assigned to the standard report evaluationproperly. Standard report Python scripts have been updated accordingly.

Tools - Extract Case Set Results failsCRQ_134632The Extract Case Set Results tool failed because some imported Python modules were notfound. The modules are now available at the right location and tool works again properly.

Utilitiy - Data Recovery: Magnitude/Phase Punch outputCRQ_133730When writing recovered results to a Nastran Punch file in frequency domain formagnitude/phase values, the phase values have been written in degrees instead ofradians. Now the proper unit for phase values is written to the Punch file.

Utility - Data Recovery: format of external recovery matrixCRQ_132685In some cases when the Utility Data Recovery uses an external recovery, the matrix maystop without an obvious error. The problem may be caused by a Python error atrecognition of the format of the external transformation matrix. The issue has been fixed.

Utility - Data Recovery: models with huge external recovery matrixCRQ_132303The problem was related to checking the format - ASCII or binary - of the recovery matrixin Python script for utility Data Recovery. Unfortunately Python started to read theentire matrix and caused a memory overflow. A new proper working function for fileformat checking has been implemented to overcome the problem.

Utility - Modal Strain Recovery: principal strain data do not matchCRQ_130266

Comparing principal strain results from modal data recovery to either linear stressperturbation steps or measurements offer too high deviations. The problem has been


29/92


28-Feb-2015 1-21

fixed by correcting the shear components in evaluation formula, which have to be dividedby 2 for principal strains.

Utility - Prepare Section Forces fails to startCRQ_132808The utility 'Prepare Section Forces' fails to start due to an installation issue. Three

specific Python files are added in a common Python library path.Utility - Prepare Section Forces: given pin & journal nodes not sorted properlyCRQ_134470So far the given nodes for journal and pin center are sorted by labels. This caused awrong assembly of the element dictionary table as well as wrong calculation of theelement stiffness matrices, since node labels are not modeled in ascending order. Now thesorting is based on nodal coordinates in crankshaft axis direction and delivers properelement dictionary table and element stiffness matrices.

Visualization of the Load Item curvesCRQ_132750If the defined range for some load curve is less than the visualized range, missing valuesshould be extrapolated according to "Extrapolation mode" specified in the load

assignment.

Wear analysis failed for models using length units in meterCRQ_134640When using model units in N-m-s the wear evaluation failed. The issue has been fixed.

Wind Turbine Solution PackCRQ_132291Unnecessary warning messages for the Wind Turbine Solution Pack have been removed.

Wrong unit group is set in Case Standard Reports for motion amplitudes forForce/MomentCRQ_132518Standard case reports show a wrong unit group, namely Ratio (-), for requested Motion

Amplitude results for the quantities Force and Moment. The reports will show nowcorrect units.

1.1.4. Installat ion Examples

100_General EXCITE Power Unit: General Model

General_Example1

Purpose of this model is to understand in

general the Excite workflow with simple and

understandable bodies and joint for the

simulation and result evaluation

General_Example2Example based on General Example1 – with

duplicated bodies and joints.

General_Example3Example based on General Example2 with

different shaft and joint definitions.

General_Example3_extendedExample based on General Example3 with

extended body and joint definitions

101_Primer EXCITE Power Unit: Simple 1 cylinder

engine

Primer_FEM_NONL_abq

Common EXCITE model setup and basic

presentation – Nonlinear joints, 3D structure

based on Abaqus matrices

Primer_FEM_ENHD_abq Example based on Abaqus matrices,

advanced bearing joint investigation with


30/92


1-22 28-Feb-2015

enhanced hydrodynamic properties.

Primer_FEM_NONL_abq_runup

Example in which increasing speed range is

defined (speed is increasing over time interval)

– Abaqus matrices.

Primer_SHM_NONL_abq

Simple example with Abaqus matrices for

Block body. Crankshaft body is built with ShaftModeler.

Primer_Designer

Simple 1 cylinder engine in EXCITE Designer

mode. Torsional vibrations are analyzed.

Crankshaft model defined with Shaft Modeler.

Primer_MatlabExcite Co-simulation with MATLAB/Simulink.

Clutch analysis.

Primer_FEM_NONL_nas Excite model based on MSC.Nastran matrices.

102_I4_demo EXCITE Power Unit: 4 Cylinder Engine

I4_demo_CS_SHM_abq_enhd_sweep

Crankshaft Dynamics, Shaft ModelerCrankshaft body, enhanced hydrodynamics

main bearing definition, single speed definition.

Block based on Abaqus matrices

I4_demo_CS_FEM_nas_enhd_sweep

Crankshaft Dynamics, Crankshaft Finite

Element Model with Nastran input files. ENHD

main bearing definition, single Speed definition.

I4_demo_CS_FEM_abq_enhd_sweep

Crankshaft Dynamics, Volumetric Crankshaft

body and block based on Abaqus input files,

ENHD main bearing definition and for single

speeds.

I4_demo_PU_SHM_nas_nonl_sweep

Based on Nastran files, external loads from

EXCITE Piston&Rings and EXCITE Timing

Drive. Crankshaft body is built up with Shaft

Modeler.

Used for NVH analysis.

I4_demo_PU_FEM_abq_nonl_sweep

Power Unit Data Recovery with Abaqus files.

External loads from EXCITE Piston&Rings. Co-

simulation with EXCITE Timing Drive.

I4_demo_CS_FEM_nas_ehd_sweep

Crankshaft Dynamics with Nastran Finite

Element body definition. Detailed EHD main

bearing definition.

I4_demo_CS_SHM_abq_ehd_sweep

Crankshaft Dynamics with Abaqus Finite

Element body definition. Crankshaft body is

built up with Shaft Modeler. Detailed EHD main

bearing definition.

I4_demo_CS_FEM_abq_nonl_sweep

_AXHD and

I4_demo_CS_FEM_nas_nonl_sweep

_AXHD

Detailed axial bearing analysis. Axial

Hydrodynamic (AXHD) joints are included.

I4_demo_PU_FEM_abq_nonl_sweep_

fric

This model is based on

I4_demo_PU_FEM_abq_nonl_sweep example.

Only external loads from EXCITEPiston&Rings are used. Friction settings and


31/92


28-Feb-2015 1-23

results are available.

I4_demo_combined_body

In general Nastran matrices are used for input.

Crankshaft body is built as a combination of

volumetric and structured FE models.

I4_demo_Matlab

This model is for engine mount joint analysis,

co-simulated with MATLAB/Simulink program.It is based on

I4_demo_CS_SHM_abq_enhd_sweep

example. Engine Mounts are frequency

dependent.

I4_demo_PU_FEM_abq_nonl_TDcosim

I4_demo_PU_FEM_nas_nonl_TDcosim Co-simulation Models with Timing Drive

103_Bearing Main Bearing Wall Analysis

MainBearing_EHD_abqDetailed bearing analysis, Strength evaluation,

Abaqus matrices, with detailed thermal BC

MainBearing_EHD_nasDetailed bearing analysis, Strength evaluation,

Nastran matrices

MainBearing _EHD_ansDetailed bearing analysis, Strength evaluation,

Ansys matrices

104_Conrod Conrod Analysis

Conrod_abaqus Detailed bearing analysis, safety evaluation

Conrod_nastranModal Stress Recovery with load history files

included.

105_Piston Detailed Piston Calculation

Piston_hydroPiston/Liner analysis using EPIL joints for

Abaqus, Nastran and Ansys matrices

105a_Piston Detailed Piston pin Calculation

Piston_pinPiston/Liner analysis using EPIL joints for

Abaqus matrices with floating pin definition

106_EMO1 Engine mount definition

emo1_example Engine Mount joint definition

107_I4_demo_TransmissionManual EXCITE Power Unit: 4 Cylinder Engine +Manual Transmission

I4_demo_TransmissionManual_NVHTransmission Manual model for NVH

evaluation (gear noise)

I4_demo_TransmissionManual_rigidTransmission Manual model for Engine Mount

evaluation

108_I4_demo_TransmissionAutomatic EXCITE Power Unit: 4 Cylinder Engine +

automatic Transmission

I4_demo_automatic_transmissionTransmission Manual model for NVH

evaluation (gear noise)

114_UDJ User Defined Joint


32/92


1-24 28-Feb-2015

UDJ_LISP_example Short EXCITE example with Fortran code

115_UD_PostProcessing EXCITE Post Processing

Power.pp2 Basic information about Python

116_EMount_Concept_I4 Inline engine in concept phaseEMount_Concept_Ri3DBlock-6DOF Simplified engine geometry in concept phase

EMount_Concept_Ri3DBlock-6DOF_

runup

Simplified engine geometry with increasing

speed over the time.

117_ConceptPhase_V6 V-type engine in concept phase

V6_mweb_designer Simplified V6 engine in designer mode

V6_mweb_3d_enhd_N-NV6 engine using main bearing node-node

connection in enhanced hydrodynamic joints

V6_mweb_3d_favourites Favorites Designer options described

118_TemplatesTemplates / Hints on how to solve realistic

problems with EXCITE program

119_LargeEngine Ship Engine Model

1.2. EXCITE Designer

1.2.1. New Features

1.2.1.1. Mount Layout Tool: Damped Modal Analysis

In addition to classical (undamped) modal analysis, one can perform now damped modalanalysis of mounts supporting rigid engine/power unit. This is available as a separatetask:

Both viscous and visco-elastic (material) damping types are taken into account – thisenables to analyze viscous and rubber mounts.

In addition to the existing results, the following new ones are generated:

1. Decay rates and corresponding traces (magnitude vs. time), showing the vibrationrelaxation behavior of the system with damping:


33/92


28-Feb-2015 1-25


34/92


1-26 28-Feb-2015

2. Mode shapes in 2D, available both in results shown in GUI and in the IMPRESSChart report: for displacements (normalized unit-less motion magnitudes, as well as

phases); for kinetic energy rates (in %).

3. Point trajectories are now shown during mode animation, giving a betterimpression of 3D motion (in case of viscous damping the trajectories becomeclosed-loop curves).


35/92


28-Feb-2015 1-27

1.2.1.2. Mount Layout Tool: Other GUI Viewer Enhancements

Default 3D perspective view (from “top-front-left” direction) of the vehicle;

Engine part and mount labels:

Exploded view:

Different vehicle chassis (parametrizable):


36/92


1-28 28-Feb-2015

1.2.1.3. Torsion: Equivalent Speed Dependent Stiffness of ViscousDamper (for use in EXCITE Power Unit)

If the element stiffness is frequency dependent (the usual definition of viscous damper),then it can be re-calculated using the Torsion task of EXCITE Designer into anequivalent speed dependent stiffness. The transformation is based on equivalence of

kinetic energy.

This additional result can then be used in EXCITE Power Unit to model the sameelement with equivalent speed dependent characteristics (together with already existing

result of equivalent speed dependent viscous damping).


37/92


28-Feb-2015 1-29

1.2.2. Enhancements

Mount Layout: improvementsCRQ_1293671. Pull-down lists for copying power unit components and mounts are now empty bydefault. When nothing is chosen the copy button will skip the process.

2. The speed table for selecting simulation speeds has been moved to the simulationsection.3. The "Show report/results" button has been moved to the results section.

Mount Layout: increased maximum number of mounts and power unit componentsCRQ_130342Maximum number of mounts and power unit components is increased to 20.


MBLoad: too tight a tolerance for checking the crank pin positionCRQ_132806In MBLoad, there was an unreasonably high accuracy threshold set for checking theconsistency of the crank pin position. Tolerance is now changed to 1% of crank radius.

Mount Layout Tool: no coordinate transformation for constant torque and dynamic loadsCRQ_132805The vector of constant torque (engine torque) and the variable components of dynamicload (coming from Unbalance) are specified per definition in power unit (relative)coordinate system. These had to be transformed into vehicle (absolute) coordinate systembefore using them for solution. Fixed with v2014.0.1.

Mount Layout Tool: percentage of kinetic energy in modes not exactCRQ_132812In modal analysis results, the calculation of percentage of kinetic energy in modesassumed up to now a diagonal tensor of inertia, and therefore could not be exact (i.e. the

sum of percentages for different motion components within a mode could differ from100%, and in some cases, the percentages could even become negative). This has beenmodified now to take tensor of inertia of general type into account, too.

Standard Report: irrelevant or misleading messages in logCRQ_122323EXCITE Designer tried to generate a standard report for the tasks which did not run (i.e.were not selected), instead of skipping them. As a result, multiple irrelevant ormisleading warning and error messages were generated.

Standard Report (Torsion): names of Elements/Nodes missing in report for Torsional AnalysisCRQ_132810

Names of Elements/Nodes are written to the legend in the Torsional Analysis reportagain.

Standard Report (Torsion): generation fails for systems with frequency-dependentstiffnessCRQ_132811In v2014, Torsion report generation failed for systems with frequency-dependent stiffness(this worked with v2013.X).

Standard Report (Torsion): shear stress synthesis curve missingCRQ_134591In v2014, shear stress synthesis curves were missing in the Torsion report, which werepresent in v2013.2.


38/92


1-30 28-Feb-2015

1.2.4. Installat ion Examples

121_Designer_I4 4 Cylinder Engine Analysis in EXCITE Designer

IL4Bearing Analysis, Torsional Vibration Analysis, Strength

analysis

IL4_AdvMaterial Advanced material definition (Haigh)

IL4_GoughPollard Gough Pollard Method

IL4_MBLoad Calculation from Main bearing loads

123_Designer_I4_driveline 4 Cylinder Engine Analysis in EXCITE Designer

IL4_driveline Branched system up to wheels added to the model.

124_Designer_I4_timingdrive-

belt4 Cylinder Engine Analysis in EXCITE Designer

Designer_I4_timingdrive-belt Additional camshaft bodies and timing belt areincluded.

141_ShaftModeler_cs4_1 Shaft Modeler Example

cs4_1

Basic options in Shaft Modeler are presented.

Structural properties of webs and disks calculated

externally using volumetric FE Model

(Patran/Nastran/Scripts); AutoSHAFT not used.

142_Shaftmodeler_i4_disksAutoSHAFT analysis in combination with Shaft

Modeler

i4_ast_disksCrankshaft Geometry based on 3D CAD model (STLformat). Structural properties of webs and disks are

calculated with AutoSHAFT.

143_ShaftModeler_i5 5 Cylinder engine AutoSHAFT analysis

i5Structural properties of a single web calculated with

AutoSHAFT; results copied to other similar webs.

144_ShaftModeler_v6_disks V6 – type crankshaft in Shaft Modeler

v6_ast_disks A V –engine crankshaft with split pin for Shaft Modeler/

AutoSHAFT


39/92


28-Feb-2015 1-31

1.3. EXCITE Piston&Rings

1.3.1. 3D Pisto n Ring

1.3.1.1. Basic Description

In the 3D Piston Ring Dynamics Module, the 3rd dimension, which is the circumferentialdirection, is added to the piston ring analysis domain. The ring is discretized into acertain number of 3D beam elements in circumferential direction. Each element has 2nodes and the displacement at each node has 6 degrees of freedom (DOF).

Figure 1-1: 3D Beam Element

This results in a 12x12 stiffness matrix for each element and a 6x6 mass matrix for eachnode. The stiffness and mass matrices as well as the element force vector are thenassembled, and the resulting system of equations is solved iteratively.

There are two approaches to generate the stiffness and mass matrices, as shown in thefollowing figure.

Figure 1-2: 3D Ring Body Modeling Workflow


40/92


1-32 28-Feb-2015

The main approach is to use the integrated 3D Ring Modeler , which is described in thesection 1.3.1.2. The geometrical input data required for 3D ring modeling is the samewhich is used for 2D ring modeling: cross section, bore and gap. Additionally, one has tospecify Poisson’s ratio in material data of the ring.

The 3D model of ring body can be generated for any type of cross section specified by its

contour (the same geometrical data specification as for 2D modeling). The number ofnodes (mass points) on the ring is specified by the user.

An alternative approach is to use any of the EXCITE supported Finite Element Packagesto generate these matrices of the 3D-beam element and save them in the exb-file format.

The following figure shows how to activate 3D ring modeling.

Figure 1-3: Ring Simulation Control Activating 3D Ring-Pack Modeling Approaches

All the ring forces used in the 2D modeling are applied at each node (ring mass point) asit is shown in the following figure.

Figure 1-4: Ring Forces

The hydrodynamic and asperity contacts are evaluated at each ring segment.


41/92


28-Feb-2015 1-33

1.3.1.2. 3D Ring Modeler

The 3D model of piston ring body is generated based on the same principles as structuredmodels of crankshafts and plain shafts (NOD6 type bodies in EXCITE Power Unit) usingEXCITE Shaft Modeler. Such a model contains lumped masses connected by elasticelements.

The ring is discretized into equal lumps with the nodes placed in the centers of respectivesegments. The connecting elastic elements are approximated by solid bars.

When running the Ring Dynamics task with the 3D Ring Model option, the 3D model ofthe ring body (stiffness & mass matrices, element connectivity, coordinate system, …etc.)can be viewed using EXB-Explorer. The EXB-Explorer can be started from the Tools barmenu in Excite Piston&Ring GUI.

Figure 1-5: Assembled 3D Ring Body Model in EXB-Explorer

The 3D model of the ring body (nodes and connecting elements) can be visualized and itsnatural modes can be animated using AWS PP3 by loading the respective .mod files.

Besides that, an .xml file for each ring contains the list of natural frequencies and theidentification of modes based on share of kinetic energy components.

Figure 1-6: 3D Ring Body Model in AWS PP3: visualization left) and

animation of normal modes right)


42/92


1-34 28-Feb-2015

Additionally, the 3D surface of the ring can be viewed by loading the respective .stl filesinto IMPRESS 3D.

Figure 1-7: 3D Ring Body surface visualization in AWS Impress 3D

1.3.1.3. 3D Piston Ring Simulation

All the results data generated by the 2D Ring Dynamics Module are available also for the3D Ring Module. Additionally the following files are created for each ring.

TF.SD1 Binary file contains the scalar results of the top flank

BF.SD1 Binary file contains the scalar results of the bottom flank

RF.SD1 Binary file contains the scalar results of the ring runningface

TF.2D1 Binary file contains the top flank 2D results

BF.2D1 Binary file contains the bottom flank 2D results

RF.2D1 Binary file contains the 2D results of the ring running face

1.3.1.3.1. Result files used by IMPRESS Chart

These files are saved in a binary format equivalent to the format used with EXCITEPower Unit. When submitting Simulation -> Create results the results are converted intoGIDAS format and can be visualized using IMPRESS Chart.

The following list of new ring dynamics variables is available in the results tree.

Scalar Results

Ring Top/Bottom Flanks

o Peak Total Pressure

o Angular Position of Peak Total Pressureo Radial Position of Peak Total Pressure

o Peak Oil Film Pressureo Angular Position of Peak Oil Film Pressureo Radial Pos. of Peak Oil Film Pressureo Peak Asperity Pressure

o Angular Position of Asperity Pressure

o Radial Position of Asperity Pressure

Ring Running Face

o Peak Total Pressure

o Angular Position of Peak Total Pressureo Axial Position of Peak Total Pressure


43/92


28-Feb-2015 1-35

o Peak Oil Film Pressureo Angular Position of Peak Oil Film Pressureo Axial Pos. of Peak Oil Film Pressure

o Peak Asperity Pressure

o Angular Position of Peak Asperity Pressure

o Axial Pos. of Peak Asperity Pressureo Asperity Friction Power Losses o Hydrodynamic Power Losseso Total Power losseso Minimum Oil Film Thickness

o Angular Position of Minimum Oil Film Thickness

o Axial Pos. of Minimum Oil Film Thickness-Running Face

o Gas flow along the land in the circumferential directiono Gas flow along the groove behind the ring in the circumferential direction

2D Results

Ring Top/Bottom Flanks

o Total Pressureo Hydrodynamic Pressure

o Asperity Contact Pressure

o Clearance Height

o Total Shear Stress

o Hydrodynamic Shear Stresso Asperity Contact Shear Stresso Asperity Contact Ratio

Ring Running Face

o Total Pressureo Hydrodynamic Pressureo Asperity Contact Pressure

o Total Shear Stress

o Hydrodynamic Shear Stress

o Asperity Contact Shear Stress

o Clearance Heighto Asperity Contact Ratioo Oil Film Thicknesso Fill Ratio

1.3.1.3.2. Result files used by IMPRESS (3D Animation)

The following files are created by the 3D Ring Dynamics Module for each ring and can beused directly by IMPRESS 3D.

.SD1 Binary file contains the ring/body variables

TF.2D1 Binary File contains the top flank 2D results

BF.2D1 Binary File contains the Bottom flank 2D results

RF.2D1 Binary File contains the running face 2D results

The following variables are available for 3D animation:

Ring Top/Bottom Flank

o Total Pressureo Hydrodynamic Pressure


44/92


1-36 28-Feb-2015

o Asperity Contact Pressureo Clearance Heighto Total Shear Stress

o Hydrodynamic Shear Stress


o Asperity Contact Ratio Ring Running Face

o Total Pressure

o Hydrodynamic Pressure

o Asperity Contact Pressure

o Total Shear Stresso Hydrodynamic Shear Stress


o Clearance Height

o Asperity Contact Ratioo Oil Film Thickness

Body Variables

o Translational Acceleration

o Angular Acceleration

o Translational Velocity

o Angular Velocityo Displacemento Inertia Force

The following figure is an example of an animation of total pressure magnified at runningfaces & colored at bottom/top flanks (different scaling top ring – 2nd/3rd ring).

Figure 1-8: Ring State Variables Animation in 3D


45/92


28-Feb-2015 1-37

1.3.2. Enhancements

3D Ring gas pressure channelsCRQ_134171

Added new 3D Ring gas pressure channels

Friction modelCRQ_129264

A new friction model is implemented. The manuals are updated accordingly.

Problems occur if the number of contact points on piston exeeds 250CRQ_127502In previous version, problems occur if the number of contact points on the piston surfaceexeeds 250. The data field depending on the number of contact points is restructured andits required memory is allocated dynamically.

Ring Force resultsCRQ_132426Ring Force results are now provided also for models with more than five piston rings.


3D Ring Body AnimationCRQ_130252The problem in 3D Ring Body Animation occurred due to the difference between elmentsinternal and external numbering.

Body coordiante systemCRQ_137323In ring animation, the body coordiante system does not match the hydrodynamicscoordinate system. This bug is repaired.

Checking out the license for Ring DynamicsCRQ_135932The problem of checking out the license for Ring Dynamics is resolved.

Different volumes for Land 1 for TS & ATS w/o considering piston secondary motionCRQ_132807

A bug in calculating the contribution of liner ovality to the land volume in v2013.2 hasbeen repaired.

Duty factor does not match the friction coefficient

01 excite release notes

Documents