• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 83 subscribers
  • Views 989 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DRV8312-69M-KIT: Programming of motor parameters

Demetrios Katsaduros
Prodigy 80 points
Part Number: DRV8312-69M-KIT
Other Parts Discussed in Thread: MOTORWARE

Hello to all,

I would like to ask how is it possible to first extract motor parameters from the C2000 motor controller and save as a setting file? 

Second, is there a way to manually program the C2000 motor controller with motor parameters when different motor types are attached?

  • 0
    TI__Guru** 116090 points

    1. You can save the motor parameters in on-chip flash or external memory like eeprom via I2C/SPI, or transmit these parameters to PC to save as a data file.

    2. You can define different motor parameters in a header file as user.h, and then change the motor parameters variables of gUserParams as USER_setParams(&gUserParams), to call below 3 functions to re-setup motor parameters for instaSPIN.
    CTRL_setParams(ctrlHandle,&gUserParams);
    CTRL_setUserMotorParams(ctrlHandle);

  • 0 in reply to Yanming Luo
    Prodigy 80 points

    Thank you very much for your help and response! 

    1. - for the software extraction portion, is this done via motorware?

    2. - where are these being called from? GUI Composer?

  • 0 in reply to Demetrios Katsaduros
    TI__Genius 17175 points
    1) Writing to an external memory must be taken care of in user code, we do not provide this feature by default in our examples
    2) There are API that copy user variables/settings from the user.h into the gUserParams struct during run time in the Motorware example code. These API are mentioned in Yanming's post. You'll need to look at the example source code to see where these are called; the GUI simply acts on a compiled source project that is handed to the GUI in form of a .out file. You won't get any idea of what's happening "under the hood" by using the GUI tool

    Sean