The disclosure relates generally to valves, and more particularly, to gas valve assemblies.
Valves are commonly used in conjunction with many appliances for regulating the flow of fluid. For example, gas valves are often incorporated into gas-fired appliances to regulate the flow of gas to a combustion chamber or burner. Examples of such gas-fired appliances may include, but are not limited to, water heaters, furnaces, boilers, fireplace inserts, stoves, ovens, dryers, grills, deep fryers, or any other such device where gas control is desired. In such gas-fired appliances, the gas may be ignited by a pilot flame, electronic ignition source, or other ignition source, causing combustion of the gas at the burner element producing heat for the appliance. In many cases, in response to a control signal from a control device such as a thermostat or other controller, the gas valve may be moved between a closed position, which prevents gas flow, and an open position, which allows gas flow. In some instances, the gas valve may be a modulating gas valve, which allows gas to flow at one or more intermediate flow rates between the fully open position and the fully closed position.
This disclosure relates generally to valves, and more particularly, to gas valve assemblies. In one illustrative but non-limiting example, a valve assembly may be configured to communicate information from the valve assembly to a combustion appliance controller that is located remotely from the valve assembly. The combustion appliance controller may be associated with a combustion appliance for which the valve assembly is configured to control the flow of fuel. In some cases, the valve assembly may communicate with the combustion appliance controller through a wired or wireless communications interface that is compatible with a predetermined communication bus protocol.
In some cases, the valve assembly may include a valve body having an inlet port and an outlet port, with a fluid path extending between the inlet and outlet ports. One or more valves or valve sealing members of the valve assembly may be situated in or about the fluid path between the inlet port and the outlet port to open and close the fluid path. The one or more valves may be selectively moved between a closed position, which closes the path between the inlet port and the outlet port, and an opened position by one or more respective valve actuators secured relative to the valve body. The valve assembly may include one or more sensors in communication with the fluid path, where the sensors may be utilized in the valve assembly for sensing one or more parameters within the fluid path of the valve body. A controller of the valve assembly, secured relative to the valve body, may be in communication with the one or more sensors and may be configured to determine one or more valve assembly conditions based on the one or more sensed parameters. The controller may communicate with one or more devices located remotely from the valve assembly (e.g. a combustion appliance controller).
The controller of the valve assembly may, in some cases, communicate with the devices located remotely from the valve assembly through a wired or wireless communications interface compatible with a predetermined communication bus protocol. Through the communications interface, the controller may communicate the determined one or more of the valve assembly conditions to the devices located remotely from the valve assembly, or other similar or dissimilar information, as desired.
Alternatively, or in addition, the controller may be configured to receive one or more inputs from the device that is located remotely from the valve assembly. Illustratively, the received one or more inputs from the device that is located remotely from the valve assembly may include, but are not limited to, one or more of an acknowledgement of reception of one or more valve assembly conditions, a user setting, a valve command, and other similar or dissimilar inputs.
The preceding summary is provided to facilitate an understanding of some of the innovative features unique to the present disclosure and is not intended to be a full description. A full appreciation of the disclosure can be gained by taking the entire specification, claims, drawings, and abstract as a whole.
The disclosure may be more completely understood in consideration of the following detailed description of various illustrative embodiments in connection with the accompanying drawings, in which:
While the disclosure is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit aspects of the disclosure to the particular illustrative embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.
The following description should be read with reference to the drawings wherein like reference numerals indicate like elements throughout the several views. The detailed description and drawings show several illustrative embodiments which are meant to be illustrative of the claimed disclosure.
Gas valves may be added to fluid path systems supplying fuel and/or fluid to appliances (e.g., burners, etc.) or may be used individually or in different systems. In some instances, gas safety shutoff valves may be utilized as automatic redundant valves. Redundancy is achieved, and often times required by regulatory agencies, by placing at least two safety shutoff valves in series. The aforementioned redundant valves may be separate valves fitted together in the field and/or valves located together in a single valve body, these redundant valves are commonly referred to as double-block valves. In accordance with this disclosure, these and other gas valves may be fitted to include sensors and/or switches and/or other mechanical or electronic devices to assist in monitoring and/or analyzing the operation of the gas valve and/or connected appliance. The sensors and/or switches may be of the electromechanical type or the electronic type, or of other types of sensors and/or switches, as desired.
In some cases, a gas valve assembly may be configured to monitor and/or control various operations including, but not limited to, monitoring fluid flow and/or fluid consumption, electronic cycle counting, overpressure diagnostics, high gas pressure and low gas pressure detection, valve proving system tests, valve leakage tests, proof of valve closure tests, diagnostic communications, and/or any other suitable operation as desired.
Valve Assembly
The illustrative valve body 12 includes an inlet port 14, an outlet port 16 and a fluid path or fluid channel 18 extending between inlet port 14 and outlet port 16. Further, valve body 12 may include one or more gas valve ports 20 (e.g., a first valve port 20a and a second valve port 20b, shown in
Valve assembly 10 may further include one or more actuators for operating moving parts therein. For example, valve assembly 10 may have actuators including, but not limited to, one or more stepper motors 94 (shown as extending downward from bottom 12d of valve body 12 in
As shown, valve body 12 may include one or more sensor and electronics compartments 56, which in the illustrative embodiment, extend from back side 12e as depicted in
In the illustrative embodiment, the one or more fluid valve ports 20 may include first gas valve port 20a and second gas valve port 20b situated along and/or in communication with fluid channel 18. This is a double-block valve design. Within each gas valve port 20, a gas valve sealing member 22 may be situated in fluid channel 18 and may be positioned (e.g., concentrically or otherwise) about an axis, rotatable about the axis, longitudinally and axially translatable, rotationally translatable, and/or otherwise selectively movable between a first position (e.g., an open or closed position) and a second position (e.g., a closed or open position) within the corresponding valve port 20. Movement of the valve sealing member 22 may open and close valve port 20.
It is contemplated that valve sealing member 22 may include one or more of a valve disk 91, a valve stem 92 and/or valve seal 93 for sealing against a valve seat 32 situated in fluid channel 18, as best seen in
Valve actuator(s) 30 may be any type of actuator configured to operate valve sealing member 22 by actuating valve sealing member 22 from the closed position to an open position and then back to the closed position during each of a plurality of operation cycles during a lifetime of the gas valve assembly 10 or of actuator 30. In some cases, valve actuator 30 may be a solenoid actuator (e.g., a first valve actuator 30a and a second valve actuator 30b, as seen in
In some cases, valve assembly 10 may include a characterized port defined between inlet port 14 and outlet port 16. A characterized port may be any port (e.g., a fluid valve port 20 or other port or restriction through which fluid channel 18 may travel) at or across which an analysis may be performed on a fluid flowing therethrough. For example, if a flow resistance of a valve port 20 is known over a range of travel of the valve sealing member 22, the one of the one or more gas valve ports 20 may be considered the characterized port. As such, and in some cases, the characterized port may be a port 20 having valve sealing member 22 configured to be in an open position and in a closed position. Alternatively, or in addition, a characterized port may not correspond to a gas valve port 20 having valve sealing member 22. Rather, the characterized port may be any constriction or feature across which a pressure drop may be measured and/or a flow rate may be determined.
In some cases, the characterized port may be characterized at various flow rates to identify a relationship between a pressure drop across the characterized port and the flow rate through the fluid channel 18. In some cases, the pressure drop may be measured directly with one or more pressure sensors 42, 43, 44, and/or 38. In other cases, the pressure drop may be inferred from, for example, the current position of the valve member(s). These are just some examples. In some cases, the relationship may be stored in a memory 37, such as a RAM, ROM, EEPROM, other volatile or non-volatile memory, or any other suitable memory of the gas valve assembly 10, but this is not required.
In some cases, gas valve assembly 10 may include a flow module 28 for sensing one or more parameters of a fluid flowing through fluid channel 18, and in some cases, determining a measure related to a gas flow rate of the fluid through the fluid channel 18. In some instances, flow module 28 may include a pressure block or pressure sensor assembly 24, a temperature sensor 34, a valve member position sensor 48 and/or a valve controller 26, among other assemblies, sensors and systems for sensing, monitoring and/or analyzing parameters of a fluid flowing through fluid channel 18, such as can be seen in
It is contemplated that flow module 28 may utilize any type of sensor to facilitate determining a measure related to a flow rate of a fluid through fluid channel 18, such a pressure sensor, a flow sensor, a valve position sensor, and/or any other type of sensor, as desired. In one example, the flow module 28, which in some cases may be part of a valve controller 26, may be configured to monitor a differential pressure across a characterized port, and in some cases, a position of one or more valve sealing members 22 of the gas valve assembly 10. The information from monitoring may be utilized by the flow module 28 to determine and monitor the flow rate of fluid (liquid or gas) passing through the fluid channel 18. For example, the flow module 28 may determine a measure that is related to a gas flow rate through the fluid channel 18 based, at least in part, on the measure that is related to the pressure drop across the characterized port along with the pre-stored relationship in the memory 37. In some cases, the current position of one or more valve sealing members 22 of the gas valve assembly 10 may also be taken into account (e.g. is the valve 30% open, 50% open or 75% open).
In some instances, the flow module 28 may be configured to output the flow rate of fluid passing through the fluid channel 18 to a display or a remote device. In some cases, the flow module 28 may maintain a cumulative gas flow amount passing through the fluid channel 18 (e.g. over a time period), if desired. The measure related to a gas flow may include, but is not limited to, a measure of fuel consumption by a device or appliance that is connected to an output port 16 of the gas valve assembly 10.
It is contemplated that electronic valve controller or valve control block 26 (see,
The memory 37, which in some cases may be part of valve controller 26, may be configured to record data related to sensed pressures, sensed differential pressures, sensed temperatures, and/or other measures. The valve controller 26 may access this data, and in some cases, communicate (e.g., through a wired or wireless communication link 100) the data and/or analyses of the data to other systems (e.g., a system level or central building control) as seen in
In some instances, valve controller 26 may be considered a portion of flow module 28, flow module 28 may be considered part of valve controller 26, or the flow module 28 and valve controller 26 may be considered separate systems or devices. In some instances, valve controller 26 may be coupled relative to valve body 12 and one or more gas valve ports 20, where valve controller 26 may be configured to control a position (e.g., open or closed positions, including various open positions) of valve sealing member 22 within valve port 20. In some cases, the valve controller 26 may be coupled to pressure sensor assembly 24, temperature sensor 34, position sensor 48, and/or other sensors and assemblies, as desired.
In the illustrative embodiment of
In some instances, valve controller 26 may include a determining block, which may include a microcontroller 36 or the like, which may include or be in communication with a memory, such as a non-volatile memory 37. Alternatively, or in addition, determining block (e.g. microcontroller 36) may be coupled to or may be configured within valve control block or valve controller 26. Determining block may be configured to store and/or monitor one or more parameters, which may be used when determining a measure that is related to a fluid flow rate through fluid channel 18. Determining block (e.g. microcontroller 36) may be configured to use the stored and/or monitored parameters (e.g. the relationship between a pressure drop across a characterized port and the flow rate through the fluid channel 18) stored in the memory 37 to help determine a measure that is related to a fluid flow rate through fluid path or fluid channel 18.
Illustratively, determining block (e.g. microcontroller 36) may be configured to determine and/or monitor a measure (e.g., a flow rate of fluid passing through the characterized port or other similar or different measure, as desired) based, at least in part, on stored and/or monitored measures including, but not limited to, measures related to pressure drop across a characterized valve port or other pressure related measures upstream and downstream of the characterized valve port, a temperature of the fluid flowing through fluid channel 18, and/or a measure related to a current position of valve sealing member 22 at gas valve port 20 or the size of an opening at the characterized port. In one example, a determining block (e.g. microcontroller 36) may include non-volatile memory 37 that is configured to store opening curves of valve assembly 10, where the opening curves may characterize, at least in part, a flow rate as a function of a sensed axial position of valve sealing member 22, and a sensed differential pressure across a characterized valve port 20 or an otherwise determined pressure at or adjacent a characterized valve port 20 (e.g., knowing a set-point of an upstream pneumatic pressure reducing valve (PRV), as the set-point pressure of the PRV may be substantially equal to the pressure at an inlet of the characterized valve port), and may facilitate determining an instantaneous and/or cumulative fluid (e.g., fuel) flow in fluid channel 18 and/or consumption by an appliance in fluid communication with valve assembly 10.
It is contemplated that determining block (e.g. microcontroller 36) may continuously or non-continuously control, store, and/or monitor a position (e.g., an axial or rotary position or open/closed state or other position) of valve sealing member 22 within valve port 20, monitor a differential pressure across the characterized port, and/or monitor a temperature upstream and/or downstream of the characterized port. In addition, microcontroller 36 may continuously or non-continuously determine the flow rate of the fluid passing through the characterized port, where microcontroller 36 may be configured to record in its memory or in another location, an instantaneous flow rate of fluid flowing through the characterized port, a cumulative flow volume, and/or a determined instantaneous or cumulative (e.g., total) fluid consumption based on the positions of valve sealing member(s) 22 and determined flow rates at an instant of time or over a specified or desired time period. In addition, determining block (e.g. microcontroller 36) may be configured to report out the instantaneous flow rate, cumulative flow volume and/or total or cumulative fluid consumption over a given time period. Determining block (e.g. microcontroller 36) may report the instantaneous flow rate, cumulative flow rate, and/or total or cumulative consumption of the fluid flowing through the characterized port to system display 52 of an overall system controller 50 (e.g., a building/industrial automation system (BAS/IAS) controller), an appliance display 62 of an appliance controller 60 where the appliance may be configured to receive the flowing fluid, a display adjacent gas valve assembly 10, or any other display, device, controller and/or memory, as desired.
In some instances, valve controller 26 may include or be in communication with a valve actuator 30, which in conjunction with stepper motor 94 or other device is configured to position valve sealing member 22 in valve port 20. Valve actuator 30 and/or stepper motor 94 may be in communication with microcontroller 36 of valve controller 26, and microcontroller 36 may be configured to control, monitor, and/or record the position (e.g., axial position, radial position, etc.) of valve sealing member 22 within valve port 20 through valve actuator 30 (e.g., valve actuator 30 may be configured to effect the locking (e.g., valve actuator 30 OFF) or the unlocking (e.g., valve actuator 30 ON) of the valve sealing member 22 in a particular position) and stepper motor 94 (e.g., stepper motor 94 may be configured to adjust the position of valve sealing member 22 when it is not locked in a particular position), or through only stepper motor 94. Alternatively, or in addition, microcontroller 36 may be configured to monitor and record the position of valve sealing member 22 within valve port 20 through a connection with a position sensor 48 or through other means.
Microcontroller 36 may continuously or non-continuously monitor and record the position (e.g., axial position, radial position, etc.) of valve sealing member 22 within valve port 20 through valve actuator 30 and stepper motor 94, and microcontroller 36 may indicate the sensed and/or monitored position of valve sealing member 22 within valve port 20 as a prescribed position of valve sealing member 22. The prescribed position of valve sealing member 22 may be the position at which valve sealing member 22 was and/or is to be located, whereas a position of valve sealing member 22 sensed by position sensor system 48 may be considered an actual position of valve sealing member 22 within valve port 20.
In some instances, valve controller 26 may be configured to perform electronic operational cycle counting or may include an electronic counter configured to count each operational valve cycle of valve sealing members 22 during, for example, the lifetime of gas valve assembly 10 or during some other time period. In some cases, microprocessor 36 of valve controller 26 may be configured to monitor a total number of operational cycles (e.g., the number of times fuel valve sealing members 22 are operated from a closed position to an open position and back to a closed position) of valve ports 20 and measures related thereto. In some cases, microprocessor 36 may store such data in a non-volatile memory, such as memory 37, sometimes in a tamper proof manner, for record keeping and/or other purposes. Microprocessor 36 may monitor the number of cycles of valve sealing members 22 in one or more of several different manners. For example, microprocessor 36 may monitor the number of cycles of valve sealing members 22 by monitoring the number of times first main valve switch 72 and/or second main valve switch 74 are powered or, where one or more control signals may be provided to fuel valve actuator(s) 30 controlling when fuel valve actuator(s) 30 selectively moves (e.g., opens or closes) valve sealing member(s) 22, microprocessor 36 may monitor the one or more control signals.
Valve controller 26, in some cases, may monitor main valve switches 72, 74 by receiving signals directly from a device located remotely from valve assembly 10 on which main valve switches 72, 74 may be located (e.g. see
As an alternative to monitoring control signals, or in addition, microprocessor 36 may monitor the number of cycles of valve sealing members 22 by monitoring data from a position sensor 48. For example, microprocessor 36 of valve controller 26 may monitor position sensor 48 and record the number of times valve sealing members 22 are in an open position after being in a closed position and/or the number of times valve sealing members 22 are in a closed position after being in an open position and/or the number of times valve sealing members are operated from a close position to an open position and back to a closed position. These are just some examples. Further, if valve controller 26 is operating valve sealing members 22, valve controller 26 may monitor the number of operational cycles by counting its own control signals sent to valve actuators 30 and/or stepper motors 94.
The non-volatile memory 37, which may maintain and/or store the number of operational valve cycles, may be positioned directly on, or packaged with, valve body 12 (e.g., on or within memory of microcontroller 36) and/or may be accessible by valve controller 26. Such storage, placement and/or packaging of valve cycle data may allow for replacement of components in the overall system (e.g., an appliance control 60, etc.) without losing the valve cycle data. In an illustrative instance, valve cycle data may be securely stored, such that it may not be tampered with. For example, the valve cycle data may be stored the non-volatile memory 37 of valve controller 26 and the valve cycle data may be password protected.
Microcontroller 36 of valve assembly 10 may be configured to compare a count of a total number of operational cycles of valve sealing members 22 to a threshold number of operational cycles. In an instance where the counted number of operational cycles of the valve sealing member(s) 22t approaches, meets, or exceeds the threshold number of cycles, microcontroller 36 may initiate a warning and/or request a switch 69 in a limit string 67 to open and thus, remove or cut power to valve switches 72, 74 and fuel valve actuator(s) 30. Alternatively, or in addition, microcontroller 36 may send a signal to initiate an alarm and/or put the system in a safety lockout, or microcontroller 36 may be configured to take other action as desired. Illustratively, microcontroller 36 may be configured to prevent fuel valve actuator(s) 30 from allowing valve sealing member(s) 22 to open after the total number of operational cycles meets and/or exceeds the threshold number of operational cycles. In some instances, the threshold number of cycles may be related to the number of cycles for which valve assembly 10 is rated (e.g., a maximum number of cycles before failures might be expected, etc.) or related to any other benchmark value. In addition, microcontroller 36 may be configured to perform other diagnostics based on analyzing captured operational cycle data, where the other diagnostics may include number of cycles, time duration of cycles, and similar or different diagnostics, as desired.
Valve controller 26 may include an I/O or communications interface 110 with a communication protocol for transmitting data to and/or otherwise communicating with one or more remote device(s) that may be located remotely from valve assembly 10 (e.g., a combustion appliance including controller 60 located remotely from valve assembly 10). Communications interface 110 may be a wired or wireless communication interface, where the wired or wireless communication interface 110 may be configured to be compatible with a predetermined communication bus protocol or other communication protocol. A wired link may be low voltage (e.g. 24V, 5V, 3V, etc.), which may reduce certain issues related to line-voltage wiring schemes. Illustratively, communications interface 110, using the predetermined communication bus protocol or other communication protocol, may be configured to output and/or communicate one or more valve conditions, one or more measures related to valve conditions, one or more conditions related to a fluid flow through fluid channel 18, and/or one or more diagnostic parameters, conditions or events, to a device located adjacent or remote from valve assembly 10.
As discussed, valve controller 26 may be configured to determine one or more valve conditions based on one or more diagnostic parameters related to fluid channel 18 sensed by one or more sensor(s) (e.g., a pressure sensor, etc.) in communication with fluid channel 18. The diagnostic parameters may be determined by valve controller 26 and stored in a non-volatile memory 37 or other memory accessible by valve controller 26. The diagnostic parameters may include, but are not limited to, a total number of operational cycles, a fuel usage parameter, one or more fault history parameters, one or more user or factory or other setting parameters, self diagnostic check parameters, fault parameters and/or other similar or dissimilar parameters, as desired. The communicated valve condition(s) or measure(s) related to the valve condition(s) may be determined by valve controller 26 or one or more remote devices. Illustrative valve conditions and measures related to valve conditions may include, but are not limited to: high fuel pressure conditions, low fuel pressure conditions, valve closure conditions, valve leak conditions, safety event condition, and/or other similar or dissimilar valve conditions and/or outputs.
In addition to communication interface 110 being configured to output information to a device located adjacent or remote from valve assembly 10, communication interface 110 may be configured to receive one or more inputs from the remote device or an adjacently positioned device. Illustrative inputs may include, but are not limited to: an acknowledgement of reception of one or more of the valve conditions, a user setting, a system setting, a valve command, and/or other similar or dissimilar input.
In some instances, valve controller 26 may communicate through the I/O interface or communication interface 110 with a remotely located output block 46, where output block 46 may display and/or output a determined measure related to fluid flow rate through fluid channel 18, sometimes along with other data, information and controls sent from valve controller 26 (see, for example,
In an illustrative operation, valve controller 26 may be utilized in a method for communicating information between valve assembly 10 and a combustion appliance controller 60, where the combustion appliance controller 60 may be associated with a combustion appliance (e.g., a device separate from, and possibly remotely relative to valve assembly 10) for which valve assembly 10 may control a flow of fuel. The operation may include sensing, with one or more sensor (e.g., pressure sensor assembly 24), one or more sensed parameters within fluid channel 18 of valve assembly 10. The sensed parameter may be stored in a non-volatile memory 37, or other memory, of valve controller 26. Valve controller 26 may determine one or more valve conditions (e.g., a safety event condition) based on the one or more sensed parameters. For example, valve controller 26 may compare the one or more sensed parameters to a threshold parameter to determine one or more valve conditions. If one or more valve conditions have been determined, valve controller 26 may be configured to send information that may be related to the one or more determined valve conditions from valve assembly 10 to the combustion appliance controller 60 (or other controller or device) across a communication link or bus 100 connected to a communications interface 110.
In one example, upon receiving one or more determined valve conditions, such as a safety event condition, combustion appliance controller 60 (or other controller or device) may be configured to open safety switch 70, such that power to a valve control signal that is coupled to one or more valve actuators 30 is cut, thereby automatically closing one or more valve ports 20 (e.g., closing valve sealing member(s) 22 of valve port(s) 20). In some cases, safety switch 70 may be controlled by an algorithm in combustion appliance controller 60, where an output of the algorithm is affected by information passed via the communication link 100. Additionally, or in the alternative, other feedback signals may affect an output of the algorithm, where the other feedback signals may or may not be passed via the communication link 100 and may or may not originate from valve assembly 10.
In other illustrative operations, a low gas pressure/high gas pressure event may be reported from valve controller 26 to combustion appliance controller 60. In response to receiving a reported low gas pressure/high gas pressure event, combustion appliance controller 60 may be configured to open safety switch 70. Further, in cases where a proof of closure event is reported to combustion appliance controller 60 prior to ignition of the combustion appliance, an ignition sequence may not be started. In certain other instances where a Valve Proving System (VPS) sequence test is being performed, a combustion appliance controller 60 may use reported results of the VPS sequence test to make an evaluation. For example, if in the evaluation of the VPS test it were determined that a valve was leaking, the appliance controller 60 might be programmed to open safety switch 70, to initiate a safety lockout, to initiate an alarm, and/or to take any other similar or dissimilar measure.
In other scenarios, valve assembly 10 may be used as a control valve and in that case, valve controller 26 may send a signal to combustion appliance controller 60 indicative of a valve position, and combustions appliance controller 60 may respond accordingly. These other scenarios, for example, may be applied in parallel positioning system applications, low fire switch applications, auxiliary switch applications, etc. Additionally, it is contemplated that valve controller 26 may interact with remote devices in other similar and dissimilar manners within the spirit of this disclosure.
Pressure block or pressure sensor assembly 24 may be included in flow module 28, as seen in
In some cases, pressure sensor assembly 24 may include a differential pressure sensor 38 for measuring a differential pressure drop across a characterized valve port 20, or across a different characterized port, as seen in
Alternatively, or in addition, an illustrative pressure sensor assembly 24 may include one or more first pressure sensors 42 upstream of a characterized valve port and one or more second pressure sensors 43 downstream of the characterized valve port, where first and second pressure sensors 42, 43 may be in fluid communication with fluid channel 18 and may be configured to sense one or more measures related to a pressure upstream and a pressure downstream, respectively, of the characterized valve port, as seen in
Pressure sensors 42, 43, 44 may be configured to send each of the sensed measure(s) directly to microcontroller 36. Microcontroller 36 may be configured to save the sensed measures and/or related information to a non-volatile memory 37, and may perform one or more analyses on the received sensed measures. For example, microcontroller 36, which may be a portion of flow module 28 and/or valve controller 26, may determine a measure that is related to a fluid flow rate through the fluid path based, at least in part, on the received sensed measures related to pressure upstream of the characterized port and on the received sensed measures related to pressure downstream of the characterized port.
Where a valve assembly 10 includes one or more valve ports 20, pressure sensor assembly 24 may include first pressure sensor 42 positioned upstream of first valve port 20a at or downstream of inlet port 14, as seen in
In some instances, such arrangements of pressure sensors 38, 42, 43, 44 within valve assembly 10, along with the connection between valve controller 26 and pressure sensors 38, 42, 43, 44 may be used to emulate functions of high gas pressure (HGP) and low gas pressure (LGP) switches, which traditionally require wires and further housings extending to and from and/or attached to valve body 12. When the electronics and elements of valve assembly 10 are configured to emulate LGP/HGP switches, gas-valve wiring connections and interactions may be at least partially avoided, eliminated or simplified. In some instances, such configuration of valve controller 26 and pressure sensors 38, 42, 43, 44 may reduce manual operations (e.g., manually adjusting a mechanical spring or other device of conventional high gas pressure (HGP) and low gas pressure (LGP) switches), and allow for a more precise fitting with the electronics of valve assembly 10.
In some cases, pressure sensor assembly 24 may include one or more absolute pressure sensors 54 in communication with microcontroller 36. Absolute pressure sensor 54 may sense an atmospheric pressure adjacent gas valve assembly 10, and may be configured to communicate and transfer data related to the sensed atmospheric pressure to microcontroller 36. Microcontroller 36 may take into account the atmospheric pressure from the absolute pressure sensor 54 when determining the flow rate of fluid flowing through the characterized port and/or an estimate of fuel consumption by an attached appliance and/or when determining threshold values. Other sensors may be included in valve assembly 10, for example, one other type of sensor may be a barometric pressure sensor.
As discussed, valve assembly 10 and the flow module 28 thereof may include temperature sensor(s) 34, as seen in
Flow module 28 of valve assembly 10 may further include a position sensor system that may be configured to continuously or discontinuously sense at least one or more of an axial position, a rotary position, and/or a radial position, of valve sealing member 22 within or about fluid valve port 20. In some cases, position sensor system may include more than one position sensors 48, such that each position sensor 48 may monitor a sub-range of a valve's total travel. Moreover, position sensor system may be utilized as a proof of closure switch system. Position sensor(s) 48 of the position sensor system may be situated or positioned in valve body 12 at or about a valve port 20. For example, and in some instances, position sensor(s) 48 may be fluidly isolated from fluid channel 18 (e.g., fluidly isolated from fluid channel 18 by valve body 12), and radially spaced from an axis upon which a valve sealing member(s) 22 may axially and/or rotationally translate between a closed position and an open position, as seen in
An illustrative gas valve assembly 10 may include a first valve port 20a and a second valve port 20b (see
As discussed above, position sensor 48 may be configured to detect a measure that is related to whether valve sealing member 22 is in an open or closed position and/or a measure related to an intermediate position of valve sealing member 22 within fluid valve port 20. In one example, position sensor(s) 48 may be configured to provide a proof of closure (POC) sensor(s) for valve port(s) 20 (e.g., first valve port 20a and/or second valve port 20b).
Where valve sealing member(s) 22 have a range of travel (e.g., rotationally and/or axially) within valve port(s) 20, position sensor(s) 48 may be configured to sense a current position of valve sealing member(s) 22 anywhere along the range of travel of valve sealing member(s) 22. Position sensor 48 may then send (e.g., through electronic or other communication) sensed positioning data of the measure related to the position of valve sealing member 22 to determining block and/or microcontroller 36 and/or a non-volatile memory 37 of valve controller 26 and/or flow module 28, where microcontroller 36 may be configured to monitor the axial position of valve sealing member 22 within valve port 20 through position sensor system 48.
In some instances, valve controller 26 may include an electronic circuit board and a wired or wireless communication link 100 may facilitate communication between position sensor(s) 48 and the electronic circuit board or other device of valve controller 26. Valve controller 26 may be configured to further pass on positioning information to remote devices through communication lines (e.g., communication link 100) and/or display positioning data of valve sealing member 22 on one or more displays 76 attached to valve assembly 10 and/or remote devices, as seen in
In some instances, the position sensor system may include one or more switches 64 (e.g., a first switch 64a and a second switch 64b, where switch(es) 64 may be or may include relays or other switch types such as FETs, TRIACS, etc.) having one or more switched signal paths 66 and one or more control inputs 68 (e.g., a first control input 68a and a second control input 68b), as seen in
Illustratively, valve sealing member(s) 22 may include a sensor element 80, and position sensor(s) 48 may include one or more transducer or field sensors 82. For example, valve sealing member(s) 22 may include a sensor element 80 (e.g., a magnet when using a field sensor 82, a ferrous core when using a linear variable differential transformer (LVDT) 84, or other sense element, and/or similar or dissimilar indicators) secured relative to and translatable with valve sealing member(s) 22. Position sensor(s) 48 may include one or more field sensors 82 (e.g., magnetic field sensors, a LVDT 84, Hall Effect sensors or other similar or dissimilar sensors), as seen in
In some cases, a strain gauge 86, as depicted in
As may be inferred from the disclosure, position sensor 48 may in some instances operate by detecting a position of a valve sealing member 22 and/or optionally valve stem 92 or the like within a valve assembly 10 having a valve body 12, where valve sealing member 22 may be translatable with respect to valve port 20 of valve body 12 along a translation or longitudinal axis “A” within a valve port 20. In some cases, sensor element 80, affixed relative to valve sealing member 22, may be positioned within the interior of valve body 12 and may optionally fluidly communicate with fluid channel 18; however, position sensor 48 may be isolated from fluid channel 18 and/or positioned exterior to valve body 12. In an illustrative embodiment, valve sealing member 22 may be positioned at a first position within an interior of valve port 20 along translation axis A. The first position of the valve sealing member 22 may be sensed with position sensor 48 by sensing a location of a sensor element 80 secured relative to valve sealing member 22 with position sensor 48. Then, position sensor 48 may automatically or upon request and/or continuously or discontinuously, send the sensed location and/or open or closed state of valve sealing member 22 to the valve controller 26.
It is contemplated that valve controller 26 may electronically calibrate the closed position of valve sealing member 22 and/or valve stem 92. Such a calibration may store the position of the valve sealing member 22 and/or valve stem 92 when the valve sealing member 22 and/or valve stem 92 is in a known closed position (e.g. such as during installation of the valve assembly 10). During subsequent operation, the position of the valve sealing member 22 and/or valve stem 92 can be compared to the stored position to determine if the valve sealing member 22 and/or valve stem 92 is in the closed position. A similar approach may be used to electronically calibrate other positions of the valve sealing member 22 and/or valve stem 92 (e.g. fully open position, or some intermediate position), as desired.
Fuel Rate Monitor
In operation, valve assembly 10 may be utilized to measure a flow rate of fluid flowing through a characterized port (e.g., valve port 20 or other port). As discussed above, the measuring method may include utilizing a microcontroller 36 or the like to monitor (e.g., monitoring sensed measures, monitoring control signals, set-points, and user settings, etc.) a differential pressure across a characterized valve port which may be continuously or discontinuously monitored by pressure sensor assembly 24, monitoring (e.g., monitoring sensed/feedback measures, monitoring control signals, set-points and user settings, etc.) a position of a valve sealing member 22 within the characterized valve port which may be continuously or discontinuously monitored by position sensor 48, and/or determining a flow rate of the fluid flowing through the characterized port with the microcontroller 36 from the monitored differential pressure, and in some cases, the monitored position of the valve sealing member 22.
To facilitate determining the flow rate of fluid flowing through the characterized port, microcontroller 36 may utilize a valve's opening curves stored in a memory 37. In some cases, the characterized port may be characterized at various flow rates, across various open positions, to identify a relationship between a measured pressure drop across the characterized port and the flow rate through the gas valve. Of course, when the valve only switches between a fully closed position and a fully open position, the characterized port need not be characterized over various open positions; just over the fully open position. In some cases, the relationship may be stored in a non-volatile memory 37 of the gas valve assembly 10.
Through the use of valve opening curves and/or other similar or different data and/or algorithms, microcontroller 36 may determine a flow rate for any combination of sensed pressure drop and sensed valve sealing member 22 positions. As further detailed herein, it is contemplated that temperature, atmospheric pressure, inlet pressure, outlet pressure and/or other sensed parameters may be used to help increase the accuracy of the determined flow rate, if desired.
Microcontroller 36 may be configured to continuously monitor the differential pressure across the characterized port, and in some cases continuously monitor the position of the valve sealing member 22, in such a manner as to be configured to continuously determine the flow rate of the fluid flowing through the valve port. Continuously monitoring the differential pressure(s) and in some cases the positioning of the valve sealing member 22, and continuously determining the flow rate of fluid flowing through the characterized port, may facilitate the microcontroller 36 continuously tracking, reporting, and/or outputting an instantaneous flow rate of the fluid flowing through the characterized port and/or to continuously tracking, reporting, and outputting a cumulative flow volume of the fluid (integral of the flow rate over time) flowing through the characterized port over a given period of time. An average flow rate of fluid flowing through the characterized port may be determined from the instantaneous flow rates of the fluid over time. In addition, microcontroller 36 may send one or more of the tracked and reported instantaneous flow rates and/or the cumulative flow volume from microcontroller 36 to a system controller 50 and/or an appliance controller 60 via a communication link 100, if desired, and the reported instantaneous flow rates and/or the cumulative flow volume and/or other data may be read out at the local valve controller display 76, appliance display 62 and/or system display 52.
In addition to taking into consideration differential pressure across a characterized port, and in some cases the positioning of valve sealing member 22 (e.g. when intermediate open positions are used), microcontroller 36 may consider measures from one or more other sensors that sense characteristics within or about fluid channel 18 or other resources. For example, microcontroller 36 may consider one or more measures related to a temperature in fluid channel 18 sensed by temperature sensor(s) 34 (e.g., temperature may be used to correct/calculate a fluid flow rate), one or more measures related to an absolute pressure about fluid channel 18 sensed by an absolute pressure sensor 54 (e.g., absolute pressure may be used to correct/calculate flow rate of a fluid), and/or other measures sensed by other sensors or received from other sources, as desired.
It is also contemplated that microcontroller 36 may take into consideration the altitude of the fluid channel 18 with respect to sea level or another baseline measure when determining a flow rate of fluid through fluid channel 18. Altitude may be continuously or discontinuously sensed by an altimeter on or adjacent or remotely located from valve assembly 10 and/or an altitude may be preset within microcontroller 36 or entered at any time prior to or during or after installation of the valve assembly 10. Also, it is contemplated that a Wobbe index associated with the fluid flowing through fluid channel 18 may be stored and utilized. Utilization of a Wobbe index may facilitate reporting out of fluid flow rates through fluid channel 18 by microcontroller 36 in units of energy per time (e.g., BTU/hour for indicating fuel consumption), rather than reporting a volumetric or mass flow measure. Such consideration of further characteristics (including characteristics not listed) related to fluid channel 18 may allow for determining more accurate flow rate measures of the fluid flowing through fluid channel 18, as the utilizing of further characteristics may have the ability to reduce assumptions in known flow equations/algorithms utilized by microcontroller 36.
Electronic Cycle Counting
In operation, gas valve assembly 10 may monitor the number of operational valve cycles experienced by one or more valve sealing member 22 over a period of time (such as the lifetime of gas valve assembly 10). In one example, valve controller 26 of valve assembly 10 may monitor a valve sealing member 22 of at least one of the valve ports 20 being opened from a closed position and/or being returned to the closed position to complete an operational cycle, where a plurality of operational cycles may be completed during the lifetime of the valve assembly 10. In one example, a count of the number of operational cycles may be maintained and/or stored in a non-volatile memory 37, or other memory, of valve controller 26 (e.g., microcontroller 36 or other device) of valve assembly 10 in a tamper proof manner. Alternatively, and to detect an operation cycle, valve controller 26 of valve assembly 10 may monitor a valve sealing member 22 moving from an open position to a closed position and back to an open position, or any other cycle involving movement of valve sealing member 22 and/or other parts, portions or devices of valve assembly 10. In some cases, valve controller 26 may monitor valve actuators 30, positions of valve sealing member 22 and/or signals to valve actuators 30, and/or other indicators to monitor the number of operational valve cycles experienced by each valve port 20 over a period of time, such as the lifetime of valve assembly 10.
The memory (e.g., non-volatile memory 37) of valve controller 26 storing the electronic operational valve cycle counting system may also be programmed with one or more number of cycles for which valve assembly 10 may be rated (e.g., one or more threshold numbers of operational valve cycles). Valve controller 26 may be configured to retrieve the one or more threshold numbers of operational valve cycles from the non-volatile memory 37, and compare the count of the number of operational valve cycles to the one or more threshold numbers of operational valve cycles. If desired, valve assembly 10 may be configured to take action if a counted number of cycles meets and/or exceeds one of the one or more threshold numbers of valve cycles. Taking action may include, for example, after a first threshold number of operational cycles has been surpassed, initiating a warning or an alarm 78 or sending for a maintenance call, and after a second threshold number of operational cycles has been surpassed, shutting the system down by removing power from main valve switches 72, 74, preventing valve actuator(s) 30 from selectively moving valve sealing member(s) 22 (e.g., preventing the opening of valve port(s) 20), and/or any other desired action.
As the operational valve cycle data may be electronically stored in memory (e.g., non-volatile memory 37) of microcontroller 36, the valve cycle data (e.g., a total number of operational cycles, etc.) may be communicated and/or outputted to one or more remote devices, such as system controller 50 and/or appliance controller 60, via a wired or wireless communication interface including or connected to a bus or link 100 or other link, where the operational valve cycle data (e.g., total number of operational cycles, etc.) may be displayed on displays 52, 62 or other display interfaces. Alternatively, or in addition, the operational valve cycle data may be displayed on a handheld device and/or a display at or adjacent valve assembly 10 (e.g., a touch-screen on valve body 12) or on another display or device, as desired.
In addition, microcontroller 36 may be configured to continuously or discontinuously monitor and/or analyze the duration and number of cycles, time between half cycles (time between the open and closing of the valve), and/or other parameters to help determine any abnormal patterns that would be indicative of system or component malfunction and/or failures, and/or other normal or abnormal patterns. In some further illustrative instances, the electronic counter may take the place of an electronic clock on the system, such that the operational cycle count may be utilized as a digital time stamp when storing information on various events detected by valve controller 26, such as diagnostic, warning and/or error messages and the like.
Overpressure Diagnostics
Valve assembly 10 may be configured to detect, report, and/or automatically act upon an overpressure event occurrence at, within, and/or on valve assembly 10. An overpressure event may be an event where pressure at the input port 14, output port 16, or within fluid channel 18 of valve assembly 10 is greater than an overpressure threshold value (e.g., a valve pressure rating value, a pressure value below which the specifications of the valve assembly 10 are guaranteed, a pressure value below which it is guaranteed no damage will occur to the valve assembly 10 from pressure, a pressure value between the pressure value below which the specification of valve assembly 10 is guaranteed and the pressure value below which it is guaranteed no damage will occur to the valve assembly 10 from pressure, etc.), where the overpressure may cause damage to the valve assembly 10. Acting on such sensed overpressure events may, for example, take a valve offline until the valve can be inspected, enable more accurate system diagnostics under some circumstances, optimize maintenance scheduling, minimizing service and down time, and/or increasing safety levels with respect to valve assembly 10. These are just some examples.
The overpressure threshold value may be related to a valve pressure rating value of valve assembly 10 and/or valve ports 20 therein. The overpressure threshold value may be substantially equal to or less than or greater than the valve pressure rating value of valve assembly 10. A valve pressure rating value may be any pressure value assigned to valve assembly 10. For example, a valve pressure rating value may be equal to or less than a pressure value at which valve assembly 10 or valve ports 20 within valve assembly 10 is or are expected to fail or become otherwise damaged.
Similarly, a pressure sensor 38, 42, 43, 44 of pressure sensor assembly 24, which may continuously monitor pressure levels of fluid flowing through fluid channel 18, may have a sensor pressure rating value. In an illustrative instance, the sensor pressure rating value of at least one of the pressure sensors 38, 42, 43, 44 may be equal to or substantially greater than the valve pressure rating of valve assembly 10. In some cases, there may be multiple overpressure threshold values, which may indicate different levels of severity of an overpressure event, and/or may be useful for other purposes or may indicate different thresholds at different locations along the fluid channel 18 (e.g., at the input and output of fluid channel 18) where pressure levels are being sensed and/or monitored.
Valve controller 26 of valve assembly 10 may be utilized to facilitate overpressure diagnostics. Valve controller 26, which may be secured relative to valve body 12 and in communication with pressure sensor assembly 24, may be configured to compare a measure related to a sensed pressure of fluid (e.g., fuel, etc.) flowing through fluid channel 18 of valve body 12 with an overpressure threshold value stored in non-volatile memory 37 or other memory accessible by valve controller 26. The sensed pressure may be sensed by pressure sensor assembly 24 at any position along fluid channel or path 18; for example, a pressure may be sensed upstream of one or more valve port(s) 20 (e.g., first and/or second valve port 20a, 20b) or downstream of one or more valve port 20 (e.g., first and/or second valve port 20a, 20b) or if there are two or more valve ports 20 (e.g., first valve port 20a and second valve port 20b), then in between, upstream or downstream valve ports 20. Pressure sensor assembly 24 may be configured to utilize one or more pressure sensors 38, 42, 43, 44 that may facilitate continuously sensing a pressure in fluid channel 18 at one or more desired locations (e.g., upstream of a first valve port 20a) and then automatically and repeatedly, or continuously, communicate the sensed pressure at the desired location(s) to valve controller 26.
Valve controller 26 may be configured to determine if the measure related to the sensed pressure exceeds or surpasses the overpressure threshold value. If the measure does surpass the overpressure threshold value, the valve controller 26 may be configured to provide a predetermined output signal indicating that an over pressure event has occurred. The predetermined output signal may be provided to a remote device (e.g. 50 or 60) and/or an audible and/or visual alarm may be displayed on a remote display (e.g., 52, 62) or a display located adjacent and/or on valve assembly 10. Alternatively, or in addition, the predetermined output signal may, indirectly or directly, cause valve actuator(s) 30 to close valve port(s) 20 (e.g., by closing valve sealing member(s) 22 therein) and/or cause valve controller 26 to store the over pressure event in a non-volatile memory 37 or other memory of valve controller 26 and/or other device. The predetermined output signal may also, indirectly or directly, cause valve controller 26 to store one or more of a time stamp of the overpressure event, a level of the sensed pressure causing the overpressure event, a duration of the overpressure event, a cumulative number of overpressure events, classification identifier of the overpressure event, any parameter calculated from a series of measured pressure readings, and/or other related or unrelated data.
The stored data or information related to the overpressure events may be processed and/or analyzed by valve controller 26 and/or transferred to other devices. Processing the stored information may include, but is not limited to, determining a most likely cause of an over pressure event, classifying the event by most likely cause, estimating the severity of the event, calculating the cumulative number of over pressure events, comparing any of the stored information (e.g., level of the sensed pressure causing the event, time stamp of an event, duration of an event, number of events, severity of an event, etc.), which may be stored in valve controller 26, to one or more threshold values that may also be stored in valve controller 26 or at one or more other locations, notifying a user by visual or audible means or alarm, running self checking diagnostics to evaluate key performance characteristics (e.g., seat leakage testing through a VPS test, regulator performance etc.), indirectly or directly closing valve port(s) 20 via valve actuator(s) 30, and/or sending a signal to trigger some system level overpressure countermeasure in response to a measure surpassing a respective threshold value. Additionally, all or some or none of the actions and/or results of the processing may be communicated to users or other devices over communication link 100, an I/O interface, and/or any other communication mechanism.
High Gas Pressure and Low Gas Pressure Detection
Valve assembly 10 may be configured to monitor the occurrence of pressure events along a fluid channel 18. Valve assembly 10 may be configured as an electronic module for detecting low gas pressure (LGP) upstream of first valve port 20a and high gas pressure (HGP) downstream of the first valve port 20a and/or second valve port 20b or another valve port 20 depending on which valve port 20 is the most downstream valve port 20 in valve assembly 10. By placing a pressure sensor 42 upstream of the first valve port 20 to sense an inlet gas pressure and/or placing a pressure sensor 42 downstream of the second valve port 20 to sense an outlet gas pressure and/or placing a pressure sensor 42 in an intermediate volume 19 between a first valve port 20a and a second valve port 20b to sense an intermediate volume gas pressure, the electronics of valve assembly 10 may be configured to electronically emulate and/or perform electromechanical or mechanical HGP/LGP switch functions, such that the functions of electromechanical or mechanical HGP/LGP switches may be directly integrated in valve assembly 10. At a minimum, a single pressure sensor is needed to perform both HGP/LGP switch functions in accordance with this disclosure. The integration of the switch functions may facilitate internalizing wiring connections within valve body 12, and may result in size and cost savings due, at least in part, to valve and switch functions sharing a common housing, while providing other solutions and benefits as would be generally realized.
In an illustrative instance, one or more first pressure sensors 42, positioned upstream of first valve port 20a, may continuously or discontinuously sense an inlet pressure in fluid channel 18 and may be in communication with valve controller 26. Valve controller 26 may be configured to continuously or discontinuously compare a first measure (e.g., inlet pressure) or data related thereto, which may be stored in memory (e.g., non-volatile memory 37) of valve controller 26, that at least tracks a measure related to a sensed pressure sensed by the one or more first pressure sensors 42 in valve body 12 upstream of first valve port 20a, with a first pressure threshold programmed into and stored in memory (e.g., non-volatile memory 37) of valve controller 26. Valve controller 26 may then provide a predetermined first output signal if the first measure surpasses the first pressure threshold, where the first output signal may result in first valve actuator 30a closing first valve port 20a and second valve actuator 30b closing second valve port 20b.
In an illustrative example, valve controller 26 may compare the first measure to a low gas pressure threshold (e.g., a first pressure threshold) and if the first measure drops below or is less than the low gas pressure threshold, the first measure may be said to have surpassed the low pressure threshold, and valve controller 26 may provide the predetermined first output signal. Alternatively, or in addition, valve controller 26 may be configured to compare the first measure with a second pressure threshold (e.g., a high gas pressure threshold) programmed into and stored in valve controller 26, where valve controller 26 may be configured to provide a predetermined second output signal if the first measure surpasses the second pressure threshold (e.g., if the first measure is greater than or more than the high pressure threshold). The first and second pressure thresholds may be automatically, manually through a user interface, locally (e.g., on a valve assembly's 10 own display/user interface 76), and/or remotely (e.g., via an appliance or system level display 52, 62 and communication bus 100) determined and programmed during setup. In some cases, the first and second pressure thresholds may be selectable from the American National Standards Institute (ANSI) standards and/or European (EN) standards. For example, a first or high gas pressure threshold may be 125% of a first pressure run and a second or low gas pressure threshold may be 75% of a first pressure run. The predetermined first and second pressure output signal may indicate a pressure event has occurred and/or other data or information related to the pressure event.
Likewise, one or more second pressure sensors 43 positioned downstream of first valve port 20a and/or second valve port 20b may continuously or discontinuously sense outlet pressures in fluid channel 18 and may be in communication with valve controller 26. Valve controller 26 may be configured to continuously or discontinuously compare a second measure (e.g., outlet pressure) or data related thereto, which may be stored in memory (e.g., non-volatile memory 37) of valve controller 26, that at least tracks a sensed pressure in valve body 12 downstream of second valve port 20b with a third pressure threshold or other pressure threshold programmed into and stored in memory (e.g., non-volatile memory 37) of valve controller 26. Valve controller 26 may then provide a predetermined third output signal if the second measure surpasses the third pressure threshold, where the third output signal may result in first valve actuator 30a closing first valve port 20a and second valve actuator 30b closing second valve port 20b.
In an illustrative example, valve controller 26 may compare the second measure to a high gas pressure threshold and if the second measure rises above the high gas pressure threshold, the second measure may be said to have surpassed the high gas pressure threshold and valve controller 26 may provide the predetermined third output signal. Alternatively, or in addition, valve controller 26 may be configured to compare the second measure with a fourth pressure threshold (e.g., a low pressure threshold), or other pressure threshold, programmed into and stored in valve controller 26, where valve controller 26 may be configured to provide a predetermined fourth output signal if the second measure surpasses the fourth pressure threshold. The predetermined third and fourth output signals may indicate a pressure event has occurred and/or other data or information related to the pressure event.
In a similar manner, one or more third pressure sensors 44 positioned downstream of first valve port 20a and upstream of second valve port 20b may continuously or discontinuously sense an intermediate pressure, or a measure related thereto, in intermediate volume 19 of fluid channel 18 and may be in communication with valve controller 26. Valve controller 26 may be configured to continuously or discontinuously compare a third measure (e.g., intermediate pressure) or data related thereto, which may be stored in memory (e.g., non-volatile memory 37) of valve controller 26 with a fifth pressure threshold or other pressure threshold programmed into and stored in memory (e.g., non-volatile memory 37) of valve controller 26. Valve controller 26 may then provide a predetermined fifth output signal if the third measure surpasses the fifth pressure threshold, where the fifth output signal may result in first valve actuator 30a closing first valve port 20a and second valve actuator 30b closing second valve port 20b.
In an illustrative example, valve controller 26 may compare the third measure to a high gas pressure threshold and if the third measure rises above the high gas pressure threshold, valve controller 26 may provide the predetermined fifth output signal. Alternatively, or in addition, valve controller 26 may be configured to compare the third measure with a sixth pressure threshold (e.g. a low pressure threshold), or other pressure threshold, programmed into and stored in valve controller 26, where valve controller 26 may be configured to provide a predetermined sixth output signal if the third measure surpasses the sixth pressure threshold. The predetermined fifth and sixth output signals may indicate a pressure event has occurred and/or other data or information related to the pressure event.
As discussed above, the HGP/LGP testing may be performed with one or more pressure sensors. The numbering and positioning of the pressure sensors (e.g., first pressure sensor 42—upstream, second pressure sensor 43—downstream, third pressure sensor 44—intermediate, etc.) is for illustrative purposes only. For example, there may be a single pressure sensor in valve assembly 10, where the single pressure sensor is located upstream of the valve port(s) 20, downstream of the valve port(s) 20 or intermediate the valve ports 20. Further, each pressure sensor 38, 42, 43, 44 included in valve assembly 10 may be associated with one or more pressure threshold value and those one or more pressure threshold values may be similar to or different from one or more pressure threshold values associated with any other pressure sensor.
Valve controller 26 may include software to effect methods of operation disclosed herein. In some illustrative instances, software filtering techniques may be utilized to eliminate transient pressure readings from causing a false opening of a switch 69 in the limit string 67, for example, a switch in series with safety switch 70, which may help prevent nuisance valve port(s) 20 closures. Safety switch 70 may be wired in series between main valve switches 72, 74 and the limit string 67, for example. In such a configuration, if valve controller 26 detects a pressure event, valve controller 26 may initiate a series of actions resulting in a switch 69 in the limit string 67 opening, which may remove power from main valve switches 72, 74, resulting in valve ports 20 closing. The software may help improve robustness of the system by allowing the software to be intelligent about when it monitors the sensor states and what action is taken in response.
As the functions of HGP/LGP switches may now be emulated by sensors and electronics, and the output may no longer only be a simple “switch open” or “switch closed”, but rather, in addition or alternatively, an actual readable pressure value or value related thereto, it may be advantageous to configure valve controller 26 to communicate this data to a remote device (e.g., a building automation system or system controller 50, an appliance controller 60, etc.) or display 52, 62. System display 52 or appliance display 62 may be configured to show threshold pressures along with actual sensed pressures during operation to show a user how much margin there is until a pressure event trip point. In addition, valve controller 26 may be configured to communicate to system controller 50 or appliance controller 60 that a pressure event has occurred, which may result in an indicator being displayed on displays 52, 62. Such communication may take place over a wired or wireless bus or link 100, where the bus may be configured to carry data to and from valve assembly 10. In some cases, low and high pressure thresholds may be inputted by an operator of valve assembly 10 and may be downloaded or otherwise programmed into valve controller 26.
Note, first, second, third, fourth, fifth and sixth pressure thresholds and output signals are merely some illustrative examples, and there may be any number of pressure thresholds and output signals with respect to each provided pressure sensor 42, 43, 44 (or 38), as desired. Further, with respect to a first and second pressure threshold related to a single valve port 20 and/or pressure sensor 42, 43, 44 (or 38), one of the first or second pressure threshold may relate to a high or low pressure threshold and the other pressure threshold may relate to the other of the high and low pressure thresholds. In addition, each of the one or more first pressure sensors 42, each of the one or more second pressure sensors 43 and each of the third pressure sensors 44, respectively, may include pressure sensors each having different or the same pressure sub-ranges. For example, where two third pressure sensors 44 are positioned downstream of the first valve port 20a and upstream of second valve port 20b, one of the two third pressure sensors 44 may have a first pressure sensing sub-range over which it may sense pressures and the other of the two third pressure sensors 44 may have a second pressure sensing sub-range over which it may sense pressures, but this is not required.
Although valve controller 26 may be configured to provide the above-mentioned first, second, third, fourth, fifth, and/or sixth output signals when the first, second, or third sensed measure related to each valve port 20 surpasses one of the pressure threshold stored in valve controller 26 to indicate a pressure event has occurred, valve controller 26 may be configured to not provide the predetermined first, second, third, fourth, fifth, or sixth output signal during at least one time period, even if any of the first, second, or third measures surpass a respective pressure threshold. For example, valve controller 26 may be programmed to not provide the predetermined output signal where the one time period is associated with a status of the first and/or second valve actuators 30a, 30b (e.g., at or around when the first and/or second valve actuator 30a, 30b are being actuated, etc.). Actuating the first and/or second valve actuator 30a, 30b may cause pressure transients, which could result in false HGP or LGP events. In some, but not all cases, for example, microcontroller 36 may be taught to ignore sensed pressures when valve port(s) 20 is/are closed, as the outlet pressure may be close to zero and likely below any threshold value and a sensed pressure in the intermediate volume 19 may be in a range from around zero to the inlet pressure.
Although typical safety valve assemblies may have sensed HGP downstream of a second valve port 20b and LGP upstream of a first valve port 20a, utilizing sensors of pressure sensor assembly 24 may allow pressure to be monitored at a single pressure sensor positioned at a single location (e.g. upstream of the first valve, intermediate the first and second valves, or downstream of the second valve) in or about valve assembly 10. Further, the microcontroller 36 onboard the valve assembly 10 may allow the valve controller 26 to assess when the combustion appliance is on and when it is off and in which state (e.g. open/closed) the valve sealing members 22 are positioned. Furthermore, it is possible to observe with one or more pressure sensors both HGP and LGP states upstream, downstream, and/or intermediate valve port(s) 20. As discussed, a single pressure sensor may be located at any position within or about valve assembly 10, such that the pressure sensor may be in fluid communication with fluid channel 18. A single pressure sensor configuration for detecting HGP and LGP may be facilitated by having microprocessor 36 observing sensed data for both low and high pressure conditions simultaneously. In one example, a single pressure sensor intermediate the first valve port 20a and the second valve port 20b, may monitor for both HGP and LGP events in the gas stream provided to the gas valve assembly 10. In the example, the single pressure sensor intermediate the first valve port 20a and the second valve port 20b may monitor for both HGP and LGP events whenever at least the first valve port 20a is open.
Valve Proving System Test
Valve controller 26 may be configured to perform an electronic valve proving system (VPS) test on valve assembly 10, where all or substantially all of the structure required for the VPS may be integrated directly into valve assembly 10. When so provided, the direct integration may allow sensors and electronics needed for VPS testing to share a common housing. Valve assembly 10 may be in communication with combustion appliance controller 60 or other device, and may at least partially control a fuel flow to a combustion appliance through fluid channel 18. Illustratively, the combustion appliance may cycle on and off during a sequence of operational cycles, where at least some of the operational cycles may include performing a VPS test prior to and/or after igniting received fuel during the corresponding operational cycle. For example, VPS tests may be performed on each valve port 20 prior to igniting received fuel during a corresponding operational cycle, VPS tests may be performed on each valve port 20 after a call for heat is satisfied (e.g., at the very end of an operational cycle), or a VPS test may be performed on a first valve port 20 prior to igniting received fuel during a corresponding operational cycle and on a second valve port 20 after a call for heat is satisfied. Due to the timing of the VPS test before and/or after operational cycles, or both, the test may be achieved in an amount of time consistent with the useful operation of an individual appliance (e.g., a short amount of time of 10-15 seconds or 5-30 seconds or a longer amount of time) depending on the inlet pressure, size of the intermediate volume 19, volume of the appliance combustion chamber, length of time of the appliance pre-purge cycle, firing rate of the appliance burner, the leakage threshold level, etc. The VPS test may be an automated process that occurs every, or at least some, operational cycle(s) (e.g., once the VPS test has been set up by a field installer or at the original equipment manufacturer, the testing may not require the end user to participate in any way).
The structural set up of valve assembly 10 for a VPS test may include valve controller 26 in communication with a pressure sensor 44 that may be in fluid communication with intermediate volume 19 between two valve ports (e.g., first valve port 20a and second valve port 20b, as seen in
In some cases, utilizing an inlet pressure sensor 42 in addition to or as an alternative to pressure sensor 44 may allow controller 26 to determine in real time which valve port 20 is leaking. By using pressure sensor 42 at the inlet, the inlet pressure may be known prior to a VPS sequence and controller 26 may be able to pre-determine thresholds for pressure rise and decay based on knowing the inlet pressure prior to the VPS sequence. Such pre-determination of the thresholds may allow sensed pressures to be compared to the thresholds at any time during the VPS sequence.
Valve controller 26 may include non-volatile memory 37 or other memory that may include a first VPS threshold value (e.g., for comparing to a pressure rise) and a second VPS threshold value (e.g., for comparing to a pressure decay) utilized in performing the VPS test. Alternatively, or in addition, the memory may be located at a position other than in valve controller 26, such that any remote memory may be in communication with valve controller 26. Valve controller 26 may further be configured to compare the determined measure related to a pressure change rate in the intermediate volume 19 to the first and/or second threshold value during a first valve leakage test having a first duration, and/or comparing the measure that is related to a pressure change rate in the intermediate volume 19 to the third and/or fourth threshold value during a second valve leakage test having a second duration that is longer than the first duration. Illustratively, the first and/or second threshold values may be utilized in a valve leakage test each time a combustion appliance or other device connected to valve assembly 10 opens one or more valve ports 20, for example, in a VPS test or other test. The third and/or fourth threshold values may be utilized in a valve leakage test or other test performed as scheduled maintenance while valve assembly 10 is offline, at the time of commissioning of valve assembly 10, and/or at other preferred times.
The VPS test may be achieved by commanding valve actuators 30 to open and/or closed in a useful sequence. This sequence may be initialized and/or controlled through valve controller 26 and/or through the combustion appliance controller 60. When the VPS sequence is initialized and controlled remotely (e.g., remote from valve controller 26) through the combustion appliance controller 60, the valve controller 26 may be configured to detect if the VPS test or another test is occurring by monitoring gas valve assembly 10 and signals communicated to valve assembly 10. If the VPS test is to be controlled by the valve controller 26, the set up of the VPS settings may occur at a display/user interface 76 on board the valve itself or at a remote display (e.g., displays 52, 62). If the VPS test is to be actuated or initiated at or through combustion appliance controller 60, the set up of the VPS settings may occur at a remote display (e.g., displays 52, 62). Valve controller 26 may monitor valve actuators 30a, 30b, first control signal (MV1) controlling first valve actuator 30a and second control signal (MV2) controlling second valve actuator 30b, and/or the states of valve ports 20a, 20b (e.g., by monitoring the output of position sensor(s) 48) to identify if the VPS test is occurring. First and second control signals (MV1 and MV2) may be actuated by a combustion appliance controller 60 in communication with valve assembly 10 or by a valve controller 26 or by a field tool in communication with valve controller 26 or any other tool or individual in communication with valve assembly 10. Although the field tool and other tools are most often used for actuating first and second control signals (MV1 and MV2) in a valve leakage test, such similar or different tools may be used to operate a VPS test or for system level diagnostics and/or troubleshooting by a trained appliance technician in the field.
In performing a VPS test, valve controller 26 may cause or identify the following first predetermined sequence. The first valve actuator 30a may close the first valve port 20a (if not already closed). The second valve actuator 30b may then open the second valve port 20b (if not already opened) to depressurize the intermediate volume 19 between the first valve port 20a and the second valve port 20b. The second valve actuator 30b may then close the second valve port 20b to seal the depressurized intermediate volume 19.
Valve controller 26 may cause or identify this first predetermined sequence as a first sub-test of a VPS test, and valve controller 26 may be configured to compare a measure that is related to the pressure change rate in intermediate volume 19 to a first VPS sub-test threshold value prior to, during, or after a first sub-set VPS duration. After or while comparing the measure related to the pressure change rate in intermediate volume 19 to the first sub-test threshold value, valve controller 26 may output a signal if the measure meets and/or exceeds the first sub-test threshold value. Valve controller 26 may be configured to output the signal over the communication bus 100 or using a simple pair of contacts (e.g., relay contacts that close when a measured pressure surpasses a threshold pressure value) at or in communication with appliance controller 60, one or more of a local display, a remote device 50, 60 and/or a remote display 52, 62 of the remote device(s) 50, 60. The first sub-test of the VPS test may be configured to at least detect a leaking first valve port 20a. The outputted signal may indicate, or may cause to be indicated, a valve leakage within valve assembly 10 and/or a measure of the magnitude of the valve leakage.
In addition to identifying the first sub-test of a VPS test, valve controller 26 may cause or identify the following second predetermined sequence. The second valve actuator 30b may close the second valve port 20b (if not already closed). The first valve actuator 30a may then open the first valve port 20a (if not already opened) to pressurize the intermediate volume 19 between the first valve port 20a and the second valve port 20b. The first valve actuator 30a may then close the first valve port 20a to seal the pressurized intermediate volume 19.
Valve controller 26 may cause or identify this second predetermined sequence as a second sub-test of a VPS test, and valve controller 26 may be configured to compare a measure that is related to the pressure change rate in intermediate volume 19 to a second VPS sub-test threshold value prior to, during, or after a second sub-set VPS duration. After or while comparing the measure related to the pressure change rate in intermediate volume 19 to the second sub-test threshold value, valve controller 26 may output a signal if the measure meets and/or exceeds the second sub-test threshold value. Valve controller 26 may be configured to output the signal to one or more of a local display, a remote device 50, 60 and/or a remote display 52, 62 of the remote device(s) 50, 60. The second sub-test of the VPS test may be configured to at least detect a leaking second valve port 20b. The outputted signal may indicate, or may cause to be indicated, a valve leakage within valve assembly 10 and/or a measure of the magnitude of the valve leakage. Further, first VPS sub-test and second VPS sub-test of the VPS test may be performed in any order, as desired.
The first and second VPS sub-test threshold values may be programmed into valve controller 26, and the first and second VPS sub-test threshold values may be different or substantially the same value. Alternatively, or in addition, valve controller 26 may be configured to calculate the first and second VPS sub-test threshold values based on one or more parameters and, in some instances, the valve controller 26 may be configured to store the first and second VPS sub-test threshold values. The one or more parameters that valve controller 26 may consider if it is determining a VPS sub-test threshold value include, but are not limited to, a sensed pressure, a sensed temperature, max flow rate of the system, a number of ON-OFF cycles operated up to a point in time, volume of flow channel 18, altitude of valve assembly 10, barometric pressure, absolute pressure, gas type (e.g., density), ANSI requirements, EN requirements, other agency requirements, an allowed VPS test duration, and how small of a leak is to be detected, etc. Further, in the event more than two sub-tests are performed as part of the VPS test, there may be more threshold values than the first and second VPS sub-test threshold values, if desired.
In an illustrative operation, a VPS test may be performed on a valve assembly 10 that is coupled to a non-switched gas source, or other gas source, that is under a positive pressure during the VPS test to test gas valve assembly 10 for leaks.
A similar VPS test performed on valve assembly 10 may include opening one of the first and second valve port 20a, 20b with the other of the first and second valve ports 20a, 20b remaining or being closed. After opening one of the first and second valve ports 20a, 20b, closing the opened valve port such that both valve ports 20a, 20b are closed such that a first initial gas pressure may be present in intermediate volume 19. An intermediate pressure sensor 44 may continuously or discontinuously sense a pressure in intermediate volume 19, including the first initial pressure therein, and send the sensed pressures to valve controller 26. The initial pressure in intermediate volume 19 may be sensed at any time, for example, the initial pressure may be sensed after opening one of the valve ports 20a, 20b and before closing that opened valve port 20a, 20b. Valve controller 26 may monitor (e.g., continuously or discontinuously), over time, the pressure in intermediate volume 19 and determine a first measure that is related to a pressure change rate within intermediate volume 19 while both valve ports 20a, 20b are in a closed position. After determining the first measure that is related to a pressure change rate within intermediate volume 19, valve controller 26 may compare the determined first measure related to a pressure change rate in the intermediate volume 19 to a first threshold value stored in valve controller 26. Valve controller 26 may then output to a display and/or remote device 50, 60 or other device an output signal that is related to the first measure related to the pressure change rate (e.g., a determined pressure change in intermediate volume 19, or other determined measure), where outputting the output signal may also include storing the determined first measure related to the pressure change rate in non-volatile memory 37 on valve controller 26. Optionally, valve controller 26 may output the output signal if the determined first measure meets and/or exceeds the first threshold value. The output signal, however, may convey any information, as desired. For example, the output signal may convey information related to when (e.g. time stamp) the determined measure that is related to the pressure change rate meets and/or exceeds a threshold value, or other information related to or not related to the pressure in intermediate volume 19. In an alternative, or in addition to providing the output signal, a visual and/or audible indicator may be provided to indicate if valve assembly 10 passed or failed the VPS test.
In addition, first and/or second valve port 20a, 20b may be manipulated such that a second initial gas pressure may be present in the intermediate volume 19 while the first and second valve ports 20a, 20b are in the closed position. For example, second valve port 20b may be closed, then the first valve port 20a may be opened to pressurize intermediate volume 19 and then closed to seal in the second initial pressure. The second initial pressure may be substantially different than the first initial gas pressure, as the first initial pressure may be associated with a depressurized state of intermediate volume 19 and the second initial pressure may be associated with a pressurized state of intermediate volume 19, for example. Similar to above, intermediate pressure sensor 44 may sense pressure within intermediate volume 19 and communicate the sensed pressure and measures related to the sensed pressures to valve controller 26. Valve controller 26 may monitor (e.g., continuously or discontinuously), over time, the pressure in intermediate volume 19 and determine a second measure that is related to a pressure change rate within intermediate volume 19 while both valve ports 20a, 20b are in the closed position. After determining the second measure that is related to a pressure change rate within intermediate volume 19, valve controller 26 may compare the determined second measure related to a pressure change rate in the intermediate volume 19 to a second threshold value stored in valve controller 26. Valve controller 26 may then output to a display and/or remote device 50, 60 or other device an output signal that is related to the second measure related to a pressure change rate, where outputting the output signal may also include storing the determined second measure related to the pressure change rate in non-volatile memory 37 on valve controller 26. Optionally, valve controller 26 may output the output signal or a different output signal if the determined second measure meets and/or exceeds the second threshold value. The output signal, however, may convey any information and the outputted signals may be outputted in any situation. Further, the output signal may be configured to provide, or cause to be provided, a visual and/or audible indicator to indicate if valve assembly 10 passed and/or failed the VPS test.
The steps of the illustrative VPS test may be performed once such as when the gas valve assembly 10 is installed or during routine maintenance, and/or the steps may be repeated during each combustion cycle of a combustion appliance. In either case, the valve controller 26 or other device, or even a user, may identify a trend in the stored determined measures related to the pressure change rate or in other data sensed, calculated and/or stored during the valve leakage tests. A determined trend may be used for any of many purposes, for example, a trend may be used to predict when the valve will require replacement and/or servicing, and/or to make other predictions. Further, a VPS test and/or leakage test may be initiated and/or operated dependent on or independent of an attached device (e.g., a combustion appliance controller 60). In such an instance, valve controller 26 may be configured to initiate and operate a VPS test and/or leakage test independent of an attached device and may be configured to disable a heat call or other signal to and/or from an attached device, when appropriate.
Valve Leakage Test (VLT)
Valve controller 26 may be configured to perform a Valve Leakage (VL) Test on valve assembly 10. Valve controller 26 may be manually initialized by a field service technician or other user at either a local display on the valve assembly 10 (e.g., when valve controller 26 controls the operation of the VL test) or at a remote display 52, 62 (e.g., when either the valve controller 26 controls the operation of the VL test or when the VL test is remotely controlled). Similar to the set up for a VPS test, the structural set up of valve assembly 10 for a VL test may include valve controller 26 in communication with a pressure sensor 44 that may be in fluid communication with intermediate volume 19 between two valve ports 20 (e.g., first valve port 20a and second valve port 20b), as seen in
The VL test may be performed in the same manner as the VPS test discussed above. However, in the VL test, the test duration may be longer (e.g., one minute, two minutes, several minutes, or other time period that may possibly be longer than a typical length of time it may take to run a VPS test) during which time a combustion appliance may be offline, thereby allowing smaller leaks to be detected. Also, the thresholds values used during the VL test may be different from those used in the VPS test. Also, the VL test may be performed less frequently than the VPS test. For example, the VL test may be performed once a year or during routine maintenance, and not during every combustion cycle.
In some cases, valve controller 26 may be configured to initiate a VL test. In some instances, the valve controller 26 may be configured to detect if a VPS test or a longer, Valve Leakage (VL) test, is occurring by monitoring gas valve assembly 10 and signals communicated to valve assembly 10. For example, valve controller 26 may monitor valve actuators 30a, 30b, first control signal (MV1) controlling first valve actuator 30a and/or second control signal (MV2) controlling second valve actuator 30b, and/or the states of valve ports 20a, 20b to identify if a VPS test or a longer VL test is occurring. In some cases, first and second control signals (MV1 and MV2) may be controlled by a combustions appliance in communication with valve assembly 10 or a field tool in communication with valve assembly 10 or any other tool or individual in communication with valve assembly 10. If a VL test is detected, valve controller 26 may automatically apply thresholds associated with the longer VL test rather than thresholds of the shorter VPS test. The valve controller 26 may revert back, automatically or otherwise, to using VPS thresholds after the longer VL test has been completed, if desired.
When valve assembly 10 may be disconnected from a combustion appliance controller 60 and connected to a field tool to effect the VL test with VL thresholds, it is contemplated that when combustion appliance controller 60 is reconnected with valve assembly 10, previous combustion appliance-valve assembly thresholds/conditions (e.g., VPS thresholds) may be automatically reset, as valve controller 26 and device controller 60 may automatically detect the reconnection.
Those skilled in the art will recognize that the present disclosure may be manifested in a variety of forms other than the specific embodiments described and contemplated herein. Accordingly, departure in form and detail may be made without departing from the scope and spirit of the present disclosure as described in the appended claims.
This is a continuation of co-pending U.S. patent application Ser. No. 13/326,523, filed Dec. 15, 2011, and entitled “GAS VALVE WITH COMMUNICATION LINK”, which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
156769 | Cameron | Nov 1874 | A |
424581 | Sickels | Apr 1890 | A |
1033204 | Skinner | Jul 1912 | A |
1147840 | Bowser | Jul 1915 | A |
1156977 | Cloos | Oct 1915 | A |
1165315 | Cameron | Dec 1915 | A |
1206532 | Gray | Nov 1916 | A |
1847385 | Dengler | Mar 1932 | A |
2093122 | Andrews | Sep 1937 | A |
2196798 | Horstmann | Apr 1940 | A |
2403692 | Tibbetts | Jul 1946 | A |
2440329 | Doble | Apr 1948 | A |
2497549 | Heller | Feb 1950 | A |
2561793 | Furczyk | Jul 1951 | A |
2791238 | Bryant | May 1957 | A |
2975307 | Schroeder et al. | Mar 1961 | A |
3164364 | McColl | Jan 1965 | A |
3202170 | Holbrook | Aug 1965 | A |
3304406 | King | Feb 1967 | A |
3346008 | Scaramucci | Oct 1967 | A |
3381623 | Elliott | May 1968 | A |
3393965 | Vaughan | Jul 1968 | A |
3414010 | Sparrow | Dec 1968 | A |
3493005 | Kakegawa | Feb 1970 | A |
3641373 | Elkuch | Feb 1972 | A |
3646969 | Stampfli | Mar 1972 | A |
3744754 | Demi | Jul 1973 | A |
3769531 | Elkuch | Oct 1973 | A |
3803424 | Smiley et al. | Apr 1974 | A |
3884266 | Kondo | May 1975 | A |
3947644 | Uchikawa | Mar 1976 | A |
3960364 | Hargrave | Jun 1976 | A |
3973576 | Dietiker et al. | Aug 1976 | A |
3973976 | Boyd | Aug 1976 | A |
3993939 | Slavin et al. | Nov 1976 | A |
4114652 | Oberle | Sep 1978 | A |
4115036 | Paterson | Sep 1978 | A |
4140936 | Bullock | Feb 1979 | A |
4188013 | Battersby et al. | Feb 1980 | A |
4188972 | Van Der Zee | Feb 1980 | A |
4197737 | Pittman | Apr 1980 | A |
4242080 | Tabei | Dec 1980 | A |
4277832 | Wong | Jul 1981 | A |
4360955 | Block | Nov 1982 | A |
4402340 | Lockwood, Jr. | Sep 1983 | A |
4406131 | Weasel, Jr. | Sep 1983 | A |
4418886 | Holzer | Dec 1983 | A |
4442853 | Gort | Apr 1984 | A |
4450868 | Duval et al. | May 1984 | A |
4453169 | Martner | Jun 1984 | A |
4478076 | Bohrer | Oct 1984 | A |
4478077 | Bohrer et al. | Oct 1984 | A |
4481776 | Araki et al. | Nov 1984 | A |
4493303 | Thompson et al. | Jan 1985 | A |
4498850 | Perlov et al. | Feb 1985 | A |
4498863 | Hanson et al. | Feb 1985 | A |
4501144 | Higashi et al. | Feb 1985 | A |
4539575 | Nilsson | Sep 1985 | A |
4543974 | Dietiker et al. | Oct 1985 | A |
4576050 | Lambert | Mar 1986 | A |
4581624 | O'Connor | Apr 1986 | A |
4581707 | Millar | Apr 1986 | A |
4585209 | Aine et al. | Apr 1986 | A |
4619438 | Coffee | Oct 1986 | A |
4622699 | Spriggs | Nov 1986 | A |
4622999 | Ray | Nov 1986 | A |
4645450 | West | Feb 1987 | A |
4651564 | Johnson et al. | Mar 1987 | A |
4654546 | Kirjavainen | Mar 1987 | A |
4722360 | Odajima et al. | Feb 1988 | A |
4756508 | Giachino et al. | Jul 1988 | A |
4798531 | Breckner | Jan 1989 | A |
4815699 | Mueller | Mar 1989 | A |
4821999 | Ohtaka | Apr 1989 | A |
4829826 | Valentin et al. | May 1989 | A |
4835717 | Michel et al. | May 1989 | A |
4836247 | Chuang | Jun 1989 | A |
4898200 | Odajima et al. | Feb 1990 | A |
4911616 | Laumann, Jr. | Mar 1990 | A |
4915613 | Landis | Apr 1990 | A |
4938742 | Smits | Jul 1990 | A |
4939405 | Okuyama et al. | Jul 1990 | A |
5022435 | Jaw-Shiunn | Jun 1991 | A |
5065978 | Albarda et al. | Nov 1991 | A |
5069419 | Jerman | Dec 1991 | A |
5070252 | Castenschiold et al. | Dec 1991 | A |
5078581 | Blum et al. | Jan 1992 | A |
5082242 | Bonne et al. | Jan 1992 | A |
5082246 | Stanley et al. | Jan 1992 | A |
5085562 | Van Lintel | Feb 1992 | A |
5096388 | Weinberg | Mar 1992 | A |
5129794 | Beattty | Jul 1992 | A |
5146941 | Statler | Sep 1992 | A |
5148074 | Fujita et al. | Sep 1992 | A |
5169063 | Miyazaki et al. | Dec 1992 | A |
5171132 | Miyazaki et al. | Dec 1992 | A |
5176358 | Bonne et al. | Jan 1993 | A |
5180288 | Richter et al. | Jan 1993 | A |
5180623 | Ohnstein | Jan 1993 | A |
5186054 | Sekimura | Feb 1993 | A |
5190068 | Philbin | Mar 1993 | A |
5192197 | Culp | Mar 1993 | A |
5193993 | Dietiker | Mar 1993 | A |
5199456 | Love et al. | Apr 1993 | A |
5199462 | Baker | Apr 1993 | A |
5203688 | Dietiker | Apr 1993 | A |
5205323 | Baker | Apr 1993 | A |
5206557 | Bobbio | Apr 1993 | A |
5215112 | Davison | Jun 1993 | A |
5215115 | Dietiker | Jun 1993 | A |
5219278 | van Lintel | Jun 1993 | A |
5224843 | Van Lintel | Jul 1993 | A |
5244527 | Aoyagi | Sep 1993 | A |
5244537 | Ohnstein | Sep 1993 | A |
5263514 | Reeves | Nov 1993 | A |
5294089 | LaMarca | Mar 1994 | A |
5317670 | Elia | May 1994 | A |
5322258 | Bosch et al. | Jun 1994 | A |
5323999 | Bonne | Jun 1994 | A |
5325880 | Johnson et al. | Jul 1994 | A |
5336062 | Richter | Aug 1994 | A |
5368571 | Horres, Jr. | Nov 1994 | A |
5388607 | Ramaker et al. | Feb 1995 | A |
5441597 | Bonne et al. | Aug 1995 | A |
5449142 | Banick | Sep 1995 | A |
5452878 | Gravesen et al. | Sep 1995 | A |
5460196 | Yonnet | Oct 1995 | A |
5477877 | Schulze et al. | Dec 1995 | A |
5499909 | Yamada et al. | Mar 1996 | A |
5513611 | Ricouard et al. | May 1996 | A |
5520533 | Vrolijk | May 1996 | A |
5526172 | Kanack | Jun 1996 | A |
5529465 | Zengerle et al. | Jun 1996 | A |
5536963 | Polla | Jul 1996 | A |
5538220 | LaMarca | Jul 1996 | A |
5541465 | Higuchi et al. | Jul 1996 | A |
5552654 | Konno et al. | Sep 1996 | A |
5565832 | Haller et al. | Oct 1996 | A |
5571401 | Lewis et al. | Nov 1996 | A |
5580444 | Burrows | Dec 1996 | A |
5590235 | Rappenecker et al. | Dec 1996 | A |
5621164 | Woodbury et al. | Apr 1997 | A |
5642015 | Whitehead et al. | Jun 1997 | A |
5662465 | Kano | Sep 1997 | A |
5676342 | Otto et al. | Oct 1997 | A |
5683159 | Johnson | Nov 1997 | A |
5685707 | Ramsdell et al. | Nov 1997 | A |
5696662 | Bauhahn | Dec 1997 | A |
5725363 | Bustgens et al. | Mar 1998 | A |
5735503 | Hietkamp | Apr 1998 | A |
5741978 | Gudmundsson | Apr 1998 | A |
5748432 | Przywozny et al. | May 1998 | A |
5755259 | Schulze et al. | May 1998 | A |
5759014 | Van Lintel | Jun 1998 | A |
5759015 | Van Lintel et al. | Jun 1998 | A |
5769043 | Nitikiewicz | Jun 1998 | A |
5774372 | Berwanger | Jun 1998 | A |
5790420 | Lang | Aug 1998 | A |
5792957 | Luder et al. | Aug 1998 | A |
5797358 | Brandt et al. | Aug 1998 | A |
5808205 | Romo | Sep 1998 | A |
5822170 | Cabuz et al. | Oct 1998 | A |
5827950 | Woodbury et al. | Oct 1998 | A |
5836750 | Cabuz | Nov 1998 | A |
5839467 | Saaski et al. | Nov 1998 | A |
5847523 | Rappenecker et al. | Dec 1998 | A |
5863708 | Zanzucchi et al. | Jan 1999 | A |
5887847 | Holborow | Mar 1999 | A |
5893389 | Cunningham | Apr 1999 | A |
5901939 | Cabuz et al. | May 1999 | A |
5911872 | Lewis et al. | Jun 1999 | A |
5918852 | Otto | Jul 1999 | A |
5933573 | Lukenich et al. | Aug 1999 | A |
5944257 | Dietiker et al. | Aug 1999 | A |
5954079 | Barth et al. | Sep 1999 | A |
5954089 | Seymour | Sep 1999 | A |
5957158 | Volz et al. | Sep 1999 | A |
5959448 | Baranski et al. | Sep 1999 | A |
5967124 | Cook et al. | Oct 1999 | A |
5971355 | Biegelsen et al. | Oct 1999 | A |
5971746 | Givens et al. | Oct 1999 | A |
5986573 | Franklin et al. | Nov 1999 | A |
5997280 | Welz, Jr. | Dec 1999 | A |
6003552 | Shank et al. | Dec 1999 | A |
6050281 | Adams et al. | Apr 2000 | A |
6057771 | Lakra | May 2000 | A |
6106245 | Cabuz | Aug 2000 | A |
6109889 | Zengerle et al. | Aug 2000 | A |
6116863 | Ahn et al. | Sep 2000 | A |
6122973 | Nomura et al. | Sep 2000 | A |
6151967 | McIntosh et al. | Nov 2000 | A |
6152168 | Ohmi et al. | Nov 2000 | A |
6155531 | Holborow et al. | Dec 2000 | A |
6167761 | Hanzawa et al. | Jan 2001 | B1 |
6176247 | Winchcomb et al. | Jan 2001 | B1 |
6179000 | Zdobinski et al. | Jan 2001 | B1 |
6179586 | Herb et al. | Jan 2001 | B1 |
6182941 | Scheurenbrand et al. | Feb 2001 | B1 |
6184607 | Cabuz et al. | Feb 2001 | B1 |
6189568 | Bergum et al. | Feb 2001 | B1 |
6213758 | Tesar et al. | Apr 2001 | B1 |
6215221 | Cabuz et al. | Apr 2001 | B1 |
6240944 | Ohnstein et al. | Jun 2001 | B1 |
6242909 | Dorsey et al. | Jun 2001 | B1 |
6247919 | Welz, Jr. et al. | Jun 2001 | B1 |
6255609 | Samuelson et al. | Jul 2001 | B1 |
6263908 | Love et al. | Jul 2001 | B1 |
6288472 | Cabuz et al. | Sep 2001 | B1 |
6297640 | Hayes | Oct 2001 | B1 |
6321781 | Kurth | Nov 2001 | B1 |
6360773 | Rhodes | Mar 2002 | B1 |
6373682 | Goodwin-Johansson | Apr 2002 | B1 |
6386234 | Sontag | May 2002 | B2 |
6390027 | Lyons et al. | May 2002 | B1 |
6397798 | Fiaccabrino | Jun 2002 | B1 |
6401753 | Neu | Jun 2002 | B2 |
6418793 | Pechoux et al. | Jul 2002 | B1 |
6445053 | Cho | Sep 2002 | B1 |
6450200 | Ollivier | Sep 2002 | B1 |
6460567 | Hansen, III et al. | Oct 2002 | B1 |
6463546 | Jeske et al. | Oct 2002 | B1 |
6496348 | McIntosh | Dec 2002 | B2 |
6496786 | Dieterle et al. | Dec 2002 | B1 |
6505838 | Cavaliere | Jan 2003 | B1 |
6508528 | Fujii et al. | Jan 2003 | B2 |
6520753 | Grosjean et al. | Feb 2003 | B1 |
6533574 | Pechoux | Mar 2003 | B1 |
6536287 | Beekhuizen et al. | Mar 2003 | B2 |
6550495 | Schulze | Apr 2003 | B1 |
6553979 | Albright | Apr 2003 | B2 |
6561791 | Vrolijk et al. | May 2003 | B1 |
6563233 | Hinks | May 2003 | B1 |
6564824 | Lowery et al. | May 2003 | B2 |
6571817 | Bohan, Jr. | Jun 2003 | B1 |
6572077 | Worner | Jun 2003 | B1 |
6579087 | Vrolijk | Jun 2003 | B1 |
6584852 | Suzuki et al. | Jul 2003 | B2 |
6590267 | Goodwin-Johansson et al. | Jul 2003 | B1 |
6606911 | Akiyama et al. | Aug 2003 | B2 |
6619388 | Dietz et al. | Sep 2003 | B2 |
6619612 | Freisinger et al. | Sep 2003 | B2 |
6623012 | Perry et al. | Sep 2003 | B1 |
6640642 | Onose et al. | Nov 2003 | B1 |
6644351 | La Marca et al. | Nov 2003 | B2 |
6650211 | Pimouguet | Nov 2003 | B2 |
6651506 | Lee et al. | Nov 2003 | B2 |
6651636 | Albright | Nov 2003 | B1 |
6651954 | Porcher et al. | Nov 2003 | B1 |
6655409 | Steenburgh et al. | Dec 2003 | B1 |
6655652 | Meinhof | Dec 2003 | B2 |
6658928 | Pollack et al. | Dec 2003 | B1 |
6676580 | Tsai et al. | Jan 2004 | B2 |
6704186 | Ishikura | Mar 2004 | B2 |
6725167 | Grumstrup et al. | Apr 2004 | B2 |
6728600 | Contaldo et al. | Apr 2004 | B1 |
6729601 | Freisinger et al. | May 2004 | B2 |
6742541 | Pimouguet | Jun 2004 | B2 |
6768406 | Fiaccabrino | Jul 2004 | B1 |
6796326 | Bayer | Sep 2004 | B2 |
6813954 | Gokhfeld | Nov 2004 | B2 |
6814102 | Hess et al. | Nov 2004 | B2 |
6814339 | Berger et al. | Nov 2004 | B2 |
6819208 | Peghaire et al. | Nov 2004 | B1 |
6820650 | Solet et al. | Nov 2004 | B2 |
6825632 | Hahn et al. | Nov 2004 | B2 |
6826947 | Solet et al. | Dec 2004 | B2 |
6851298 | Miura et al. | Feb 2005 | B2 |
6874367 | Jakobsen | Apr 2005 | B2 |
6877380 | Lewis | Apr 2005 | B2 |
6877383 | Horie et al. | Apr 2005 | B2 |
6880548 | Schultz et al. | Apr 2005 | B2 |
6880567 | Klaver et al. | Apr 2005 | B2 |
6885184 | Gofman | Apr 2005 | B1 |
6888354 | Gofman | May 2005 | B1 |
6889705 | Newman et al. | May 2005 | B2 |
6892756 | Schulze | May 2005 | B2 |
6903526 | Weisser et al. | Jun 2005 | B2 |
6906484 | Berroth et al. | Jun 2005 | B1 |
6923069 | Stewart | Aug 2005 | B1 |
6949903 | Berroth et al. | Sep 2005 | B2 |
6956340 | Schondelmaier et al. | Oct 2005 | B2 |
6956343 | Berroth et al. | Oct 2005 | B2 |
6968851 | Ramirez et al. | Nov 2005 | B2 |
6981426 | Wang et al. | Jan 2006 | B2 |
6983759 | Maichel et al. | Jan 2006 | B2 |
6994308 | Wang et al. | Feb 2006 | B1 |
6997684 | Hahn et al. | Feb 2006 | B2 |
7000635 | Erbe et al. | Feb 2006 | B2 |
7004034 | Chen | Feb 2006 | B2 |
7036791 | Wiese | May 2006 | B2 |
7039502 | Berwanger et al. | May 2006 | B2 |
7066203 | Baarda | Jun 2006 | B2 |
7082835 | Cook et al. | Aug 2006 | B2 |
7089086 | Schoonover | Aug 2006 | B2 |
7089959 | Cai | Aug 2006 | B2 |
7093611 | Murray et al. | Aug 2006 | B2 |
7107820 | Nunnally et al. | Sep 2006 | B2 |
7119504 | Dornhof | Oct 2006 | B2 |
7121525 | Gelez | Oct 2006 | B2 |
7174771 | Cooper | Feb 2007 | B2 |
7216547 | Stewart et al. | May 2007 | B1 |
7223094 | Goebel | May 2007 | B2 |
7225056 | Bolduan et al. | May 2007 | B2 |
7249610 | Moses | Jul 2007 | B2 |
7260994 | Oboodi et al. | Aug 2007 | B2 |
7290502 | Kidd et al. | Nov 2007 | B2 |
7290902 | Suehiro et al. | Nov 2007 | B2 |
7297640 | Xie et al. | Nov 2007 | B2 |
7302863 | Kielb et al. | Dec 2007 | B2 |
7319300 | Hahn | Jan 2008 | B2 |
7328719 | Madden | Feb 2008 | B2 |
7347221 | Berger et al. | Mar 2008 | B2 |
7360751 | Herrfurth | Apr 2008 | B2 |
7390172 | Winkler | Jun 2008 | B2 |
7398796 | Hjorth et al. | Jul 2008 | B2 |
7402925 | Best et al. | Jul 2008 | B2 |
7405609 | Krotsch | Jul 2008 | B2 |
7422028 | Nugent et al. | Sep 2008 | B2 |
7451600 | Patel et al. | Nov 2008 | B2 |
7451644 | Karte | Nov 2008 | B2 |
7453696 | Tungl et al. | Nov 2008 | B2 |
7461828 | Kidprasert | Dec 2008 | B2 |
7493822 | Stewart et al. | Feb 2009 | B2 |
7503221 | Wade | Mar 2009 | B2 |
7520487 | Mattes | Apr 2009 | B2 |
7537019 | Ting et al. | May 2009 | B2 |
7543604 | Benda | Jun 2009 | B2 |
7553151 | O'Mara et al. | Jun 2009 | B2 |
7554279 | Loffler et al. | Jun 2009 | B2 |
7556238 | Seberger | Jul 2009 | B2 |
7574896 | Cooper | Aug 2009 | B1 |
7586228 | Best | Sep 2009 | B2 |
7586276 | Dornhof | Sep 2009 | B2 |
7624755 | Benda et al. | Dec 2009 | B2 |
7627455 | Lenz et al. | Dec 2009 | B2 |
7644731 | Benda et al. | Jan 2010 | B2 |
7647842 | Killian et al. | Jan 2010 | B1 |
7669461 | Kates et al. | Mar 2010 | B2 |
7688011 | Berroth et al. | Mar 2010 | B2 |
7715168 | Gofman et al. | May 2010 | B2 |
7740024 | Brodeur et al. | Jun 2010 | B2 |
7759884 | Dufner et al. | Jul 2010 | B2 |
7769493 | Elshafei et al. | Aug 2010 | B2 |
7811069 | Fleig | Oct 2010 | B2 |
7812488 | Cosco et al. | Oct 2010 | B2 |
7816813 | Yagudayev et al. | Oct 2010 | B2 |
7841541 | Ardelt et al. | Nov 2010 | B2 |
7869971 | Varga | Jan 2011 | B2 |
7880421 | Karwath | Feb 2011 | B2 |
7880427 | Foll et al. | Feb 2011 | B2 |
7890216 | Boger et al. | Feb 2011 | B2 |
7890276 | Killion et al. | Feb 2011 | B2 |
7891972 | Blank et al. | Feb 2011 | B2 |
7898372 | Melchionne, Jr. | Mar 2011 | B2 |
7902776 | Karwath | Mar 2011 | B2 |
7904608 | Price | Mar 2011 | B2 |
7905251 | Flanders | Mar 2011 | B2 |
7922481 | Geiger et al. | Apr 2011 | B2 |
7940189 | Brown | May 2011 | B2 |
8020585 | Shock et al. | Sep 2011 | B2 |
8024978 | Khemet et al. | Sep 2011 | B2 |
8036837 | Wilke | Oct 2011 | B2 |
8061212 | Shubert | Nov 2011 | B2 |
8066255 | Wang | Nov 2011 | B2 |
8099248 | Umekage et al. | Jan 2012 | B2 |
8104510 | Ams et al. | Jan 2012 | B2 |
8109289 | Trnka et al. | Feb 2012 | B2 |
8126631 | Scalia, Jr. | Feb 2012 | B2 |
8205484 | Sasaki | Jun 2012 | B2 |
8212507 | Wystup et al. | Jul 2012 | B2 |
8225814 | Igarashi | Jul 2012 | B2 |
8235064 | Kasprzyk et al. | Aug 2012 | B2 |
8240636 | Smith | Aug 2012 | B2 |
8258660 | Strobel et al. | Sep 2012 | B2 |
8265794 | Minervini et al. | Sep 2012 | B2 |
8271141 | Cummings et al. | Sep 2012 | B2 |
8286937 | Forster | Oct 2012 | B2 |
8297948 | Laufer et al. | Oct 2012 | B2 |
8307845 | Kouchi et al. | Nov 2012 | B2 |
8319461 | Wystup et al. | Nov 2012 | B2 |
8353281 | Oberhomburg et al. | Jan 2013 | B2 |
8380448 | Franklin | Feb 2013 | B2 |
8381760 | Santinanavat et al. | Feb 2013 | B2 |
8387441 | Falta et al. | Mar 2013 | B2 |
8439667 | Fan et al. | May 2013 | B2 |
8473229 | Kucera et al. | Jun 2013 | B2 |
8500441 | Geiger et al. | Aug 2013 | B2 |
8539972 | Xu | Sep 2013 | B2 |
8550109 | Miyata et al. | Oct 2013 | B2 |
8567757 | Pitchford et al. | Oct 2013 | B2 |
8596957 | Seebauer | Dec 2013 | B2 |
8636501 | Geiger et al. | Jan 2014 | B2 |
8639464 | Artiuch et al. | Jan 2014 | B2 |
8677913 | Kastingschafer et al. | Mar 2014 | B2 |
8721325 | Geiger et al. | May 2014 | B2 |
8746275 | Santinanavat et al. | Jun 2014 | B2 |
8839815 | Young et al. | Sep 2014 | B2 |
8899264 | Young et al. | Dec 2014 | B2 |
8905063 | Young et al. | Dec 2014 | B2 |
8947242 | Kucera | Feb 2015 | B2 |
9020765 | Seebauer | Apr 2015 | B2 |
9074770 | Young | Jul 2015 | B2 |
9109610 | Streng et al. | Aug 2015 | B2 |
9222816 | Patel et al. | Dec 2015 | B2 |
9234661 | Young et al. | Jan 2016 | B2 |
9557059 | Kucera | Jan 2017 | B2 |
20020029808 | Friend et al. | Mar 2002 | A1 |
20020175791 | LaMarca et al. | Nov 2002 | A1 |
20030167851 | Parker | Sep 2003 | A1 |
20040035211 | Pinto et al. | Feb 2004 | A1 |
20040217182 | St. Jean et al. | Nov 2004 | A1 |
20050199286 | Appleford et al. | Sep 2005 | A1 |
20050279956 | Berger et al. | Dec 2005 | A1 |
20060141409 | Chian | Jun 2006 | A1 |
20060226299 | Tungl et al. | Oct 2006 | A1 |
20060243334 | Brochhaus et al. | Nov 2006 | A1 |
20060272712 | Sontag | Dec 2006 | A1 |
20060278281 | Gynz-Rekowski et al. | Dec 2006 | A1 |
20070024225 | Hahn et al. | Feb 2007 | A1 |
20070024255 | Yasumura | Feb 2007 | A1 |
20070068511 | Bachinsky et al. | Mar 2007 | A1 |
20070082304 | Burnham et al. | Apr 2007 | A1 |
20070089789 | Mudd et al. | Apr 2007 | A1 |
20070155423 | Carmody | Jul 2007 | A1 |
20070164243 | Volz | Jul 2007 | A1 |
20070256478 | Guadagnola et al. | Nov 2007 | A1 |
20080099082 | Moenkhaus | May 2008 | A1 |
20080157707 | Jeske et al. | Jul 2008 | A1 |
20080318098 | Matsunaga | Dec 2008 | A1 |
20090068503 | Yamazaki et al. | Mar 2009 | A1 |
20090105852 | Wintrich et al. | Apr 2009 | A1 |
20090120338 | Adendorff et al. | May 2009 | A1 |
20090126798 | Mather | May 2009 | A1 |
20090142717 | Lavelle | Jun 2009 | A1 |
20090197212 | Masen | Aug 2009 | A1 |
20090280989 | Astra et al. | Nov 2009 | A1 |
20090288399 | Fayard | Nov 2009 | A1 |
20090303076 | Setiadi et al. | Dec 2009 | A1 |
20100112500 | Maiello et al. | May 2010 | A1 |
20100138167 | Bessyo et al. | Jun 2010 | A1 |
20100146939 | Sim et al. | Jun 2010 | A1 |
20110039217 | Happe | Feb 2011 | A1 |
20110041483 | Kapparos | Feb 2011 | A1 |
20110240157 | Jones et al. | Oct 2011 | A1 |
20110266473 | Santinanavat et al. | Nov 2011 | A1 |
20120107753 | Kemp | May 2012 | A1 |
20130153041 | Kucera et al. | Jun 2013 | A1 |
20130153042 | Young et al. | Jun 2013 | A1 |
20130153798 | Kucera et al. | Jun 2013 | A1 |
20140096850 | Filkovski et al. | Apr 2014 | A1 |
20150045971 | Endel et al. | Feb 2015 | A1 |
20150107675 | Kucera | Apr 2015 | A1 |
20160123584 | Young et al. | May 2016 | A1 |
20160326967 | Yamamoto et al. | Nov 2016 | A1 |
20170134214 | Sethuraman et al. | May 2017 | A1 |
Number | Date | Country |
---|---|---|
3638604 | May 1988 | DE |
19617852 | Oct 1997 | DE |
19824521 | Dec 1999 | DE |
102005033611 | Oct 2006 | DE |
0062854 | Oct 1982 | EP |
0068517 | Jan 1983 | EP |
0275439 | Jul 1988 | EP |
0282758 | Sep 1988 | EP |
0356690 | Mar 1990 | EP |
0522479 | Jan 1993 | EP |
0563787 | Oct 1993 | EP |
0617234 | Sep 1994 | EP |
0645562 | Mar 1995 | EP |
0652501 | May 1995 | EP |
0664422 | Jul 1995 | EP |
0665396 | Aug 1995 | EP |
0678178 | Oct 1995 | EP |
0744821 | Nov 1996 | EP |
0757200 | Feb 1997 | EP |
0822376 | Feb 1998 | EP |
0817931 | Dec 1998 | EP |
0881435 | Dec 1998 | EP |
0896191 | Feb 1999 | EP |
0896192 | Feb 1999 | EP |
0907052 | Apr 1999 | EP |
0817934 | May 1999 | EP |
0952357 | Oct 1999 | EP |
0976957 | Feb 2000 | EP |
1031792 | Aug 2000 | EP |
1069357 | Jan 2001 | EP |
1073192 | Jan 2001 | EP |
1084357 | Mar 2001 | EP |
1084358 | Mar 2001 | EP |
1121511 | Aug 2001 | EP |
1176317 | Jan 2002 | EP |
1186779 | Mar 2002 | EP |
1157205 | Sep 2002 | EP |
0992658 | May 2003 | EP |
1323966 | Jul 2003 | EP |
1078187 | Aug 2003 | EP |
1382907 | Jan 2004 | EP |
1403885 | Mar 2004 | EP |
1269054 | Aug 2004 | EP |
1484509 | Dec 2004 | EP |
1191676 | Jan 2005 | EP |
1275039 | Jan 2005 | EP |
1446607 | Mar 2005 | EP |
1510756 | Mar 2005 | EP |
1299665 | Apr 2005 | EP |
1324496 | Jun 2005 | EP |
0751350 | Sep 2005 | EP |
1584870 | Oct 2005 | EP |
1243857 | Dec 2005 | EP |
1282798 | Dec 2005 | EP |
1424708 | Dec 2005 | EP |
0843287 | Feb 2006 | EP |
1346463 | Mar 2006 | EP |
1535388 | Jun 2006 | EP |
1703140 | Sep 2006 | EP |
1703146 | Sep 2006 | EP |
1183772 | Oct 2006 | EP |
1303718 | Oct 2006 | EP |
1314240 | Oct 2006 | EP |
1715229 | Oct 2006 | EP |
1256763 | Nov 2006 | EP |
1727268 | Nov 2006 | EP |
1559936 | Dec 2006 | EP |
1748534 | Jan 2007 | EP |
1748545 | Jan 2007 | EP |
1327808 | Feb 2007 | EP |
1329659 | Feb 2007 | EP |
1291532 | Jun 2007 | EP |
1610046 | Jun 2007 | EP |
1592905 | Jul 2007 | EP |
1610045 | Jul 2007 | EP |
1727261 | Oct 2007 | EP |
1860328 | Nov 2007 | EP |
1626321 | Feb 2008 | EP |
1848907 | Apr 2008 | EP |
1936778 | Jun 2008 | EP |
1413045 | Jul 2008 | EP |
1499008 | Oct 2008 | EP |
1882882 | Oct 2008 | EP |
1536169 | Nov 2008 | EP |
1298679 | Dec 2008 | EP |
1714040 | Dec 2008 | EP |
2014979 | Jan 2009 | EP |
1669648 | Feb 2009 | EP |
2048439 | Apr 2009 | EP |
1659462 | Jun 2009 | EP |
2093545 | Aug 2009 | EP |
2107248 | Oct 2009 | EP |
2116857 | Nov 2009 | EP |
2119946 | Nov 2009 | EP |
1370787 | Mar 2010 | EP |
1413044 | Mar 2010 | EP |
2164164 | Mar 2010 | EP |
2177796 | Apr 2010 | EP |
2178201 | Apr 2010 | EP |
1970610 | May 2010 | EP |
2197101 | Jun 2010 | EP |
2068056 | Aug 2010 | EP |
1712800 | Oct 2010 | EP |
2118493 | Oct 2010 | EP |
2242344 | Oct 2010 | EP |
1715582 | Nov 2010 | EP |
1675757 | Dec 2010 | EP |
2267883 | Dec 2010 | EP |
1703139 | Jan 2011 | EP |
2286976 | Feb 2011 | EP |
1596495 | Apr 2011 | EP |
2212984 | Apr 2011 | EP |
2306622 | Apr 2011 | EP |
2010500 | Jun 2011 | EP |
2113696 | Jul 2011 | EP |
2604924 | May 2015 | EP |
2099158 | Dec 1982 | GB |
2327750 | Feb 1999 | GB |
02086258 | Mar 1990 | JP |
05219760 | Aug 1993 | JP |
9061284 | Mar 1997 | JP |
9184600 | Jul 1997 | JP |
2004125809 | Apr 2004 | JP |
2004309159 | Nov 2004 | JP |
2008135922 | Jun 2008 | JP |
2008286478 | Nov 2008 | JP |
744877 | Jun 1980 | SU |
8705375 | Sep 1987 | WO |
9627095 | Sep 1996 | WO |
9729538 | Aug 1997 | WO |
9801709 | Jan 1998 | WO |
9924758 | May 1999 | WO |
9960292 | Nov 1999 | WO |
9964769 | Dec 1999 | WO |
9964770 | Dec 1999 | WO |
0028215 | May 2000 | WO |
0106179 | Jan 2001 | WO |
0133078 | May 2001 | WO |
0161226 | Aug 2001 | WO |
0173297 | Oct 2001 | WO |
0190617 | Nov 2001 | WO |
0204852 | Jan 2002 | WO |
02077502 | Oct 2002 | WO |
02084156 | Oct 2002 | WO |
02086365 | Oct 2002 | WO |
02086918 | Oct 2002 | WO |
02097840 | Dec 2002 | WO |
2004059830 | Jul 2004 | WO |
2004070245 | Aug 2004 | WO |
2005042313 | May 2005 | WO |
2005076455 | Aug 2005 | WO |
2005076456 | Aug 2005 | WO |
2005085652 | Sep 2005 | WO |
2005094150 | Oct 2005 | WO |
2006000366 | Jan 2006 | WO |
2006000367 | Jan 2006 | WO |
2006039956 | Apr 2006 | WO |
2006042635 | Apr 2006 | WO |
2006053816 | May 2006 | WO |
2006077069 | Jul 2006 | WO |
2006088367 | Aug 2006 | WO |
2007012419 | Feb 2007 | WO |
2007018876 | Feb 2007 | WO |
2007093312 | Aug 2007 | WO |
2007140927 | Dec 2007 | WO |
2008061575 | Mar 2008 | WO |
2008039061 | Apr 2008 | WO |
2008119404 | Oct 2008 | WO |
2008141911 | Nov 2008 | WO |
2008148401 | Dec 2008 | WO |
2009000481 | Dec 2008 | WO |
2009049694 | Apr 2009 | WO |
2009065815 | May 2009 | WO |
2009073510 | Jun 2009 | WO |
2009089857 | Jul 2009 | WO |
2009126020 | Oct 2009 | WO |
2010018192 | Feb 2010 | WO |
2010052137 | May 2010 | WO |
2010056111 | May 2010 | WO |
2010083877 | Jul 2010 | WO |
2011010274 | Jan 2011 | WO |
2011045776 | Apr 2011 | WO |
2011047895 | Apr 2011 | WO |
2011051002 | May 2011 | WO |
2011069805 | Jun 2011 | WO |
2011072888 | Jun 2011 | WO |
2011092011 | Aug 2011 | WO |
2011095928 | Aug 2011 | WO |
Entry |
---|
“Flexible, Compact and with a High Performance—the New Valvario, G. Kromschroder AG Launches it's New, Improved Series of Gas Fittings,” Press Release, 2 pages, 2003. |
“Large-Scale Linearization Circuit for Electrostatic Motors” IBM Technical Disclosure Bulletin, IBM Corporation, vol. 37, No. 10, pp. 563-564, Oct. 1, 1994. |
ASCO RedHat, “2-Way Normally Closed General Purpose & Watertight Enclosure Gas Shutoff Valves ¾″ to 3″ NPT, 2/2 Series 8214 (200) AH(E) V710(B),” 6 pages, prior to Dec. 15, 2011. |
ASCO RedHat, “2-Way Normally Closed General Purpose & Watertight Enclosure Gas Shutoff Valves ¾″ to 3″ NPT, 2/2 Series 8214 (200),” 8 pages, prior to Dec. 15, 2011. |
ASCO Valve, Inc., “8290 Series Angle Body Piston Valves, Introducing the All New 8290 Assembly Configurator,” 12 pages, prior to Dec. 15, 2011. |
ASCO, “2-Way Normally Closed V710(B) Valve Body Pipe Sizes ¾″ to 3″ NPT, Series V710(B),” 4 pages, prior to Dec. 15, 2011. |
ASCO, “On/Off General Purpose & Watertight Hydramotor Actuator for Use with V710 Gas Valve Body, Series AH2E,” 2 pages, prior to Dec. 15, 2011. |
Athavale et al., “Coupled Electrostatics-Structures-Fluidic Simulations of a Bead Mesopump,” Proceedings of the International Mechanical Engineers Congress & Exhibition, pp. 1-7, Oct. 1999. |
Bertz et al., “Silicon Grooves With Sidewall Angles Down to 1° made by Dry Etching,” pp. 331-339, prior to Dec. 29, 2004. |
Bonne et al. “Actuation-Based Fuel Gas Microsensors,” IGT Symposium on Natural Gas Quality, Energy Measurement, Metering and Utilization Practices, 17 pages, Mar. 2001. |
Branebjerg, “A New Electrostatic Actuator Providing Improved Stroke Length and Force,” IEEE, pp. 6-11, Feb. 4-7, 1992. |
Bustgens et al., “Micropump Manufactured by Thermoplastic Molding,” IEEE, pp. 18-21, 1994. |
Cabuz et al., “Factors Enhancing the Reliability of Touch-Mode Electrostatic Actuators,” Sensors and Actuators 79, pp. 245-250, 2000. |
Cabuz et al., “Mesoscopic Sampler Based on 3D Array of Electrostatically Activated Diaphragms,” Proceedings of the 10th Int. Conf. On Solid-State Sensors and Actuators, Transducers 1999. |
Cabuz et al., “The Dual Diaphragm Pump,” 4 pages prior to Dec. 29, 2004. |
Cabuz, “Dielectric Related Effects in Micromachined Electrostatic Actuators,” IEEE, 1999 Conference on Electrical Insulation and Dielectric Phenomena, pp. 327-332, 1999. |
Cabuz, “Electrical Phenomena at the Interface of Rolling-Contact, Electrostatic Actuators,” 16 pages, prior to Dec. 29, 2004. |
Cabuz, et al., “High Reliability Touch-Mode Electrostatic Actuators”, Technical Digest of the Solid State Sensor and Actuator Workshop, Hilton Head, S.C., pp. 296-299, Jun. 8-11, 1998. |
Cabuz. “Tradeoffs in MEMS Materials,” SPIE, vol. 2881, pp. 160-170, prior to Dec. 29, 2004. |
Carlisle, “10 Tips on Valve-Proving Systems,” Karl Dungs Inc., 5 pages, Aug. 1, 2002, printed May 23, 2012. |
European Search Report for EP Application No. 12196394.6 dated May 23, 2013. |
European Search Report for EP Application No. 12196396.1 dated Jun. 11, 2013. |
European Search Report for EP Application No. 12196398.7 dated Jun. 11, 2013. |
Examination Report for EP Application No. 12196398.7, dated Apr. 11, 2014. |
CSA, “B149.3S1-07 Supplement No. 1 to CAN/CAS-B149.3-05 Code for the Field Approval of Fuel-Related Components on Appliances and Equipment,” 40 pages, Jan. 2007. |
Dungs Combustion Controls, “Double Solenoid Valve Combined Pressure Regulator and Safety Valves Infinitely Variable Operating Mode, MBC- . . . -VEF DN65—DN100,” 8 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “Double Solenoid Valve Combined Pressure Regulator and Safety Valves Servo Pressure Regulator, MBC- . . . -SE DN 65 DN 125,” 8 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “Double Solenoid Valve Control and Safety Combination Valve Servo Pressure Controller, DMV-SE 507/11—525/11,” 8 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “Double Solenoid Valve Regulator and Safety Combination Infinitely Variable Floating Operation, DMV-VEF 507-525,” 8 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “Gas/Air Ratio Control MB-VEF, DMV-VEF,” 15 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “GasMultiBloc Combined Regulator and Safety Shut-Off Valves Two-Stage Function, MB-ZRD(LE) 415-420 B01,” pp. 1-6, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “GasMultiBloc Combined Regulator and Safety Valve Infinitely Variable Air/Gas Ratio Control Mode, MBC-300-VEF, MBC-700-VEF, MBC-1200-VEF,” 8 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “GasMultiBloc Combined Servo Pressure Regulator and Safety Shut-Off Valves, MBC-300-SE, MBC-700-SE, MBC-1200-SE, MBC-300-N, MBC-700-N,” 8 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “Pressure Regulator FRN Zero Pressure Regulator,” 4 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “Pressure Regulator FRS,” 6 pages prior to Dec. 15, 2011. |
Dungs Combustion Controls, “Pressure Regulator FRU Circulation Regulator,” 4 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “Pressure Switch for Gas, Air, Flue Gases and Combustion Products, GW 500 A4, GW 500 A4/2” 6 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “Program,” 4 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “Valve Testing System VPS 504 for Multiple Actuators,” 12 pages, prior to Dec. 15, 2011. |
Dungs Combustion Controls, “Valve Testing System VPS 508 for Multiple Actuators,” 12 pages, prior to Dec. 15, 2011. |
Freund et al., “A Chemically Diverse Conducting Polymer-Based ‘Electronic Nose’,” Proceedings of the National Academy of Sciences of the United States of America, vol. 92, No. 7, pp. 2652-2656, Mar. 28, 1995. |
Halg, “On a Nonvolatile Memory Cell Based on Micro-Electro-Mechanics,” IEEE pp. 172-176, 1990. |
Honeywell Inc., “Hall Effect Sensing and Application,” 126 pages, prior to Dec. 15, 2011. |
Honeywell, “RM7800L1087; RM7840G1022,L1075,L1091; EC7840L1014 Relay Modules with Valve Proving,” Installation Instructions, 32 pages, 2009. |
Korte et al., “Smart Valve Positioners and Their Use in Safety Instrumented Systems,” Industrial Valves, pp. 41-47, 2009. |
Kromschroder, “Governor with Solenoid Valve VAD Air/Gas Ratio Control with Solenoid Valve VAG,” 24 pages, prior to Dec. 15, 2011. |
Kromschroder, “Governor with Solenoid Valve VAD Air/Gas Ratio Control with Solenoid Valve VAG,” 8 pages, prior to Dec. 15, 2011. |
Kromschroder, “Solenoid Valves for Gas VAS,” 28, pages, prior to Dec. 15, 2011. |
Kromschroder, “Solenoid Valves for Gas VAS,” 8 pages, prior to Dec. 15, 2011. |
Kromschroder, “Tightness Control TC,” 8 pages, 2011. |
Allgemein Grundlagen and Anforderungen, EN ISO 5167-1, German Translation, Chapter 3.3.6, p. 8, 2003. |
A Communication of a Letter from the Opponent for EP Application No. 12196398.7 dated Feb. 9, 2017. |
A Communication of Notice of Opposition for EP Application No. 12196398.7 dated Feb. 15, 2016. |
Office Action for EP Application No. 14194824.0 dated Jun. 23, 2017. |
The Response to Opposition for EP Application No. 12196398.7 dated Jul. 15, 2016. |
https://en.wikipedia.org/wiki/SCADA, SCADA—Wikipedia the Free Encyclopedia, 11 pages, printed Mar. 29, 2016. |
Minami et al., “Fabrication of Distributed Electrostatic Micro Actuator (DEMA).” IEEE Journal of Microelectromechanical Systems, vol. 2, No. 3, pp. 121-127, Sep. 1993. |
Ohnstein et al., “Micromachined Silicon Microvalve,” IEEE, pp. 95-98, 1990. |
Porex Technologies, brochure, 4 pages, prior to Dec. 29, 2004. |
Shikida et al., “Characteristics of an Electrostatically-Driven Gas Valve Under High Pressure Conditions,” IEEE, pp. 235-240, 1994. |
Shikida et al., “Electrostatically Driven Gas Valve With High Conductance,” IEEE Journal of Microelectromechanical Systems, vol. 3, No. 2, pp. 76-80, Jun. 1994. |
Shikida et al., “Fabrication of an S-Shaped Microactuator,” IEEE Journal of Microelectromechanical Systems, vol. 6, No. 1, pp. 18-24, Mar. 1997. |
Siemens Building Technologies, “Double Gas Valves VGD20 . . . , VGD40 . . . ,” 12 pages, Aug. 5, 2002. |
Siemens Building Technologies, Inc., “Siemens Technical Instructions Document No. 155-512P25VG . . . ,” 12 pages, Aug. 11, 2005. |
Siemens Building Technologies, Inc., “SKP . . . 15U.. Gas Valve Actuator with Safety Shutoff Function,” Document No. 155-751 SKP15 . . . U.., 5 pages, Jul. 1, 2005. |
Siemens Building Technologies, Inc., “SKP25 . . . U.. Air/Gas Ratio Controlling Gas Valve Actuator with Safety Shutoff Function,” Technical Instructions Document No. 155-754, SKP25 . . . U, 9 pages, Jul. 1, 2005. |
Siemens Building Technologies, Inc., “SKP25 . . . U.. Pressure Regulating Gas Valve Actuator with Safety Shut-Off Function,” Technical Instructions Document No. 155-752, SKP25 . . . U, 7 pages, Jul. 1, 2005. |
Srinivasan et al., “Self-Assembled Fluorocarbon Films for Enhanced Stiction Reduction”, IEEE Transducers, 1997 International Conference on Solid-State Sensors and Actuators, Chicago, pp. 1399-1402, Jun. 16-19, 1997. |
Universal Metering, “SmartValve Wireless Shut-Off Valve,” Universal Metering Ltd., 4 pages, prior to Mar. 12, 2013. |
Wagner et al., “Bistable Microvalve with Pneumatically Coupled Membranes,” IEEE, pp. 384-388, 1996. |
Wilkerson, “Understanding Valve Actuatior Diagnostics,” Control Engineering, vol. 56, No. 11, 4 pages, Nov. 2009. |
www.combustion911.com/products/valve-proving-controls-tc-410.html, “Kromschroeder Valve Proving Controls TC410,” 7 pages, prior to Dec. 15, 2011, printed May 23, 2012. |
Yang et al., “Fluorescent Porous Polymer Films as TNT Chemosensors: Electronic and Structural Effects”, J. Am. Chem. Soc., pp. 11864-11873, 1998. |
Yang et al., “Porous Shape Persistent Fluorescent Polymer Films: An Approach to TNT Sensory Materials”, J. Am. Chem. Soc., pp. 5321-5322, 1998. |
Number | Date | Country | |
---|---|---|---|
20170115002 A1 | Apr 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13326523 | Dec 2011 | US |
Child | 15397590 | US |