News: has a Community Board and Customer Support System. Submit a ticket at

Recent Posts

Pages: [1] 2 3 ... 10
if I see it right there might be a bug during import:
we use cylindrical coordinate systems (COS) to align the element COS to. The FEM import correctly recognizes the following:
  • the local coordinate systems (visible in FEM Viewer)
  • the assignment of a local coordinate system to elements
But it seems as if information on the COS type (cartesian/cylindrical) is lost. I tested a panel, where local cylindrical COS #15 (axis = panel cylinder axis) is used for the left half (cf. pictures):
  • ANSYS: the x-axis (black) is in downward circumferential direction
  • HS: the x-axis direction points upwards circumferential for the first 5 element rows, then changes to downwards. My guess: HS assigns COS #15 to these elements but treats it as cartesian. That means, for the lower part of the shell: x-axis-projection is used (downwards). Upper part: x-axis-projection gets too small (or even a point), so the y-axis of COS15 is used as the elements' x-axis. Many FEM-programs such as ANSYS also use this method).
  • HS FEM-Viewer "Create or change local COS"-form: here I also cannot find any indication if a COS is of cylindrical or cartesion type.
Even more confusing: plotting, say, N11 in the FEM-Viewer, it shows the correct ANSYS result, i.e. for the actual x-direction, not the one depicted by the arrows! So my understanding is that, for the sizing process, HS uses the actual N11-result for the components but assuming it is the value for the direction shown by the arrow (which is wrong by 180° in this case, and by 90° in the case of my first post).
Can you confirm this?

Scripting / Re: User Load Superposition
« Last post by garyjh on Yesterday at 04:55:50 AM »
The original post was from 2010, but I am still interested in how additional user defined loads can be added to FEA loads, as mentioned, due to Brazier loading.

Has anything in latest versions 7.3.xx changed that will help with adding in Brazier loading?

HyperSizer Stress Reports / Re: Strain values in excel report format
« Last post by James on June 15, 2018, 07:05:13 AM »
The Word report is much faster in HyperSizer v7.
Also, the Excel report contains a lot of element data in HyperSizer v7.
Finally, the analysis detail reports contain this information, in HyperSizer v7.

HyperSizer Stress Reports / Strain values in excel report format
« Last post by vishal on June 15, 2018, 04:39:20 AM »

I am very new to Hypersizer.

Right now I want strain values in Direction 1 and 2 in report format.
Word report takes lot of time. Report in excel format is quick however it does not have strain values.

Is there option to get strain values in excel format OR any other way to get Strain values quicker.

Vishal A
Creating & Editing Composite Laminates / Re: Laminate Creation Error Message
« Last post by garyjh on June 14, 2018, 10:24:24 AM »
Though that was the issue but can only see about 800 laminates so was a little confused. Tried your suggested solution & deleted a lot so only 20 left and still get same message.

UPDATE: Compacted database and then opened new compacted database and can create laminates OK now. Confusing??
Creating & Editing Composite Laminates / Re: Laminate Creation Error Message
« Last post by James on June 14, 2018, 10:21:52 AM »
It appears that you hit the database limit for number of laminates. Limit = 10,000.

Use the material clean-up feature to remove laminates from the database.

Creating & Editing Composite Laminates / Laminate Creation Error Message
« Last post by garyjh on June 14, 2018, 10:17:09 AM »
When trying to create a laminate get the following error message (see attachment).

Create a laminate OK before this error so not sure what has happened. Closed down HS and reopened db, but still get error message. Please can someone advise. Thanks.

FEM Coupling (HyperFEA) / Re: Generalized shell export: temperature-dependence
« Last post by JanPio on June 14, 2018, 01:31:13 AM »
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.

FEM Coupling (HyperFEA) / Re: Generalized shell export: temperature-dependence
« Last post by Stephen on June 13, 2018, 12:30:37 PM »
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!

FEM Coupling (HyperFEA) / Generalized shell export: temperature-dependence
« Last post by JanPio on June 13, 2018, 11:25:23 AM »
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?
Pages: [1] 2 3 ... 10