pandaleone
Mechanical
- Feb 10, 2005
- 5
HI all
I am trying to import a assembly meshed with Cosmosworks 2005 inside Femap for setting up the analysis with Nastran. I don't want to import the geometry into Femap because it would take a longer time to prepare a good mesh.
In this assembly there are some surfaces on contact (pin/hole, mates, ...) and the resulting mesh contains gaps badly described; for example, for two coincident nodes where the format should be:
CGAP cgap_id pgap_id nodeA nodeB orientation_node
the node orientation is defined as a casual one on the mesh (all CGAPs get the same node for oientation), and therefore does not define the right gap direction. The property PGAP is empty, no values are defined, but this could be left to the user. Moreover, when nodes are coincident, Nastran requires a 6th field in CGAP definition where the CID is defined which Cosmos does not write.
Is there something I'm missing or Cosmosworks translator to Nastran is not reliable for assemblies?
Thank you for your support
I am trying to import a assembly meshed with Cosmosworks 2005 inside Femap for setting up the analysis with Nastran. I don't want to import the geometry into Femap because it would take a longer time to prepare a good mesh.
In this assembly there are some surfaces on contact (pin/hole, mates, ...) and the resulting mesh contains gaps badly described; for example, for two coincident nodes where the format should be:
CGAP cgap_id pgap_id nodeA nodeB orientation_node
the node orientation is defined as a casual one on the mesh (all CGAPs get the same node for oientation), and therefore does not define the right gap direction. The property PGAP is empty, no values are defined, but this could be left to the user. Moreover, when nodes are coincident, Nastran requires a 6th field in CGAP definition where the CID is defined which Cosmos does not write.
Is there something I'm missing or Cosmosworks translator to Nastran is not reliable for assemblies?
Thank you for your support