Operations Guide Table of Contents
1. Introducing ANSYS 2. The ANSYS Environment 2.1. Entering a Processor
2.2. Exiting from a Processor or ANSYS
2.2.1. Stopping the Input of a File 2.3. The ANSYS Database
2.3.1. Defining or Deleting Database Items 2.3.2. Saving the Database 2.3.3. Restoring Database Contents
2.3.4. Using the Session Editor to Modify the Database 2.3.5. Clearing the Database 2.4. ANSYS Program Files
2.4.1. ANSYS File Types 2.4.2. ANSYS File Sizes 2.4.3. The Jobname.LOG File
2.5. Communicating With the ANSYS Program
2.5.1. Communicating Via the Graphical User Interface (GUI) 2.5.2. Communicating Via Commands 2.5.3. Command Defaults 2.5.4. Abbreviations
2.5.5. Command Macro Files
3. Running the ANSYS Program 3.1. Starting an ANSYS Session from the Command Level 3.2. The Mechanical APDL Product Launcher
3.2.1. Starting an ANSYS Session from the Start Menu/Launcher 3.2.2. Launcher Menu Options 3.3. Interactive Mode
3.3.1. Executing the ANSYS or DISPLAY Programs from Windows Explorer 3.4. Batch Mode
3.4.1. Starting a Batch Job from the Command Line 3.5. Choosing an ANSYS Product via Command Line 3.6. Setting Preferences with the start130.ans File
3.6.1. The start130.ans File
4. Using the ANSYS GUI 4.1. GUI Controls
4.1.1. A Dialog Box and Its Components 4.2. Activating the GUI 4.3. Layout of the GUI
4.3.1. The Utility Menu 4.3.2. The Standard Toolbar
第 1 页
Operations Guide 4.3.3. Command Input Options 4.3.4. The ANSYS Toolbar 4.3.5. The Main Menu 4.3.6. The Graphics Window 4.3.7. The Output Window
4.3.8. Creating, Modifying and Positioning Toolbars
5. Graphical Picking 5.1. Locational and Retrieval Picking 5.2. Query Picking
5.2.1. The Model Query Picker 5.2.2. The Results Query Picker
6. Customizing ANSYS and the GUI 6.1. The Configuration File
6.2. Splitting Files Across File Partitions 6.3. Customizing the GUI
6.3.1. Changing the GUI Layout 6.3.2. Changing Colors and Fonts
6.3.3. Changing the GUI Components Shown at Start-Up 6.3.4. Changing the Mouse and Keyboard Focus
6.3.5. Changing the Menu Hierarchy and Dialog Boxes Using UIDL 6.3.6. Creating Dialog Boxes Using Tcl/Tk 6.4. ANSYS Neutral File Format
6.4.1. Neutral File Specification
6.4.2. AUX15 Commands to Read Geometry Into the ANSYS database 6.4.3. A Sample ANSYS Neutral File Input Listing
7. Using the ANSYS Session and Command Logs 7.1. Using the Session Log File 7.2. Using the Database Command Log 7.3. Using a Command Log File as Input
Release 13.0 - ? 2010 SAS IP, Inc. All rights reserved.
第 2 页
Operations Guide
Chapter 1: Introducing ANSYS
ANSYS finite element analysis software enables engineers to perform the following tasks:
? Build computer models or transfer CAD models of structures, products, components, or
systems.
? Apply operating loads or other design performance conditions.
? Study physical responses, such as stress levels, temperature distributions, or electromagnetic
fields.
? Optimize a design early in the development process to reduce production costs.
? Do prototype testing in environments where it otherwise would be undesirable or impossible
(for example, biomedical applications).
The ANSYS program has a comprehensive graphical user interface (GUI) that gives users easy, interactive access to program functions, commands, documentation, and reference material. An intuitive menu system helps users navigate through the ANSYS program. Users can input data using a mouse, a keyboard, or a combination of both.
This manual provides basic instructions for operating the ANSYS program: starting and stopping the product, using and customizing its GUI, using the online help system, etc. For other information about using ANSYS, see the following documents:
? For general instructions on performing finite element analyses for any engineering discipline,
see the Basic Analysis Guide, the Modeling and Meshing Guide, and the Advanced Analysis Techniques Guide. ? For information about performing specific types of analysis (thermal, structural, etc.), see the
applicable Analysis Guide.
? For examples of analyses, see the Mechanical APDL Tutorials and Verification Manual. ? For reference information about ANSYS commands, elements, and theory, see the Command Reference, Element Reference, and Theory Reference for the Mechanical APDL and Mechanical Applications.
第 3 页
Operations Guide
Chapter 2: The ANSYS Environment
The ANSYS program is organized into two basic levels:
? Begin level
? Processor (or Routine) level
The Begin level acts as a gateway into and out of the program. It is also used for certain global program controls such as changing the jobname, clearing (zeroing out) the database, and copying binary files. When you first enter the program, you are at the Begin level.
At the Processor level, several processors are available. Each processor is a set of functions that perform a specific analysis task. For example, the general preprocessor (PREP7) is where you build the model, the solution processor (SOLUTION) is where you apply loads and obtain the solution, and the general postprocessor (POST1) is where you evaluate the results of a solution. An additional postprocessor, POST26, enables you to evaluate solution results at specific points in the model as a function of time.
The following environment topics are available:
? Entering a Processor ? Exiting from a Processor or ANSYS ? The ANSYS Database ? ANSYS Program Files ? Communicating With the ANSYS Program
2.1. Entering a Processor
In general, you enter a processor by selecting it from the ANSYS Main Menu in the Graphical User Interface (GUI). For example, choosing Main Menu > Preprocessor takes you into PREP7. Alternatively, you can use a command to enter a processor (the format is /name, where name is the name of the processor). Table 2.1: Processors (Routines) Available in ANSYS lists each processor, its function, and the command to enter it.
Table 2.1 Processors (Routines) Available in ANSYS Processor PREP7 SOLUTION POST1 POST26 OPT Function Build the model (geometry, materials, etc.) Apply loads and obtain the finite element solution Review results over the entire model at specific time points Review results at specific points in the model Main Menu > TimeHist Postpro as a function of time Improve an initial design Main Menu > Design Opt /POST26 /OPT Main Menu > General Postproc /POST1 GUI Path Main Menu > Preprocessor Main Menu > Solution Command /PREP7 /SOLU 第 4 页
Operations Guide PDS Quantify the effect of scatter and uncertainties associated with input variables of a finite element analysis on the results of the analysis AUX2 AUX12 Dump binary files in readable form Calculate radiation view factors and generate a radiation matrix for a thermal analysis AUX15 SX Translate files from a CAD or FEA program Test the response of different input values. Utility Menu > File > Import Main Menu > DesignXplorer > Solution > Solve /AUX15 /SX Utility Menu > File > List > Binary Files Utility Menu > List > Files > Binary Files Main Menu > Radiation Matrix /AUX12 /AUX2 Main Menu > Prob Design /PDS 2.2. Exiting from a Processor or ANSYS
To return to the Begin level from a processor, pick Main Menu > Finish or issue the FINISH (or /QUIT) command. You can move from one processor to another without returning to the Begin level. Simply pick the processor you want to enter, or issue the appropriate command.
To leave the ANSYS program (and return to the system level), pick Utility Menu > File > Exit or use the /EXIT command to display the Exit from ANSYS dialog box. By default, the program saves the model and loads portions of the database automatically and writes them to the database file, Jobname.DB. If a backup of the current database file already exists, ANSYS writes it to Jobname.DBB. Options in the dialog box (and on the /EXIT command) allow you to save other portions of the database or to quit without saving.
2.2.1. Stopping the Input of a File
You can also stop the processing of an ANSYS file as it is being input. Most files of more than a few lines will display the ANSYS Process Status window at the top of the screen. If you want to terminate the input of a file, select the STOP button on the ANSYS Process Status window. ANSYS itself does not stop when you select the STOP button. Stopping file input is useful if you inadvertently input a binary file.
To input a new file, select Utility Menu > File > Clear & Start New to clear the current file from memory, then select a file to input. If you want to return to processing the original file, select Utility Menu > File > Read Input from... and select the name of the file, the line number or label to resume from, and select the OK button. See the /INPUT command for more information on resuming a file input process.
2.3. The ANSYS Database
In one large database, the ANSYS program stores all input data (model dimensions, material properties, load data, etc.) and results data (displacements, stresses, temperatures, etc.) in an organized fashion. The main advantage of the database is that you can list, display, modify, or delete any specific data item quickly and easily.
No matter which processor you are in, you are working with the same database. This gives you basic access to the model and loads portions of the database from anywhere in the program. \means the ability to select, list, or display an item.
第 5 页
Operations Guide
The following database topics are available:
? Defining or Deleting Database Items ? Saving the Database ? Restoring Database Contents ? Using the Session Editor to Modify the Database ? Clearing the Database
2.3.1. Defining or Deleting Database Items
To define items, or to delete items from the database, you must be in the appropriate processor. For example, you can define nodes, elements, and other geometry only in PREP7, the general preprocessor. You can specify and apply loads in either the PREP7 or the SOLUTION processor, and you can declare optimization variables only in OPT (the design optimization processor). However, you can select geometry items, list them, or display them from anywhere in the program, including the Begin level.
2.3.2. Saving the Database
Because the database contains all your input data, you should frequently save copies of it to a file. To do this, pick Utility Menu > File > Save as Jobname.DB or issue the SAVE command. Either choice writes the database to the file Jobname.DB. If you use the SAVE command, you have the option to save: ? the model data only
? the model and solution data
? the model, solution and preprocessing data
To specify a different file name, pick Utility Menu > File > Save as or use the appropriate fields on the SAVE command. Any save operation first writes a backup of the current database file (if the database already exists) to Jobname.DBB. If a Jobname.DBB file already exists, the new backup file overwrites it. For a static or transient structural analysis, the file Jobname.RDB (a copy of the database) will be automatically saved at the first substep of the first load step.
2.3.3. Restoring Database Contents
To restore data from the database file, pick Utility Menu > File > Resume Jobname.DB or issue the RESUME command. This reads the file Jobname.DB. To specify a different file name, pick Utility Menu > File > Resume from or use the appropriate fields on the RESUME command.
You can save or resume the database from anywhere in the ANSYS program, including the Begin level. A resume operation replaces the data currently in memory with the data in the named database file. Using the save and resume operations together is useful when you want to \When you do a multiframe restart, ANTYPE,,REST automatically resumes the .RDB file for the current job.
2.3.4. Using the Session Editor to Modify the Database
During an analysis, you may want to modify or delete commands entered since your last SAVE or RESUME. You can access the session editor by issuing the UNDO command, or by choosing Main Menu > Session Editor. The session editor display is shown below.
第 6 页
Operations Guide
Figure 2.1 The Session Editor
Use this dialog for displaying and editing the string of operations performed since your last SAVE or RESUME command. You can modify command parameters, delete whole sections of text, and even save a portion of the command string to a separate file.
You can access the following file operations from the session editor dialog:
? OK: Enters the series of operations displayed in the window below. You will use this option to
input the command string after you have modified it.
? Save: Saves the command string displayed in the window below to a separate file. ANSYS
names the file Jobnam000.cmds, with each subsequent save operation incrementing the filename by one digit. You can use the /INPUT command to reenter the saved file. ? Cancel: Dismisses this window and returns to your analysis. ? Help: Displays the command reference for the UNDO command.
The Session Editor is available in interactive (GUI) mode only. If no SAVE or RESUME command has been issued during your analysis, all commands from your current session will be executed, including your start130.ans file, if present.
2.3.5. Clearing the Database
While building a model, sometimes you may want to clear out the database contents and start over. To do so, choose Utility Menu > File > Clear & Start New or issue the /CLEAR command. Either method clears (zeros out) the database stored in memory. Clearing the database has the same effect as leaving and reentering the ANSYS program, but does not require you to exit.
2.4. ANSYS Program Files
The ANSYS program writes and reads many files for data storage and retrieval. File names follow this pattern: Name.Ext
第 7 页
Operations Guide
Name defaults to the jobname, which you can specify while entering the ANSYS program or by choosing Utility Menu > File > Change Jobname (equivalent to issuing the /FILNAME command). The default jobname is FILE (or file).
Ext is a unique, two- to four-character ANSYS identifier that identifies the contents of the file. For example, Jobname.DB is the database file, Jobname.EMAT is the element matrix file, and Jobname.GRPH is the neutral graphics file. Some systems (such as PCs) truncate the extension to three characters. Also, the extension may be in lowercase, depending on the system.
The following program file topics are available:
? ANSYS File Types ? ANSYS File Sizes ? The Jobname.LOG File
2.4.1. ANSYS File Types
Table 2.2: ANSYS File Types and Formats lists the main ANSYS file types and their formats. For more information about files, see File Management and Files in the Basic Analysis Guide.
Table 2.2 ANSYS File Types and Formats File Type Log file Error file Output file Database file Results file: structural or coupled thermal magnetic FLOTRAN Load step file Graphics file Element matrices File Name Jobname.LOG Jobname.ERR Jobname.OUT Jobname.DB Jobname.xxx Jobname.RST Jobname.RTH Jobname.RMG Jobname.RFL Jobname.Sn Jobname.GRPH Jobname.EMAT ASCII ASCII (special format) Binary ASCII ASCII ASCII Binary Binary File Format On the following ANSYS commands, you can specify the name and path of the file to be written: /ASSIGN *LIST /COPY /OUTPUT *CREATE /PSEARCH /DELETE /RENAME /INPUT
In such cases, the filename can contain up to 248 characters, including the directory name, and the extension can contain up to eight characters. If the file name uses more than 248 characters, including the directory, you must use a soft link on UNIX/Linux systems.
ANSYS can process blanks in file or directory names, so blank spaces are allowed in ANSYS object names. Be aware that many UNIX/Linux commands do not support object names with spaces. When an object has a blank space in its name, always enclose the name in a pair of single quotes.
第 8 页
Operations Guide
On UNIX/Linux systems, all directory names except for /(root) should end with a slash (/). For example, to run the ANSYS program using an input file called vm1.dat, which resides in the directory /ansys_inc/v130/ansys/data/verif, use the following commands: ansys130
/inp,vm1,dat, /ansys_inc/v130/ansys/data/verif/
On Windows systems, you must use back slashes (\\) instead of slashes in directory names. For example, on a Windows system, the directory path shown in the UNIX example above looks like this: /inp,vm1,dat, Program Files\\Ansys Inc\\V130\\ANSYS\\data\\verif\\
2.4.2. ANSYS File Sizes
The maximum size of an ANSYS file depends on the file system on the hard drive partition being used. Most computer systems now handle very large files without any need for the automatic file splitting option that is provided in ANSYS. The FAT32 file system is occasionally still used on some Windows and Linux systems and has a file size limitation of 4 GB. We recommend converting any FAT32 hard drives to a file system that can support much larger files (e.g., for Windows, we recommend converting to the NTFS file system). If you are running a problem that will create an ANSYS file over 4 GB on a system using a FAT32 hard drive, then you can use the /CONFIG,FSPLIT command to set the maximum ANSYS file size to any value under 4 GB.
2.4.3. The Jobname.LOG File
The Jobname.LOG file (also called the session log) is especially important, because it provides a complete log of your ANSYS session. The file opens immediately when you enter the ANSYS program, and it records all commands you execute, whether you execute those commands via GUI paths or type them in directly. You can read the Jobname.LOG file, view it while in ANSYS, edit it, and input it later.
The ANSYS program always appends log data to the log file instead of overwriting it. If you change the jobname while in an ANSYS session, the log file name does not change to the new jobname. For more information about Jobname.LOG, see Using the ANSYS Session and Command Logs.
2.5. Communicating With the ANSYS Program
The easiest way to communicate with the ANSYS program is by using the ANSYS menu system, called the Graphical User Interface (GUI).
2.5.1. Communicating Via the Graphical User Interface (GUI)
The GUI consists of windows, menus, dialog boxes, and other components that allow you to enter input data and execute ANSYS functions simply by picking buttons with a mouse or typing in responses to prompts. All users, both beginner and advanced, should use the GUI for interactive ANSYS work. See Using the ANSYS GUI for an extensive discussion of how to use the GUI. The rest of this section describes other topics related to communication with ANSYS commands, abbreviations, etc.
2.5.2. Communicating Via Commands
第 9 页
Operations Guide
Commands are the instructions that direct the ANSYS program. ANSYS has more than 1200 commands, each designed for a specific function. Most commands are associated with specific (one or more) processors, and work only with that processor or those processors.
To use a function, you can either type in the appropriate command or access that function from the GUI (which internally issues the appropriate command). The Command Reference describes all ANSYS commands in detail, and also tells you whether each command has an equivalent GUI path. (A few commands do not.)
ANSYS commands have a specific format. A typical command consists of a command name in the first field, usually followed by a comma and several more fields (containing arguments). A comma separates each field. For example, the F command, which applies a force at a node, looks like this: F,NODE,Lab,VALUE To apply an X-direction force of 2000 at node number 376, the F command would read as follows: F,376,FX,2000
You can abbreviate command names to their first four characters (except as noted in the Command Reference). For example, FINISH, FINIS, and FINI all have the same meaning. Some \(such as ADAPT and RACE) are actually macros. You must enter macro names in their entirety.
Note:
If you are not sure whether an instruction is a command or a macro, see the Command Reference.
Commands that begin with a slash ( / ) usually perform general program control tasks, such as entry to routines, file management, and graphics controls. Commands that begin with a star ( * ) are part of the ANSYS Parametric Design Language (APDL). See the ANSYS Parametric Design Language Guide for details.
Command arguments may take a number or an alphanumeric label, depending on their purpose. In the F command example described previously, NODE and VALUE are numeric arguments, but Lab is an alphanumeric argument. In this and other ANSYS manuals, numeric arguments appear in all uppercase italic letters (as in NODE and VALUE), and alphanumeric arguments appear in initial uppercase italic format (as in Lab). Some commands (for example, /PREP7, /POST1, FINISH, etc.) have no arguments, so the entire command consists of just the command name.
Some general rules and guidelines for commands are listed below:
? When you enter commands, the arguments do not have to be in specific columns.
? You can use successive commas to skip arguments. When you do so, ANSYS uses default
values for the omitted arguments (as discussed in the individual command descriptions).
? You can string together multiple commands on the same line by using the $ character as the
delimiter for each command. (For restrictions on use of the $ delimiter, see the Command Reference.) ? The maximum number of characters allowed per line is 640, including commas, blank spaces,
$ delimiters, and any other special characters.
Note: Other software programs and printers may wrap text to the next line or truncate the text after a certain character.
第 10 页
Operations Guide
? 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.
? The acceptable range of values for real data is +/-1.0E+200 to +/-1.0E-200. No exponent can
exceed +200 or be less than -200. The program accepts real numbers in integer fields, but rounds them to the nearest integer. You can specify a real number using a decimal point (such as 327.58) or an exponent (such as 3.2758E2). The E (or D) character, used to indicate an exponent, may be in upper or lower case. This limit applies to all ANSYS input commands, regardless of platform.
Even though all ANSYS input must be within the allowed range, all numeric operations, including parametric operations, can produce numbers to machine precision, which may exceed the ANSYS input range.
? ANSYS interprets numbers entered for Angle arguments as degrees. Note that there are
functions in ANSYS that could use radians if the *AFUN command had been used. ? The following special characters are not allowed in alphanumeric arguments:
! @ # $ % ^ & * ( ) _ - + = | \\ { } [ ] \ ' / < > ~ `
? Exceptions are filename and directory arguments, where some of these characters may be
required to specify system-dependent pathnames. However, using special characters in filename and directory arguments could result in ANSYS or the operating system misreading the argument. We strongly recommend that you limit filename and directory arguments to A-Z, a-z, 0-9, -, _, and spaces. Any text prefaced by an exclamation mark (!) is treated as a comment.
? Avoid using tabs (to line up comments, for instance) or other control (CTRL) sequences. They
usually generate device-dependent characters that the program cannot recognize.
? If you are a longtime ANSYS user, avoid using commands that have been removed from the
currently documented command set. Such commands are obsolete and may cause difficulties.
2.5.3. Command Defaults
To minimize the amount of data input, most commands have defaults. There are two types of defaults: command default and argument default.
A command default is the specification assumed when a command is not issued. For example, if you do not issue the /FILNAME command, the jobname defaults to FILE (or whatever jobname was specified when you entered the ANSYS program).
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,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. Numeric arguments (such as X, Y, Z) default to zero except as noted in the Command Reference. The command descriptions usually explain defaults for other arguments.
Note:
The defaults for some commands and their arguments differ depending on which ANSYS product is using the commands. The \clearly documents such cases. If you plan to use your input file in more than one ANSYS product, you
第 11 页
Operations Guide
should explicitly specify commands or command argument values, rather than letting them default. Otherwise, behavior in the other ANSYS product may be different from what you expect.
2.5.4. Abbreviations
If you use a command or a GUI function frequently, you can rename it or abbreviate it to a string of up to eight alphanumeric characters using one of the following: Command(s): *ABBR Utility Menu > Macro > Edit Abbreviations
GUI:
Utility Menu > MenuCtrls > Edit Toolbar
For example, the following command defines ISO as an abbreviation for the command /VIEW,,1,1,1 (which specifies isometric view for subsequent graphics displays): *ABBR,ISO,/VIEW,,1,1,1
Keep the following rules and guidelines in mind when creating abbreviations:
? The abbreviation must begin with a letter and should not have any spaces.
? If an abbreviation that you set matches an ANSYS command, the abbreviation overrides the
command. Therefore, use caution in choosing abbreviation names.
? You can abbreviate up to 60 characters, and up to 100 abbreviations are allowed per ANSYS
session.
In the GUI, abbreviations appear as push buttons on the Toolbar, which you can execute with a quick click of the mouse. For details, see the section on using the toolbar in Using the ANSYS GUI .
2.5.5. Command Macro Files
You can record a frequently used sequence of ANSYS commands in a macro file, thus creating a personalized ANSYS command. If you enter a command name that ANSYS does not recognize, it searches for a macro file by that name (with an extension of .MAC or .mac). If the file exists, ANSYS executes it.
On UNIX/Linux and Windows systems, the ANSYS program searches for macro files in the following order:
? ANSYS looks first in the ANSYS APDL directory.
? It then looks at the directories that have been defined for the environmental variable
ANSYS_MACROLIB. You can set up the ANSYS_MACROLIB variable after the installation of ANSYS software and before the program is started.
On UNIX/Linux, the structure for ANSYS_MACROLIB is: dir1/:dir2/:dir3/
On Windows, the structure is: c:\\dir1\\;d:\\dir2\\;e:\\dir3
The letter to the left of the colon indicates the drive where the directory is stored.
Enter up to 2048 characters for the entire string. Dir1 is searched first, followed by dir2, dir3, etc. These files provide customization at both the site and user levels.
? Next, on UNIX/Linux systems, ANSYS looks in /PSEARCH or in the login directory. On
Windows systems, it looks in /PSEARCH or in the home directory. ? Finally, ANSYS looks in the current or working directory.
第 12 页
Operations Guide
ANSYS searches for both upper and lower case macro file names in each search directory, except /apdl on UNIX/Linux systems. If both exist in the search directory, the upper case file is used. Only upper case is used in the /apdl directory on UNIX/Linux systems.
The ANSYS installation media provide many ANSYS macro files that reside in the /apdl subdirectory. If you cannot use any of the ANSYS-provided macro files, contact your system administrator.
To access any macro, you simply enter its file name. For instance, to access the LSSOLVE.MAC file, you enter LSSOLVE. You can also access macros you created via the Utility Menu > Macro > Execute Macro menu path. However, this menu path will not work for any macros containing function granules (such as a call to a dialog box) or picking commands. Macros with these functions must be accessed by entering the macro name in the Input Window.
Specifying File Names in Windows
In the Windows environment, some devices/ports have specific names, such as PRN, COM1, COM2, LPT1, LPT2, and CON. The device/port names resemble files in that they can be opened, read from, written to, and closed. Entering the names of these devices/ports in ANSYS, however, causes unpredictable behavior, including system freezes or fatal error conditions. Therefore, do not issue PC device/port names as commands.
Configuring Search Paths on Windows Systems
1. In the Control Panel, click on the System Icon.
2. On Windows XP systems, click on My Computer on the Start Menu. Under System Tasks,
select View System Information. Select the Advanced Tab. Click on the Environment Variables button. Click New under System Variable. Enter the value of ANSYS_MACROLIB for the variable name. Enter
3. On Windows 2000 systems, select the Advanced tab. Click on the Environment Variables
button. Click on the New button under System Variables. Enter the value of ANSYS_MACROLIB for the variable name. Enter
第 13 页
Operations Guide
Chapter 3: Running the ANSYS Program
You can run the ANSYS program in interactive mode or in batch mode. In interactive mode (the default), you exchange information with the computer continuously. You can execute a command by selecting its menu path in the GUI or by typing it in directly. The ANSYS program processes the command in real time. Interactive mode allows you to use the GUI, online help, and various tools to create the engineering model in the graphics window and modify it as you work through the analysis.
In batch mode, you submit a file of commands to the ANSYS program. This command file may have been generated by a previous ANSYS session, by another program, or by creating a command file with an editor. On some operating systems, you can run a batch job in the background while doing other work on the computer. Batch mode is useful when you do not need to interact with the program, such as during the solution phase of an analysis.
ANSYS offers a set of separately-licensed \not have access to the GUI, to online help, or to other interactive features of ANSYS. For more information about the batch-only products, see your ANSYS sales representative.
There are a number of options for starting and setting options for your ANSYS session. You can enter the ANSYS program directly by issuing the ANSYS execution command at the command level and define aspects of the ANSYS operating system using the optional arguments for the execution command.
You can also use the ANSYS Launcher to set options for an ANSYS run and its auxiliary programs, such as the LS-DYNA solver.
The following ANSYS session topics are available:
? Starting an ANSYS Session from the Command Level ? The Mechanical APDL Product Launcher ? Interactive Mode ? Batch Mode ? Choosing an ANSYS Product via Command Line ? Setting Preferences with the start130.ans File
3.1. Starting an ANSYS Session from the Command Level
To start an interactive ANSYS session in graphics mode on UNIX/Linux systems, type the following command at the prompt: ansys130 -g
To start ANSYS from the MS-DOS command prompt on a Windows system, type the following command: ansys130
Always use the ANSYS-supplied scripts (ansys130 and launcher130) for running ANSYS. User-written scripts for running ANSYS products are not supported.
第 14 页
Operations Guide
You can specify any of the following options for the ANSYS execution command: -acc device -ansexe -b list or nolist -custom -d device Enables the use of GPU hardware to accelerate the analysis. See \Advanced Analysis Techniques Guide for more information. In the ANSYS Workbench environment, activates a custom ANSYS executable. Activates the ANSYS program in batch mode. The options -b list or -b by itself cause the input listing to be included in the output. The -b nolist option causes the input listing not to be included. For more information about running ANSYS in batch mode, see Batch Mode. Calls a custom ANSYS executable. See Running Your Custom Executable in the Guide to ANSYS User Programmable Features for more information. Specifies the type of graphics device. This option applies only to interactive mode. For UNIX/Linux systems, graphics device choices are X11, X11C, or 3D. For Windows systems, graphics device options are WIN32 or WIN32C, or 3D. -db value Defines the portion of workspace (memory) to be used as the initial allocation for the database. The default is 512 MB for 64-bit machines, 256 MB for 32-bit machines. Specify a negative number (-value) to use a fixed size throughout the run; useful on small memory systems (for example, 32-bit). -dir -dis -dvt -dyn -f option Defines the initial working directory. Using the -dir option overrides the ANSYS130_WORKING_DIRECTORY environment variable. Enables Distributed ANSYS. See the Distributed ANSYS Guide for more information. Enables ANSYS DesignXplorer advanced task (add-on). Enables LS-DYNA. Applicable only for ANSYS Structural and higher license levels. Sets ANSYS to run in fixed-memory mode. The no or off options set ANSYS to use dynamic memory allocation for scratch memory as needed (default setting). If you do not set any arguments, ANSYS uses fixed-mode memory allocation for scratch memory, but allows other sections of the ANSYS work space to grow as required. -g Launches the ANSYS program with the Graphical User Interface (GUI) on. If you select this option, an X11 graphics device is assumed for UNIX/Linux unless the -d option specifies a different device. This option is not used on Windows systems. To activate the GUI once ANSYS has started, you need to enter two commands in the ANSYS input window: /SHOW to define the graphics device, and /MENU,ON to activate the GUI. The -g option is valid only for interactive mode. Note: If you start ANSYS via the -g option, the program ignores any /SHOW command in the start130.ans file and displays a splash screen briefly before opening the GUI windows. -i inputname -j Jobname -l language Specifies the name of the file to read input into ANSYS for batch processing. On UNIX/Linux, the preferred method to indicate an input file is <. Specifies the initial jobname, a name assigned to all files generated by the program for a specific model. If you omit the -j option, the jobname is assumed to be file. Specifies a language file to use other than US English. This option is valid only if you have a translated message file in an appropriately named subdirectory in /ansys_inc/v130/ansys/docu (or Program Files\\Ansys Inc\\V130\\ANSYS\\docu on Windows systems). -m workspace -machines -mfm -mpi Specifies the total size of the workspace (memory) in megabytes used for the initial allocation. If you omit the -m option, the default is 1 GB (1024 MB) for 64-bit machines, 512 MB for 32-bit machines. Specifies the machines on which to run a Distributed ANSYS analysis. See Starting Distributed ANSYS in the Distributed ANSYS Guide for more information. Specifies the master field name in an ANSYS Multi-field solver - MFX analysis. See Starting and Stopping an MFX Analysis in the Coupled-Field Analysis Guide for more information. Specifies the type of MPI to use. See the Distributed ANSYS Guide for more information. 第 15 页
Operations Guide -mpifile -name value -np Specifies an existing MPI file (appfile) to be used in a Distributed ANSYS run. See Using MPI appfiles in the Distributed ANSYS Guide for more information. Defines ANSYS parameters at program start-up. The parameter name must be at least two characters long. For details about parameters, see the ANSYS Parametric Design Language Guide. Specifies the number of processors to use when running Distributed ANSYS or Shared-memory ANSYS. See the Distributed ANSYS Guide or the Advanced Analysis Techniques Guide for more information. -o outputname -p Specifies the name of the file to store the output from a batch execution of ANSYS. On UNIX/Linux, the preferred method to indicate an output file is >. Defines which ANSYS product will run during the session (ANSYS Multiphysics, ANSYS Structural, Command Line. -s read or noread -ser -v Specifies whether the program reads the start130.ans file at start-up. If you omit the -s option, ANSYS reads the start130.ans file in interactive mode and not in batch mode. Specifies the communication port number between ANSYS and CFX in an MFX analysis. Returns the ANSYS release number, update number, copyright date, customer number, and license manager version number. productname etc.). For more detailed information about the -p option, see Choosing an ANSYS Product via
3.2. The Mechanical APDL Product Launcher
3.2.1. Starting an ANSYS Session from the Start Menu/Launcher
Use the Mechanical APDL Product Launcher when you want to run an ANSYS program, one of the auxiliary programs, or to access a modifiable ANSYS file. You can access some launcher functionality directly from the Windows Start Menu. To access ANSYS functionality, including the launcher, on Windows systems, choose Start> Programs> ANSYS 13.0 and select the appropriate option.
To activate the launcher on UNIX/Linux systems, enter the following command: launcher130
You can also place one of the following commands in your .login or .profile file: .login file command:
launcher130 >& /dev/null & .profile file command:
launcher130 > /dev/null 2> &1 &
Either command causes the launcher to appear automatically when you log onto the system.
Note:
Mechanical APDL does not support the Product Launcher on HP-UX systems.
Start Menu Options on Windows
To activate the launcher on Windows, choose Start> Programs> ANSYS 13.0> Mechanical APDL Product Launcher
From the ANSYS Start Menu, you can select other options in addition to the launcher:
第 16 页
Operations Guide
? Utilities, such as the ANS_ADMIN, CAD Configuration Manager, and Product Configuration
utilities ? Help
? Applications, such as ANSYS, FLUENT, CFX, etc. ? ANSYS Client Licensing ? Uninstall
You can run ANSYS directly by choosing ANSYS from the Start Menu. If you have not yet run the launcher, selected any products, or defined any profiles, the highest product that your site is licensed for will be run, or the product as specified by your license administrator using the Specify Product Order option of the ANSLIC_ADMIN utility (see the ANSYS, Inc. Licensing Guide). If you have run the launcher, then running the product directly from the Start Menu will start the product with the last launcher configuration.
The Launcher Log File
The launcher creates a log file named launcher.130.log. This file contains a history of launcher selections along with any error messages that may occur. On UNIX/Linux systems, this file is written to your home directory. On Windows, it is written to the directory specified with the TEMP environment variable. If TEMP is not set, the file is written to the root directory of the value specified on the WINDIR environment variable. The log file is always written by default. You can turn off the log file via the Options menu, but we do not recommend doing so.
Launcher Tasks
Use the launcher to select product settings, such as the simulation environment, the specific license, and any add-on modules or analysis type you want to run. Based on your product selections, you can then specify file management, customization/preferences, and solver setup options. Product settings and the options under each tab are explained below. You may not see all options, depending on your product selection.
The launcher tabs are:
? The File Management Tab
? The Customization/Preferences Tab
? The High Performance Computing Setup Tab
You can also access launcher-specific functionality via the menu bar. The File, Profiles, Options, Tools, Links, and Help menus are explained in later sections.
In addition to the tabs and the menu bar options, the launcher also has additional buttons at the bottom.
? Run launches the product you have selected with the settings specified on the various tabs. ? Cancel Run allows you to cancel an ANSYS Batch run. For an ANSYS Batch run, the analysis
must be nonlinear or full transient (linear or nonlinear), or use the PCG, ICCG, or JCG solver (linear or nonlinear solutions). The cancel run request will be ignored for any other types of analyses.
For an ANSYS Batch run, Cancel Run creates a file in the working directory called Jobname.ABT. If you are running multiple jobs, be sure to specify a unique jobname for each
第 17 页
Operations Guide
job.
? Queue allows you to launch a batch run at a later time. When you click the Queue button, you
will be prompted to enter a delayed start time and date. This option is only available on UNIX/Linux systems.
? Product Help launches the help file for the selected simulation environment.
In most places where you can specify path names, you can specify paths using drive letters or UNC paths. However, you may encounter places where UNC paths cannot be used. If you see a message indicating that UNC paths are not available, re-enter the path using drive letters.
3.2.1.1. Product Settings
Here you specify your simulation environment, license, and add-on modules. The simulation environment indicates which interface you want to use to run interactively or allows you to start a batch run. Options include:
? ANSYS
? ANSYS Batch ? LS-DYNA Solver
Depending on which environment you select and what licenses are available at your site, the remaining product selection choices and the options under the remaining tabs will vary.
In the License field, select a license from the available types. Only those licenses that are both available for your site and valid with the simulation environment selected will be shown. All applicable licenses will be shown, regardless of your license preference settings.
The order in which products are listed can be modified using the ANSLIC_ADMIN's Specify Product Order option or the Set License Preferences for User option. See the ANSYS, Inc. Licensing Guide for more information. Once a product has been run via the launcher, the launcher profile will take precedence over changes to the product order made via the ANSLIC_ADMIN utility.
You can then select from available add-on modules or other product-specific options. You will only be able to pick modules/options that are available for the selected product and/or environment. If a choice is not shown, it is not available for the product or environment that you have selected. If a choice is grayed out, then that choice is available for the selected product and environment, but your site does not have the necessary license. To obtain a license for any grayed-out option, please contact your ANSYS sales representative.
Possible Add-on Modules include:
LS-DYNA (-dyn)
Enables LS-DYNA. Applicable only for ANSYS Structural and higher license levels. ANSYS DesignXplorer (-dvt)
Enables the ANSYS DesignXplorer advanced task. The DesignXplorer module is part of the ANSYS Workbench product and is used to compute the requested results for the entire range of all design parameters with one solve. See the DesignXplorer online help for more information.
第 18 页
Operations Guide
Possible Analysis Types available with the LS-DYNA Solver environment include:
? Typical LS-DYNA Analysis
? Implicit-to-Explicit Sequential Solution ? Simple Restart Analysis ? Small Restart Analysis ? Full Restart Analysis
See the ANSYS LS-DYNA User's Guide for more information on these analysis types.
3.2.1.2. The File Management Tab
This tab contains the information necessary to manage your files, such as location of your working directory and job name. The available options will differ depending on the simulation environment you selected.
If you selected the ANSYS simulation environment, you can specify:
Working directory
Sets the directory in which the ANSYS run will be executed. The program writes files it generates to this directory. To change the working directory, type the new directory name in the Working Directory text box or press the Browse button to display a file selection dialog box. On Windows, you must use an absolute path.
You can also specify the working directory by defining the ANSYS130_WORKING_DIRECTORY environment variable. If ANSYS130_WORKING_DIRECTORY is set, the launcher will use that setting as the default. However, any working directory that is specified via the launcher (such as a profile) overrides the ANSYS130_WORKING_DIRECTORY environment variable setting.
If you run ANSYS as an administrator using a particular working directory, and then run as a non-administrator using the same directory, you may encounter permission problems with the .log file. Users with administrator privileges should not use the same working directory as non-administrator users. Jobname
Defines the base filename used for all files generated by the ANSYS run. The initial jobname defaults to file. You can change it to any alphanumeric string up to 32 characters long.
If you selected the ANSYS Batch simulation environment, you can specify the above items as well as the following:
Input file
Specifies the file of ANSYS commands you are submitting for batch execution. You can either type in the desired filename or click the Browse button to display a file selection dialog box or click on Edit to view the file in an editor. If you specify a relative path, it will be relative from the working directory as specified in the launcher. Output file
Specifies the file to which ANSYS directs text output by the program. If you specify a relative path, it will be relative from the working directory as specified in the launcher. If the filename already exists in the working directory, it will be renamed to jobname.out.
第 19 页
Operations Guide
rather than rename it by unchecking the Save Existing Output Files From Batch Runs item under the Options menu on the launcher.
The Working directory and Jobname options include Update I/O path and Update I/O name toggles, respectively. If these toggles are checked, the directory path that appears in the Input file name and the name that appears in the Output file name text boxes will be updated automatically to match the specified Working directory and Jobname. Include input listing in output
Includes or excludes the input file listing at the beginning of the output file.
On UNIX/Linux systems, if you wish to start your batch job at a later date, click the Queue button. You will be prompted to enter a start date and time. To use this option, you must have permission to run the at command on UNIX/Linux systems, meaning your user name must appear in the at.allow file. If that file does not exist, the at.deny file is checked to see if access should be denied. If neither file exists, only users with root access may use this feature. If at.deny is empty, global usage is permitted.
These files consist of one user name per line and can be modified only by the superuser. The location of the at.allow and at.deny files on each hardware platform is listed below:
? Sun: /usr/lib/cron ? IBM: /var/adm/cron ? Linux: /etc
If you selected the LS-DYNA Solver simulation environment, you can specify the working directory as described above, and the following:
Keyword Input File
Specify the name of the file.k that ANSYS writes. On Windows systems, the file must reside in the working directory. Restart Dump File
Specify the name of the small restart input file. On Windows systems, the file must reside in the working directory. For more information, see the EDSTART command.
3.2.1.3. The Customization/Preferences Tab
The settings under this tab allow you to specify detailed settings about your working environment, such as memory settings, parallel/distributed processing settings, custom executables, and additional parameters. The available options will differ depending on the simulation environment you selected on the first tab.
If you selected the ANSYS or ANSYS Batch simulation environment, you can specify:
Use Custom Memory Settings
Specifies the use of custom memory settings rather than using the default memory model. You must select custom memory settings in order to set the -m or -db options. See Memory Management and Configuration in the Basic Analysis Guide for information about memory management. Total Workspace (MB)
Specifies the initial allocation of memory requested for the ANSYS run. It defaults to 1 GB (1024 MB) for 64-bit machines or 512 MB for 32-bit machines. These values are sufficient for most modest-sized
第 20 页
Operations Guide
Numbers and symbols drawn in immediate mode (such as keypoint numbers and boundary condition symbols) have a similar drawback: they will disappear when you request a plot unless they are explicitly set to \ PlotCtrls menu. You can turn off immediate mode using the Immediate Display function under Utility Menu> PlotCtrls> Erase Options.
If you \request a plot (using the Plot menu or a plot command), the ANSYS program calculates the graphics scaling such that the display fills the window. This is more of a \display in that it stays in place even if it is obscured by a dialog box or a menu or if the Graphics Window is iconified and then restored. See the Basic Analysis Guide for details about ANSYS graphics.
4.3.6.2. XOR Mode
The ANSYS program uses this mode when something needs to be drawn or erased quickly without destroying whatever is currently being displayed in the Graphics Window. For example, XOR mode takes effect during graphical picking to highlight or unhighlight the item being picked. It is also used to display the working plane and for rubber-banding.
The advantage of using XOR mode is that it produces an instantaneous display without affecting the existing plot on the screen. The only drawback is that drawing in the same location a second time erases the display. For example, picking the same node or keypoint a second time erases the highlight. Similarly, with the working plane display on, requesting another plot without erasing the screen erases the working plane.
4.3.6.3. Capture Image Feature
A useful feature that allows you to create \function (using the Capture Image button in the Standard Toolbar or Utility Menu> PlotCtrls> Capture Image). After an image is captured (when the \restore it in any ANSYS session. Captured images are useful for comparing different views, sets of results, or other significant images simultaneously on the screen.
4.3.6.4. Right-mouse Button Context-sensitive Menus
You can click the right-mouse button to access many of the functions you use to adjust the Graphics Window display. The available information will vary according to the type of display and the position of your cursor in the window. Along with some of the standard Pan-Zoom-Rotate functions, you can also access many of the window control functions found in the PlotCrtrls section of the Utility Menu. Placing your cursor over the legend areas of the Graphics Window channels the context to access the legend control menus.
4.3.7. The Output Window
The Output Window receives all text output from the program - command responses, notes, warnings, errors, and any other messages. It is usually positioned behind the GUI, but you can raise it to the front when necessary.
Figure 4.19 Output Window
第 46 页
Operations Guide
4.3.7.1. Using the Output Window on UNIX/Linux Systems
If you enter the ANSYS program via the launcher, the launcher creates the Output Window. It is a terminal window (such as xterm) that is also used to execute the ANSYS executable. If you enter the program by typing in the ANSYS execution command, then the window in which you typed the command becomes the Output Window.
Caution: Using your window manager to close the Output Window terminates the ANSYS session.
4.3.7.2. Sizing and Positioning the Output Window on Windows Systems
If you are running ANSYS on a Windows system, you can save the size and position of the Output Window:
1. Move the window to the desired location. 2. Size the window to the desired dimensions.
第 47 页
Operations Guide
3. Select Utility Menu> MenuCtrls> Save Menu Layout.
4.3.8. Creating, Modifying and Positioning Toolbars
When you begin your ANSYS session, the start up routine reads a number of text files and scripts that set parameters and conditions for your ANSYS session. Many of these files can be modified to provide a more customized level of operation. The start130.ans file is one such file. You call up toolbars, set their position and define their content in a similar fashion.
You list the toolbars in the tlbrlst130.ans file. This file contains a list of the toolbars you want to activate at start up. The toolbar filenames are designated as *.TLB files, and each file in the list contains the specifications for the content, appearance and position of the toolbars in the ANSYS GUI. You can add additional toolbars to the GUI, (including a Pan-Zoom-Rotate functionality button bar (ANSYSGRAPHICAL.TLB) that is included with the program), by creating the corresponding *.TLB files and including them in the tlbrlst130.ans file. The default tlbrlst130.ans file loads the Standard Toolbar (see The Standard Toolbar) by calling the file \\ANSYSSTANDARD.TLB, and the ANSYS Toolbar (see The ANSYS Toolbar) by calling the file \\ANSYSABBR.TLB. These files should be placed in the same directory as your tlbrlst130.ans file, although the files themselves can be placed anywhere as long as the proper path string is designated and remains valid.
4.3.8.1. Creating a Toolbar File
All of the toolbar files listed above are included with ANSYS. Each of these files contains the instructions you need to create a toolbar. You can load the ANSYSGRAPHICAL.TLB toolbar as shipped into your tlbrlst130.ans file, or you can open any of the included *.TLB files to investigate and replicate the construction. The Standard Toolbar (\\ANSYSSTANDARD.TLB) contains most of the program calls and definitions you would need to create your own, customized toolbar, and is listed below:
!.============================================================================ !
! Toolbars are structured in a heirarchical fashion starting with the ! name of the file which is used to read in the rest of this file. The
! filename MUST be capitalized and corresponds to the CLASS for resource ! query. The file is loaded by adding it to the tlbrlistNN.ans file. ! !
! The entry point is the classname attribute which indicates the classnames ! used in this file. This allows the definition of more than one toolbar ! area for toolbars in a file. ! REQUIRED
*ANSYSSTANDARD.classname: ANS_STD ANS_MAIN ! !
! The title is displayed when the toolbar is loaded in the output ! and if expcol is 1 will be displayed on the Hide/Show bar. ! REQUIRED
*ANS_STD.title: ANSYS Standard Toolbar !
第 48 页
Operations Guide
!
! The location of the toolbar area can be n, s, e, w as position relative ! to the graphics area. The toolbars are placed as they are read in, ! so change the order in the TLB file or tlbrlistNN.ans file. ! n ! ------------- ! | | ! w | graphics | e ! | | ! ------------- ! s !
! REQUIRED
*ANS_STD.location: n ! !
! If expcol is 1 the toolbar will be displayed in a Hide/Show area so that ! the realestate can be toggled on and off. ! OPTIONAL - default is 0 *ANS_STD.expcol: 0 ! !
! The type of toolbar is either abbr or nonabbr see ANSYSABBR.TLB for ! an abbr type toolbar.
! OPTIONAL - default is nonabbr *ANS_STD.type: nonabbr !
! The imagedir is where the icons images will be loaded from this ! must be in Tcl form (e.g. \! a form usuable by the Tcl \! REQUIRED
*ANS_STD.imagedir: $env(EUIDL_DIR) gui $::euidl::euidlArray(language) images ! !
! The toolbars list allows multiple groupings within a single toolbar. ! Each toolbar will have its own frame area. ! REQUIRED
*ANS_STD.toolbars: Standard CmdPrompt UIDLPopWin ResetPicking AnsDynamic !#
!# Standard Toolbar !# !
! The buttonlist indicates the name identifier of each control which will ! belong to this toolbar. ! REQUIRED
*ANS_STD*Standard.buttonlist: new open save sep1 panzomrot sep2 imagecap reportgen help ! !
第 49 页
Operations Guide
! The type is a standard Tcl/Tk widget type. The least difficult is a ! simple button, others can be used but are more complicated. ! OPTIONAL - default is button
*ANS_STD*Standard.new.type: button ! !
! The imagefile is the file to use for the icon. The image formats
! supported are: PNG (transparent), GIF, JPEG, BMP (Windows). The ! file must be placed in the directory specified by imagedir. ! OPTIONAL/REQUIRED - if text is used then not needed *ANS_STD*Standard.new.imagefile: new16x16.gif ! !
! Text may be used instead of an imagefile but the imagefile overrides ! OPTIONAL/REQUIRED - if imagefile is used then not needed *ANS_STD*Standard.new.text: New ! !
! The command specified will be sent to the EUIDL Tcl/Tk interpreter ! which as interfaces to the ANSYS API. Most useful would be ! ans_sendcommand to call an ANSYS command, macro, or UIDL. ! REQUIRED
*ANS_STD*Standard.new.command: catch {::euidl::databaseSetup::newAnalysis} ! !
! The tooltip is a brief description of what this item does and is ! displayed when the mouse pointer is held over the control. ! OPTIONAL - default is no tooltip shows
*ANS_STD*Standard.new.tooltip: New Analysis ! !
! The anscmd item is used provide a hyperlink into the help system. ! OPTIONAL - default is no hyperlinks to ANSYS help system *ANS_STD*Standard.new.anscmd: \\
\VE}} \
\
\! !
! What's This allows you to provide detailed information about this item. ! Use standard C formatting: ! \\\\ - single slash ! \\n - newline ! \\t - tab
! \\b - backspace
! OPTIONAL - default is no \*ANS_STD*Standard.new.whatsthis: \\
\
第 50 页
百度搜索“yundocx”或“云文档网”即可找到本站免费阅读全部范文。收藏本站方便下次阅读，云文档网，提供经典综合文库ANSYS13.0官方入门操作指南(英文打印版)在线全文阅读。
最新更新：
