TARGE169 Element Description

TARGE169 is used to represent various 2D "target" surfaces for the associated contact elements (CONTA172 and CONTA175). The contact elements themselves overlay the solid elements describing the boundary of a deformable body and are potentially in contact with the target surface, defined by TARGE169.

You can impose translational or rotational displacement, temperature, voltage, magnetic potential, pore pressure, and concentration on the target segment element. You can also impose forces and moments on target elements. See TARGE169 in the Mechanical APDL Theory Reference for more details about this element. To represent 3D target surfaces, use TARGE170, a 3D target segment element.

For rigid targets, these elements can easily model complex target shapes. For flexible targets, these elements will overlay the solid elements describing the boundary of the deformable target body.

Figure 169.1: TARGE169 Geometry

TARGE169 Input Data

The target surface is modeled through a set of target segments. Typically, several target segments make up one target surface.

Figure 169.2: TARGE169 2D Segment Types shows the available segment types for TARGE169.

For any target surface definition, the node ordering of the target segment element is critical for proper detection of contact. The nodes must be ordered so that, for a 2D surface, the associated contact elements (CONTA172 or CONTA175) must lie to the right of the target surface when moving from target node I to target node J. For a rigid 2D complete circle, contact must occur on the outside of the circle; internal contacting is not allowed.

Pair-Based Contact versus General Contact

There are two methods to define a contact interaction: the pair-based contact definition and the general contact definition. Both contact definitions can exist in the same model. TARGE169 can be used in either type of contact definition.

Pair-Based Contact

In a pair-based contact definition, the 2D contact elements (CONTA172 or CONTA175) are associated with 2D target segment elements (TARGE169) via a shared real constant set. The program looks for contact interaction only between surfaces with the same real constant set ID (which is greater than zero). The material ID associated with the contact element is used to specify interaction properties (such as friction coefficient) defined by MP or TB commands.

The target surface can be either rigid or deformable. For rigid-flexible contact, the rigid surface must be represented by a target surface. For flexible-flexible contact, one of the deformable surfaces must be overlaid by a target surface. See Designating Contact and Target Surfaces in the Contact Technology Guide for more information.

Each target surface can be associated with only one contact surface, and vice-versa. However, several contact elements could make up the contact surface and therefore come in contact with the same target surface. Likewise, several target elements could make up the target surface and thus come in contact with the same contact surface. For either the target or contact surfaces, you can put many elements in a single target or contact surface, or you can localize the contact and target surfaces by splitting the large surfaces into smaller target and contact surfaces, each of which contain fewer elements.

If a contact surface may contact more than one target surface, you must define duplicate contact surfaces that share the same geometry but relate to separate targets, that is, have separate real constant set numbers.

General Contact

In a general contact definition, the general contact surfaces are generated automatically by the GCGEN command based on physical parts and geometric shapes in the model. The program overlays contact surface elements (CONTA172) on 2D deformable bodies (on both lower- and higher-order elements). The general contact definition may also contain target elements (TARGE169) overlaid on the surfaces of standalone rigid bodies.

The GCGEN command automatically assigns section IDs and element type IDs for each general contact surface. As a result, each general contact surface consists of contact or target elements that are easily identified by a unique section ID number. The real constant ID and material ID are always set to zero for contact and target elements in the general contact definition.

The program looks for contact interaction among all surfaces and within each surface. You can further control contact interactions between specific surfaces that could potentially be in contact by using the GCDEF command. The material ID and real constant ID input on GCDEF identify interface properties (defined by MP or TB commands) and contact control parameters (defined by the R command) for a specific contact interaction. Unlike a pair-based contact definition, the contact and target elements in the general contact definition are not associated with these material and real constant ID numbers.

Considerations for Rigid Targets

Each target segment is a single element with a specific shape, or segment type. The program supports seven 2D segment types, as described in Table 169.1: TARGE169 2D Segment Types, Target Shape Codes, and Nodes. The segment types are defined by one, two, or three nodes and a target shape code (TSHAP command) which indicates the geometry (shape) of the element. The segment location is determined by the nodes.

A radius value is required for the circle segment type. For pair-based contact, the radius is specified by real constant (R1). For a general contact definition, the radius is specified by section data (the SECTYPE,,CONTACT,RADIUS command with the radius entered on the SECDATA command).

Table 169.1: TARGE169 2D Segment Types, Target Shape Codes, and Nodes

TSHAP	Segment Type	Node1 (DOF)	Node 2 (DOF)[1]	Node 3 (DOF)	R1	R2
LINE	Straight line	1st corner pt (UX, UY) (TEMP) (VOLT) (AZ)	2nd corner pt (UX, UY) (TEMP) (VOLT) (AZ)	None	None	None
ARC	Arc, clockwise	1st corner pt (UX, UY) (TEMP) (VOLT) (AZ)	2nd corner pt (UX, UY) (TEMP) (VOLT) (AZ)	Circle center pt (UX, UY) (TEMP) (VOLT) (AZ)	None	None
CARC	Arc, counter- clockwise	1st corner pt (UX, UY) (TEMP) (VOLT) (AZ)	2nd corner pt (UX, UY) (TEMP) (VOLT) (AZ)	Circle center pt (UX, UY) (TEMP) (VOLT) (AZ)	None	None
PARA	Parabola	1st corner pt (UX, UY) (TEMP) (VOLT) (AZ)	2nd corner pt (UX, UY) (TEMP) (VOLT) (AZ)	Midside pt (UX, UY) (TEMP) (VOLT) (AZ)	None	None
CIRC	Circle[2][4]	Circle center pt (UX, UY) (TEMP) (VOLT) (AZ)	None	None	Radius	None
PILO	Pilot node	1st point (UX, UY, ROTZ) (TEMP) (VOLT) (AZ)	None	None	None	None
POINT	Point[3]	1st point (UX, UY)	None	None	None	None

1. The DOF available depends on the setting of KEYOPT(1) for the associated contact element. For more information, see the element documentation for CONTA172 or CONTA175.

2. When using the direct generation modeling method to create a circle target segment, specify the R1 value (define the real constant set for pair-based contact; or define the RADIUS section data for general contact) before creating the element.

3. Rigid surface node. This segment type is only used to apply boundary conditions to rigid target surfaces.

4. The surface projection contact method (KEYOPT(4) = 3 on the contact element) does not support primitive target segments.

Figure 169.2: TARGE169 2D Segment Types

For simple rigid target surfaces, you can define the target segment elements individually by direct generation. You must first specify the SHAPE argument for the TSHAP command. When creating circles through direct generation, you must also define the radius value before creating the element (specify real constant R1 for pair-based contact, or specify the RADIUS section type via SECTYPE and SECDATA commands for general contact).

For general 2D rigid surfaces, target segment elements can be defined by line meshing (LMESH). You can also use keypoint meshing (KMESH) to generate the pilot node.

If the TARGE169 elements are created via automatic meshing (LMESH or KMESH), then the TSHAP command is ignored and the program chooses the correct shape automatically.

For rigid-to-flexible contact, by default, the program automatically fixes the structural degree of freedom for rigid target nodes if they aren't explicitly constrained (KEYOPT(2) = 0). If you wish, you can override the automatic boundary condition settings by setting KEYOPT(2) = 1 for the target elements. For flexible-to-flexible contact, no special boundary conditions treatment is performed, and the KEYOPT(2) = 0 setting should be used.

You can assign only one pilot node to an entire rigid target surface (or none if it is not needed). In a pair-based contact definition, the target element associated with the pilot node has the same real constant ID as the other target elements in the pair. In a general contact definition, the target element associated with the pilot node has the same section ID, but it has a zero real constant ID, as do the other target elements of each rigid surface in the general contact definition.

The pilot node, unlike the other segment types, is used to define the degrees of freedom for the entire target surface. This node can be any of the target surface nodes, but it does not have to be. All possible rigid motions of the target surface will be a combination of a translation and a rotation around the pilot node. The pilot node provides a convenient and powerful way to assign boundary conditions such as rotations, translations, moments, temperature, voltage, magnetic potential, pore pressure, and concentration on an entire rigid target surface. By default (KEYOPT(2) = 0), you can assign the boundary conditions only to the pilot node, eliminating the need to assign boundary conditions to individual target nodes, thus reducing the chance of errors. The program also automatically fixes the structural degrees of freedom on the pilot node if they aren't explicitly constrained.

By setting KEYOPT(2) = 1 for the target elements, you can apply boundary conditions on any rigid target nodes rather than only on the pilot node. It is your responsibility to make sure the rigid target surface is not under-constrained or over-constrained. It is still recommended that you apply all boundary conditions on the pilot node, even when KEYOPT(2) = 1.

Considerations for Fluid Penetration Loading

To model the fluid penetration loads shown in Figure 169.3: Fluid Penetration Pressure Directions, use the SFE command to specify the fluid pressures in the normal (LKEY = 1) and tangential directions (LKEY = 3) in the element coordinate system (ESYS) and the fluid penetration starting points (LKEY = 2). You must also set KEYOPT(10) = 1 to apply the fluid pressure loading to the target element. For more information, see Applying Fluid-Pressure-Penetration Loads in the Contact Technology Guide.

Figure 169.3: Fluid Penetration Pressure Directions

TARGE169 Output Data

The solution output associated with the element is shown in Table 169.2: TARGE169 Element Output Definitions. The following notation is used:

The Element Output Definitions table uses the following notation:

A colon (:) in the Name column indicates that the item can be accessed by the Component Name method (ETABLE, ESOL). The O column indicates the availability of the items in the file jobname.out. The R column indicates the availability of the items in the results file.

In either the O or R columns, “Y” indicates that the item is always available, a letter or number refers to a table footnote that describes when the item is conditionally available, and “-” indicates that the item is not available.

You can display or list the actual fluid pressure applied to the target element through several POST1 postprocessing commands, as shown below:

PLESOL,CONT,FPRS
PLNSOL,CONT,FPRS
PRESOL,CONT
PRNSOL,CONT

Note that only the FPRS (fluid penetration pressure) output item is meaningful when the PRESOL and PRNSOL commands are used for target elements.

Table 169.3: TARGE169 Item and Sequence Numbers lists output available through the ETABLE command using the Sequence Number method. See Creating an Element Table in the Basic Analysis Guide and The Item and Sequence Number Table in this reference for more information. The following notation is used in Table 169.3: TARGE169 Item and Sequence Numbers:

TARGE169 Assumptions and Restrictions

TARGE169 Product Restrictions

There are no product-specific restrictions for this element.