ansys.mapdl.core.Mapdl.cdread#

Mapdl.cdread(option='', fname='', ext='', fnamei='', exti='', **kwargs)#

Reads a file of solid model and database information into the database.

Mechanical APDL Command: CDREAD

Parameters:
optionstr

Selects which data to read:

  • ALL - Read all geometry, material property, load, and component data (default). Solid model geometry and loads will be read from the file fnamei.exti. All other data will be read from the file fname.ext. None

  • DB - Read all database information contained in file Fname.Ext. This file should contain all information mentioned above except the solid model loads. If reading a .CDB file written with the GEOM option of the cdwrite command, element types ( et ) compatible with the connectivity of the elements on the file must be defined prior to reading.

  • SOLID - Read the solid model geometry and solid model loads from the file Fnamei.Exti. This file could have been written by the cdwrite or igesout command.

  • COMB - Read the combined solid model and database information from the file Fname.Ext. None

fnamestr

File name and directory path (248 characters maximum, including the characters needed for the directory path). An unspecified directory path defaults to the working directory; in this case, you can use all 248 characters for the file name. The file name defaults to Jobname.

extstr

Filename extension (eight-character maximum). The extension defaults to .cdb if Fname is blank.

fnameistr

Name of the IGES file and its directory path (248 characters maximum, including directory). If you do not specify a directory path, it will default to your working directory and you can use all 248 characters for the file name.

The file name defaults to Fname. Used only if Option = ALL or SOLID.

extistr

Filename extension (eight-character maximum). Defaults to IGES if Fnamei is blank.

Notes

This command causes coded files of solid model (in IGES format) and database (in command format) information to be read. These files are normally written by the cdwrite or igesout command. Note that the active coordinate system in these files has been reset to Cartesian ( csys,0).

If a set of data exists prior to the cdread operation, that data set is offset upward to allow the new data to fit without overlap. The nooffset command allows this offset to be ignored on a set-by-set basis, causing the existing data set to be overwritten with the new data set.

When you write the geometry data using the cdwrite,GEOM option, you use the cdread,DB option to read the geometry information.

Using the cdread,COMB option will not write numoff commands to offset entity ID numbers if there is no solid model in the database.

Multiple .cdb file imports cannot have elements with real constants in one file and section definitions in another. The section attributes will override the real constant attributes. If you use cdread to import multiple CDB files, define all of the elements using only real constants, or using only section definitions. Combining real constants and section definitions is not recommended.

If a radiosity mapping data file ( .rsm file) was saved by the previous cdwrite command, that mapping file must be present in the directory along with the coded geometry file in order for radiosity surface elements ( SURF251, SURF252 ) to be correctly mapped onto the model when cdread is issued.

If you issue cdwrite to import a .cdb file containing a user-defined element, manually insert usrelem and usrdof commands in the .cdb file to provide the user-defined element characteristics. Insert the two commands after the et command (defining the user-defined element) and before the EBLOCK command. (If multiple element types are defined in the .cdb file, insert the The type statement command to select the user-defined element. Place it before usrelem and usrdof.)

This command is valid in any processor.