Search Results

Sudden tire deflation, or blow-out, is sometimes cited as the cause of a crash. Safety researchers have previously attempted to study the loss of vehicle control resulting from a blow-out with some success using computer simulation. However, the simplified models used in these studies did little to expose the true transient nature of the handling problem created by a blown tire. New developments in vehicle simulation technology have made possible the detailed analysis of transient vehicle behavior during and after a blow-out. This paper presents the results of an experimental blow-out study with a comparison to computer simulations. In the experiments, a vehicle was driven under steady state conditions and a blow-out was induced at the right rear tire. Various driver steering and braking inputs were attempted, and the vehicle response was recorded. These events were then simulated using EDVSM. A comparison between experimental and simulated results is presented.

The time/distance relationship for heavy trucks starting from a stopped position is often needed to accurately assess the events leading up to a collision. A series of tests were conducted to document tractor/trailer low speed acceleration performance. The vehicles were instrumented with a DATRON speed sensor and engine RPM was also documented. This paper presents the data from these tests and discusses the acceleration profile of heavy trucks in general.

Scientific visualizations and computer animations are frequently presented to show the results of simulation models or the opinions of a reconstructionist. In these cases it is important to properly document the graphical images being presented. Proper documentation depends somewhat on the methodologies used to produce the images, but every scientific visualization, computer animation, and computer generated image should be documented sufficiently to allow others to duplicate the images. There are also some basic data that should accompany any computer generated images that will reveal the basis of the motion for all primary objects being depicted. This paper presents some basic definitions and outlines the data that is required to document scientific visualizations and computer animations.

Computer models used to study crashes require information to describe the vehicles. Information such as weight, length, wheelbase, tire locations, crush stiffness, tire parameters, etc. all require a reliable source. Usually the tire parameters are difficult to obtain. Analysts will routinely use default or “typical” values. In 1999, Engineering Dynamics Corp. (EDC) attempted to address this issue, with support from many in the field of crash reconstruction, by conducting tire tests. The resulting tire test data will be used to study motor vehicle performance. The computer simulations in use today require information about tire properties or lookup tables that must be extracted from raw collected data. This paper presents a basic overview of the tire test data and a technique for extracting the required tire parameters for use in computer simulation modeling.

Computer animation and its use in the engineering/scientific community are in their infancy. As this visualization tool becomes more widely used and accepted, individual expectations may differ greatly regarding appropriate usage and documentation of an animation. This paper lays the foundation for establishing guidelines for documenting the data and techniques used in producing an animation. The many elements that make up an animation are discussed, along with their importance to the presentation. The ultimate goal, for using the proposed guideline, is to achieve consistency within the engineering / scientific community when evaluating an animation.

A substantial programming effort is required to develop a human or vehicle dynamics simulator. More than half of this effort is spent designing and programming the user interface (the means by which the user supplies program input and views program output). This paper describes a pre-programmed, 3-dimensional (3-D), input/output window-type interface which may be used by developers of human and vehicle dynamics programs. By using this interface, the task of input/output programming is reduced by approximately 50 percent, while simultaneously providing a more robust interface. This paper provides a conceptual overview of the interface, as well as specific details for writing human and vehicle dynamics programs which are compatible with the interface. Structures are provided for the human, vehicle and environment models. Structures are also provided for events, interface variables, and the output data stream.

Developers of human dynamics simulation software inherently use a mathematical/physical model to represent the human. This paper describes a pre-programmed, object-oriented human model for use in human dynamics simulations. This human model is included as part of an integrated simulation environment, called HVE (Human-Vehicle-Environment), described in previous research. The current paper first provides a general overview of the HVE user and development environments, and then provides detailed specifications for the HVE Human Model. These specifications include definitions for model parameters (supported human types and human properties, such as dimensions, inertias, joints and injury tolerances). The paper also provides detailed specifications for the HVE time-dependent human output group parameters (kinematics, joints, contacts, belts and airbags).

Developers of vehicle dynamics simulation software inherently use a mathematical/physical model to represent the vehicle. This paper describes a pre-programmed, object-oriented vehicle model for use in vehicle dynamics simulations. This vehicle model is included as part of an integrated simulation environment, called HVE (Human-Vehicle-Environment), described in previous research [1,2] *. The current paper first provides a general overview of the HVE user and development environments, and then provides detailed specifications for the HVE Vehicle Model. These specifications include definitions for model parameters (supported vehicle types; vehicle properties, such as dimensions, inertias, suspensions; tire properties, such as dimensions and inertias, mu vs slip, cornering and camber stiffnesses; driver control systems, such as engine, transmission/differential, brakes and steering; restraint systems, such as belts and airbags).

The Human Vehicle Environment (HVE) program, developed by Engineering Dynamics Corporation, combines the vehicle parameters, physics and graphics into a single computer system for use in analyzing motor vehicle collisions, handling issues, studying occupant motion, etc. One of the most valuable assets of the HVE program is the open architecture that allows easy access to the data and graphics capabilities from an independent computer program. Thus, virtually any program that can be recompiled on the Silicon Graphics system can be set up to utilize the HVE tools. HVE is written in two computer languages known as C and C++ pronounced (“C plus plus”), this aids in the graphics processing. Unfortunately, FORTRAN programs do not automatically interface with C or C++ programs. These programs must be modified to allow a two-way data path to and from HVE.

There are many collisions in which the “standard” analysis methods are not sufficient to complete an analysis. Many times the points of rest for the vehicles are not documented or the vehicles were “driven” to the points of rest. There are also cases in which one of the vehicles is repaired prior to being documented. In these cases, there is a method that can be used to establish the approximated speed change of the vehicles. This method involves using the crush profile of one of the vehicles and balancing the opposing forces across the crush profile to determine an equivalent crush depth on the undocumented vehicle. Using this “balanced forces” method requires a detailed crush profile of one of the vehicles and good stiffness data for both vehicles. The method is not as accurate as standard methods because of the unknowns, but does yield reasonable results for the speed change severity for the vehicles involved.

EDVSM is a 3-dimensional vehicle simulator developed for the HVE simulation environment. The EDVSM vehicle model was based on the original HVOSM model, developed at Calspan for the Federal Highway Administration. This paper describes the vehicle and tire models used by EDVSM. The basic model is unchanged from the original HVOSM model, however, tire-road modeling has been substantially improved by the model's integration into the HVE environment. This paper provides the details of the integration procedure. The paper also includes a validation study, comparing results between EDVSM, HVOSM and real-world handling studies. Comparison reveals the results are substantially similar. Finally, applications and limitations of the model are addressed.

The EDSMAC personal computer program for use by accident investigators is described. The input data requirements are reviewed. The general calculation procedures are discussed and the specific procedures for computing delta-V are explained in detail. The method, based on equalizing the force between the vehicles at all times during the impact phase, is seen to be simple in concept but extremely complex in practice. The numerical and graphical output and warning messages are reviewed. Applications of the program are illustrated. The major benefit of EDSMAC is the ability, using graphics, to provide an analytical method illustrating how an accident may, or may not, have occurred.

This paper describes how a photogrammetric analysis computer program entitled FOTOGRAM™ is used with a personal computer. The FOTOGRAM program was described in a paper entitled “Photogrammetric Analysis Using the Personal Computer” by Brelin, Cichowski, and Holcomo.(1)* The technique described herein utilizes field examples to show how skid mark data are extracted from photographs using manual as well as electronic digitization methods. The digitized photographic data are then converted with the FOTOGRAM computer program into ‘real-world’ data points that may be plotted on a collision scene schematic. Thus, the actual path of the vehicle during skidding and/or tire marking can be determined for use in reconstructing the accident.

A new three-dimensional collision simulation algorithm, called DyMESH (Dynamic MEchanical SHell) was recently introduced.[1]* This paper presents a validation of DyMESH for vehicle vs. barrier collisions. The derivation of the three-dimensional force vs. crush relationship was described previously.[1] Here the application of three-dimensional force vs. crush curves using the outlined methodology is shown to be effective. Nonlinear force versus crush relationships are introduced for use in DyMESH. Included are numerous DyMESH collision simulations of several types of vehicles (e.g., light and heavy passenger car and sport utility) compared directly with experimental collision test results from various types of barrier tests (e.g., full frontal, angled frontal, and offset frontal). The focus here is not on the vehicle’s change in velocity, but on the acceleration vs. time history.

The EDSMAC simulation model has been in widespread use by vehicle safety researchers since its introduction in 1985. Several papers have been published that describe the model and provide validations of its use. In 1997, the collision and vehicle dynamics models were extended significantly. The main control logic was also extended and generalized. The resulting model was named EDSMAC4. This paper describes the EDSMAC4 model with particular attention to the extensions to the original algorithms. The paper also provides a validation of the new model by direct comparison to staged collision experiments and the results from the previous EDSMAC model.

The two procedures, DAMAGE and OBLIQUE IMPACT, which are used by EDCRASH for computing delta-V, are described in detail. Enhancements in EDCRASH Version 4 which improve the DAMAGE method of computing delta-V are also described. The advantages and disadvantages of each method are explored, and the numerical and graphical output and use of warning messages are reviewed. In general, it was found the two methods are complimentary: The DAMAGE procedure is best-suited for the conditions in which the OBLIQUE IMPACT procedure is least-suited, and vice-versa.

When an automobile is driven on wet roads, its tires must remove water from between the tread and road surfaces. It is well known that the ability of a tire to remove water depends heavily on tread depth, water depth and speed, as well as other factors, such as tire load, air pressure and tread design. It is less well known that tire tread depth combined with placement can have an adverse effect on vehicle handling on wet roads. This paper investigates passenger car handling on wet roads. Flat bed tire testing, three-dimensional computer simulation and skid pad experimental testing are used to determine how handling is affected by tire tread depth and front/rear position of low-tread-depth tires on the vehicle. Some skid pad test results are given, along with corresponding simulations. A literature review also is presented. Significant changes in tire-road longitudinal and lateral friction are shown to occur as speed, tread depth and water depth vary, even before hydroplaning occurs.

The time/distance relationship for a heavy truck starting from a stopped position is often needed to accurately assess the events leading up to a collision. A series of tests were conducted to document the low speed acceleration performance of a Freightliner FLD-120 tractor-truck. The tests including several load configurations and acceleration rates. The vehicle was instrumented with a DATRON speed sensor and the engine RPM was also documented. This paper presents data from these tests and discusses low speed acceleration profiles of heavy trucks