FORCE card is not being exported
Hello,
Normal case:
First, a force is defined on a geometric point in HyperMesh. Thus, the force will be allocated to the current load collector as a 'geometry object' in Model Browser. After exporting of the input file (a FORCE card is written), the force appears in Model Browser in the load collector as a 'geometry object' as well as an 'FEM object'.
My model:
I have this kind of forces defined on points but they will not be written to the input file. They appear in HyperMesh as 'geometry objects'. I have tried different export options (all/custom/displayed) but even if I select only the force collector to be exported, the FORCE cards will not be written. This is the only thing that will be exported of the load collector called 'Gasloads':
'
$$------------------------------------------------------------------------------$
$$ HyperMesh Commands for loadcollectors name and color information $
$$------------------------------------------------------------------------------$
$HMNAME LOADCOL 1'Gasloads'
$HWCOLOR LOADCOL 1 29
$$
'
Any idea what I am doing wrong? The forces are definitely still there in HyperMesh, because I see the force arrows on the display. And after export the forces will not appear as 'FEM objects' in the Model Browser as would happen in 'Normal case'.
Answers
-
Try to map your loads on geom. Analysis -> loads on geom
As I understand you, you have your loads only as geometry object. This could be because your loads are only mapped to a surface and not to nodes.
could you let us know what is the user profile you are in and what is the file type when you are exporting (refer to the picture below)?
can you provide the update details for HyperWorks on your machine?
to get the updates goto-->Help-->Update and system information
0 -
Hello,
thanks for your replies.
merula,
Analysis/load on geom --> No mapping occurred.
The forces are mapped to geometry points, see figure. I would like to have them written on the nodes during exporting.
The weird thing about this is that the export was first working properly, then I updated my design and non design spaces for the optimization (meaning that I added some new elements to the collectors) but did not change the force definitions, since they are defined on the geometry.
PrakashPag-adala, the information you requested:
Profile: OptiStruct
File type: OptiStruct
Template: Standard FormatUpdates Information:
------------------------------------------------------------
hwdesktop12.0
hwdesktophelp12.0
hwsolvers12.0
hwsolvershelp12.0Versions:
------------------------------------------------------------
hgtrans.exe: 12.0.0.85 (Feb 8 2013)
hm12.dll: 12.0.0.85 (Feb 8 2013)
hmopengl.exe: 12.0.0.85 (Feb 8 2013)
hst_ng.exe: 12.0.0.85.437093 (Feb 8 2013)
hstbatch_ng.exe: 12.0.0.85.437093 (Feb 8 2013)
hstdss.exe: 12.0.0.85.437093 (Feb 8 2013)
hvp.exe: 12.0.0.85 (Feb 8 2013)
hw.exe: 12.0.0.85 (Feb 8 2013)
hwmbdmodel.dll: 12.0.0.85 (Feb 8 2013)
hwplot.dll: 12.0.0.85 (Feb 8 2013)
hwplot3d.dll: 12.0.0.85 (Feb 8 2013)
hwpost.dll: 12.0.0.85 (Feb 8 2013)
hwtext.dll: 12.0.0.85 (Feb 8 2013)
hwvideo.dll: 12.0.0.85 (Feb 8 2013)
hwx.exe: 12.0.0.85 (Feb 8 2013)
templex.exe: 12.0.0.85 (Feb 8 2013)0 -
seppaelae
When exporting the model using an export template, only the loads on mesh are exported. 12.0 does map loads to the mesh before exporting and you have observed this as well.
Mapping is necessary and good practise, you can check as in your image above, clicking on the mesh icon of the load collector does not affect the display state of the force while clicking on the geometry icon does,
Try the below first
1. From the “geom.” page, go to the “node edit” panel.
2. In the “associate” panel, select the surfs to associate nodes to and then select the nodes to be associated (specifying a tolerance).
3. Click the green “associate” button.Do you see an error while mapping the loads? are you using the export all option now? can you card edit these forces? make sure they are active and allowed for export in the entity state browser
0 -
Hi,
associating the nodes on the points helped with all except one load (it was already associated). The last load I had to recreate. Now its working..0