ANSA v17.0.4

BETA CAE Systems announces the release of the v17.0.4 of its software suite

About this release


BETA CAE Systems announces the release of the new BETA suite v17.0.4.

This maintenance release focuses on resolving identified issues with v17.0x.

The most important fixes implemented are listed below.ANSA v17.0.4

Contents

 

Known issues resolved in ANSA
Known issues resolved in µETA
Compatibility and Supported Platforms
Download

 

Known issues resolved in ANSA

 

CAD Import

ANSA translation libraries would not handle curves away from periodic surfaces.

Compare – Report

In certain cases, erroneous number of SETs would appear in Compare Report.

Data Management

When changing the representation of a part, internal connections might be erased.

Connections – Connections Manager

When realizing self-connected connections, both the GS of the NASTRAN CWELD and the SHIDA would be erroneously attached to the same element.

Shell Mesh

The Reconstruct function could erroneously split the edges of frozen shells.

Decks

Renumber: When reading ELEMENT numbering rules from older ANSA versions, Rules for RBE2s might not be correctly applied.

Save as v16

When saving the Database with option "Save as v16", RIGID BODY entities' Ids would be renumbered.

CFD Decks

Upon input of SC/TETRA files, BC (boundary condition) regions could not be read when their name contained a space character.

NASTRAN

Checks>CWELDs: Elements could be identified as problematic.

LS-DYNA

Thick Shell OrientationCohesive Solid Orientation Checks might not identify existing problems.

PERMAS

MPC RIGID entities might not be written correctly upon output.

RADIOSS

Unsupported Engine Keywords might be omitted when opening an ANSA database created from a RADIOSS file.

Scripting

The base.CollectEntities() function would fail to gather the ABAQUS SPRING and PERMAS XSTIFF elements from CELAS2 NASTRAN elements.

 

For more details about the new software features, enhancements and corrections please, refer to the Release Notes document.

 

Known issues resolved in µETA


Supported Interfaces

Not all states would be recognized and loaded for certain EnSight transient analysis files.

The MS-Windows version of META would terminate when reading larger than 2GB IM files.

No Strain Energy results would be recognized and loaded for the last cycle of NASTRAN SOL200 .op2 files.

Loading META projects of Pam-Crash frequency response results would cause erroneous termination.

2D Plots

Curves from LS-DYNA elout files could not be plotted using META commands.

Several curve functions, including crash criteria and filters, would not take into account the curves' unit system.

Editing the Axis Options of polar plots would cause termination.

Saving curves in NASTRAN TABLED format could cause termination.

NVH

In the Modal Response tool when declaring a subload, other than the first one, as enforced excitation, the results might be incorrect.

The META commands to create a new MAC plot from the AutoMAC tool were not working.

Section Forces

Section Forces calculated from FEMZIP-compressed files would be incorrect.

Toolbars

The OIC toolbar would not work for WS-50 dummies if a user-defined IR-TRACC length was used.

The TPA from Forces and FRFs toolbar would not input correctly FRFs in .unv format.

The SOL200 Plot toolbar would not read Design Response values from .f06 files at certain cases.

Save

The File Manager for exporting files could not access USB devices.

Saving models in Abaqus format, connections would not be saved correctly in the .metadb if it was saved with the <16.0.0 option.

 

For more details about the new software features, enhancements and corrections please, refer to the Release Notes document.

Compatibility and Supported Platforms

 

ANSA files saved by all the first and second point releases of a major version are compatible to each other. New major versions can read files saved by previous ones but not vice versa.

META Project files saved from version 17.0.4 are compatible and can be opened by META version 16.0.0 or later. To be readable by META versions earlier than v16.0.0, they have to be saved selecting the option "Version <16.0.0".

Support for 32-bit platform has been discontinued for all operating systems.

 

Download

 

Where to download from

Customers who are served directly by BETA CAE Systems, or its subsidiaries, may download the new software, examples and documentation from their account on our server. They can access their account through the "user login" link at our  web site.
Contact us if you miss your account details. The [ PublicDir ] link will give you access to the public downloads area.
Customers who are served by a local business agent should contact the  local support channel channel for software distribution details.

 

What to download

All files required for the installation of this version reside in the folder named "BETA_CAE_Systems_v17.0.4" and are dated as of February 9, 2017. These files should replace any pre-releases or other files downloaded prior to that date.
The distribution of this version of our pre- and post-processing suite is packaged in one, single, unified installation file, that invokes the respective installer and guides the procedure for the installation of the required components.

For the installation of the software on each platform type, the.sh installer file residing in the folder with respective platform name, for Linux and MacOS or the respective .msi installer file for Windows, 64bit, have to be downloaded.

In addition to the above, optionally, the µETA Viewer is available to be downloaded for each supported platform.

The tutorials and the example files reside in the folder named "TUTORIALS". This folder includes the complete package of the tutorials and example files, and a package with only the updated ones.

The Abaqus libraries required for the post-processing of Abaqus .odb files are included in the installation package and can be optionally unpacked.

Earlier software releases are also available in the sub-directory called "old" or in a folder named after the product and version number.