6.13.1.3.7. Imported Cross Sections

When your upstream External Model source file includes Line Body cross section data, cross section objects are automatically created/inserted under the Cross Sections folder. These imported cross sections act as any other user-defined cross section.

Highlighted below is an example of an imported Line Body. It automatically includes a property reference to the accompanying imported cross section (CrossSection1).

Here is CrossSection1 highlighted. The mesh display is turned on for this image.

Supported Source File Commands

The application imports the following source file data/commands as line body/beam cross sections:

  • CDB: The SECTION/REAL attribute defined with the element in the EBLOCK section.

    • BEAM, LINK and PIPE Types are supported.

    • The MESH Subtype is not supported.

  • NASTRAN: Property ID designated with the PBAR, PBARL, PBEAM, PBEAML, PROD and CONROD bulk data entry.

    • CHAN2, H, CROSS, T1, HEXA, and HAT1 section types are not supported in Mechanical. The equivalent ASEC properties are calculated and used for these sections.

  • ABAQUS: On the each “*BEAM SECTION”, “*BEAM GENERAL SECTION” and “FRAME SECTION” keyword:

    • ARBITRARY, HEX, TRAPEZOID, and ELBOW Sections are not supported and are not used.

    • Tapered beams are not supported in Mechanical. If a tapered beam is specified in the CDB or ABAQUS file the section data from the first node is used.

Also see the Cross Section Objects section for more information.