The subject matter described herein relates generally to cooling systems and, more particularly, to cooling systems, including diagnostic self-tests to identify one or more failure modes.
Vehicle cooling systems may experience one or more failure modes, such as leaks, coolant overfill or underfill, system clogs, and the like. In some instances, coolant level sensors are employed to detect some of these system-wide failure modes. However, it is also known that coolant level sensors may also experience one or more failure modes. For instance, for float-type coolant level sensors, failure modes may include a stuck or broken float. Other failure modes include broken switches, debris accumulation, valve malfunction, and the like. These failure modes can render the sensors ineffective or even inoperable.
In conventional cooling systems, failures are identified either (a) when the system fails, or (b) during frequent, time-intensive, and laborious manual system checks. These manual checks result in significant vehicle downtime, and may not be effective in identifying a source of a system or sensor failure. Moreover, certain tests, such as compression/squeeze tests, can add stress to the cooling system, which can in turn reduce the operational lifetime of the system. Additionally, at least some known coolant level sensors are configured or installed in a manner that makes the sensors difficult to inspect and may require significant dismantling of one or more components of the cooling system to inspect, repair, or replace.
In one or more embodiments, a coolant sensor assembly includes a sensor package having a first end and a second end, a first valve coupled between the first end of the sensor package and a coolant tank, a second valve coupled between the second end of the sensor package and the coolant tank, and a third valve coupled in flow communication with the second end of the sensor package. The sensor package includes a transparent, semi-transparent or opaque sight glass housing a coolant level sensor and configured to receive a flow of coolant therethrough.
In one or more embodiments, a cooling system of a vehicle includes a coolant tank, a coolant sensor assembly in flow communication with the coolant tank, and a controller configured to execute a diagnostic test (e.g. self-test) of the cooling system by: (a) cycling the cooling system through a plurality of operating modes; and (b) in each operating mode of the plurality of operating modes: (i) recording first sensor data output from the coolant sensor assembly to detect a level of coolant in the coolant tank; (ii) isolating the coolant sensor assembly from the coolant tank; (iii) recording second sensor data output from the coolant sensor assembly as the coolant is drained from the coolant sensor assembly; and (iv) analyzing the recorded first and second sensor data to identify or determine whether the cooling system is experiencing one or more failure modes.
In one or more embodiments, a method of diagnosing a cooling system of a vehicle includes (a) recording, by a controller, first sensor data output from a coolant sensor assembly in flow communication with a coolant tank of the cooling system, to detect a level of coolant in the coolant tank; (b) isolating the coolant sensor assembly from the coolant tank; (c) recording, by the controller, second sensor data output from the coolant sensor assembly as the coolant is drained from the sensor assembly; and (d) analyzing, by the controller, the recorded first and second sensor data to identify or determine whether the cooling system is experiencing one or more failure modes.
The inventive subject matter may be understood from reading the following description of non-limiting embodiments, with reference to the attached drawings, wherein below:
Embodiments of the subject matter described herein relate to vehicle cooling systems.
As described herein, vehicle cooling systems are essential for the reliable functioning of a vehicle engine (or other propulsion system). However, it is recognized there are various ways that a cooling system can fail, in particular, lose coolant, which degrades the performance of the engine over some period of time.
Accordingly, various coolant diagnostic systems have been contemplated and implemented, for identifying issues in a vehicle cooling system before the issue leads to significant performance degradation or even system failure. For instance, coolant level sensors have been implemented to monitor a level of coolant within the cooling system (and/or other significant parameters of the coolant, such as temperature, flow, and the like). If the coolant level drops below a threshold value, a potential leak is identified.
However, as discussed above, such coolant sensors have various failure modes themselves, which can lead to incorrect readings and reduced efficacy of such sensors in detecting leaks or other cooling system issues. Embodiments of the present disclosure are directed to improved coolant sensor assemblies that may reduce or eliminate one or more of the above-described disadvantages of known coolant sensors. Moreover, embodiments of the coolant sensor assemblies may include self-diagnostic functionality that enables additional assessment of the cooling system and/or the coolant sensor assembly itself. Even further, embodiments of the present disclosure may be directed to cooling systems that employ the coolant sensor assemblies as part of a larger system of assessment and diagnostics, to improve predictive failure identification and, thereby, preventative failure mitigation.
Embodiments of the present disclosure include, therefore, a coolant sensor assembly designed to mitigate or eliminate the above-described disadvantages of known coolant sensors, as well as to execute diagnostic self-tests to identify one or more failure modes experienced by the coolant sensor assembly. The coolant sensor assembly is coupled in flow communication with a coolant tank, and broadly includes a coolant level sensor, which may be embodied as a float sensor or any other suitable coolant level sensor, enclosed in a transparent, semi-transparent or opaque sight glass. The coolant sensor assembly may include one or more additional sensors. As described further herein, the additional sensors may be arranged in a tube parallel to the sight glass or may be positioned within the sight glass (e.g., coupled to an inner wall of the sight glass).
In operation, embodiments of the coolant sensor assembly execute a diagnostic test (e.g. self-test) by isolating the sight glass from the coolant tank (e.g., by actuating one or more valves) and draining the coolant from the sight glass. Sensor data output from the coolant level sensor, as well the additional sensor(s)(if present), is recorded and analyzed to identify any applicable failure mode(s) of the coolant sensor assembly and/or the cooling system overall. Failure modes of the coolant sensor assembly may include, for example and without limitation, mechanical failure, electrical failure, misaligned ports, poor coolant quality, sensor failure, and/or operational failure.
In the example embodiment, this diagnostic test is executed at least in part by a controller communicatively coupled to the coolant sensor assembly. As described further herein, the controller may be local to (e.g., physically coupled to) the coolant sensor assembly, or may be remote therefrom (e.g. a vehicle controller that controls multiple operations of a vehicle).
Additionally, the coolant sensor assembly of the present disclosure includes mechanical advantages over known coolant sensors, including the transparent, semi-transparent or opaque sight glass, which enables visual monitoring/diagnostics and/or remote diagnostics using specific signatures unique to the failure modes of the coolant sensor, as well as an improved connection system that enables more efficient removal of the coolant sensor assembly from the cooling system, for cleaning, repair, replacement, and the like.
Embodiments of a cooling system including the coolant sensor assembly are also described in further detail herein. The cooling system may leverage the diagnostic test, (e.g. self-test) executed in or for the coolant sensor assembly as well as additional sensor data to identify system-level failure modes, including leakage rates and locations, as well as overfilling or underfilling of the system. Remedial actions, including maintenance, repair, or mission cancellation, or other vehicle control (e.g. slowing or stopping) may be identified, proposed and/or executed based on the outcome of the diagnostic testing.
Turning now to the figures,
The sensor package 116 has a first or top end 122 and a second or bottom end 124 of the sensor package 116. In embodiments, at least a portion of the sight glass 118 extends from a first or top end, corresponding generally to the top end 122 of the sensor package 116, to a second or bottom end, corresponding generally to the bottom end 124 of the sensor package 116. The sight glass 118 is transparent or semi-transparent, to enable visual inspection of the coolant level sensor 120 therein. For instance, the sight glass 118 may be formed from a polymeric (e.g., plastic) material, or from glass. In some embodiments, the sight glass 118 is partially transparent/semi-transparent, in that the sight glass 118 may be formed from an opaque metallic material, such as steel, but include one or more windows (e.g., of a polymer or glass) for visibility. Therefore, when the sight glass is formed of an opaque material, a suitable transparent or semitransparent opening is provided in the sight glass to enable visual inspection of the coolant sensor level. In the example embodiment, the sight glass 118 is chemically inert to the coolant 102, as well as any additives thereof, and is capable of withstanding high temperatures, such as up to about 140° C. The sight glass 118 may be further encapsulated—on the interior or exterior thereof—with a film (e.g., a plastic or other polymeric film), a heat reflective sheet, and/or a guard material, to implement or enhance any feature or function of the sight glass 118, as well as to provide protection (e.g., thermal protection, shatter protection) to the sight glass 118.
In embodiments, the sight glass is made of glass or a transparent polymer and the entirety of the sight glass is transparent. In other embodiments, at least a portion of the sight glass is at least semi-transparent, meaning semi-transparent or transparent, with the sight glass possibly including opaque portions. However, in other embodiments, the entirety of the sight glass is opaque. An opaque sight tube may be used in instances where the sight tube is not readily visible when installed, or based on the nature of the coolant (plus additives), or if other portions of the coolant sensor assembly are transparent or semi-transparent, e.g., parallel sensor tubes for housing additional sensors, as described elsewhere herein. Thus, the term “sight glass” generally refers to an elongate, hollow tube or other elongate, hollow structure, and does not necessarily require that the sight glass be made of glass and/or is at least semi-transparent, unless otherwise specified herein.
In the example embodiment, the coolant level sensor 120 is coaxial with the sight glass 118 and also extends between the top end 122 and bottom end 124 of the sensor package 116. The coolant sensor assembly 114 is coupled in flow communication with the coolant tank 112, such that the sight glass 118 is at least partially filled with coolant 102, in correspondence with a level of coolant in the coolant tank (e.g., when all parts are operating as intended, a level of coolant in the sight glass will correspond, at least relatively or proportionally, to a level of coolant in the coolant tank, such that if the level of coolant in the coolant tank goes up the level of coolant in the sight glass increases correspondingly, and if the level of coolant in the coolant tank goes down the level of coolant in the sight glass decreases correspondingly). The coolant level sensor 120 is embodied in the example embodiment as a float sensor, which includes a float 126 circumscribing a stem 128. The stem 128 includes an electrical sensor, such as voltage sensor, having a plurality of switches (not illustrated) oriented along a vertical or longitudinal axis of the stem 128. The plurality of switches are arranged in a predetermined, regularly spaced pattern (e.g., every 0.25 inches along the length of the coolant level sensor 120). In normal operation, as the float 126 traverses the stem 128 (vertically downward), the float 126 opens the switches (e.g., via magnet), and a predictable voltage signal is output therefrom. The coolant level sensor 120 may alternatively be embodied as any other suitable coolant level sensor such as an ultrasound sensor or a capacitive sensor.
The coolant sensor assembly 114 also includes a first valve 130 coupled to the top end of the sight glass 118 and a second valve 132 coupled to the bottom end of the sight glass 118 (see
A sensor-tank interface 140 (see
As depicted in
The additional sensors 150 include any suitable sensor types that may be implemented for failure mode detection. In the example embodiment, the additional sensors 150 include pH sensor(s), to measure alkalinity of the coolant; corrosion sensor(s), to measure rust accumulation; capacitive sensor(s), to measure total dissolved solids (TDS); ultrasound sensors to use signal transmission to measure particulate matter in the coolant; and/or any combination thereof.
In the example embodiment, the coolant sensor assembly 114 is located outside of the coolant tank 112, which may enable more efficient inspection, operation, removal, and/or replacement thereof. However, in one or more alterative embodiments, the coolant sensor assembly 114 is positioned within the coolant tank 112.
Turning to
The cooling system 100 includes a plurality of valves 160 (see
In one example embodiment, the cooling system 100 also includes a controller 170 (see
The controller 170 includes at least one processor 172 for executing instructions. In some embodiments, executable instructions are stored in a memory 174. In some embodiments, the processor 172 includes one or more processing units (e.g., in a multi-core configuration). The memory 174 is any device allowing information such as executable instructions and/or other data to be stored and retrieved. Specifically, in some embodiments, the memory 174 includes, but is not limited to, random access memory (RAM) such as dynamic RAM (DRAM) or static RAM (SRAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and non-volatile RAM (NVRAM). The above memory types are exemplary only, and are thus not limiting as to the types of memory usable for storage of a computer program and/or data.
In some embodiments, the controller 170 is coupled to any component of the cooling system 100 via a wired and/or a wireless connection. In some embodiments, the controller 170 is configured to facilitate activation and control of the cooling system 100 (e.g., automatic control of the cooling system 100) to perform system-wide or assembly-level diagnostic tests, according to stored or received controls. In some embodiments, the controller 170 initiates the test(s) in response to a request or command, such as from an operator or remote device. In other embodiments, the controller 170 initiates the diagnostic test(s) periodically, according to a stored schedule.
Accordingly, the controller 170 may include a communication interface 176, which is communicatively couplable to any component of the cooling system 100 described herein and/or to a remote device (e.g., an operator device) that transmits controls for controlling operation of the cooling system 100 and/or receiving outputs (e.g., instructions, directions, alerts, remedial actions, etc.). In some embodiments, the communication interface 176 includes, for example and without limitation, a wired or wireless network adapter or a wireless data transceiver adapted for communication over a radio link (e.g., narrowband or broadband radio links), a cellular or mobile data network (e.g., 3G, 4G, or 5G network technology), or a BLUETOOTH link.
The controller 170 may be configured to interpret data from any sensor or other component of the cooling system 100 in accordance with pre-programmed instructions. For example, the controller 170 may interpret sensor data to identify the nature and/or location of one or more failure modes of the cooling system 100. As used herein, the identification of “failure modes” may include the identification of any system malfunction, as well as any normal or properly functioning condition of the cooling system 100 or any component thereof. That is, the controller 170 may store data (e.g., sensor data signatures, learning algorithms, etc.) to identify any “normal” or “abnormal” functioning of the cooling system 100 or any component thereof.
With reference to
The valve sensors 162 record 204 data during each transaction (e.g., to confirm suitable valve operation). In each operating mode, the coolant sensor assembly 114 and any valve sensors 162 record 204 sensor data. This sensor data is output to the controller 170. In some embodiments, the sensor data is output to the controller 170 substantially in real-time, such as within milliseconds or seconds of the sensor data being recorded at the respective sensor. In other embodiments, the sensor data is aggregated and output to the controller 170 at some later time, although still within seconds to minutes of each cycle 202.
The controller 170 analyzes 206 the sensor data, during or after receipt thereof. That is, in some cases, the controller 170 monitors and analyzes 206 the sensor data substantially concurrently with receipt of the sensor data; in other cases, the controller 170 receives and stores the sensor data and then subsequently performs analysis 206 of the entire sensor data set. In any embodiment, the controller 170 may store the received sensor data for any suitable length of time, for current or subsequent analysis thereof.
Moreover, the controller 170 may receive and store sensor data from periods of time other than during the diagnostic test(s). For example, cooling system sensors may record data during normal operation of the cooling system 100. The controller 170 may store this operational or “historical” sensor data and leverage the historical data in any of the analyses described herein (e.g., to track an identified leak over a period of time).
In the example embodiment, the controller 170 analyzes 206 the sensor data (e.g., including the recorded sensor data and, in some embodiments, the historical sensor data) by comparing the sensor data to stored signatures of known operational or failure modes that the coolant sensor assembly 114 or any other component(s) of the overall cooling system 100 may experience. For example and without limitation, the controller 170 stores, in the memory 174, the signature of operational switches, closed switches, open switches, missing or non-operational switches, power supply issues, operational float 126, stuck float 126, damaged or sunk float 126, leakage from the sight glass 118, leakage from another component of the cooling system 100, debris accumulation in the sight glass 118 or valves 130, 132, coolant alkalinity (representative of additive levels), coolant contamination, debris accumulation on the float 126, valve 130, 132, 160 malfunction, sensor package 116 misalignment, overheated coolant 102, overfilled coolant 102, and underfilled coolant 102. These signatures may be embodied as known sensor output from one or more of the coolant level sensor 120, valve sensor(s) 162, and/or additional sensor(s) 150, such as an electrical (e.g., voltage) signature or other characteristic of any collected sensor data. In some embodiments, the system-wide diagnostic test may also include a step of pressurizing the cooling system 100, which may accentuate the signatures of the known failure modes.
Various failure mode signatures are depicted in
In embodiments, the particular rate of loss of coolant within one operating mode, or common to all operating modes, is determined by the controller 170 and used to identify a location of a coolant leak based on when the coolant loss is detected (e.g., in which operating mode(s)) and the magnitude of the coolant loss. For example and without limitation, a moderate rate of coolant loss common across all operating modes may be reflective of a failure of a coolant pump (not shown); a drastic rate of coolant loss may represent a broken pipe, and the location may be identified using the signature of one or more valve sensors; a slow rate of coolant loss common across all operating modes may reflect internal leaks in the engine 104; a drastic rate of coolant loss in Mode 1 and Mode 3, but not in Mode 2, may be representative of a leak in the radiator 106 or a radiator hose; and a slow rate of coolant loss in Mode 1 and Mode 3, but not in Mode 2 (or less in Mode 2) may be representative of a leak in the intercooler 108.
By analyzing the sensor data, the controller 170 identifies 208 one or more failure modes experienced by the coolant sensor assembly 114 or of the cooling system 100 in which the coolant sensor assembly 114 is implemented.
In embodiments, the cycling 202 may also include initiating a diagnostic self-test in the coolant sensor assembly 114, during operation in one or more of the operating modes. Alternatively, the assembly diagnostic test may be executed independently of the system-wide diagnostic test. For example, in some instances, the controller 170 initiates the assembly diagnostic test periodically, in accordance with a stored schedule (e.g., every six months, twelve months, etc.). The stored schedule may be modified according to seasonal or ambient changes (e.g., to be initiated more frequently during the winter or in colder climates). In some instances, the controller 170 initiates the assembly diagnostic test after a positive outcome from the system-wide diagnostic test. In still other instances, the controller 170 initiates the assembly diagnostic test in response to a request or command, such as from an operator or remote device. For example, an operator may request initiation of the assembly diagnostic test prior to every vehicle mission.
Turning to
In an embodiment, the diagnostic test includes, once the coolant sensor assembly is isolated from the coolant tank by closing the valves 130, 132 (and with the drain valve remaining closed), receiving sensor data output by the sensor(s) of the coolant sensor assembly, and comparing the received sensor data to one or more designated criteria that are indicative of potential faults in the coolant sensor assembly. For example, once the assembly is isolated, the level of coolant in the sight glass should remain the same, unless there is a leak in the assembly. Thus, if the received sensor signals show a steady coolant level, the system may determine that the assembly is not leaking. However, if the received sensor signals show a decreasing coolant level, the system may determine that the assembly is leaking and needs repair. Similarly, other than temperature, other characteristics of the coolant should not change significantly when the assembly is isolated, at least not within a relatively short time period. Thus, if within a designated, relatively short time period the sensor output of any of the additional sensors changes (e.g. by more than a designated threshold, depending on sensor type), this may be indicative of a leak and/or sensor failure.
In another embodiment, isolating the coolant sensor assembly without draining may be used as an alternative or additional way to sense leaks in the coolant tank or other parts of the coolant system. For example, the coolant sensor assembly may be isolated, and then checked for leaks as per above. If the coolant sensor assembly is deemed as not leaking (e.g., all sensor outputs are steady), a current level of coolant in the sight tube is sensed and recorded, and the coolant system is controlled to a steady state, e.g., engine turned off and coolant pump deactivated, plus waiting a designated time period for any coolant in the circuit to return to the tank. Subsequently, a designated waiting period is tracked while the coolant system remains in steady state and the coolant sensor assembly is isolated. The waiting period provides a time for coolant to exit the tank if there are leaks present, e.g., thirty minutes to one hour. After the waiting period, the coolant sensor assembly is re-fluidly connected to the coolant tank, and the subsequent coolant level in the sight tube is sensed and recorded for a designated time period (e.g., several seconds or more). If there are no leaks present in the coolant tank (or other relevant locations), the sensed subsequent coolant level in the sight tube should be approximately the same as the original recorded coolant level. On the other hand, if there are leaks present in the coolant tank, the sensed subsequent coolant level in the sight tube should be less than the original recorded coolant level, and exhibit a near step-like decrease. The step-like decrease may be easier for the controller to identify than a gradual decrease.
The assembly diagnostic test may further include draining 304 the sensor package 116 (e.g., the sight glass 118) of coolant 102. The draining 304 includes actuating the drain valve 134 to an open, drain position. Where the drain valve 134 is remotely actuatable (e.g., may be electro-mechanically or electro-pneumatically actuated), the controller 170 may transmit signals to the drain valve 134, where the signals cause actuation of the drain valve 134 to the open position. Where the drain valve 134 is manually actuatable, the controller 170 may transmit instructions to an operator device communicatively coupled to the controller, wherein the instructions cause the operator device to display (e.g., on the user interface thereof) directions to a human operator to manually actuate the drain valve 134 to the open position.
During the isolating 302 and the draining 304, the sensors, including the coolant level sensor 120 and any additional sensors 150, record 306 sensor data, which is analyzed 308 by the controller 170 as described above. Notably, the analyzing 308 of the sensor data recorded 306 during the assembly diagnostic self-test may be performed in parallel with or before/after the cycling 202 of the cooling system 100 in the system-wide diagnostic test. Moreover, in certain embodiments, the assembly diagnostic test is performed entirely independently of any system-wide diagnostic test.
In an embodiment, the diagnostic test may include the coolant level of coolant in the coolant sensor assembly (e.g., in the sight glass) being sensed by the coolant level sensor from a time period after the coolant sensor assembly is isolated from the coolant tank but before the coolant sensor assembly is drained, through to when drainage is completed (while the sensor assembly is isolated from the coolant tank). If the coolant level sensor is operating normally, draining the coolant from the isolated coolant sensor assembly should result in the sensed coolant level exhibiting a linear decrease during the drainage time period (e.g., the sensed coolant level should transition from a steady higher level and then decrease linearly to a steady lower level). If the controller identifies such a linear decrease within the time period, it may determine that the coolant level sensor is operating as expected. On the other hand, if the controller identifies a different sensor signal waveform, such as a lack of such a linear decrease within the time period, the controller may determine that the coolant level sensor is not operating as expected and in a fault mode. The operation of other sensors in the coolant sensor assembly may be assessed similarly, e.g., during drainage each sensor should transition, during the time period, from a first state indicating a given characteristic of the coolant from the coolant being present to a second state indicating a lack of the given characteristic from the coolant being absent.
After drainage and recording/assessing sensor data of the coolant sensor assembly, the controller may be configured to control the drain valve closed and subsequently control the other valves open, to re-fluidly connect the coolant sensor assembly to the coolant tank, etc.
In embodiments, the system may be configured for coolant drained from the coolant sensor assembly to be routed back to the coolant tank, indirectly or directly, e.g., there may be line connected between the drain valve and the coolant system pump, such that the coolant system pump will pump the coolant drained from the coolant sensor assembly into the engine cooling fluid circuit. Or there may be a fluid conduit directly between the drain valve and the tank.
If any failure modes are identified 208, 310, during the system-wide or assembly diagnostic test, the controller 170 generates 210, 312 an instruction or other signal to address the identified failure modes. The instructions may identify the failure mode as well as remedial action to address the failure mode. The controller 170 may cause display of the instructions on a user interface (of the controller or a separate operator device) as directions for an operator to implement the remedial action(s). For example and without limitation, remedial actions include: for a stuck float, remove the sensor package and clean the float; for a non-operational switch, no action needed, or replace the sensor, depending the number of non-operational switches and/or the extent of the sensor malfunction; for power supply issues, inspect sensor package wiring harness; for a damaged float, replace the float and/or entire coolant level sensor; for valve malfunction, inspect and clean or replace the valve, depending on the nature and extent of the malfunction; for a leak, replace the identified leaking component; for an overfilled coolant tank, drain an amount of coolant from the tank; for an underfilled coolant tank, add coolant to the tank. In some embodiments, depending on the nature of the failure mode, the instructions may be delivered in the form of an alert. In some embodiments, the controller 170 may prevent operation of the cooling system 100 until the remedial action is taken.
In embodiments, the controller may be configured, responsive to determination of a fault condition of the cooling system or the coolant sensor assembly, to generate control signals for controlling a device that includes the cooling system (e.g., a vehicle) from a first mode of operation to a different, second mode of operation. E.g., slowing or stopping the vehicle, or preventing or discontinuing the vehicle from embarking on a trip or mission, or operating the engine or engine system in a way that accommodates for low coolant levels or situations where it is unclear what the actual coolant level is (e.g., modes of operation where the engine requires less or minimum cooling). Or operating the cooling system in a way to account for possible low coolant levels, such as running a radiator fan at a higher duty cycle (e.g., for longer and/or more often), and/or routing coolant always through subcoolers, multiple radiators, etc.
The system and methods of the present disclosure provide several advantages over conventional cooling systems and coolant level sensors. In particular, the coolant sensor assembly disclosed herein enables (i) more efficient identification of sensor disfunction (e.g., via visual inspection, while installed or removed, due to the sight glass; or via assembly diagnostic-self test); and (ii) more efficient removal of the assembly from the cooling system for inspection, cleaning, maintenance, repair, or replacement of any component thereof. Additionally, the system-wide diagnostic self-test facilitates (i) more precise and efficient identification and location of failure, including leaks; (ii) ensuring improved function of the cooling system before the vehicle is released for any mission; (iii) reducing or eliminating over/underfill of the coolant tank; (iv) reducing or eliminating the disadvantages of the compression/squeeze tests in conventional cooling systems; (v) reducing or eliminating excessive/insufficient coolant additives; and (vi) ensuring a vehicle is not released for any mission when the vehicle would be unable to complete the mission due to cooling system malfunction. These advantages not only improve the functionality of the cooling system but also facilitate reducing vehicle downtime, both due to more time-consuming and laborious conventional system testing, as well as due to system malfunction.
In one or more embodiments of the present disclosure, a coolant sensor assembly includes a sensor package having a first end and a second end, a first valve coupled between the first end of the sensor package and a coolant tank, a second valve coupled between the second end of the sensor package and the coolant tank, and a third valve coupled in flow communication with the second end of the sensor package. The sensor package includes a partially transparent or semi-transparent sight glass housing a coolant level sensor and configured to receive a flow of coolant therethrough.
Optionally, the coolant level sensor may include a float sensor, capacitive sensor or ultrasound sensor.
Optionally, the sensor package may further includes one or more additional sensors, including one or more of a capacitive sensor, a corrosion sensor, a conductivity sensor, or a pH sensor.
Optionally, the sensor package may further include a secondary tube parallel to and in fluid communication with the sight glass, wherein the one or more additional sensors are arranged in the secondary tube.
Optionally, the one or more additional sensors may be arranged within the sight glass along a coolant flow path therethrough.
Optionally, the sensor package may be removably coupled to the coolant tank.
Optionally, the first valve and the second valve may each include a respective cutout valve that is actuatable between an open position and a closed position.
Optionally, the third valve may be a drain valve actuatable between a closed position and an open, draining position.
Optionally, the coolant level sensor may include float and a stem, the stem including voltage sensor including a plurality of switches oriented along a vertical axis thereof.
Optionally, the assembly may further include a controller communicatively coupled to the coolant sensor and the one or more additional sensors, the controller including a processor and a memory device.
Optionally, the controller may be configured to execute an assembly diagnostic self-test for the coolant sensor assembly.
Optionally, to execute the diagnostic self-test, the controller may be configured to: (a) isolate the sensor package from the coolant tank by actuating the first and second valves from an open position to a closed position and the third valve from a closed position to an open, drain position to drain coolant from the sensor package; (b) record sensor data output from the coolant level sensor and the one or more additional sensors; and (c) analyze the recorded sensor data to identify whether the coolant sensor assembly is experiencing one or more failure modes.
Optionally, to analyze the recorded sensor data, the controller may be further configured to identify a signature sensor output indicative of one or more of: one or more missing switches, a stuck float of the coolant level sensor, one or more open switches, one or more switch failures, a sunk float of the coolant level sensor, a clog in the sensor package, or coolant contamination.
Optionally, the controller may be further configured to, when the diagnostic self-test indicates the coolant sensor assembly is experiencing one or more failure modes: (a) identify a nature of the one or more failure modes experienced by the coolant sensor assembly; (b) generate an instruction for remedial action to address the one or more failure modes experienced by the coolant sensor assembly; and (c) cause display of the instruction for remedial action on a local or remote user interface.
In one or more embodiments of the present disclosure, a cooling system of a vehicle includes a coolant tank, a coolant sensor assembly in flow communication with the coolant tank, and a controller configured to execute a diagnostic self-test of the cooling system by: (a) cycling the cooling system through a plurality of operating modes; and (b) in each operating mode of the plurality of operating modes: (i) recording sensor data output from the coolant sensor assembly to detect a level of coolant in the coolant tank; (ii) isolating the coolant sensor assembly from the coolant tank; (iii) recording sensor data output from the coolant sensor assembly as the coolant is drained from the coolant sensor assembly and the one or more additional sensors; and (iv) analyzing the recorded sensor data to identify whether the cooling system and/or the coolant sensor assembly is experiencing one or more failure modes.
Optionally, the controller may be further configured to: (c) retrieve historical sensor data from a memory; (d) analyze the recorded sensor data and the historical sensor data to determine a rate of coolant loss during any one or more operating modes of the plurality of operating modes; and (e) based on the rate of coolant loss, identify one or more sources of the coolant loss.
Optionally, the controller may be further configured to analyze the recorded sensor data to determine whether the coolant tank is overfilled or underfilled.
Optionally, the controller may be further configured to: (f) generate an instruction for remedial action to address a cause of the one or more failure modes; and (g) transmit the instruction for remedial action as an alert to a local or remote user interface.
In one or more embodiments of the present disclosure, a method of diagnosing a cooling system of a vehicle includes (a) recording, by a controller, sensor data output from a coolant sensor assembly in flow communication with a coolant tank of the cooling system, to detect a level of coolant in the coolant tank; (b) isolating the coolant sensor assembly from the coolant tank; (c) recording, by the controller, sensor data output from the coolant sensor assembly as the coolant is drained from the coolant sensor assembly; and (d) analyzing, by the controller, the recorded sensor data to identify whether the cooling system and/or the cooling sensor assembly is experiencing one or more failure modes.
Optionally, the method may include cycling the cooling system through a plurality of operating modes; and performing steps (a)-(d) in each operating mode of the plurality of operating modes.
As used herein, the terms “processor” and “computer,” and related terms, e.g., “processing device,” “computing device,” and “controller” may be not limited to just those integrated circuits referred to in the art as a computer, but refer to a microcontroller, a microcomputer, a programmable logic controller (PLC), field programmable gate array, and application specific integrated circuit, and other programmable circuits. Suitable memory may include, for example, a computer-readable medium. A computer-readable medium may be, for example, a random-access memory (RAM), a computer-readable non-volatile medium, such as a flash memory. The term “non-transitory computer-readable media” represents a tangible computer-based device implemented for short-term and long-term storage of information, such as, computer-readable instructions, data structures, program modules and sub-modules, or other data in any device. Therefore, the methods described herein may be encoded as executable instructions embodied in a tangible, non-transitory, computer-readable medium, including, without limitation, a storage device and/or a memory device. Such instructions, when executed by a processor, cause the processor to perform at least a portion of the methods described herein. As such, the term includes tangible, computer-readable media, including, without limitation, non-transitory computer storage devices, including without limitation, volatile and non-volatile media, and removable and non-removable media such as firmware, physical and virtual storage, CD-ROMS, DVDs, and other digital sources, such as a network or the Internet.
The singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise. “Optional” or “optionally” means that the subsequently described event or circumstance may or may not occur, and that the description may include instances where the event occurs and instances where it does not. Approximating language, as used herein throughout the specification and claims, may be applied to modify any quantitative representation that could permissibly vary without resulting in a change in the basic function to which it may be related. Accordingly, a value modified by a term or terms, such as “about,” “substantially,” and “approximately,” may be not to be limited to the precise value specified. In at least some instances, the approximating language may correspond to the precision of an instrument for measuring the value. Here and throughout the specification and claims, range limitations may be combined and/or interchanged, such ranges may be identified and include all the sub-ranges contained therein unless context or language indicates otherwise.
This written description uses examples to disclose the embodiments, including the best mode, and to enable a person of ordinary skill in the art to practice the embodiments, including making and using any devices or systems and performing any incorporated methods.
This application claims the benefit of priority to U.S. Provisional Patent Application No. 63/290,541, filed on Dec. 16, 2021, which is hereby incorporated by reference herein.
Number | Date | Country | |
---|---|---|---|
63290541 | Dec 2021 | US |