I am trying to implement a closed-loop control strategy for a DC-DC (boost) converter. I designed the controller per well-known guidelines and successfully implemented it in MATLAB Simulink. The simulation results are absolutely fine. However, when the same controller is being implemented on a platform like dSPACE to trigger a real converter, the control signal i.e, the duty cycle upper saturation limit is reached.
Why does this happen for a controller which was well behaving in the simulation?
What are the potential reasons for this problem?
What should be done to rectify this problem?
Please help me out with some specific suggestions in this regard.
Hello Malyala Venkata Satya Sai Chandra ,
You say you simulated the controller on MATLAB Simulink. Did you also simulate the DC-to-DC converter on MATLAB Simulink? I am having a hard time understanding how you know the controller was working perfectly. I mean, if the closed loop control was done all as a simulation (both the controller and the converter were simulated), how do you know that your simulation of the DC-to-DC converter behaves like the real converter? What do you mean by the statement, "the same controller is being implemented on a platform like dSPACE to trigger a real converter"?
Regards,
Tom Cuff
For the implementation of a controller for DC-DC converters with a hardware platform such as dSPACE, TMS microcontroller, STM32 microcontroller, or Arduino you should first identify the operation region of the load as well as the input voltage range until reaches the suitable signal i.e, the updating of the duty cycle without saturation during the controller working.
- Badges
- Science topic