Recent Posts

71

Miscellaneous Software Topics / Re: Analysis time increased with 7.3.37 installation

« Last post by ruth.k.ross@spiritaero.com on October 28, 2020, 10:49:57 AM »

I'm having a rather similar issue to what was originally described.
I have
1 project
2 assemblies
658 components
57 effective laminates.

It was taking 2 hours to run last week, but it suddenly went to about 24 hours to run only 1 of the assemblies.

Any idea why this would've suddenly changed, and how to reduce run-time?

It looks like the exhaustive search flag has already been set as a default to "no".

72

Scripting / Re: Getting joint data using vba

« Last post by Stephen on September 25, 2020, 10:07:31 AM »

Hello,

Unfortunately, no it is not currently possible to extract joint-related data through the VBA scripting API.

Thanks,
Stephen

73

Scripting / Getting joint data using vba

« Last post by aeromaner on September 25, 2020, 08:28:14 AM »

Is it possible to obtain any data such as left panel, right panel, ortho panel, joint grid ?ds etc about Joint using vba scripting?

74

FEM Coupling (HyperFEA) / Re: Temperature Dependent Material Properties in HyperFEA

« Last post by bacjac on September 24, 2020, 01:55:48 PM »

Still not sure if my conclusion is right James. Appears I don't get the expected behavior. Do you have an example that shows the process working ?

75

FEM Coupling (HyperFEA) / Re: Temperature Dependent Material Properties in HyperFEA

« Last post by bacjac on September 21, 2020, 09:01:32 AM »

that would be good. Somehow I'm not seeing the higher temperature in the Loads Tab. I size the component from that tab, either with a sigma or element based but both still show this component at 70F when I believe it should be 1300F from the Tload callout in the thermal rundeck.

76

FEM Coupling (HyperFEA) / Re: Temperature Dependent Material Properties in HyperFEA

« Last post by James on September 21, 2020, 08:27:30 AM »

If you're running element-based or peak-element load processing metrics, the peak is used.
If you're running a n-sigma statistical method, the area-weighted average is used.
Take a look at the FEA loads tab, it should include some information about the temperature averaging.

-James

77

FEM Coupling (HyperFEA) / Re: Temperature Dependent Material Properties in HyperFEA

« Last post by bacjac on September 21, 2020, 07:55:00 AM »

Ok, found an error, missing an include file in one of my attempts. Got closer to what I think should happen.  Can you tell me James what HyperSizer uses for a temperature to get allowables, for a component of multiple elements, where each element is a different temperature. Is it an average or the max temperature. Appears in the "Stress" tab the max temperature is used. Ok, just good to know what the philosophy is. 

78

FEM Coupling (HyperFEA) / Re: Temperature Dependent Material Properties in HyperFEA

« Last post by bacjac on September 18, 2020, 03:09:22 PM »

Say, can the thermal and mechanical subcases have the same ID, since they are in separate run decks. I seem to remember something about that being an issue?

79

FEM Coupling (HyperFEA) / Re: Temperature Dependent Material Properties in HyperFEA

« Last post by bacjac on September 18, 2020, 02:29:53 PM »

I believe I tried that James, but I'd better try again to see if I did it right.  Thanks. Will let you know.

80

FEM Coupling (HyperFEA) / Re: Temperature Dependent Material Properties in HyperFEA

« Last post by James on September 18, 2020, 09:50:40 AM »

Yes, HyperSizer will read and average element and nodal temperatures from the input file, and use them as analysis temperatures for each component. You have to run the thermal subcase separately from the mechanical case and combine the thermal and mechanical sets together into 1 load case.

Here's a brief help topic on the subject.
http://hypersizer.com/help_7.3/#FE-Results-Import/results-thermal_loads.php

Also keep in mind thermal help/hurt factors. See:
http://hypersizer.com/help_7.3/#LoadSets/ls-factors.php

The temperatures should be defined as element or nodal. The 'initial temp' is not used, instead it's the applied temps. Assigning temperatures with at TEMPD card is supported.

I hope this is helpful.

-James