Jump to content

Q.Nguyen-Dai

Members
  • Content Count

    1245
  • Joined

  • Last visited

  • Days Won

    51

Everything posted by Q.Nguyen-Dai

  1. Maybe you need do "equivalent" of nodes?
  2. If you use Pyramid between Hexa & Tet, it's OK. In you model "1.1.hm" please check "Tet collapse"!!! I see some bad elements.
  3. I just tested LS-DYNA export under Hyperworks 2019.1, it's OK for Pyramid elements! Check this key file: dyna_pyra_1.zip And here's what I got with LS-PrePost: So if you use Hypermesh 2019.* you not need to modify the template.
  4. Sometime, life is easier with solid meshing
  5. You can not connect TET elements to Quad faces. It's not valid from point of view of FEA. You have to use Pyramid elements as in my model.
  6. Your mesh is NOT valid! Have a look at my modification: components "my_3D(*)" : 1.1__.hm
  7. From point of view FEA, you can not connect TET to HEXA directly. You have to use PYRAMID between them. Default LS-DYNA template of Hypermesh can not (at least until release v14) export Pyramid elements for LS-DYNA. But you can do it by modifying this template
  8. If you assign MAT to each element (not by component), you have to read all elements, one by one, to count. Maybe share your model?
  9. In your case, maybe it's better to organize one material for each component. "Why complicate the life when you can simplify it?"
  10. Sorry, I don't know CADFEKO. But I can confirm you that your STL is valid & readable
  11. No error/warning message when I import your STL into Hypermesh 2019.1
  12. Your PSOLID property (ID=2) references to material ID=4 which does not exist. So check your materials definition.
  13. Try this code and tell us if it works? *createmarkpanel nodes 1 "Select node" set node1 [hm_getmark nodes 1] *createmarkpanel surfaces 1 "Select surface" set surf_id [hm_getmark surfaces 1] *createmark nodes 1 $node1 *duplicatemark nodes 1 0 hm_createmark nodes 1 -1 set node2 [hm_getmark nodes 1] *createmark nodes 1 $node2 *markprojectnormallytosurface nodes 1 $surf_id set d12 [lindex [split [hm_getdistance nodes $node1 $node2 0] " "] 0] puts [format "Thickness= %0.3f" $d12]
  14. I'm not sure Optistruct (and another FEA softs like Ansys, Abaqus,...) can do contact analyse at microscopic level.
  15. Try to define environment variable ALTAIR_LICENSE_PATH=<full path to altair_lic.dat> ?
  16. You found it in Hyperworks help (path from my Windows installation): file:///C:/Program Files/Altair/2019/help/altair_help/topics/getting_started/hw_licensing_hwd_application_unit_draw_r.htm?zoom_highlightsub=HWU
  17. Keep in your mind that not every STL file could be used for FEA. STL is used firstly for surface presentation, not for FEA.
  18. When you buy 1 HWU, you'll see COUNT=1000 within license file. So COUNT = <HWU number> x 1000
  19. It's possible. But why you need this kind of mesh? Special analysis?
×
×
  • Create New...