Software Use > FEM Coupling (HyperFEA)

Generalized shell export: temperature-dependence


we use ANSYS with HFEA and I noticed that the ASEC-beams, RECT-beams and SHELL-sections in the updated "..._i.cdb" have pointers on their respective material definitions, which are temperature-dependent (MPTEMP, MPDATA).
The GENS-shells, however, seem to have only one set of material properties. That means that all the shell elements of the updated FE-model will not have temperature-dependent material properties in the next analysis.

* The properties of which temperature are used to calculate the generalized shell properties written to the new ANSYS file?
* GENS-shells in ANSYS can actually have up to 6 different sets of mat-properties by reentering the SSPA, SSPD etc commands for different temperatures. Is there an option in HS to use this?Thanks,

Hi Jan,

You are correct that we are outputting a single set of generalized shell properties to the FEM when iterating with HyperFEA.

1. HyperSizer outputs properties corresponding to the temperature of the controlling loadcase for that component.
2. At this time, we do not support multiple sets of material properties for a single section in the FEM. If this changes in the future, we will be sure to state so in the update notes.

Let me know if you have any other questions!


Hi Stephen,
thanks so far, this answered my questions.
Regarding your answer #2 my doubt is the following:
actually you do support this already for all the beam and layered/continuous shell sections (SECTYPE,...,SHELL) by exporting the temperature table MPTEMP,...,TEMP1,TEMP2,etc. This could lead to errors, e.g. the shell section has a constant Young's modulus for all temperatures while the adjacent beam changes stiffness or thermal expansion coefficient with varying temperature. Additional "phantom stress" would occur.


Hi Jan,

You are correct that we do indeed export temperature-dependent properties to ANSYS for composite shells and bars. Unfortunately I do not have an immediate solution for you on this, but I have discussed with our developers and we will try to address it in a future release.

For now, one possible option is iterating with a single set of properties (copy materials and remove all but one temperature), before doing a final analysis and sizing cycle with the temperature-dependent properties.



[0] Message Index

Go to full version