During magnetic disk manufacturing, disk surfaces are exposed to various sources of contamination. For example, different gases, chemicals, deposition materials and dust may end up as contaminants. These contaminants may be deposited on the disk surfaces in particulate or other forms and must then be removed during one or more stages of the manufacturing process.
Contaminants are typically removed using a combination of sonication and rinsing techniques. A disk may first be submerged in a sonication cleaning tank to loosen and remove contaminants, and then moved to a rinsing tank where the remaining contaminants may be carried away from the disk surfaces. Conventionally, there is no real-time mechanism for measuring the efficiency of these cleaning processes. Thus, there may be relatively little feedback for an operator to determine that the disks are not being cleaned effectively or to detect failure in one or more components of the cleaning apparatuses.
Referring to
The sonication cleaning system 100 may be used in a variety of manufacturing and/or cleaning environments. In one embodiment, the sonication cleaning system 100 includes a disk holder 114 configured to hold a disk 116 within the liquid 104 during a cleaning operation. The disk 116 may comprise, for example, a magnetic disk, and the sonication cleaning system 100 may be used to perform a post-sputter cleaning of the disk 116. In other embodiments, the methods and systems described herein may be used during cleaning operations performed on other workpieces (e.g., industrial equipment, lenses, or other electronic equipment).
The sonication cleaning tank 102 may comprise any of a variety of cleaning tanks employing sonication. In one embodiment, the sonication cleaning tank 102 may comprise a cross flow cleaning tank (illustrated in greater detail in
A sonication generator (not shown) may be positioned proximate the sonication cleaning tank 104 in order to generate sonication (i.e., acoustic waves) through the liquid 104. The sonication generator may generate megasonication, ultrasonication (a lower frequency sonication than megasonication), or acoustic waves at other frequencies. Ultrasonic cleaning may use lower frequencies and thereby produce more random cavitations, while megasonication may use higher frequencies and thereby produce more controlled cavitations.
The sonication cleaning tank 102 may further include one or more ingress and egress ports, which serve to direct the liquid 104 into and out from the sonication cleaning tank 102. The sonication cleaning tank 102 may further include at least one opening at the top through which workpieces may be lowered into the liquid 104. In one embodiment, as illustrated, the sonication cleaning tank 102 does not include a top wall. The sonication cleaning tank 102 may also have any suitable shape (e.g., rectilinear or bowl-shaped).
In one embodiment, the liquid 104 flowing through the sonication cleaning tank 102 principally comprises deionized water. However, in other embodiments, the liquid 104 may comprise any of a variety of solvents and solutes. For example, the liquid 104 may comprise alcohols, detergents and/or wetting agents. In some embodiments, the liquid 104 may include some undissolved solids. The type of solution may depend upon the type of workpiece being cleaned as well as upon the cleaning operation performed using the sonication cleaning system 100.
The at least one filter 106 fluidly coupled to the sonication cleaning tank 102 may be configured to filter a variety of different contaminants in order to produce the filtered liquid 108. In one embodiment, the at least one filter 106 may comprise at least one of an ionic chemical filter, a carbon filter, a particle filter or some other type of filter. The at least one filter 106 may further comprise a system of similar or different filters connected in series or in parallel. Each filter in this system of filters may be directly fluidly coupled to the at least one liquid particle counter 110, such that the at least one liquid particle counter 110 may generate opacity counts corresponding to each of these filters. However, in other embodiments, the at least one liquid particle counter 110 may be fluidly coupled only to an output of the entire system of filters, such that only a single opacity count indicative of contaminants and/or bubbles in the filtered liquid 108 may be generated.
In one embodiment, the at least one filter 106 may be positioned between the egress and ingress ports of the sonication cleaning tank 102, and the filtered liquid 108 may thus flow back through the sonication cleaning tank 102. In other embodiments, the at least one filter 106 is not used to filter the liquid 104, and the filtered liquid 108 is not reintroduced to the sonication cleaning tank 102.
In one embodiment, the at least one liquid particle counter 110 is fluidly coupled to the sonication cleaning tank 102 via a first fluid path 118 and is configured to generate a first opacity count indicative of contaminants and/or bubbles in the liquid 104. The at least one liquid particle counter 110 may include a light sensor configured to generate signals indicative of the first opacity count. For example, at least some liquid may be drawn from the sonication cleaning tank 102 into the at least one liquid particle counter 110 via the first fluid path 118, and the light sensor may comprise a CCD array configured to detect contaminants and bubbles that block or scatter light passing through the drawn liquid. In another embodiment, the at least one liquid particle counter 110 may operate by a reflectance optical measurement technique and may be coupled to a wall of the sonication cleaning tank 102. In still another embodiment, the at least one liquid particle counter 110 may be disposed within the sonication cleaning tank 102 itself. Many liquid particle counters are unable to differentiate between contaminants and bubbles, and thus the opacity count generated by the at least one liquid particle counter 110 may be indicative of both contaminants and bubbles.
The at least one liquid particle counter 110 may be further configured to generate a second opacity count indicative of contaminants and/or bubbles in the filtered liquid 108 from the at least one filter 106. As illustrated, the at least one liquid particle counter 110 may be fluidly coupled to the at least one filter 106 via a second fluid path 120. In some embodiments, a single liquid particle counter 110 may be fluidly coupled to both the sonication cleaning tank 102 and the at least one filter 106 and may be configured to generate both the first and second opacity counts. However, in other embodiments, the at least one liquid particle counter 110 may include a first liquid particle counter fluidly coupled to the sonication cleaning tank 102 and configured to generate the first opacity count, and a second liquid particle counter fluidly coupled to the at least one filter 106 and configured to generate the second opacity count. These different embodiments are discussed at greater length below.
The at least one liquid particle counter 110 may include a degasser (not shown in
The contaminants detected by the at least one liquid particle counter 110 may include particulates, oils, and other impurities in the liquid 104. In some embodiments, the at least one liquid particle counter 110 may be configured to detect contaminants and bubbles above a certain size. For example, in one embodiment, the at least one liquid particle counter 110 may be configured to detect contaminants larger than 1.0 μm. In another embodiment, the at least one liquid particle counter 110 may be configured to detect contaminants larger than 0.5, 0.2 or 0.1 μm. In some embodiments, the contaminant size detected by the at least one liquid particle counter 110 may correspond generally to the contaminant size filtered by the at least one filter 106.
As illustrated schematically in
The computing device 112 is communicatively coupled to the at least one liquid particle counter 110 and is configured to determine a contaminant count corresponding to an estimated number of contaminants in the liquid 104 based at least in part on the first and second opacity counts. In one embodiment, the first opacity count may be indicative of both contaminants and bubbles present in the liquid 104, while the second opacity count may be primarily indicative of the bubbles present in the liquid 104 (since the contaminants may be largely filtered out by the at least one filter 106). Thus, in one embodiment, the computing device 112 may compute the contaminant count by subtracting the second opacity count from the first opacity count. Of course, the contaminant count determined in this way may not be precisely equal to a contaminant level in the liquid 104. However, the contaminant count determined by the computing device 112 may represent a closer approximation to an absolute contaminant level than either of the opacity counts individually.
The computing device 112 may also take into account other variables when calculating the contaminant count. For example, the computing device 112 may factor in information indicative of a filtering efficiency of the at least one filter 106 in order to correct for contaminants included in the second opacity count. As another example, the computing device 112 may factor in information indicative of “natural” degassing that occurs between the sonication cleaning tank 102 and the at least one liquid particle counter 110 along the first fluid path 118 and/or the second fluid path 120.
The computing device 112 may comprise any of a variety of computing devices (e.g., a personal computer running Windows), and may include a processor operable to execute instructions and a computer-readable memory having instructions stored thereon that are executable by the processor in order to cause the processor to perform one or more acts. In one embodiment, many of the acts described herein may be orchestrated by the processor based on those instructions stored in the computer-readable memory.
As described above, the sonication cleaning system 100 may include a disk holder 114. The disk holder 114 may be movable between a raised position, wherein the disk 116 is positioned above the liquid 104, and a lowered position, wherein the disk 116 is positioned within the liquid 104. For example, an actuator (not shown) may be coupled to the disk holder 114, and the actuator may be electronically controlled in order to move the disk holder 114 between these positions. In other embodiments, the disk holder 114 need not be movable. In still other embodiments, the sonication cleaning system 100 need not include a disk holder 114, but may include another structure for holding a workpiece within the liquid 104 during a cleaning operation.
The disk 116 may comprise any of a variety of magnetic or optical disks having a substantially concentric opening defined therethrough. As used herein, the term “disk” refers to a magnetic or optical disk at any stage of manufacturing. That is, the disk 116 need not be readable or writable at the time a cleaning operation is performed using the sonication cleaning system 100. In one embodiment, the sonication cleaning system 100 may be configured to hold and clean a single disk 116. However, in other embodiments, the sonication cleaning tank 102 may accommodate a plurality of disks 116 (not shown).
The sonication cleaning system 200 of
The at least one degasser 222 may comprise one or more separate degassers connected in series or in parallel. These degassers may be of the same or of different types. In one embodiment, for example, the at least one degasser 222 comprises at least two degassers connected in series. Such an arrangement may improve both a degassing efficiency as well as the transition time to achieve the optimal degassing efficiency.
In addition to the first and second opacity counts, the at least one liquid particle counter 210 may be further configured to generate a third opacity count indicative of contaminants and/or bubbles in at least some of the degassed liquid 224. As illustrated, the at least one liquid particle counter 210 may be fluidly coupled to the at least one degasser 222 via a third fluid path 226. In some embodiments, a single liquid particle counter 210 may be fluidly coupled to the sonication cleaning tank 202, the at least one filter 206 and the at least one degasser 222 and may be configured to generate the first, second and third opacity counts. However, in other embodiments, the at least one liquid particle counter 210 may include a first liquid particle counter fluidly coupled to the sonication cleaning tank 202 and configured to generate the first opacity count, a second liquid particle counter fluidly coupled to the at least one filter 206 and configured to generate the second opacity count, and a third liquid particle counter fluidly coupled to the at least one degasser 222 and configured to generate the third opacity count. These different embodiments are discussed at greater length below.
In one embodiment, a flow rate through the at least one degasser 222 may be controlled. For example, a flow rate of less than 100 milliliters per minute may be maintained through the at least one degasser 222. As illustrated, the at least one liquid particle counter 210 may be fluidly coupled to an outlet of the at least one degasser 222, and the flow rate of the at least one liquid particle counter 210 may thus be controlled in order to maintain the flow rate through the at least one degasser 222. In other embodiments, other components may be employed to control the flow rate through the at least one degasser 222. For example, the at least one degasser 222 may include its own proportional valve (not shown). By maintaining a relatively slow flow rate, the degassing efficiency of the at least one degasser 222 may be improved.
In one embodiment, the computing device 212 is further configured to determine a degassing efficiency associated with the at least one degasser 222 based at least in part on the first, second and third opacity counts. The degassing efficiency generally corresponds to the number of bubbles removed by the at least one degasser 222 divided by the total number of bubbles in the liquid 204. In one embodiment, the degassing efficiency may be equal to a numerator divided by a denominator, wherein the numerator is equal to the third opacity count subtracted from the first opacity count (yielding an approximate number of bubbles removed by the at least one degasser 222) and the denominator is equal to the second opacity count (yielding an approximate number of bubbles in the liquid 204). In other embodiments, the third opacity count may be used for other calculations as well.
The computing device 212 may also take into account other variables when calculating the degassing efficiency. For example, the computing device 212 may factor in information indicative of a filtering efficiency of the at least one filter 206 in order to correct for contaminants included in the second opacity count. As another example, the computing device 212 may factor in information indicative of “natural” degassing that occurs between the sonication cleaning tank 202 and the at least one liquid particle counter 210 along the first fluid path 218 and/or the second fluid path 220.
In one embodiment, the overall flow of the liquid 304 through the sonication cleaning tank 302 may be generally parallel to the direction of propagation of the acoustic waves generated by a sonication generator (not shown). However, in other embodiments, a sonication generator may be otherwise oriented, such that the overall flow of the liquid 304 through the sonication cleaning tank 302 is generally perpendicular (or at some other angle) to the direction of propagation of the acoustic waves.
The sonication cleaning system 400 may include a flow control element 428 fluidly coupled to the sonication cleaning tank 402 via one or more ingress ports 401 and configured to cause the liquid 404 to flow through the sonication cleaning tank 402 from right to left (as illustrated in
The sonication cleaning tank 402 may further include a perforated side panel (not shown) near the ingress port(s) 401. The perforated side panel may be configured to create a generally laminar cross flow across the sonication cleaning tank 402 (from right to left in
The sonication cleaning system 400 may further include a sonication generator 430 configured to generate sonication (i.e., acoustic waves) through the liquid 404 within the sonication cleaning tank 402. The sonication generator 430 may generate megasonication, ultrasonication (a lower frequency sonication than megasonication), or acoustic waves at other frequencies. Ultrasonic cleaning may use lower frequencies and thereby produce more random cavitations, while megasonication may use higher frequencies and thereby produce more controlled cavitations.
In one embodiment, the sonication generator 430 may comprise a frequency generator configured to drive one or more sonication transducers (not shown). The sonication transducers may, in turn, generate the acoustic stream 432 emanating from the bottom of the sonication cleaning tank 402. The sonication generator 430 may also be electronically controlled, such that the frequency and/or amplitude of the generated sonication may be varied. For example, the sonication generator 430 may comprise a programmable digital generator having a range of 0 to 800 watts. Although illustrated at the bottom of the sonication cleaning tank 402, the sonication generator 430 and associated transducers may be oriented differently in order to generate acoustic waves traveling in other directions.
As illustrated, the sonication cleaning system 400 includes two liquid particle counters 410a, 410b. The first liquid particle counter 410a may be fluidly coupled to the sonication cleaning tank 402 near one or more egress ports 403. In one embodiment, the first liquid particle counter 410a is configured to generate a first opacity count indicative of contaminants and/or bubbles in the liquid 404. The liquid 404 drawn through the first liquid particle counter 410a may then flow to the filter 406, which is fluidly coupled thereto. The filter 406 may then remove contaminants from at least some of the liquid 104 to produce filtered liquid 408, which may then flow to the second liquid particle counter 410b. In one embodiment, the second liquid particle counter 410b is configured to generate a second opacity count indicative of contaminants and/or bubbles in the filtered liquid 408 from the filter 406. The two liquid particle counters 410a, 410b may correspond to the at least one liquid particle counter 110 discussed at length above with respect to
In one embodiment, both liquid particle counters 410a, 410b are communicatively coupled to the computing device 412, which may be configured to determine a contaminant count corresponding to an estimated number of contaminants in the liquid 404 based at least in part on the first and second opacity counts. As illustrated, the computing device 412 may comprise a processor 412a operable to execute instructions and a computer-readable memory 412b having instructions stored thereon that are executable by the processor 412a in order to cause the processor 412a to perform certain functions (e.g., determining the contaminant count). In different embodiments, the computing device 412 may perform different functions, as described in greater detail below.
The sonication cleaning system 400 may further include a controller 434 coupled to the computing device 412 and configured to control at least one of the flow control element 428 and the sonication generator 430 based on at least one of the first and second opacity counts. The controller 434 may comprise, for example, a programmable logic controller. In one embodiment, the computing device 412 may send signals to the controller 434 based at least in part on the contaminant count, and the controller 434 may, in turn, control at least one of the flow control element 428 and the sonication generator 430 based at least in part on those signals. For example, if the contaminant count is relatively high, the controller 434 may cause the flow control element 428 to increase flow through the sonication cleaning tank 402 in order to “flush” the contaminants out more quickly, and/or the controller 434 may cause the sonication generator 430 to decrease power in order to slow down the generation of additional contaminants. In some embodiments, the computing device 412 and the controller 434 may be configured to control the flow control element 428 and the sonication generator 430 based on one or more control algorithms.
As illustrated, the sonication cleaning system 500 includes a recirculation loop 536 extending between one or more egress ports 503 and one or more ingress ports 501 of the sonication cleaning tank 502. Positioned along this recirculation loop 536, the filter 506 may be configured to remove contaminants washed away from the disk 516 before the liquid 504 is reintroduced into the sonication cleaning tank 502.
In one embodiment, at least two proportional valves 538a, b may be included in the sonication cleaning system 500. A first proportional valve 538a may be positioned between the sonication cleaning tank 502 and the liquid particle counter 510, and a second proportional valve 538b may be positioned between the filter 506 and the liquid particle counter 510. In one embodiment, the liquid particle counter 510 may drain liquid passing therethrough away from the recirculation loop 536, while, in another embodiment, the proportional valves 538a, b may comprise two-way valves, such that when a proportional valve 538 is “closed,” liquid might still pass through in one direction.
The proportional valves 538a, b may be manually operated. However, in other embodiments, a controller 540 (e.g., a programmable logic controller) may be coupled to and configured to control the first and second proportional valves 538a, b. The controller 540 may be configured to open the first proportional valve 538a and close the second proportional valve 538b in order to generate the first opacity count, and configured to close the first proportional valve 538a and open the second proportional valve 538b in order to generate the second opacity count. The controller 540 may also be communicatively coupled to a computing device (which may be the computing device 512 or another computing device), which may cause the controller 540 to open and close the proportional valves 538a, b according to a defined control algorithm.
As illustrated, the same liquid particle counter 510 may be used to generate opacity counts corresponding to both the liquid 504 and the filtered liquid 508. In one embodiment, the computing device 512 may be configured to determine a filter efficiency based at least in part on the first and second opacity counts. The filter efficiency may be determined by the computing device 512 in a variety of ways. In one embodiment, the filter efficiency may be determined by introducing a known quantity of contaminants into the liquid 504, and then comparing the known quantity of contaminants against the contaminant count determined based on the first and second opacity counts. The difference between the known quantity of contaminants and the contaminant count may be indicative of the filter efficiency. In another embodiment, historical averages of the first and second opacity counts may be used to determine an approximate filter efficiency based on relatively predictable contaminant and bubble levels produced during cleaning operations.
The computing device 512 may then compare the filter efficiency against a filter efficiency threshold, and trigger an alarm based at least in part on the comparison. The filter efficiency threshold may be defined by a user and stored on the computing device 512, and the threshold may correspond to a filter efficiency below which the filter 506 is no longer suitable for the cleaning operations of the sonication cleaning system 500. If the filter efficiency drops below the filter efficiency threshold, the alarm may alert an operator that the filter 506 should be changed. In one embodiment, the cleaning operations may also be halted based upon the alarm. Thus, the sonication cleaning system 500 may enable an operator to monitor the health of the filter 506 and replace it at appropriate intervals.
In one embodiment, the sonication cleaning system 600 includes a plurality of liquid particle counters 610a, b, c fluidly coupled to the sonication cleaning tank 602, the filter 606 and the degasser 622. In particular, a first liquid particle counter 610a may be fluidly coupled to the sonication cleaning tank 602 and configured to generate a first opacity count. A second liquid particle counter 610b may be fluidly coupled to the filter 606 and configured to generate a second opacity count. A third liquid particle counter 610c may be fluidly coupled to the degasser 622 and configured to generate the third opacity count. These liquid particle counters 610a, b, c may be of the same general configuration or may be differently configured. Thus, in one embodiment, rather than having a system of proportional valves and a single liquid particle counter, multiple liquid particle counters 610a, b, c may be employed. In one embodiment, the three liquid particle counters 610a, b, c may be communicatively coupled to a computing device (not shown).
In one embodiment, the degasser 622 is coupled to a vacuum source 642, as described above. The vacuum source 642 may comprise, for example, a venturi vacuum, a pump vacuum or some other vacuum generation apparatus.
As illustrated, the sonication cleaning system 700 includes a recirculation loop 736 extending between one or more egress ports 703 and one or more ingress ports 701 of the sonication cleaning tank 702. In one embodiment, a liquid particle counter 710 is positioned along this recirculation loop 736. The liquid particle counter 710 may be fluidly coupled to the sonication cleaning tank 702, the filter 706 and the degasser 722, and may be configured to generate the first opacity count, the second opacity count and the third opacity count.
In one embodiment, the sonication cleaning system 700 may further include at least three proportional valves 738a, b, c. A first proportional valve 738a may be positioned between the sonication cleaning tank 702 and the liquid particle counter 710. A second proportional valve 738b may be positioned between the filter 706 and the liquid particle counter 710. A third proportional valve 738c may be positioned between the degasser 722 and the liquid particle counter 710.
In one embodiment, the proportional valves 738a, b, c may be manually operated. However, in other embodiments, a controller 740 may be coupled to the proportional valves 738a, b, c. The controller 540 may be configured to open the first proportional valve 738a and close the second and third proportional valves 738b, c in order to generate the first opacity count, to open the second proportional valve 738b and close the first and third proportional valves 738a, c in order to generate the second opacity count, and to open the third proportional valve 738c and close the first and second proportional valves 738a, b in order to generate the third opacity count. Of course, in other embodiments, other valve configurations may be used to allow the liquid 704 to flow between the various components of the sonication cleaning system 700.
The sonication cleaning system 800 may include multiple filters 806a, b, c. A first filter 806a may be configured to remove a first type of contaminants from at least some of the liquid in the sonication cleaning tank to produce filtered liquid. A second filter 806b may be configured to remove a second type of contaminants from at least some of the liquid to produce filtered liquid. A third filter 806c may be configured to remove a third type of contaminants from at least some of the liquid to produce filtered liquid. The different filters 806 may remove a variety of contaminants. In one embodiment, the first filter 806a comprises an ionic chemical filter configured to remove ionic chemicals, the second filter 806b comprises a carbon filter configured to remove contaminants that react with the carbon (e.g., volatile organic compounds), and the third filter 806c comprises a particle filter (e.g., a paper filter) configured to remove particles above a certain minimum size. Of course, in other embodiments, any combination or sub-combination of the illustrated filters may be arranged in any order. Indeed, in some embodiments, a different set of filters may be used (including one or more of the same filters coupled in series or parallel). Each of the filters 806a, b, c may be fluidly coupled to the sonication cleaning tank and to the liquid particle counter 810.
The liquid particle counter 810 may be configured to generate a number of opacity counts corresponding to unfiltered, filtered and degassed liquids produced within the sonication cleaning system 800. In one embodiment, the liquid particle counter 810 is configured to generate a first opacity count indicative of contaminants and/or bubbles in the liquid (unfiltered by any of the filters 806), a second opacity count indicative of contaminants and/or bubbles in the liquid filtered using the first filter 806a, a third opacity count indicative of contaminants and/or bubbles in the liquid filtered using the second filter 806b, a fourth opacity count indicative of contaminants and/or bubbles in the liquid filtered using the third filter 806c and a fifth opacity count indicative of contaminants and/or bubbles in the liquid degassed by the degassers 822a, b coupled in series. The liquid particle counter 810 may also be configured to generate only a subset of the above opacity counts.
In other embodiments, the liquid particle counter 810 may also generate opacity counts indicative of contaminants and/or bubbles in liquid that has passed through more than one of the filters 806a, b, c. For example, the liquid particle counter 810 may be configured to generate a total filtered opacity count indicative of contaminants and/or bubbles in liquid filtered using all three filters 806a, b, c.
A computing device (not shown) may be coupled to the liquid particle counter 810 as discussed at length above. The computing device may be configured to generate a first contaminant count corresponding to an estimated number of the first type of contaminants (e.g., ionic chemicals) based at least in part on the first and second opacity counts, a second contaminant count corresponding to an estimated number of the second type of contaminants (e.g., contaminants that react with the carbon) based at least in part on the first and third opacity counts, and a third contaminant count corresponding to an estimated number of the third type of contaminants (e.g., particles in a certain size range) based at least in part on the first and fourth opacity counts. The computing device may be further configured to determine a degassing efficiency associated with the degassers 822a, b based at least in part on the first opacity count, the fifth opacity count and the total filtered opacity count.
As illustrated, the sonication cleaning system 800 may also include a plurality of proportional valves 838a-l. The proportional valves 838 may be positioned between the sonication cleaning tank (not shown), the first filter 806a, the second filter 806b, the third filter 806c, the degassers 822a, b, and the liquid particle counter 810. In one embodiment, the proportional valves 838 may be manually operated. However, in other embodiments, a controller (not shown) may be coupled to and configured to control the plurality of proportional valves 838. The controller may be configured to control the plurality of proportional valves 838 in order to generate the first opacity count, the second opacity count, the third opacity count, the fourth opacity count, the fifth opacity count, and the total filtered opacity count. For example, the first opacity count may be generated by controlling the plurality of proportional valves 838 to allow at least some of the liquid to flow from the sonication cleaning tank through the liquid particle counter 810. The second opacity count may be generated by controlling the plurality of proportional valves 838 to allow at least some of the liquid filtered using the first filter 806a to flow from the first filter 806a through the liquid particle counter 810. The third opacity count may be generated by controlling the plurality of proportional valves 838 to allow at least some of the liquid filtered using the second filter 806b to flow from the second filter 806b through the liquid particle counter 810. The fourth opacity count may be generated by controlling the plurality of proportional valves 838 to allow at least some of the liquid filtered using the third filter 806c to flow from the third filter 806c through the liquid particle counter 810. The fifth opacity count may be generated by controlling the plurality of proportional valves 838 to allow at least some of the liquid degassed using the degassers 822a, b to flow from the degasser 822b through the liquid particle counter 810. The total filtered opacity count may be generated by controlling the plurality of proportional valves 838 to allow at least some of the liquid filtered using all of the filters 806a-c to flow from the third filter 806c through the liquid particle counter 810. Of course, in other embodiments, different valve configurations may be used to control the flow of liquid between the components of the sonication cleaning system 800.
The sonication cleaning system 900 may include a plurality of degassers 948a-g associated with the plurality of filters 906a, b, c, and separated from the degassers 922a, b. Each of these degassers 948 may be configured similarly to the degassers 922, and may be configured to degas the liquid passing therethrough. Of course, in other embodiments, the degassers may be configured differently from the degassers 922.
As illustrated, the sonication cleaning system 1000 includes a plurality of degassers 1022. Each of the degassers 1022a, b, c is fluidly coupled to the sonication cleaning tank and configured to remove bubbles from at least some of the liquid to produce degassed liquid. In one embodiment, each of the degassers 1022a, b, c may be similarly configured. However, in other embodiments, different degassers may be used.
The liquid particle counter 1010 may be configured to generate a number of opacity counts corresponding to unfiltered, filtered and degassed liquids produced within the sonication cleaning system 1000. In one embodiment, the liquid particle counter 1010 is configured to generate a first opacity count indicative of contaminants and/or bubbles in the liquid, a second opacity count indicative of contaminants and/or bubbles in the liquid filtered using one or more of the filters 1006, a third opacity count indicative of contaminants and/or bubbles in the liquid degassed using a first degasser 1022a, a fourth opacity count indicative of contaminants and/or bubbles in the liquid degassed using a second degasser 1022b, and a fifth opacity count indicative of contaminants and/or bubbles in the liquid degassed using a third degasser 1022c.
In some embodiments, the liquid particle counter 1010 may also generate opacity counts indicative of contaminants and/or bubbles in liquid that has passed through more than one of the degassers 1022a-c. For example, the liquid particle counter 1010 may be configured to generate a total degassed opacity count indicative of contaminants and/or bubbles in liquid degassed using all three degassers 1022a-c.
A computing device (not shown) may be coupled to the liquid particle counter 1010 as discussed at length above. The computing device may be configured to generate a contaminant count corresponding to an estimated number of contaminants based at least in part on the first and second opacity counts, a first degassing efficiency associated with the first degasser 1022a based at least in part on the first, second and third opacity counts, a second degassing efficiency associated with the second degasser 1022b based at least in part on the first, second and fourth opacity counts, and a third degassing efficiency associated with the third degasser 1022c based at least in part on the first, second and fifth opacity counts. In one embodiment, the computing device may be further configured to generate a total degassing efficiency associated with all of the degassers 1022a-c based at least in part on the first opacity count, the second opacity count and the total degassed opacity count.
As illustrated, the sonication cleaning system 1000 may include a plurality of proportional valves 1038a-s. The proportional valves 1038 may be positioned between the sonication cleaning tank (not shown), the filters 1006a-c, the degassers 1022a-c and the liquid particle counter 1010. In one embodiment, the proportional valves 1038 may be manually operated. However, in other embodiments, a controller (not shown) may be coupled to and configured to control the plurality of proportional valves 1038. The controller may be configured to control the plurality of proportional valves 1038 in order to generate the first opacity count, the second opacity count, the third opacity count, the fourth opacity count, the fifth opacity count, and the total degassed opacity count. For example, the first opacity count may be generated by controlling the plurality of proportional valves 1038 to allow at least some of the liquid to flow from the sonication cleaning tank through the liquid particle counter 1010. The second opacity count may be generated by controlling the plurality of proportional valves 1038 to allow at least some filtered liquid to flow from one or more of the filters 1006 through the liquid particle counter 1010. The third opacity count may be generated by controlling the plurality of proportional valves 1038 to allow at least some of the liquid degassed using the first degasser 1022a to flow from the first degasser 1022a through the liquid particle counter 1010. The fourth opacity count may be generated by controlling the plurality of proportional valves 1038 to allow at least some of the liquid degassed using the second degasser 1022b to flow from the second degasser 1022b through the liquid particle counter 1010. The fifth opacity count may be generated by controlling the plurality of proportional valves 1038 to allow at least some of the liquid degassed using the third degasser 1022c to flow from the third degasser 1022c through the liquid particle counter 1010. The total degassed opacity count may be generated by controlling the plurality of proportional valves 1038 to allow at least some of the liquid degassed using all of the degassers 1022a-c to flow from the third degasser 1022c through the liquid particle counter 1010. Of course, in other embodiments, other valve configurations may be used to control the flow of liquid between the components of the sonication cleaning system 1000.
As described herein, many of the acts comprising the method 1100 may be orchestrated by a computing device 112, and, in particular, by a processor based at least in part on computer-readable instructions stored in computer-readable memory and executable by the processor. Of course, a manual implementation of one or more acts of the method 1100 may also be employed.
At act 1102, a first opacity count indicative of contaminants and/or bubbles in the liquid 104 is generated. As described in greater detail above, the first opacity count may be generated by passing at least some of the liquid 104 from the sonication cleaning tank 102 through a liquid particle counter 110 including a light sensor configured to generate signals indicative of the first opacity count.
In one embodiment, the first opacity count is generated while a cleaning operation is being carried out. For example, a disk 116 may first be placed into the sonication cleaning tank 102. The disk 116 may be lowered in a disk holder 114 movable between raised and lowered positions. The entire disk 116 may be submerged, as illustrated in
At act 1104, at least some of the liquid 104 is filtered to remove contaminants from the liquid 104. As described in greater detail above, at least some of the liquid 104 may pass through one or more filters 106 configured to remove contaminants therefrom. A variety of different filters may be used in order to remove various contaminants from the liquid 104.
At act 1106, a second opacity count indicative of contaminants and/or bubbles in the filtered liquid 108 is generated. The second opacity count may be generated in a manner similar to that employed at act 1102. That is, the filtered liquid 108 may be passed through a liquid particle counter 110. In some embodiments, a single liquid particle counter 110 may be used to generate both the first and the second opacity counts, using, for example, a system of valves. In other embodiments, multiple liquid particle counters may be positioned in the sonication cleaning system 100 in order to generate the different opacity counts (as illustrated in
As illustrated in
At act 1108, based at least in part on the first and second opacity counts, a contaminant count corresponding to an estimated number of contaminants in the liquid 104 may be determined. The contaminant count may be determined by a computing device 112 coupled to the at least one liquid particle counter 110. In one embodiment, the contaminant count is equal to the second opacity count subtracted from the first opacity count. Of course, the computing device 112 may also take into account other variables when calculating the contaminant count, as described at length above.
As illustrated in
In another embodiment, as illustrated in
Each of the first opacity count, the second opacity count and the third opacity count may be generated at least once every ten seconds. That is, the computing device 212 and the at least one liquid particle counter 210 may generate an opacity count measurement for each of the first, second and third opacity counts at least once every ten seconds. Indeed, in one embodiment, each of the first, second and third opacity counts may be generated at least once every six seconds. In such an embodiment, changes in the contaminant count and degassing efficiency of the sonication cleaning system 200 may be detected rapidly, and appropriate corrective actions may be taken.
The foregoing detailed description has set forth various embodiments of the systems and/or processes via the use of block diagrams, schematics, and examples. Insofar as such block diagrams, schematics, and examples contain one or more functions and/or operations, each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, the present subject matter may be implemented via Application Specific Integrated Circuits (ASICs). However, the embodiments disclosed herein, in whole or in part, can be equivalently implemented in standard integrated circuits, as one or more programs executed by one or more processors, as one or more programs executed by one or more controllers (e.g., microcontrollers), as firmware, or as virtually any combination thereof.
Number | Name | Date | Kind |
---|---|---|---|
3276458 | Davis et al. | Oct 1966 | A |
4181009 | Williamson | Jan 1980 | A |
4711256 | Kaiser | Dec 1987 | A |
4779451 | Ezawa et al. | Oct 1988 | A |
4865060 | Shibano | Sep 1989 | A |
4907611 | Shibano | Mar 1990 | A |
5089144 | Ozkahyaoglu et al. | Feb 1992 | A |
5286657 | Bran | Feb 1994 | A |
5301701 | Nafziger | Apr 1994 | A |
5482068 | Kitahara et al. | Jan 1996 | A |
5647386 | Kaiser | Jul 1997 | A |
5849104 | Mohindra et al. | Dec 1998 | A |
5868855 | Fukazawa et al. | Feb 1999 | A |
5873947 | Mohindra et al. | Feb 1999 | A |
5931173 | Schiele | Aug 1999 | A |
5988189 | Mohindra et al. | Nov 1999 | A |
6106590 | Ueno et al. | Aug 2000 | A |
6167891 | Kudelka et al. | Jan 2001 | B1 |
6172376 | Xu et al. | Jan 2001 | B1 |
6357458 | Tanaka et al. | Mar 2002 | B2 |
6402818 | Sengupta | Jun 2002 | B1 |
7004016 | Puskas | Feb 2006 | B1 |
7311847 | Kashkoush | Dec 2007 | B2 |
7976718 | Kashkoush et al. | Jul 2011 | B2 |
20020142617 | Stanton | Oct 2002 | A1 |
20030159713 | Park et al. | Aug 2003 | A1 |
20040016442 | Cawlfield | Jan 2004 | A1 |
20040035449 | Nam | Feb 2004 | A1 |
20040238005 | Takayama | Dec 2004 | A1 |
20070028437 | Kimura et al. | Feb 2007 | A1 |
20070267040 | Watanabe et al. | Nov 2007 | A1 |
20070289394 | Yao et al. | Dec 2007 | A1 |
20090088909 | Yokoi | Apr 2009 | A1 |
Number | Date | Country |
---|---|---|
02-157077 | Jun 1990 | JP |
2001-009395 | Jan 2001 | JP |
2007-326088 | Dec 2001 | JP |
2007-225335 | Sep 2007 | JP |
2007079695 | Aug 2007 | KR |
Entry |
---|
U.S. Appl. No. 12/473,223, filed May 27, 2009, 33 pages. |
Office Action dated Apr. 11, 2012 from U.S. Appl. No. 12/473,223, 8 pages. |
Office Action dated Sep. 5, 2012 from U.S. Appl. No. 12/473,223, 8 pages. |
Notice of Allowance dated Nov 30, 2012 from U.S. Appl. No. 12/473,223, 11 pages. |