• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 81 subscribers
  • Views 523 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Motor identification problem

Yau Tsang
Prodigy 160 points
Other Parts Discussed in Thread: DRV8301, MOTORWARE, CCSTUDIO

Hi,

I have the DRV8301 Drive and Piccolo F28069MISO ControlCard. After setting the whole thing up, I opened InstaSPIN Motion F2806xM and tried to let it identify my motor. With Automatic ID identification method, the progress would only go as far as 45 or 46% where it abruptly stops, giving an "EST_State_Error" status. I have also went through the whole ordeal with recompiling the user.h file and renaming projects' *.out file as appProgram, and placing them in the appropriate folder, but then InstaSPIN Motion could not even identify the Hardware (the green light appears next to the HV Kit 1.1 instead of the DRV8301...)!

I then tried doing this in InstaSPIN F2806xM Universal, and it shines a green light indicating an 'Identified Motor' if I have the "user.h settings" selected, but my motor does not spin at all, and it gives me "CTRL_State_OffLine" and "EST_State_Idle" statuses the whole time. All my parameters in my "user.h" file do show up correctly in the interface though. If I have the "user.h settings" disabled and attempt running it, the Motor Identification has a red light instead, indicating a failure.

There is one thing that bugs me; the LD2 LED on the ControlCard continues to blink if I open InstaSPIN F2806xM Universal, but this doesn't happen at all if I just use InstaSPIN F2806xM Motion. Does the blinking LED mean an error with the connection or hardware setup? Even in CCS v5, when I try to debug a project, it keeps giving me (Error 151 @ 0x0) with a message about problem with connection. I'm not sure if this is the right place to ask this question, but I would really appreciate any sort of help and guidance!


Thank you
.

Regards,

Yau

  • 0
    TI__Guru** 118000 points

    Yau Tsang said:
    have also went through the whole ordeal with recompiling the user.h file and renaming projects' *.out file as appProgram, and placing them in the appropriate folder, but then InstaSPIN Motion could not even identify the Hardware (the green light appears next to the HV Kit 1.1 instead of the DRV8301...)!

    This happened because you tried to use the "standard" InstaSPIN MOTION GUI with a MotorWare project. Per the documentation this is not supporting. The InstaSPIN MOTION GUI is "frozen" and is for demo purposes only. It won't work with certain motors and doesn't have all the updates that have been added into MotorWare.

    Yau Tsang said:
    I then tried doing this in InstaSPIN F2806xM Universal,

    This was the correct thing to do. When using MotorWare project and following the Projects & Labs User's Guide you can use the CCStudio Expressions and manipulate variables in the gMotorVars structure, or you can use the Universal GUI inside CCS (my preference) or standalone.

    Yau Tsang said:
    and it shines a green light indicating an 'Identified Motor' if I have the "user.h settings" selected, but my motor does not spin at all, and it gives me "CTRL_State_OffLine" and "EST_State_Idle" statuses the whole time.

    1. which pro_lab## did you run?

    2. are you following the procedures in the Lab Guide?

    3. if you checked the "user.h settings" it will skip motor ID (if the lab is enabled for this) and load from user.h....do you have the correct motor settings IN user.h?  Doubtful.  You need to do a motor ID first, meaning DESELECT user.h and use proj_lab02b or 02c (if you have a high speed motor)

    Yau Tsang said:
    There is one thing that bugs me; the LD2 LED on the ControlCard continues to blink if I open InstaSPIN F2806xM Universal, but this doesn't happen at all if I just use InstaSPIN F2806xM Motion. Does the blinking LED mean an error with the connection or hardware setup?

    No, it doesn't have a meaning. LD2 is controlled from the .out that you load, so it depends on which SW you are running. Blinking is usually a good sign that the embedded code is running.