Command summary
abaqus fromansys
job=job-name [input=input-file]
Command line options
# job
This option is used to specify the name of the Abaqus input file to be output by the translator. It is also the default name of the input file containing the ANSYS data. Diagnostics created by the translator will be written to a file named job-name.log.
# input
This option is used to specify the name of the file containing the ANSYS data if it is different from job-name.
# 3.2.33 TRANSLATING PAM-CRASH INPUT FILES TO PARTIAL Abaqus INPUT FILES
Product: Abaqus/Explicit
# Reference
• “Execution procedure for Abaqus: overview,” Section 3.1.1
# Overview
The translator from PAM-CRASH to Abaqus converts certain keywords in a PAM-CRASH input file into their equivalent in Abaqus/Explicit.
# Using the translator
The translator requires an input file created by PAM-CRASH Version 2002 or later. The input file can have any name and extension.
The PAM-CRASH data entries that are translated are listed in the tables below. Other PAM-CRASH keywords and data are skipped over and noted in the log file.
The translator creates a partial Abaqus input file that contains only the model data. You must provide history data (including output data) to complete the input.
# Element numbering and grouping
All elements must have unique element numbers. Elements that are assigned the same PART identification number are grouped together in an element set.
Except for connector elements that result from the translation of SPRING and KJOIN, section properties need to be entered in the PART section rather than individually in the element section. Elements that have different material or section properties should be given different PART identification numbers; that is, the same material and section properties must be applicable to all elements grouped in the same element set.
If elements that result from the translation of SPRING and KJOIN have different element data (such as frame numbers used to define local directions), and they are assigned the same PART identification number, the translator automatically separates them into different element sets.
# Material models
The translator supports only the material models shown in Table 3.2.33–3. All unsupported material models between Types 1 and 99 are translated as bilinear elastic-plastic, and all other material types are translated as linear elastic if a stress-strain law definition is required. In these cases the translator provides nominal values for the material properties.
# History section data
The translator creates a history section based partially on keywords (except TITLE) from the control section of the PAM-CRASH file as shown in Table 3.2.33–1. Other control data are unsupported.
# Summary of PAM-CRASH entities translated
Table 3.2.33–1 Control section data.
| PAM-CRASH keyword | Abaqus equivalent |
| PART / BAR | Truss element properties and grouping data |
| PART / BEAM | Beam element properties and grouping data |
| PART / SPRING | Connector behavior and grouping data |
| PART / KJOIN | Connector type, behavior, and grouping data |
| PART / SOLID | Solid element properties and grouping data |
| PART / SHELL | Shell element properties and grouping data |
| PART / MEMBR | Membrane element properties and grouping data |
| PART / TIED | Mesh tie constraint data and parameters |
| PART / PLINK | Mesh-independent fastener data and parameters |
Table 3.2.33–3 Material section data.
| PAM-CRASH keyword | Abaqus equivalent |
| MATER / Types 1, 16, 41, 99 | C3D4/C3D6/C3D8R; solid material model data |
| MATER / Types 100, 101, 102, 103, 105 | S3RS/S4RS; shell material model data |
| MATER / Types 150, 151 | M3D3/M3D4/M3D4R and *USER MATERIAL |
| MATER / Types 200, 201, 202 | T3D2/B31; beam and truss material model data |
| PAM-CRASH keyword | Abaqus equivalent |
| RWALL(Stationary, segmented finite rigid wall)Velocity flag=0Wall description=20 | *RIGID BODY and *CONTACT |
| RBODYTypes 0, 3 | *RIGID BODY and/or *MPC (type BEAM)To define a group of elements as a rigid body, enter the part identification number of that element group as the PART entity $^{1}$ .To define an element as a rigid body, enter the element number as the ELE entity or enter all the element node numbers as the NOD entity $^{2}$ . |
| RBODYType 1 | CONN3D2, *CONNECTOR SECTION [PROJECTION CARTESIAN + PROJECTION FLEXION-TORSION], *CONNECTOR DAMAGE INITIATION, and *CONNECTOR DAMAGE EVOLUTION |
| CNTACSliding interface types:33, 34, 36, 37, 46 | *CONTACT, *CONTACT INCLUSIONS, *CONTACT EXCLUSIONS, *CONTACT PROPERTY ASSIGNMENT, *CONTACT FORMULATION, *SURFACE INTERACTION, and *SURFACE PROPERTY ASSIGNMENT |
| TIED | *TIE |
| $^{1}$ If PART entities are used to define a rigid body, RBODY is translated as *RIGID BODY. $^{2}$ If the ELE and NOD entities constitute all elements in a part, RBODY is translated as *RIGID BODY. If the ELE and NOD entities do not constitute all elements in a part (i.e., if the part consists of both rigid and deformable elements), RBODY is translated as *MPC (MPC type BEAM), a beam-type multi-point constraint for the set of nodes that consists of all input NOD entities and nodes extracted from all ELE entities. |
Table 3.2.33–7 Nodes/faces/elements entity selection data.
| PAM-CRASH keyword | Abaqus equivalent |
| GASPEC | *FLUID BEHAVIOR, *MOLECULAR WEIGHT, and *CAPACITY |
| BAGIN | *PHYSICAL CONSTANTS and *FLUID CAVITY |
| GEN_INI_COND | *INITIAL CONDITIONS |
| GAS | *FLUID CAVITY, BEHAVIOR or MIXTURE |
| CHAMBER | *NODE, NSET=ref_node_name; *SURFACE, TYPE=ELEMENT; and *FLUID CAVITY |
| EXT_SKIN | M3D3/M3D4 and *SURFACE, TYPE=ELEMENT |
| WALL_OPENING | *FLUID EXCHANGE, *FLUID EXCHANGE ACTIVATION, and *FLUID EXCHANGE PROPERTY |
| WALL_FABRIC | *FLUID EXCHANGE, *FLUID EXCHANGE ACTIVATION, and *FLUID EXCHANGE PROPERTY |
| LEAKAGE | *FLUID EXCHANGE, *FLUID EXCHANGE ACTIVATION, and *FLUID EXCHANGE PROPERTY |
| PAM-CRASH keyword | Abaqus equivalent |
| GROUP | Convert entities to Abaqus equivalents |
| METRIC | *INITIAL CONDITIONS, TYPE=REF COORDINATE |
| SENSOR | Type-1: use activation time in *AMPLITUDEType-4: use belt feed rate in *CONNECTOR LOCK |
| FUNCT | Data for material properties and time-dependent parameters, such as *AMPLITUDE, *CONNECTOR ELASTICITY, *PLASTIC, and *FLUID EXCHANGE PROPERTY |
| RUPMO | Data for connector behavior, such as *CONNECTOR DAMAGE INITIATION, *CONNECTOR DAMAGE EVOLUTION, *CONNECTOR POTENTIAL, and *CONNECTOR HARDENING |
| THELE | Element sets defined as *ELSET; output quantities are not specified for the element set |
| THNOD | Node sets defined as *NSET; output quantities are not specified for the node set |
Command summary