The present disclosure relates to systems for displaying messages with respect to compressor system operation.
The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent the work is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.
Compressors are used in a wide variety of industrial and residential applications including, but not limited to, heating, ventilating, and air conditioning (HVAC) systems. Electric motors are used to power and/or actuate elements of the compressors. A control system for controlling operation of an electric motor of a compressor can include a drive. The drive can include: a power factor correction (PFC) circuit; filters, such as an electromagnetic interference (EMI) filter and a direct current filter; an inverter power circuit; a processor; and other circuit components.
A drive of a compressor may include a rectifier that converts, for example, alternating current (AC) power received via utility power source via power lines to a direct current (DC) voltage, which is received at a DC bus. The DC bus provides the DC voltage to an inverter. The inverter converts the DC voltage to an AC voltage that is supplied to a compressor. A condenser fan motor may be connected (i) to the power lines that provide power to the drive, (ii) via a fan inverter, to a DC bus connected to an output of a PFC circuit, or (iii) to power lines connected to and providing power to the compressor. The power lines and the DC bus can be at high voltage potentials. For example, the utility power lines may be at 575 VAC and the DC bus may be at 810 VDC. As a result, the condenser fan motor is rated for 575 VAC. Typically, the condenser fan motor is rated for the same AC voltage as the power lines supplying power to the drive. In general, the higher the AC voltage rating of the condenser fan motor, the more specialized and/or costly the condenser fan motor.
A drive circuit is provided and includes a rectification circuit, a buck converter, a first inverter, and a second inverter. The rectification circuit is configured to rectify a first AC voltage signal to generate a rectified voltage signal. The buck converter is configured to downconvert the rectified voltage signal to a DC voltage signal, wherein the DC voltage signal is supplied to a DC bus. The first inverter is configured to convert the DC voltage signal to a second AC voltage signal and supply the second AC voltage signal to a compressor motor. The second inverter is configured to convert the DC voltage signal to a third AC voltage signal and supply the third AC voltage signal to a condenser fan motor. Peak voltages of the second AC voltage signal and the third AC voltage signal are less than peak voltages of the first AC voltage signal.
In other features, a drive circuit includes a rectification circuit, a buck converter, a first inverter and a condenser fan motor. The rectification circuit is configured to rectify a first AC voltage signal to generate a rectified voltage signal. The buck converter is configured to downconvert the rectified voltage signal to a first direct current (DC) voltage signal, wherein the first DC voltage signal is supplied to a DC bus. The first inverter is configured to convert the first DC voltage signal to a second AC voltage signal and supply the second AC voltage signal to a compressor motor. The condenser fan motor assembly is configured to receive the first DC voltage signal and one of: convert the first DC voltage signal to a third AC voltage signal and supply the third AC voltage signal to a condenser fan motor; pulse the first DC voltage signal and supply the pulsed first DC voltage signal to the condenser fan motor; and convert the first DC voltage signal to a second DC voltage signal and supply a pulsed version of the second DC voltage signal to the condenser fan motor.
In other features, a drive circuit is provided and includes a rectification circuit, a buck converter, and a first inverter. The rectification circuit is configured to rectify a first AC voltage signal to generate a rectified voltage signal. The buck converter is configured to downconvert the rectified voltage signal to a DC voltage signal, where the DC voltage signal is supplied to a DC bus. The first inverter is configured to convert the DC voltage signal to a second AC voltage signal and supply the second AC voltage signal to a compressor motor and to a condenser fan motor. Peak voltages of the second AC voltage signal are less than peak voltages of the first AC voltage signal.
Further areas of applicability of the present disclosure will become apparent from the detailed description, the claims and the drawings. The detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the disclosure.
In the drawings, reference numbers may be reused to identify similar and/or identical elements.
A refrigeration system includes a drive, a compressor and a condenser fan motor. The drive receives power from a utility power source via power lines and supplies the power to a compressor. The condenser fan motor may receive power from the power lines supplying power to the drive or receive power directly from the drive. The condenser fan motor may be rated for an AC voltage on the power lines. If this AC voltage is high (e.g., 575 VAC), the cost of the condenser fan motor is also high due to the need for high-voltage rated windings and satisfaction of high-voltage insulation to ground requirements. These types of condenser fan motors are typically produced in low volumes, which further increase costs of the condenser fan motors.
To minimize cost of a condenser fan motor, a required peak voltage rating of the condenser fan motor may be decreased by connecting the condenser fan motor to power lines supplying power to the drive via a transformer. The transformer downconverts a first AC voltage (e.g., 575 VAC or 600 VAC) of power lines supplying power to the drive to provide a second AC voltage (e.g., 480 VAC or 230 VAC), which can then be provided to the condenser fan motor. Although this reduces the peak voltage requirements and costs of the condenser fan motor, costs are increased due to use of the transformer. Also, the transformer to perform the stated downconversion can be large and heavy.
Compressor drives and corresponding circuits set forth herein include the use of buck converters to reduce peak voltage requirements of condenser fan motors. The buck converters reduce peak voltages received by condenser fan motors and provide output voltages that may be adjusted during operation. The disclosed embodiments are applicable to AC motors, DC motors, Induction motors, permanent magnetic motors, single phase motors, 3-phase motors, and/or other types of condenser fan motors.
The compressor 102 receives refrigerant in vapor form and compresses the refrigerant. The compressor 102 provides pressurized refrigerant in vapor form to the condenser 104. The compressor 102 includes an electric motor (or compressor motor) that drives a pump. For example only, the pump of the compressor 102 may include a scroll compressor and/or a reciprocating compressor.
All or a portion of the pressurized refrigerant is converted into liquid form within the condenser 104. The condenser 104 transfers heat away from the refrigerant, thereby cooling the refrigerant. When the refrigerant vapor is cooled to a temperature that is less than a saturation temperature, the refrigerant transforms into a liquid (or liquefied) refrigerant. The condenser 104 may include an electric fan that increases the rate of heat transfer away from the refrigerant.
The condenser 104 provides the refrigerant to the evaporator 108 via the expansion valve 106. The expansion valve 106 controls the flow rate at which the refrigerant is supplied to the evaporator 108. The expansion valve 106 may include a thermostatic expansion valve or may be controlled electronically by, for example, a system controller 130. A pressure drop caused by the expansion valve 106 may cause a portion of the liquefied refrigerant to transform back into the vapor form. In this manner, the evaporator 108 may receive a mixture of refrigerant vapor and liquefied refrigerant.
The refrigerant absorbs heat in the evaporator 108. Liquid refrigerant transitions into vapor form when warmed to a temperature that is greater than the saturation temperature of the refrigerant. The evaporator 108 may include an electric fan that increases the rate of heat transfer to the refrigerant.
A utility 120 provides power to the refrigeration system 100. For example only, the utility 120 may provide single-phase alternating current (AC) power at approximately 230 Volts root mean squared (VRMS). In other implementations, the utility 120 may provide three-phase AC power at approximately 400 VRMS, 480 VRMS, or 600 VRMS at a line frequency of, for example, 50 or 60 Hz. When the three-phase AC power is nominally 600 VRMS, the actual available voltage of the power may be 575 VRMS.
The utility 120 may provide the AC power to the system controller 130 via an AC line, which includes two or more conductors. The AC power may also be provided to a drive 132 via the AC line. The system controller 130 controls the refrigeration system 100. For example only, the system controller 130 may control the refrigeration system 100 based on user inputs and/or parameters measured by various sensors (not shown). The sensors may include pressure sensors, temperature sensors, current sensors, voltage sensors, etc. The sensors may also include feedback information from the drive control, such as motor currents or torque, over a serial data bus or other suitable data buses.
A user interface 134 provides user inputs to the system controller 130. The user interface 134 may additionally or alternatively provide the user inputs directly to the drive 132. The user inputs may include, for example, a desired temperature, requests regarding operation of a fan (e.g., a request for continuous operation of the evaporator fan), and/or other suitable inputs. The user interface 134 may take the form of a thermostat, and some or all functions of the system controller (including, for example, actuating a heat source) may be incorporated into the thermostat.
The system controller 130 may control operation of the fan of the condenser 104, the fan of the evaporator 108, and the expansion valve 106. The drive 132 may control the compressor 102 based on commands from the system controller 130. For example only, the system controller 130 may instruct the drive 132 to operate the motor of the compressor 102 at a certain speed or to operate the compressor 102 at a certain capacity. In various implementations, the drive 132 may also control the condenser fan.
A thermistor 140 is thermally coupled to the refrigerant line exiting the compressor 102 that conveys refrigerant vapor to the condenser 104. The variable resistance of the thermistor 140 therefore varies with the discharge line temperature (DLT) of the compressor 102. As described in more detail, the drive 132 monitors the resistance of the thermistor 140 to determine the temperature of the refrigerant exiting the compressor 102.
The DLT may be used to control the compressor 102, such as by varying capacity of the compressor 102, and may also be used to detect a fault. For example, if the DLT exceeds the threshold, the drive 132 may power down the compressor 102 to prevent damage to the compressor 102.
In
A charging circuit 208 controls power supplied from the EMI filter and protection circuit 204 to a power factor correction (PFC) circuit 212. For example, when the drive 132 initially powers up, the charging circuit 208 may place a resistance in series between the EMI filter and protection circuit 204 and the PFC circuit 212 to reduce the amount of current inrush. These current or power spikes may cause various components to prematurely fail.
After initial charging is completed, the charging circuit 208 may close a relay that bypasses the current-limiting resistor. For example, a control module 220 may provide a relay control signal to the relay within the charging circuit 208. In various implementations, the control module 220 may assert the relay control signal to bypass the current-limiting resistor after a predetermined period of time following start up, or based on closed loop feedback indicating that charging is near completion.
The PFC circuit 212 provides a power factor correction between an inputted AC and a generated DC. A power factor is an indicator of a relationship between current and voltage in a circuit, or how effectively a circuit uses real power as compared to reactive power, which is stored and returned to a power source. A power factor can be expressed as a value between zero and one. A power factor can be equal to a ratio of actual electrical power dissipated by a circuit relative to a product of root mean squared (RMS) values of current and voltage for the circuit. The power factor approaches 1 as this ratio increases. The PFC circuit can be implemented to increase a power factor of a drive, thereby increasing an amount of real power used by the circuit as compared with an amount of reactive power the circuit stores and returns to the power source.
The PFC circuit 212 converts incoming AC power to DC power. The PFC circuit 212 may not be limited to PFC functionality—for example, the PFC circuit 212 may also perform voltage conversion functions, such as acting as a boost circuit and/or a buck circuit. In some implementations, the PFC circuit 212 may be replaced by a non-PFC voltage converter. The DC power may have voltage ripples, which are reduced by filter capacitance 224. Filter capacitance 224 may include one or more capacitors arranged in parallel and connected to the DC bus. The PFC circuit 212 may attempt to draw current from the AC line in a sinusoidal pattern that matches the sinusoidal pattern of the incoming voltage. As the sinusoids align, the power factor approaches one, which represents the greatest efficiency and the least demanding load on the AC line.
The PFC circuit 212 includes one or more switches that are controlled by the control module 220 using one or more signals labeled as power switch control. The control module 220 determines the power switch control signals based on a measured voltage of the DC bus, measured current in the PFC circuit 212, AC line voltages, temperature or temperatures of the PFC circuit 212, and the measured state of a power switch in the PFC circuit 212. While the example of use of measured values is provided, the control module 220 may determine the power switch control signals based on an estimated voltage of the DC bus, estimated current in the PFC circuit 212, estimated AC line voltages, estimated temperature or temperatures of the PFC circuit 212, and/or the estimated or expected state of a power switch in the PFC circuit 212. In various implementations, the AC line voltages are measured or estimated subsequent to the EMI filter and protection circuit 204 but prior to the charging circuit 208.
The control module 220 is powered by a DC-DC power supply 228, which provides a voltage suitable for logic of the control module 220, such as 3.3 Volts, 2.5 Volts, etc. The DC-DC power supply 228 may also provide DC power for operating switches of the PFC circuit 212 and an inverter power circuit 232. For example only, this voltage may be a higher voltage than for digital logic, with 15 Volts being one example.
The inverter power circuit 232 also receives power switch control signals from the control module 220. In response to the power switch control signals, switches within the inverter power circuit 232 cause current to flow in respective windings of a motor 236 of the compressor 102. The control module 220 may receive a measurement or estimate of motor current for each winding of the motor 236 or each leg of the inverter power circuit 232. The control module 220 may also receive a temperature indication from the inverter power circuit 232.
For example only, the temperature received from the inverter power circuit 232 and the temperature received from the PFC circuit 212 are used only for fault purposes. In other words, once the temperature exceeds a predetermined threshold, a fault is declared and the drive 132 is either powered down or operated at a reduced capacity. For example, the drive 132 may be operated at a reduced capacity and if the temperature does not decrease at a predetermined rate, the drive 132 transitions to a shutdown state.
The control module 220 may also receive an indication of the discharge line temperature from the compressor 102 using the thermistor 140. An isolation circuit 260 may provide a pulse-width-modulated representation of the resistance of the thermistor 140 to the control module 220. The isolation circuit 260 may include galvanic isolation so that there is no electrical connection between the thermistor 140 and the control module 220.
The isolation circuit 260 may further receive protection inputs indicating faults, such as a high-pressure cutoff or a low-pressure cutoff, where pressure refers to refrigerant pressure. If any of the protection inputs indicate a fault and, in some implementations, if any of the protection inputs become disconnected from the isolation circuit 260, the isolation circuit 260 ceases sending the PWM temperature signal to the control module 220. Therefore, the control module 220 may infer that a protection input has been received from an absence of the PWM signal. The control module 220 may, in response, shut down the drive 132.
The control module 220 controls an integrated display 264, which may include a grid of LEDs and/or a single LED package, which may be a tri-color LED. The control module 220 can provide status information, such as firmware versions, as well as error information using the integrated display 264. The control module 220 communicates with external devices, such as the system controller 130 in
In
The PFC circuit 300 generates a DC bus, where a first terminal of the DC bus is connected to a cathode of the diode 316 while a second terminal of the DC bus is connected to the second output terminal of the rectifier 304 via the current sensor 312. The current sensor 312 can, therefore, sense the current within the switch 320 as well as the current in the DC bus and current in the inductor 308. The second terminal of the DC bus is also connected to a second terminal of the switch 320.
A driver 324 receives the power switch control signal from the control module 220 of
A switch monitor circuit 328 measures whether the switch is on or off. This closed loop control enables the control module 220 to determine whether the switch 320 has reacted to a command provided by the power switch control signal and may also be used to determine how long it takes the switch 320 to respond to that control signal. The measured switch state is output from the switch monitor circuit 328 back to the control module 220. The control module 220 may update its control of the power switch control signal to compensate for delays in turning on and/or turning off the switch 320.
In
Once the voltage at the anode of the diode 316 increases above the turn-on voltage of the diode 316, the current through the inductor 308 can be fed through the diode 316 to the DC bus. The current through the inductor 308 decreases and then the switch 320 is closed once more, causing the current and the inductor 308 to increase.
In various implementations, the switch 320 may be turned on until the current sensor 312 determines that a predetermined threshold of current has been exceeded. At that time, the switch 320 is turned off for a specified period of time. This specified period may be adaptive, changing along with the voltage of the DC bus as well as the voltage of the AC input change. However, the off time (when the switch 320 is open) is a specified value. Once a time equal to the specified value has elapsed, the switch 320 is turned back on again and the process repeats. The off time can be fixed or variable. In the case of the off time being variable, the off time can be limited to at least a predetermined minimum off time.
To reduce the physical size and parts cost of the PFC circuit 300, the inductance of the inductor 308 (which may be the largest contributor to the physical size of the PFC circuit 300) may be lowered. However, with a lower inductance, the inductor 308 will saturate more quickly. Therefore, the switch 320 will have to operate more quickly. While more quickly and smaller are relative terms, present power switching control operates in the range of 10 kilohertz to 20 kilohertz switching frequencies. In the present application, the switching frequency of the switch 320 may be increased to more than 50 kilohertz, more than 100 kilohertz, or more than 200 kilohertz. For example, the switching frequency of the switch may be controlled to be approximately 200 kilohertz.
The switch 320 is therefore chosen to allow for faster switching as well as to have low switching losses. With faster switching, the inductance of the inductor 308 can be smaller. In addition, the diode 316 may need to be faster. Silicon carbide diodes may have fast response times. For example, the diode 316 may be an STPSC2006CW Silicon Carbide dual diode package from STMicroelectronics.
In order to accurately drive the switch 320 when operating at higher speeds, the control strategy must similarly be accelerated. For example only, the control module 220 may include multiple devices, such as a microcontroller configured to perform more involved calculations and an FPGA (field programmable gate array) or PLD (programmable logic device) configured to monitor and respond to inputs in near real time. In this context, near real time means that the time resolution of measurement and time delay in responding to inputs of the FPGA or PLD is negligible compared to the physical time scale of interest. For faster switching speeds, the near real time response of the FPGA/PLD may introduce non-negligible delays. In such cases, the delay of the FPGA/PLD and driving circuitry may be measured and compensated for. For example, if the turn-off of a switch occurs later than needed because of a delay, the turn-off can be instructed earlier to compensate for the delay.
A bypass rectifier 340 is connected in parallel with the rectifier 304 at the AC line input. A second output terminal of the bypass rectifier 340 is connected to the second terminal rectifier 304. However, a first output terminal of the bypass rectifier 340 is connected to the cathode of the diode 316.
As a result, when the PFC circuit 300 is not operating to boost the DC bus voltage, the bypass rectifier 340 will be active when the line-to-line voltage of the AC input exceeds the voltage across the DC bus. The bypass rectifier 340, in these situations, diverts current from passing through the diode 316. Because the inductor 308 is small, and the switch 320 switches rapidly, the diode 316 is also selected to exhibit fast switching times. The diode 316 may, therefore, be less tolerant to high currents, and so current is selectively shunted around the diode 316 by the bypass rectifier 340.
In addition, the current path through the rectifier 304 and the diode 316 experiences three diode voltage drops or two diode voltage drops and the switch voltage drop, while the path through the bypass rectifier 340 experiences only two diode voltage drops. While the single phase AC input in
In
A three-phase rectifier 354 receives three-phase AC and generates pulsating DC across first and second terminals. A switch 358 is connected between the first terminal of the three-phase rectifier 354 and a common node. The common node is connected to an inductor 366 and a cathode of a power diode 370.
An anode of the power diode 370 is connected to a second terminal of the three-phase rectifier 354. An opposite terminal of the inductor 366 establishes one terminal of the DC bus, while the second output of the three-phase rectifier 354 establishes the other terminal of the DC bus. In the configuration shown in
A current sensor 362 is connected in series between the anode of the diode 370 and the DC bus. In other implementations, the current sensor 362 may be located in series with the inductor 366. In other implementations, the current sensor 362 may be located in series with the switch 358. In other implementations, the current sensor 362 may be located in series between the anode of the diode 370 and the second output of the three-phase rectifier 354. The current sensor 362 measures current through the inductor 366 as well as current through the DC bus and provides a current signal indicative of the amount of the current.
A driver 374 drives a control terminal of the switch 358 based on a power switch control signal from the control module 220 in
Various voltages are described with respect to the following
The portion 400 includes an EMI filter 406, a rectification circuit 408, an inductor 410, a diode 412, a switch 414, a driver 416 and one or more current sensors 418a, 418b. The EMI filter 406 receives a 3-phase AC voltage VAC from a 3-phase AC input 422. The EMI filter 406 may be connected to the output of the bridge rectifier 420 or an output of the first current sensor 418a. The EMI filter 406 filters the 3-phase AC voltage VAC. The rectification circuit 408 includes a bridge rectifier 420. The bridge rectifier 420 may include six diodes, as shown. The bridge rectifier 420 includes AC inputs, a return input and an output. The AC inputs of the bridge rectifier 420 receive a 3-phase AC voltage output from the EMI filter 406. The return inputs are connected to a same output 424 of the second current sensor 418b. The output of the bridge rectifier 420 is connected to the switch 414. An output voltage of the bridge rectifier 420 may be referred to as a main voltage. A DC output of the portion 400 is provided to a DC bus 426, which may refer to the DC bus connected between the PFC circuit 212 and the inverter power circuit 208 of
The inductor 410, diode 412, switch 414 and driver 416 provide an example implementation of the buck converter 404. The buck converter 404 may be configured differently than shown. The buck converter 404 operates as voltage and power converter. The buck converter 404 reduces a first (or main) voltage provided to the buck converter 404 to a second voltage provided to the DC bus 426. In one embodiment, the driver 416 controls ON time, OFF time, duty cycle and/or frequency of the switch 414 to adjust the voltage on the DC bus 426. The driver 416 may transition the switch between ON and OFF states based on an average mode control with a predetermined frequency, a variable minimum off time of the switch 414, a peak voltage mode control, and/or other control mode of operation. The average mode control referring to adjusting a duty cycle of the switch 414 and cycling the switch at the predetermined frequency.
The peak voltage mode control includes adjusting a peak voltage. The buck converter 404 reduces a peak voltage out of the bridge rectifier 420. The buck converter 404 may step down voltage while stepping up current. The buck converter 404 may be (i) OFF (operating in an inactive mode and switch 414 is held in an open state) or ON and operating in a low activity mode and switching the switch 414 between ON and OFF states at a low frequency for rising and falling portions of rectified AC signal out of the bridge rectifier 420, or (ii) ON, operating in a high activity mode, and switching the switch 414 between ON and OFF states at a high frequency near peaks of the rectified AC signal out of the bridge rectifier 420. The operation of the buck converter 404 limits the DC output voltage VDCOUT at the DC bus 426 while reducing power losses of the buck converter 404. In one embodiment, the buck converter 404 may be turned ON (i.e. the switch 414 is closed) and maintained in the ON state, such that there is no switching loses. This may occur during light load conditions. A peak voltage of the DC output voltage VDCOUT is based on (i) an average voltage at an output of the switch 414 minus a minor voltage drop across the inductor 410, and (ii) a duty cycle of the switch and voltage received at the switch 414.
The inductor 410 is connected (i) at a first end, to the switch and a cathode of the diode 412, and (ii) at a second end, to the DC bus 426 and a capacitor 430. The inductor 410 operates as a choke and may be small (e.g., 80 micro-Henry (μH)). The diode 412 may be formed of, for example, silicon carbide SiC. The anode of the diode 412 is connected to an input 432 of the second current sensor 418b and a reference terminal 434 (e.g., a ground reference). The switch 414 is connected in series with the inductor 410 between (i) the output of the primary bridge rectifier 420 and/or the first current sensor 418a and (ii) the inductor 410.
The switch 414 may be a transistor, such as a super-junction field effect transistor (FET), a power metal oxide semiconductor field-effect transistor (MOSFET), and/or a super-junction MOSFET. The switch 414 may be configured to be oscillated between ON (e.g., closed) and OFF (e.g., open) states at a high frequency (e.g., greater than or equal to 200 kilo-hertz (kHz)). A first terminal of the switch 414 is connected to the output of the bridge rectifier 420 or an output of the first current sensor 418a. A second terminal of the switch 414 is connected to the inductor 410 and a cathode of the diode 412.
A control terminal of the switch 414 receives a control signal SWCTRL from the driver (or switch driving control circuit) 416. The driver 416 generates the control signal SWCTRL based on an output signal PFCOUT of the control module 220. The control module 220 generates the output signal PFCOUT and the inverter signals INVOUT based on: one or more current sense signal PFCINC1, PFCINC2 from the current sensors 418; an AC signal PFCACREP representative of the AC voltage VAC; and a DC signal PFCDCREP that is representative of the DC output voltage VDCOUT. The current sense signal PFCINC1 may be equal to and/or indicative of an amount of current (i) passing through the inductor 410, and/or (ii) passing through the PFC circuit. The current sense signal PFCINC2 may be equal to and/or indicative of an amount of current (i) returning from the DC bus 426 to the second current sensor 418b, and/or (ii) passing through the PFC circuit. The AC signal PFCACREP may be equal to and/or indicative of the AC voltage VAC. The DC signal PFCDCREP may be equal to and/or indicative of the DC output voltage VDCOUT.
The capacitor 430 may be connected between the DC bus 426 and the reference terminal 434. The capacitor 430 may be connected (i) at a first end, to the inductor 410 and the DC bus 426, and (ii) at a second end, to the input 432 of the second current sensor 418b and the reference terminal 434.
The control module 220, which is further described below with respect to
The control module 220 may command a DC output voltage VDCOUT that is less than a peak voltage of the input voltage VAC and/or the output of the bridge rectifier 420 during a period when the DC output voltage VDCOUT is within a predetermined range. The predetermined range may be centered on the peak voltage of the input voltage VAC and/or the output of the bridge rectifier 420. The commanded voltages may be determined by the control module 220.
Since the buck converter 404 reduces the voltage provided to the DC bus 426, a low voltage condenser fan can be connected to the compressor power lines 452, 454, 456 or may be connected directly or indirectly to the DC bus 426 and reference terminal 434. As a first example embodiment, a 3-phase AC condenser fan motor 470 is connected to the compressor power lines 452, 454, 456 and receives power from the inverter. The 3-phase AC condenser fan motor 470 may be an induction motor, a permanent magnet motor, a single speed motor, a variable speed motor and/or other suitable motor. The 3-phase AC condenser fan motor 470 is configured to receive a predetermined peak voltage, such as 575 VAC, 480 VAC, 230 VAC, 208 VAC, or other AC voltage.
In another embodiment and as an alternative to using the 3-phase AC condenser fan motor 470, a condenser fan motor assembly 472 is connected to the DC bus 426 and the reference terminal 434 via lines 474, 476. The condenser fan motor assembly 472 includes a condenser fan motor 473 (e.g., a permanent magnet motor, an induction motor, a synchronous reluctance motor or other AC condenser fan motor) that may be a single speed or a variable speed motor. In one embodiment the condenser fan motor 473 is a switched reluctance motor that receives pulsed DC. The condenser fan motor assembly 472 is configured to receive a predetermined peak voltage, such as 810 VDC, 675 VDC, 300 VDC, or other DC voltage. The condenser fan motor assembly 472 may be directly connected to the DC bus 426 and the reference terminal 434 and may include a control circuit 480. The control circuit 480 may include a relay 482, a controller 484, a variable speed interface (VSI) 486 and/or other circuit components to transfer, adjust, and/or convert the received DC voltage signal from the DC bus 416. The predetermined peak voltage may be converted to AC via the control circuit 480 or may be pulsed by the control circuit 480 and provided to the condenser fan motor 473. Another example embodiment for indirectly connecting a condenser fan to the DC bus 426 and reference terminal 434 is described below with respect to
In one embodiment, inductors 490, 492, 494 are connected respectively to the compressor power lines 452, 454, 456 and to power inputs of the AC condenser fan motor 470. The inductors 490, 492, 494 may be included, for example, to reduce peak voltages seen by the AC condenser fan motor 470. The inductors 490, 492, 494 may be included based on an insulation rating of the AC condenser fan motor 470.
The relay 482 when in an open state disables the condenser fan motor 472 and when in a closed state enables the condenser fan motor 472. The VSI 486 may receive a control signal CONT from the control module 220 to adjust speed of the condenser fan motor 472. The control circuit 480 may close the relay 482 and/or adjust voltage to the condenser fan motor 472 based on the control signal CONT. The controller 484 may convert the DC voltage (first DC voltage) received from the DC bus 426 to (i) another (or second) DC voltage, or (ii) to an AC voltage. Thus, the control circuit 480 and/or the controller 484 may include a transformer to convert the first DC voltage. The controller 484 may vary the second DC voltage, a pulsed frequency of the first DC voltage, a pulsed frequency of the second DC voltage, or the AC voltage provided to the condenser fan motor 473 based on the control signal CONT.
During operation, the buck converter 404 downconverts a received voltage (e.g., 575 VAC) out of the bridge rectifier 420 to the DC voltage (e.g., 480 VAC, 230 VAC, or 208 VAC) received by the DC bus 426. The reduced DC voltage may be (i) converted to AC via the inverter and supplied to the compressor 102 and the AC condenser fan motor 470, or (ii) provided to the condenser fan motor assembly 472. The inverter outputs pulse width modulated (PWM) signals on the compressor power lines 452, 454, 456 that are received by the compressor 102 and the AC condenser fan motor 470. In one embodiment, the buck converter 404 may operate such that the received voltage is not downconverted, where a peak voltage provided to the inverter is a same as a peak voltage supplied to the bridge rectifier 420.
In one embodiment, the motor 488 of the compressor 102 and the AC condenser fan motor 470 are variable speed motors. In an embodiment, the motor 488 is an induction motor or a permanent magnet motor and the AC condenser fan motor 470 is an induction motor. The number of poles of the AC condenser fan motor 470 may be higher than the number of poles of the motor 488. The higher pole count causes the AC condenser fan motor 470 to spin at a lower speed than a speed of the motor 488 of the compressor 102. In one embodiment, the number of poles of the AC condenser fan motor 470 is twice the number of poles of the motor 488 of the compressor 102. In one embodiment, the number of poles of the AC condenser fan motor 470 is three times the number of poles of the motor 488 of the compressor 102. In another embodiment, both of the motors 470, 488 are induction motors and the number of poles of the AC condenser fan motor 470 is greater than the number of poles of the motor 488.
For further defined structure of the modules of
The output module 510 may operate in an active mode, an inactive mode, a low activity mode, a high activity mode, a full PFC mode, and a partial PFC mode. In an embodiment, frequency of oscillated operation of the switch 414 is decreased rather than deactivated. The frequency may be decreased to less than, for example, 200 kHz during low activity periods (or low activity mode). Timing of the low activity periods may be the same or similar to that of inactive periods. As an example, the frequency during the low activity periods may be an order of magnitude less than during the active periods (or active mode). As such, operation of the switch 414 may be transitioned between low activity modes and high activity modes rather than between inactive modes and active modes.
The full PFC mode may refer to when the buck converter 404 is continuously in an active or high activity mode to buck (or decrease) the DC bus voltage to match a commanded DC voltage VDCCOM. The partial PFC mode refers to switching between operating in (i) an active or high activity mode and (ii) an inactive or low activity mode.
In one embodiment, the timing module 513 switches from operating in the full PFC mode to operating in the partial PFC mode. The partial PFC mode reduces power losses by operating at reduced DC voltages and provides improved operating efficiency. The timing module 513 may, for example, operate in the partial PFC mode during light compressor loading conditions (e.g., load on compressor less than a predetermined load) and operate in the full PFC mode during heavy compressor loading conditions (e.g., load on compressor greater than or equal to the predetermined load). During the light load conditions, frequency of the switch 414 is decreased since the amount of current through the inductor 410 is low. As the current through the inductor 410 increases for increased load, the switch 414 may be pulse width modulated at a higher frequency to further decrease the bus voltage. This prevents overheating the inverter power circuit 232 of
The output module 510 generates signals PFCOUT and INV1-n based on outputs of the module 502, 504, 506, 608. In one embodiment, the inverter signals INV1-n include the inverter signals provided to the inverter of the compressor 102. In an alternative embodiment, the inverter signals INV1-n include the inverter signals provided to the compressor 102 and to an inverter of an AC condenser motor. This alternative embodiment is shown in
The inverter of the AC condenser fan motor 602 is provided by switches 610, 612, 614, 616, 618, 620. The switches 610, 612, 614, 616, 618, 620 are connected similar as the switches 440, 442, 444, 446, 448, 450 and to the DC bus 426 and reference terminal 434.
The AC condenser fan motor 602 is connected to and receives power from output terminals 630, 632, 634 via power lines 640, 642, 644. The output terminals 630, 632, 634 are connected respectively to (i) switches 610, 616, (ii) switches 612, 618, and (iii) switches 614, 620. In one embodiment, inductors 650, 652, 654 are connected to the output terminals 630, 632, 634 and inputs of the AC condenser fan motor 602 to reduce peak voltages seen by the AC condenser fan motor 602.
Although the example implementation of
The portion 700 includes an EMI filter 706, a rectification circuit 708, an inductor 710, a diode 712, a switch 714, a driver 716 and one or more current sensors 718a, 718b. The EMI filter 706 receives a single phase AC voltage VAC from a single phase AC input 722. The EMI filter 706 may be connected to the output of the bridge rectifier 720 or an output of the first current sensor 718a. The EMI filter 706 filters the single phase AC voltage VAC. The rectification circuit 708 includes a bridge rectifier 720. The bridge rectifier 720 may include four diodes, as shown. The bridge rectifier 720 includes AC inputs, a return input and an output. The AC inputs of the bridge rectifier 720 receive a single phase AC voltage output from the EMI filter 706. The return inputs are connected to a same output 724 of the second current sensor 718b. The output of the bridge rectifier 720 is connected to the switch 714. An output voltage of the bridge rectifier 720 may be referred to as a main voltage. A DC output of the portion 700 is provided to a DC bus 726, which may refer to the DC bus connected between the PFC circuit 212 and the inverter power circuit 208 of
The inductor 710, diode 712, switch 714 and driver 716 provide an example implementation of the buck converter 704. The buck converter 704 may be configured differently than shown. The buck converter 704 operates as voltage and power converter. The buck converter 704 reduces a first (or main) voltage provided to the buck converter 704 to a second voltage provided to the DC bus 726. In one embodiment, the driver 716 controls ON time, OFF time, duty cycle and/or frequency of the switch 714 to adjust the voltage on the DC bus 726. The driver 716 may transition the switch between ON and OFF states based on an average mode control with a predetermined frequency, a variable minimum off time of the switch 714, a peak voltage mode control, and/or other control mode of operation. The average mode control referring to adjusting a duty cycle of the switch 714 and cycling the switch at the predetermined frequency.
The peak voltage mode control includes adjusting a peak voltage. The buck converter 704 reduces a peak voltage out of the bridge rectifier 720. The buck converter 704 may step down voltage while stepping up current. The buck converter 404 may be (i) OFF (operating in an inactive mode and switch 714 is held in an open state) or ON and switching the switch 714 between ON and OFF states at a low frequency for rising and falling portions of rectified AC signal out of the bridge rectifier 720, or (ii) ON, operating in a high activity mode, and switching the switch 714 between ON and OFF states at a high frequency near peaks of the rectified AC signal out of the bridge rectifier 720. The operation of the buck converter 704 limits the DC output voltage VDCOUT at the DC bus 726 while reducing power losses of the buck converter 704. In one embodiment, the buck converter 704 may be turned ON (i.e. the switch 714 is closed) and maintained in the ON state, such that there is no switching loses. This may occur during light load conditions.
The inductor 710 is connected (i) at a first end, to the switch and a cathode of the diode 712, and (ii) at a second end, to the DC bus 726 and a capacitor 730. The inductor 710 operates as a choke and may be small (e.g., 80 micro-Henry (μH)). The diode 712 may be formed of, for example, silicon carbide SiC. The anode of the diode 712 is connected to an input 732 of the second current sensor 718b and a reference terminal 734 (e.g., a ground reference). The switch 714 is connected in series with the inductor 710 between (i) the output of the primary bridge rectifier 720 and/or the first current sensor 718a and (ii) the inductor 710.
The switch 714 may be a transistor, such as a super-junction FET, a MOSFET, and/or a super-junction MOSFET. The switch 714 may be configured to be oscillated between ON (e.g., closed) and OFF (e.g., open) states at a high frequency (e.g., greater than or equal to 200 kilo-hertz (kHz)). A first terminal of the switch 714 is connected to the output of the bridge rectifier 720 or an output of the first current sensor 718a. A second terminal of the switch 714 is connected to the inductor 710 and a cathode of the diode 712.
A control terminal of the switch 714 receives a control signal SWCTRL from the driver (or switch driving control circuit) 716. The driver 716 generates the control signal SWCTRL based on an output signal PFCOUT of the control module 220. The control module 220 generates the output signal PFCOUT and the inverter control signal INVCONT based on: one or more current sense signal PFCINC1, PFCINC2 from the current sensors 718; an AC signal PFCACREP representative of the AC voltage VAC; and a DC signal PFCDCREP that is representative of the DC output voltage VDCOUT. The current sense signal PFCINC1 may be equal to and/or indicative of an amount of current (i) passing through the inductor 710, and/or (ii) passing through the PFC circuit. The current sense signal PFCINC2 may be equal to and/or indicative of an amount of current (i) returning from the DC bus 726 to the second current sensor 718b, and/or (ii) passing through the PFC circuit. The AC signal PFCACREP may be equal to and/or indicative of the AC voltage VAC. The DC signal PFCDCREP may be equal to and/or indicative of the DC output voltage VDCOUT.
The capacitor 730 may be connected between the DC bus 726 and the reference terminal 734. The capacitor 730 may be connected (i) at a first end, to the inductor 710 and the DC bus 726, and (ii) at a second end, to the input 732 of the second current sensor 718b and the reference terminal 734.
The control module 220, which is further described above with respect to
The control module 220 may command a DC output voltage VDCOUT that is less than a peak voltage of the input voltage VAC and/or the output of the bridge rectifier 720 during a period when the DC output voltage VDCOUT is within a predetermined range. The predetermined range may be centered on the peak voltage of the input voltage VAC and/or the output of the bridge rectifier 720. The commanded voltages may be determined by the control module 220.
Since the buck converter 704 reduces the voltage provided to the DC bus 726, a low voltage condenser fan can be connected to the compressor power lines 752, 754 or may be connected directly or indirectly to the DC bus 726 and reference terminal 734. As a first example embodiment, the single phase AC condenser fan motor 750 is connected to the compressor power lines 752, 754 and receives power from the inverter. The single phase AC condenser fan motor 752 may be an induction motor, a permanent magnet motor, a single speed motor, a variable speed motor and/or other suitable motor. The single phase AC condenser fan motor 752 is configured to receive a predetermined peak voltage, such as 575 VAC, 480 VAC, 230 VAC, 208 VAC, or other AC voltage.
In another embodiment and as an alternative to using the single phase AC condenser fan motor 752, a condenser fan motor assembly 754 is connected to the DC bus 726 and the reference terminal 734 via lines 774, 776. The condenser fan motor assembly 754 may be directly connected to the DC bus 726 and the reference terminal 734 and/or may include a control circuit 780, which may be configured similar to the control circuit 480 of
In one embodiment, inductors 790, 792 are connected respectively to the compressor power lines 752, 754 and to power inputs of the AC condenser fan motor 752. The inductors 790, 792 may be included, for example, to reduce peak voltages seen by the AC condenser fan motor 752. The inductors 790, 792 may be included based on an insulation rating of the AC condenser fan motor 752.
In one embodiment, the compressor 750 and the AC condenser fan motor 752 are variable speed devices. The number of poles of AC condenser fan motor 752 may be higher than the number of poles of a motor 788 of the compressor 750. The higher pole count causes the AC condenser fan motor 752 to spin at a lower speed than a speed of the motor 788 of the compressor 750. In one embodiment, the number of poles of the AC condenser fan motor 752 is twice the number of poles of the motor of the compressor 750.
For further defined structure of the modules of
The systems disclosed herein may be operated using numerous methods, an example methods is illustrated in
The method may begin at 800. At 802, the load module 502 may receive various signals and parameters from (i) the PFC circuit 212 of
At 804, the AC voltage module 504 may receive or generate the AC signal PFCACREP. The AC voltage module 504 may detect voltages at the output of the bridge rectifier 420. The AC signal PFCACREP may be set equal to and/or be representative of one or more of the output of the bridge rectifier 420.
At 806, the DC voltage module 506 may receive or generate the DC signal PFCDCREP. The DC voltage module 506 may (i) detect the voltage DCDCout at the DC bus between the PFC circuit 212 and the inverter power circuit 208, and/or (ii) receive a DC bus voltage indication signal from a sensor and/or module external to the control module 220 and/or the DC voltage module 506.
At 808, the current module 508 may determine an amount of current supplied to the compressor and/or passing through one or more of the current sensors 418. This may be based on the current sense signals PFCINC1, PFCINC2.
At 810, the reference generation module 514 may generate a reference sinusoidal signal and/or a reference rectified sinusoidal signal. The references signals may be generated based on the AC input signal VAC, an output of the EMI filter 406, and/or the output of the bridge rectifier 420. In one embodiment, the reference signals are generated based on the output of the EMI filter 406 or the output of the bridge rectifier 420. This may include estimating the phase of the output of the EMI filter 406 or the output of the bridge rectifier 420. The AC input signal VAC, the output of the bridge rectifier 420 and/or the output of the EMI filter 406 may have noise or irregular activity as not to be perfect sinusoidal and/or rectified sinusoidal waves. The reference generation module 514 generates the reference signals to be pure sinusoidal and/or rectified sinusoidal reference signals having the same phase as the AC input signal VAC, the output of the bridge rectifier 420 and/or the output of the EMI filter 406. This synchronizes the reference signals to the AC input signal VAC, the output of the bridge rectifier 402 and/or the output of the EMI filter 406. The reference generation module 514 may output reference data including phase, frequency, period, and/or other time-varying derivative (or gradient) of the reference signals. The reference data may include scaled versions of the reference signals.
At 812, the timing module 513 may generate the commanded DC voltage VDCCOM to be less than a peak (or maximum) AC input voltage VAC and/or a peak (or maximum) output voltage of the bridge rectifier 420. This is unlike traditional PFC circuits, which always have the commanded DC voltages above a peak AC input voltage. The commanded DC voltage VDCCOM may be set to be within a predetermined range of the peak output voltage of the bridge rectifier 420. As an example, as the load on the compressor increases, the commanded DC voltage VDCCOM may be decreased. By lowering the commanded DC voltage VDCCOM, the amount of time between end times and successive start times (or times between active modes and following inactive modes) of oscillated switch control operation increases. This allows the DC output voltage VDCOUT to increase during inactive periods to a higher peak voltage. Mode transition points refer to transitions between (i) the active (and/or high activity) mode (oscillated switch operation enabled) and (ii) the low activity mode. Examples of mode transition points are shown as cross-over points in
At 814, the timing module 513 may adjust: next start times and/or end times of the oscillated operation of the switch 414; duty cycle of the oscillated operation of the switch 414; frequency of the oscillated operation of the switch 414; frequency of inverter switches (e.g., the switches 442, 444, 446, 448, 450, 610, 612, 614, 616, 618, 620, 740, 742, 744, 746, and/or the control signal DCCONT. This may include adjusting times of rising and/or falling edges of the control signal SWCTRL. The stated adjustments may be performed to adjust a speed of one of the motors 470, 472, 602, 752, 754. The stated adjustment(s) may be based on the load of the compressor determined at 802, the AC voltage received and/or generated at 804, the DC voltage received and/or generated at 606, one or more of the current levels detected at 808, and/or one or more of the reference signals generated at 810. The adjustments may also be based on capacitance of the DC bus, torque commanded of the compressor, predicted voltages of the output of the bridge rectifier 420, and/or other parameters associated with operation of the drive circuit. The adjustments may advance or delay the transition start times and/or the transition end times. The adjustments may be determined based on equations, algorithms, maps, and/or tables relating the stated parameters, which may be stored in the memory 512 and accessed by the timing module 513. The adjustments may also be based on previous (historical) values and/or results, which may also be stored in and accessed from the memory 512. For example, if a last peak DC bus voltage or peak detected current (current detected by one of the current sensors 418a, 418b) was above a predetermined threshold, than the next transition end time or transition start time may be advanced to reduce the peak DC bus voltage and/or peak detected current.
At 816, the timing module 513 determines whether the phase angle of the output of the bridge rectifier 420 matches a predetermined start time of an active period. In addition or alternatively, voltages of the output of the bridge rectifier 420 (or input to switch 414) and/or the output of the buck converter 404 (or output of the inductor 410) may be compared to predetermined voltages for the predetermined start time to determine whether the stated condition exists. If there is a match, task 818 is performed, otherwise task 620 is performed.
At 818, the timing module 513 transitions to the inactive mode or low activity mode. If the timing module 513 transitions to the inactive mode, then the buck converter 404 is transitioned to an OFF state and the switch 414 is switched to an open state. If the timing module 513 transitions to the low activity mode, then oscillated operation of the switch 414 continues, but at a reduced frequency and/or at a reduced duty cycle, such that OFF times of the switch 414 are increased and/or ON times of the switch 414 are decreased. Task 802 may be performed subsequent to task 818.
At 820, the timing module 513 may determine whether the DC bus voltage is less than or equal to the commanded DC voltage VDCCOM and/or whether a next transition phase angle (next phase angle at which point a transition between operating modes occurs) is an end time (e.g., one of the end times e1-e6 of
At 821, the timing module 513 determines whether (i) a light load condition exists, (ii) VAC is less than a “high-line” voltage (is at or near a maximum operating voltage) and/or voltage out of the bridge 420 (or Vbridge) is less than a predetermined maximum voltage, and/or (iii) if temperature of the inverter power circuit 232 is inbound (i.e. within a predetermined temperature range). By checking if VAC is less than the “high-line” voltage and/or output of the bridge 420 Vbridge is less than the predetermined maximum voltage, the system prevents stress on the inverter power circuit 232 of
At 822, the timing module 513 remains in or transition to the low activity mode. Task 802 may be performed subsequent to task 822. At 824, the timing module 513 determines whether the phase angle is an end time of an active mode and/or a high activity mode. In addition or alternatively, a voltage of the output of the bridge rectifier 420 and/or the buck converter 404 may be compared to predetermined voltages for the end time to determine whether the stated condition exists. If the phase angle is an end time, task 826 is performed, otherwise task 828 is performed.
At 826, the timing module 513 transitions to the active (or high activity) mode. This includes oscillated operation of the switch 414 at a first (or high) frequency. The duty cycle of the switch 808, including durations of ON times and OFF times, may correspond to duty cycle information determined at 814. Task 802 may be performed subsequent to task 826. At 828, the timing module 513 operates in the active mode or high activity mode. Task 802 may be performed subsequent to task 828.
At 830, the switch 414 is held in a closed (or ON) state and is not switched between states. When the switch is ON, the portion 400 performs as a 3-phase rectifier with a DC choke. Thus, no switching occurs when VAC is at a nominal or low-line voltage. Task 802 may be performed subsequent to task 830.
When VAC is too high, switching of the switch 414 (or bucking) occurs to decrease the bus voltage VDCOUT. As the load increases, the bus voltage VDCOUT is decreased, the amount of current through the inductor 410 increases and the control module 220 begins bucking by pulse width modulating the switch 414 to lower the bus voltage VDCOUT (e.g., at tasks 826, 828) to a selected command voltage. The control module 220 may shape the current by adjusting the duty cycle of SWCTRL during this period for PFC operation. This may include providing a flat (or constant) amount of current through the choke or a profiled current shape. The ability to buck during certain conditions and not to buck during other conditions is referred to as “partial buck” operation.
During the light load condition, the switch 414 may be switched at a low frequency since the amount of current through the inductor 410 is low. As the current through the inductor 410 increases for increased load, the frequency of the switch 414 may be increased to decrease the bus voltage. This prevents overheating the inverter power circuit 232 of
Although the above tasks 816-830 are provided in a particular order, tasks 816-830 may be performed in a different order. As an example, task 821, 824, 826, 828 may be performed prior to tasks 816, 818, 820 and 822. If task 821, 824, 826, 828 are performed prior to tasks 816, 818, 820 and 822, then task 820 may be modified to determine whether the DC bus voltage is greater than or equal to the commanded voltage, the next transition phase angle is a start time of an active mode and/or high activity mode, and/or the current phase angle is within a predetermined range (e.g., between an end time of an inactive mode or a low activity mode and a subsequent start time of the inactive mode or low activity mode). This may include comparing a voltage of the outputs of the bridge rectifier 420 and/or the buck converter 404 to corresponding predetermined voltages and ranges to effectively determine if the next transition phase angle is a start time of an active mode and/or high activity mode, and/or the current phase angle is within a predetermined range.
The above-described operations of
The peak voltages for the condenser fan motors described above are not higher than and may be lower than peak voltages seen at the mains and/or voltages received by the buck converters. Levels of the peak voltages seen by the condenser fan motors can be adjusted by controlling the buck converters to adjust the DC voltage on the DC buses. Inclusion of a buck converter is less expensive than inclusion of a transformer for high-to-low voltage conversion. To adjust the speeds of the condenser motors, the DC bus voltages may be adjusted, frequencies of inverter switches may be adjusted, and/or control signals to condenser fan motor assemblies may be adjusted.
In one embodiment, a high AC voltage (e.g., 575 VAC or 600 VAC) is downconverted by a buck converter to a low DC voltage (e.g., 675 VDC or 300 VDC), which is provided to an inverter that outputs a low AC voltage (e.g., 480 VAC or 230 VAC). This allows for a low voltage inverter and low voltage condenser fan motor. In one embodiment, the condenser fan motor is an induction motor and the condenser fan motor is “slaved” to a compressor, such that the power inputs of the condenser are connected to power lines of the compressor. The condenser fan motor may run at the same stator frequency as the compressor. The speed of the condenser fan motor is related to the speed of the compressor. In this example, the number of poles of the condenser fan motor is greater than the number of poles of the compressor. Since the buck output voltages and the peak voltages supplied to the condenser fan motor are reduced, insulation phase-to-phase and winding to ground ratings of the condenser fan motor are reduced and rated for the peak voltages.
In another embodiment, the speed of the condenser fan motor is adjusted by adjusting PWM of the corresponding inverter. The PWM adjustment is controlled to maintain the output voltage of the inverter below or equal to a predetermined voltage (e.g., 230 VAC).
The foregoing description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. The broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent upon a study of the drawings, the specification, and the following claims. It should be understood that one or more steps within a method may be executed in different order (or concurrently) without altering the principles of the present disclosure. Further, although each of the embodiments is described above as having certain features, any one or more of those features described with respect to any embodiment of the disclosure can be implemented in and/or combined with features of any of the other embodiments, even if that combination is not explicitly described. In other words, the described embodiments are not mutually exclusive, and permutations of one or more embodiments with one another remain within the scope of this disclosure.
Spatial and functional relationships between elements (for example, between modules, circuit elements, semiconductor layers, etc.) are described using various terms, including “connected,” “engaged,” “coupled,” “adjacent,” “next to,” “on top of,” “above,” “below,” and “disposed.” Unless explicitly described as being “direct,” when a relationship between first and second elements is described in the above disclosure, that relationship can be a direct relationship where no other intervening elements are present between the first and second elements, but can also be an indirect relationship where one or more intervening elements are present (either spatially or functionally) between the first and second elements. As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A OR B OR C), using a non-exclusive logical OR, and should not be construed to mean “at least one of A, at least one of B, and at least one of C.”
In the figures, the direction of an arrow, as indicated by the arrowhead, generally demonstrates the flow of information (such as data or instructions) that is of interest to the illustration. For example, when element A and element B exchange a variety of information but information transmitted from element A to element B is relevant to the illustration, the arrow may point from element A to element B. This unidirectional arrow does not imply that no other information is transmitted from element B to element A. Further, for information sent from element A to element B, element B may send requests for, or receipt acknowledgements of, the information to element A.
In this application, including the definitions below, the term “module” or the term “controller” may be replaced with the term “circuit.” 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.
Some or all hardware features of a module may be defined using a language for hardware description, such as IEEE Standard 1364-2005 (commonly called “Verilog”) and IEEE Standard 1076-2008 (commonly called “VHDL”). The hardware description language may be used to manufacture and/or program a hardware circuit. In some implementations, some or all features of a module may be defined by a language, such as IEEE 1666-2005 (commonly called “SystemC”), that encompasses both code, as described below, and hardware description.
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 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 functional blocks and flowchart elements described 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 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), XML (extensible markup language), or JSON (JavaScript Object Notation) (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, Swift, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, Javascript®, HTML5 (Hypertext Markup Language 5th revision), Ada, ASP (Active Server Pages), PHP (PHP: Hypertext Preprocessor), Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, Visual Basic®, Lua, MATLAB, SIMULINK, 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.”
This application is a divisional of U.S. patent application Ser. No. 15/487,226 filed on Apr. 13, 2017. This application claims the benefit of U.S. Provisional Application No. 62/323,498, filed on Apr. 15, 2016, U.S. Provisional Application No. 62/323,505, filed Apr. 15, 2016, U.S. Provisional Application No. 62/323,607, filed Apr. 15, 2016, U.S. Provisional Application No. 62/398,641, filed on Sep. 23, 2016, and U.S. Provisional Application No. 62/398,658, filed on Sep. 23, 2016. The entire disclosures of the applications referenced above are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3723961 | McNaney | Mar 1973 | A |
4388578 | Green et al. | Jun 1983 | A |
4437146 | Carpenter | Mar 1984 | A |
4504922 | Johnson et al. | Mar 1985 | A |
4939473 | Eno | Jul 1990 | A |
5367617 | Goossen et al. | Nov 1994 | A |
5410360 | Montgomery | Apr 1995 | A |
5493101 | Innes | Feb 1996 | A |
5506484 | Munro et al. | Apr 1996 | A |
5583420 | Rice et al. | Dec 1996 | A |
5594635 | Gegner | Jan 1997 | A |
5600233 | Warren et al. | Feb 1997 | A |
5754036 | Walker | May 1998 | A |
5801516 | Rice et al. | Sep 1998 | A |
5823004 | Polley et al. | Oct 1998 | A |
5903130 | Rice et al. | May 1999 | A |
6018200 | Anderson et al. | Jan 2000 | A |
6031749 | Covington et al. | Feb 2000 | A |
6115051 | Simons et al. | Sep 2000 | A |
6137253 | Galbiati et al. | Oct 2000 | A |
6158887 | Simpson | Dec 2000 | A |
6169670 | Okubo et al. | Jan 2001 | B1 |
6181587 | Kuramoto et al. | Jan 2001 | B1 |
6188203 | Rice et al. | Feb 2001 | B1 |
6215287 | Matsushiro et al. | Apr 2001 | B1 |
6239523 | Janicek et al. | May 2001 | B1 |
6249104 | Janicek | Jun 2001 | B1 |
6281658 | Han et al. | Aug 2001 | B1 |
6282910 | Helt | Sep 2001 | B1 |
6295215 | Faria et al. | Sep 2001 | B1 |
6307759 | Inarida et al. | Oct 2001 | B1 |
6309385 | Simpson | Oct 2001 | B1 |
6313602 | Arefeen et al. | Nov 2001 | B1 |
6366070 | Cooke | Apr 2002 | B1 |
6384579 | Watanabe | May 2002 | B2 |
6433504 | Branecky | Aug 2002 | B1 |
6437997 | Inarida et al. | Aug 2002 | B1 |
6476663 | Gauthier et al. | Nov 2002 | B1 |
6483265 | Hollenbeck et al. | Nov 2002 | B1 |
6498451 | Boules et al. | Dec 2002 | B1 |
6515437 | Zinkler et al. | Feb 2003 | B1 |
6556462 | Steigerwald et al. | Apr 2003 | B1 |
6586904 | McClelland et al. | Jul 2003 | B2 |
6593881 | Vail et al. | Jul 2003 | B2 |
6629776 | Bell et al. | Oct 2003 | B2 |
6693407 | Atmur | Feb 2004 | B2 |
6693409 | Lynch et al. | Feb 2004 | B2 |
6710573 | Kadah | Mar 2004 | B2 |
6717457 | Nanba et al. | Apr 2004 | B2 |
6737833 | Kalman et al. | May 2004 | B2 |
6781802 | Kato et al. | Aug 2004 | B2 |
6801028 | Kernahan et al. | Oct 2004 | B2 |
6806676 | Papiernik et al. | Oct 2004 | B2 |
6810292 | Rappenecker et al. | Oct 2004 | B1 |
6859008 | Seibel | Feb 2005 | B1 |
6885161 | de Nanclares et al. | Apr 2005 | B2 |
6885568 | Kernahan et al. | Apr 2005 | B2 |
6900607 | Kleinau et al. | May 2005 | B2 |
6902117 | Rosen | Jun 2005 | B1 |
6906500 | Kernahan | Jun 2005 | B2 |
6906933 | Taimela | Jun 2005 | B2 |
6909266 | Kernahan et al. | Jun 2005 | B2 |
6930459 | Fritsch et al. | Aug 2005 | B2 |
6949915 | Stanley | Sep 2005 | B2 |
6952089 | Matsuo | Oct 2005 | B2 |
6961015 | Kernahan et al. | Nov 2005 | B2 |
6979967 | Ho | Dec 2005 | B2 |
6979987 | Kernahan et al. | Dec 2005 | B2 |
6984948 | Nakata et al. | Jan 2006 | B2 |
7015679 | Ryba et al. | Mar 2006 | B2 |
7053569 | Takahashi et al. | May 2006 | B2 |
7061195 | Ho et al. | Jun 2006 | B2 |
7068016 | Athari | Jun 2006 | B2 |
7068191 | Kuner et al. | Jun 2006 | B2 |
7071641 | Arai et al. | Jul 2006 | B2 |
7081733 | Han et al. | Jul 2006 | B2 |
7112940 | Shimozono et al. | Sep 2006 | B2 |
7135830 | El-Ibiary | Nov 2006 | B2 |
7148664 | Takahashi et al. | Dec 2006 | B2 |
7149644 | Kobayashi et al. | Dec 2006 | B2 |
7154238 | Kinukawa et al. | Dec 2006 | B2 |
7164590 | Li et al. | Jan 2007 | B2 |
7176644 | Ueda et al. | Feb 2007 | B2 |
7180273 | Bocchiola et al. | Feb 2007 | B2 |
7181923 | Kurita et al. | Feb 2007 | B2 |
7193383 | Sarlioglu et al. | Mar 2007 | B2 |
7202626 | Jadric et al. | Apr 2007 | B2 |
7208891 | Jadric et al. | Apr 2007 | B2 |
7221121 | Skaug et al. | May 2007 | B2 |
7239257 | Alexander et al. | Jul 2007 | B1 |
7256564 | MacKay | Aug 2007 | B2 |
7274241 | Ho et al. | Sep 2007 | B2 |
7309977 | Gray et al. | Dec 2007 | B2 |
7330011 | Ueda et al. | Feb 2008 | B2 |
7336514 | Amarillas et al. | Feb 2008 | B2 |
7339346 | Ta et al. | Mar 2008 | B2 |
7358706 | Lys | Apr 2008 | B2 |
7359224 | Li | Apr 2008 | B2 |
7425806 | Schnetzka et al. | Sep 2008 | B2 |
7459864 | Lys | Dec 2008 | B2 |
7463006 | Ta et al. | Dec 2008 | B2 |
7495404 | Sarlioglu et al. | Feb 2009 | B2 |
7508688 | Virolainen | Mar 2009 | B2 |
7532491 | Lim et al. | May 2009 | B2 |
7573275 | Inagaki et al. | Aug 2009 | B2 |
7592820 | Laakso et al. | Sep 2009 | B2 |
7598698 | Hashimoto et al. | Oct 2009 | B2 |
7612522 | Williams et al. | Nov 2009 | B2 |
7613018 | Lim et al. | Nov 2009 | B2 |
7616466 | Chakrabarti et al. | Nov 2009 | B2 |
7633249 | Sekimoto et al. | Dec 2009 | B2 |
7650760 | Nakata et al. | Jan 2010 | B2 |
7659678 | Maiocchi | Feb 2010 | B2 |
7667986 | Artusi et al. | Feb 2010 | B2 |
7671557 | Maeda et al. | Mar 2010 | B2 |
7675759 | Artusi et al. | Mar 2010 | B2 |
7723964 | Taguchi | May 2010 | B2 |
7750595 | Yamada et al. | Jul 2010 | B2 |
7771115 | Pan | Aug 2010 | B2 |
7847507 | Wagoner | Dec 2010 | B2 |
7880430 | Gale et al. | Feb 2011 | B2 |
7888922 | Melanson | Feb 2011 | B2 |
7903441 | Chen et al. | Mar 2011 | B2 |
7952293 | Kelly | May 2011 | B2 |
7966079 | Graves | Jun 2011 | B2 |
7966081 | Graves | Jun 2011 | B2 |
8032323 | Taylor | Oct 2011 | B2 |
8040703 | Melanson | Oct 2011 | B2 |
8044623 | Takeuchi et al. | Oct 2011 | B2 |
8050063 | Wagoner et al. | Nov 2011 | B2 |
8054033 | Kem et al. | Nov 2011 | B2 |
8065023 | Graves | Nov 2011 | B2 |
8072170 | Hwang et al. | Dec 2011 | B2 |
8092084 | Riddle et al. | Jan 2012 | B2 |
8096139 | Taras et al. | Jan 2012 | B2 |
8120299 | Hwang et al. | Feb 2012 | B2 |
8130522 | Maksimovic | Mar 2012 | B2 |
8154230 | Kimura | Apr 2012 | B2 |
8164292 | Park | Apr 2012 | B2 |
8169180 | Hwang et al. | May 2012 | B2 |
8174853 | Kane et al. | May 2012 | B2 |
8182245 | Maeda et al. | May 2012 | B2 |
8193756 | Jadric et al. | Jun 2012 | B2 |
8223508 | Baarman et al. | Jul 2012 | B2 |
8228700 | Yahata et al. | Jul 2012 | B2 |
8258731 | Shimizu | Sep 2012 | B2 |
8264192 | Green et al. | Sep 2012 | B2 |
8264860 | Green | Sep 2012 | B2 |
8269370 | Haga | Sep 2012 | B2 |
8278778 | Rockenfeller et al. | Oct 2012 | B2 |
8288985 | Takahashi | Oct 2012 | B2 |
8292503 | Pan | Oct 2012 | B2 |
8299653 | Rockenfeller et al. | Oct 2012 | B2 |
8305780 | Saruwatari et al. | Nov 2012 | B2 |
8320145 | Horii | Nov 2012 | B2 |
8321039 | Graves | Nov 2012 | B2 |
8335095 | Mi et al. | Dec 2012 | B2 |
8344638 | Shteynberg et al. | Jan 2013 | B2 |
8345454 | Krolak et al. | Jan 2013 | B1 |
8358098 | Skinner et al. | Jan 2013 | B2 |
8395874 | Yamai et al. | Mar 2013 | B2 |
8400089 | Bonner et al. | Mar 2013 | B2 |
8406021 | Green | Mar 2013 | B2 |
8432108 | Kelly et al. | Apr 2013 | B2 |
8432713 | Popescu et al. | Apr 2013 | B2 |
8467197 | Perisic et al. | Jun 2013 | B2 |
8477514 | Artusi et al. | Jul 2013 | B2 |
8477517 | Joshi | Jul 2013 | B2 |
8487601 | Saint-Pierre | Jul 2013 | B2 |
8493014 | Henderson et al. | Jul 2013 | B2 |
8508165 | Shinomoto et al. | Aug 2013 | B2 |
8508166 | Marcinkiewicz et al. | Aug 2013 | B2 |
8520415 | Krishnamoorthy et al. | Aug 2013 | B1 |
8520420 | Jungreis et al. | Aug 2013 | B2 |
8547024 | Grotkowski et al. | Oct 2013 | B2 |
8547713 | Kono et al. | Oct 2013 | B2 |
8564982 | Song et al. | Oct 2013 | B2 |
8582263 | Butler | Nov 2013 | B2 |
8587962 | Perisic et al. | Nov 2013 | B2 |
8599577 | Kajouke et al. | Dec 2013 | B2 |
8614562 | Bouchez et al. | Dec 2013 | B2 |
8633668 | Marcoccia | Jan 2014 | B2 |
8638074 | Babcock et al. | Jan 2014 | B2 |
8648558 | Clothier et al. | Feb 2014 | B2 |
8657585 | Hong et al. | Feb 2014 | B2 |
8669805 | Serventi et al. | Mar 2014 | B2 |
8693228 | Matan et al. | Apr 2014 | B2 |
8698433 | Green | Apr 2014 | B2 |
8704409 | Owens | Apr 2014 | B2 |
8736207 | Ritter et al. | May 2014 | B2 |
8749222 | Williams | Jun 2014 | B2 |
8751374 | Graves | Jun 2014 | B2 |
8760089 | Smith | Jun 2014 | B2 |
8760096 | Inamura et al. | Jun 2014 | B2 |
8767418 | Jungreis et al. | Jul 2014 | B2 |
8773052 | Clothier et al. | Jul 2014 | B2 |
8796967 | Sato | Aug 2014 | B2 |
8817506 | Shimomugi et al. | Aug 2014 | B2 |
8823292 | Sumi et al. | Sep 2014 | B2 |
8829976 | Kuwabara et al. | Sep 2014 | B2 |
8836253 | Kato et al. | Sep 2014 | B2 |
8847503 | Chang et al. | Sep 2014 | B2 |
8866459 | Zilberberg | Oct 2014 | B2 |
8884560 | Ito | Nov 2014 | B2 |
8896248 | Becerra et al. | Nov 2014 | B2 |
8928262 | Chretien | Jan 2015 | B2 |
8933654 | Chen et al. | Jan 2015 | B2 |
8937821 | Amano et al. | Jan 2015 | B2 |
8941347 | Otorii et al. | Jan 2015 | B2 |
8941365 | Murdock et al. | Jan 2015 | B2 |
8976551 | Igarashi et al. | Mar 2015 | B2 |
9020731 | Yamada | Apr 2015 | B2 |
9030143 | Guzelgunler | May 2015 | B2 |
9065365 | Omata et al. | Jun 2015 | B2 |
9065367 | Greetham | Jun 2015 | B2 |
9070224 | Esfahbod Mirhosseinzadeh Sarabi et al. | Jun 2015 | B1 |
9071186 | Wu et al. | Jun 2015 | B2 |
9088232 | Marcinkiewicz et al. | Jul 2015 | B2 |
9088237 | Sanchez et al. | Jul 2015 | B2 |
9093941 | Lawrence et al. | Jul 2015 | B2 |
9100019 | Akiyama | Aug 2015 | B2 |
9109959 | Nieddu et al. | Aug 2015 | B2 |
9118260 | Gautier et al. | Aug 2015 | B2 |
9124095 | Barron et al. | Sep 2015 | B1 |
9124200 | Dai | Sep 2015 | B2 |
9130493 | Chen et al. | Sep 2015 | B2 |
9134183 | Jeong et al. | Sep 2015 | B2 |
9136757 | Arisawa et al. | Sep 2015 | B2 |
9136790 | Park et al. | Sep 2015 | B2 |
9154061 | Green et al. | Oct 2015 | B2 |
9185768 | Navabi-Shirazi et al. | Nov 2015 | B2 |
9188491 | Pan | Nov 2015 | B2 |
9190926 | Taguchi | Nov 2015 | B2 |
9197132 | Artusi et al. | Nov 2015 | B2 |
9214881 | Sekimoto et al. | Dec 2015 | B2 |
9225258 | Shimomugi et al. | Dec 2015 | B2 |
9225284 | Ried | Dec 2015 | B2 |
9240739 | Fukuta et al. | Jan 2016 | B2 |
9240749 | Green et al. | Jan 2016 | B2 |
9246398 | Sakakibara et al. | Jan 2016 | B2 |
9246418 | Becker et al. | Jan 2016 | B2 |
9247608 | Chitta et al. | Jan 2016 | B2 |
9250299 | Yarlagadda et al. | Feb 2016 | B1 |
9257931 | Tooyama et al. | Feb 2016 | B2 |
9300241 | Becerra et al. | Mar 2016 | B2 |
9312780 | Taguchi | Apr 2016 | B2 |
9322717 | Dhaliwal et al. | Apr 2016 | B1 |
9322867 | Chatroux et al. | Apr 2016 | B2 |
9325517 | Grohman | Apr 2016 | B2 |
9331598 | Jeong et al. | May 2016 | B2 |
9331614 | Becerra et al. | May 2016 | B2 |
9387800 | Tran | Jul 2016 | B2 |
9407093 | Cummings | Aug 2016 | B2 |
9407135 | Kinomura et al. | Aug 2016 | B2 |
9419513 | Mao et al. | Aug 2016 | B2 |
9425610 | Nakashita et al. | Aug 2016 | B2 |
9431915 | Arisawa et al. | Aug 2016 | B2 |
9431923 | Harada et al. | Aug 2016 | B2 |
9438029 | Cameron | Sep 2016 | B2 |
9444331 | Carletti et al. | Sep 2016 | B2 |
9461577 | Ried | Oct 2016 | B2 |
9479070 | van der Merwe | Oct 2016 | B2 |
9502981 | Schaemann et al. | Nov 2016 | B2 |
9504105 | Ekbote et al. | Nov 2016 | B2 |
9547974 | Wang et al. | Jan 2017 | B2 |
9560718 | Sadwick | Jan 2017 | B2 |
9564846 | Marcinkiewicz et al. | Feb 2017 | B2 |
9564848 | Ishizeki et al. | Feb 2017 | B2 |
9565731 | DeJonge | Feb 2017 | B2 |
9577534 | Ishizeki et al. | Feb 2017 | B2 |
9580858 | Maekawa et al. | Feb 2017 | B2 |
9581626 | Schwind | Feb 2017 | B2 |
9595889 | Li et al. | Mar 2017 | B2 |
9618249 | Hatakeyama et al. | Apr 2017 | B2 |
9619978 | Kensy et al. | Apr 2017 | B2 |
9621101 | Kane | Apr 2017 | B2 |
9625190 | Lee et al. | Apr 2017 | B2 |
9634602 | Hou et al. | Apr 2017 | B2 |
9640617 | Das et al. | May 2017 | B2 |
9641063 | Ramabhadran et al. | May 2017 | B2 |
9641115 | Chretien | May 2017 | B2 |
9654048 | West et al. | May 2017 | B2 |
9667169 | Nawa et al. | May 2017 | B2 |
9683904 | Matsumoto et al. | Jun 2017 | B2 |
9692312 | Yuasa et al. | Jun 2017 | B2 |
9692332 | Taoka et al. | Jun 2017 | B2 |
9696693 | Element | Jul 2017 | B2 |
9698768 | Leong et al. | Jul 2017 | B2 |
9712071 | Yuasa et al. | Jul 2017 | B2 |
9715913 | Mn et al. | Jul 2017 | B1 |
9722488 | Ishizeki et al. | Aug 2017 | B2 |
9732991 | An et al. | Aug 2017 | B2 |
9741182 | Zhu | Aug 2017 | B2 |
9742319 | Marvelly et al. | Aug 2017 | B2 |
9742346 | Esnault | Aug 2017 | B2 |
9746812 | Kosaka | Aug 2017 | B2 |
9762119 | Kim et al. | Sep 2017 | B2 |
9772131 | Hatakeyama et al. | Sep 2017 | B2 |
9772381 | Bock et al. | Sep 2017 | B2 |
9780683 | Sakakibara et al. | Oct 2017 | B2 |
9787175 | Phadke | Oct 2017 | B2 |
9787246 | Tsumura et al. | Oct 2017 | B2 |
9791327 | Rhee et al. | Oct 2017 | B2 |
9800138 | Katsumata | Oct 2017 | B2 |
9813000 | Jabusch et al. | Nov 2017 | B2 |
9816743 | Nakase et al. | Nov 2017 | B2 |
9819294 | Park et al. | Nov 2017 | B2 |
9823105 | Lehmkuhl et al. | Nov 2017 | B2 |
9829226 | Hatakeyama et al. | Nov 2017 | B2 |
9829234 | Hatakeyama et al. | Nov 2017 | B2 |
9837952 | Carcia et al. | Dec 2017 | B1 |
9839103 | Avrahamy | Dec 2017 | B2 |
9852559 | Rettig et al. | Dec 2017 | B2 |
9853559 | Taniguchi et al. | Dec 2017 | B2 |
9853588 | Green et al. | Dec 2017 | B2 |
9867263 | Avrahamy | Jan 2018 | B2 |
9870009 | Erwin et al. | Jan 2018 | B2 |
9882466 | Kondo et al. | Jan 2018 | B2 |
9888535 | Chitta et al. | Feb 2018 | B2 |
9888540 | DeJonge | Feb 2018 | B2 |
9893522 | Wallace et al. | Feb 2018 | B2 |
9893603 | Nishizawa et al. | Feb 2018 | B2 |
9893668 | Hart et al. | Feb 2018 | B2 |
9899916 | Okamura et al. | Feb 2018 | B2 |
9929636 | Shinomoto et al. | Mar 2018 | B2 |
9935569 | Tsumura et al. | Apr 2018 | B2 |
9935571 | Frampton et al. | Apr 2018 | B2 |
9941834 | Tsukano et al. | Apr 2018 | B2 |
9954473 | Je et al. | Apr 2018 | B2 |
9954475 | Cho et al. | Apr 2018 | B2 |
9965928 | Green | May 2018 | B2 |
9973129 | Schuster et al. | May 2018 | B2 |
9998049 | Kashima et al. | Jun 2018 | B2 |
10003277 | Taguchi et al. | Jun 2018 | B2 |
10014858 | Flynn et al. | Jul 2018 | B2 |
10656026 | Green | May 2020 | B2 |
10763740 | Green | Sep 2020 | B2 |
10770966 | Marcinkiewicz et al. | Sep 2020 | B2 |
20020085468 | Kobayashi | Jul 2002 | A1 |
20030021127 | Loef et al. | Jan 2003 | A1 |
20030117818 | Ota | Jun 2003 | A1 |
20030218448 | Lidak et al. | Nov 2003 | A1 |
20040136208 | Agarwal et al. | Jul 2004 | A1 |
20040183513 | Vinciarelli | Sep 2004 | A1 |
20050017695 | Stanley | Jan 2005 | A1 |
20050017699 | Stanley | Jan 2005 | A1 |
20050028539 | Singh et al. | Feb 2005 | A1 |
20050068337 | Duarte et al. | Mar 2005 | A1 |
20050076659 | Wallace et al. | Apr 2005 | A1 |
20050109047 | Park et al. | May 2005 | A1 |
20050122082 | Eckardt | Jun 2005 | A1 |
20060022648 | Ben-Yaakov et al. | Feb 2006 | A1 |
20060245219 | Li | Nov 2006 | A1 |
20070012052 | Butler et al. | Jan 2007 | A1 |
20070036212 | Leung et al. | Feb 2007 | A1 |
20070217233 | Lim et al. | Sep 2007 | A1 |
20080000246 | Ha et al. | Jan 2008 | A1 |
20080104983 | Yamai et al. | May 2008 | A1 |
20080115512 | Rizzo | May 2008 | A1 |
20080122418 | Briere et al. | May 2008 | A1 |
20080174255 | Schnetzka | Jul 2008 | A1 |
20080272748 | Melanson | Nov 2008 | A1 |
20080310201 | Maksimovic | Dec 2008 | A1 |
20090085625 | Melanson | Apr 2009 | A1 |
20090178424 | Hwang et al. | Jul 2009 | A1 |
20090251198 | Rudolph | Oct 2009 | A1 |
20090273297 | Kelly | Nov 2009 | A1 |
20100067270 | Odell | Mar 2010 | A1 |
20100117545 | Kelly et al. | May 2010 | A1 |
20100207536 | Burdalski et al. | Aug 2010 | A1 |
20100253295 | Tan et al. | Oct 2010 | A1 |
20100309700 | Maeda et al. | Dec 2010 | A1 |
20110012526 | Kelly | Jan 2011 | A1 |
20110015788 | Celik et al. | Jan 2011 | A1 |
20110018349 | Rockenfeller | Jan 2011 | A1 |
20110018472 | Rockenfeller | Jan 2011 | A1 |
20110030396 | Marcinkiewicz et al. | Feb 2011 | A1 |
20110030398 | Marcinkiewicz et al. | Feb 2011 | A1 |
20110031911 | Marcinkiewicz et al. | Feb 2011 | A1 |
20110031920 | Henderson et al. | Feb 2011 | A1 |
20110031942 | Green | Feb 2011 | A1 |
20110031943 | Green | Feb 2011 | A1 |
20110034176 | Lord et al. | Feb 2011 | A1 |
20110141774 | Kane et al. | Jun 2011 | A1 |
20110164339 | Schmid et al. | Jul 2011 | A1 |
20110170324 | Hsieh et al. | Jul 2011 | A1 |
20110204820 | Tikkanen et al. | Aug 2011 | A1 |
20110205161 | Myers et al. | Aug 2011 | A1 |
20110304279 | Felty | Dec 2011 | A1 |
20120013282 | Introwicz | Jan 2012 | A1 |
20120075310 | Michail et al. | Mar 2012 | A1 |
20120153396 | Sugiura et al. | Jun 2012 | A1 |
20120153916 | Weinstein et al. | Jun 2012 | A1 |
20120179299 | Gyota et al. | Jul 2012 | A1 |
20120191253 | Rockenfeller | Jul 2012 | A1 |
20120280637 | Tikkanen et al. | Nov 2012 | A1 |
20120313646 | Nishikawa | Dec 2012 | A1 |
20130010508 | Courtel | Jan 2013 | A1 |
20130020310 | Hacham | Jan 2013 | A1 |
20130147269 | Zimmermann et al. | Jun 2013 | A1 |
20130170260 | Kitamura et al. | Jul 2013 | A1 |
20130182470 | Chen et al. | Jul 2013 | A1 |
20140001993 | Iwata et al. | Jan 2014 | A1 |
20140015463 | Merkel et al. | Jan 2014 | A1 |
20140042948 | Green et al. | Feb 2014 | A1 |
20140077770 | Omoto et al. | Mar 2014 | A1 |
20140091622 | Lucas et al. | Apr 2014 | A1 |
20140169046 | Chen | Jun 2014 | A1 |
20140197961 | Kensy et al. | Jul 2014 | A1 |
20140241507 | Woywode | Aug 2014 | A1 |
20140285163 | Lin et al. | Sep 2014 | A1 |
20140292212 | Gray et al. | Oct 2014 | A1 |
20150043252 | Kuang | Feb 2015 | A1 |
20150084563 | Lucas et al. | Mar 2015 | A1 |
20150109077 | Tomimbang et al. | Apr 2015 | A1 |
20150191133 | Okamura et al. | Jul 2015 | A1 |
20150192346 | Lee et al. | Jul 2015 | A1 |
20150214833 | Ramabhadran et al. | Jul 2015 | A1 |
20150219503 | Yoshida | Aug 2015 | A1 |
20150229204 | Mao et al. | Aug 2015 | A1 |
20150236581 | Chen et al. | Aug 2015 | A1 |
20150285691 | Caffee et al. | Oct 2015 | A1 |
20150326107 | Hsiao et al. | Nov 2015 | A1 |
20150333633 | Chen et al. | Nov 2015 | A1 |
20150354870 | Lee et al. | Dec 2015 | A1 |
20150365034 | Marcinkiewicz et al. | Dec 2015 | A1 |
20160013740 | Skinner et al. | Jan 2016 | A1 |
20160020716 | Skinner | Jan 2016 | A1 |
20160043632 | Tomioka | Feb 2016 | A1 |
20160043633 | Phadke | Feb 2016 | A1 |
20160094039 | Winstanley et al. | Mar 2016 | A1 |
20160117907 | Wang et al. | Apr 2016 | A1 |
20160133411 | Bock et al. | May 2016 | A1 |
20160211791 | Green et al. | Jul 2016 | A1 |
20160218624 | Ishizeki et al. | Jul 2016 | A1 |
20160248365 | Ishizeki et al. | Aug 2016 | A1 |
20160261217 | Tang | Sep 2016 | A1 |
20160263331 | Nessel et al. | Sep 2016 | A1 |
20160268839 | Mouridsen | Sep 2016 | A1 |
20160268949 | Benn | Sep 2016 | A1 |
20160268951 | Cho et al. | Sep 2016 | A1 |
20160320249 | Reiman et al. | Nov 2016 | A1 |
20160329716 | Inoue | Nov 2016 | A1 |
20170141709 | Fukuda et al. | May 2017 | A1 |
20170141717 | Winstanley et al. | May 2017 | A1 |
20170155347 | Park et al. | Jun 2017 | A1 |
20170190530 | Seki et al. | Jul 2017 | A1 |
20170201201 | Aoki et al. | Jul 2017 | A1 |
20170205103 | Newcomb | Jul 2017 | A1 |
20170214341 | Matthews et al. | Jul 2017 | A1 |
20170244325 | Carralero et al. | Aug 2017 | A1 |
20170264223 | Kitano et al. | Sep 2017 | A1 |
20170287721 | Wood | Oct 2017 | A1 |
20170288561 | Lemberg et al. | Oct 2017 | A1 |
20170299444 | Green | Oct 2017 | A1 |
20170300107 | Green et al. | Oct 2017 | A1 |
20170301192 | Green | Oct 2017 | A1 |
20170302158 | Green | Oct 2017 | A1 |
20170302159 | Green et al. | Oct 2017 | A1 |
20170302160 | Marcinkiewicz et al. | Oct 2017 | A1 |
20170302161 | Green | Oct 2017 | A1 |
20170302162 | Green | Oct 2017 | A1 |
20170302165 | Marcinkiewicz et al. | Oct 2017 | A1 |
20170302200 | Marcinkiewicz | Oct 2017 | A1 |
20170302212 | Marcinkiewicz et al. | Oct 2017 | A1 |
20170302214 | Marcinkiewicz et al. | Oct 2017 | A1 |
20170317623 | Taniguchi et al. | Nov 2017 | A1 |
20170317637 | VanEyll et al. | Nov 2017 | A1 |
20170324362 | Colangelo et al. | Nov 2017 | A1 |
20170328786 | Takechi | Nov 2017 | A1 |
20170373629 | Shin et al. | Dec 2017 | A1 |
20180026544 | Baumann et al. | Jan 2018 | A1 |
20180034403 | Kim et al. | Feb 2018 | A1 |
20180062551 | Moon et al. | Mar 2018 | A1 |
20180073934 | Horng et al. | Mar 2018 | A1 |
20180076748 | Yamasaki et al. | Mar 2018 | A1 |
20180082991 | Toyoda et al. | Mar 2018 | A1 |
20180091075 | Musil | Mar 2018 | A1 |
20180094512 | Sadilek et al. | Apr 2018 | A1 |
20180175752 | Takeoka et al. | Jun 2018 | A1 |
20180180490 | Barbier et al. | Jun 2018 | A1 |
20180191261 | Chung et al. | Jul 2018 | A1 |
20180191288 | Li et al. | Jul 2018 | A1 |
Number | Date | Country |
---|---|---|
1051787 | May 1991 | CN |
101459993 | Jun 2009 | CN |
101763699 | Jun 2010 | CN |
201522062 | Jul 2010 | CN |
102270367 | Dec 2011 | CN |
102364814 | Feb 2012 | CN |
202134068 | Feb 2012 | CN |
102412712 | Apr 2012 | CN |
103001463 | Mar 2013 | CN |
103078475 | May 2013 | CN |
103822334 | May 2014 | CN |
103927832 | Jul 2014 | CN |
203775025 | Aug 2014 | CN |
104620498 | May 2015 | CN |
104764287 | Jul 2015 | CN |
104916088 | Sep 2015 | CN |
105078416 | Nov 2015 | CN |
105207652 | Dec 2015 | CN |
105444340 | Mar 2016 | CN |
0377538 | Jul 1990 | EP |
0744816 | Nov 1996 | EP |
1271067 | Jan 2003 | EP |
1641113 | Mar 2006 | EP |
1689069 | Aug 2006 | EP |
2237402 | Oct 2010 | EP |
2403120 | Jan 2012 | EP |
2983283 | Feb 2016 | EP |
H11237427 | Aug 1999 | JP |
2001289549 | Oct 2001 | JP |
2006134607 | May 2006 | JP |
2010011602 | Jan 2010 | JP |
2010541256 | Dec 2010 | JP |
2011160508 | Aug 2011 | JP |
2011193647 | Sep 2011 | JP |
2015080316 | Apr 2015 | JP |
20040025420 | Mar 2004 | KR |
20110092055 | Aug 2011 | KR |
20130067440 | Jun 2013 | KR |
2007035407 | Mar 2007 | WO |
2010143239 | Dec 2010 | WO |
2011074972 | Jun 2011 | WO |
Entry |
---|
International Search Report regarding International Application No. PCT/US2017/027691, dated Aug. 18, 2017. |
Written Opinion of the International Searching Authority regarding International Application No. PCT/US2017/027691, dated Aug. 18, 2017. |
International Search Report regarding International Application No. PCT/US2017/027744, dated Aug. 18, 2017. |
Written Opinion of the International Searching Authority regarding International Application No. PCT/US2017/027744, dated Aug. 18, 2017. |
International Search Report regarding International Application No. PCT/US2017/027738, dated Aug. 18, 2017. |
Written Opinion of the International Searching Authority regarding International Application No. PCT/US2017/027738, dated Aug. 18, 2017. |
Office Action regarding U.S. Appl. No. 15/419,394, dated Sep. 11, 2017. |
International Search Report regarding International Application No. PCT/US2017/027726, dated Sep. 12, 2017. |
Written Opinion of the International Searching Authority regarding International Application No. PCT/US2017/027726, dated Sep. 12, 2017. |
International Search Report regarding International Application No. PCT/US2017/027729, dated Sep. 13, 2017. |
Written Opinion of the International Searching Authority regarding International Application No. PCT/US2017/027729, dated Sep. 13, 2017. |
International Search Report regarding International Application No. PCT/US2017/027710, dated Sep. 20, 2017. |
Written Opinion of the International Searching Authority regarding International Application No. PCT/US2017/027710, dated Sep. 20, 2017. |
Amit Kumar Sinha et al. “SEPIC Based PFC Converter for PMBLDCM Drive in Air Conditioning System.” International Journal of Advanced Computer Research, vol. 3, No. 1, Issue 8. Mar. 2013. |
International Search Report regarding International Application No. PCT/US2017/027721, dated Sep. 20, 2017. |
Written Opinion of the International Searching Authority regarding International Application No. PCT/US2017/027721, dated Sep. 20, 2017. |
International Search Report regarding International Application No. PCT/US2017/027699, dated Sep. 20, 2017. |
Written Opinion of the International Searching Authority regarding International Application No. PCT/US2017/027699, dated Sep. 20, 2017. |
Applicant-Initiated Interview Summary regarding U.S. Appl. No. 15/419,394, dated Oct. 30, 2017. |
Office Action regarding U.S. Appl. No. 15/419,394, dated Dec. 7, 2017. |
Office Action regarding U.S. Appl. No. 15/419,464 dated Dec. 29, 2017. |
Office Action regarding U.S. Appl. No. 15/419,423 dated Jan. 8, 2018. |
Office Action regarding U.S. Appl. No. 15/487,201 dated Jan. 9, 2018. |
Interview Summary regarding U.S. Appl. No. 15/419,394 dated Jan. 29, 2018. |
Interview Summary regarding U.S. Appl. No. 15/419,423 dated Feb. 21, 2018. |
Notice of Allowance regarding U.S. Appl. No. 15/430,978 dated Feb. 22, 2018. |
Applicant-Initiated Interview Summary regarding U.S. Appl. No. 15/487,201 dated Mar. 5, 2018. |
Advisory Action regarding U.S. Appl. No. 15/419,394 dated Mar. 12, 2018. |
Restriction Requirement regarding U.S. Appl. No. 15/487,226 dated Mar. 12, 2018. |
Restriction Requirement regarding U.S. Appl. No. 15/487,151 dated Apr. 5, 2018. |
Non-Final Office Action regarding U.S. Appl. No. 15/487,101 dated Apr. 9, 2018. |
Final Office Action regarding U.S. Appl. No. 15/487,201 dated Apr. 19, 2018. |
Non-Final Office Action regarding U.S. Appl. No. 15/419,423 dated May 14, 2018. |
Notice of Allowance regarding U.S. Appl. No. 15/419,464 dated May 11, 2018. |
Notice of Allowance regarding U.S. Appl. No. 15/419,394 dated May 11, 2018. |
Applicant-Initiated Interview Summary regarding U.S. Appl. No. 15/487,201 dated May 30, 2018. |
Restriction Requirement regarding U.S. Appl. No. 15/487,175 dated May 16, 2018. |
Non-Final Office Action regarding U.S. Appl. No. 15/487,226 dated May 16, 2018. |
Applicant-Initiated Interview Summary regarding U.S. Appl. No. 15/487,027 dated Jun. 21, 2018. |
Applicant-Initiated Interview Summary regarding U.S. Appl. No. 15/487,101 dated Jun. 21, 2018. |
Notice of Allowance regarding U.S. Appl. No. 15/419,394 dated Jul. 20, 2018. |
Notice of Allowance regarding U.S. Appl. No. 15/487,201 dated Jul. 20, 2018. |
Applicant-Initiated Interview Summary regarding U.S. Appl. No. 15/419,423 dated Aug. 9, 2018. |
Notice of Allowance regarding U.S. Appl. No. 15/419,394 dated Aug. 27, 2018. |
Corrected Notice of Allowability regarding U.S. Appl. No. 15/419,394 dated Sep. 10, 2018. |
Notice of Allowance regarding U.S. Appl. No. 15/419,464 dated Sep. 24, 2018. |
Non-Final Office Action regarding U.S. Appl. No. 15/419,349 dated Oct. 18, 2018. |
Non-Final Office Action regarding U.S. Appl. No. 15/419,423 dated Oct. 11, 2018. |
Notice of Allowance regarding U.S. Appl. No. 15/487,027 dated Oct. 2, 2018. |
Notice of Allowance regarding U.S. Appl. No. 15/487,175 dated Oct. 3, 2018. |
Final Office Action regarding U.S. Appl. No. 15/487,101 dated Nov. 14, 2018. |
Notice of Allowance regarding U.S. Appl. No. 15/487,151 dated Oct. 25, 2018. |
Applicant-Initiated Interview Summary regarding U.S. Appl. No. 15/419,423 dated Dec. 12, 2018. |
Non-Final Office Action regarding U.S. Appl. No. 15/487,175 dated Jan. 10, 2019. |
Applicant-Initiated Interview Summary regarding U.S. Appl. No. 15/487,101 dated Jan. 13, 2019. |
Non-Final Office Action regarding U.S. Appl. No. 15/487,226 dated Jan. 7, 2019. |
Non-Final Office Action regarding U.S. Appl. No. 15/419,423 dated Jan. 29, 2019. |
EPO Communication regarding Rules 161/162 for related PCT Application No. US2017027691 mailed on Nov. 23, 2018. |
Notice of Allowance regarding U.S. Appl. No. 15/943,660 dated Jan. 25, 2019. |
Notice of Allowance regarding U.S. Appl. No. 15/419,464 dated Jan. 25, 2019. |
Notice of Allowance regarding U.S. Appl. No. 15/487,027 dated Jan. 25, 2019. |
Notice of Allowance regarding U.S. Appl. No. 15/419,394 dated Jan. 11, 2019. |
Notice of Allowance regarding U.S. Appl. No. 15/487,151 dated Jan. 9, 2019. |
Notice of Allowance regarding U.S. Appl. No. 15/487,101 dated Feb. 1, 2019. |
Applicant-Initiated Interview Summary regarding U.S. Appl. No. 15/419,423 dated Mar. 28, 2019. |
Non-Final Office Action regarding U.S. Appl. No. 15/419,349 dated Apr. 18, 2019. |
Non-Final Office Action regarding U.S. Appl. No. 15/419,423 dated May 23, 2019. |
Notice of Allowance regarding U.S. Appl. No. 15/943,660 dated May 22, 2019. |
Final Office Action regarding U.S. Appl. No. 15/487,226 dated Jul. 9, 2019. |
Final Office Action regarding U.S. Appl. No. 15/487,175 dated Jul. 29, 2019. |
Applicant-Initiated Interview Summary regarding U.S. Appl. No. 15/419,423 dated Aug. 1, 2019. |
Final Office Action regarding U.S. Appl. No. 15/419,423 dated Aug. 30, 2019. |
Non-Final Office Action regarding U.S. Appl. No. 15/419,349 dated Oct. 4, 2019. |
Non-Final Office Action regarding U.S. Appl. No. 16/43,548 dated Sep. 30, 2019. |
Advisory Action regarding U.S. Appl. No. 15/487,175 dated Oct. 24, 2019. |
Advisory Action regarding U.S. Appl. No. 15/419,423 dated Nov. 21, 2019. |
Applicant-Initiated Interview Summary regarding U.S. Appl. No. 16/433,548 dated Dec. 11, 2019. |
Supplementary Search Report for EP 17783287 dated Nov. 22, 2019; 8 pages. |
Notice of Allowance regarding U.S. Appl. No. 15/419,349 dated Jan. 10, 2020. |
First Office Action for Chinese Application No. CN201780029917.6 issued Jan. 20, 2020. Translation provided. |
European Search Report on Euripean Patent Application No. EP 17 78 3275 dated Nov. 13, 2019. |
Choi Bo H et al: “A Novel Single-SiC-Switch-Based ZVZCS Tapped Boost Converter”, IEEE Transactions on Power Electronics, Institute of Electrical and Electronics Engineers, USA, vol. 29, No. 10, Oct. 1, 2014 (Oct. 1, 2014), pp. 5181-5194, XP011549983, ISSN: 0885-8993, DOI: 10.1109/TPEL.2013.2293813 [retrieved on Jun. 2, 2014]. |
Final Office Action regarding U.S. Appl. No. 16/433,548 dated Mar. 30, 2020. |
Notice of Allowance regarding U.S. Appl. No. 15/419,423 dated Apr. 15, 2020. |
First Office Action for Chinese Application No. CN201780035647.X issued Mar. 26, 2020. Translation provided. |
Notice of Allowance regarding U.S. Appl. No. 15/487,175 dated Apr. 17, 2020. |
Notice of Allowance regarding U.S. Appl. No. 15/419,423 dated Apr. 27, 2020. |
Supplemental Notice of Allowance regarding U.S. Appl. No. 15/419,423 dated Jun. 26, 2020. |
Supplemental Notice of Allowability regarding U.S. Appl. No. 15/419,423 dated Aug. 6, 2020. |
Notice of Allowance regarding U.S. Appl. No. 16/595,277 dated Oct. 20, 2020. |
European Office Action regarding Application No. 17783267.2 dated Oct. 28, 2020. |
Second Chinese Office Action regarding Application No. 201780030180.X dated Aug. 12, 2020. English translation provided by Unitalen Attorneys at Law. |
Second Chinese Office Action regarding Application No. 201780032245.4 dated Dec. 3, 2020. English translation provided by Unitalen Attorneys at Law. |
Second Chinese Office Action regarding Application No. 201780030179.7 dated Dec. 2, 2020. English translation provided by Unitalen Attorneys at Law. |
Chinese Office Action regarding Application No. 201780035647.X dated Dec. 2, 2020. English translation provided by Unitalen Attorneys at Law. |
First Chinese Office Action regarding Application No. 201780030215.X dated Jan. 6, 2021. English translation provided by Unitalen Attorneys at Law. |
Notice of Allowance regarding U.S. Appl. No. 15/487,226 dated Oct. 26,. 2021. |
Notice of Allowance regarding U.S. Appl. No. 15/487,226 dated Mar. 14, 2022. |
Number | Date | Country | |
---|---|---|---|
20220320997 A1 | Oct 2022 | US |
Number | Date | Country | |
---|---|---|---|
62398641 | Sep 2016 | US | |
62398658 | Sep 2016 | US | |
62323607 | Apr 2016 | US | |
62323505 | Apr 2016 | US | |
62323498 | Apr 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15487226 | Apr 2017 | US |
Child | 17849564 | US |