The present disclosure generally relates to methods and systems for leak detection in an engine sound transportation passageway, and more particularly to detecting a rupture within a barrier of the sound transportation passageway.
An engine sound transportation passageway (“passageway”) can be used to communicate engine noise to a driver or other passengers within a passenger cabin of an automobile. The passageway is typically a tube of sorts and is often coupled to an engine airway (e.g., engine intake airway or exhaust airway) at one end and to the passenger cabin at the other end. Typically, an air-tight sound-permeable barrier (e.g., a diaphragm) exists within the passageway to prevent fluid communication between the engine intake airway and the interior passenger cabin. The airways on each side of the barrier are mechanically coupled through the barrier to allow sound vibrations from the engine intake to pass through the passageway into the passenger cabin.
To allow sound vibrations to be communicated, the air-tight sound-permeable barrier is typically constructed of a thin material (e.g., plastic), which allows the barrier to vibrate in response to the sound vibrations within the engine airway. However, due to its thin nature, it may be susceptible to rupturing or developing a leak. If such a rupture or leak develops, fluid communication between the engine airway and the passenger cabin can occur, which can be undesirable. Current preventative solutions exist to combat the development of a rupture, including, for example, the inclusion of mechanical stops that hinder overexpansion of the barrier to reduce stress thereon. In other approaches, vehicle manufacturers simply dictate a scheduled replacement of the barrier (e.g., every 10,000 miles or 2 years) to prevent ruptures or to repair existing ruptures that may be otherwise unnoticed.
Though suitable for at least some purposes, such approaches do not necessarily meet all needs of all application settings and/or all users. For example, current solutions are merely preventative in nature and do not account for or accommodate an actual occurrence of a rupture within the barrier.
In one embodiment, a method includes monitoring a sound transportation passageway existing between an engine airway and a passenger cabin to effectuate sonic communication therebetween, the sound transportation passageway including an air-tight sound-permeable barrier between the engine airway and the passenger cabin. The method also includes detecting a rupture in the air-tight sound-permeable barrier and effecting a warning and/or a corrective action in response to detecting the rupture.
In another embodiment, an apparatus includes a sensor configured to sense a characteristic of a volume of gas within a sound transportation passageway including an air-tight sound-permeable barrier between an engine airway and a passenger cabin. The apparatus also includes a processing device communicatively coupled to the at least one sensor. The processing device is configured to receive sensor data from the sensor, determine an occurrence of a rupture in the barrier based on the received sensor data, and effect a warning and/or a corrective action in response to determining an occurrence of a rupture.
In another embodiment, a vehicle includes an engine air intake, a passenger cabin, and a sound transportation passageway. The passageway includes a first portion in fluid communication with the engine air intake, a second portion in fluid communication with the passenger cabin, a sound-permeable diaphragm defining an air-tight boundary between the first portion and the second portion, and an intake sound control valve configured to attenuate a sound level transported from the engine air intake to the passenger cabin. The vehicle also includes a sensor configured to sense a characteristic of a volume of air within the first portion and/or the second portion of the sound transportation passageway. The vehicle also includes a processing device communicatively coupled to the intake sound control valve and the sensor, the processing device configured to receive sensor data from the at least one sensor, determine an occurrence of a rupture in the diaphragm based on the received sensor data, and transmit a command to the intake sound control valve to close in response to determining the occurrence of the rupture.
Before any embodiments of the disclosure are explained in detail, it is to be understood that the disclosure is not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the following drawings. The disclosure is capable of other embodiments and of being practiced or of being carried out in various ways. Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including,” “comprising,” or “having” and variations thereof herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items.
Referring now to the figures,
Turning now to
In one embodiment, the engine assembly 200 includes a sound transportation passageway 216 existing between an engine airway and a passenger cabin 104 of the vehicle 100. As is shown in
Although the description provided here is with regards to a sound transportation passageway 216 in fluid communication with the engine air intake 208, these teachings are understood to be applicable to other engine airways. For example, in another embodiment, the sound transportation passageway 216 may include or comprise a branch off of the exhaust piping 204. Thus, it should be understood that these teachings are not limited to the embodiment described here utilizing the air intake 208.
With continued reference to
The apparatus 228 also includes at least one sensor 232 communicatively coupled to the processing device 230. In certain embodiments, at least a second sensor 234 can be communicatively coupled to the processing device 230, while in other embodiments other additional sensors may be utilized. The sensors 232, 234 can communicate with the processing device 230 via known communication protocols (e.g., CAN, UART, and the like). In one embodiment, either or both of the sensors 232, 234 are flow sensors, while in another embodiment, either or both of the sensors 232, 234 are pressure sensors. A combination of sensor types may also be utilized in other embodiments, while other sensor types may be utilized in still other embodiments (e.g., temperature sensors, microphones, leak detectors, humidity sensors, chemical make-up sensors, CO2 sensors, smoke detectors, and the like). The sensors 232, 234 are configured to sense, detect, monitor, or measure a characteristic of a volume of gas (e.g., air, exhaust, etc.) within the sound transportation passageway 216. For example, the sensors 232, 234 may sense a pressure level or flow rate of the air 210 within the sound transportation passageway 216.
The sensors 232, 234 are positioned such that at least one sensor monitors a volume of gas on either the first portion 220 of the sound transportation passageway 216 or the second portion 222 of the sound transportation passageway 216. The sensors 232, 234 may include modules that are mounted or coupled to an external surface of the sound transportation passageway 216, or otherwise exist outside of the sound transportation passageway 216, with sensing elements passing through apertures within a wall of the sound transportation passageway 216. Alternatively, the sensors 232, 234 can be mounted on an internal surface of the sound transportation passageway 216. In one embodiment as is illustrated in
The processing device 230 and/or 402 is configured or programmed to receive sensor data from either or both of the sensors 232, 234 including sensor readings or other data indicative of a current, average, or historical state of the particular measured characteristic corresponding to the monitored volume of gas within the sound transportation passageway 216. For example, the processing device 230 and/or 402 may receive first sensor data from the first sensor 232 and receive second sensor data from the second sensor 234. The processing device 230 and/or 402 is further configured or programmed to monitor the readings from the sensors 232, 234, thus effectively monitoring the characteristics of the volume of gas within the sound transportation passageway 216.
Turning now to
Although fluid communication between the passenger cabin 104 and the engine air intake 208 may not be harmful, it may produce undesirable results or effects for the driver and/or passengers. For example, pressure changes may occur within the passenger cabin 104 dependent upon the operational state of or amount of air required by the engine 108 due to the fluid communication with the engine air intake 208. Additionally, air outside of the passenger cabin 104 may enter the passenger cabin 104 without first passing through applicable filters (e.g., environmental filters) and without being subject to control mechanisms that otherwise control the environment of the passenger cabin 104 (e.g., heater or air conditioning). Further, a rupture 302 in the air-tight sound permeable barrier 218 may alter the sound characteristics of the engine noise 227 provided into the passenger cabin 104. Thus, it is advantageous to either warn of the occurrence of a rupture 302 and/or correct the rupture 302 (e.g., control, reduce, or neutralize the effects of a rupture 302) if and when it develops.
The processing device 230 and/or 402 is configured to utilize, at least in part, the readings from the sensors 232, 234 to detect or determine the occurrence of the rupture 302 within the air-tight sound-permeable barrier 218. In response to detecting the rupture 302, the processing device 230 and/or 402 can effect a warning and/or a corrective action. For example, the processing device 230 and/or 402 could perform an action on its own behalf to effect a corrective action (e.g., by effecting an action or producing a warning by a system over which is has direct or indirect control). For example, in the instance that the processing device 230 and/or 402 is part of an ECU 214, a warning may include effecting illumination of a warning light for a system that the ECU 214 controls. Similarly, a corrective action may include reducing the maximum revolutions per minute (RPMs) (e.g., a redline governor) or reconfiguring the engine 108 and/or engine air intake 208 in a manner that may reduce or neutralize the effect of the rupture 302 on the passenger cabin 104.
Alternatively, the processing device 230 and/or 402 may communicate with another system 236 to either communicate an indication of the occurrence of the rupture 302 or to communicate a command for that system 236 to produce a warning or to perform a corrective action. A warning could include, for example, an audible warning (e.g., a tone and/or a vocal warning), a visual warning (e.g., a warning light, a graphical image, or a textual message), a tactile warning (e.g., vibrating the steering wheel or the seat), or other suitable types of warnings. In such an instance, the processing device 230 and/or 402 may communicate with a system 236 such as, for example, a media system, a navigation system, an audio system, a dashboard controller, or some other system to effect the warning. In some embodiments, an engine code may be stored within the ECU 214 to be read by a diagnostic scanning tool, for example, an on-board diagnostic (e.g., OBD, OBD-II, EOBD, or the like) compatible scanner. Similarly, the processing device 230 and/or 402 may command one or more other systems 236 to perform the corrective action. For example, the processing device 230 and/or 402 may communicate with an environmental system so that it may control the effects of the rupture on the passenger cabin 104 by, for example, accounting for the exterior temperature or engine temperature (which air 306 may be at that increased or decreased temperature) when controlling the temperature of the passenger cabin 104. In another approach, the environmental system may control the flow rate of air blown into the passenger cabin 104 in a variable manner to account for and counteract any pressure changes that may occur due to the rupture 302. In another approach still, the processing device 230 and/or 402 may communicate with a window control system to open the windows or skylight slightly to neutralize any pressure change effects from the rupture 302 and/or to provide additional ventilation. Many other warning and corrective actions may be performed by varying systems 236 and/or by the processing device 230 and/or 402 itself and are contemplated by this disclosure.
Turning now to
The valve 406 may be in electrical communication with and controlled by a sound valve controller 404 including a processing device 402. The sound valve controller 404 may be communicatively linked to the ECU 214. Alternatively, the valve 406 may be in electrical communication with and controlled by the ECU 214 or controlled by both the sound valve controller 404 and the ECU 214. The processing device 402 or 230 (whichever is in control of the valve 406) may be configured to transmit a plurality of commands to the valve 406 to variably open and close the valve 406 based, at least in part, on a current operational state of the engine 200 of the vehicle 100. For example, at certain speeds and/or revolutions-per-minutes (RPMs) of the engine 200, the valve 406 may be closed or opened (partially or fully) to reduce or increase the engine sound 227 transported into the passenger cabin 104, respectively. In one approach, at wide-open throttle, the valve 406 may be fully opened to allow maximum engine sound 227 levels within the passenger cabin 104, while at lower RPMs or throttle levels, the valve 406 may be partially or fully closed to reduce the engine sound 227. In other approaches, the opposite may occur in that the valve 406 may be opened when at lower RPMs when the sound 224 output by the engine is at a lower volume while the valve 406 may be closed when at higher RPMs when the sound 224 output by the engine 200 is louder. Further, the operation of the valve 406 may be determined by, at least in part, a setting of the vehicle (e.g., a factory setting or a user-selectable setting, e.g., sport mode, quiet mode, etc.) which may influence or dictate the amount of engine sound 227 to be transported into the cabin 104. Many variations are possible as to the control of the valve 406 when functioning as a sound control valve, which variations are fully contemplated by this disclosure.
In certain embodiments, as is shown in
Turning now to
In some embodiments, the air-tight sound-permeable barrier 218 can be replaced (either in response to the failure or as part of a normal maintenance routine based on mileage and/or time). The processing device 230 and/or 402 may be made aware of the replacement (for example, by a mechanical clearing an OBD engine code stored within the ECU 214) and can resume normal operation of the valve 406 which may entail opening the valve 406 to allow engine sound 224 to pass therethrough once again. Alternatively, the apparatus 400 can continue to monitor the air 210 within the sound transportation passageway 216 (continuously or periodically) to determine if the rupture 302 has been repaired or otherwise remedied. For example, the valve 406 may be periodically opened (e.g., based on time, or when starting or stopping the engine 108) to determine if sensor readings have returned to levels indicative of normal operation of the system. If such a determination is made, the apparatus 400 can once again resume normal operation as described herein.
Turning now to
In one embodiment, detecting the rupture 302 in the air-tight sound-permeable barrier 218 further includes determining that a value corresponding to a characteristic of a volume of gas (e.g., air 210) within the sound transportation passageway is outside of an allowable range. In one approach, sensor 232 and/or 234 may return sensor data to the processing device 230 and/or 402 that is outside of an allowable range, which in turn indicates, at least in part, the occurrence of a rupture 302. For example, the first sensor 232 may be a flow sensor that detects the flow of air 304 or other gasses. Before the occurrence of a rupture 302, the flow of air 304 within the first portion 220 of the sound transportation passageway 216 (e.g., the passenger cabin-side of the barrier 218) may be relatively low or negligible. Thus, for example, an allowable range may include zero air flow up to a small threshold amount of air flow 304. However, in the case of a rupture 302, air flow 304 sensed by the first sensor 232 may exceed the threshold amount of air flow 304, thereby exceeding the allowable range of air flow 304. In such an instance, the processing device 230 and/or 402 may determine the occurrence of a rupture 302. Similarly, in another example, a second sensor 234 may also be a flow sensor detecting the flow of air 210 within the second portion 222 of the sound transportation passageway 216 (e.g., the engine-side of the air-tight sound-permeable barrier 218). When the air-tight sound-permeable barrier 218 is intact, the flow of air 210 past the sensor 234 should be relatively low as the second portion 222 of the sound transportation passageway 216 is a dead-end without an air outlet. Thus, in the absence of a rupture 302, the flow of air 210 may be predominantly within an allowable range. However, if a rupture 302 occurs, the air 210 within this second portion 222 of the sound transportation passageway 216 may flow through the air-tight sound-permeable barrier 218, thus causing an increase in the amount of air flow 210 at the second sensor 234. This may produce a higher sensor reading from sensor 234 and the processing device 230 and/or 402 may determine that the sensor data exceeds a threshold or is outside of an allowable range and, in turn, determine that a rupture 302 has developed.
In another example, the first sensor 232 may be a pressure sensor that detects the air pressure (e.g., ambient air pressure) within the first portion 220 of the sound transportation passageway 216 (e.g., the passenger cabin-side). Before the occurrence of a rupture 302, the pressure within the first portion 220 (which, in certain embodiments, may mirror the pressure within the passenger cabin 104) may remain relatively steady. In another approach, the pressure may follow (for example, within an allowable tolerance rage) a known, expected, or recorded pressure curve that may vary according to different operational aspects of the vehicle, including, for example, vehicle speed, window position (e.g., open or closed, distance opened), climate control operations (e.g., fresh air intake or recirculation, fan speed, etc.), engine operation, or other factors that may impact pressure within the passenger cabin 104. It should also be noted that, when used as a pressure sensor, in certain embodiments, the first sensor 232 may be located in other locations within the passenger cabin. After a rupture 302 occurs, the pressure within the first portion 220 of the sound transportation passageway 216 (and, possibly the entirety of the passenger cabin 104) may fluctuate, for example, in accordance with the operation of the engine 108. These fluctuations may exceed an allowable range, for example, a range of allowable pressure levels, a range of allowable pressure level fluctuations (e.g., an allowable amount of pressure fluctuation above and below a measured or determined average pressure level), or a range of allowable pressure level rates of change (e.g., an allowable rate at which the pressure level may fluctuate, for example, corresponding to a first-order derivative of the pressure level). If these values are outside of the allowable range, the processing device 230 and/or 402 may determine that a rupture 302 has occurred. In another embodiment, the second sensor 234 situated within the second portion 222 of the sound transportation passageway 216 may be a pressure sensor to detect the pressure within the second portion 222. Before the occurrence of a rupture 302, the pressure within the second portion 222 may be highly variable and dependent upon the current operation of the engine 108. However, after a rupture 302 occurs, the pressure within the second portion 222 may become less variable as pressure is relieved and/or pressure change rates or values are attenuated through fluid communication with the larger body of air within the first portion 220 and within the passenger cabin 104 via the rupture 302. Thus, the pressure values and/or fluctuations may be outside of (for example, below) an allow range of pressure values or fluctuation rates. If these values are outside of the allowable range, the processing device 230 and/or 402 may determine that a rupture 302 has occurred.
The particular values for the allowable range (for example, the threshold as the upper-end of an allowable range of air flow) may be set or determined based on the needs and characteristics of a particular application and/or setting. Further, the allowable ranges may have only one point (e.g., single threshold) at which values above or below that point are considered within the allowable range, two end points defining a particular allowable range, or multiple various segments of allowable ranges.
Turning now to
In making a determination that the rupture 302 has occurred, the processing device 230 and/or 402 may wait a predetermined amount of time during which the sensor data may be outside of an allowable range before making a final determination of the occurrence of a rupture 302. For example, a rupture may be determined if sensor data is outside of an allowable range (consistently or intermittently) for 1 second, 2 seconds, 5 seconds, 10 seconds, or another shorter or longer period of time. In other embodiments, the processing device 230 and/or 402 may count the number of sensor data samples that are outside of an allowable range. In other embodiments, the processing device 230 and/or 402 may determine the allowable range based on a current operation of the engine 108 coupled to the engine airway. For example, if an engine 108 is being operated at higher RPMs or with wide-open throttle, air flow 210 may be greater or pressure may be greater (e.g., high turbo-boost pressure, etc.) or less (e.g., higher vacuum) as more air 210 is being consumed by the engine 108.
In a similar manner, the sensors 232, 234 can be utilized by the processing device 230 and/or 402 to determine if the valve 406 has malfunctioned, become frozen, developed a leak, become damaged, or is otherwise inoperative. In one example, the second sensor 234 can be read to determine if its data properly corresponds to a current setting of the valve 406. For example, if the valve 406 is closed, air pressure, air flow, sound volume, or other measurable characteristics may be very low within the second portion 222 of the sound transportation passageway 216 that is downstream from the valve 406. The second sensor 234 may be located within this downstream portion. Accordingly, in this example, if the measured value (e.g., air flow, pressure, sound level, etc.) is above a threshold level corresponding to when the valve 406 is closed, the processing device 230 and/or 402 may determine that the valve 406 has malfunctioned, become frozen, developed a leak, become damaged, or is otherwise inoperative. Many other implementations are possible for utilizing the sensors 232, 234 to determine the operational status of the valve 406 and are contemplated by this disclosure.
Turning now to
Various embodiments of the present invention may be embodied in many different forms, including, but in no way limited to, computer program logic for use with a processor (e.g., a microprocessor, micro controller, digital signal processor, server computer, or general purpose computer), programmable logic for use with a programmable logic device (e.g., a Field Programmable Gate Array (FPGA) or other PLD), discrete components, integrated circuitry (e.g., an Application Specific Integrated Circuit (ASIC)), or any other means including any combination thereof.
Computer program logic implementing all or part of the functionality previously described herein may be embodied in various forms, including, but in no way limited to, a source code form, a computer executable form, and various intermediate forms (e.g., forms generated by an assembler, compiler, linker, or locator). Source code may include a series of computer program instructions implemented in any of various programming languages (e.g., an object code, an assembly language, or a high-level language such as C, C++, or JAVA) for use with various operating systems or operating environments. The source code may define and use various data structures and communication messages. The source code may be in a computer executable form (e.g., via an interpreter), or the source code may be converted (e.g., via a translator, assembler, or compiler) into a computer executable form.
The computer program may be fixed in any form (e.g., source code form, computer executable form, or an intermediate form) in a tangible storage medium, such as a semiconductor memory device (e.g., a RAM, ROM, PROM, EEPROM, or Flash-Programmable memory), a magnetic memory device (e.g., a diskette or fixed disk), an optical memory device (e.g., a CD-ROM), a PC card (e.g., PCMCIA card), or other memory device. The computer program may be distributed in any form as a removable storage medium with accompanying printed or electronic documentation (e.g., shrink wrapped software), preloaded with a computer system (e.g., on system ROM or fixed disk), or distributed from a server or electronic bulletin board over the communication system (e.g., the Internet or World Wide Web).
Hardware logic (including programmable logic for use with a programmable logic device) implementing all or part of the functionality previously described herein may be designed using traditional manual methods, or may be designed, captured, simulated, or documented electronically using various tools, such as Computer Aided Design (CAD), a hardware description language (e.g., VHDL or AHDL), or a PLD programming language (e.g., PALASM, ABEL, or CUPL).
Programmable logic may be fixed either permanently or temporarily in a tangible storage medium, such as a semiconductor memory device (e.g., a RAM, ROM, PROM, EEPROM, or Flash-Programmable memory), a magnetic memory device (e.g., a diskette or fixed disk), an optical memory device (e.g., a CD-ROM), or other memory device. The programmable logic may be distributed as a removable storage medium with accompanying printed or electronic documentation (e.g., shrink wrapped software), preloaded with a computer system (e.g., on system ROM or fixed disk), or distributed from a server or electronic bulletin board over the communication system (e.g., the Internet or World Wide Web).
The present disclosure describes preferred embodiments with reference to the Figures, in which like numbers represent the same or similar elements. Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
The described features, structures, or characteristics of the invention may be combined in any suitable manner in one or more embodiments. In the description, numerous specific details are recited to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
The schematic flow chart diagrams included are generally set forth as logical flow-chart diagrams. As such, the depicted order and labeled steps are indicative of one embodiment or various embodiments of the presented method. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated method. Additionally, the format and symbols employed are provided to explain the logical steps of the method and are understood not to limit the scope of the method. Although various arrow types and line types may be employed in the flow-chart diagrams, they are understood not to limit the scope of the corresponding method. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the method. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted method. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown. Some embodiments provided for are described as computer-implemented method claims. However, one of ordinary skill in the art would realize that the method steps may be embodied as computer code and the computer code could be placed on a tangible, non-transitory computer readable medium defining a computer program product.
Although the above discussion discloses various exemplary embodiments of the invention, it should be apparent that those skilled in the art can make various modifications that will achieve some of the advantages of the invention without departing from the true scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
6065329 | Fukada | May 2000 | A |
6192749 | Marek | Feb 2001 | B1 |
6551389 | Spannbauer et al. | Apr 2003 | B2 |
6600408 | Walter et al. | Jul 2003 | B1 |
7658263 | Jasnie et al. | Feb 2010 | B2 |
7975802 | Yokoya et al. | Jul 2011 | B2 |
20060236973 | Seibt | Oct 2006 | A1 |
20100314193 | Jasnie | Dec 2010 | A1 |
20130008737 | Muller et al. | Jan 2013 | A1 |
20130199487 | Bernard | Aug 2013 | A1 |
Number | Date | Country |
---|---|---|
2008184991 | Aug 2008 | JP |
2008184992 | Aug 2008 | JP |
Number | Date | Country | |
---|---|---|---|
20160286326 A1 | Sep 2016 | US |