You can perform a load-transfer coupled-field analysis with multiple physics by issuing LDREAD to read the results from one analysis and apply them as loads in the other. The geometric model, mesh, element and node numbers must be consistent between the different physics analyses that compose the coupled-field analysis.
Figure 3.1: Data Flow for a Load Transfer Coupled-Field Analysis With One-Way Coupling shows the data flow for a typical load-transfer analysis with one-way coupling. The appropriate solid model, elements, loads, etc. are set up for each analysis. Information is read in from the results file of the first analysis and applied as loads to the subsequent analysis. One-way coupling is appropriate when the results of the first physics analysis significantly affects the second, but the results of the second physics analysis have negligible effects on the first, such as a typical thermal-stress analysis. (See Example Thermal-Stress Analysis.)
Problems like induction heating require two-way coupling because the results of the different physics analyses involved significantly affect each other. These problems require an iterative solution, and their data flow per iteration is illustrated in Figure 3.2: Data Flow for a Load Transfer Coupled-Field Analysis With Two-Way Coupling. (See Example Induction Heating Analysis.)
The database file may grow during multiple solution passes. In that case, take one of the following actions:
Issue SAVE after creating the physics environments and RESUME after each physics solution.
Do not write results into the database (that is, write to the results file only); then, issue SET when you want to read data from the results file into the database for postprocessing. To activate this option, either issue /CONFIG,NOELAB,1 or insert
NO_ELDBW = 1into the config.ans file.