General Mechanical

General Mechanical

Topics relate to Mechanical Enterprise, Motion, Additive Print and more

Normal Tangent Element “Not Consistent” Error

    • Vishal Ganore
      Ansys Employee

      What is the cause of the following ANSYS Mechanical error?

      “The normal of target element 19817570 is not consistent with the normal of target element 19817571 in real set 171. Please use the ENORM command to correct it.”

    • pgl
      Ansys Employee

      The most likely cause of this error is having adjacent contact elements with different normal directions.

      The error message is from the MAPDL solver, but in Mechanical a better remedy is usually to repair the underlying geometry rather than using ENORM to flip the element normal directions.

      If it not clear which contact pair is causing this error, insert Contact Tool under the Connections branch. In the Initial Information Worksheet, the real constant set for each contact pair is identified. Surface bodies (meshed with shell elements) have a designated "Top" surface which determines the orientation of the body. When selecting a face, with the default graphics settings, the "Top" surface is highlighted in green. You need to ensure that the top surface designation is consistent for all faces in all contacts. If the faces are not consistent, you can either flip the faces using DesignModeler or Spaceclaim, or divide the contact pairs into smaller pairs that have a consistent direction (note: over-constraint might then be an issue with MPC contact). For solid bodies, this behavior can be caused if the contact and/or target side was defeatured at the mesh level. A local mesh size control can help retain features close to the contact. Limiting the scope of the contact and target sides might also help. The tolerance slider can be used to tighten the tolerance of the automatic contact detection. To create contacts with a tighter tolerance, you need to delete the old contact pair and right click on the Connection Group - > "Create Automatic Connections". Finally, if mesh size is not an issue, you can try turning off mesh defeaturing, decreasing the defeaturing tolerance, or using a smaller Min Size with the Advanced Size Function.

    • d.g.

      I also have the same problem. In particular, I noticed that:

      -when I import the 3d model from spacclaim, whitout share topology, Ansys MAPD create automatically contact regions and it success to solve the model. 

      -when I share topology in Spaceclaim, Ansys MAPDL doesn't create contact region automatically, and success to solve the model against. 

      - when I share topology in Spaceclaim, Ansys MAPDL doesn't create contact region automatically. Since I need to create contact region, I introduce them through the command "Manual contact region" (right-click on the connection voice, in the main tree), but in thi case, when I solve the model the error occur.

      What can be the problem?


    • d.g.

      Mayby it can be useful explain what I want ...

      I want to import a 3d solid with shared topology to have a better quality mesh, but if I do this, Ansys MAPDL doesn't create contact regions between parts. I need contact region to read the results of the analyse in correspondance to them. So, are these two command compatible? I also read about the possibility to improve mesh directly in MAPDL throught the command "node merge" or, on the contrary, import not-shared topology solid and create "manual contact region" as whitten above, but in both case Ansys gives error. 

    • ramisayoud

      Hi , 

      I got the same problem. 

      Please, do you knwo how to know the element that correspond to the element number show in the message error, cause the element number shown exceed the total number of FE nodes and FE elements. 

      Thank you. 



    • Sankar93

      Element 0 is not defined as part of the current model

    • PedroModrzew


      I have similar error: "Target element [number] belongs to deformable target surface, while no underlying element was found.".

      I have checked and there are TARGE170 - CONTA173. Real is defined for both. I am using Ansys APDL. Could someone help me with this error?

      Thanks, Pedro

Viewing 6 reply threads
  • You must be logged in to reply to this topic.