3.3.5. Boundary Conditions

Even though both solvers model structural problems, the boundary conditions have a number of differences. Unlike the Explicit dynamic structural solver, the Implicit static structural solver has no real dependency on inertia. That is why the load cases in Implicit are usually 1 second per step, which is an arbitrary amount. Altering this value does not really have any effect on the solution. The Explicit Dynamics solver, on the other hand, uses time as its main reference for the calculations since the duration of the events in an Explicit problem are extremely short, and it is one of the most important aspects of the solve. When the two systems are connected and use the same Mechanical instance, boundary conditions can be copied by dragging and dropping from the Implicit to the Explicit system. This is the initial step in transferring the boundary conditions, but before the Explicit solve, adjustments to the boundary condition definitions must be made.

3.3.5.1. Adjusting Load Cases for Reasonable Run Times

Unlike the Explicit solver, the Implicit solver has no real dependency on inertia (in the static structural solver). That is why the load cases in Implicit are usually 1 second per step, which is an arbitrary amount. Altering this value does not really have any effect on the solution. The Explicit Dynamics solver, on the other hand, uses time as its main reference for the calculations since the duration of the events in an Explicit problem are extremely short, and it is one of the most important aspects of the solve (see Timestep Controls).

As a starting point, a time scale factor of 100 or 1000 should be used; that is, 1 second in the implicit solver becomes 1E-2 or 1E-3 seconds in the explicit solver. The main thing to monitor are the velocities in the model. A good velocity to aim for is 5 m/s; it is not too low going into the static setup realm and it is not too high which would introduce significant inertial effects.

3.3.5.2. Missing Boundary Conditions from Explicit Dynamics

There are a few Mechanical boundary conditions that do not exist in Explicit Dynamics. Some of them can be simulated by using other boundary conditions. These include cylindrical support, frictionless support, bolt pretension and others. Refer to the table below for ways to simulate some of the missing boundary conditions.

Boundary condition Implicit solver Explicit solver
Frictionless supportAvailable

Available/

Simulated by using an equivalent symmetry plane (rigid behavior) or by creating displacement with fixed components to provide the desired constraint.

Bolt pretensionAvailableSimulated using a fixed support and displacement (previously evaluated required deformation) to achieve the stress values in the bolt.
Cylindrical supportAvailableSimulated using remote displacement to restrict rotation.
Displacement (step applied)AvailableSimulated using different boundary conditions to give the same movement - force, velocity etc.
Pressure (tabular variable value)AvailableSimulated using the Magnitude - Function setting to create a function giving the same values across the scoped geometry.

3.3.5.3. Application of Boundary Conditions Using Steps

Boundary conditions in the Implicit solver can be applied through simulation steps. A step can also be used to suppress a boundary condition. This means a displacement can be applied up to a certain point, after which the scoped geometry is released and it can deform freely. This behavior is not straightforward to model using the Explicit solver. If the displacement value is set to 0 this just means that the geometry will return to its original position. To achieve the same results in an explicit solve, a different boundary condition has to be applied to model the step-applied displacement. For example, in the explicit solver: use force to deform a body and then set the force to 0 at a point in the simulation in order to simulate a step-applied displacement in the implicit solver. This difference in approach stems from the time dependant nature of the explicit solver, which means boundary conditions like velocity or force can be modeled exactly like their step applied counterparts in the implicit solver but the displacement cannot.

3.3.5.4. Avoiding Conflicting Boundary Conditions

When the scoping of two boundary conditions is done on two intersecting planes, the shared edge can trigger an error: Could not transfer loads and constraints to the solver and/or The combination of supports is causing some nodes to be over-constrained. The Explicit solver will only allow more than one boundary condition to be applied to the same node if they are not conflicting (for example, two different forces scoped to adjacent faces). The shared edge will experience the vector sum of the forces. A common example of conflicting boundary conditions would be a fixed support applied to one plane and displacement on an intersecting plane.

3.3.5.5. Initial Conditions

The Initial Conditions object in the Explicit Dynamics system can be helpful when certain aspects of the Implicit model cannot be directly recreated. It is a simple initial velocity, angular or directional, that is scoped to a body and is assigned at the initial cycle. This can be altered freely by different boundary conditions and events during the solve; its value is not constrained or limited. Another use for Initial Conditions is adding a pre-stress, usually from an Implicit solve. This is useful when an extensive complex combined simulation is required, and is not intended for situations where you need to run the same model setup with the two different solvers.

Figure 3.12:  exd_ag_init_conditions.png

exd_ag_init_conditions.png


Release 18.2 - © ANSYS, Inc. All rights reserved.