HyperWorks Release Notes

ANSYS Interface 2017 Release Notes

ANSYS Interface 2017 Release Notes

Previous topic Next topic No expanding text in this topic  

ANSYS Interface 2017 Release Notes

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

Highlights


In this release, Node and Element data from ANSYS WB *.DAT file can be read in HyperMesh.

 

Nodes and Elements from WB *.dat File

HyperMesh 2017 reads nodes and element data from WB internal solver file - *.DAT file. This includes support of node block, element block and EN keywords from WB DAT files. However, element data in keyword- “E” is ignored. These will be supported in a future release. The ANSYS template in HyperMesh exports those nodes and elements in CDB format only. Hence it should be noted that the support is ONLY at the input reader. Other data like loads and load steps, materials are not exclusively supported for DAT files, but DAT files do contain the same format for a few loads, load steps and material as of CDB format. HyperMesh input can read some of this data. However, you need to carefully check the model for this model data.

 

Other Enhancements

Model Checker with contact surface checks: The ANSYS interface in 14.0.130 supports contacts and contact pairs using surface and groups in HyperMesh. In the 2017 release, checks that review the correctness of contact surfaces and contact pairs in the model have been added. These checks are now available in Model Checker browser. Right-clicking on the errors provide manual and automatic correction options where available.
The table below shows the lists of the checks added in the Model browser for contact surfaces and pairs:

Check Title

Category

Check Description

1

Empty contact surfaces

Info

Check and list for contact surfaces where not a single element surface exists.

2

Empty contact masses

Info

Check and list all those node sets which have Contact Mass card image, but no node exists.

3

Empty pilot node set

Info

Check and list all those node sets which have pilot node card image, but no node exists.

4

Unused contact surfaces

Warning

List all the contact surfaces that are not used in any contact pair.

5

Unused contact masses

Warning

List all the contact mass node sets that are not used in any contact pair.

6

Unused pilot nodes

Warning

List all the pilot node sets that are not used at all.

7

Invalid contact surfaces

Error

List contact surfaces where mixed surfaces exist. Cases of mixed surfaces are any shell edge + any solid face, first order shell edge + second order shell edge; first order solid face + second order solid face

8

Invalid pilot node sets

Error

List pilot node sets that have more than one node.

9

Incomplete contact pairs

Error

List the contact group if any of the following conditions exist: both contact and target surface attachment is missing; either contact or target surface is missing; Et Type for either contact or target is missing; no property card is set.

10

Invalid contact pair

Error

Show this error if: 1) there is a mismatch of ET Type (sensor) and the contact/target surface. Correct match of the sensor and contact/target surface is given below. 2) If the Contact sensor type and property type in the pair are different. 3) If Contact is solid face and Target is shell edge or vice versa.

New Element support - Element LINK11 is now supported in HyperMesh.
Inclusion of Vector panel – Vector panel which was removed in ANSYS Interface as there is no entity called – Vectors in ANSYS solver. However many users claimed that the Vector panel is still useful for model building even though ANSYS solver does not support Vector entity. In this release Vector panel has been added back to 1-D page
Acceleration Load card- CMACEL is now available under load cases. Each sub case can now have CMACEL load.
OptiStruct > ANSYS conversion: OptiStruct to ANSYS conversion tool now supports the conversion of surface to surface contact surfaces and contact pairs.
Post-Processing: In this release, HyperView supports the following porosity results:
-Type: DPAR
-Options: TPOR (total porosity - Gurson material model), GPOR (porosity due to void growth), NPOR (porosity due to void nucleation).