Patent Grant
7940664
This invention relates generally fluid pumps. More particularly, embodiments of the present invention relate to input/out systems, methods, and apparatuses for interfacing a pump controller with various devices.
There are many applications for which precise control over the amount and/or rate at which a fluid is dispensed by a pumping apparatus is necessary. In semiconductor processing, for example, it is important to control the amount and rate at which photochemicals, such as photoresist chemicals, are applied to a semiconductor wafer. The coatings applied to semiconductor wafers during processing typically require a certain flatness and/or even thickness across the surface of the wafer that is measured in angstroms. The rates at which processing chemicals are applied (i.e., dispensed) onto the wafer have to be controlled carefully to ensure that the processing liquid is applied uniformly.
Photochemicals used in the semiconductor industry today are typically very expensive, costing as much as $1000 and up per a liter. Therefore, it is highly desirable to ensure that a minimum but adequate amount of chemical is used and that the chemical is not damaged by the pumping apparatus. Current multiple stage pumps can cause sharp pressure spikes in the liquid. Such pressure spikes and subsequent drops in pressure may be damaging to the fluid (i.e., may change the physical characteristics of the fluid unfavorably) and/or adversely affect the performance of the pumping system. Additionally, pressure spikes can lead to built up fluid pressure that may cause a dispense pump to dispense more fluid than intended or dispense the fluid in a manner that has unfavorable dynamics.
One shortcoming of prior pumps is interfacing the pump controller with other devices. The pump controller typically receives signals from a control system (e.g., other computers/tools) to receive process parameters, trigger signals or other signals and sends signals to indicate the state of a dispense cycle or other data. Many computers/manufacturing tools, however, use different physical interfaces and signaling schemes to communicate signals to and receive signals from a pump. Generally, for each input/output line, the pumping system requires one conductor leading to the pump controller. This means customizing the pump controller for a pump for the specific interface on another device to/from which the pump communicates data. In semiconductor manufacturing systems which generally use a large number of pump signals this can lead to complicated wiring leading to a single pump. Moreover, in many semiconductor manufacturing systems, there are multiple pumps stacked together, leading to a complicated array of wires leading to the pumps. Another shortcoming of prior systems was that the discrete input/output (“I/O”) lines were limited in length. There is a need for new and better ways to interface devices with the pumps. Embodiments of the invention can address this need and more.
Embodiments of the present invention provide new I/O systems, methods, and apparatuses for interfacing pump controller(s) with various devices. More particularly, embodiments of the present invention provide an I/O system and method for interfacing pump controller(s) with external control device(s) which may have different interfaces and/or signaling formats.
In one embodiment, at least one I/O interface module is positioned between a pumping system and at least one programmed device such as a computer running a particular pump software application, a man-machine interface device, or a manufacturing tool for monitoring/controlling the pumping system. In one embodiment, the pumping system implements a single or multiple stage (“multi-stage”) pump having a pump controller coupled thereto. The pump controller is configured to control the valve and motor timings of the pump directly and locally in accordance with the signals from the control device.
In embodiments of the invention, the I/O interface module can be implemented on a circuit board having thereon a processor and a memory. The circuit board has at least two data communications interfaces, one for communicating with the pump controller and one for communicating with the control device. These data communications interfaces can be customized to suit, depending upon implementation.
In some embodiments of the present invention, a single I/O interface module can be implemented. In one embodiment, the I/O interface module can include a first data communications interface to connect to a pump controller and a second data communications interface to connect to a control device (e.g., a computer, a manufacturing tool, a man-machine interface device, or the like) external to the pump. One example of this embodiment is described below with reference to
In embodiments of the invention, the I/O interface module can interface with the control device via RS232, RS485, RS422 or other interfaces, can include analog inputs and outputs, DVC interface, or retrofit interfaces. The I/O interface module is customizable without changing pump hardware. Further, the I/O interface module can be tailored to each user's particular need to send signals to and receive signals from a pump. The I/O interface module allows a variety of interfaces and control schemes to be implemented with a particular pump without changing the hardware of the pump. According to one embodiment, regardless of the interfaces and communications protocols used between the I/O interface module and the control device, the I/O interface module streams serial packetized data over a high speed SPI serial bus to the pump controller.
Advantages provided by embodiments of the present invention can be numerous. As an example, by interpreting and asserting signals for the pump controller and the control device, the I/O interface module can reduce the number of discrete lines that otherwise would have been required in a direction connection configuration, thus greatly reducing cabling.
The reduction in cabling requirements provides the additional advantages of space saving, which can be an important factor in miniaturizing a pumping system, and cost saving, which can be highly desirable in just about any application.
Another advantage of the I/O interface module is that it eliminates the distance limitation imposed by discrete lines and allows for longer connections between the pumping system and the control device.
Other advantages of the embodiments of the I/O system disclosed herein include versatility and adaptability. Since the data communications interface of the I/O interface module can be customized to connect to the data communications interface of the control device, the control device and/or control schemes can be replaced or otherwise modified without having to change the hardware of the pump. Furthermore, since the data communications interface of the I/O interface module can be customized to connect to the data communications interface of the pump controller, the pump or its hardware can be replaced or otherwise modified without having to qualify the entire pump and/or re-arbitrate the pump to establish communication between the control device and the new pump. Moreover, embodiments of the invention advantageously allow the logic for controlling the pump to be allocated among two or more I/O interface modules or between a plurality of I/O interface modules and a plurality of pump controllers in various configurations without being limited by the processing power of the pump controllers.
A more complete understanding of the present invention and the advantages thereof may be acquired by referring to the following description, taken in conjunction with the accompanying drawings in which like reference numbers indicate like features and wherein:
Preferred embodiments of the present invention are described below with reference to the figures which are not necessarily drawn to scale and where like numerals are used to refer to like and corresponding parts of the various drawings.
Embodiments of the present invention are directed to pump controllers in pumping systems. Such a pumping system may employ a multiple stage (“multi-stage”) pump for feeding and accurately dispensing fluid onto wafers during a semiconductor manufacturing process. Particularly, embodiments of the present invention provide input/output (“I/O”) interface systems, methods, and devices for interfacing a pump controller with various devices. It should be noted that the pumping system embodying such a pump controller as described herein are provided by way of example, but not limitation, and embodiments of the present invention can be utilized and/or suitably implemented for other designs and configurations. Specifically, embodiments of the invention can be applied to various pumps, including single stage and multi-stage pumps. An exemplary pumping system will first be described below before describing in detail embodiments of I/O systems, methods, and devices for interfacing the pump controller of the pumping system with various devices.
The operation of pump 100 can be controlled by pump controller 20, which can be onboard pump 100 or connected to pump 100 via a one or more communications links for communicating control signals, data or other information. Additionally, the functionality of pump controller 20 can be distributed between an onboard controller and another controller, including an I/O interface controller onboard an I/O interface module external to pump 100.
Pump controller 20 can include a computer readable medium 27 (e.g., RAM, ROM, Flash memory, optical disk, magnetic drive or other computer readable medium) containing a set of control instructions 30 for controlling the operation of pump 100. A processor 35 (e.g., CPU, ASIC, RISC or other processor) can execute the instructions. One example of a processor is the Texas Instruments TMS320F2812PGFA 16-bit DSP (Texas Instruments is Dallas, Tex. based company).
In the example of
Feed stage 105 and dispense stage 110 can include rolling diaphragm pumps to pump fluid in pump 100. Feed-stage pump 150 (“feed pump 150”), for example, includes a feed chamber 155 to collect fluid, a feed stage diaphragm 160 to move within feed chamber 155 and displace fluid, a piston 165 to move feed stage diaphragm 160, a lead screw 170 and a stepper motor 175. Lead screw 170 couples to stepper motor 175 through a nut, gear or other mechanism for imparting energy from the motor to lead screw 170. Feed motor 170 rotates a nut that, in turn, rotates lead screw 170, causing piston 165 to actuate. Dispense-stage pump 180 (“dispense pump 180”) can similarly include a dispense chamber 185, a dispense stage diaphragm 190, a piston 192, a lead screw 195, and a dispense motor 200. Dispense motor 200 can drive lead screw 195 through a threaded nut (e.g., a Torlon or other material nut).
During operation of pump 100, the valves of pump 100 are opened or closed to allow or restrict fluid flow to various portions of pump 100. These valves can be pneumatically actuated (i.e., gas driven) diaphragm valves that open or close depending on whether pressure or a vacuum is asserted. However, any suitable valve can be used.
The following provides a summary of various stages of operation of pump 100. However, pump 100 can be controlled according to a variety of control schemes including, but not limited to those described in [U.S. Provisional Patent Application Ser. No. 60/741,682, filed Dec. 5, 2005, entitled “SYSTEM AND METHOD FOR PRESSURE COMPENSATION IN A PUMP” by Inventors Cedrone et al. U.S. patent application Ser. No. 11/502,729, filed Aug. 11, 2006, Entitled “SYSTEMS AND METHODS FOR FLUID FLOW CONTROL IN AN IMMERSION LITHOGRAPHY SYSTEM” by inventors Clarke et al.; U.S. patent application Ser. No. 11/292,559 filed Dec. 2, 2005, entitled “SYSTEM AND METHOD FOR CORRECTING FOR PRESSURE VARIATIONS USING A MOTOR” by Inventors Gonnella et al.; U.S. patent application Ser. No. 11/292,559, filed Dec. 2, 2005, entitled “SYSTEM AND METHOD FOR CONTROL OF FLUID PRESSURE” by Inventors Gonnella et al. U.S. patent application Ser. No. 11/364,286, filed Feb. 28, 2006, entitled “SYSTEM AND METHOD FOR MONITORING OPERATION OF A PUMP” by Inventors Gonnella et al., each of which is fully incorporated by reference herein, to sequence valves and control pressure. According to one embodiment, pump 100 can include a ready segment, dispense segment, fill segment, pre-filtration segment, filtration segment, vent segment, purge segment and static purge segment. During the feed segment, inlet valve 125 is opened and feed stage pump 150 moves (e.g., pulls) feed stage diaphragm 160 to draw fluid into feed chamber 155. Once a sufficient amount of fluid has filled feed chamber 155, inlet valve 125 is closed. During the filtration segment, feed-stage pump 150 moves feed stage diaphragm 160 to displace fluid from feed chamber 155. Isolation valve 130 and barrier valve 135 are opened to allow fluid to flow through filter 120 to dispense chamber 185. Isolation valve 130, according to one embodiment, can be opened first (e.g., in the “pre-filtration segment”) to allow pressure to build in filter 120 and then barrier valve 135 opened to allow fluid flow into dispense chamber 185. During the filtration segment, dispense pump 180 can be brought to its home position. As described in U.S. Provisional Patent Application No. 60/630,384, entitled “SYSTEM AND METHOD FOR A VARIABLE HOME POSITION DISPENSE SYSTEM” by Laverdiere, et al., filed Nov. 23, 2004 and PCT Application No. PCT/US2005/042127, entitled “SYSTEM AND METHOD FOR VARIABLE HOME POSITION DISPENSE SYSTEM”, by Laverdiere et al., filed Nov. 21, 2005, which are incorporated herein by reference, the home position of the dispense pump can be a position that gives the greatest available volume at the dispense pump for the dispense cycle, but is less than the maximum available volume that the dispense pump could provide. The home position is selected based on various parameters for the dispense cycle to reduce unused hold up volume of pump 100. Feed pump 150 can similarly be brought to a home position that provides a volume that is less than its maximum available volume.
At the beginning of the vent segment, isolation valve 130 is opened, barrier valve 135 closed and vent valve 145 opened. In another embodiment, barrier valve 135 can remain open during the vent segment and close at the end of the vent segment. During this time, if barrier valve 135 is open, the pressure can be understood by the controller because the pressure in the dispense chamber, which can be measured by pressure sensor 112, will be affected by the pressure in filter 120. Feed-stage pump 150 applies pressure to the fluid to remove air bubbles from filter 120 through open vent valve 145. Feed-stage pump 150 can be controlled to cause venting to occur at a predefined rate, allowing for longer vent times and lower vent rates, thereby allowing for accurate control of the amount of vent waste. If feed pump is a pneumatic style pump, a fluid flow restriction can be placed in the vent fluid path, and the pneumatic pressure applied to feed pump can be increased or decreased in order to maintain a “venting” set point pressure, giving some control of an other wise un-controlled method.
At the beginning of the purge segment, isolation valve 130 is closed, barrier valve 135, if it is open in the vent segment, is closed, vent valve 145 closed, and purge valve 140 opened and inlet valve 125 opened. Dispense pump 180 applies pressure to the fluid in dispense chamber 185 to vent air bubbles through purge valve 140. During the static purge segment, dispense pump 180 is stopped, but purge valve 140 remains open to continue to vent air. Any excess fluid removed during the purge or static purge segments can be routed out of pump 100 (e.g., returned to the fluid source or discarded) or recycled to feed-stage pump 150. During the ready segment, isolation valve 130 and barrier valve 135 can be opened and purge valve 140 closed so that feed-stage pump 150 can reach ambient pressure of the source (e.g., the source bottle). According to other embodiments, all the valves can be closed at the ready segment.
During the dispense segment, outlet valve 147 opens and dispense pump 180 applies pressure to the fluid in dispense chamber 185. Because outlet valve 147 may react to controls slower than dispense pump 180, outlet valve 147 can be opened first and some predetermined period of time later dispense motor 200 started. This prevents dispense pump 180 from pushing fluid through a partially opened outlet valve 147. Moreover, this prevents fluid moving up the dispense nozzle caused by the valve opening (it's a mini-pump), followed by forward fluid motion caused by motor action. In other embodiments, outlet valve 147 can be opened and dispense begun by dispense pump 180 simultaneously.
An additional suckback segment can be performed in which excess fluid in the dispense nozzle is removed. During the suckback segment, outlet valve 147 can close and a secondary motor or vacuum can be used to suck excess fluid out of the outlet nozzle. Alternatively, outlet valve 147 can remain open and dispense motor 200 can be reversed to such fluid back into the dispense chamber. The suckback segment helps prevent dripping of excess fluid onto the wafer.
Embodiments of pump 100 may employ various pump control mechanisms and valve timings to help reduce deleterious effects of pressure on a process fluid.
The opening and closing of various valves can cause pressure spikes in the fluid within pump 100. Because outlet valve 147 is closed during the static purge segment, closing of purge valve 140 at the end of the static purge segment, for example, can cause a pressure increase in dispense chamber 185. This can occur because each valve may displace a small volume of fluid when it closes. More particularly, in many cases before a fluid is dispensed from chamber 185 a purge cycle and/or a static purge cycle is used to purge air from dispense chamber 185 in order to prevent sputtering or other perturbations in the dispense of the fluid from pump 100. At the end of the static purge cycle, however, purge valve 140 closes in order to seal dispense chamber 185 in preparation for the start of the dispense. As purge valve 140 closes it forces a volume of extra fluid (approximately equal to the hold-up volume of purge valve 140) into dispense chamber 185, which, in turn, causes an increase in pressure of the fluid in dispense chamber 185 above the baseline pressure intended for the dispense of the fluid. This excess pressure (above the baseline) may cause problems with a subsequent dispense of fluid. These problems are exacerbated in low pressure applications, as the pressure increase caused by the closing of purge valve 140 may be a greater percentage of the baseline pressure desirable for dispense.
More specifically, because of the pressure increase that occurs due to the closing of purge valve 140 a “spitting” of fluid onto the wafer, a double dispense or other undesirable fluid dynamics may occur during the subsequent dispense segment if the pressure is not reduced. Additionally, as this pressure increase may not be constant during operation of pump 100, these pressure increases may cause variations in the amount of fluid dispensed, or other characteristics of the dispense, during successive dispense segments. These variations in the dispense may in turn cause an increase in wafer scrap and rework of wafers. To account for unwanted pressure increases to the fluid in dispense chamber 185, during the static purge segment dispense motor 200 may be reversed to back out piston 192 a predetermined distance to compensate for any pressure increase caused by the closure of barrier valve 135, purge valve 140 and/or any other sources which may cause a pressure increase in dispense chamber 185.
The above-described pump control mechanisms provide pump 100 with gentle fluid handling characteristics. By compensating for pressure fluctuations in a dispense chamber before a dispense segment, potentially damaging pressure spikes can be avoided or mitigated. Other pump control mechanisms and valve timings may also be utilized or otherwise implemented to help reduce undesirable effects of pressure on a process fluid.
Supply lines 260 provide pressure or vacuum to valve plate 230, which has a plurality of valves configured to allow fluid to flow to various components of pump 100. Actuation of the valves is controlled by valve control manifold 302 that directs either pressure or vacuum to each supply line 260. Each supply line 260 can include a fitting (e.g., fitting 318) with a small orifice. This orifice may be of a smaller diameter (e.g., approximately 0.010 inches in diameter) than the diameter of the corresponding supply line 260 to which fitting 318 is attached. Thus, the orifice of fitting 318 may serve to place a restriction in supply line 260. The orifice in each supply line 260 helps mitigate the effects of sharp pressure differences between the application of pressure and vacuum to the supply line and thus may smooth transitions between the application of pressure and vacuum to the valve. In other words, the orifice helps reduce the impact of pressure changes on the diaphragm of the downstream valve. This allows the valve to open and close more smoothly which may lead to increased to smoother pressure transitions within the system which may be caused by the opening and closing of the valve and may in fact increase the longevity of the valve itself.
Valve control Manifold 302 can include a set of solenoid valves to selectively direct pressure/vacuum to valve plate 230. When a particular solenoid is on thereby directing vacuum or pressure to a valve, depending on implementation, the solenoid will generate heat. In this example, valve control manifold 302 is mounted to a printed circuit board (“PCB”) 397, which is mounted on a back plate (not shown), away from dispense block 205 and particularly dispense chamber 185. This helps prevent heat from the solenoids in valve control manifold 302 from affecting fluid in dispense block 205. Such a back plate can be made of machined aluminum or other material that can act as a heat sink for pump 100, dissipating heat from valve control manifold 302 and PCB 397. Valve control manifold 302 can receive signals from PCB 397 to cause solenoids to open/close to direct vacuum/pressure to the various supply lines 260 to control the valves of pump 100. Again, as shown in
Pump 100 includes several interfaces for communications with a pump controller (e.g., pump controller 20 of
It should be noted that the pump 100 described above is provided by way of example, but not limitation, and embodiments of the present invention can be implemented for other pump configurations.
As discussed above, pump controller 20 can provide signals locally and/or internally to the various motors and the solenoid (i.e., to open/close the valves) and provide data to other devices (remote or external to pump controller 20) in a semiconductor manufacturing system. Previous versions of pump controllers use a serial connection and discrete input/output lines to communicate. The serial connection is used to transmit/receive data corresponding to a man-machine interface (“MMI”). The discrete lines, on the other hand, carry signals such as trigger signals, alarm signals, etc. Each discrete line is for a dedicated function and carries a signal having a particular purpose (e.g., a signal on the discrete line had a specific purpose or meaning to the pump controller). For example, the changing of state on a particular discrete line (e.g., going from low to high or high to low) could indicate the start of dispense, whereas a signal on another discrete line could indicate the end of dispense.
Data communications system 5000 of
Embodiments of the present invention address these limitations with a versatile I/O system, method, and device interfacing the pump with other device(s).
Dispense process parameters, recipes, system variables and other process data can be transferred to/from pump controller 5520 on one set of serial lines (e.g., serial transmission lines 5522 and serial receive lines 5526). The other serial lines can be used to transmit, for example, triggers, error indications, and other pieces of data formerly carried as discrete signals. In one embodiment, these pieces of data are formed into a packet and transmitted serially over a second serial port. In the example shown in
As can be noted, the configuration of
I/O interface module 5550 comprises a first data communications interface 5506 and a second data communications interface 5604. As exemplified by
I/O interface module 5550 can further include a processor 5556 (e.g., CPU, PIC, DSP, ASIC or other processor) and associated logic coupled to (i.e., capable of communicating with) first data communications interface 5506 and second data communications interface 5604. One example of a processor is a PIC PIC18F8720-I/PT 8-bit microcontroller by MICROCHIP Technology Inc. of Chandler, Ariz. A computer readable medium 5558 (e.g., RAM, ROM, Flash memory, EEPROM, magnetic storage, optical storage) or other computer readable medium can carry software or program instructions 5552 executable by processor 5556. It should be noted that computer readable medium 5558 can be onboard processor 5556. Furthermore, instructions 5552 are executable to translate data received on data communications interface 5604 to a format usable by pump controller 5520 and data received via data communications interface 5506 to a format usable by device 5616 connected via data communications interface 5604. For example, I/O interface module 5550 can include logic to map discrete line signals to bits in a packet for serial communication.
As an example, assume data communications interface 5604 includes serial communications lines 5662 to transfer process variables and other variable data (e.g., data associated with device 5616) to/from pump 5100, line 5666 for Trigger 1, line 5668 for Trigger 2, line 5670 for Trigger 3, line 5672 for Clear Error, line 5674 for the Ready signal, line 5676 for an Error Signal, line 5678 for a pre-dispense signal, and line 5680 for a dispense signal. When I/O interface module 5550 receives serial data via serial communications lines 5662, I/O interface module 5550 can pass the data to pump 5100 on serial communications lines 5526 with or without manipulation. When I/O interface module 5550 receives data on line 5666, 5668, 5670 or 5672, I/O interface module 5550 can set a corresponding bit in a packet and send the packet to pump 5100 on serial data lines 5526 or 5528.
Further assume, for example, that I/O interface module 5550 forms 12 byte packets with 4 bytes (i.e., 32 bits) reserved for transmitting data received over interface 5506 to pump 5100 and operates at 3 kHz. Each line (up to 32 lines in this case) can be assigned a bit in a packet. Thus, for example, when a signal is received on line 5666 indicating Trigger 1, I/O interface module 5550 can set the first data bit (or other bit corresponding to line 5066) in the next outgoing packet. When pump 5100 receives the packet, pump controller 5520 will read the bit and understand that Trigger 1 is being asserted and act correspondingly. In the opposite direction, pump controller 5520 can pass data, such as a Ready state, to I/O interface module 5550 in an appropriate bit (i.e., a data bit in the packet corresponding to line 5674). When I/O interface module 5550 receives the packet from pump 5100, I/O interface module 5550 can assert the appropriate state on line 5674. Thus, in this example, I/O interface module 5550 acts as a parallel to serial converter for pump data.
I/O interface module 5550, according to one embodiment, can be agnostic to the meaning of signals asserted on various lines and set in corresponding bits. For example, when I/O interface module 5550 receives a signal on line 5666, it simply sets the appropriate bit in the next outgoing packet to pump 5100. In this case, pump controller 5520 at pump 5100 is responsible for interpreting the received bit as Trigger 1. It should be noted that the software at pump 5100 can be user-configurable to interpret bits to correspond to certain states. For example, the software can be configured to use data bit one as the Trigger 1 bit or data bit five as the Trigger 1 bit. Thus, the software at pump 5100 can provide for flexibility in interpreting/forming the input/output packets.
Similarly, when I/O interface module 5550 receives a packet from pump 1500 with the bit corresponding to line 5674 set, I/O interface module 5550 can assert a signal on line 5674. In this case, device 5616 (to which the signal is asserted) is responsible for interpreting the signal to indicate the ready state. Other bits in the packets sent from I/O interface module 5550 can include, for example, the module type, addressing information or other information. According to other embodiments of the present invention, I/O interface module 5550 can include programming and/or suitable logic to interpret the bits set by pump 5100 or signals asserted on interface 5604 to take action in response to the bits/signals. In some embodiments, after a signal from device 5616 is received at I/O interface module 5550, the logic or intelligence to interpret and act on that signal is allocated between I/O interface module 5550 and pump controller 5520. The allocation could be distributed (e.g., 50-50) or optimized (e.g., a smart pump controller or a smart I/O interface module), depending upon implementation. For example, in some embodiments, I/O interface module 5550 simply provides serial-parallel data conversion, thus requiring very little computational power and memory. In some embodiments, I/O interface module 5550 can be configured (and correspondingly equipped) to perform most of the pump control functions. In this way, very little intelligence and hence computational power and memory is required at the pump controller. Such a pump controller would only need to handle the basic functions to control the motor(s) and valves locally. In some embodiments, I/O interface module 5550 can be configured (and correspondingly equipped) to service more than one pumps.
I/O interface systems 5500 and 5800 provide several advantages over previous pump control interface systems. First, different I/O interface modules can support different functionality. For example, in the above example, I/O interface module 5550 supports four discrete inputs and four discrete outputs. However, other interface modules could support more inputs and outputs. If a user wishes to support an additional function, rather than having to replace data communications interface 5504 and/or pump controller 5520 at pump 5100, the user would simply replace I/O interface module 5550 with a new or different version of the I/O interface module. Continuing with the previous example, if the user wishes to change from a four discrete input/output system to a five discrete input/output system, the user could simply replace I/O interface module 5550 with a new I/O interface module that supported five discrete lines. Furthermore, if the user changes computer systems and/or has a new physical interface, the user can change out I/O interface module 5550 with one that can accommodate the new physical interface and/or the new computer system(s) without needing to change any interface at the pump. This shortens the time it takes the new system (and hence the user) to establish/re-establish communications with the pump.
Another advantage provided by embodiments of the present invention is that the interface module can handle network addressing if the interface module is connected to other devices through a network (e.g., an RS-232 network). If the pump behind the interface module experiences problems and must be replaced, a new pump can be transparently connected to the old interface module. Because the network address is associated with the interface module rather than the pump, the network address does not have to be re-arbitrated when the new pump is added to replace the old pump.
Yet another advantage provided by embodiments of the present invention is to allow newer pumps, such as the pump described in U.S. Provisional Patent Application Ser. No. 60/742,435 filed Dec. 5, 2005, entitled “SYSTEM AND METHOD FOR MULTI-STAGE PUMP WITH REDUCED FORM FACTOR” by Inventors Cedrone et al. which is incorporated herein by reference, to interface with older control systems. For example, older multi-stage pump control systems would assert signals for each pump stage including motor signals. An interface module can translate these signals into packetized data and send the data packets to the pump over the 15-line cable. The pump software can read the data packet to determine which bits are set and take the appropriate action (e.g., close or open a valve, move a motor in forward or reverse etc.). Thus, a newer pump can be controlled by an older control system using a different physical interface and implementing an older control routine.
It should be noted that embodiments of the I/O interface modules disclosed herein may process the signals asserted by the control system to translate the signals into data usable by the pump. For example, a control system may simply assert a signal to move a motor clockwise or counter clockwise on particular lines as shown in
As the above example illustrates, a signal on a particular line received by I/O interface module 5550 may cause I/O processor or controller 5556 to perform some processing of the signal to set multiple bits. Similarly, multiple bits in a packet received from pump 5100 may be processed by I/O processor or controller 5556 to cause I/O interface module 5550 to assert a signal on a particular line or lines.
In some embodiments, I/O interface module 5550 is capable of performing analog-digital conversion. For example, I/O interface module 5550 can digitize analog signals to send information received in an analog form to pump 5100 in a packet and covert packetized data received from pump 5100 to an analog signal. Additionally, I/O interface module 5550 is capable of supporting some functions which may not be supported by pump 5100 and which may be expected by the computer or other device communicatively coupled to pump 5100. In this way, I/O interface module 5550 can virtualize the functionality for pump 5100 and assert appropriate signals to the external computer or device.
Embodiments of the invention disclosed herein provide many advantages. One advantage is that, by eliminating the distance limitation imposed by discrete lines used in prior systems, embodiments of the present invention allow cable connections/disconnections to be removed or separate from the area where the pump operates.
As
Another advantage of embodiments of the invention is that the I/O interface module can reduce the computational power and/or data storage space required at the pump. In the example shown in
Although the present invention has been described in detail herein with reference to the illustrative embodiments, it should be understood that the description is by way of example only and is not to be construed in a limiting sense. It is to be further understood, therefore, that numerous changes in the details of the embodiments of this invention and additional embodiments of this invention will be apparent to, and may be made by, persons of ordinary skill in the art having reference to this description. It is contemplated that all such changes and additional embodiments are within the scope and spirit of this invention. Accordingly, the scope of the invention should be determined by the following claims and their legal equivalents.
The present application claims priority from U.S. Provisional Patent Application No. 60/741,657, filed Dec. 2, 2005, entitled “I/O INTERFACE SYSTEM AND METHOD FOR A PUMP” which is incorporated herein by reference for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 269626 | Bodel et al. | Dec 1882 | A |
| 826018 | Concoff | Jul 1906 | A |
| 1664125 | Lowrey | Mar 1928 | A |
| 2153664 | Freedlander | Apr 1939 | A |
| 2215505 | Hollander | Sep 1940 | A |
| 2328468 | Laffly | Aug 1943 | A |
| 2457384 | Krenz | Dec 1948 | A |
| 2631538 | Johnson | Mar 1953 | A |
| 2673522 | Dickey | Mar 1954 | A |
| 2757966 | Samiran | Aug 1956 | A |
| 3072058 | Christopher et al. | Jan 1963 | A |
| 3227279 | Bockelman | Jan 1966 | A |
| 3327635 | Sachnik | Jun 1967 | A |
| 3623661 | Wagner | Nov 1971 | A |
| 3741298 | Canton | Jun 1973 | A |
| 3895748 | Klingenberg | Jul 1975 | A |
| 3954352 | Sakai | May 1976 | A |
| 4023592 | Patzke | May 1977 | A |
| 4093403 | Schrimpf | Jun 1978 | A |
| 4452265 | Lonnebring | Jun 1984 | A |
| 4483665 | Hauser | Nov 1984 | A |
| 4541455 | Hauser | Sep 1985 | A |
| 4597719 | Tano | Jul 1986 | A |
| 4597721 | Santefort | Jul 1986 | A |
| 4601409 | DiRegolo | Jul 1986 | A |
| 4614438 | Kobayashi | Sep 1986 | A |
| 4671545 | Miyazaki | Jun 1987 | A |
| 4690621 | Swain | Sep 1987 | A |
| 4705461 | Clements | Nov 1987 | A |
| 4797834 | Honganen et al. | Jan 1989 | A |
| 4808077 | Kan et al. | Feb 1989 | A |
| 4810168 | Nogami et al. | Mar 1989 | A |
| 4821997 | Zdeblick | Apr 1989 | A |
| 4824073 | Zdeblick | Apr 1989 | A |
| 4865525 | Kern | Sep 1989 | A |
| 4913624 | Seki et al. | Apr 1990 | A |
| 4915126 | Gyllinder | Apr 1990 | A |
| 4943032 | Zdeblick | Jul 1990 | A |
| 4950134 | Bailey et al. | Aug 1990 | A |
| 4952386 | Davison | Aug 1990 | A |
| 4966646 | Zdeblick | Oct 1990 | A |
| 5061156 | Kuehne | Oct 1991 | A |
| 5061574 | Henager, Jr. | Oct 1991 | A |
| 5062770 | Story | Nov 1991 | A |
| 5134962 | Amada | Aug 1992 | A |
| 5135031 | Burgess | Aug 1992 | A |
| 5167837 | Snodgrass | Dec 1992 | A |
| 5192198 | Gebauer | Mar 1993 | A |
| 5261442 | Kingsford | Nov 1993 | A |
| 5262068 | Bowers | Nov 1993 | A |
| 5316181 | Burch | May 1994 | A |
| 5344195 | Parimore, Jr. et al. | Sep 1994 | A |
| 5350200 | Peterson et al. | Sep 1994 | A |
| 5380019 | Hillery | Jan 1995 | A |
| 5434774 | Seberger | Jul 1995 | A |
| 5476004 | Kingsford | Dec 1995 | A |
| 5490765 | Bailey | Feb 1996 | A |
| 5511797 | Nikirk | Apr 1996 | A |
| 5516429 | Snodgrass | May 1996 | A |
| 5527161 | Bailey | Jun 1996 | A |
| 5546009 | Raphael | Aug 1996 | A |
| 5575311 | Kingsford | Nov 1996 | A |
| 5580103 | Hall | Dec 1996 | A |
| 5599100 | Jackson et al. | Feb 1997 | A |
| 5599394 | Yabe | Feb 1997 | A |
| 5645301 | Kingsford | Jul 1997 | A |
| 5652391 | Kingsford | Jul 1997 | A |
| 5653251 | Handler | Aug 1997 | A |
| 5743293 | Kelly | Apr 1998 | A |
| 5762795 | Bailey | Jun 1998 | A |
| 5772899 | Snodgrass | Jun 1998 | A |
| 5784573 | Szczepanek et al. | Jul 1998 | A |
| 5785508 | Bolt | Jul 1998 | A |
| 5793754 | Houldsworth et al. | Aug 1998 | A |
| 5839828 | Glanville | Nov 1998 | A |
| 5848605 | Bailey | Dec 1998 | A |
| 5947702 | Biederstadt | Sep 1999 | A |
| 5971723 | Bolt | Oct 1999 | A |
| 5991279 | Haugli et al. | Nov 1999 | A |
| 6033302 | Ahmed et al. | Mar 2000 | A |
| 6105829 | Snodgrass | Aug 2000 | A |
| 6190565 | Bailey | Feb 2001 | B1 |
| 6238576 | Yajima | May 2001 | B1 |
| 6250502 | Cote | Jun 2001 | B1 |
| 6251293 | Snodgrass | Jun 2001 | B1 |
| 6302660 | Kurita | Oct 2001 | B1 |
| 6318971 | Ota | Nov 2001 | B1 |
| 6325032 | Sekiya et al. | Dec 2001 | B1 |
| 6325932 | Gibson | Dec 2001 | B1 |
| 6330517 | Dobrowski et al. | Dec 2001 | B1 |
| 6348124 | Garbett | Feb 2002 | B1 |
| 6474950 | Waldo | Nov 2002 | B1 |
| 6478547 | Savard | Nov 2002 | B1 |
| 6506030 | Kottke | Jan 2003 | B1 |
| 6540265 | Turk | Apr 2003 | B2 |
| 6554579 | Martin | Apr 2003 | B2 |
| 6592825 | Pelc | Jul 2003 | B2 |
| 6635183 | Gibson | Oct 2003 | B2 |
| 6742992 | Davis | Jun 2004 | B2 |
| 6742993 | Savard | Jun 2004 | B2 |
| 6766810 | Van Cleemput | Jul 2004 | B1 |
| 6767877 | Kuo | Jul 2004 | B2 |
| 6837484 | Kingsford | Jan 2005 | B2 |
| 6901791 | Frenz et al. | Jun 2005 | B1 |
| 6925072 | Grohn | Aug 2005 | B1 |
| 6952618 | Davlin et al. | Oct 2005 | B2 |
| 7013223 | Zhang et al. | Mar 2006 | B1 |
| 7029238 | Zagars | Apr 2006 | B1 |
| 7063785 | Hiraku et al. | Jun 2006 | B2 |
| 7083202 | Eberle et al. | Aug 2006 | B2 |
| 7156115 | Everett et al. | Jan 2007 | B2 |
| 7247245 | Proulx et al. | Jul 2007 | B1 |
| 7249628 | Pillion et al. | Jul 2007 | B2 |
| 7272452 | Kan et al. | Sep 2007 | B2 |
| 7362798 | Starnberger | Apr 2008 | B1 |
| 7383967 | Gibson | Jun 2008 | B2 |
| 7454317 | Karasawa | Nov 2008 | B2 |
| 7476087 | Zagars et al. | Jan 2009 | B2 |
| 7494265 | Niermeyer et al. | Feb 2009 | B2 |
| 7547049 | Gashgaee | Jun 2009 | B2 |
| 20020044536 | Izumi et al. | Apr 2002 | A1 |
| 20020095240 | Sickinger | Jul 2002 | A1 |
| 20020197584 | Kendir et al. | Dec 2002 | A1 |
| 20030033052 | Hillen et al. | Feb 2003 | A1 |
| 20030040881 | Steger et al. | Feb 2003 | A1 |
| 20030148759 | Leliveld | Aug 2003 | A1 |
| 20030222798 | Floros | Dec 2003 | A1 |
| 20040000904 | Cotter | Jan 2004 | A1 |
| 20040013531 | Curry et al. | Jan 2004 | A1 |
| 20040050771 | Gibson | Mar 2004 | A1 |
| 20040072450 | Collins | Apr 2004 | A1 |
| 20040133728 | Ellerbrock et al. | Jul 2004 | A1 |
| 20050061722 | Takao et al. | Mar 2005 | A1 |
| 20050113941 | Ii et al. | May 2005 | A1 |
| 20050126985 | Campbell | Jun 2005 | A1 |
| 20050182497 | Nakano | Aug 2005 | A1 |
| 20050184087 | Zagars | Aug 2005 | A1 |
| 20050197722 | Varone et al. | Sep 2005 | A1 |
| 20050232296 | Schultze et al. | Oct 2005 | A1 |
| 20050238497 | Holst | Oct 2005 | A1 |
| 20060015294 | Yetter, Jr. et al. | Jan 2006 | A1 |
| 20060070960 | Gibson | Apr 2006 | A1 |
| 20060083259 | Metcalf et al. | Apr 2006 | A1 |
| 20070104586 | Cedrone | May 2007 | A1 |
| 20070125796 | Cedrone | Jun 2007 | A1 |
| 20070125797 | Cedrone | Jun 2007 | A1 |
| 20070126233 | Gashgaee | Jun 2007 | A1 |
| 20070128046 | Gonnella | Jun 2007 | A1 |
| 20070128047 | Gonnella | Jun 2007 | A1 |
| 20070128048 | Gonnella | Jun 2007 | A1 |
| 20070128050 | Cedrone | Jun 2007 | A1 |
| 20070206436 | Niermeyer et al. | Sep 2007 | A1 |
| 20070217442 | McLoughlin | Sep 2007 | A1 |
| 20080089361 | Metcalf et al. | Apr 2008 | A1 |
| 20080131290 | Magoon et al. | Jun 2008 | A1 |
| 20090047143 | Cedrone | Feb 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| B-7887287 | Apr 1988 | AU |
| 1271140 | Jul 1990 | CA |
| 1331783 | Jan 2002 | CN |
| 299 09 100 | Aug 1999 | DE |
| 0 249 655 | Dec 1987 | EP |
| 0 410 394 | Jan 1991 | EP |
| 0261972 | Dec 1992 | EP |
| 0863538 | Sep 1998 | EP |
| 0867649 | Sep 1998 | EP |
| 0 892 204 | Jan 1999 | EP |
| 1133639 | Jun 2004 | EP |
| 661 522 | Nov 1951 | GB |
| 58203340 | Nov 1983 | JP |
| 11 026430 | Jan 1999 | JP |
| 2009-517601 | Apr 2009 | JP |
| 2009-517618 | Apr 2009 | JP |
| 2009-517778 | Apr 2009 | JP |
| 2009-517888 | Apr 2009 | JP |
| 2009-521636 | Jun 2009 | JP |
| 9635876 | Nov 1996 | WO |
| WO 9937435 | Jul 1999 | WO |
| WO 9906514 | Dec 1999 | WO |
| WO 0031416 | Jun 2000 | WO |
| WO 0140646 | Jun 2001 | WO |
| WO 02090771 | Nov 2002 | WO |
| WO 2006057957 | Jun 2006 | WO |
| WO 2007067359 | Jun 2007 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20070127511 A1 | Jun 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60741657 | Dec 2005 | US |
