Part Number: TMS320F28069
Other Parts Discussed in Thread: CONTROLSUITE
Are there any suggestions on the best way to implement dead band compensation on the 28069 platform?
Thanks in advance!
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: TMS320F28069
Other Parts Discussed in Thread: CONTROLSUITE
Are there any suggestions on the best way to implement dead band compensation on the 28069 platform?
Thanks in advance!
Sandy12108,
The previous post was about a system example that was using the Dead Band (DB).
If you simply want to setup and use the DB sub module you should look at the "epwm_deadband" example, which can be found in controlSUITE at "C:\ti\controlSUITE\device_support\f2806x\v151\F2806x_examples_ccsv5\epwm_deadband".
The DB is between the 'A' and 'B' channels of the same PWM. The DB sub module will not help you get a DB between ePWM1A and ePWM2B.
Regards,
Cody
Cody,
I am already using dead band. What I am looking for is db compensation, where depending on output current polarity, a compensation duty cycle is added or subtracted in a feed forward manner to improve performance by compensating for distortions introduced by the dead band.
Is that the intent in this module where the deadband in moved up and down between 0 and the maximum value?
"Each ePWM is configured to interrupt on the 3rd zero event
when this happens the deadband is modified such that
0 <= DB <= DB_MAX. That is, the deadband will move up and
down between 0 and the maximum value."
Thanks,
Sandy
Sandy,
This sub module is very simple, it places a dead band between the A and B channels by simply adding or subtracting a Rising Edge Delay or a Falling Edge Delay from one of the channels. If you would like to keep the DB from distorting the signal's high or low time then you will need to modify(compensate) the compare values by the length of the DB.
In short, yes that is a reasonable use case but it is not automatically done by the DB sub module, it will require some software intervention.
Regards,
Cody