Space Grant Consortium - University of Wisconsin - Green Bay
Space Grant Consortium - University of Wisconsin - Green Bay
Space Grant Consortium - University of Wisconsin - Green Bay
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
forces is implemented in the popular industry-grade s<strong>of</strong>tware MSC/ADAMS, while the new LCP<br />
contact formulation and fixed-point iterative solver are implemented in the research-grade<br />
S<strong>of</strong>tware Development Kit (SDK) ChronoEngine. Difficulty was encountered while porting the<br />
original model, which was built using MSC/ADAMS, to ChronoEngine using the SDK. Details<br />
about the differences <strong>of</strong> the multibody models in each dynamics engine will be presented.<br />
Original Computational Model. The original model is a tracked subsystem <strong>of</strong> a hydraulic<br />
excavator which consists <strong>of</strong> the following rigid bodies: a center block, five bottom rollers, one<br />
main idler, three top rollers, a drive sprocket and 45 track shoes. Each <strong>of</strong> the five bottom rollers<br />
are modeled identically with a revolute joint that is at a fixed location from the center block,<br />
allowing the roller to spin around its own center axis with one Degree <strong>of</strong> Freedom (DOF).<br />
Friction is present in these joints. There are also contact forces between each roller and all the<br />
individual shoe elements. The three support rollers are modeled in a similar fashion as the<br />
bottom rollers.<br />
The drive sprocket is composed <strong>of</strong> three parts: two identical gears and a drive wheel. Both gears<br />
are rigidly attached to the drive wheel, and each gear has contact forces specified with all 45<br />
track shoes. The drive sprocket revolves around its central axis by a revolute joint which is a<br />
fixed distance from the center block. It is also where the driving torques and motions are applied.<br />
The front idler is modeled almost identically as the bottom rollers; it is constrained with a<br />
revolute joint and has contact forces specified with the track shoes. There is one main difference<br />
which is due to the presence <strong>of</strong> a simplified tensioning system. The revolute joint is not a fixed<br />
distance from the center block; it is constrained with a translational joint that represents the track<br />
tensioner system. This allows the idler to have an extra DOF so it can move forwards and<br />
backwards with respect to the center block. A single component horizontal force applied to the<br />
center <strong>of</strong> the idler keeps the shoes in tension.<br />
Each track shoe is connected to its neighboring shoes with revolute joints that rotate along the<br />
axis <strong>of</strong> the connecting pins. Contact forces are specified between each track shoe and all the<br />
running gear components, i.e. the rollers, idler and drive sprocket. There are also contact forces<br />
between the track shoes and the ground block, which is simply a large rectangle. Finally, the<br />
entire model is constrained to a single plane by applying a primitive joint to the center block<br />
which removes the ‘roll’ DOF <strong>of</strong> the vehicle. The assembled model as seen in MSC/ADAMS is<br />
shown in Figure 1.<br />
This type <strong>of</strong> tracked vehicle was originally selected because it has a simple suspension and low<br />
operating speeds (~2 km/h) which make its behavior easy to predict. There are also a total <strong>of</strong> 585<br />
rigid body contact forces specified in the model, which is the computational bottleneck. The<br />
original model was tested under multiple conditions using the ground block, the type <strong>of</strong><br />
propulsion method and the rate <strong>of</strong> the propulsion method as independent variables. However for<br />
this comparison, a straight-line quasi-steady state dynamic simulation was used for simplicity.<br />
The next step was to create a model in ChronoEngine that is as similar to the original as possible.<br />
19