The present invention relates in general to automotive crash detection, and, more specifically, to detecting the direction of an impacting body's trajectory at the point of impact with a host vehicle and the location on the host vehicle of that point of impact.
Vehicle crash detection is a well-developed technology in the context of passive restraint systems which deploy during a crash in order to protect the vehicle occupants. Specialized sensors and robust detection algorithms provide a high reliability in detecting the onset of a crash that has a sufficient severity to automatically activate a passive restraint.
A typical crash sensing system may be comprised of an array of accelerometers, for example. Longitudinal and lateral acceleration sensor signals from the accelerometers can be generated within or communicated to a Restraints Control Module (RCM) which makes a deployment decision. Accelerometers mounted in the RCM have detection ranges from about −50 g to about +50 g. Satellite accelerometers remotely located in the front and sides of the vehicle typically have ranges from about −250 g tom about +250 g. Light to moderate impacts involving lower levels of acceleration cannot be reliably detected using the existing accelerometers. However, there would be benefits to having an ability to detect light impacts, i.e., when the impact severity is less than what the RCM module uses to initiate a restraint deployment.
Although light impacts between vehicles do not cause significant damage to the driver or passenger directly, they could begin a chain of post impact events which can lead to undesired outcomes such as further impacts or rollovers. Therefore, the detection and recording of occurrences of light impact collisions may of interest to vehicle owners, vehicle fleet operators, law-enforcement personnel, and insurance providers. This invention discloses techniques and systems for detecting light impacts to enable many different kinds of reactions such as modified vehicle control, the real-time alerting of third parties (e.g., insurance, fleet, and law enforcement agencies), and the recording/storage of incident information in the vehicle for later use by fleet operators and law enforcement for accident reconstruction.
When an impact occurs, it would be useful to automatically determine in real time not only the fact that an impact has occurred but also a direction of impact and the location along the outer perimeter of the vehicle where the impact has occurred. This information may be useful not only for reporting of incident details for accident reconstruction by crash investigators but also for real time control of vehicle systems including adapting or preparing passive restraint systems to deploy in a manner consistent with a developing situation or adjusting performance of powertrain systems for maintaining control and stability of the vehicle, for example.
In one aspect of the invention, a technique is provided for crash detection in a road vehicle which includes determining the location of an impact along an outer perimeter of the vehicle. Lateral acceleration, longitudinal acceleration, and yaw rate are measured during operation of the vehicle, wherein the lateral and longitudinal accelerations define a total acceleration. Occurrence of an impact is detected by comparing a total acceleration to an impact threshold. An impact angle is determined according to an arctangent of a ratio of the lateral and longitudinal accelerations. A center-of-gravity to impact distance is determined according to a mass of the vehicle, a moment of inertia of the vehicle, the measured accelerations, and the yaw rate. When the yaw rate is zero or less than a calibrated value and the impact angle is within a predetermined range of an integer multiple of 90°, then the impact location is determined in response to a projection of the impact distance selected according to signs of the lateral and longitudinal accelerations. Otherwise, the impact location is determined in response to a projection of the impact distance selected according to signs of the lateral and longitudinal accelerations and a sign of the yaw rate. As used herein, impact location typically means the coordinates (relative to the center-of-gravity of the vehicle) on the perimeter of vehicle where an impacting body strikes the vehicle (relative to the center-of-gravity of the impacting object).
Referring to
A body control module (BCM) 15, which is coupled to bus 12, is commonly present in a vehicle electrical architecture for performing general vehicle functions. BCM 15 provides one advantageous location for implementing the light impact detection of the invention. Controller network 11 further includes a powertrain controller, shown in this embodiment as an engine control module (ECM) 16 which is coupled to various powertrain sensors 17 such as a speed sensor. The vehicle may also have a traction control module comprised of an antilock brake system (ABS) module 18 connected to associated sensors such as wheel speed sensors.
BCM 15 may include, or is coupled to, a nonvolatile memory or storage 20 to be used in connection with crash detection and reporting. For purposes of accessing remote data and reporting impact events in real-time to remote systems (e.g., law enforcement or insurance companies), a wireless communication module 21 may also be connected with bus 12 to work in cooperation with BCM 15. An antenna 22 is connected to wireless communication module 21 for establishing a data communication channel (e.g., a cellular data connection).
The purpose of the light impact detection function is to detect as quickly as possible an impact that, although not sufficiently severe to trigger deployment of a passive restraint, could create vehicle instability or significantly alter the vehicle's initial kinetic energy (either rotational or linear momentum). This function is not intended to deploy airbags or any other passive restraints. However, sensitivity to impacts needs to be much higher than what is currently used in connection with the restraints controls.
This invention, however, is not limited to light-impact events only, but is intended to detect impact locations for all type of incidents including severe impacts. By increasing the sampling time of the algorithm (i.e., by increasing the number of times the algorithm is evaluated per second using the high-speed CAN signals as input to the algorithm), the invention will allow the determination of impact locations and directions for any type of events not involving rollover.
Impact detection may be done as shown in copending U.S. application Ser. No. 16/085,374, entitled “Light Impact Detection for Vehicle Using Low Computation Overhead.” filed concurrently herewith, which was granted as U.S. Pat. No. 10,417,913, and which is hereby incorporated by reference in its entirety. In summary, the light impact detection function uses progressive monitoring stages which initially may suspect and then confirm the occurrence of an impact. Vehicle acceleration and yaw rate are measured, and possibility of an impact is recognized using the following procedure:
where ax is longitudinal acceleration, ay is lateral acceleration, z is a time index wherein times z1, Z2, and Z3 are consecutive samples taken at a time step interval ΔT and where z2 is the current sample and z1 is the previous sample, and InImpact is a flag used to detect a duration for which the condition remains true.
When the ImImpact flag remains at a value of 1 for a predetermined duration then an impact is suspected and monitoring of the vehicle dynamics is heightened. For example, if the last three consecutive InImpact flags are 1, then an Impact_Suspected flag changes from 0 to 1. In the following pseudo-code, z1, z2, and z3 are the last three samples and the consecutive impact flags are InImpact[z1], InImpact[z2], and InImpact[z3]:
When Impact_Suspected[z3] equals 1, then various dynamic behaviors indicative of an impact are monitored in an attempt to confirm whether or not an impact is actually occurring. The dynamic behaviors may include checking for threshold values of the skidding of the front and rear tires, longitudinal and lateral velocity changes, continued excessive acceleration or yaw rate, and lane departure speed, for example. More specifically, an Impact_Confirmed flag may be set in response to the following vehicle dynamic behaviors.
One dynamic behavior is Change in Longitudinal Velocity. This is calculated by integrating the longitudinal acceleration ax as follows:
When an impact is suspected, LongVchange is checked against a threshold value SpeedChangeCalibration1. When the condition abs(LongVchange)>SpeedChangeCalibration1 is satisfied, then the Impact_Confirmed flag changes from 0 to 1.
Another dynamic behavior is Change in Lateral Velocity. This is calculated by integrating the lateral acceleration ay:
When an impact is suspected, LatVchange is checked against a threshold value SpeedChangeCalibration2. When the condition abs(LatVchange)>SpeedChangeCalibration2 is satisfied, then the Impact_Confirmed flag changes from 0 to 1.
Another dynamic behavior for confirming an impact is Rate of Side-Slip Due to Yaw Motion and Lateral Acceleration. This flag checks whether the front or the rear tires exceed a threshold predefined sideslip value. The computations of the sideslips are done using the following physics based model. First, the lateral acceleration alateral is computed using the measured sensor data ay, ωz, and vx such that
alateral=ay−χz×vx.
Then the lateral velocity is
The lateral velocity due to angular yaw rate, ωz, is
vangularFT=ω×dFT for front tires, and
vangularRT=ω×dRT for rear tires.
The total lateral velocities of the front and the rear tires are
vlateralFT=vlateral+vangularFT for front tires, and
vlateralRT=vlateral−vangularRT for rear tires.
So, the sideslip ratios for the front tire and the rear tire are
SideSlipFT=vlateralFT/vx for front tires, and
SideSlipRT=vlateralRT/vx for rear tires.
Then the impact confirmation is obtained by using predefined threshold values, SideSlipCalibration1 and SideSlipCalibration2, of the side slip ratios for the front and the rear axles.
For the front axle,
and for the rear axle
Another dynamic behavior for confirming an impact is Lane-Departure Acceleration Threshold. The lane departure acceleration is calculated by multiplying the yaw rate and the vehicle longitudinal velocity. If this lateral acceleration exceeds a threshold value AccelerationCalibration3 then an impact is confirmed as follows:
Yet another behavior for confirming an impact is impact duration wherein the Impact_Suspected flag is integrated over time, denoted by InImpactTime. An impact is confirmed when Impact_Suspected flag is activated and InImpactTime exceeds a pre-defined threshold value ImpactDurationCalibration1.
When any of the above conditions is satisfied, the value of the Impact_Confirmed flag is set to 1. Details concerning the impact are stored in a memory (i.e., black box) and an alert may be sent to a remote system or authority (e.g., law enforcement or insurance company). The detected impact can also be used to modify vehicle powertrain operation or to modify performance of a passive restraint system.
The present invention uses acceleration and yaw rate in order to geometrically identify an angle and location of an impact. As shown in
Impact distance dCG is preferably calculated from the moment of inertia of the vehicle using the following formula:
where in is the mass of the vehicle and J is the moment of inertia about CG 25. Impact distance is computed only when the total acceleration exceeds a predetermined threshold so that the above calculation does not involve dividing by zero.
To reduce noise in the computation (due to inherent noise in acceleration and yaw-rate signals received over a multiplex bus) and for more accurate estimation of the impact distance, a recursive least square (RLS) algorithm is preferably used in computing the impact distance from CG 25.
The impact angle is preferably found using the inverse tangent of the ratios of the lateral and longitudinal accelerations of the vehicle as shown below,
where
As shown in
In order to reduce data traffic when sending wireless crash reports over the “cloud” and to reduce onboard memory usage, the reporting and storage of crash data may use the quadrants shown in
Variables used in the impact location calculation according to a preferred embodiment include the following, as shown in the indicated Figures:
As a first step in determining an impact location, the invention checks for a special case in which the impact direction coincides with one of the ordinal directions (i.e., D1, D3, D5, or D7) and a yaw rate generated by the impact is below a threshold value. The low yaw rate indicates that the trajectory of impact intersects with the center of gravity (i.e., generates little or no torque around the CG). Since the impact occurs at a right angle, the location of impact can thus be narrowed down to one of the four locations at the ordinal directions from the CG, shown in
The invention uses various geometric projections wherein impact distance is projected according to axes/dimensions of the vehicle using the angle of impact. Variables representing various projections to be used in the analysis are as follows:
Rfs=Rf|sin(θ−ϕf)|
Rrs=Rr|sin(θ−ϕr)|
Rfs+=Rf|sin(θ+ϕf)|
Rrs+=Rr|sin(θ+ϕr)|
Lfs=Lf|sin(θ)|
Lrs=Lr|sin(θ)|
dWc=dW|cos(θ)|
dWs=dW|sin(θ)|
By way of example,
The possible coordinate locations of impact on the vehicle are then computed using the following derivations.
Depending on the acceleration, yaw-rate, and the direction of impact, a coordinate and its sign (positive or negative) are chosen from the above list of x and y coordinates.
When the special case is not detected in step 43, then geometric analysis is used to determine impact location by first calculating an impact distance dCG in step 47. In step 48, projections of the impact distance are identified, and corresponding possible values of the x and y coordinates are determined. In step 49, the actual x and y values are selected based on the signs of the longitudinal and lateral accelerations and the sign of the yaw rate. The thresholds used to detect the signs are defined as: εx corresponding to the x-acceleration (ax), εy corresponding to the y-acceleration (ay), ε107 corresponding to the yaw rate (ω), and εθ corresponding to the impact angle (θ).
For determining when lateral or longitudinal accelerations or yaw rate is approximately zero, one or more thresholds denoted εx, εy and εω are defined as calibratable numbers close to zero (e.g., εx=0.1). Thus, wherever the absolute value of longitudinal acceleration ax is less than threshold εx (i.e., |ax|≥εx), then the total acceleration is almost all a lateral acceleration (i.e., D3 or D7). Whenever the absolute value of yaw rate ω is less than threshold εω (i.e., |ω|≤εω), then the impact trajectory coincides with the center of gravity (i.e., dCG≈0).
When the special case is not found, then impact distance dCG is calculated and the geometric projections based on impact angle θ are determined. In a preferred embodiment, the geometric analysis may preferably be organized according to the quadrant in which the total acceleration direction occurs. Thus,
When acceleration falls in quadrant D2 because ax≥εx and ay≤−εy, then a corresponding one of
When acceleration is in quadrant D2 and the sign of the yaw rate is positive (ω>−εω) as shown in box 62, then the impact coordinates are found using
When acceleration is in quadrant D2 and the sign of the yaw rate is negative (ω<−εω) as shown in box 72, then the impact coordinates are found using
When acceleration falls in quadrant D4 because ax≤−εx and ay≤−εy, then a corresponding one of
When acceleration falls in quadrant D6 because ax≤−εx and ay≥εy, then a corresponding one of
When acceleration falls in quadrant D8 because ax≥εx and ay≥εy, then a corresponding one of
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2016/022425 | 3/15/2016 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2017/160274 | 9/21/2017 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
6741168 | Webb et al. | May 2004 | B2 |
7359821 | Smith et al. | Apr 2008 | B1 |
7725216 | Kim | May 2010 | B2 |
8436722 | Roh et al. | May 2013 | B2 |
8768565 | Jefferies et al. | Jul 2014 | B2 |
8825277 | McClellan et al. | Sep 2014 | B2 |
9002554 | Chen | Apr 2015 | B2 |
20030112133 | Webb | Jun 2003 | A1 |
20070100521 | Grae | May 2007 | A1 |
20070271105 | Gunderson et al. | Nov 2007 | A1 |
20080201042 | Cuddihy et al. | Aug 2008 | A1 |
20100017066 | Lu | Jan 2010 | A1 |
20110006890 | Le | Jan 2011 | A1 |
20130124035 | Doerr | May 2013 | A1 |
20130320654 | Clark | Dec 2013 | A1 |
20140024334 | Berry et al. | Jan 2014 | A1 |
20140163848 | Tamir | Jun 2014 | A1 |
20140375446 | Wanami | Dec 2014 | A1 |
Number | Date | Country |
---|---|---|
2261087 | Dec 2010 | EP |
2485971 | Jun 2012 | GB |
20140134849 | Nov 2014 | KR |
Entry |
---|
Machine Translation of EP2261087A1 (Year: 2010). |
Number | Date | Country | |
---|---|---|---|
20190126874 A1 | May 2019 | US |