Patent Application
20240010191
Embodiments described herein relate to a low clearance warning system for vehicles.
Many vehicles, such as trucks, are configured to haul or transport loads. One aspect of a vehicle load is a vertical height, such as the height of a freight container or a load on a truck flatbed. It may be desirable for the vehicle to include a clearance warning associated with the vertical height. Therefore, embodiments described herein provide, among other things, systems and methods of low clearance warning.
In some embodiments, a low clearance detection system for a vehicle includes a first sensor, the first sensor configured to detect an object in front of the vehicle and generate an object clearance signal. The system includes a second sensor, the second sensor configured to detect a load height of a load of the vehicle and generate a load height signal. The system also includes a third sensor configured to detect a distance between the third sensor to a ground surface and to generate a ground reference signal. The system also includes an electronic processor configured to receive the object clearance signal from the first sensor, receive the load height signal from the second sensor, and receive the ground reference signal from the third sensor. The electronic processor is further configured to determine an object clearance threshold based on the object clearance signal, determine a clearance height of the load based on the load height signal and the ground reference signal, compare the object clearance threshold to the clearance height of the load, determine a load collision condition when the clearance height of the load exceeds the object clearance threshold and, in response to determining the load collision condition, control a vehicle system.
In some embodiments, a low clearance detection system for a vehicle includes a first sensor, the first sensor configured to detect an object in front of the vehicle and generate an object clearance signal. The system also includes a second sensor, the second sensor configured to detect a load height of a load of the vehicle, and generate a load height signal. The second sensor further configured to detect a distance between the second sensor to a ground surface and to generate a ground reference signal. The system also includes an electronic processor configured to receive the object clearance signal from the first sensor, receive the load height signal from the second sensor, and receive the ground reference signal from the second sensor. The electronic processor is further configured to determine an object clearance threshold based on the object clearance signal, determine a clearance height of the load based on the load height signal and the ground reference signal, compare the object clearance threshold to the clearance height of the load, determine a load collision condition when the clearance height of the load exceeds the object clearance threshold, and in response to determining the load collision condition, control a vehicle system.
Some embodiments provide a method of clearance detection for a vehicle. The method includes receiving, at a controller, object clearance data from a first sensor, receiving, at the controller, load height data from a second sensor, and receiving, at the controller, ground reference data from the second sensor. The method further includes determining, via the controller, an object clearance threshold based on the object clearance data, determining, via the controller, a clearance height of the load based on the load height data and the ground reference data, and comparing, via the controller, the object clearance threshold to the clearance height of the load. The method also includes determining, via the controller, a load collision condition in response to the calculated clearance height of the load exceeding the object clearance threshold, and in response to determining the load collision condition, controlling a vehicle system.
Other aspects, features, and embodiments will become apparent by consideration of the detailed description and accompanying drawings.
In the illustrated example, the system 100 includes a second sensor 130. In some examples, second sensor 130 is similar to first sensor 105, but is positioned to detect objects to the rear R of the vehicle 110. In one aspect, second sensor 130 is configured to detect objects in a field of view 135 and configured to detect a height 140 of a load 145 of the vehicle 110 based on one or more reflections of radio signals generated by the second sensor 130. The load 145 of the vehicle 110 may be, for example, a shipping container, a cargo container, or the like. In one aspect, the system 100 also includes a third sensor 150, similar to first sensor 105 and second sensor 130. In some examples, third sensor 150 is placed at the top-front of the load 145 of the vehicle 110 and positioned in a ground-facing orientation. In this example, third sensor 150 has a field of view 155 such that third sensor 150 detects a distance to ground 160 (again based on one or more reflections). In some examples, a fourth sensor 165, similar to the third sensor 150, is placed at the top-rear of the load of the vehicle 145 and configured in a ground-facing orientation. The fourth sensor 165 has a field of view 170 and is configured to detect a distance to ground 175. In some examples, the distance to ground 160 detected by the third sensor 150 is the same as the distance to ground 175. In other examples, the distance to ground 160 and distance to ground 175 are different.
The first sensor 105 is configured to generate and output an object clearance signal associated with the object detected by the first sensor 105. For instance, when the first sensor 105 detects the height 122 of the bridge 115 in front of the vehicle 110, the first sensor generates an object clearance signal associated with the height 122 of the bridge 115. In some cases, the object clearance signal includes information about a height of the bridge with reference to a ground level underneath the bridge. In other aspects, the object clearance signal includes a width of the opening underneath the bridge, positions of support beams of the bridge, or other information detected by the first sensor 105. The first sensor 105 and second sensor 130 are configured to communicate with a controller, such as controller 410 that is described in greater detail below. For instance, the first sensor 105 generates the object clearance signal and the second sensor 130 generates a load height signal associated with the height of the load 145 of the vehicle 11, and both signals are communicated to the controller 410.
The third sensor 150 and the fourth sensor 165 operate similarly and are both configured to communicate with controller 410. Both the third sensor 150 and the fourth sensor 165 are positioned at the top of the of the load 145 of the vehicle 110 and configured in a ground-facing orientation. In some instances, only one of the third sensor 150 and the fourth sensor 165 are mounted on the load 145 of the vehicle 110. In other instances, additional sensors are used. In some examples, third sensor 150 is configured to generate a ground reference signal associated with ground surface conditions detected by the third sensor 150. These ground conditions may include, among other things, road surface conditions, road roughness, an uneven road, potholes, and the like.
The forward structure detection sensor 405 is similar to first sensor 105 and is configured to generate an object clearance signal that represents an object detected by the forward structure detection sensor 405. The forward structure detection sensor 405 is configured to transmit the object clearance signal to controller 410.
The sensor 415 may be configured similarly to second sensor 130 or second sensor 210. The sensor 415 is configured to project rear-facing radar to detect a height of a load of the vehicle and/or a height of the vehicle. The ground reference detection sensor 420 is similar to third sensor 150 and is positioned in a ground-facing orientation to project ground-facing radar. In some examples, the sensor 420 detects road conditions, such as a rough road, an uneven road, a gravel road, a smooth paved road, and the like. The sensor 420 is also configured to generate ground reference signal, similar to the third sensor 150, and transmit the ground reference signal to the controller 410. The ground reference detection sensor 420 is provides the load height signal and the vehicle height signal to the controller 410.
The braking control interface 425 connects to a vehicle braking system, such as an antilock braking system (ABS), an electronic stability control (ESC) system, a dynamic rear proportioning (DRP) system, a traction control system (TCS), or the like.
The warning display 430 may include a heads-up display, a touch screen interface, lights on a dashboard of the vehicle, a vehicle infotainment system, or the like. In some embodiments, the warning display 430 is configured to display information generated by controller 410. For example, the controller 410 receives both a load height signal from sensor 415 and a forward structure detection signal from sensor the forward structure detection sensor 405. The controller 410 then compares the load height signal and the forward structure detection signal to determine if the load height is greater than the forward structure opening. This comparison is then displayed on the warning display 430. The warning display may also be configured to show one or more thresholds of clearance. For example, if the load height is within a certain first threshold of the forward structure opening, a first warning may be displayed on the warning display 430. If the load height is within a certain second threshold of the forward structure opening, the second threshold being greater than the first threshold, then a second warning may be displayed on the warning display. In these instances, the warnings illustrate degrees of clearance for the load of the vehicle and the opening detected by the forward structure sensor. In some instances, the warning display 430 is configured to display road surface conditions, detected infrastructure height, load height from ground, total vehicle height, distance to the detected infrastructure, or the like.
As previously discussed, in some instances, ground reference sensor data includes road surface conditions. Step 530 of the process 500 includes a road surface determination. For example, controller 410 determines that a road surface is rough and uneven using the ground reference sensor data obtained in step 515. Process 500 also includes step 535, where a controller calculates vertical safety distance threshold using the clearance height calculations, load height calculations, and the road surface determination. For example, in some instances, controller 410 determines that a detected infrastructure object with a calculated clearance height will require a vertical safety distance threshold of 3.0 feet to account for a rough and uneven road condition. Vertical safety distance threshold may range from inches to feet, such as from 1.0 inch to 10.0 feet. Other examples include additional vertical safety distance thresholds.
The process includes step 540, where the controller 410 determines if the vehicle and load heights are sufficiently large enough for the vehicle to safely traverse beneath the detected infrastructure object. If the controller 410 determines that the vehicle height and/or the load height is less than the vertical safety distance threshold, then, in step 545, the controller 410 controls the warning display 430 to display the infrastructure object height from ground, the load height from ground, and the distance from the vehicle to the infrastructure object. On the other hand, if the controller 410 determines that the vehicle height and/or the load height is greater than or equal to the vertical safety distance threshold, the process proceeds to step 560, as discussed below.
The process 500 includes step 550, where the controller 410 determines a distance to infrastructure using the infrastructure height sensor data, as previously discussed. The process 500 also includes step 555, where the controller 410 receives a vehicle speed. The process includes 560, where the controller 410 uses the vehicle speed and the distance to the infrastructure to determine if there is sufficient time for a driver braking response. For example, the controller 410 may receive a vehicle speed of 30 miles per hour and a distance to infrastructure of 250 feet. The controller 410 then determines whether or not there is sufficient time for a driver braking response. If controller 410 determines that there is sufficient time for a driver braking response, the controller 410 controls, in step 565, the warning display 430 to display the infrastructure object height from ground, the load height from ground, the distance from the vehicle to the infrastructure object, and a warning notice that a collision is imminent. The warning notice may be a light, sound, tactile response, or other alarm output by the warning display 430. For example, in some instances, if controller 410 determines that a collision between the vehicle and the detected infrastructure object is imminent and that a driver has sufficient time for a driver braking response, controller 410 controls warning display 430 to sound an audible alarm and flash a visible light. In some examples, higher vehicle speeds require a greater amount of time for a driver braking response. In these instances, the controller 410 determination occurs at a greater distance between the vehicle and the infrastructure.
On the other hand, if controller 410 determines that there is not sufficient time for a driver braking response, then, in step 570, the controller 410 controls the warning display 430 an audible, visual, or tactile response in addition to controlling the vehicle braking system to initiate an automatic braking maneuver. For example, controller 410 receives a vehicle speed of 30 miles per hour and a distance to infrastructure of 25 feet and determines that there is insufficient time for a driver braking response and initiates an automatic braking maneuver in order to bring the vehicle to a stop before a collision occurs. In some examples, the sufficient time for a driver braking response is a predetermined threshold and may vary depending on the vehicle, load weight, load size, or other such conditions. The controller 410 is configured to initiate an automatic braking maneuver at a range of distances and a range of speeds, such as between 1.0 foot and 1,000 feet, or between 5.0 miles per hour and 120 miles per hour.
The process 600 also includes step 635, where the controller determines if a previously calculated standard deviation of the load height sensor data is greater than a threshold. When the controller 410 determines, in step 640, that the standard deviation is not greater than a threshold, then the controller 410 determines that the road conditions are smooth and even. In some instances, smooth and even road conditions are indicative of a normal road, and in step 545, controller 410 uses a normal safety vertical distance adder when calculating the vertical safety distance threshold. However, when the controller 410 determines that the standard deviation is greater than the threshold, in step 650, the controller 410 determines that road conditions are bumpy and uneven. In some instances, bumpy and uneven road conditions are indicative of an abnormal road, and in step 655, controller 410 increase the vertical distance adder or use an abnormal safety distance adder when calculating the vertical safety distance threshold. In some examples, the vertical distance adder is a dynamic calculation made by the controller 410 as road conditions change during vehicle travel. For instance, as the vehicle travels over a road, the road conditions may change. In these instances, the vertical safety distance threshold is increased or decreased to meet the changing road conditions.
In some examples, the illustrated components may be combined or divided into separate software, firmware and/or hardware. For example, instead of being located within and performed by a single electronic processor, logic and processing may be distributed among multiple electronic processors. Regardless of how they are combined or divided, hardware and software components may be located on the same computing device or may be distributed among different computing devices connected by one or more networks or other suitable communication links. Accordingly, various implementations of the systems and methods described herein provide, among other things, techniques for a low clearance warning system for vehicles. Other features and advantages of the invention are set forth in the following claims.
In the foregoing specification, specific examples have been described. However, one of ordinary skill in the art appreciates that various modifications and changes may be made without departing from the scope of the invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present teachings.
The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims as issued.
Moreover, in this document relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms “comprises,” “comprising,” “has,” “having,” “includes,” “including,” “contains,” “containing,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, contains a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
An element proceeded by “comprises . . . a,” “has . . . a,” “includes . . . a,” or “contains . . . a” does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, includes, contains the element. The terms “a” and “an” are defined as one or more unless explicitly stated otherwise herein. The terms “substantially,” “essentially,” “approximately,” “about,” or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting example the term is defined to be within 10%, in another example within 5%, in another example within 1% and in another example within 0.5%. The term “coupled” as used herein is defined as connected, although not necessarily directly and not necessarily mechanically. A device or structure that is “configured” in a certain way is configured in at least that way but may also be configured in ways that are not listed.
