TIDUFB1 December 2024
guiVbus
(VIENNA_guiVbus_Volts
in the Expression window) variable is updating. If there is no change in the value, then make sure the real-time mode is enabled, and the hardware is set up correctly. Do not proceed further unless the update is verified. guiVbus
, guiVbusPM
, and guiVbusMN
display the correct values. For the 80VRMS L-N, guiVbus
is close to 190V, the graph function can show the waveform, as shown in Figure 3-10. The guiVbusPM
and guiVbusMN
variables are both close to 85V. The code runs a sine analyzer module, which computes the RMS value of the voltage and current. Figure 3-11 shows that the guiVrms1
, guiVrms2
and guiVrms3
values are close to the input value, that is, 80VRMS. This verifies the voltage sensing of the board.guiVrms1
, guiVrms2
, and guiVrms3
variables, for the given test condition these values are close to 0.5A. Additionally, the graphs must be seen to verify the current measurement. Figure 3-12 shows the currents on a graph. dutyPU_DC
variable to 0.5 in the expressions view.clearTrip
.guiVbus
is about 190V; with switching, the guiVbus
rises up to 380V. Thus, guiVbusPM
and guiVbusMN
are both higher than the input voltage maximum.guiVbus
variable rises to about 380V and guiVbusPM
and guiVbusMN
are close to 190V each, and the current is close to 1.1ARMS when the input voltage reaches 80VRMS L-N. The Expressions view appears as shown in step Figure 3-14. Make sure all the variables are accurate, that is, guiVrms1
, guiVrms2
, guiVrms3
, guiIrms1
, guiIrms2
, guiIrms3
, guiPF1
, guiPF2
, and guiPF3
. If any variable is not accurate (as shown in Figure 3-14), this means there is a hardware issue with the sensing circuit. controlISR
and tenkHzISR()
variables