about shell 163 and solid 164

- July 10, 2023 at 9:35 am
  
  伟张
  Subscriber
  
  hi,
  I encountered some issues while using ANSYS. The projectile body is made of mat_ 015 and solid 164 models, with Mat as the target plate_ 054 and shell 163 models, selected contact_ Eroding_ Surface_ To_ Surface and contact_ Automatic_ Surface_ To_ Surface, but "Warning 30364 (INI+364)
  Contact ID 1 is an ERODING contact A side effect of
  ERODING contact is that a negative volume failure criterion
  Is automatically enabled for all solid parts” appears during the calculation process.
  I want to know where my mistake is? How to solve it?
  And unknown encountered while solving LS-DYNA.
  Hope to receive help.
- July 12, 2023 at 4:40 pm
  
  Bill Bulat
  Ansys Employee
  
  From your description, I assume you are accessing the LS Dyna technology/solver through MAPDL. We no longer (at 2023R1) document/support the MAPDL GUI features that provide access to LS Dyna technology, and I suspect our newer licensing options (e.g., "Enterprise") would not permit the definition or creation of LS Dyna models in MAPDL.
  I can see that SOLID164 & SHELL163 were documented back at v18.2. I do not know the release at which we discontinued LS Dyna via MAPDL. What release or version of MAPDL are you using? Are you trying to solve your model in the MAPDL GUI? Maybe you can try writing out the file.k and solving it directly with the LS Dyna executable (outside of the MAPDL GUI). We used to do this with the Product Launcher (image below). Note the message I got when I selected this option using the 18.2 Product Launcher. This shared/parallel solver issue might have something to do with errors you are getting.
  Kind regards,
  Bill
- July 13, 2023 at 2:41 am
  
  伟张
  Subscriber
  
  hi,
  I am using MAPDL to build a model, then making modifications in ls report, and finally solving in ls run.
- July 19, 2023 at 4:05 pm
  
  Ushnish Basu
  Ansys Employee
  
  This is an internal error in LS-DYNA that would need to be fixed if it hasn't been already. You can ask you Ansys contact to see if they can provide access to a current Dev version to see if this issue has been fixed.
  In the meantime, I would suggest that you take out the CONTACT cards one at a time to see which one may be causing the issue (or take them all out and put them in one at a time)
  Please also make sure that you don't have overlapping contacts in your model