• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 1782 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.

InstaSPIN_MOTION and user.h

tyavashev
Prodigy 130 points

Other Parts Discussed in Thread: MOTORWARE, CCSTUDIO

Hi,

I'm using InstaSPIN_MOTION_F2806xM with DRV8301D kit. And now I want to use ID method user.h, but unfortunately it is not so easy as I expected, i.e. the App will load user.h file from somewhere, the "identified hardware target" folder for example. So in "qsg_gui_instaspin_motion.pdf", I found the following:

"

• User.h Settings (Note: The steps for modifying the user.h file are covered in
detail in the InstaSPIN-FOC and InstaSPIN-MOTION User Guide.)
o Select “User.h Settings” to bypass the Identification process and load the
values and Identification Settings stored under USER_MOTOR in the
user.h file that was used during project compile.
o To save your own motor parameters you will need to update the user.h
file, recompile, and copy the .out to \appProgram.out
Note: Re-compiling of this project will be offered shortly in a
future revision

"

Please, I will appreciate if somebody could provide me a step-by-step how to do this. 

  • 0
    TI__Guru** 119680 points

    tyavashev,

    You can NOT use your own user.h settings with

    C:\ti\guicomposer\webapps\InstaSPIN_MOTION_F2806xM

    At one point we thought we were going to release the project so that you could rebuild with your own user.h file, but we decided against this. The source for the project is not something we want to have to support for a variety of reasons (old code base that doesn't exactly match what we have released in MotorWare, doesn't have latest enhancments in MotorWare, very complex state machine / switching to support FOC/MOTION/PI/SpinTAC, etc.)

    The GUI should be thought of as a quick way to demo and see the capability of most of the InstaSPIN features. It will ID about 80% of motors, but not all (due to fixed scaling and missing some ID enhancements we've added in last year to MotorWare).

    So you need to move on to the MotorWare projects.

    You should follow 
    C:\ti\motorware\motorware_1_01_00_12\docs\labs\instaspin_labs.pdf

    You can use a GUI to instrument this MotorWare code though (either stand-alone or inside of CCStudio):
    C:\ti\motorware\motorware_1_01_00_12\docs\guis\universal\qsg_gui_universal.pdf

    This document is also useful for understanding some of the user.h scaling that you need to be aware of for your particular motor.

    I also recommend you read some posts on this forum, especially the ones Stickied

     

  • 0 in reply to ChrisClearman
    Prodigy 130 points

    Hi Chris and thank you.

    I've already got familiar with MotorWare documentations and projects. Yes, not 100% of course. :)

    As usually happens, once I sent the previous post, I've used lab 5c  to get the system inertia.

    So, now I have control and my project goes very well.

    Just to share some info - My project is to control the motor in position mode, using an encoder. The encoder is incremental for now and the selected one is according to the precision we want. But later we plan either to replace it with an absolute encoder or to use both together. So, I read all post here about position mode, I think. :) And of course I've used lab 13b (mostly) to tune my system. In additional I did a GUI using GUI Composer to interact with this lab. But my project requires absolute position mode and I have to access the encoder data to implement it.

    So, I will appreciate any suggestions, examples and so on.

    Best Regards,

    Tenko Yavashev

     

  • 0 in reply to tyavashev
    TI__Guru** 119680 points

    glad to hear things are going well.

    All of the position conttrol information is in proj_lab13x, so you are looking in the correct place.

    You may be interested in the post LineStream has made regarding the 2-axis CNC machine.