Debugging method of frequency converter

Abstract

The invention provides a debugging method of a frequency converter. The debugging method comprises the steps of controlling a break to be in the forbidden state, controlling an IGBT in a circuit to be in the off state, controlling the break to be adjusted into the enabled state from the forbidden state, detecting whether the break in the enabled state meets the enabled condition, and executing the break when the break meets the enabled condition.

Description

technical field [0001] The invention relates to an air conditioner control technology, in particular to a debugging method for a frequency converter. Background technique [0002] In the traditional debugging process, by setting breakpoints in the program, the Micro Control Unit (MCU) can stop at the interrupt point, and then observe various variables, such as observing the value of logic variables, single-step running, and viewing the program. direction, etc., and even use an oscilloscope to observe the level status of the input / output port, so that it is very convenient to observe the waveform of the circuit input / output signal. [0003] However, if the above-mentioned debugging method is adopted, the following problems exist: during the debugging process of the frequency converter, since the hardware circuit of the frequency converter includes an insulated gate bipolar transistor (Insulated Gate Bipolar Transisitor, IGBT), it usually includes six upper and lower complemen...

AI Technical Summary

Problems solved by technology

[0003] However, if the above-mentioned debugging method is adopted, the following problems exist: during the debugging process of the frequency converter, since the hardware circuit of the frequency converter includes an insulated gate bipolar transistor (Insulated Gate Bipolar Transisitor, IGBT), it usually includes six upper and lower complementary IGBT

First of all, whether it is any IGBT in the upper bridge arm or any IGBT in the lower bridge arm, the conduction time is strictly limited. Therefore, it is not possible to simply stop the MCU during the running of the program. Debugging, otherwise, it will cause the IGBT to burn out

In addition, the upper and lower complementary IGBTs cannot be turned on at the same time, and a dead zone needs to be inserted in real time, which also requires strict control. Similarly, if the MCU is simply stopped for debugging during the running of the program, the upper and lower bridges will be caused. The arm is short-circuited, thereby burning out the IGBT in the upper and lower arms

Images