DEACTIVATE
The DEACTIVATE command turns off a statement that was previously turned on by the ACTIVATE command, or that was active by default.
Format
Arguments
BEAM | Indicates that Adams Solver (C++) is to deactivate BEAM statements. |
BUSHING | Indicates that Adams Solver (C++) is to deactivate BUSHING statements. |
CLEARANCE | Indicates that Adams Solver (C++) is to deactivate CLEARANCE statements. |
CONTACT | Indicates that Adams Solver (C++) is to deactivate CONTACT statements. |
COUPLER | Specifies that Adams Solver (C++) is to deactivate COUPLER statements. |
DIFF | Specifies that Adams Solver (C++) is to deactivate DIFF statements. |
FE_LOAD | Specifies that Adams Solver (C++) is to deactivate FE_LOAD statements. |
FIELD | Indicates that Adams Solver (C++) is to deactivate FIELD statements. |
GCON | Indicates that Adams Solver (C++) is to deactivate GCON statements. |
GFORCE | Indicates that Adams Solver (C++) is to deactivate GFORCE statements. |
ID=id1[,...,id30] | Lists up to 30 statement identifiers for statements that Adams Solver (C++) is to deactivate. You may use the ID argument in conjunction with the RANGE argument. |
JOINT | Indicates that Adams Solver (C++) is to deactivate JOINT statements. |
JPRIM | Indicates that Adams Solver (C++) is to deactivate JPRIM statements. |
LIST | Indicates that Adams Solver (C++) is to display a list of all the existing elements of the specified type, along with their current activity status. |
MFORCE | Indicates that Adams Solver (C++) is to deactivate MFORCE statements. |
MOTION | Indicates that Adams Solver (C++) is to deactivate MOTION statements. |
RANGE=id1, id2 | Indicates a range of statement identifiers for statements that Adams Solver (C++) is to deactivate. Adams Solver (C++) deactivates all statements with identifiers that are numerically between the given identifiers, inclusively. The range may contain unused identifiers. You may use the RANGE argument in conjunction with the ID argument. Range: id1 < id2 |
SENSOR | Indicates that Adams Solver (C++) is to deactivate SENSOR statements. |
SFORCE | Indicates that Adams Solver is to deactivate SFORCE statements. |
SPRINGDAMPER | Indicates that Adams Solver (C++) is to deactivate SPRINGDAMPER statements. |
VFORCE | Indicates that Adams Solver (C++) is to deactivate VFORCE statements. |
VTORQUE | Indicates that Adams Solver (C++) is to deactivate VTORQUE statements. |
Extended Definition
The DEACTIVATE command, used in conjunction with the ACTIVATE command, switches Adams Solver (C++) elements off and on. All Adams Solver (C++) elements are active by default in the input dataset, but some may be deactivated using the DEACTIVATE command. For simulation purposes, when Adams Solver (C++) deactivates a statement, the statement effectively disappears from the model. When a statement is activated, the statement appears as though it were always in the dataset. Both the DEACTIVATE and ACTIVATE commands take effect when you issue the next SIMULATE command. Once deactivated, a statement remains inactive until it is activated using an ACTIVATE command.
After the deactivation of any element, Adams Solver (C++) reprocesses the model at the next SIMULATE command as if it had just been read in from the dataset. During the reprocessing, Adams Solver (C++) checks the entire model for consistency, reinitializes user subroutines, and recomputes initial conditions.
Adams Solver (C++) reports zero forces for the inactive element if a force request or force graphic refers to an inactive element. Additionally, references to deactivated elements in function expressions evaluate to zero.
Adams Solver (C++) also reinitializes all user subroutines to re-establish functional dependencies. For each element that refers to a user-written subroutine, Adams Solver (C++) calls the user-written subroutine with IFLAG set to true.
Prior to the actual simulation, Adams Solver (C++) computes initial conditions for the model. If this is the first simulation, Adams Solver (C++) begins with the positions and velocities specified in the dataset. If you ran a previous simulation, Adams Solver (C++) begins with the final displacements and velocities. Adams Solver (C++) then adjusts the initial conditions to ensure that they are consistent with the model constraints. If this is the first simulation, Adams Solver (C++) also maintains any user-supplied joint initial-conditions and part positions specified as EXACT.
Adams Solver (C++) reports zero values in all output files for any forces associated with inactive elements, including both applied forces and joint reaction forces. This includes force requests, force graphics, and forces in the Results File.
Tip: | Typically, you use DEACTIVATE and ACTIVATE to set up the model for a particular loadcase or configuration after a FILE or RELOAD command. |
Caution: | Deactivating elements may produce strong discontinuities in the model causing convergence difficulties and reduced integrator performance. It is important that you use these commands carefully to avoid discontinuities. |
Examples
DEACTIVATE/JOINT,ID=71,72,73
This DEACTIVATE command deactivates JOINTs 71, 72, and 73.
DEACTIVATE/SENSOR,RANGE=5,10
This DEACTIVATE command deactivates all SENSORs with identifiers between 5 and 10, including 5 and 10.
You can turn off contact forces in your model during a simulation by using the DEACTIVATE command in the .acf file.
SIMULATE/TRANSIENT, END=1.0, STEPS=100
DEACTIVATE/CONTACT,ID=1,3, LIST
SIMULATE/TRANSIENT, DURATION=1.0, STEPS=100
DEACTIVATE/CONTACT,ID=1,3, LIST
SIMULATE/TRANSIENT, DURATION=1.0, STEPS=100
This simulates four active contact elements for one second, disabling two out of four contacts, then continuing the simulation for another second. The LIST argument is useful for obtaining feedback in the .msg file on the status of active elements. When deactivation has taken place, you will see a similar message:
CONTACT/1, INACTIVE CONTACT/2, ACTIVE CONTACT/3, INACTIVE CONTACT/4, ACTIVE
See other Simulation available.