HyperMesh - Abaqus Interface
Altair EmployeeHello everybody,
I got a problem with the HyperMesh - Abaqus Export. I try to export a model with three different components, but when I import it in Abaqus they are all in one part.
How can I import them as three different parts?
The second question is how can I create sets in HyperMesh to use them in Abaqus? I need to create them in HyperMesh because I want to select the elements based on geometry and after importing in Abaqus I only have elements.
Thanks for your help.
Greetings bene
(I attached my file. You have to change the file extension from *.txt to *.hm)
Answers
-
Hi,
I know nothing about Abaqus, so I can not confirm your import problem.
But from point of view of FEA, I don't think your mesh is good enough for analysis. The TET4 mesh within component 'Gehaeuse' is not good. Don't use TET4 in this case! Why not use shell mesh here ?
If you prefer volume elements, I think you have to refine a lot to have 2-3 elements over thichness, and important is work with TET10, not TET4.
Don't forget to check element quality: you have TET4 with aspect ~ 50 !!!
0 -
Hi,
this is a prob mesh. I´ll improve the mesh quality after I managed to import my parts to Abaqus....
0 -
Altair Forum User said:
Hello everybody,
I got a problem with the HyperMesh - Abaqus Export. I try to export a model with three different components, but when I import it in Abaqus they are all in one part.
How can I import them as three different parts?
The second question is how can I create sets in HyperMesh to use them in Abaqus? I need to create them in HyperMesh because I want to select the elements based on geometry and after importing in Abaqus I only have elements.
Thanks for your help.
Greetings bene
(I attached my file. You have to change the file extension from *.txt to *.hm)
Hi,
3 components should refer to 3 properties
to create sets => enter panel analysis>entity sets
0 -
Hi Bene,
I haven't tried importing meshed part into Abaqus but I presume: all the meshed parts are basically point cloud information with connectivity matrix describing how the points that are connected to form each element (in a similar form as the information contained in ABAQUS's .inp files). Therefore the geometry and elements are uncoupled and the information you import at ABAQUS will only contain the element information but not the geometries. All the boundary conditions will have to be applied on the element nodes in ABAQUS I believe because a form of geometry-element associating function will be required to allow the selection of elements by picking relevant geometry features.
It could be very handy though, for ABAQUS users, if both geometry and mesh can be transferred to ABAQUS from Hypermesh. Let's see what other ppl say.
Cheers,
Wensong
0 -
Hello tinh,
if I create a set like the it is only available in the assembly but not in the part.
Hello wensong,
as far as I know you can`t export the mesh and geometry from HyperMesh. But if I can create sets in HyperMesh I can use them to build my setup.
Greetings bene
0 -
Altair Forum User said:
Hello tinh,
if I create a set like the it is only available in the assembly but not in the part.
Hello wensong,
as far as I know you can`t export the mesh and geometry from HyperMesh. But if I can create sets in HyperMesh I can use them to build my setup.
Greetings bene
Hello
did you try creating 3 properties and assign them to 3 components?
because i saw with user profile abaqus, component has no card image ( so that means component is nothing in abaqus)
similar to nastran, just properties have card image so if you want to separate parts in abaqus, you have to separate their properties in hypermesh
0 -
Altair Forum User said:
Hello
did you try creating 3 properties and assign them to 3 components?
because i saw with user profile abaqus, component has no card image ( so that means component is nothing in abaqus)
similar to nastran, just properties have card image so if you want to separate parts in abaqus, you have to separate their properties in hypermesh
This is solver specification: How to define a 'component' within solver?
For SAMCEF solver for example, a 'component' may be defined by an element attribut ID. So by mapping Hypermesh component ID to SAMCEF attribut ID we can define directly solver 'component' within Hypermesh. For LS-DYNA solver, it's the same.
It's not need to have one property for each component in Hypermesh. We can have several components which share the same property. It's an organisation question of work.
0 -
Yes I think same to you.
Just because at top of topic he said in hypermesh he made some components but when export model, then import to abaqus then all elems come into one component so i think the cause is property because element attribute refer to property but not component
We need not care much about component in solver, when post process by hyperview we can select both model file and result file, so organization of components are same as in hypermesh
i am just questionable why he has to move model to abaqus for pre-processing instead of hypermesh
/emoticons/default_huh.png' alt=':huh:'>
0 -
Hi,
I tried to separate the components by properties. But I that lead to the same result, I have only one part in Abaqus.I’ll mesh my parts in HyperMesh, afterwards I switch to Abaqus for defining constraints, material data and so on (this is easier to handel in Abaqus than in HyperMesh).
Therefore I want to import a *.inp file to Abaqus, in which every component is a single part.
regards
bene
0 -
@bene: Imported INP (generated from Hypermesh) into Abaqus, I have different components, see screenshot.
<?xml version="1.0" encoding="UTF-8"?>
0 -
hi,
thanks for your reply.
But the problem is, I need each HyperMesh component as a single part in Abaqus. With your solution there is only one part with three sections.
regards bene0 -
Maybe you try to export each HM component into one INP for Abaqus?
0 -
Yes, this is one possibility. But I it is not that comfortable, hence I try to find a way to export all in one single inp-file.
greetings0 -
Hello there,
I would like to address bene's second question once again: Is it possible to define geometry based sets in HyperMesh (in a similar way as in Abaqus)?
So far I have only managed to save elements in sets which is bad for me because after remeshing of the part (which probably will be necessary in the further course of the project) my element based set is empty again and I have to redefine the set again.
My entire assembly consists of lot of different parts which are bonded to each other at particular surfaces. As I have a lot of adhesion surfaces I would like to define all these surfaces as single sets so that I can easly define all tie contacts (for Abaqus) by selecting the appropriate surfaces from the sets list.
I am not necessarily bound to Abaqus, I might probably as well use Optistruct for my simulation. What is the best way to define my contact surfaces in an efficient manner? I will have around 100 surfaces so I need a well structured list with appropriate naming and geometry based definition of the sets.
0 -
Hi MSC,
In OptiStruct you can use Auto contact manager (Tools menu>> Auto Contact manager) to define contacts. I think this will save you some time.
0 -
Hi everybody
If your model come in one part in Abaqus, I think this is the quickest way to separate them.
1. Right click on ''part''
2 Select ''copy...'', a window will open
3. Check ''Separate disconnected regions into parts'' and click ok
We still have to rename all part, but I think quicker than export all part one by one.
0 -
Have you had any luck with having set transfer from the original part to the disconnected regions?
0
