How To Evaluate and Develop with InstaSPIN-FOC and InstaSPIN-MOTION

Here is our recommendation for developing with InstaSPIN

Assuming you have already used the InstaSPIN website, the InstaSPIN simulation, and read through the Technical Reference Manuals (links on website)

to convince yourself that InstaSPIN-FOC and/or -MOTION are the right solution for you...

  1. Purchase an evalution kit
      1. includes TMDSCNCD28069MISO and TMDSCNCD28027F controlCARDs
    2. DRV8301-69M-KIT
      1. includes TMDSCNCD28069MISO
      2. you can purchase separately TMDSCNCD28027F which also requires the use of an external emulator (your choice: XDS100V2, XDS510, isolation recommended)
    3. DRV8312-69M-KIT
      1. includes TMDSCNCD28069MISO
      2. you can purchase separately TMDSCNCD28027F which also requires the use of an external emulator (your choice: XDS100V2, XDS510, isolation recommended)
    4. LAUNCHXL-F28027F + BOOSTXL-DRV8301
      1. Isolated XDS100v2 LaunchPad with InstaSPIN-FOC enabled TMS320F28027F
      2. BoosterPack for 6-24V, 10A continuous three phase motors
    5. LAUNCHXL-F28069M + BOOSTXL-DRV8301
      1. Isolated XDS100v2 LaunchPad with InstaSPIN-FOC and -MOTION enabled TMS320F28069M
      2. BoosterPack for 6-24V, 10A continuous three phase motors
  2. Install latest version of 
  3. Run MotorWare.ex from the install location, ex: C:\ti\motorware\MotorWare_1_01_00_11\MotorWare.exe
  • Each kit which includes a 69M devices has a CD with "kit contents". The latest version of these kit contents is always here. The 27F and Launchpad based kits have Universal GUI support with latest version always here.
  • Download and unzip this file and note the contents:
  • Read and follow "readmefirst_instaspin_motor_kits.pdf"
    • This document is also included in MotorWare.exe, linked with every piece of hardware.
    • Also note the location of the QSG Hardware document for each piece of hardware, these should be reviewed as you set-up the kits
  1. The hardware design files are kept in controlSUITE (C2000 MCU main product support) to keep the MotorWare installation smaller. Install controlSUITE if you want to access these files.

GUI Evaluation

  1. Follow the "qsg_gui_instaspin_foc.pdf" or "_motion.pdf" or "qsg_gui_universal.pdf"
    1. This includes running the GUI Composer installer which installs the standalone run-time
  2. If needed, view the GUI training videos
  1. InstaSPIN-FOC GUI Overview
  2. InstaSPIN-MOTION GUI Overview
  3. InstaSPIN-FOC LaunchPad and BoosterPack (Universal GUI) Series 

Evaluate the MotorWare projects and start learning about the software architecture, code structure, and API interface

  1. install the latest version of CCStudio from the included DVD or from the wiki site.
  2. Ensure that you are using compiler 6.2.3 or newer. There is a MAJOR BUG in compilers 6.2.0-6.2.2 DO NOT USE
  3. Follow the Projects & Lab User's Guide in MotorWare.exe
  4. CCS notes
  • Be sure that when you import the projects you do NOT select "Copy projects into workspace" option. We recommend working out of the MotorWare installation directory. This will make it much simpler to keep up with future revisions.
  • Do NOT change any of the project settings. Ex: you do NOT need to change the General --> Variant option to a specific device. This just selects a pre-installed .cmd file that will NOT work with the MotorWare projects.  The .cmd files included in MotorWare are already attached to the projects.
  • The general path for using CCS and MotorWare projects
  1. Import projects
  2. Make changes to user.h or the project .c as required
  3. Build selected project
  4. Set-up Target Configuration (emulator and device)
    1. XDS100v2 + F28069 (all kits)
    2. XDS100v1 + F28027 (HVMTR kit)
    3. XDS100v2 + F28027 (LaunchPad)
    4. your emulator + F28027 (DRV kits)
  5. Launch Target Configuration
  6. Connect Target
  7. Load Program you built in 3.
  8. Turn on real-time debug
  9. Run
  10. Set-up Expressions View using the .js file for that project
  11. Interface to software using Expressions
    1. Starting in release _10 you can also use new Universal GUI inside CCS to instrument variable

  • As you work through the labs, consult the appropriate sections of the InstaSPIN-FOC & -MOTION User's Guide for further details
    1. Ex: when working through lab 2 you will want to review the Motor Identification chapter of the UG to understand exactly what is happening and the options you have to make changes.
  • If you want to start your own project based on a MotorWare example, a method for doing so that allows portability as we release new revisions (~2-4 times per year planned) is outlined in this post.

After evaluation and initial software development, prepare your own hardware

  1. Be sure to follow the guidance in the User's Guide regarding analog sense circuitry design


64 Replies

  • In reply to Richard Shank18:

    Hi Chris,

    Here's the data:

    Actual measured inductance from phase to phase is about 130 uH.  This leads to actual inductance being about 200 uH per winding in delta configuration.

    Actual measured resistance from phase to phase is about 23 mohm => 35 mohms per winding in delta configuration.

    I don't know calculate in your program yet.

    Here are the results of lab 3b:

  • In reply to Richard Shank18:

    if you just expand gMotorVars then yes, you need to set the number type.
    If you use the Scripting console and run the proj_lab##.js it will import the variables required for that lab with the proper number type. This is in the instructions.

    you can also install INSTASPINUNIVERSALGUI
    and follow the instructions from

    on how to use this GUI inside of CCS. That's what I do and I find it easier than using the variables in the Expressions.

    regarding your motor parameters, I trust the motor ID function (and your LCR meter) more than the motor designer.

    use proj_lab02c to ID the motors and store in USER_MOTOR section of user.h per the instructions.
  • connectionIssues.txt

    Hi Chris

    Thanks for the very elaborate instructions. It's a life saver.

    I opened the code present in


    Compiled it in ccs 7.0, but i have problems connecting to target.

    I had to choose a processor (28069M and XDSv2 as connection) I have a big "test connection report".  

    What do i do ?



  • In reply to srinath mallikarjunan:


    Please create a new thread for us to better attend to your question, we do not wish to support issues in old threads such as this.


    Did a reply answer your question? If yes, please click the "Verify Answer" button located at the bottom of that post.
    Visit these helpful C2000 Links!

    C2000 TI Wiki Pages
    TI Forum Sitemap
    C2000 Getting Started
    CLA FAQs
    Workshop Material!