ANSYS命令流完全指南：2023R1版

需积分: 5 167 浏览量更新于2024-06-14 收藏 22.44MB PDF 举报

"ANSYS命令流帮助文档是官方提供的详细指南，涵盖了ANSYS软件的CommandReference，主要针对Release 2023R1版本。该文档旨在帮助用户理解和使用ANSYS命令流（APDL）进行参数化操作。文档由ANSYS, Inc.发布，包含了ANSYS, Ansys Workbench, AUTODYN, CFX, FLUENT等品牌及产品的商标信息，并强调未经许可禁止非法使用、分发或复制。此外，文档中还可能包含ANSYS软件的商业秘密和机密信息，仅供授权用户参考使用。" ANSYS命令流（APDL）是ANSYS软件的核心部分，它允许用户通过编程方式执行各种模拟任务，包括几何建模、网格划分、材料属性定义、边界条件设置、求解以及结果后处理等。APDL语言具有强大的功能，可以实现复杂的自动化工作流程，提高工作效率。在ANSYS APDL操作中，用户可以通过编写一系列命令来控制分析过程，这些命令可以是单行命令，也可以是组合成宏的多行命令。在参数化方面，ANSYS APDL支持变量和函数的使用，使得模型参数可以灵活调整，便于进行参数研究和优化。用户可以定义变量，然后在命令中引用这些变量，从而实现模型尺寸、材料属性等的改变。此外，还可以使用条件语句和循环结构，实现更高级的逻辑控制。通过这种方式，用户可以快速生成不同工况下的模型，进行批量分析。 ANSYS帮助文档通常会详细解释每个命令的功能、语法和使用示例，以便用户能够准确地理解和应用。例如，用户可以查找关于如何创建几何、指定材料属性、施加边界条件、解决静态或动态问题、后处理结果等方面的命令。此外，文档还会提供错误处理和调试技巧，帮助用户解决在使用过程中遇到的问题。 "ANSYS 命令流帮助文档"是ANSYS用户的重要参考资料，无论新手还是经验丰富的用户，都可以从中获取必要的信息，提升自己的ANSYS使用技能。通过深入学习和熟练掌握APDL，用户可以更加高效、精准地完成各种工程仿真任务。

! @ # $ % ^ & * ( ) _ - +

= | \ { } [ ] " ' / < > ~ `

Numeric data may be input in a variety of ways as described in Data Input (p. 5). Some commands

are switches of the form Commandname,Key where Key can be 0, NO or OFF to toggle the switch off;

or 1, YES or ON to toggle the switch on.

Degree of Freedom -- The degrees of freedom are the primary nodal unknowns determined by the

analysis. They may be displacements, rotations, temperatures, pressures, voltages, etc. A degree of

freedom is defined by a node number and a label, for example, 1 UX, 87 ROTZ, 4 TEMP, etc. Derived

results, such as stresses, heat flows, etc. are computed from the degree of freedom results and are

considered secondary unknowns.

Element types with unequal sets of degrees of freedom can be combined in a single structure. For ex-

ample, a 2D structure composed of 2D solid elements having two degrees of freedom (UX, UY) at each

node and a 2D beam element having three degrees of freedom (UX, UY, ROTZ) at each node will have

the latter three degrees of freedom at the common nodes. Nodes which do not have a beam element

attached will have only two degrees of freedom with ROTZ eliminated from the solution printout.

Field -- The command name and data items entered on a command are separated into consecutive

fields. A field is assumed to be as "wide" as the number of characters specified. A comma is used to

end one field and begin the next.

Line -- A line of input is a physical record read by the computer. Input lines are limited to 640 characters

(including preceding blanks, commas, and any special characters). For file input, a line is represented

by one 640 column data record. For interactive input, a line is the string of characters (640 maximum)

entered before the RETURN key is pressed. Several commands may be put on one line as described in

Data Input (p. 5). Blank lines are permitted for clarity.

Command name -- Only the first four characters of any alphabetic (or alphanumeric) command name

are interpreted by the program (except as noted for certain commands, such as /POSTN, /AUXN. *EN-

DDO (p. 628), etc.). The remaining characters of the field are ignored. Names shown with fewer than

four characters are assumed to have blanks up through the fourth character as part of the name. For

example, this sample ET (p. 678) command may be input as ET (p. 678),1,42 or ET (p. 678) ,1,42 or

ET (p. 678) ,1,42, but not as ETABCD,1,42. Names may not contain special characters (as described in

Data Input (p. 5)). If the command name is omitted, the name defaults to the name of the previous

command, unless it was a slash (/) or star (*) command.

Postprocessing Phase -- The set of commands causing further processing of the solution output. These

commands consist of commands from the POST1 and POST26 processors. The postprocessing phase

may consist of input for several postprocessing sessions (in series).

Preprocessing Phase -- The set of commands related to defining the model. The preprocessing phase

consists of input from the PREP7 processor.

Program -- The collection of all processors (preprocessing, postprocessing, auxiliary, etc.) is called the

Mechanical APDL program.

Processor -- A group of related functions, such as model definition (PREP7) or results examination

(POST1).

of ANSYS, Inc. and its subsidiaries and affiliates.4

About This Reference

Run -- The collection of all commands between the system-level commands is called a run or session).

A session may also consist of several analyses in series (separated by a /CLEAR (p. 344) command).

Solution Phase -- The set of commands which apply boundary conditions to the model created in

preprocessing, then performs a solution for that set of boundary conditions. The solution phase may

consist of several solutions in series, such as a static solution, followed by a modal solution, etc.

1.3. Command Characteristics

The following characteristics apply to commands:

1.3.1. Data Input

1.3.2. Free-Format Input

1.3.3. Nonrestrictive Data Input

1.3.4. Condensed Data Input

1.3.5. Units

1.3.6. Command and Argument Defaults

1.3.7. File Names

1.3.8. Star and Slash Commands

1.3.1. Data Input

The data input for each command is described in this manual. Data should not be input in any un-

documented field, nor should other than documented values be input in any field. Also, the data input

described in this manual should not be used with any earlier version of the program. Some features

that allow easy input of data are free-format, nonrestrictive, and condensed input.

1.3.2. Free-Format Input

Free-format capability allows the user to input data in consecutive fields without having to space to

each field. The comma (,) character effectively ends the field so that the next character will be input

in the beginning of the next field. A blank field is skipped by having no data item between the

commas. Fields are assumed to be as wide as the number of characters specified. Input is converted

to formatted fields when coded files are written (of width large enough (16 characters maximum) to

minimize loss of accuracy).

Significant figures of output should not be expected to match that of input. Machine precision,

rounding of numbers when writing internal scratch files, etc., tend to lower the precision during the

analysis.

1.3.3. Nonrestrictive Data Input

Nonrestrictive data input allows the user to enter any form of data in a field and the Mechanical APDL

program will interpret it as required (integer, real, or alphabetic) or ignore it. Double precision is used

throughout the program for all real numbers. Alphabetic data may be entered in upper or lower case.

Lower case is internally converted to upper case within the program (except for case-sensitive applic-

ations, such as in comments, (text preceded by a !) titles, and file names.)

of ANSYS, Inc. and its subsidiaries and affiliates.

Command Characteristics

The following features are available with the nonrestrictive data input.

• No distinction is necessary between real and integer data.

• Data may be placed anywhere within the field.

• Real data input without a decimal point has the decimal point assumed after the right-most

digit.

• Real number values input to integer data fields will be rounded to the nearest integer. The

absolute value of integer data must fall between zero and 2,000,000,000.

• Element and node numbers (IDs) should be between 1 and 999,999,999. Element type, mater-

ial reference, real constant, section, and coordinate system IDs should be between 1 and

9,999,999. IDs larger than these may not be written out correctly in listings (xLIST commands),

CDWRITE (p. 291) files, LSWRITE (p. 1063) files, and other text-based output files.

• Exponents may be input in the field after the number. The E (or D) character must be used

(upper or lower case). The sign after the E character is assumed to be the sign associated with

the exponent (the absence of a sign is assumed to be +). The acceptable range of values for

real data is +/-1.0E+200 to +/-1.0E-200.

• A nonnumeric character in the numeric field (other than a valid convenience label, a parameter

name, or an E or D exponent character) will be ignored and will cause the remainder of the

field to be ignored. When the program can accept an alphanumeric label in a field, it will in-

terpret any alphanumeric input that matches a valid label as the appropriate label. In other

words, the program will not interpret a valid label as an identically named parameter. If you

truly want to use a parameter in place of a valid label, you can use forced parametric substitu-

tion (using % signs). A non-alphanumeric character in a label field is taken as part of the label.

Non-alphanumeric characters (such as CONTROL-characters, TAB-characters, and other terminal

editing characters) should be avoided since they may be used directly instead of being inter-

preted by the terminal.

1.3.4. Condensed Data Input

An option for condensing the data input is available with the $ character. This character effectively

ends a command and allows the next command to begin on the same line (at the next column). The

line must not extend beyond 640 characters (including all commas and $ signs). If a command cannot

be completed on the line, it should begin on the next line. Blank commands are ignored. The $

character should not be used following any command that causes a file switch to read additional

commands (such as the /INPUT (p. 923), *USE (p. 2021), CDREAD (p. 289), etc. commands, any "unknown

command" macro, or any do-loops or if-then-else constructs). The $ character should not be used

between a command and its required following format line (such as *VREAD (p. 2105), *VWRITE (p. 2126),

*MSG (p. 1158), etc.). The $ character should not be used after the ALLSEL (p. 112) command. Using

the $ character in interactive mode may result in unexpected output behavior.

1.3.5. Units

The Mechanical APDL program permits the use of any consistent set of units for length, force, time,

temperature, etc. Care must be taken to ensure that all input data are in the same set of units. The

/UNITS (p. 2015) command may be used to note the system of units being used. Temperatures may

be absolute or relative in most cases. For problems requiring absolute temperatures, such as those

of ANSYS, Inc. and its subsidiaries and affiliates.6

About This Reference

involving creep, swelling, or radiation, temperatures may be input as Celsius or Fahrenheit, for con-

venience, with a temperature shift from absolute zero (TOFFST (p. 1969)).

1.3.6. Command and Argument Defaults

To minimize the amount of data input, most commands have defaults which apply both to the

command itself and to any arguments.

Command Defaults

A command default refers to the specification or behavior that is assumed when a command is not

issued. For example, if you do not issue the /FILNAME (p. 747) command, the jobname defaults to

FILE (or whatever jobname was specified when you entered the program).

Argument Defaults

An argument default is the value assumed for a command argument if the argument is not specified.

For example, if you issue the command N (p. 1181),10 (defining node 10 with the X, Y, Z coordinate

arguments left blank), the node is defined at the origin; that is, X, Y, and Z default to zero.

Values for numeric arguments (such as X, Y, Z) typically default to zero, although exceptions exist for

some commands, such as those with arguments specifying coefficients or tolerances. Such exceptions

are noted in the documentation for those commands.

When an argument has a nonzero default, entering a blank or a zero for that argument triggers the

nonzero default value. If an effective zero is desired for such an argument, input a very small number

(such as 1E-14) instead.

In cases where no default is indicated or obvious for an argument, enter the desired value. Such ar-

guments have no favored default value and require an explicit input value.

Some Command Defaults May Differ According to Product

The defaults for some commands and their arguments may differ depending on which product is

using the commands. The "Product Restrictions" section of the descriptions of the affected

commands clearly documents such cases.

If you intend to use your input file in more than one product, it is good practice to explicitly specify

commands and argument values, rather than letting them default. Otherwise, behavior in the other

product may differ from what you expect.

1.3.7. File Names

Various files are used during a session for reading, writing, and storing data. Program-generated files

are identified by a name, a system-dependent separator, and an extension (as in the form fname.ext).

The name is obtained from the Jobname (250 characters maximum, including the directory name)

as defined with the execution command. (Windows cannot create directory names longer than 245

characters.)

Unless otherwise specified, the Jobname defaults to a system-dependent name (usually FILE). The

extension is a two- to four-character identifier. (See Program-Generated Files in the Basic Analysis

of ANSYS, Inc. and its subsidiaries and affiliates.

Command Characteristics

Guide.) For example, the error message file (which has the identifier ERR) with a jobname of FILE

and separator (.) would be generated as FILE.ERR. If the Jobname is JOB1, the file would be named

JOB1.ERR. The documentation generically refers to program-generated files as Jobname.identi-

fier, such as Jobname.ERR for the error message file. Unless otherwise indicated, files are written

in the current working directory.

Some commands (such as /INPUT (p. 923) and /OUTPUT (p. 1304)) allow you to specify a file name

other than Jobname, and an extension other than the default extension. Such user-written files use

a naming convention similar to the Mechanical APDL-generated files except that the name (248

characters maximum, including the directory name) is user defined, and the extension (8 characters

maximum) is optional. The file name can include the directory path, but it is not necessary if you

want to use the default directory. File names containing directory paths must reference existing dir-

ectories. File and directory names may contain blank spaces, but strings containing blank spaces must

be enclosed in single quotes.

A system dependent separator is automatically written between file name and extension (if the exten-

sion exists) input on commands.

File name fields are usually restricted to 248 characters (including the directory name) in command

inputs. If you specify no directory path, the default path is your working directory, and you can use

all 248 characters for the file name.

To help ensure portability of input files across systems, the program has certain requirements for file

names. Avoid using special characters (+,-,*,/,$,!, etc.) in file names unless meaningful, and begin file

names with a letter. Some system-dependent special characters (such as ~) are not interpreted the

same as they are at the operating system level when used in path names. Parameter substitution can

be forced within the name, extension, or directory fields by enclosing the parameter within percent

(%) signs. For example, if I = 5, the name TEST%I% becomes TEST5.

Chinese and Japanese character file names are supported. The input file, output file, Jobname, and

working directory can include Chinese or Japanese characters in the file or folder name. These names

can be input at the command line, through the Mechanical APDL Launcher, or through commands

such as /FILNAME (p. 747), RESUME (p. 1569), and /ASSIGN (p. 198). Keep the following points in mind

when using Chinese or Japanese characters:

• The locale setting of the operating system must match that of the language being used for

naming.

• The file extensions must remain in standard English characters.

• Non-English characters are not supported by GUI operations. Specifically, the Open File button

on the Standard Toolbar does not accept Mechanical APDL files that are named with non-

English characters, and the GUI command input area does not accept commands that include

non-English characters.

1.3.8. Star and Slash Commands

The slash (/) and star ( *) commands are usually used for supplying general control instructions to

the program. For example, slash commands are used for entering a processor (/PREP7 (p. 1447),

/POST1 (p. 1429), etc.). Printout controls, display controls, and file controls are available within the slash

command set.

of ANSYS, Inc. and its subsidiaries and affiliates.8

About This Reference

剩余2167页未读，继续阅读

万物可爱co-bre

粉丝: 0
资源: 9

ANSYS命令流完全指南：2023R1版

ANSYS命令流总结.pdf

ANSYS命令流

ANSYS命令流详解

ansys_command.rar_ANSYS 命令流_ANSYS命令流_ansys_ansys command_命令流

ansys_minglingliu.rar_ANSYS 命令流_ANSYS命令流_ansys_ansys 开发_命令流

ansys命令流文档

Ansys命令流中文对照.zip_ANSYS命令流_ansys

ansys命令流

ANSYS命令流文件.pdf

ansys命令流很全的命令流

最新资源