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.

TMS320F280049C: Evaluation and Demonstration System Items needed for Motor Control

Part Number: TMS320F280049C
Other Parts Discussed in Thread: DRV8301, BOOSTXL-DRV8320RS, TMDSADAP180TO100, TMDSHVMTRINSPIN, MOTORWARE, LAUNCHXL-F280049C, BOOSTXL-DRV8301

We would like to evaluate / demonstrate motor control using the TMS320F280049C and InstaSPIN-FOC.

1 – What items do we need to achieve this in the quickest and easiest way?

2 – Which is recommended the “F280049C Launchpad” or the “F280049C with F280049C Docking Station”?

3 – We have a DRV8301 motor kit board.  Is this compatible with the F280049C control card?  If not, which motor drive kit is recommended for F280049C?

4 – Is Code Composer Version 7.3.0 sufficient for motor control with F280049C?  Or do we need a later version?

5 – Does MotorControl SDK work with Code Composer or is it used in place of Code Composer?

6 – Which GUI do we need? “SDK InstaSPIN Universal GUI” or “InstaSPIN Universal GUI” or “InstaSPIN-FOC & -Motion GUI”?

7 – Do you have any other tools, kits, or recommendations?

  • 1 - The MotorControl SDK is going to be the best resource for the F280049C--www.ti.com/.../c2000ware-motorcontrol-sdk

    2 and 3 - Currently the kits that the InstaSPIN solution supports are LaunchPad+BOOSTXL-DRV8320RS or controlCARD+TMDSADAP180TO100+TMDSHVMTRINSPIN. DRV8301 works with the F28004x controlCARD, but it won't be as out-of-the-box as the other options. If you want to use the DRV8301 kit, you will need to get the TMDSADAP180TO100 to make the controlCARD fit in its dock and you'll also need to make some modifications to the HAL code to deal with the differences in hardware.

    4 - We say in the SDK documentation that a minimum CCS version of 7.4.0 is needed. I don't know any reason why 7.3.0 wouldn't work, but we didn't test with it. If you aren't completely committed to CCSv7 though, my recommendation is to just go to CCSv9.

    5 - The SDK works with CCS. The examples in the SDK are all CCS projects, so you'll need both.

    6 - You'll want the new SDK version that's available in the dev.ti.com Gallery. The others are intended for use with MotorWare and devices older than the F28004x.

    7 - Nothing else is coming to mind at the moment. :)

    Whitney

  • Thank you for the reply. A few follow-up questions…

    8 - With the “LAUNCHXL-F280049C+BOOSTXL-DRV8320RS” approach, would we also need a MOSFETs board with three half h-bridges? What board would we use for the FETs?

    9 - The BOOSTXL-DRV8301 looks like it has both the gate drivers and the FETs and can directly drive a BLDC motor. Please confirm.

    10 – You did not list the combination of “LAUNCHXL-F280049C + BOOSTXL-DRV8301”, but they appear to be directly stackable. You mentioned we would need to make modifications to the HAL code to deal with the differences in hardware (between BOOSTXL-DRV8320RS and BOOSTXL-DRV8301). We are leaning towards this combination, depending on how extensive the HAL modifications are. Could you provide more specific instructions on the modifications that would need to be made?
  • 8 and 9 - It's my understanding that they both can be used directly. If you go to the product pages for the boards, you should be able to find download links for zips that can give you the schematics to make sure they have what you need for your motor. My expertise is on the F28004x side of things, but there's a motor drivers forum if you need more details on those: e2e.ti.com/.../38

    10 - As far as I know they'll be compatible, but I don't know of anyone on our team who has actually tried it. The DRV8320RS board was specifically designed with the F28004x PGAs in mind, so that's the one that we strongly recommend. I'm not familiar enough with the DRV8301 board to know how extensive the changes will be--off the top of my head, the registers on the DRV8320RS and the DRV8301 are different, so that interface will need to change if you need to be able to read/write from them, and as I already mentioned, the configuration of the PGAs.

    Whitney