Patent Grant
11573037
The present disclosure relates to a compressor floodback protection system.
This section provides background information related to the present disclosure and is not necessarily prior art.
A climate-control system such as, for example, a heat-pump system, a refrigeration system, or an air conditioning system, may include a fluid circuit having an outdoor heat exchanger, one or more indoor heat exchangers, one or more expansion devices disposed between the indoor and outdoor heat exchangers, and one or more compressors circulating a working fluid (e.g., refrigerant or carbon dioxide) between the indoor and outdoor heat exchangers. Efficient and reliable operation of the one or more compressors is desirable to ensure that the climate-control system in which the one or more compressors are installed is capable of effectively and efficiently providing a cooling and/or heating effect on demand.
This section provides a general summary of the disclosure, and is not a comprehensive disclosure of its full scope or all of its features.
In one form, the present disclosure provides a climate-control system that may include a compressor, a condenser, an evaporator, a first sensor, a second sensor, a third sensor, and a control module. The compressor may include a motor and a compression mechanism. The condenser receives compressed working fluid from the compressor. The evaporator is in fluid communication with the compressor and disposed downstream of the condenser and upstream of the compressor. The first sensor may detect an electrical operating parameter of the motor. The second sensor may detect a discharge temperature of working fluid discharged by the compression mechanism. The third sensor may detect a suction temperature of working fluid between the evaporator and the compression mechanism. The control module is in communication with the first, second and third sensors and may determine whether a refrigerant floodback condition is occurring in the compressor based on data received from the first, second and third sensors.
In some configurations, the control module determines whether the refrigerant floodback condition is occurring based on a comparison between a calculated discharge-superheat-value and a predetermined discharge-superheat-threshold.
In some configurations, the only measured data used to detect the refrigerant floodback condition is data measured by the first, second and third sensors.
In some configurations, a severity of the refrigerant floodback condition is determined based on a level of oil dilution in an oil sump of the compressor.
In some configurations, the control module issues a fault warning or a fault trip in response to determining the severity of the refrigerant floodback condition.
In some configurations, the level of oil dilution is calculated using the equation:
wherein P is a pressure of gas immediately above an oil level in the oil sump within the compressor; wherein ω is the level of oil dilution; wherein T is a temperature of the oil in the oil sump; and wherein a1 through a9 are constants.
In some configurations, the severity of the refrigerant floodback condition is determined based on a comparison of the level of oil dilution and a dilution limit value.
In some configurations, the dilution limit value is determined based on a calculated condensing temperature and a calculated evaporating temperature.
In some configurations, the pressure (P) of gas immediately above the oil level is measured by the third sensor.
In some configurations, the compressor is a low-side scroll compressor.
In another form, the present disclosure provides a system that may include a compressor, a first heat exchanger, a second heat exchanger, a first sensor, a second sensor, a third sensor, a fourth sensor, and processing circuitry. The compressor includes a shell, a compression mechanism disposed within the shell, and a motor driving the compression mechanism. The first heat exchanger may receive compressed working fluid from the compressor. The second heat exchanger is in fluid communication with the compressor and the first heat exchanger and may provide suction-pressure working fluid to the compressor. The first sensor may detect a parameter (e.g., electrical current of the motor or pressure of working fluid at a location along a high-pressure side of the system) indicative of a temperature of working fluid within the first heat exchanger (e.g., a saturated temperature or a condensing temperature). The second sensor may detect a discharge temperature of fluid discharged from the compressor. The third sensor may detect a suction temperature of fluid upstream of the compression mechanism and downstream of the first and second heat exchangers. The fourth sensor may detect an oil temperature of oil in a sump defined by the shell. The processing circuitry is in communication with the first, second, third and fourth sensors. The processing circuitry may determine whether a refrigerant floodback condition is occurring in the compression mechanism and a severity of the refrigerant floodback condition based on data received from the first, second, third and fourth sensors.
In some configurations, the first sensor is a current sensor that measures a current of the motor.
In some configurations, the first sensor is a pressure sensor that measures a pressure of working fluid at a location along a high-pressure side of the system.
In some configurations, the only measured data used to detect the refrigerant floodback condition is data measured by the first, second and third sensors.
In some configurations, the processing circuitry determines whether a refrigerant floodback condition has occurred based on a comparison between a calculated discharge-superheat-value and a predetermined discharge-superheat-threshold.
In some configurations, the severity of the refrigerant floodback condition is determined based on a level of oil dilution in an oil sump disposed within the shell of the compressor.
In some configurations, the level of oil dilution is calculated using the equation:
wherein P is a pressure of gas immediately above an oil level in the oil sump within the compressor; wherein co is the level of oil dilution; wherein T is a temperature of the oil in the oil sump; and wherein a1 through a9 are constants.
In some configurations, the severity of the refrigerant floodback condition is determined based on a comparison of the level of oil dilution and a dilution limit value.
In some configurations, the dilution limit value is determined based on a calculated condensing temperature and a calculated evaporating temperature.
In some configurations, the pressure (P) of gas immediately above the oil level is determined based on the suction temperature measured by the third sensor.
In some configurations, the processing circuitry issues a fault warning or a fault trip in response to determining the severity of the refrigerant floodback condition.
In some configurations, the compressor is a low-side scroll compressor.
Further areas of applicability will become apparent from the description provided herein. The description and specific examples in this summary are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.
The drawings described herein are for illustrative purposes only of selected embodiments and not all possible implementations, and are not intended to limit the scope of the present disclosure.
Corresponding reference numerals indicate corresponding parts throughout the several views of the drawings.
Example embodiments will now be described more fully with reference to the accompanying drawings.
Example embodiments are provided so that this disclosure will be thorough, and will fully convey the scope to those who are skilled in the art. Numerous specific details are set forth such as examples of specific components, devices, and methods, to provide a thorough understanding of embodiments of the present disclosure. It will be apparent to those skilled in the art that specific details need not be employed, that example embodiments may be embodied in many different forms and that neither should be construed to limit the scope of the disclosure. In some example embodiments, well-known processes, well-known device structures, and well-known technologies are not described in detail.
The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms “a,” “an,” and “the” may be intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms “comprises,” “comprising,” “including,” and “having,” are inclusive and therefore specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order discussed or illustrated, unless specifically identified as an order of performance. It is also to be understood that additional or alternative steps may be employed.
When an element or layer is referred to as being “on,” “engaged to,” “connected to,” or “coupled to” another element or layer, it may be directly on, engaged, connected or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being “directly on,” “directly engaged to,” “directly connected to,” or “directly coupled to” another element or layer, there may be no intervening elements or layers present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., “between” versus “directly between,” “adjacent” versus “directly adjacent,” etc.). As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
Although the terms first, second, third, etc. may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms may be only used to distinguish one element, component, region, layer or section from another region, layer or section. Terms such as “first,” “second,” and other numerical terms when used herein do not imply a sequence or order unless clearly indicated by the context. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the example embodiments.
Spatially relative terms, such as “inner,” “outer,” “beneath,” “below,” “lower,” “above,” “upper,” and the like, may be used herein for ease of description to describe one element or feature's relationship to another element(s) or feature(s) as illustrated in the figures. Spatially relative terms may be intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements described as “below” or “beneath” other elements or features would then be oriented “above” the other elements or features. Thus, the example term “below” can encompass both an orientation of above and below. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly.
With reference to
The compressor 12 may include a shell 24, a compression mechanism 26 and a motor 28. The compression mechanism 26 is disposed within the shell 24 and is driven by the motor 28 via a crankshaft (not shown). In the particular configuration shown in
While the compressor 12 is described above as a low-side compressor, in some configurations, the compressor 12 could be a high-side compressor (i.e., the compression mechanism 26, motor 28 and oil sump 34 could be disposed in a discharge-pressure region of the shell). Furthermore, in some configurations, the compressor 12 could be a reciprocating compressor or a rotary vane compressor, for example, rather than a scroll compressor.
In a cooling mode, the outdoor heat exchanger 14 may operate as a condenser or as a gas cooler and may cool discharge-pressure working fluid received from the compressor 12 by transferring heat from the working fluid to air forced over the outdoor heat exchanger 14 by the outdoor blower 15, for example. The outdoor blower 15 could include a fixed-speed, multi-speed or variable-speed fan. In the cooling mode, the indoor heat exchanger 18 may operate as an evaporator in which the working fluid absorbs heat from air forced over the indoor heat exchanger 18 by the indoor blower 19. In a heating mode (in configurations where the system 10 is a heat pump), the outdoor heat exchanger 14 may operate as an evaporator, and the indoor heat exchanger 18 may operate as a condenser or as a gas cooler and may transfer heat from working fluid discharged from the compressor 12 to air forced over the indoor heat exchanger 18 by the indoor blower 19.
The control module 22 may be in communication with first, second, third and fourth sensors 36, 38, 40, 41. The first sensor 36 may be a current sensor disposed within the shell 24 that measures a current draw of the motor 28. The second sensor 38 may be a temperature sensor and may measure a discharge temperature of working fluid discharged from the compressor 12. In some configurations, the second sensor 38 may be mounted on a discharge line 42 that fluidly connects the compressor 12 and the outdoor heat exchanger 14. In some configurations, the second sensor 38 could be mounted within the compressor 12 (e.g., in the discharge-pressure region 32 or at the discharge passage of the compression mechanism 26). The third sensor 40 may be a temperature sensor and may measure a suction temperature of working fluid provided to the compressor 12. In some configurations, the third sensor 40 may be mounted on a suction line 44 that fluidly connects the compressor 12 and the indoor heat exchanger 18. In some configurations, the third sensor 40 may be mounted within the compressor 12 (e.g., in the suction-pressure region 30) or on a suction fitting connecting the suction line 44 with the shell of the compressor 12. The fourth sensor 41 may be a temperature sensor disposed within the oil sump 34 and may measure a temperature of oil in the oil sump 34. The sensors 36, 38, 40, 41 may take measurements and communicate those measurements to the control module 22 intermittently, continuously, or on-demand. Communication between the sensors 36, 38, 40, 41 and the control module 22 may be wired or wireless.
As described above, the control module 22 determines whether a floodback condition is occurring in the compressor 12 and a severity level of the floodback condition. The control module 22 may determine whether the floodback condition is occurring using measured data only from the first, second and third sensors 36, 38, 40.
A floodback condition is a condition where liquid working fluid flows into the suction line 44 from the evaporator 18. During a floodback condition, the working fluid in the suction line 44 may not be completely evaporated and may be at least partially in liquid phase (i.e., a mixture of gaseous and liquid working fluid or entirely liquid working fluid). Severe liquid floodback can be detrimental to the reliability of the compressor 12 and can unacceptably increase oil dilution and reduce oil viscosity and oil-film thicknesses between mating moving parts, which can damage the moving parts. Floodback conditions can be caused by blocked evaporator fans, stuck or malfunctioning expansion valves, and defrost cycles, for example.
While severe floodback can be detrimental to compressor health, lower levels of floodback can be beneficial. For example, acceptable levels of floodback can lower discharge temperatures and increase oil-film thicknesses during certain operating conditions of the system 10 (e.g., operating conditions where evaporating temperatures are low and condensing temperatures are high). Beneficial levels of floodback can expand the operating envelope of the compressor and reduce or eliminate the need for liquid-injection or vapor-injection systems in certain applications.
With reference to
The graph of
The condensing temperature is calculated for the individual compressor and is therefore specific to compressor model and size. The following equation is used in determining condensing temperature, where P is compressor power, C0-C9 are compressor-specific constants, Tcond is condensing temperature, and Tevap is evaporating temperature:
P=C0+(C1*T+cond)+(C2*Tevap)+(C3*Tcond2)+(C4*Tcond*Tevap)+(C5*Tevap2)+(C6*Tcond3)+(C7*Tevap*Tcond2)+(C8*Tcond*Tevap2)+(C9*Tevap3).
The above equation is applicable to all compressors, with constants C0-C9 being compressor model and size specific, as published by compressor manufacturers, and can be simplified as necessary by reducing the equation to a second-order polynomial with minimal compromise on accuracy. The equations and constants can be loaded into the control module 22 by the manufacturer, in the field during installation using a hand-held service tool, or downloaded directly to the control module 22 from the internet, for example.
The condensing temperature, at a specific compressor power (based on measured current draw by the first sensor 36), is determined by referencing a plot of evaporating temperature (using the equation above, for example) for a given system versus compressor power consumption. The condensing temperature can be read by cross-referencing power consumption (determined from a measured current reading) against the evaporating temperature plot. Therefore, the condensing temperature is simply a function of reading a current drawn at the first sensor 36. For example,
As an alternative to the above methods for determining condensing temperature, the condensing temperature may be calculated using only motor current data (e.g., from the first sensor 36). That is, the condensing temperature may be calculated from a polynomial equation based on a regression of current (amperage) versus condensing temperature data (e.g., data published by a compressor manufacturer), where the motor current correlates closely to condensing pressure (and therefore, condensing temperature), as shown in
Tcond=−0.0006A5+0.001A4−0.0899A3+3.8446A2−75.683A+601.96.
The above equation is applicable to all compressors (with constants C0-C5 being chosen for a specific compressor) and can be simplified as necessary by reducing the equation to a lesser-order polynomial with minimal comprise on accuracy. Multiple equations can be generated as necessary to account for additional variables (such as voltage or operating speed) on the behavior of condensing pressure on current. Because the principles of the present disclosure can be used with multi-speed compressors and applied in multiple grid voltage situations, the above equation may be corrected based on a motor speed (e.g., obtained from current signal) and a measured voltage, for example.
While step 110 of the floodback-detection algorithm 100 is described above as determining a non-measured condensing temperature, in some configurations of the algorithm 100, the control module 22 may, at step 110, obtain a measured condensing temperature value from a temperature sensor that measures condensing temperature directly. In such configurations, the first sensor 36 may be a temperature sensor disposed on or in a coil of the outdoor heat exchanger 14, for example. The first sensor 36 may measure the condensing temperature and communicate the measured condensing temperature value to the control module 22 via a wired or wireless connection between the first sensor 36 and the control module 22. Alternatively, the first sensor 36 may be a pressure sensor measuring the pressure of working fluid at a high-pressure side of the system 10 (e.g., at a location at or near the outdoor heat exchanger 14 or along the discharge line 42, for example. The control module 22 may receive this pressure data from the first sensor 36 and convert the measured pressure value to a condensing temperature value (i.e., since the pressure of the working fluid at a location within the system 10 is proportional to the temperature of the working fluid at the same location).
Referring again to
The control module 22 may calculate the actual discharge-superheat-value (step 130) by subtracting the condensing temperature (determined at step 110) from the temperature measurement taken by the second sensor 38 (i.e., discharge temperature; hereinafter, Tdis). Stated in the form of an equation, DSHactual=Tdis−Tcond.
After steps 120 and 130 are complete, the control module 22 may, at step 140, compare the actual discharge-superheat-value (calculated at step 130) with the theoretical discharge-superheat-value (determined at step 120). If the actual discharge-superheat-value is greater than or equal to the theoretical discharge-superheat-value, then the control module 22 determines that a floodback condition does not exist and the working fluid in the discharge line 42 is superheated (step 150). If the actual discharge-superheat-value is less than the theoretical discharge-superheat-value, then the control module 22 determines that a floodback condition does exist (step 160).
If the control module 22 determines that a floodback condition exists, the control module 22 may execute a floodback protection algorithm 200 (
At step 220, the control module 22 may calculate an actual oil dilution value using the following equation:
where P is a pressure of gaseous working fluid immediately above an oil level in the oil sump 34 within the compressor 12, ω is the actual oil dilution value, T is a temperature of the oil in the oil sump 34 (measured by the fourth sensor 41), and a1 through a9 are constants. In a low-side compressor, the pressure P of the gaseous working fluid immediately above the oil level in the oil sump 34 can be assumed to be equal to evaporating pressure (calculated or measured at step 210). The constants a1 through a9 are dilution coefficients that are provided by working fluid (e.g., refrigerant) manufacturers for a combination of a given working fluid and a given oil. Exemplary dilution coefficients provided by DuPont™ for a combination of Suva® R410A refrigerant and POE (polyolester) synthetic oil are shown in
At step 230, the control module 22 may determine a dilution limit value based on a pressure ratio (condensing pressure to evaporating pressure) of the system 10. Because a one-to-one correlation exists between condensing pressure and condensing temperature and between evaporating pressure and evaporating temperature, the pressure ratio (Pratio) of the system 10 can be calculated by the equation Pratio=Tcond/Tevap. As described above, the condensing temperature is calculated at step 110 of the floodback detection algorithm 100, and evaporating temperature can be assumed to be equal to the suction temperature measured by the third sensor 40. Once the pressure ratio is determined, the control module 22 can determine the dilution limit value by a lookup table or from the graph and equation shown in
At step 240, the control module 22 may compare the actual dilution value (determined at step 220) and the dilution limit value (determined at step 230). If the actual dilution value is less than or equal to the dilution limit value, the control module 22 may determine that the floodback is at an acceptable level (step 250). If the actual dilution value is greater than the dilution limit value, the control module 22 may determine that the floodback is at an unacceptable level (step 260). If the floodback is at an unacceptable level, the control module 22 may, at step 270, issue a fault warning or notification, change a rotational speed of the motor 28 of the compressor 12, trip a motor protector temporarily disabling the compressor 12, and/or control the expansion device 16, the compressor motor 28, pumps (not shown), and/or blowers 15, 19, for example, to reduce or eliminate the floodback.
While the algorithm 200 is described above as determining whether the floodback condition is at an acceptable level or an unacceptable level based on oil dilution values, in some configurations, the algorithm 200 may determine the severity of the floodback condition based on oil viscosity values.
In this application, including the definitions below, the term “module” may be replaced with the term “circuit” or “processing circuitry.” The term “module” may refer to, be part of, or include: an Application Specific Integrated Circuit (ASIC); a digital, analog, or mixed analog/digital discrete circuit; a digital, analog, or mixed analog/digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor circuit (shared, dedicated, or group) that executes code; a memory circuit (shared, dedicated, or group) that stores code executed by the processor circuit; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip.
The module may include one or more interface circuits. In some examples, the interface circuits may include wired or wireless interfaces that are connected to a local area network (LAN), the Internet, a wide area network (WAN), or combinations thereof. The functionality of any given module of the present disclosure may be distributed among multiple modules that are connected via interface circuits. For example, multiple modules may allow load balancing. In a further example, a server (also known as remote, or cloud) module may accomplish some functionality on behalf of a client module.
The term code, as used above, may include software, firmware, and/or microcode, and may refer to programs, routines, functions, classes, data structures, and/or objects. The term shared processor circuit encompasses a single processor circuit that executes some or all code from multiple modules. The term group processor circuit encompasses a processor circuit that, in combination with additional processor circuits, executes some or all code from one or more modules. References to multiple processor circuits encompass multiple processor circuits on discrete dies, multiple processor circuits on a single die, multiple cores of a single processor circuit, multiple threads of a single processor circuit, or a combination of the above. The term shared memory circuit encompasses a single memory circuit that stores some or all code from multiple modules. The term group memory circuit encompasses a memory circuit that, in combination with additional memories, stores some or all code from one or more modules.
The term memory circuit is a subset of the term computer-readable medium. The term computer-readable medium, as used herein, does not encompass transitory electrical or electromagnetic signals propagating through a medium (such as on a carrier wave); the term computer-readable medium may therefore be considered tangible and non-transitory. Non-limiting examples of a non-transitory, tangible computer-readable medium are nonvolatile memory circuits (such as a flash memory circuit, an erasable programmable read-only memory circuit, or a mask read-only memory circuit), volatile memory circuits (such as a static random access memory circuit or a dynamic random access memory circuit), magnetic storage media (such as an analog or digital magnetic tape or a hard disk drive), and optical storage media (such as a CD, a DVD, or a Blu-ray Disc).
The apparatuses and methods described in this application may be partially or fully implemented by a special purpose computer created by configuring a general purpose computer to execute one or more particular functions embodied in computer programs. The descriptions above serve as software specifications, which can be translated into the computer programs by the routine work of a skilled technician or programmer.
The computer programs include processor-executable instructions that are stored on at least one non-transitory, tangible computer-readable medium. The computer programs may also include or rely on stored data. The computer programs may encompass a basic input/output system (BIOS) that interacts with hardware of the special purpose computer, device drivers that interact with particular devices of the special purpose computer, one or more operating systems, user applications, background services, background applications, etc.
The computer programs may include: (i) descriptive text to be parsed, such as HTML (hypertext markup language) or XML (extensible markup language), (ii) assembly code, (iii) object code generated from source code by a compiler, (iv) source code for execution by an interpreter, (v) source code for compilation and execution by a just-in-time compiler, etc. As examples only, source code may be written using syntax from languages including C, C++, C#, Objective C, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, Javascript®, HTML5, Ada, ASP (active server pages), PHP, Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, Visual Basic®, Lua, and Python®.
None of the elements recited in the claims are intended to be a means-plus-function element within the meaning of 35 U.S.C. § 112(f) unless an element is expressly recited using the phrase “means for,” or in the case of a method claim using the phrases “operation for” or “step for.”
The foregoing description of the embodiments has been provided for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure. Individual elements or features of a particular embodiment are generally not limited to that particular embodiment, but, where applicable, are interchangeable and can be used in a selected embodiment, even if not specifically shown or described. The same may also be varied in many ways. Such variations are not to be regarded as a departure from the disclosure, and all such modifications are intended to be included within the scope of the disclosure.
This application is a divisional of U.S. patent application Ser. No. 15/428,410, filed on Feb. 9, 2017, which claims the benefit of U.S. Provisional Application No. 62/296,841, filed on Feb. 18, 2016. The entire disclosures of the above applications are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4918931 | Lowes | Apr 1990 | A |
| 6018959 | Schmidt | Feb 2000 | A |
| 6578373 | Barbier | Jun 2003 | B1 |
| 7079967 | Rossi et al. | Jul 2006 | B2 |
| 7114343 | Kates | Oct 2006 | B2 |
| 7201006 | Kates | Apr 2007 | B2 |
| 7234313 | Bell et al. | Jun 2007 | B2 |
| 7412842 | Pham | Aug 2008 | B2 |
| 7469546 | Kates | Dec 2008 | B2 |
| 7484376 | Pham | Feb 2009 | B2 |
| 7775057 | VanderZee | Aug 2010 | B2 |
| 8418483 | McSweeney et al. | Apr 2013 | B2 |
| 8459051 | Jeong et al. | Jun 2013 | B2 |
| 8572995 | Kasahara | Nov 2013 | B2 |
| 8590328 | Bittner et al. | Nov 2013 | B2 |
| 8924181 | Hrncar et al. | Dec 2014 | B2 |
| 20030005710 | Singh | Jan 2003 | A1 |
| 20030077179 | Collins et al. | Apr 2003 | A1 |
| 20040194485 | Dudley | Oct 2004 | A1 |
| 20050235660 | Pham | Oct 2005 | A1 |
| 20060259276 | Rossi et al. | Nov 2006 | A1 |
| 20070089436 | Singh et al. | Apr 2007 | A1 |
| 20070089437 | Singh | Apr 2007 | A1 |
| 20070205296 | Bell et al. | Sep 2007 | A1 |
| 20080209925 | Pham | Sep 2008 | A1 |
| 20090090118 | Pham | Apr 2009 | A1 |
| 20090094997 | McSweeney | Apr 2009 | A1 |
| 20090095002 | McSweeney et al. | Apr 2009 | A1 |
| 20100204840 | Sun et al. | Aug 2010 | A1 |
| 20110185753 | Lifson et al. | Aug 2011 | A1 |
| 20110209485 | Lifson et al. | Sep 2011 | A1 |
| 20120247138 | Sent, Jr. et al. | Oct 2012 | A1 |
| 20120260678 | Yoshida | Oct 2012 | A1 |
| 20120272673 | Yokohara et al. | Nov 2012 | A1 |
| 20130167567 | Fukui et al. | Jul 2013 | A1 |
| 20140137573 | Lin et al. | May 2014 | A1 |
| 20140138451 | Pham | May 2014 | A1 |
| 20140163744 | Dolcich et al. | Jun 2014 | A1 |
| 20150027139 | Lin et al. | Jan 2015 | A1 |
| 20150033780 | Hatomura et al. | Feb 2015 | A1 |
| 20150068231 | Rite et al. | Mar 2015 | A1 |
| 20160018148 | Yura | Jan 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 101506600 | Aug 2009 | CN |
| 204154404 | Feb 2015 | CN |
| 2952829 | Dec 2015 | EP |
| H07180933 | Jul 1995 | JP |
| WO-2009038624 | Mar 2009 | WO |
| Entry |
|---|
| Restriction Reguirement regarding U.S. Appl. No. 15/428,410, dated Mar. 25, 2019. |
| Office Action regarding U.S. Appl. No. 15/428,410, dated Jul. 11, 2019. |
| Notice of Allowance regarding U.S. Appl. No. 15/428,410, dated Nov. 25, 2019. |
| International Search Report regarding International Application No. PCT/US2017/018484, dated Jun. 1, 2017. |
| Written Opinion of the International Searching Authority regarding International Application No. PCT/US2017/018484, dated Jun. 1, 2017. |
| International Preliminary Report on Patentability regarding International Application No. PCT/US2017/018484, dated Aug. 30, 2018. |
| Search Report regarding European Patent Application No. 17753978.0, dated Oct. 4, 2019. |
| Office Action regarding Chinese Patent Application No. 201780017945.6, dated Feb. 26, 2020. Translation provided by Unitalen Attorneys at Law. |
| Second Chinese Office Action regarding Application No. 201780017945.6 dated Oct. 10, 2020. English translation provided by Unitalen Attorneys at Law. |
| European Office Action regarding European Patent Application No. 17753978.0 dated Dec. 22, 2021. |
| Number | Date | Country | |
|---|---|---|---|
| 20200166256 A1 | May 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62296841 | Feb 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15428410 | Feb 2017 | US |
| Child | 16780270 | US |
