4569846498
Multibody systems simulation software 109 the I marker from the J marker resolved parallel to the axes of the I marker or DZ(I, J, I). Note that the third marker in brackets has been added to the system variable DZ to indicate that the component of displacement is resolved using this frame rather than by default the ground reference frame. A first attempt at modelling this force could be achieved with the following SFORCE statement. In this example 0206 is the I marker, 0307 is the J marker, the length of the bump stop is 50 mm and a linear stiffness for the bump stop of 300 N/mm is used. SFORCE/0607,I0206,J0307,TRANS, FUNCTIONIF(DZ(0206,0307,0206)-50:300*(50-DZ (0206,0307,0206)),0,0) This example has introduced an arithmetic IF that allows us to conditionally program the value of the FUNCTION and hence the force returned by this statement. The format used here is IF (expression 1: expression 2, expression 3, expression 4) Expression 1 is evaluated and the value obtained is used to determine which expression is used to evaluate the FUNCTION as follows: IF expression 1 0 then the FUNCTION expression 2 IF expression 1 0 then the FUNCTION expression 3 IF expression 1 0 then the FUNCTION expression 4 In this case expression 1 is DZ(0206,0307,0206)-50. Clearly when this is greater than zero the gap is open and so the calculated force from expression 4 is zero. When expression 1 is equal to zero the I marker is just making contact with the face of the bump stop but no deformation has taken place and so the force is still zero. When expression 1 is less than zero then the contact force is generated using 300*(50-DZ(0206,0307,0206)). Note that this has been programmed to ensure that a positive value is generated for the bump stop as it compresses. Although the method introduced here might work it is possible that it will cause problems during the numerical integration of the solution. This is because the arithmetic IF causes the force to switch on and off instantaneously about the point of contact. Such modelling is usually undesirable and some method is needed to improve the formulation by ‘smoothing’ the transition as contact occurs. This could be achieved by introducing another feature known as a STEP FUNCTION as follows: SFORCE/0607,I0206,J0307,TRANS, FUNCTIONSTEP(VARVAL(1),0,0,0.5,1)*(300*(50-DZ (0206,0307,0206))) VARIABLE/1,FUNCTION50-DZ(0206,0307,0206) Although referred to here as a step users of similar multibody systems software packages may also think of it as a ramp since the change in value returned by the function is not an instantaneous step change. The STEP function used here uses a cubic polynomial to smooth the transition from one state to another as shown in Figure 3.32. This example also introduces the use of VARIABLES that can be used to program equations and substitute the returned value, VARVAL(id), into
110 Mutibody Systems Approach to Vehicle Dynamics FUNCTION STEP (x, x 1 , y 1 , x 2 , y 2 ) y 1 (x 2 , y 2 ) 0 (x 1 , y 1 ) 0 0.5 x VARVAL (1) Fig. 3.32 Step function for a bump stop force J I X Y Z Fig. 3.33 Modelling of suspension bushes another FUNCTION. In this case VARIABLE/1,FUNCTION 50-DZ (0206,0307,0206) is used to program the deformation of the bump stop. The value of this, VARVAL(1) is used to define the variable on the x-axis that is used to step from one state to another. In this the step function is used to smooth the formulation of the contact force between 0 and 0.5 mm of bump stop deformation. Additional functions exist, such as an IMPACT function which might be used to switch on a contact force or to extend the material model from the initial linear one used here to a non-linear model. Another consideration here is that the force formulation takes no account of the possibility that the solution could find a point where the I marker actually moves through the bump stop and past the J marker into the vehicle body. Although this makes no sense physically there is nothing in the formulation to take account of this and should it happen the force would actually reverse direction leading to a probable failure of the solution. Clever programming can take this into account. In addition to improving the material model this could include, for
- Page 82 and 83: Kinematics and dynamics of rigid bo
- Page 84 and 85: Kinematics and dynamics of rigid bo
- Page 86 and 87: Kinematics and dynamics of rigid bo
- Page 88 and 89: Kinematics and dynamics of rigid bo
- Page 90 and 91: Kinematics and dynamics of rigid bo
- Page 92 and 93: Kinematics and dynamics of rigid bo
- Page 94 and 95: Kinematics and dynamics of rigid bo
- Page 96 and 97: Kinematics and dynamics of rigid bo
- Page 98 and 99: 3 Multibody systems simulation soft
- Page 100 and 101: Multibody systems simulation softwa
- Page 102 and 103: Multibody systems simulation softwa
- Page 104 and 105: Multibody systems simulation softwa
- Page 106 and 107: Multibody systems simulation softwa
- Page 108 and 109: Multibody systems simulation softwa
- Page 110 and 111: Multibody systems simulation softwa
- Page 112 and 113: Multibody systems simulation softwa
- Page 114 and 115: Multibody systems simulation softwa
- Page 116 and 117: Multibody systems simulation softwa
- Page 118 and 119: Multibody systems simulation softwa
- Page 120 and 121: Multibody systems simulation softwa
- Page 122 and 123: Multibody systems simulation softwa
- Page 124 and 125: Multibody systems simulation softwa
- Page 126 and 127: Multibody systems simulation softwa
- Page 128 and 129: Multibody systems simulation softwa
- Page 130 and 131: Multibody systems simulation softwa
- Page 134 and 135: Multibody systems simulation softwa
- Page 136 and 137: Multibody systems simulation softwa
- Page 138 and 139: Multibody systems simulation softwa
- Page 140 and 141: Multibody systems simulation softwa
- Page 142 and 143: Multibody systems simulation softwa
- Page 144 and 145: Multibody systems simulation softwa
- Page 146 and 147: Multibody systems simulation softwa
- Page 148 and 149: Multibody systems simulation softwa
- Page 150 and 151: Multibody systems simulation softwa
- Page 152 and 153: Multibody systems simulation softwa
- Page 154 and 155: 4 Modelling and analysis of suspens
- Page 156 and 157: Modelling and analysis of suspensio
- Page 158 and 159: Modelling and analysis of suspensio
- Page 160 and 161: Modelling and analysis of suspensio
- Page 162 and 163: Modelling and analysis of suspensio
- Page 164 and 165: Modelling and analysis of suspensio
- Page 166 and 167: Modelling and analysis of suspensio
- Page 168 and 169: Modelling and analysis of suspensio
- Page 170 and 171: Modelling and analysis of suspensio
- Page 172 and 173: Modelling and analysis of suspensio
- Page 174 and 175: Modelling and analysis of suspensio
- Page 176 and 177: Modelling and analysis of suspensio
- Page 178 and 179: Modelling and analysis of suspensio
- Page 180 and 181: Modelling and analysis of suspensio
Multibody systems simulation software 109<br />
the I marker from the J marker resolved parallel to the axes of the I marker<br />
or DZ(I, J, I). Note that the third marker in brackets has been added to the<br />
system variable DZ to indicate that the component of displacement is<br />
resolved using this frame rather than by default the ground reference frame.<br />
A first attempt at modelling this force could be achieved with the following<br />
SFORCE statement. In this example 0206 is the I marker, 0307 is the J<br />
marker, the length of the bump stop is 50 mm and a linear stiffness for the<br />
bump stop of 300 N/mm is used.<br />
SFORCE/0607,I0206,J0307,TRANS,<br />
FUNCTIONIF(DZ(0206,0307,0206)-50:300*(50-DZ<br />
(0206,0307,0206)),0,0)<br />
This example has introduced an arithmetic IF that allows us to conditionally<br />
program the value of the FUNCTION and hence the force returned by<br />
this statement. The format used here is<br />
IF (expression 1: expression 2, expression 3, expression 4)<br />
Expression 1 is evaluated and the value obtained is used to determine which<br />
expression is used to evaluate the FUNCTION as follows:<br />
IF expression 1 0 then the FUNCTION expression 2<br />
IF expression 1 0 then the FUNCTION expression 3<br />
IF expression 1 0 then the FUNCTION expression 4<br />
In this case expression 1 is DZ(0206,0307,0206)-50. Clearly when this is<br />
greater than zero the gap is open and so the calculated force from expression<br />
4 is zero. When expression 1 is equal to zero the I marker is just making<br />
contact with the face of the bump stop but no deformation has taken place<br />
and so the force is still zero. When expression 1 is less than zero then the<br />
contact force is generated using 300*(50-DZ(0206,0307,0206)). Note that<br />
this has been programmed to ensure that a positive value is generated for<br />
the bump stop as it compresses.<br />
Although the method introduced here might work it is possible that it will<br />
cause problems during the numerical integration of the solution. This is<br />
because the arithmetic IF causes the force to switch on and off instantaneously<br />
about the point of contact. Such modelling is usually undesirable<br />
and some method is needed to improve the formulation by ‘smoothing’ the<br />
transition as contact occurs. This could be achieved by introducing another<br />
feature known as a STEP FUNCTION as follows:<br />
SFORCE/0607,I0206,J0307,TRANS,<br />
FUNCTIONSTEP(VARVAL(1),0,0,0.5,1)*(300*(50-DZ<br />
(0206,0307,0206)))<br />
VARIABLE/1,FUNCTION50-DZ(0206,0307,0206)<br />
Although referred to here as a step users of similar multibody systems software<br />
packages may also think of it as a ramp since the change in value<br />
returned by the function is not an instantaneous step change. The STEP<br />
function used here uses a cubic polynomial to smooth the transition from<br />
one state to another as shown in Figure 3.32.<br />
This example also introduces the use of VARIABLES that can be used<br />
to program equations and substitute the returned value, VARVAL(id), into