The present disclosure relates to check valve testing systems, and methods using the same. In particular, the present disclosure relates to check valve testing systems and leak detection methods that are suitable for use with fluid supply systems, such as a water supply system.
Fluid supply systems often convey fluid from a pressurized source to a destination, such as a building or other structure. For example, buildings often include a water supply system that is configured to receive a pressurized supply of water from a municipal water system, and to convey water to various outlets such as toilets, faucets, fire prevention systems, etc., within the building. When the water is provided at a sufficient pressure it will be pressurized against and can flow through the outlets in a forward direction. If pressure is lost or reduced below a threshold amount, however, a “backflow” condition may arise in which the water flows backwards toward the source. As fluid backflow may contaminate the source, technologies such as backflow preventers have been implemented to limit or prevent fluid backflow.
Many fluid supply systems include one or more check valves that function to limit or prevent backflow. Over time the components of a check valve may deteriorate, causing the check valve to leak or otherwise fail. To confirm that a check valve is functional and does not require replacement, maintenance personnel may periodically test its operation. Such testing is typically performed manually, which can be time consuming and inconvenient—particularly if the valve is located in a hard to reach location.
A need therefore remains in the art for check valves that are more easily and more conveniently tested, as well as systems and methods that utilize such valves. The present disclosure is aimed at such needs.
Features and advantages of various embodiments of the claimed subject matter will become apparent as the following Detailed Description proceeds, and upon reference to the Drawings, wherein like numerals designate like parts, and in which:
Although the following Detailed Description will proceed with reference being made to illustrative embodiments, many alternatives, modifications and variations thereof will be apparent to those skilled in the art.
As noted in the background water and other fluid supply systems often include a check valve assembly that is configured to limit or prevent fluid backflow towards a source. Components in such valves can break down over time, causing the valve to leak or otherwise malfunction. In a water system, a substantial amount of water may result from a leaking or otherwise malfunctioning valve. Moreover, substantial property damage may occur if a check valve leaks or otherwise malfunctions during an emergency event, such as a backflow event.
Testable check valves have been developed to address such issues. With such a valve, a maintenance technician can manually test the operation of the valve and determine whether it is working properly or needs replacement. Unfortunately such testing is often difficult and inconvenient due to the location of the valve. As a result, many check valves go untested for long periods, during which the valve may leak or otherwise fail.
The present disclosure relates to check valve testing systems, and leak detection methods using the same. As will be described in detail below, the systems described herein include a testable check valve assembly that includes a check valve, a first pressure zone (FPZ) upstream of the check valve, and a second pressure zone (SPZ) downstream of the check valve. The FPZ is fluidly coupled to (and in some cases forms part of) an inlet of the check valve assembly, which in turn is configured to fluidly couple to an outlet of an electronically actuated inlet valve. The inlet valve further includes an inlet that is configured to fluidly couple to a liquid source, such as but not limited to a municipal water supply. The SPZ is fluidly coupled to (and in some cases forms part of) an outlet of the check valve assembly. The outlet of the check valve assembly is further configured to fluidly couple to an inlet of an electronically actuated outlet valve. An outlet of the outlet valve is configured to fluidly couple to one or more outlets in a destination, such as faucets, toilets, etc. within a building or other location. The system further includes an electronically actuated drain valve, a pressure sensor, and a controller. The electronically actuated drain valve is configured to fluidly couple to the FPZ (i.e., upstream of the check valve). The pressure sensor is configured to detect a fluid pressure within the SPZ (i.e., downstream of the check valve), and to provide a sensor signal indicative of the detected liquid pressure within the SPZ to the controller. The controller is configured to communicatively couple with the inlet valve, the outlet valve, the drain valve, and the pressure sensor, e.g., via a wired or wireless communications protocol.
As used herein, the term “electronically actuated” when used in connection with a valve means that the valve is configured to close or open in response to an electronic signal, such as a control signal. For example, an electronically actuated valve may include or be coupled to a pilot that is configured to close the valve in response to a control signal. Any suitable pilot may be used, and in some embodiments the electronically actuated valves described herein may include or be coupled to a pneumatic pilot, a hydraulic pilot, an electrical pilot (e.g., a solenoid such as a proportional solenoid), or a combination thereof.
In normal operation the inlet and outlet valves are open, the drain valve is closed, and liquid (e.g., water) flows in a forward direction through the inlet valve, through the FPZ, through the check valve, through the SPZ, through the outlet valve, and to one or more outlets in a destination. During a testing operation, however, the controller configured to conduct one or more test operations to determine whether there are any leaks in the system, and/or to determine whether the check valve within the check valve assembly is functioning properly.
In embodiments, during a testing operation the controller issues (or causes the issuance of) a first control signal, wherein the first control signal is configured to cause the inlet valve to close. For example, the control signal may be transmitted to a pilot that is included in or coupled to the inlet valve, in response to which the pilot causes the inlet valve to close. The controller may then monitor the liquid pressure in the SPZ, e.g., based at least in part on the sensor signal provided by the pressure sensor. If the controller determines that the liquid pressure in the SPZ varies (e.g., falls) in response to closing of the inlet valve, the controller may determine that there is a leak downstream of the check valve and issue (or cause the issuance of) an appropriate leak notification. For example, controller may transmit or cause the transmission of a leak notification signal to an external electronic device (e.g., a cellular phone, smart phone, laptop, desktop, etc.), wherein the leak notification message is configured to cause the electronic device to present a leak notification indicator, e.g., on a display or other user audiovisual element of the electronic device.
If the pressure in the SPZ remains steady following closure of the inlet valve, the controller may optionally issue a (second) control signal to the outlet valve, wherein the (second) control signal is configured to cause the outlet valve to close. Regardless of whether the controller causes the outlet valve to close, the controller may issue a (third) control signal to the drain valve, wherein the third control signal is configured to cause the drain valve to open. The controller may then monitor the liquid pressure within the SPZ, based at least on the sensor signal provided by the pressure sensor. If the controller determines that the liquid pressure within the SPZ varies (e.g., falls) following opening of the drain valve, the controller may determine that there is a leak through the check valve within the check valve assembly. In such instances the controller may issue or cause the issuance of a faulty check valve notification. For example, the controller may transmit or cause the transmission of a faulty check valve notification to an external electronic device, wherein the faulty check valve notification is configured to cause the electronic device to present a faulty check valve notification indicator, e.g., on a display or other audiovisual element of the electronic device.
As will be appreciated, the systems and methods described herein can enable convenient and frequent testing of a check valve assembly, without the need the need for manual interaction with components of a liquid supply system e.g., by a maintenance technician.
Check valve assembly 103 may be any suitable type of check valve assembly, such as but not limited to a check valve assembly that includes one or multiple check valves. For the sake of illustration, check valve assembly 103 is shown as including a single check valve 107, a first pressure zone (FPZ) 109 upstream of check valve 107, and a second pressure zone (SPZ) 111 downstream of check valve 107. Such a configuration is not required, however, and check valve assembly 103 may have any suitable number of check valves with a corresponding number of pressure zones upstream and downstream of each check valve. For example, check valve assembly 103 may include 1, 2, 3, 4, 5, or more check valves, with pressure zones upstream and downstream of each of check valve. Non-limiting examples of check valve assemblies that may be used as check valve assembly 103 include the EA251 and EA453 non-return valves sold by WATTS®. In any case, check valve assembly 103 is generally configured to permit fluid flow in a forward direction (i.e., from an inlet of check valve assembly 103 towards an outlet thereof), but to prevent fluid flow in a backward direction (i.e., from an outlet of check valve assembly 103 towards an inlet thereof).
As used herein, the term “pressure zone” when used in connection with a check valve assembly means a conduit in which fluid can flow or be maintained under pressure. In general, the check valve assemblies described herein include at least two pressure zones per check valve included in the assembly—one upstream of the check valve and one downstream of the check valve. In embodiments where a check valve assembly that includes more than one check valve, an pressure zone that is downstream of one check valve in the assembly may be upstream of a another check valve in the assembly, and vice versa. For example, a check valve assembly that includes two check valves may include first, second, and third pressure zones, wherein the first pressure zone is upstream of the first check valve, the third pressure zone is downstream of the second check valve, and the second pressure zone is downstream of the first check valve but upstream of the second check valve.
In the embodiment of
Check valve assembly 103 includes an inlet and at least two outlets. As noted above the inlet of check valve assembly 103 is configured to fluidly couple to inlet valve 101. In embodiments, the inlet of check valve assembly 103 is an opening that is fluidly coupled to FPZ 109. The first outlet of check valve assembly is fluidly coupled to outlet valve 105. In embodiments, the first outlet of check valve assembly 103 is an opening that is fluidly coupled to SPZ 111. The second outlet from check valve assembly 103 is fluidly coupled to drain valve 113.
Check valve 107 is disposed between FPZ 109 and SPZ 111 and is configured to regulate the flow of liquid through check valve assembly 103. The nature and configuration of check valve 107 is not limited, and any suitable check valve may be used. Non-limiting examples of suitable check valves that may be used as check valve 107 include globe valves, ball check valves, double door check valves, lift check valves (e.g. a piston check valve), stop check valves, swing check valves, tilting disc check valves, combinations thereof, and the like. Without limitation, in embodiments check valve 107 is or includes a piston check valve. Regardless of its nature, check valve 107 is generally configured to permit fluid to flow from the inlet that is configured to fluidly couple to inlet valve 101 to the outlet that is configured to couple to outlet valve 105.
In the embodiment of
Any suitable type of electronically actuated valve may be used as drain valve 113. Non-limiting examples of types of valves that can be used as drain valve 113 include those mentioned above as suitable for use as inlet valve 101 and/or outlet valve 105. Without limitation, in embodiments drain valve 113 includes or is coupled to a pilot (e.g., a pneumatic or electrical pilot) that is configured to open or close drain valve 113 responsive to a corresponding control signal. For example, drain valve 113 may include or be coupled to a solenoid (e.g., a proportional solenoid), wherein the solenoid is configured to open or close drain valve 113 a control signal from controller 117. Alternatively, drain valve 113 may include or be coupled to a pneumatic pilot that is configured to open or close drain valve 113 responsive to a control signal. Non-limiting examples of valves that may be used as drain valve 113 include the DSVP series of pilot-operated water inlet valves sold by DELTROL CONTROLS®.
Sensor 115 is or includes a pressure sensor that is configured to detect fluid pressure downstream of check valve 107. For example, sensor 115 may be or include a pressure sensor that is configured to detect fluid pressure within SPZ 111, at or within the outlet of check valve assembly 103 that is configured to couple to outlet valve 105, and/or at any other point in the fluid pathway between check valve 107 and outlet valve 105. Without limitation, in embodiments sensor 115 is or includes a pressure sensor that is configured to detect fluid pressure within SPZ 111. Non-limiting examples of suitable pressure sensors that may be used as sensor 115 include the 500 and 600 series pressure sensors sold by HUBA CONTROL® and the DN5 servo-controlled manual operated valve sold by A.U.K. MULLER®.
Check valve assembly 103 may include a test cock or port that allows sensor 115 to couple to check valve assembly 103 such that it can detect fluid pressure within second pressure zone 111. In any case, sensor 115 is configured to detect a fluid pressure downstream of check valve 107 and produce a sensor signal indicative of the detected pressure. As will be described below, the sensor signal can be used by controller 117 to determine the detected pressure, e.g., during a test of check valve 107.
Controller 117 is configured to communicatively couple to sensor 115, and to communicatively couple with inlet valve 101, outlet valve 105, and drain valve 113 or one or more actuators that are configured to actuate such valves. In general, controller 117 is configured to control the operation of inlet valve 101, outlet valve 105, and drain valve 113, and to execute one or more testing operations consistent with the present disclosure. For example, during normal operation of system 100, inlet valve 101 and outlet valve 105 may be open and drain valve 113 may be closed. During such operation controller 117 may do nothing, or it may issue control signals that cause inlet valve 101 and outlet valve 105 to remain open and drain valve 113 to remain closed. During a testing operation, however, controller 117 may issue control signals that cause one or more of inlet valve 101 and outlet valve 105 to close, and which cause drain valve 113 to open. During the testing operation, the controller may determine the liquid pressure between check valve 107 and outlet valve 105 (e.g., within SPZ 111) based at least in part on the sensor signal produced by sensor 115. From the determined pressure and the configuration of valves 101, 105, and 113, controller 117 may determine whether there is a leak downstream of check valve assembly, and/or whether check valve 107 is functioning normally, as will be described in detail later.
Processor 201 may be any suitable general-purpose processor or application specific integrated circuit. Without limitation, in embodiments processor 201 is one or more single or multicore processors produced by INTEL® corporation, APPLE® corporation, AMD® corporation, SAMSUNG® corporation, NVIDIA® corporation, Advanced Risc Machines (ARM®) corporation, combinations thereof, or the like. While
Memory 203 may be any suitable type of computer readable memory. Examples of memory types that may be used as memory 203 include but are not limited to: programmable memory, non-volatile memory, read only memory, electrically programmable memory, random access memory, flash memory (which may include, for example NAND or NOR type memory structures), magnetic disk memory, optical disk memory, phase change memory, memristor memory technology, spin torque transfer memory, combinations thereof, and the like. Additionally or alternatively, memory 203 may include other and/or later-developed types of computer-readable memory.
COMMS 205 may include hardware (i.e., circuitry), software, or a combination of hardware and software that is configured to allow controller 117 to transmit and receive messages via wired and/or wireless communication from one or more external devices, such as but not limited to an external electronic device 221 as noted above, valves 101, 105, 113, and sensor 115. While
Controller 117 further includes testing control module (TCM) 209. In this specific context, the term “module” refers to software, firmware, circuitry, and/or combinations thereof that is/are configured to perform one or more check valve testing operations consistent with the present disclosure. Software may be embodied as a software package, code, instructions, instruction sets and/or data recorded on non-transitory computer readable storage mediums. Firmware may be embodied as code, instructions or instruction sets and/or data that are hard-coded (e.g., nonvolatile) in controller 117, e.g., within memory 203 or other storage. For example, TCM 209 may be in the form of computer readable instructions (e.g., stored on memory 203) which when executed by processor 201 cause controller 117 to perform check valve testing operations consistent with the present disclosure, or to return system 100 to a normal operating condition (e.g., before or after the performance of a check valve testing operation). Alternatively, in embodiments, TCM 209 is in the form of logic that is implemented at least in part in hardware to perform check valve testing operations consistent with the present disclosure, or to return system 100 to a normal operating condition (e.g., before or after the performance of a check valve testing operation).
In embodiments TCM 209 is configured to cause controller 117 to perform check valve testing operations to determine whether there is a leak downstream of check valve assembly 103. To perform such operations TCM 209 may cause controller 117 (or, more specifically, COMMS 205) to issue a first control signal to inlet valve 101, wherein the first control signal is configured to cause inlet valve 101 to move to a closed position. In embodiments where inlet valve 101 is coupled to an external pilot or other actuator, the first control signal may cause the external pilot/actuator to close inlet valve 101. During this time drain valve 113 is in a closed condition. In any case, TCM 209 may then cause controller 117 to monitor the liquid pressure downstream of check valve 107, e.g., within SPZ 111. For example, TCM 209 may cause controller 117 to monitor the liquid pressure within SPZ 111 or at another point downstream of check valve assembly 103 for a specified period of time, hereinafter referred to as a first test period. The first test period may extend for any suitable length of time, and in some embodiments ranges from greater than 0 to about 60 seconds, such as from greater than 0 to about 30 seconds, greater than 0 to about 15 seconds, or even greater than 0 to about 5 seconds. In any case, controller 117 may determine the liquid pressure detected by sensor 115 within SPZ 111 or at another point downstream of check valve assembly 103 based at least in part on sensor signals produced by sensor 115 over the first test period.
Controller 117 may then determine whether the detected pressure remains stable over the first test period. As used herein, the term “stable” when used in connection with a detected pressure means that the detected pressure did not vary by greater than a defined pressure variance threshold. The pressure variance threshold may be selected to achieve a balance between a desired sensitivity of the system and the desire to limit or false positive results. In embodiments, the pressure variance threshold is set to about a 0.5%, 1%, 3%, or even 5% change in detected pressure over the test period. In embodiments, the pressure variance threshold is set to a 0.5%, 1%, 3%, or 5% drop in pressure over the test period. The controllers may determine that a pressure is unstable if it varies by more than a pressure variance threshold during a relevant test period.
If the detected pressure remains stable over the first test period, TCM 209 may cause controller 117 to determine that a leak is not present downstream of check valve assembly 103 or, more specifically, downstream of outlet valve 105. If the detected pressure varies by more than the threshold pressure variance over the first test period, however, TCM 209 may cause controller 117 to determine that a leak or other source of pressure drop is present downstream of check valve assembly 103. In such instances, TCM 209 may cause controller 117 to issue or cause the issuance of an appropriate leak notification. For example, controller 117 may display a leak notification indicator on optional user interface 211. Alternatively or additionally, controller 117 may transmit or cause the transmission of a leak notification signal to external electronic device 221, wherein the leak notification message is configured to cause external electronic device 221 to present a leak notification indicator, e.g., on a display or other user audiovisual element of the electronic device.
If the detected pressure remains steady during the first test period (i.e., following closure of inlet valve 101), TCM 209 may cause controller 117 to determine that there is not a leak downstream of check valve assembly 103 or, more specifically, outlet valve 105. In such instances, TCM 209 may cause controller 117 to perform additional testing operations, hereinafter referred to as “second testing operations”. For example, TCM 209 may optionally cause controller 117 to issue a second control signal, wherein the second control signal is configured to cause outlet valve 105 to move to a closed condition. For example, controller 117 may transmit a second control signal to an actuator or pilot of outlet valve 105, wherein the second control signal causes the actuator or pilot of outlet valve 105 to move outlet valve 105 to a closed condition. During this time, drain valve 113 is in the closed condition. In such instances TCM 209 may then cause controller 117 to monitor the pressure downstream of check valve 107 (i.e., within SPZ 111 or at another location between check valve 107 and outlet valve 105) for a second test period. The length of the second test period may be the same or different as the length of the first test period, and may extend from the time at which outlet valve 105 is moved to the closed condition. In any case, TCM 209 may cause controller 117 to monitor the pressure detected by sensor 115 during the second test period based at least in part on the sensor signals produced by sensor 115.
For example, TCM 209 may cause controller 117 to determine the pressure detected by sensor 115 based at least in part on sensor signals produced by sensor 115, and to determine whether the detected pressure remains stable over the second test period. The manner in which the controller 117 determines that the pressure remains stable during the second test period is the same as described above for the first test period and so is not reiterated in the interest of brevity. If controller 117 determines that the detected pressure did not remain stable (i.e., dropped or dropped more than a threshold pressure variance), TCM 209 may cause controller 117 to determine that there is a leak in outlet valve 105. In such instances, TCM 209 may cause controller 117 to issue or cause the issuance of an appropriate leak notification, e.g., in the same manner described previously.
If controller 117 determines that the detected pressure remains stable over the second test period (or if the second testing operations are not performed), TCM 209 may cause controller 117 to perform additional testing operations, hereinafter referred to as third testing operations. The third testing operations may be performed following the closure of inlet valve 101 and optionally following the closure of outlet valve 105. During the third testing operations, TCM 209 may cause controller 117 to issue a third control signal, wherein the third control signal is configured to cause drain valve 113 to move to an open condition, while inlet valve 101 is closed and outlet valve 105 is optionally closed. TCM 209 may then cause controller 117 to monitor the pressure downstream of check valve 107 (e.g., within SPZ 111 or at any point between check valve 107 and outlet valve 105) over a third test period. The length of the third test period may be the same or different than the first and/or second test periods, and may extend from the time at which drain valve 113 is opened while inlet valve 101 (and optionally outlet valve 105) is closed.
In any case, TCM 209 may cause controller 117 to monitor the pressure detected by sensor 115 during the third test period based at least in part on the sensor signals produced by sensor 115. For example, TCM 209 may cause controller 117 to determine the pressure detected by sensor 115 based at least in part on sensor signals produced by sensor 115 during the third test period, and to determine whether the detected pressure remains stable over the second test period. The manner in which the controller 117 determines that the pressure remains stable during the third test period is the same as described above for the first and second test periods and so is not reiterated in the interest of brevity. If controller 117 determines that the detected pressure did not remain stable over the third test period (e.g., the pressure dropped or dropped more than a threshold pressure variance), TCM 209 may cause controller 117 to determine that there is a leak in check valve 107. In such instances, TCM 209 may cause controller 117 to issue or cause the issuance of an appropriate leak notification, e.g., in the same manner described previously concerning leaks detected in outlet valve 105 or downstream of outlet valve 105. In that way, TCM 209 may enable controller 117 to test the functionality of check valve 107 and determine whether it is or is not functioning properly.
As noted above the systems of the present disclosure are not limited to use with check valve assemblies that include a single check valve. Indeed, the systems described herein can be used with check valve assemblies that include a plurality (e.g., 2 or more) check valves. In such instances, the systems can include one or multiple (e.g., 2 or more) pressure sensors, wherein each pressure sensor is configured to monitor the pressure in a pressure zone that is downstream of one or more of the check valve assemblies. For example, in instances where check valve assembly 103 includes two or more check valves, a single pressure sensor may be used and configured to detect the pressure downstream of all of the check valves in the assembly. In such instances, testing operations identical to those conducted above could be conducted to detect whether there is a leak through any of the check valves in the assembly. In the event a leak is detected through the check valve assembly, however, such a system may not be able to identify which of the plurality of check valves in the assembly is leaking. If such functionality is desired, a plurality of pressure sensors may be used, wherein each pressure sensor is configured to detect the pressure in a pressure zone immediately downstream of a respective check valve. In such instances controller 117 may: cause inlet valve 101 to close; optionally cause outlet valve 105 to close; cause drain valve 113 to open; and monitor the pressure detected by each pressure sensor over a defined test period. If the each detected pressure remains stable over the test period, controller 117 may determine that all check valves in the assembly are functioning properly. But if the pressure detected by one or more of the plurality of sensors varies over the test period, controller 117 may determine that a leak is present through the check valve corresponding to the pressure sensor that is reporting the variable pressure.
While the foregoing description focuses on embodiments in which controller 117 and sensor 115 are coupled to other elements of a fluid supply system (e.g., inlet valve 101, check valve assembly 103, outlet valve 105, drain valve 113, etc.), such a configuration is not required and controller 117 and sensor 115 may be provisioned separately. For example, controller 117 and sensor 115 may be supplied separately from a fluid supply system and may be configured such that they can couple to the above noted components of a fluid supply system in order to perform check valve testing operations as discussed above.
Another aspect of the present disclosure relates to methods of testing check valves using a system consistent with the systems described herein. In that regard attention is directed to
Following the operations of block 305 or if such operations are omitted, the method may proceed to optional block 307, pursuant to which the pressure downstream of a check valve in the check valve assembly may be monitored by the controller. Operations pursuant to block 307 may include determining the pressure detected by a pressure sensor downstream of the check valve based at least in part on sensor signals generated by the pressure sensor over a first test period (if only the inlet valve is closed) or a second test period (if both the inlet valve and outlet valve are closed), as described above.
Following the operations of block 307 the method may proceed to optional block 309 pursuant to which a determination may be made as to whether the detected pressure remained stable over the first test period (if block 305 was omitted) or the second test period (if block 305 was included). Operations pursuant to block 309 may include determining, with a controller, whether the pressure detected by the pressure sensor during the first/second test period varied by less than a threshold pressure variance. If not (i.e., the pressure varied by more than the threshold pressure variance), the method proceeds to optional block 311, pursuant to which an alert notification is issued as described above. If block 305 was omitted, the alert notification may be configured to indicate that a leak is detected downstream of the check valve assembly. If block 305 is included, the alert notification may be configured to indicate that there is a leak through the outlet valve.
If the pressure remained stable over the first and/or second test periods, the outcome of block 309 is yes and the method may proceed to block 313, pursuant to which a drawn valve fluidly coupled to the check valve assembly upstream of a check valve is opened, while the inlet valve and optionally the outlet valve remain closed. Alternatively, the method may proceed from block 303 to block 313 in instances when the operations of blocks 305-309 are omitted. Operations pursuant to block 313 may include issuing a third control signal from a controller to the drain valve or an actuator of the drain valve, wherein the third control signal is configured to cause the drain valve to open as described above in connection with
The method may then proceed to block 317 pursuant to which a determination may be made as to whether the detected pressure remained stable over the third test period. Operations pursuant to block 317 may include determining, with a controller, whether the pressure detected by the pressure sensor during the third test period varied by less than a threshold pressure variance. If not (i.e., the pressure varied by more than the threshold pressure variance), the method proceeds to block 319, pursuant to which an alert notification is issued as described above, wherein the alert notification is configured to indicate that there is a leak through the check valve in the check valve assembly.
If the pressure remained stable during the third test period, however, the method may proceed to optional block 321, pursuant to which a pass notification may be issued. Operations pursuant to optional block 321 may include issuing a pass notification message with a controller, wherein the pass notification message is configured to cause a user interface on the controller or an external electronic device to indicate that the check valve within the check valve assembly is functioning properly. Following block 321 or if the block 321 is omitted, the method may proceed to block 323 and end.
“Circuitry”, as used in any embodiment herein, may comprise, for example, singly or in any combination, hardwired circuitry, programmable circuitry such as computer processors comprising one or more individual instruction processing cores, data machine circuitry, software and/or firmware that stores instructions executed by programmable circuitry.
Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
The terms and expressions which have been employed herein are used as terms of description and not of limitation, and there is no intention, in the use of such terms and expressions, of excluding any equivalents of the features shown and described (or portions thereof), and it is recognized that various modifications are possible within the scope of the claims. Accordingly, the claims are intended to cover all such equivalents. Various features, aspects, and embodiments have been described herein. The features, aspects, and embodiments are susceptible to combination with one another as well as to variation and modification, as will be understood by those having skill in the art. The present disclosure should, therefore, be considered to encompass such combinations, variations, and modifications.
This application claims priority to U.S. Provisional Application 63/139,481, filed 01-20-2021, which is incorporated herein by reference in its entirety.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US22/12956 | 1/19/2022 | WO |
Number | Date | Country | |
---|---|---|---|
63139481 | Jan 2021 | US |