Mass Flow Controllers and Controller Algorithms

Through the linear control system, the flow and valve modeling is used to solve the problem of unstable flow control in the existing technology, fast and accurate flow control is achieved, non-linear response is reduced, and system stability and response are improved. Time consistency.

CN113272759BActive Publication Date: 2024-11-22ILLINOIS TOOL WORKS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980070259.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-08-29
Filing Date
2019-08-28
Publication Date
2024-11-22
Estimated Expiration
2039-08-28

Smart Images

  • Figure CN113272759B_ABST
    Figure CN113272759B_ABST
Patent Text Reader

Abstract

A mass flow controller includes a linearization system for controlling the linear response of a valve so as to control the gain of the mass flow controller. The linearization system includes a flow modeling system for processing at least one of a fluid type, flow rate, pressure and temperature value signal related to the fluid flow through a flow path and determining fluid properties. The linearization system also includes a valve modeling system for determining the required operating characteristics of the valve based on the valve specification, the desired flow rate and the determined fluid properties. The linearization system determines the gain for controlling the lift of the valve to obtain the desired fluid flow rate. The gain is determined by calculating the derivative of the predicted lift with respect to the fluid flow rate and the derivative of the drive with respect to the predicted lift.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. non-provisional patent application 16 / 116,780, filed on August 29, 2018, entitled “Mass Flow Controller and Controller Algorithm,” the entire contents of which are hereby fully incorporated by reference for all purposes. Technical Field

[0003] The present disclosure relates generally to mass flow controllers (MFCs) for controlling fluid flow through a flow path, and more particularly to an MFC and controller algorithm for controlling the gain of a mass flow controller by controlling the linear response of a mass flow controller valve. Background Art

[0004] An MFC is a device used to control the flow of a fluid through a flow path based on a desired flow rate and real-time feedback measurements of the measured fluid's temperature, pressure, and flow rate. To control this process and maintain the desired flow rate, a mass flow controller electromechanically controls the opening and closing of a valve based on feedback measurements to achieve the desired flow rate. Currently, available MFCs lack the complexity required to maintain a limited level of control to continuously maintain the desired flow rate without introducing noise into the system due to various nonlinear artifacts. Summary of the invention

[0005] In an embodiment, a mass flow controller for controlling the flow of a fluid is provided. The mass flow controller includes: an inlet for receiving the fluid; a valve actuator, the valve actuator is connected to a valve, and is used to adjust the flow of the fluid flowing out of the outlet of the mass flow controller by controlling the operation of the valve; at least one sensor, the at least one sensor is used to measure at least one of the fluid type, pressure and temperature value signals related to the flow of the fluid through the flow path; and a linearization control system, the linearization control system is connected to the valve actuator, and is used to control the gain of the mass flow controller by controlling the linear response of the valve using the desired fluid flow and the at least one signal value; wherein the linear response is controlled by determining the change of the actuator drive value and the flow change dDrive / dFlow of the fluid.

[0006] In this embodiment, the linearized control system further includes: a flow modeling system, which is used to determine the fluid properties according to the at least one value signal; and a valve modeling system, which is used to determine the required operating characteristics of the valve according to the valve specifications and the determined fluid properties. The valve modeling system is further configured to: determine a drive value for controlling the lift of the valve to obtain the desired fluid flow; wherein the drive value is determined by the relationship between the valve lift for the change in fluid flow. The linearized control system is configured to: scan the drive value for the valve stored in the memory device of the mass flow controller; determine the corresponding flow value based on the pressure and the temperature value signal; convert the determined flow value into a lift value; and determine the relationship between the drive value and the lift value for a given change in flow. The mass flow controller also includes a memory module for storing multiple drive values ​​and lift values ​​of the valve. The linearized control system is configured to: use g'(x)=(Y2-Y1) / (X2-X1) to determine the derivative of the lift-flow relationship for the flow; use f'(g(x))=A*lift x 3 +B*lift x 2 +C*lift x +D to determine the actuator gain as a function of lift; and dY / dx=f'(g(x))g'(x) to determine the gain; where X1 and X2 are flow values, and Y1 and Y2 are corresponding lift values. Y1 and Y2 are calculated lift values ​​corresponding to approximately + / - 1% of the flow values ​​X1 and X2.

[0007] In yet another embodiment, a method for controlling the flow of a fluid through a mass flow controller is provided. The method includes: receiving the fluid through an inlet; regulating the flow of the fluid out of the outlet of the mass flow controller by controlling the operation of the valve using a valve actuator; receiving a desired fluid flow rate and receiving at least one of a pressure, a temperature value, a flow rate, and a fluid type signal related to the flow of the fluid through a flow path from at least one sensor; and controlling the gain of the mass flow controller by controlling the linear response of the valve using the at least one signal value; wherein the linear response is controlled by determining a change in the actuator drive value and a flow change dDrive / dFlow of the fluid. The method further includes: determining a fluid property based on the at least one value signal; and determining a desired operating characteristic of the valve based on the valve specification and the determined fluid property. The method further includes: determining a drive value for controlling the lift of the valve to obtain the desired fluid flow rate; wherein the drive value is determined by the relationship between the valve lift for the fluid flow change. The method further includes: scanning the drive value of the valve stored in the memory unit of the mass flow controller; determining the corresponding flow value based on the pressure and temperature value signal; converting the determined flow value into a lift value; and determining the relationship between the drive value and the lift value for a given change in flow. The method further includes storing multiple drive values ​​and lift values ​​of the valve in a memory module. The method also includes: using g'(x)=(Y2-Y1) / (X2-X1) to determine the derivative of the lift-to-flow relationship for flow; using f'(g(x))=A*lift x 3 +B*lift x 2 +C*lift x +D to determine the actuator gain as a function of lift; and dY / dx=f'(g(x))g'(x) to determine the gain; where X1 and X2 are flow values, and Y1 and Y2 are corresponding lift values. Y1 and Y2 are calculated lift values ​​corresponding to approximately + / - 1% of the flow values ​​X1 and X2.

[0008] In yet another embodiment, a process control system for use in a mass flow controller is provided. The control system includes: a linearization module, the linearization module is communicatively coupled to a valve actuator and a memory device, the linearization module controls the gain of the mass flow controller by controlling the linear response of the valve using a desired fluid flow rate and at least one of a pressure, a temperature value, a flow rate, and a fluid type related to the flow rate of the fluid through a flow path from at least one sensor. The linearization module further includes: a flow modeling system, the flow modeling system is used to determine the fluid property based on the at least one value signal; and a valve modeling system, the valve modeling system is used to determine the required operating characteristics of the valve based on the valve specification and the determined fluid property. The linear response is controlled by determining a change in the actuator drive value and a change in the flow rate of the fluid. The valve control system is further configured to: scan the drive value of the valve stored in the memory unit of the mass flow controller; determine a corresponding flow value based on the pressure and temperature value signals; convert the determined flow value into a lift value; and determine a relationship between the drive value and the lift value for a given change in flow. The linearization module is further configured to: determine the derivative of the lift and flow relationship for flow using g'(x)=(Y2-Y1) / (X2-X1); determine the derivative of the lift and flow relationship for flow using f'(g(x))=A*lift x 3 +B*lift x 2 +C*lift x +D to determine the actuator gain as a function of lift; and dY / dx=f'(g(x))g'(x) to determine the gain; where X1 and X2 are flow values, and Y1 and Y2 are corresponding lift values. Where Y1 and Y2 are calculated lift values ​​corresponding to approximately + / - 1% of the flow values ​​X1 and X2.

[0009] Additional embodiments, advantages and novel features are set forth in the detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] For a more complete understanding of the features and advantages of the present disclosure, reference is now made to the detailed description taken in conjunction with the accompanying drawings, wherein corresponding reference numerals in the different drawings represent corresponding parts, and wherein:

[0011] Figure 1 is an illustration of a block diagram of an MFC according to certain example embodiments;

[0012] Figure 2 is a diagram of a controller system for controlling a linear response of a control valve of an MFC according to certain example embodiments;

[0013] Figure 3Ais a diagram of a valve and fluid flow modeling algorithm for a controller system according to certain example embodiments;

[0014] Figure 3B is a diagram of a fluid flow control algorithm of a controller system according to certain example embodiments;

[0015] Figure 4A is a graphical representation of a control command filtered ramp signal after having passed through a filtering process of a controller system in accordance with certain example embodiments;

[0016] Figure 4B is an illustration of a performance graph illustrating precision process control of a filtered set point value associated with an associated process signal, according to certain example embodiments;

[0017] Figure 4C is a graphical representation of a performance graph of a pressure-based MFC response time versus set point value for different controller system settings; and

[0018] Figure 5 is a block diagram depicting computing machines and system applications, according to certain example embodiments. DETAILED DESCRIPTION

[0019] Although the manufacture and use of various embodiments of the present disclosure are discussed in detail below, it should be understood that the present disclosure provides many applicable inventive concepts that can be embodied in many specific contexts. The specific embodiments discussed herein are illustrative only and do not limit the scope of the present disclosure. For the sake of clarity, all features of the actual implementation may not be described in this disclosure. Of course, it should be understood that in the development of any such actual embodiment, many decisions specifically for the implementation must be made to achieve the specific goals of the developer, such as complying with system-related constraints and business-related constraints, which will vary from implementation to implementation. In addition, it should be understood that such development work may be complex and time-consuming, but it will be routine work for those of ordinary skill in the art who benefit from the present disclosure.

[0020] The MFC and control algorithms provided herein have many practical applications, for example, when used in the field of semiconductor processing, the MFC and control algorithms provide significant advantages. These control algorithms provide advantages over traditional MFCs, for example, by implementing the control algorithms, fast, accurate and consistent transient response characteristics are achieved over the entire control range and under all operating conditions. The control algorithms provided herein include flow control algorithms, flow modeling algorithms and valve modeling algorithms, which together can significantly improve MFC operation by providing accurate linear response control of MFC valve operation. In addition, set point control command input filtering can increase stability and consistency to control unwanted nonlinear transient responses.

[0021] The control algorithm can be completely self-contained in the MFC. Such an advantage is that when different fluid types are configured and when actual temperature, pressure and flow rate change, the fluid properties can be modeled in real time. Another advantage of this is that the fluid properties provided by the flow modeling algorithm can be used to establish the relationship between the desired valve opening of the desired flow rate and the drive signal required to achieve the flow rate. The flow control algorithm described herein can be a gain-lead-lag (GLL) controller, a form of a PID controller that combines variable and dynamic gain inputs (hereinafter referred to as GLL gain) for linearizing the plant gain of the system, which is the derivative of the feedback signal relative to the output of the controller. An alternative method for performing non-real-time GLL gain calculations is to use an offline two-dimensional table and external software. The undesirable attribute of this embodiment is that the generation of the GLL gain table is based on a predefined pressure range and temperature rather than based on actual temperature and pressure, the two-dimensional gain table requires a large amount of storage, and it may be time-consuming to create the table.

[0022] The flow modeling algorithm and valve modeling algorithm implemented in the MFC firmware provide significant advantages. For example, GLL gain calculations can be performed on each processing cycle. No table generation is required. The valve modeling algorithm can process pressure, temperature and fluid rate in real time, and therefore, the flow of different fluid types can be managed more accurately. The GLL gain is essentially the drive change required for a given change in flow. The GLL gain can be expressed as 1 / (dFlow / dDrive), or simply expressed as dDrive / dFlow. Since the GLL gain can be expressed as dDrive / dFlow, the relationship between drive and flow can be determined. Using the valve modeling algorithm, lift can be determined by flow, and vice versa, which will be discussed in more detail below.

[0023] In addition, due to the fast response time of the pressure transducer, the transient flow control response time can be specified to a tighter tolerance. For example, the transient flow response time can be controlled within 200ms + / - 10ms. This is a significant improvement over conventional systems. This can be accomplished using various filtering functions on the flow controller command input. Another advantage of command filtering is that the GLL controller now only needs to control small errors between the command input and the process variable, so the GLL controller can be tuned to be more responsive without affecting stability. Without command filtering, any change in the command input will cause the GLL controller to have a large and instantaneous error. Yet another advantage is that a means is provided to easily provide tiered response times with little time and effort. Traditionally, when tighter transient response time tolerances or generally faster transient response times are required, a lot of time and effort is often required to perfect numerous tuning parameters to obtain the desired results. In most cases, with command filtering, this can be done quickly and easily by adjusting a single attribute.

[0024] Now refer to Figure 1 , shows a block diagram of an MFC, generally designated 100, according to certain example embodiments. The MFC 100 may include a stage 102, a mass flow meter 104, and a valve assembly 106 including a valve 108 and an actuator 110, all of which may be mounted on the stage 102 between a fluid inlet 114 and a fluid outlet 116. The MFC 100 may further include a valve control system 118 communicatively coupled between the mass flow meter 104 and the valve assembly 106. Additionally, the mass flow controller 100 may include an inlet pressure transducer 120 and an outlet pressure transducer 122 coupled to the flow path at an upstream location and a downstream location and communicatively coupled to the valve control system 118. The mass flow meter 104 may include a bypass channel 124 through which the fluid flows and another channel having a flow sensor 126 through which a smaller portion of the fluid flows. In addition, the mass flow controller 100 can use thermal mass flow sensors to measure temperature and flow, but other sensor types can be used, including Coriolis-based sensors and differential pressure sensors. Coriolis-based sensors can determine mass flow independently of temperature, flow distribution, density, viscosity, and uniformity.

[0025] In practice, as the fluid flows through the pressure transducers 120 and 122 and the flow sensor 126, real-time pressure data, flow data, and temperature data may be provided to the valve control system 118. The flow rate of the fluid may be sensitive, and many operating conditions (including fluid type, inlet and outlet pressures, temperature, flow set point values, and valve operating characteristics) may affect the flow rate of the fluid, i.e., cause the flow rate to deviate from the desired set flow rate. The valve control system 118 may control the operation of the valve 10 in real time by providing an error correction drive signal to the valve actuator 110, thereby adjusting the valve 108 and the flow rate based on the fluid type, the readings of the inlet and outlet pressure transducers, the flow set point value, and the valve specifications to control the operation of the valve 108. Feedback control methods (such as proportional control, integral control, proportional-integral (PI) control, differential control, proportional-derivative (PD) control, integral-derivative (ID) control, and proportional-integral-derivative (PID) control) may be used to control the flow rate of the fluid in the mass flow controller.

[0026] Now refer to Figure 2 , shows an MFC controller system, generally designated 200, for controlling the linear response of a control valve 170 according to certain example embodiments. The controller system 200 executes a control algorithm to more accurately control the gain of the MFC 100, the control algorithm including a flow modeling algorithm, a valve modeling algorithm, and a flow control algorithm. The controller system 200 includes a set point (SP) filter 202, a gain-lead-lag (GLL) controller 204, and a flow control and modeling system 206. The GLL controller 204 receives an SP value and a feedback (FB) signal, such as pressure or temperature or both, for controlling the response of the valve 170. The flow control and modeling system 206 enhances the tuning of the GLL controller 204 by further controlling its response based on the SP command, sensor input data, and valve specifications. By filtering the set point value before processing and using these modeling algorithms during processing, the response time of the valve 170 can be more tightly controlled and the response time of the valve 170 can be more consistent under various operating conditions. Furthermore, by properly filtering the set point values ​​prior to processing, non-linear transient artifacts that affect valve response time can be eliminated or significantly reduced.

[0027] The SP filter 202 filters the received set point (SP) value and sends the filtered value to the GLL controller 204 and the modeling and flow control system 206. The SP value can be a fluid flow value. The SP filter 202 can include a configurable rate limiting filter (such as a slew rate limiting filter) and a low-pass filter to ensure that the command change rate does not change suddenly and discontinuously. By delaying the set point, the processing of the set point data and the measurement results is more accurate, and therefore, nonlinear transient artifacts can be significantly reduced or eliminated. The GLL controller 204 acts by providing a drive command to the valve actuator 208 to control the lift of the valve 170. The modeling and flow system 206 receives the SP value, as well as the real-time measurement results of the inlet / outlet pressure value, temperature value, and fluid type value. The modeling and flow system 206 can access and process the valve specification data, and based on the determined fluid modeling characteristics and valve specification data, the appropriate gain can be determined and the lift of the valve 170 can be controlled accordingly.

[0028] Now refer to Figure 3A , shows a valve and fluid flow modeling algorithm according to certain example embodiments, generally indicated as 250. Algorithm 250 begins at block 252, where filtered SP values ​​are read. These SP values ​​can be provided by the user, or programmed into the MFC and adjusted regularly based on usage. At block 254, the drive value of a particular valve is scanned to determine the corresponding flow value at a given pressure and temperature. At block 256, algorithm 250 converts the determined flow into a predicted lift value using the available valve specifications. At block 258, the relationship between drive and lift for a given change in flow (i.e., GLL gain) is calculated.

[0029] Introducing the filtered SP value eliminates or significantly reduces the overshoot that causes nonlinear transient effects and allows the GLL gain to be more accurately determined based on pressure and (optionally) other environmental readings. As shown in the table below, no overshoot was detected within the range of filtered set point values ​​and gain calculation results for a set of fluid measurement readings.

[0030]

[0031] Table - Transient Response Time Performance

[0032] The GLL gain can be defined as the inverse of the controlled plant gain. The controlled plant gain can be defined as the derivative of the feedback control signal indicative of fluid flow relative to the output (i.e., drive) of the GLL controller. A constant loop gain can be achieved by appropriately filtering the set point value and setting the GLL gain equal to the inverse of the controlled plant gain. In this way, a consistent valve response time can be achieved under a variety of operating conditions (e.g., gas, temperature, inlet and outlet pressures, and flow).

[0033] The GLL gain can be expressed as dDrive / dFlow, i.e., the change in drive is a function of the change in flow, and therefore, the appropriate relationship between drive and flow can be determined to more accurately control the response time of the valve. In general, if g(x) is the predicted lift as a function of fluid flow (SCCM) determined from the valve model, f(x) is the controller drive (a fraction of the full-scale drive), and Y is the controller drive as a function of flow, then Y=f(g(x)). The GLL gain, i.e., dDrive / dFlow, can be determined using dY / dx=f'(g(x))g'(x), where f'(g(x)) is the actuator gain, i.e., dDrive / dLift, and g'(x) is the valve model gain, i.e., dLift / dDrive. The actuator gain f'(g(x)) is the derivative of the drive with respect to the predicted lift. A curve of drive versus predicted lift can be obtained using a valve characterization process. The derivative of drive versus predicted lift can be calculated to generate an actuator gain curve. This curve can be represented in any form in the device (e.g., nth order polynomial, piecewise linear function, spine, etc.). The valve model gain g'(x) is a finite difference calculation of the derivative of the predicted lift with respect to the flow around the current operating conditions. This is the case when the error between the flow and the controller set point is close to zero. Depending on the valve model used, the equations involved can be differentiated directly and can be expressed as closed form derivatives. Regardless of the implementation, finite difference calculations or closed form will work equally well.

[0034] Now refer to Figure 3B , shows a fluid flow control algorithm, generally designated 300, according to certain example embodiments. Although the algorithmic approach provided below for determining the GLL gain is effective, it should be understood that other methods of calculating the GLL gain may be used. This is only one method by which the GLL gain may be determined. The fluid flow control algorithm calculates the relationship between the drive value and the lift for a given change in flow. The algorithm begins at block 302 where the lift of the flow is determined to flow using Equation 1:

[0035] g'(x) = (Y2 - Y1) / (X2 - X1) (Equation 1); and

[0036] Where Y1, Y2 are lift values ​​corresponding to + / -1% or approximately + / -1% of the flow X1, X2. X1 and X2 or their difference defines the flow change obtained from the set point value and the actual flow measurement. The lift value can be retrieved from the valve specification stored in the memory. At block 304, the algorithm 300 determines the actuator gain as a function of lift using Equation 2 and Horner's law:

[0037] f'(g(x))=A*liftx 3 +B*lift x 2 +C*lift x +D (Equation 2).

[0038] The coefficients of the derivatives may be stored in memory and retrieved from memory. At block 306, the algorithm 300 determines the GLL gain using Equation 3:

[0039] dY / dx=f'(g(x))g'(x) (Equation 3);

[0040] The corresponding drive signal value is then sent to the GLL controller 204 to control the valve actuator 208 .

[0041] The units of GLL gain may be expressed as fractionalDrive / fractionalFlow. For actual GLL gain calculations, the units used may be expressed as Drive (volts) / Flow (SCCM - standard cubic centimeters per minute). The reason for this expression may be to change the driver full-scale range of the device after characterization or to change the configured full-scale range of the device after characterization. Before using the GLL gain value, the algorithm may perform the necessary conversion of the GLL gain value from Drive (volts) / Flow (SCCM) to fractionalDrive / fractionalFlow. However, the GLL gain units may be expressed as the units that the GLL controller 204 is configured to operate in.

[0042] exist Figure 4A , examples of setpoint commands before and after filtering at filter 202 are shown. The trace depicted as "lpf_ramp" shows the combined ramp signal after passing through the rate limiter and low pass filter. In this case, a ramp time of 200ms combined with a low pass filter with a 20ms time constant produces an output that is within 98% of the final value within 250ms. Figure 4B is an example graph showing the precision process control of the filtered set point value in relation to supply voltage and normalized flow, fractional flow, and filtered SP value. It can be easily seen that the difference or error between the filtered SP value and flow is small to non-existent. Figure 4C, a graph of different response times for percentages of SP values ​​is shown when the controller system 200 does not use the filter 202 and the flow control and modeling system 206 is disabled, when the controller system 200 does not use the filter 202 and the flow control and modeling system 206 is enabled, and when the controller system 200 uses the filter 202 and the flow control and modeling system 206 is enabled. Without using the filter and gain control, the response time at various set points can be between 135ms and 315ms (expanded by 180ms). Enabling gain control improves consistency by a factor of 3. Enabling both SP filtering and gain control provides the best consistency at various set points, within a range of + / -10ms.

[0043] Now refer to Figure 5 , showing a computing machine 400 and a system application module 500 according to an example embodiment. The computing machine 400 may correspond to any of the various computers, mobile devices, laptop computers, servers, embedded systems, or computing systems presented herein. The module 500 may include one or more hardware or software elements, such as other OS applications and user and kernel space applications, which are designed to facilitate the computing machine 400 to perform the various methods and processing functions presented herein. The computing machine 400 may include various internal components or attached components, such as a processor 410, a system bus 420, a system memory 430, a storage medium 440, an input / output interface 450, and a network interface 460 for communicating with a network 470 (e.g., cellular / GPS, Bluetooth, or WIFI).

[0044] The computing machine may be implemented as a conventional computer system, an embedded controller, a laptop computer, a server, a mobile device, a smart phone, a wearable computer, a custom machine, any other hardware platform, or any combination or diversity thereof. The computing machine may be a distributed system configured to operate using multiple computing machines interconnected via a data network or bus system.

[0045] Processor 410 can be designed to execute code instructions to perform the operations and functions described herein, manage request flows and address mappings, and is designed to perform calculations and generate commands. Processor 410 can be configured to monitor and control the operation of components in a computing machine. Processor 410 can be a general-purpose processor, a processor core, a multiprocessor, a reconfigurable processor, a microcontroller, a digital signal processor ("DSP"), an application-specific integrated circuit ("ASIC"), a controller, a state machine, a gated logic, a discrete hardware component, any other processing unit, or any combination or diversity thereof. Processor 410 can be a single processing unit, multiple processing units, a single processing core, multiple processing cores, a dedicated processing core, a coprocessor, or any combination thereof. According to certain embodiments, processor 410 and other components of computing machine 400 can be software-based or hardware-based virtualized computing machines executed in one or more other computing machines.

[0046] System memory 430 may include non-volatile memory, such as read-only memory ("ROM"), programmable read-only memory ("PROM"), erasable programmable read-only memory ("EPROM"), flash memory, or any other device capable of storing program instructions or data with or without the application of power. System memory 430 may also include volatile memory, such as random access memory ("RAM"), static random access memory ("SRAM"), dynamic random access memory ("DRAM"), and synchronous dynamic random access memory ("SDRAM"). Other types of RAM may also be used to implement system memory 430. System memory 430 may be implemented using a single memory module or multiple memory modules. Although system memory 430 is depicted as part of a computing machine, those skilled in the art will recognize that system memory 430 may be separate from computing machine 400 without departing from the scope of the present technology. It should also be understood that system memory 430 may include, or operate in conjunction with, a non-volatile storage device such as storage medium 440.

[0047] Storage medium 440 may include a hard disk, a floppy disk, a compact disk read-only memory (“CD-ROM”), a digital versatile disk (“DVD”), a Blu-ray disk, a magnetic tape, a flash memory, other non-volatile memory devices, a solid-state drive (“SSD”), any magnetic storage device, any optical storage device, any electrical storage device, any semiconductor storage device, any physical-based storage device, any other data storage device, or any combination or diversity thereof. Storage medium 440 may store one or more operating systems, application programs and program modules, data, or any other information. Storage medium 440 may be part of or connected to a computing machine. Storage medium 440 may also be part of one or more other computing machines that communicate with the computing machine, such as a server, a database server, cloud storage, network-attached storage, etc.

[0048] The application module 500 and other OS application modules may include one or more hardware or software elements configured to facilitate the computing machine to perform the various methods and processing functions presented herein. The application module 500 and other OS application modules may include one or more algorithms or instruction sequences stored as software or firmware associated with the system memory 430, the storage medium 440, or both. Therefore, the storage medium 440 may represent an example of a machine or computer readable medium, on which instructions or codes for execution by the processor 410 may be stored. A machine or computer readable medium may generally refer to any one or more media for providing instructions to the processor 410. Such a machine or computer readable medium associated with the application module 500 and other OS application modules may include a computer software product. It should be understood that a computer software product including the application module 500 and other OS application modules may also be associated with one or more processes or methods for delivering the application module 500 and other OS application modules to a computer via a network, any signal bearing medium, or any other communication or delivery technology. The application module 500 and other OS application modules may also include hardware circuits or information for configuring hardware circuits, such as microcode or configuration information for FPGAs or other PLDs. In an exemplary embodiment, the application module 500 and other OS application modules may include algorithms capable of performing the functional operations described by the flowcharts and computer systems presented herein.

[0049] Input / output ("I / O") interface 450 may be configured to be connected to one or more external devices to receive data from one or more external devices and to send data to the one or more external devices. Such external devices, together with various internal devices, may also be referred to as peripheral devices. I / O interface 450 may include both electrical and physical connections for connecting various peripheral devices to computing machine or processor 410. I / O interface 450 may be configured to transmit data, addresses, and control signals between peripheral devices, computing machine, or processor 410. I / O interface 450 may be configured to implement any standard interface, such as small computer system interface ("SCSI"), serial attached SCSI ("SAS"), fiber channel, peripheral component interconnect ("PCI"), PCI express (PCIe), serial bus, parallel bus, advanced technology configuration ("ATA"), serial ATA ("SATA"), universal serial bus ("USB"), Thunderbolt, FireWire, various video buses, etc. I / O interface 450 may be configured to implement only one interface or bus technology. Alternatively, I / O interface 450 may be configured to implement a variety of interface or bus technologies. I / O interface 450 may be configured to operate as part, all, or in conjunction with system bus 420. I / O interface 450 may include one or more buffers for buffering transmissions between one or more external devices, internal devices, computing machines, or processors 410.

[0050] I / O interface 450 can connect the computing machine to various input devices, including a mouse, a touch screen, a scanner, an electronic digitizer, a sensor, a receiver, a touch pad, a trackball, a camera, a microphone, a keyboard, any other pointing device, or any combination thereof. I / O interface 450 can connect the computing machine to various output devices, including a video display, a speaker, a printer, a projector, a tactile feedback device, an automation control, a robotic assembly, an actuator, a motor, a fan, a solenoid valve, a valve, a pump, a transmitter, a signal transmitter, a light, etc.

[0051] The computing machine 400 can operate in a networked environment using logical connections to one or more other systems or computing machines on the network through the NIC 460. The network may include a wide area network (WAN), a local area network (LAN), an intranet, the Internet, a wireless access network, a wired network, a mobile network, a telephone network, an optical network, or a combination thereof. The network may be packet-switched, circuit-switched, of any topology, and may use any communication protocol. The communication links within the network may involve various digital or analog communication media, such as fiber optic cables, free space optics, waveguides, electrical conductors, wireless links, antennas, radio frequency communications, and the like.

[0052] The processor 410 may be connected to other elements of the computing machine or various peripherals discussed herein via a system bus 420. It should be appreciated that the system bus 420 may be internal to the processor 410, external to the processor 410, or both. According to some embodiments, any of the processor 410, other elements of the computing machine, or various peripherals discussed herein may be integrated into a single device, such as a system on a chip (“SOC”), a system on a package (“SOP”), or an ASIC device.

[0053] Embodiments may include computer programs that embody the functions described and shown herein, wherein the computer programs are implemented in a computer system including instructions stored in a machine-readable medium and a processor that executes these instructions. However, it should be clear that there may be many different ways to implement embodiments in computer programming, and unless otherwise disclosed for exemplary embodiments, embodiments should not be interpreted as being limited to any one set of computer program instructions. Further, a skilled programmer will be able to write such a computer program based on the flowcharts, algorithms, and associated descriptions attached in the application text to implement the embodiments in the disclosed embodiments. Therefore, it is considered unnecessary to disclose a specific set of program code instructions for a full understanding of how to make and use the embodiments. Further, it will be understood by those skilled in the art that one or more aspects of the embodiments described herein may be performed by hardware, software, or a combination thereof, such as may be embodied in one or more computing systems. In addition, any reference to an action performed by a computer should not be interpreted as being performed by a single computer, because more than one computer may perform the action.

[0054] The example embodiments described herein can be used with computer hardware and software that perform the previously described methods and processing functions. The systems, methods, and processes described herein can be embodied in a programmable computer, computer executable software, or digital circuitry. The software can be stored on a computer readable medium. For example, a computer readable medium can include a floppy disk, RAM, ROM, hard disk, removable media, flash memory, memory stick, optical media, magneto-optical media, CD-ROM, etc. The digital circuitry can include an integrated circuit, a gate array, a building block logic, a field programmable gate array (FPGA), etc.

[0055] The exemplary systems, methods, and actions described in the previously presented embodiments are illustrative, and in alternative embodiments, certain actions may be performed in a different order, performed in parallel with each other, omitted entirely, and / or combined between different example embodiments, and / or certain additional actions may be performed without departing from the scope and spirit of the various embodiments. Such alternative embodiments are therefore included in the description herein.

[0056] As used herein, the singular forms "one", "an" and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It should be further understood that the terms "include" and / or "comprise" used in this specification specify the presence of stated features, integrators, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integrators, steps, operations, elements, parts, and / or their collections. As used herein, the term "and / or" includes any and all combinations of one or more items in the associated listed items. As used herein, phrases such as "between X and Y" and "between about X and Y" should be interpreted as including X and Y. As used herein, phrases such as "between about X and Y" refer to "between about X and about Y". As used herein, phrases such as "from about X to Y" refer to "from about X to about Y".

[0057] As used herein, "hardware" may include a combination of discrete components, integrated circuits, application specific integrated circuits, field programmable gate arrays, or other suitable hardware. As used herein, "software" may include one or more objects, media, threads, lines of code, subroutines, separate software applications, two or more lines of code, or other suitable software structures operated in two or more software applications on one or more processors, wherein the processor includes one or more microcomputers or other suitable data processing units, memory devices, input-output devices, displays, data input devices such as keyboards or mice, peripheral devices such as printers and speakers, associated drivers, control cards, power supplies, network devices, docking station devices, or other suitable devices operated in conjunction with processors or other devices under the control of a software system, or other suitable software structures. In an exemplary embodiment, software may include one or more lines of code or other suitable software structures running in a general-purpose software application (e.g., an operating system), and one or more lines of code or other suitable software structures operating in a special-purpose software application. As used herein, the term "connection" and its cognate terms (such as "couple" and "coupled") may include physical connections (such as copper conductors), virtual connections (such as through randomly assigned memory locations of a data storage device), logical connections (such as through logic gates of a semiconductor device), other suitable connections, or suitable combinations of such connections. The term "data" may refer to suitable structures for using, transmitting, or storing data, such as data fields, data buffers, data messages having data values ​​and sender / receiver address data, control messages having data values ​​and one or more operators that cause a receiving system or component to perform a function using the data, or other suitable hardware or software components for electronic processing of data.

[0058] Generally, a software system is a system that operates on a processor to perform a predetermined function in response to a predetermined data field. For example, a system can be defined by the function performed by the system and the data field where the function is performed. As used herein, a NAME system (wherein NAME is typically the name of a general function performed by the system) refers to a software system that is configured to operate on a processor and perform the disclosed function on a disclosed data field. Unless a specific algorithm is disclosed, any suitable algorithm known to those skilled in the art for performing functions using associated data fields falls within the scope of the present disclosure. For example, a message system that generates a message including a sender address field, a receiver address field, and a message field will include software running on a processor, which can obtain a sender address field, a receiver address field, and a message field from a suitable system or device (e.g., a buffer device or a buffer system) of the processor, can combine the sender address field, the receiver address field, and the message field into a suitable electronic message format (such as an email message, a TCP / IP message, or any other suitable message format with a sender address field, a receiver address field, and a message field), and can use the processor's electronic message transceiving system and device to send an electronic message through a communication medium (e.g., a network). Those of ordinary skill in the art will be able to provide specific coding for specific applications based on the foregoing disclosure, which is intended to illustrate exemplary embodiments of the present disclosure rather than to provide tutorials for those less professional than those skilled in the art, such as those who are not familiar with programming in a suitable programming language or processor. Specific algorithms for performing functions may be provided in the form of a flowchart or other suitable format, wherein data fields and related functions may be illustrated in an exemplary order of operations, wherein the order may be rearranged appropriately, and unless expressly stated to be limiting, it is not intended to be limiting.

[0059] For the purpose of illustration and description, the foregoing description of the embodiments of the present disclosure has been presented. It is not intended to be exhaustive or to limit the present disclosure to the precise form disclosed, and in view of the above teachings, modifications and variations are possible, or can be obtained from the practice of the present disclosure. The embodiments are selected and described to explain the principles of the present disclosure and its practical application, so that those skilled in the art can utilize the present disclosure in various embodiments, and have various modifications suitable for the specific purposes considered. Without departing from the scope of the present disclosure, other replacements, modifications, changes and omissions can be made in the design, operating conditions and arrangement of the embodiments. With reference to this specification, such modifications and combinations of the illustrative embodiments and other embodiments will be obvious to those skilled in the art. Therefore, the appended claims are intended to cover any such modifications or embodiments.

Claims

1. A mass flow controller for controlling the flow rate of a fluid, the mass flow controller comprising: an inlet, the inlet being used to receive the fluid; a valve actuator coupled to a valve for regulating the flow rate of the fluid out of an outlet of the mass flow controller by controlling operation of the valve; at least one sensor for measuring at least one of a fluid type, a pressure, and a temperature, the fluid type, the pressure, and the temperature being related to a flow rate of the fluid through a flow path; as well as a linearization control system coupled to the valve actuator for determining a gain value of the mass flow controller to control a linear response of the valve actuator using a desired fluid flow rate and using at least one of the fluid type, the pressure, and the temperature; The linearized control system determines the gain value based on the filtered flow set point value, at least one real-time fluid parameter value, valve model data, actuator gain and valve model gain, and is characterized in that the linearized control system further comprises: a flow modeling system for determining fluid properties based on measurements of the fluid type, the pressure, and the temperature; and a valve modeling system for determining desired operating characteristics of the valve based on the valve specification and the determined fluid properties; and Wherein, the valve modeling system is further configured as follows: determining a driving value for controlling the lift of the valve to obtain the desired fluid flow rate; Therein, the drive value is determined based on the desired operating characteristic.

2. The mass flow controller according to claim 1, wherein: The linearized control system is configured as follows: scanning an actuation value for the valve stored in a memory device of the mass flow controller; determining a corresponding flow value based on the pressure and the temperature; converting the determined flow value into a lift value; and The relationship between the drive value and the lift value for a given change in flow is determined.

3. The mass flow controller of claim 2, further comprising a memory module for storing a plurality of drive values ​​and lift values ​​for the valve.

4. The mass flow controller according to claim 3, wherein: The linearized control system is configured as follows: use g'(x) = (Y2 - Y1) / (X2 - X1) to determine the derivative of the lift versus flow relationship for flow; use f'(g(x)) = A*lift x 3 + B*lift x 2 + C*lift x + D to determine an actuator gain as a function of lift; and use dY / dx = f'(g(x))g'(x) To determine the controller gains; Where X1 and X2 are flow values, Y1 and Y2 are lift values ​​corresponding to the flow values ​​X1, X2, Y is the controller drive, and A, B, C, D are coefficients of the derivatives.

5. The mass flow controller according to claim 1, wherein: The gain value is given by dY / dx = f'(g(x))g'(x) Definition, where Y It is controller driven. f'(g(x)) is the actuator gain, and g'(x) is the valve model gain.

6. A method for controlling the flow rate of a fluid by means of a mass flow controller, the method comprising: receiving the fluid through an inlet; regulating the flow rate of the fluid out of an outlet of the mass flow controller by controlling operation of the valve using a valve actuator; receiving a desired fluid flow rate; receiving a measurement of at least one of a pressure, a temperature, a flow rate, and a fluid type from at least one sensor, the pressure, the temperature, the flow rate, and the fluid type being related to the flow of the fluid through a flow path; as well as controlling a gain of the mass flow controller by controlling a linear response of the valve using at least one of the pressure, the temperature, the flow rate, and the fluid type; The linear response is achieved by determining the change in the actuator drive value and the change in the flow rate of the fluid. dDrive / dFlow to control; Wherein, a gain value of the mass flow controller is determined based on the filtered flow set point value, at least one real-time fluid parameter value, valve model data, actuator gain and valve model gain, and the method further comprises: determining a fluid property based on the pressure, the temperature, the flow rate, and the fluid type; and determining desired operating characteristics of the valve based on the valve specifications and the determined fluid properties; and determining a driving value for controlling the lift of the valve to obtain the desired fluid flow rate; Therein, the drive value is determined based on the desired operating characteristic.

7. The method of claim 6, further comprising: scanning an actuation value for the valve stored in a memory unit of the mass flow controller; determining a corresponding flow value based on the pressure and the temperature; Convert the determined flow value into a lift value; as well as The relationship between the drive value and the lift value for a given change in flow is determined.

8. The method of claim 7, further comprising storing a plurality of drive values ​​and lift values ​​for the valve in a memory module.

9. The method of claim 7, further comprising: Use g'(x) = (Y2 - Y1) / (X2 - X1) to determine the derivative of the lift-to-flow relationship for flow; Use f'(g(x)) = A*lift x 3 + B*lift x 2 + C*lift x + D to determine the actuator gain as a function of lift; and Determine the controller gains using dY / dx = f'(g(x))g'(x); Where X1 and X2 are flow values, Y1 and Y2 are lift values ​​corresponding to the flow values ​​X1, X2, Y is the controller drive, and A, B, C, D are coefficients of the derivatives.

10. The method of claim 6, wherein: The gain value is given by dY / dx = f'(g(x))g'(x) Definition, where Y It is controller driven. f'(g(x)) is the actuator gain, and g'(x) is the valve model gain.

11. A process control system for a mass flow controller, the process control system comprising: a linearization module communicatively coupled to the valve actuator and the memory device, the linearization module controlling a gain of the mass flow controller by controlling a linear response of the valve using a desired fluid flow rate and using at least one of a pressure, a temperature, a flow rate, and a fluid type from at least one sensor, the pressure, the temperature, the flow rate, and the fluid type being related to a flow rate of the fluid through a flow path; Characterized in that the linearization module further comprises: a flow modeling system for determining a fluid property based on the pressure, the temperature, the flow rate, and the fluid type; and a valve modeling system for determining desired operating characteristics of the valve based on valve specifications and determined fluid properties, wherein a gain value of the mass flow controller is determined based on a filtered flow set point value, at least one real-time fluid parameter value, valve model data, an actuator gain, and a valve model gain, and wherein the valve modeling system is further configured to: determining a driving value for controlling the lift of the valve to obtain the desired fluid flow rate; Therein, the drive value is determined based on the desired operating characteristic.

12. The process control system of claim 11, wherein: The linear response is determined by determining the change in the actuator drive value and the change in the flow rate of the fluid dDrive / dFlow To control.

13. The process control system of claim 11, wherein: The valve modeling system is further configured to: scanning an actuation value of the valve stored in a memory unit of the mass flow controller; determining a corresponding flow value based on the pressure and the temperature; converting the determined flow value into a lift value; and The relationship between the drive value and the lift value for a given change in flow is determined.

14. The process control system of claim 13, wherein: The memory device stores a plurality of drive values ​​and lift values ​​for the valve.

15. The process control system of claim 13, wherein: The linearization module is further configured to: Use g'(x) = (Y2 - Y1) / (X2 - X1) to determine the derivative of the lift-to-flow relationship for flow; Use f'(g(x)) = A*lift x 3 + B*lift x 2 + C*lift x + D to determine the actuator gain as a function of lift; and Determine the gain using dY / dx = f'(g(x))g'(x); Where X1 and X2 are flow values, Y1 and Y2 are lift values ​​corresponding to the flow values ​​X1, X2, Y is the controller drive, and A, B, C, D are coefficients of the derivatives.

16. The process control system of claim 11, wherein: The gain value is given by dY / dx = f'(g(x))g'(x) Definition, where Y It is controller driven. f'(g(x)) is the actuator gain, and g'(x) is the valve model gain.

17. A mass flow controller for controlling the flow rate of a fluid, the mass flow controller comprising: an inlet, the inlet being used to receive the fluid; a valve actuator coupled to a valve for regulating the flow rate of the fluid out of an outlet of the mass flow controller by controlling operation of the valve; at least one sensor for measuring at least one of a fluid type, a pressure, and a temperature, the fluid type, the pressure, and the temperature being related to a flow rate of the fluid through a flow path; as well as a linearization control system coupled to the valve actuator for determining a gain value of the mass flow controller to control a linear response of the valve actuator using a desired fluid flow rate and using at least one of the fluid type, the pressure, and the temperature; wherein the linearized control system determines the desired fluid flow rate based on a rate-limited and low-pass filtered flow set point value, at least one real-time fluid parameter value, valve model data, actuator gains, and valve model gains, wherein the linearized control system further comprises: a flow modeling system for determining fluid properties based on measurements of the fluid type, the pressure, and the temperature; and a valve modeling system for determining desired operating characteristics of the valve based on the valve specification and the determined fluid properties; and Wherein, the valve modeling system is further configured as follows: determining a driving value for controlling the lift of the valve to obtain the desired fluid flow rate; Therein, the drive value is determined based on the desired operating characteristic.

18. A method for controlling the flow rate of a fluid by means of a mass flow controller, the method comprising: receiving the fluid through an inlet; regulating the flow rate of the fluid out of an outlet of the mass flow controller by controlling operation of the valve using a valve actuator; receiving a desired fluid flow rate; receiving a measurement of at least one of a pressure, a temperature, a flow rate, and a fluid type from at least one sensor, the pressure, the temperature, the flow rate, and the fluid type being related to the flow rate of the fluid through a flow path; as well as controlling a gain of the mass flow controller using the desired fluid flow rate and controlling a linear response of the valve using at least one of the pressure, the temperature, the flow rate, and the fluid type; The linear response is determined by determining the change in the actuator drive value and the change in the flow rate of the fluid. dDrive / dFlow to control; wherein the desired fluid flow rate is determined by a rate-limited and low-pass filtered flow set point value, at least one real-time fluid parameter value, valve model data, actuator gain, and valve model gain; and the method further comprises: determining a fluid property based on the pressure, the temperature, the flow rate, and the fluid type; and determining desired operating characteristics of the valve based on the valve specifications and the determined fluid properties; and determining a driving value for controlling the lift of the valve to obtain the desired fluid flow rate; Therein, the drive value is determined based on the desired operating characteristic.

19. A process control system for a mass flow controller, the process control system comprising: a linearization module communicatively coupled to the valve actuator and the memory device, the linearization module controlling a gain of the mass flow controller by controlling a linear response of the valve using a desired fluid flow rate and using at least one of a pressure, a temperature, a flow rate, and a fluid type from at least one sensor, the pressure, the temperature, the flow rate, and the fluid type being related to a flow rate of the fluid through a flow path; Wherein, the linearization module further comprises: a flow modeling system for determining a fluid property based on at least one of the pressure, the temperature, the flow rate, and the fluid type; and a valve modeling system for determining desired operating characteristics of the valve based on the valve specifications and the determined fluid properties; and wherein the desired fluid flow rate is determined by a rate limited and low pass filtered flow set point value, at least one real-time fluid parameter value, valve model data, actuator gains, and valve model gains, and wherein the valve modeling system is further configured to: determining a driving value for controlling the lift of the valve to obtain the desired fluid flow rate; Therein, the drive value is determined based on the desired operating characteristic.