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.

TMS320F28035: Is all I need for encoderless FOC this board and two DRV830x drivers?

Part Number: TMS320F28035
Other Parts Discussed in Thread: LAUNCHXL-F280049C, C2000WARE

Tool/software:

Hello,

I'm designing an encoderless FOC system for a motor model that I have in my company, and my research has led me to learn the C2000 microcontroller series a bit, I need to control a big BLDC motor but only have parameters for it through a traditional Allen Bradley Powerflex 525. I would like to know more about encoderless FOC and make an informed decision about what I need to do to properly implement FOC for my application.

So far I understand the DRV830x was used in tandem with the TMS320F28035 to accomplish encoderless FOC according to this but I'd like to know if there's a better way or a TI chip that already handles the clark/park transformations and other details regarding encoderless FOC that I can interface with my LaunchXL - F280049C

  • If you're using the LAUNCHXL-F280049C, you do not also need a F28035 chip- both are C2000 MCUs. The C2000Ware Motor Control SDK has plenty of examples of using the F280049C for sensorless control. These examples utilize the MCSDK's built-in libraries, including clark/park transforms, etc.

    Regards,
    Jason Osborn

  • Thanks, I'll look into this further!

  • Is Insta-Spin FOC able to be used to generate for me the code that I can edit for lower level control? I need to control the motor programmatically, and I would think that if I'm just using Instaspin FOC I couldn't change code or build a program to edit how the motor operates mid operation if it's just through GUI interaction.

  • InstaSPIN-FOC is not a GUI, it's a set of static libraries which are utilized by many example projects, some of which also have a GUI. If using any of the projects which are not packaged with a GUI, there's no issue whatsoever in altering the code provided in the MCSDK- and many of the projects with a GUI have built-in predefined symbols which can be used to disable it, ensuring that it does not interfere in your code editing.

    If you want to continue to use whichever GUI you're using, you will just need to ensure you avoid interfering with the GUI's functionality in the code as you edit it.

    Regards,
    Jason Osborn

  • I've been working through some of the lab exercises in the motor control SDK that TI provides on dev.ti, thank you for the help!