TMS320F28027F: Flying Start with simpified structure in proj_lab11a

It is possible to implement the flying start function without the controller, but you will need to replace some of the CTRL function calls in the API. There is currently no example code for this, but it shouldn't be too hard to change the code accordingly.

For example, in motor_RunCtrl(), you'll need to replace

CTRL_setId_ref_pu(handle, _IQ(0.0));
CTRL_setIq_ref_pu(handle, _IQ(0.0));
CTRL_setSpd_out_pu(handle, _IQ(0.0));

With the PI_setRefValue() API for each of the PID module instances. Lab11a has three PID module instances for speed, Iq and Id. You'll need to edit the FS_run() API as well to remove the CTRL object API and replace with the "generic" module API instead

Sean

Thanks, Sean. I guess "shouldn't be too hard" is relative :-)

I am proficient enough to have written several features into Motorware, like SCI support, ECAP, motor beep, seamless transition between speed and torque control, and others. But every time I try to port over Flying start, I fail. So from my perspective it is relatively hard.

Since proj_lab11a is the "go-to" code structure for starting our own applications (according to the lab user guide), it would be so helpful if some of these more critical features were provided with that structure. Flying start, hall sensor support, a proper RsOnline implementation, to name a few.

Thanks,
-asifjahmed

Asif,

I understand the difficulty in porting some of the individual examples from the various labs into a larger framework, I did not mean to minimize the effort needed there. My apologies. Moving forward, we will work to have a more inclusive example of the InstaSPIN features in a non-CTRL based example. We are investigating an incremental build project to perform this function in the coming SDK release.

Sean

Thanks, Sean. I appreciate the sentiment!

I am very excited to hear more about this incremental build. Seems like it could be what gets me to production! Where can I look to hear more about this?

Best,
-asifjahmed

I cannot give a solid release date for the next release. It will follow the new C2000Ware SDK format and will target a new device; as a result, it will not help in this case as the new source will not be applicable to F2802x devices (or F2805x or F2806x devices for that matter).

Sean