3.2.40 Translating an Abaqus substructure to an EXCITE flexible body

Product: Abaqus/Standard  

Overview

The abaqus toexcite translator converts an Abaqus substructure to a flexible body in a format that can be used by the EXCITE multibody dynamics code.

The translator reads Abaqus data from a substructure SIM file and writes data to an EXCITE flexible body interface (.exb) file.

Using the translator

The following procedure summarizes the typical usage of the abaqus toexcite translator:

  1. Create an Abaqus substructure. (General guidelines for building Abaqus models with substructures are described in Using substructures, Section 10.1.1.)

    The substructure generation step must write at least mass and stiffness matrices, and it must include the *FLEXIBLE BODY option as follows:

    *SUBSTRUCTURE GENERATE, MASS MATRIX=YES
    *FLEXIBLE BODY, TYPE=EXCITE or GENERIC
    • If TYPE=EXCITE, an EXCITE flexible body of type SMOT, including high-order inertia invariants, is created.

    • If TYPE=GENERIC, an EXCITE flexible body of type CON6 is created.

  2. Run the Abaqus analysis.

  3. Run the abaqus toexcite translator to read the substructure SIM database produced by the analysis and to create the flexible body interface file.

Command summary

abaqus toexcite
job=job-name
 
[substructure_sim=filename]

Command line options

job

This option specifies the input and output file names to use during results translation. The job-name value is used to construct the default substructure SIM database file name, job-name.sim. The output flexible body interface file is given the name job-name.exb.

If this option is omitted from the command line, you will be prompted for this value.

substructure_sim

This option specifies the name of the substructure SIM database (.sim) file if it is different from job-name.sim. The file will usually be named job-name_Znn.sim.

Your query was poorly formed. Please make corrections.


3.2.40 Translating an Abaqus substructure to an EXCITE flexible body

Product: Abaqus/Standard  

Your query was poorly formed. Please make corrections.

Overview

The abaqus toexcite translator converts an Abaqus substructure to a flexible body in a format that can be used by the EXCITE multibody dynamics code.

The translator reads Abaqus data from a substructure SIM file and writes data to an EXCITE flexible body interface (.exb) file.

Your query was poorly formed. Please make corrections.
Your query was poorly formed. Please make corrections.

Using the translator

The following procedure summarizes the typical usage of the abaqus toexcite translator:

  1. Create an Abaqus substructure. (General guidelines for building Abaqus models with substructures are described in Using substructures, Section 10.1.1.)

    The substructure generation step must write at least mass and stiffness matrices, and it must include the *FLEXIBLE BODY option as follows:

    *SUBSTRUCTURE GENERATE, MASS MATRIX=YES
    *FLEXIBLE BODY, TYPE=EXCITE or GENERIC
    • If TYPE=EXCITE, an EXCITE flexible body of type SMOT, including high-order inertia invariants, is created.

    • If TYPE=GENERIC, an EXCITE flexible body of type CON6 is created.

  2. Run the Abaqus analysis.

  3. Run the abaqus toexcite translator to read the substructure SIM database produced by the analysis and to create the flexible body interface file.

Your query was poorly formed. Please make corrections.
Your query was poorly formed. Please make corrections.

Command summary

abaqus toexcite
job=job-name
 
[substructure_sim=filename]

Your query was poorly formed. Please make corrections.
Your query was poorly formed. Please make corrections.

Command line options

job

This option specifies the input and output file names to use during results translation. The job-name value is used to construct the default substructure SIM database file name, job-name.sim. The output flexible body interface file is given the name job-name.exb.

If this option is omitted from the command line, you will be prompted for this value.

substructure_sim

This option specifies the name of the substructure SIM database (.sim) file if it is different from job-name.sim. The file will usually be named job-name_Znn.sim.

Your query was poorly formed. Please make corrections.
Your query was poorly formed. Please make corrections.