You are on page 1of 1

If you apply a torsional load via remote points, dont expect your reactions to

always balance if you run this as small deflection. Remote loads and
displacements in Workbench Mechanical are implemented using constraint
equations. With small deflection analysis, we do one pass thru the linear
code. These constraint equations are only created once. If the resulting
rotation is large enough, the CEs might become invalid thru the large
rotation. In the end, things will not add up. We do issue a warning in the
solver output. If in doubt, always turn large deflection ON before checking
anything else.

If you try to apply a torsional displacement to a flimsy open cross section of a


structural beam element, dont expect your moment reaction to match that
of an equivalent model represented with shells or solids. The numbers might
be way off. The reason is that, by default, the calculations are based on
classical Timoshenko beam theory. We do not include any adjustment for
cross sectional warping of the element. To get the beam moment reaction to
match that of an equivalent solid or shell model, there is an option to include
a warping DOF via KEYOPT(1)=1 (for BEAM188/9). You have to know this. The
option is documented in the elements manual, but we are not going to give
you any warnings or notes about it in the solver output.
Also, when running a truly large deflection nonlinear contact problem, if the
model converges, but the reactions do not add up, consider the NewtonRaphson convergence criteria. If the tolerances are too loose, you might be
looking at false convergence. The default tolerances are generally designed
to be conservative, but sometimes, depending on the application, they might
need to be tightened up or you might need to reconsider how you are
applying your loads and/or constraints.
Finally, if you ever do try to push on a rope and you end up face planting to
the ground, dont expect to model this scenario in a static structural run. It
will not converge.

You might also like