Académique Documents
Professionnel Documents
Culture Documents
1 cos
PowerFactor = cos --------------------------------------------------------------------
2
- = ----------------------------
1 + I2 I1 + I3 I1 +
2 2
1 + THD
Displacement
Factor Distortion Factor
2
THD = I 2 I1 2 + I3 I 1 +
where:
cos Displacement factor of the voltage and current
THD = Total Harmonic Distortion
I1 = Current drawn from the supply at fundamental frequency
I2 = Current drawn from the supply at double the fundamental frequency and so on
PFC
AC Rectifier Converter DC Output
Supply Load
(Stage I)
PFC
Converter
(Stage II)
- 0 t
V2 > V1
Buck-Boost Converter
V1 V2 < V1
S
D
+
i
C -
V1 L V2 i
+
- 0 t
IL1 ID1
ILoad
PWM1H IM1
IC
Rectifier
C
Load
IL2 ID2 PFC
Output
PWM1L IM2
dsPIC® DSC
PWM1H
t
PWM1L
IL1
t
IL2
t
ID1
t
ID2
t
IC = (ID1 + ID2) - 1
t
(VAC - VDC ) / L
VAC / L
Average Inductor
Current is controlled
IL IL
T
tON tOFF
IL2
ID
L2
D2
Load
C
S2 S1
CT CT
k1 k2 k3 k4 k5
dsPIC® DSC
VAC
VDC PI Controller IAC PI Controller
VDCRef - -
* + VL D
VERR ICAPREF IACREF IERR
+
Postscaler
VAC
- D
D+ D2
+ D
I
IRef = 0 - ERR D
+
PI Controller
Postsclaer
IM1 -
ADC
Interrupt
Service
Routine
Wait for
ADC Next Iteration Soft Start
Interrupt Function
Update VDC
PWM Trigger Duty Cycle
to ADC of Two Boost
Converters
Voltage
Compensator
Enable
Interrupts
Load
Balance
Compensator
Average
IM2 IM1 Voltage and
Voltage
Current Decoupling
Initialize
Compensator Compensator
Constants
for PI
Controllers
IAC
Initialize
ADC and
PWM
Reset
DC
AC Input AC Boost
EMI Filter Output
Power Rectifier Converter Power
Auxiliary Signal
Power Adaptation
Supply
C1
MOV1
L1
L C3 C4
N R1
G
C2
L2
D1
L3
D2
GATE 1 Q1
C6
GATE 2 Q3
12V
R25 R24
GATE1
12V
R26 3
0
1 2
R22 a1 Vcc1 a1
3 4
PWM1H Q6 a2 GND a2
0 GATE2
MCP1403
PWM1L Q5
R23
EQUATION 31:
1
f –3db = -------------------------------------
2 R 41 C 17
40 –3
--------- V ADC_peak = 32 7.76 10e = 2.5V
350 2 100
I Load_max = ---------------------- 1 + ---------
85 0.9 2
I Load_max = 7.76A
R43 R38
-
C18 C17
+
MCP6022
R44 R39
R42
D4
R13 Analog Channel
CT
R12 C10
RT = R14
TX2
IQ1 C9
3
EQUATION 37: V ADC_peak = ------------------ 373.65 = 2.78V
3 + 400
R 37 where:
k = -----------------------
R35 + R 37 Vin_peak = Peak input voltage
VADC_peak = Maximum voltage on ADC pin
V ADC_peak = k V in_max VADC_peak = Peak voltage on ADC pin
3.3V
VACL D10
D12
VACH D11
Analog Channel
R35
R37 C15
12
5
10
4
9
11
1
3
6
7
1. Connect the load to the DC BUS (+) and DC Note: The programming connectors used for
BUS (-) output terminals. connecting the MPLAB programmers/
debuggers are not isolated. The user
2. Make sure that the power cord is disconnected
should use an isolation method, such as
from the AC mains before connecting it to the
an isolated USB HUB.
IPFC reference design AC input connector.
3. Connect the power cord to the Interleaved AC SETTING UP AN APPLICATION FOR DEBUG
inlet.
Complete the following steps to prepare the application
4. Connect the power cord to the mains.
for debug:
Power-up Sequence 1. Launch MPLAB IDE, and then open the applica-
tion project. The related workspace will be open.
To power-up the IPFC system, complete the following
For information on projects and workspaces,
steps:
see the MPLAB IDE documentation mentioned
1. Connect the power cable to the AC mains. at the beginning of this section.
2. Turn-on the incoming AC supply by sliding the 2. Select Project>Build All to build the application
switch SW1 to the ON position. code. The build’s progress will be visible in the
3. Check the status of the D13 and D33 LEDs. The Build tab of the Output window.
unit is powered when these LEDs are ON. 3. Select Debugger>Select Tool>”Your Preferred
Tool”. MPLAB IDE will change to add your tool
Power-down Sequence debug features.
To disconnect the power supply to the IPFC system, 4. Select Debugger>Program to program the
complete the following steps: application code into the dsPIC33F DSC device.
1. Turn off the incoming AC supply by sliding the The debug programming progress will be visible
switch SW1 to the OFF position. in the Debugging tool tab of the Output
window.
2. Wait until the red DC bus LED indicator (D13)
turns OFF. This can take a maximum of 5
PROGRAMMING AN APPLICATION
minutes.
3. Disconnect the power cord from mains. When the program is successfully debugged and
running, the next step is to program the device for
PROGRAMMING/DEBUGGING AN standalone operation in the finished design. When
APPLICATION CODE doing this, the resources reserved for debug are
released for use by the application. To program the
The MPLAB® ICD 2, MPLAB IDC 3, PICkit™ 3 and application, use the following steps:
MPLAB REAL ICE™ in-circuit emulator may be used
along with MPLAB IDE to debug your software. MPLAB 1. Disable your tool as a debug tool by selecting
IDE is the free integrated development environment Debugger>Select Tool>None.
available from Microchip’s web site. MPLAB IDE allows 2. Select your tool as the programmer by selecting
these two devices, which are supported on the IPFC Programmer>Select Programmer menu.
Reference Design, to be used as an in-circuit debugger 3. Select Programmer>Program.
as well as a programmer: Now the application code will run independently.
• dsPIC33FJ06GS202
• dsPIC33FJ16GS504
In-circuit debugging allows you to run, examine, and
modify your program for the device embedded in the
IPFC system hardware. This greatly assists you in
debugging your firmware and hardware together.
AN6/OSC1
AN7/OSC0
12V/0.4A
DEBUGGER INTERFACE
AUXILIARY SUPPLY
LOWREF
• Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the
intended manner and under normal conditions.
• There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our
knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data
Sheets. Most likely, the person doing so is engaged in theft of intellectual property.
• Microchip is willing to work with the customer who is concerned about the integrity of their code.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not
mean that we are guaranteeing the product as “unbreakable.”
Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our
products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts
allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.
03/26/09