Name
|
Description
|
Result
|
Auto correction action
|
Manual correction action
|
Remarks
|
Component without HM_COMP
|
Checks and flags components that do not have a HM_COMP card image.
|
Lists the components that failed the check.
|
Supported.
|
Not Supported.
|
The HM_COMP card image should be attached to all components except those that have only RBE3 and RIGID.
|
Component without ET TYPE
|
Checks and flags components that have a card image, but do not have a sensor attached.
|
Lists the components that failed the check.
|
Not Supported.
|
Opens the Card Image panel.
|
|
ET Type and Element config mismatch
|
Checks and flags components whose ET Type does not match with any of the element types in the component.
|
Lists the components that failed the check.
|
Not Supported.
|
Opens the Card Image panel.
|
|
ET Type and Real sets or Sections are not matching
|
Checks and flags components that have a property type that does not match the ET Type. Targe169 and targ170 components can have a property type of any of the related contact types.
Checks and flags components that have an ET Type and section that do not match.
|
Lists the components that failed the check.
|
Not Supported.
|
Opens the Components panel.
|
The GENERALp property can be attached to componenets that have any ET Type.
|
Unpaired contacts
|
Checks and flags components of contact elements which are single. Components are identified based on the property attached to them.
|
Lists the components that failed the check.
|
Not Supported.
|
Not Supported.
|
|
Mass elements without property
|
Checks and flags MASS21 and/or MASS71 elements if they have no property attached or if the attached property is not of type MASS21p or MASS71p, and if the values related to the mass elements are zero.
|
Lists the elements that failed the check.
|
Not Supported.
|
Not Supported.
|
It is necessary to define at least one of the mass values on the property.
|
Improper Entity Set Names
|
Checks and flags entity sets with a name that is longer than 32 characters, contains special characters other than an underscore, or that does not start with a letter in the alphabet.
|
Lists the entity sets that failed the check.
|
Renames the set by removing the special characters, reducing the length of the name to 32 characters, and/or removing the non alphabetic characters from the start of the name.
|
Not Supported.
|
Hypen and space are also considered special characters. The Model Checker currently does not check to see if the name already exists.
|
Free Nodes
|
Checks and flags nodes that are not connected to a valid ANSYS element.
|
Lists the nodes that failed the check.
|
Deletes the free nodes.
|
Not Supported.
|
RBE3, CERIG, and CP are considered equations by ANSYS.
|
Free 1D elements
|
Checks and flags 1D elements that are not attached to any structural components.
|
Lists the elements that failed the check.
|
Deletes the free 1D elements.
|
Not Supported.
|
|
Duplicate 1D Elements
|
Checks and flags 1D elements that are connected between the same two nodes.
|
Lists the elements that failed the check.
|
Deletes the duplicate 1D elements.
|
Not Supported.
|
The order of nodes does not matter.
|
Duplicate 2D Elements
|
Checks and flags 2D elements that share common nodes.
|
Lists the elements that failed the check.
|
Deletes the duplicate 2D elements.
|
Not Supported.
|
|
Duplicate 3D Elements
|
Checks and flags 3D elements that share common nodes.
|
Lists the elements that failed the check.
|
Deletes the duplicate 3D elements.
|
Not Supported.
|
|
Pretension elements without third node
|
Checks and flags pretension elements that do not have a direction node.
|
Lists the elements that failed the check.
|
Not Supported.
|
Not Supported.
|
|
RBE3, CERIG and CP with free nodes
|
Checks and flags the RBE3, CERIG, and CPs with free, independent and dependent nodes.
|
Lists the RBE3, CERIG and CPs that failed the check.
|
Not Supported.
|
Not Supported.
|
The nodes need to be connected to a valid ANSYS element.
|
Equation with free nodes
|
Checks and flags equations that have nodes which are not connected to elements. RBE3 and RIGIDS are considered equations in ANSYS.
|
Lists the equations that failed the check.
|
Not Supported.
|
Not Supported.
|
The nodes need to be connected to a valid ANSYS element.
|
Invalid pilot node sets
|
Checks for pilot node sets that have more than one node.
|
Lists all pilot node sets that have more than one node.
|
Not Supported.
|
Opens the Entity Edit: Sets dialog.
|
|
Invalid contact surfaces
|
Checks for contact surfaces that have mixed surfaces.
Cases of mixed surfaces includes:
• | Any shell edge + any solid face |
• | First order shell edge + second order shell edge |
• | First order solid face + second order solid face |
|
Lists all contact surfaces that have mixed surfaces.
|
Not Supported.
|
Opens the Entity Edit: Contactsurfs dialog.
|
|
Incomplete contact pairs
|
Checks for contact groups that have one or more of the following conditions:
• | Missing both contact and target surface attachments. |
• | Missing a contact or target surface. |
• | Missing an ET Type for either a contact or target surface. |
• | No property card is assigned. |
|
Lists all contact groups that fail the check.
|
Not Supported.
|
Opens the Entity Edit: Groups dialog.
|
|
Invalid contact pairs
|
Checks for contact pairs that have the following:
1. | There is a mismatch of Et Type (sensor) and contact/target surfaces, and the correct match of the sensor and contact/target surface are in the given below. |
2. | The Contact sensor type and property type in the contact pair are different. |
3. | The contact is a solid face, and the target is a shell edge or vice versa. |
|
Lists all contact pairs that fail the check.
|
Not Supported.
|
Opens the Entity Edit: Groups dialog.
|
|