bdj said:
Zombiess I read posts you suggested. Concerning the dead time explanation with counting for propagation times and delays through the nodes and connections, this is math approach concerning data from datasheets, but for first steps will it be also valid by looking at scope Vgs from hi and low fets at same time and determine “good” deadtime?
Not unless you are able to simulate all operating conditions. Stick to the math approach, it's easy and safe. I learned from Highhopes, he did this kind of work in the aerospace realm and that's what he taught to me, so I stick to it. The design approach I was taught by him is pretty much setup to work every time. I only deviate from it when I have good reason and a solid understanding of what I'm doing that I can justify. A dead time of 1us will support 50kHz and still be 5% of the period. If you want to succeed in designing a motor drive which is functional and doesn't suffer random failures, you need to be conservative.
If I understood good from some other posts here fet can be considered off( with some low current) as soon as Vgs falls under its treshold value ? And also fet can be considered on(with some low current) as soon as Vgs reaches treshold value? So regarding this scenario can deadtime be modified so we would have some small part of “overlapping” form Vgs of both high and low fet? And current through both fets would be small.
Yes it's possible to have a small overlap. There is a technique where a small amount of shoot through is purposely induced in order to reduce overshoot. Bad idea unless you REALLY know what you are getting into and have developed a specialized controller for this purpose.
Can you explain me what is meant by high low frequency distortion if dead time is more than 5% of switching period? Does it mean that phase currents would have a lot of harmonics and ripple in compare to true sine wave because we don’t have controll over it for a amount of dead time?
Excessive dead time will cause an introduction of low frequency harmonics which will increase THD. Increased THD = additional motor heating and reduced torque. In aerospace they have rules about production of LF harmonics. These harmonics start to become excessive > 5% dead time, I've played around with this in simulation and measured THD. Can you exceed 5% in your application without issue, sure, but you'll need to switch > 50kHz with 1us dead time. Even my slow TD350E gate driver runs at 800ns so it's capable of > 50kHz. Most motors do not require such a high switching frequency. The required switching freq is dependent on motor inductance. The motor inductance and switching freq also dictate the amount of DC link cap required to handle the ripple current.
Concerinig transconductance work of mosfet that is reffering to linear mode? Short pulses can place fet in this mode. Concerning bootstrap gate drivers they also requre minimum pulse width to be able to properly charge bootstrap cap. So depending on charge current and cap size bootstrap gate driver can put higher demand for minimum pulse width. I read also in some post that minimum pulse width can be issue for low speed operation. Why this could be issue? Wouldn’t speed loop controller be able to “fight” against this scenario with its positive and negative output and also handle low speed operation something like hysteresis controll ?
Yes, short pulses can cause a partial turn on. That is why the motor controllers have a minimum pulse width setting.
Low speed operation could also depend on the load. A motor running at low speed and no/low load will only require short pulse widths due to the low current demand.
There are different types of controller configs. Some are PI, some PID, speed control, current control, speed-current control which is usually 2 cascaded PI controllers with a inner PI control loop managing current running about 10x faster than an slower outer loop voltage controller whose output is fed into the inner PI controllers set point. A lot of this stuff won't make sense unless you start simulating it and playing around, or you happen to be a control systems engineer.