Recent content by rcvkumar2000

I think, I just found the solution. The problem was that I used mechanical speed in place of electrical speed, in predictingng currents for the controller. Which, resulted in errors in current tracking and further in the torque generated. Now, everything seems good. Thank you, guys.

Yeah, it's a great material. Referring it this current moment.... Haven't got anything specific yet, but I'm sure I can find some solution. Will let you know for sure, if something turns up... Yes, I'm very interested in EVs and want to become a good engineer. The thing is I have to experience...

Yes, if you plot alpha vs beta. With some ripples. I'm getting that right....

Just PI. And BTW, a wonderful reference book✋....

This is what I have been mentioning. Yellow is reference and blue is Actual. And this is speed tracking:

Sorry for the late reply. I didn't find any solution to that.

Sorry for the late reply, I ain't able to find the solution.

Predictive Control for Drives and Power Converters - J.Rodriguez and Patricio Cortes

Yes, I'm confident about that. It's just difference between predicted and reference current. I'll have a variable and store the least calculated error. If any further states give lesser error, then that will be the new optimum. i_kp is used instead of Isp1. That's it. Check the latest images I...

But the requirement is for two-level. I'm afraid I cannot change that.

Yeah, instead of FOC I've used CSCC. And instead of SVM it's MPCC For current tracking, a weighting factor is not necessary as it's the only constraint I'm keeping on the system. The flux constraint is taken care of by the CSCC.

What I have implemented is not exactly from that reference..... It's a bit different.

It's the PI controller. To track speed.

I do have anti-windup. Limited the Torque reference between 0 and 30 Nm