release notes 25 - vi-grade you are reading these release notes as hardcopy (pdf document), please...

© 2008 - 2017 FEV Europe GmbH

1

25.1

Release Notes

http://www.fev.com/what-we-do/software/virtual-engine-powertrain-dynamics-simulation.html


2

Table of Contents

4Supported Operating Systems

5Licensing and Hardware Requirements

6Functional Changes and Enhancements

10Corrections

12Known Issues



3

Dear reader,if you are reading these Release Notes as hardcopy (PDF document), please be aware that actually thesame document is also part of the FEV Virtual Engine online documentation ("help"):In the online version the Release Notes contain hyperlinks to the relevant help topics - which is usually veryhelpful to locate and learn about new functionality.

These are the release notes for FEV Virtual Engine 25.1. This release supports the Adams 2017.1.0 release.

Unless otherwise indicated, all statements made within this document regarding product changes refer tothe previous release FEV Virtual Engine 24.2, 25.0.

The following icons mean:

refers to FEV Virtual Engine versions running on Windows® operating systems only

refers to FEV Virtual Engine versions running on Linux® based operating systems only

If no icon is depicted the text refers to both versions equally.

This document is grouped into the following sections:

– Supported Operating Systems

– Licensing and Hardware Requirements

– Functional Changes and Enhancements

– Bugfixes

– Known Issues

Product and company names mentioned in this document may be either trademarks and/or registered trademarks of therespective owners / companies. The publisher and the author make no claim to these trademarks.

MSC, the names of MSC software products (such as Adams, Nastran) and services, and the MSC.Software corporate logo aretrademarks or registered trademarks of the MSC.Software Corporation in the United States and/or other countries.

Windows and the Windows logo are registered trademarks of Microsoft Corporation in the United States and other countries.

Linux is a registered trademark of the Linux Mark Institute, exclusive licensor of the Linux trademark on behalf of its owner, LinusTorvalds.

Red Hat and Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and other countries.

SUSE is a registered trademark of SUSE LINUX Products GmbH, Novell business.



4

Supported Operating Systems

Following operating systems are currently supported:

Windows® 7 (x64), 10 (x64)

Red Hat® Enterprise Linux® (RHEL) 6.7 (x64), 7.1 (x94)

SUSE® Linux® Enterprise Server (SLES) 11 SP3 (x64)

Following Adams® versions are currently supported:

Adams® 2017.1.0

You have to install a version of FEV Virtual Engine which is appropriate for your Adams® base installation.In case of installing FEV Virtual Engine S (stand-alone) you don't have to care about this, because FEVVirtual Engine S includes the appropriate Adams Framework.

Your operating system must be set up / configured properly and working. This also applies to your access toyour local network (LAN) when using a floating license.



5

Licensing and Hardware Requirements

Licensing Requirements

The release FEV Virtual Engine 25.1 requires FEV Licensing 4.21.

Hardware Requirements

The requirements regarding hardware basically are those of AdamsÒ, on top of which FEV Virtual Engine isrunning as vertical application:

– up-to-date CPU, multi-core CPUs are recommended

– at least 2 GB of memory (RAM), recommended: 4 GB or more

– a graphics adapter which supports OpenGL 1.2 or later (see below for recommended models and drivers)

– enough free space on your harddisk: at least 8 GB for installation and operation

– network adapter, when using a floating license

Graphics adapter cards and drivers

The recommended graphics adapter cards and drivers are these:

NVIDIA Quadro FX 580: NVIDIA Version 340.66 (avoid 310.19)

RHEL: NVIDIA Quadro FX 580: NVIDIA Version 331.67

SLES: NVIDIA Quadro FX 580: NVIDIA Version 331.79

Display(s)

The displays must have a resolution of at least 900 px in height.



6

Functional Changes and Enhancements

Improvements

EHD Bearing simulation

Two-sided elasto-hydrodynamic analysis. The EHD-Journal Bearing model now includes the two-sidedelasto-hydrodynamics, i.e. on both the journal side and the bearing shell side. Previously the one-sidedelasto-hydrodynamic approach enabled the user to couple the bearing with the bearing shell surface whilethe coupling to the journal used journal center line nodes. With the two-sided elasto-hydrodynamic journalbearing approach now also the the journal surface can be used for coupling. For journal bearings with a stiffjournal design, e.g. main pin bearings or crank pin bearings, the one-sided elasto-hydrodynamic journalbearing approach gives the best combination of physical representation and computational performance.When journal design with a lower stiffness is provided, e.g. hollow journals or piston pins, significant surfacedeflection may occur under load. Here, the two-sided elasto-hydrodynamic journal bearing approach willconsider the surface deflection in detail and also apply the pressure distribution on to the journal surface.

Advanced Wear Analysis. Wear in journal bearings typically occurs when the hydrodynamic contact isalso accompanied by the presence of asperity contact. Previously the wear on the bearing was onlyprovided as "wear indicator" and as a post-processing result. The advanced wear analysis now evaluateswear not only for the bearing surface but also for the journal surface. Thus any wear-loaded region on bothjournal and bearing surface can be easily identified and quantified.

Advanced Wear Analysis with Shape Modification. Additionally the advanced wear analysis is capable toremove material from the bearing and the journal surface during the dynamic analysis which allows to mimicthe effect of real wear. The shape modification resulting from material removal may help to rate the durabilityof the journal bearing.



7

Elasto-hydrodynamic analysis with a user-defined mesh. Previous releases restricted the elasto-hydrodynamic journal bearing analysis to a hydrodynamic mesh which was directly derived from the flexiblebody surface mesh, which implicated a FE-mesh with adequate resolution in the bearing area. With the newoption of a user-defined mesh that restriction becomes obsolete. The user may now define a hydrodynamicmesh with a resolution along the axial and the circumferential direction. The structural dynamics andpressure distribution will then be mapped between the structural mesh and the (user-defined) hydrodynamicmesh.

Extended bearing to flexbody coupling. A new method for coupling the journal bearing with the adjoiningstructures has been extended to support also a center-node based coupling on both the journal side and thebearing shell side. The center nodes are ideally connected via a force distribution element (e.g. NastranRBE3-like element) to the structure. With this coupling a direct comparison and also replaceability forinstance with the HD rigid bearings is supported. The surfaces of both the journal and the bearing will thenbe considered as rigid.

User Interface. The dialog Box for the EHD-Journal Bearing has been redesigned to comply with the dialogboxes from other journal bearing types.

SVT Kinematics

The Single Valvetrain Kinematics analysis has been extended to rocker arm valvetrains. This mean that theanalytical kinematics approach now supports following valvetrain types:

· Tappet

· Finger Follower

· Rocker Arm (new)

The tight integration with the Valve Lift Designer allows to create cam contours directly reflecting any changeon the valve lift, including an assessment of critical parameters such as contact stress. The kinematicmodels with 0 DOF can be turned into dynamic models compliant for analysis in time domain through asimple toggle switch. Also a first development step of automated SVT optimization is implemented.

Piston Dynamics: Flexible Piston & Flexible Liner - EHD Piston-LinerContact - incl. Update with respect to VE 25.0

This release features an elastohydrodynamic contact between a flexible piston and a flexible liner. Theusage is described in detail in the Piston Secondary Motion Analysis EHD tutorial.

· Update with respect to VE 25.0: The tutorial Piston Secondary Motion Analysis EHD has been updatedwith minor edits to make it easier to work through.

With regard to the EHD Piston-Liner Contact another new feature may be of interest: the Extract NodalResults functionality (see below) allows to write out the nodal displacements of a flexible body over time.With regard to a flexible piston / liner this enables the export of the water jacket's surface node displacementfor a fluid/structure analysis coupling (given that the engine block's FE model / MNF includes the waterjacket).



8

Piston Ring Dynamics

The Piston Ring Dynamics functionality is now fully integrated, including support for Liner Ports (orifices inliner surface to cope with 2-stroke and opposed piston engines) and providing a Ring ConformabilityAnalysis. Along with these changes come some improvements with regard to visualization of user inputs toallow visual checks (oil film thickness gauges, liner ports). A complete walk-through is available as tutorial.

Extended Timing Drive Chain Friction Analysis

This new feature set comprises

· Extended Friction Modeling, and

· additional Chain Friction Analysis

Extended Friction Modeling. The most chain drive elements have been extended with a viscous frictionmodel based on user-defined Stribeck curve along with additional friction output results which are used bythe Timing Drive Chain Friction Analysis. Please note that the friction shares are provided per chain driveelement. The following table provides an overview (x denotes new options):

The user can decide if friction shall be considered in the dynamics analysis or not: friction can be calculatedonly or applied as friction force / torque feedback to the chain drive elements.

New Chain Friction Analysis. The post-processing Timing Drive Chain Friction Analysis calculates theinternal and external chain friction work from an executed timing drive chain friction analysis. The analysisresult is written to a separate file. Total friction is comprised of "internal" chain friction (torque friction actingbetween bush and pin respectively roller and bush for the advanced / roller chain) and "external" chainfriction (friction between links and guides or sprockets). This functionality uses the internal and externalfriction power results to calculate the total friction work over a user-defined simulation time interval.

Extract Nodal Results

The new functionality Review - Extract Nodal Results calculates the nodal displacements, velocities andaccelerations from the modal deformation scale factors for each flexible body node and time step. The resultis saved to three separate (for displacement, velocity and acceleration) structured ASCII text files.



9

Note: Other potentially interesting features in this regard are Extract Modal Deformation Scale Factors(which extracts the modal deformation scale factors, i.e. the modal coordinates of the elastic deformation ofa flexible body during the multi-body analysis) and Extract Flexible Body Loads (which extracts all forcesand torques acting on the interface nodes of a selected flexible body).

These three flexbody-related functionalities (Extract Nodal Results, Extract Modal Deformation ScaleFactors, Extract Flexible Body Loads) typically cover any desired post-processing of flexbody results (e.g.as input for subsequent fatigue/durability analysis or as boundary condition for advanced CFD calculations).

FEV Virtual Engine Help

The help / end-user documentation has been updated where appropriate to reflect the latest changes infunctionality (please see the above list of functional changes and enhancements) and also to resolve knowsissues with the help.

Note: Whenever you feel that a link is missing, you notice a "lost topic" or stumble upon unclear (or faulty orincomplete) descriptions - let us know. Please provide a reference to the relevant help page and send anemail to: [email protected] welcome your feedback and any hint regarding the improvement of the FEV Virtual Engine help.


mailto:[email protected]


10

Corrections

Fixes and minor enhancements

[CR1961] Balancing Shaft Modify dialog box: for Inertia Method set to User Values the CM Loc. fields showedwrong coordinates.

[CR1967] Full Vehicle Analysis: Initialization problem of (e.g. crank) Angle Sensor elements has beenresolved.

[CR1977] 3D plot, Plot3D Viewer: multiple sessions (windows) of the Plot3D Viewer are now supported.

[CR1991] EHD Bearing, Filling Level: the Filling Level is now also available for result animation.

[CR2003] EHD Bearing, Friction Torque and Friction Power Loss: internal results were not properlyconverted from SI units to model units in result files.

[CR2007] Piston Ring Dynamics: Hardness definition was changed from Vickers to Brinell to have a uniformhardness definition throughout the product.

[CR2011] SVT Analytical Kinematics: Side forces and force (attack) angle on pivot are provided as additionalrequests for all drives including a valve lever with pivot.

[CR2014] Virtual Strain Gauges: VSGs can now also be built on multiple non-UDE flexible parts (generalparts replaced with flexible parts).

[CR2015] SVT Analytical Kinematics: For the tappet drive SVT the sliding and hydro velocity were not shiftedwith the timing.

[CR2025] Piston Ring Dynamics: oil film thickness gauge positions are visualized as thin cylinders on theliner (engine block R2).

[CR2026] Piston Ring Dynamics: liner ports are visualized on the liner (engine block R2).

[CR2034] Simulation didn't run if the gas force file contained only one entry for engine speed.

[CR2035] Cranktrain communicators couldn't be renamed by the user, because the template open macroreset the cranktrain communicator names to hard coded values.



11

[CR2036] The “Single Flywheel Create” dialog box caused an error message if Inertia Method was set toDensity.

[CR2037] Deactivated Flexible body modes in the property file were ignored while opening the subsystem.

[CR2039] The slow Replace Rigid to Flexible algorithm has been accelerated by a factor of about two.

[CR2040] Piston Secondary Motion analysis is now also possible with a Simple Geometry Piston.

[CR2041] Wrong property files were read after replacing rigid with flexible sprockets.

[CR2042] Modifying of the Gear 3D element lead to a reorientation of the gear geometry..

[CR2043] Replacing rigid gears with flexible ones didn't work.

[CR2044] Some graphic elements (visualizations of UDEs) were are not correctly positioned afterconverting.



12

Known Issues

Full vehicle analysis, ACAR solver

For a vehicle analysis the Adams/Car solver must be used. To this end make sure you first start Adams/Caror Adams /Driveline, then load FEV Virtual Engine as plug-in.

Maximum name length of MTX files, EHD bearings

The automatically created (and named) MTX files may have file names consisting of more than 70characters including the .mtx suffix (i.e. 66 characters for the file base name).

The automatic naming of MTX files is as follows:

subsystem-name_instance-name.mtx

If a new MTX file is created it will be created with the same name (i.e. an existing MTX file will be overwritten).But if the 70 characters limit is exceeded Adams automatically switches to a new naming scheme. In thisscheme MTX files are named flex_n.mtx where n is a counter which is incremented for any new createdMTX file.

This sort of naming will lead to significantly longer calculation time when using EHD bearings, in that caseplease check the MTX file naming. To avoid this problem you must make sure that the MTX file base namedoes not exceed 66 characters - adjust the subsystem-name and the instance-name.



13


All rights reserved.

Product and company names mentioned in this document may be trademarks or registered trademarks oftheir respective companies.

Mention of third-party products is for informational purpose only and constitutes neither an endorsement nora recommendation. The author assumes no responsibility with regard to the performance or use of theseproducts. All understandings, agreements, or warranties, if any, take place directly between the vendors andthe prospective users.

Every effort has been made to ensure that the information in this document is accurate. The author is notresponsible for printing or clerical errors.

The product described in this document incorporates copyright protection technology that is protected mymethod claims of certain U.S. patents and other intellectual property rights.

This document was created with Help&Manual.



14

Contact FEV

www.fev.com

FEV Europe GmbH

Neuenhofstr. 181

52078 Aachen • Germany

Phone +49 241 5689 -0

Fax +49 241 5689 -119

Email [email protected]

FEV Inc.

4554 Glenmeade Lane

Auburn Hills, MI 48326-1766 • USA

Phone +1 248 373 -6000

Fax +1 248 373 -8084


FEV Japan Co., Ltd.

1008 Burex Kojimachi

3-5-2 Kojimachi, Chiyoda-kuTokyo 102-0083 • Japan

Phone +81 (0) 3-3222 -0711

Fax +81 (0) 3-3222 -0712


FEV China Co., Ltd.

Room 1302, AnQuan Plaza

Beiyuan Road No.32100012 Beijing • China

Phone +86 10 8477 -5229

Fax +86 10 8477 -5230


Contact and Supportfor FEV Virtual Engine

Product related questions

General information about Virtual Engine can be found on FEV's global web site: Virtual Engine


To contact us regarding product related questions please email to: [email protected].

For Support inquiries please see below.

Support

The Virtual Engine Support is provided through FEV and its partners. Your local reseller can supply you with all necessary local customer support contact information.

FEV Virtual Engine customers having a valid Maintenance Agreement may direct their support inquiries via email to:

[email protected]

Current versions, updates and patches can be obtained through the web portal of our partner VI grade:

http://www.vi-grade.com/index.php?pagid=fev_vengine_updates_patches

Chinese Customers

Please use the following email address for local support:

[email protected]


http://www.fev.com










http://www.vi-grade.com

http://www.vi-grade.com/index.php?pagid=fev_vengine_updates_patches


release notes 25 - vi-grade you are reading these release notes as hardcopy (pdf document), please...

Documents