Find more posts tagged with
Thanks for the response. I used the HvTrans program to convert the LS-Dyna D3Plot to Altair H3D file so I could capture all of the data. I can now run the simulation in HyperLife without the insufficient data error. The simulation runs through with no errors but their is no damage or life data and no contour on any of the components. The Damage Matrix and Rainflow Matrix show nothing as well Do you think the LS-Dyna model is still the problem in this scenario?
I have a similar problem as @ep2398 experienced. I converted
Radioss A001 result files into h3d file utilizing HVtrans. In Hyperlife, different kind of stress results are available in time series and result can be seen in Transient Response as subcase.
However fatigue analysis results are stiil receive as N/A for both damage and life.
Why fatigue analyses can not solve the problem, though explicit analysis is performed time-dependent event with time dependent loads?
Currently below solvers supported:
OptiStruct, Nastran, Abaqus & Ansys
Example if the converted h3d from d3plot, result contour is Von Mises, only von mises results will be present in the exported h3d, for all the time increments. ( there are chances the result type can also be renamed,and also miss the layer information in case of shells)So when this h3d is loaded in HyperLife, the necessary query information for the stress might not be available for the required calculation.
Hello.
I have a similar query re LS-Dyna import.
Does HyperLife support LS-Dyna solution files?
Above you mention that only OptiStruct, Nastran, Abaqus & Ansys are supported however when opening the initial model or importing results files via "Loadcase" the LS-Dyna option is available (as per attached image).
Upon importing LS-Dyna files however it appears no stress data is available as it doesn't show up on model when plotting stress fringe plot.
Any help would be greatly appreciated.
Currently below solvers supported:
OptiStruct, Nastran, Abaqus & Ansys
Example if the converted h3d from d3plot, result contour is Von Mises, only von mises results will be present in the exported h3d, for all the time increments. ( there are chances the result type can also be renamed,and also miss the layer information in case of shells)So when this h3d is loaded in HyperLife, the necessary query information for the stress might not be available for the required calculation.