• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 83 subscribers
  • Views 479 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.

DK-LM4F-DRV8312 not working

Sam Hawker
Intellectual 850 points
Other Parts Discussed in Thread: DRV8312, INSTASPIN-BLDC

I have the DRV8312 kit with both the C2000 and Stellaris controlCARDs. The C2000 controlCARD works fine but I'm not overly impressed with InstaSPIN-FOC. I'm now trying to run InstaSPIN-BLDC on the Stellaris controlCARD and its not working properly. I've removed all the other Texas Instruments software versions and followed the installation instructions for the DRV8312-LM4F-BLDC. The GUI runs up but 95% of the time it fails to connect to the device. When it does connect I am able to start the motor but it stops again a few seconds later with the GUI reporting some kind of timeout. However, if I unplug the USB connection once the motor is running it will continue running indefinitely.

  • 0
    Intellectual 850 points

    Eventually I noticed a paragraph in a document somewhere that there is a known incompatibility between the Stellaris controlCARD and certain USB hubs. I tried it connected directly to the PC and it works now.

  • 0 in reply to Sam Hawker
    Guru 12800 points

    Sam,

    I noticed that you said you were not impressed with InstaSPIN-FOC.  Have you considered trying InstaSPIN-MOTION?  It features a more advanced speed controller than what is use in InstaSPIN-FOC and is able to realize better performance.  You can download the GUI for InstaSPIN-MOTION here: http://www.ti.com/tool/motorkitscncd69miso

  • 0 in reply to Adam D. Reynolds
    Intellectual 850 points

    Adam,

    I had a lot of problems with InstaSPIN-FOC initially because it was unable to identify my motor. Now I'm a bit more familiar with it and can bypass motor identification my opinion has improved somewhat. I've also switched to a motor that is slightly better suited to sinusoidal control. I have also had a quick look at InstaSPIN-MOTION. I have a feeling it isn't really a good fit for my project. To be honest I'm not sure I'm even going to use the PID speed controller in InstaSPIN-FOC. I'm making a RC car with independently controlled hub motors in all four wheels. I'm not sure that doing any kind of intertia-based control (which I think is what InstaSPIN-MOTION is doing) on individual wheels is very meaningful.

     

  • 0 in reply to Sam Hawker
    TI__Guru** 119670 points

    Sam,

    Correct, in a car type of application you are only commanding torque, and the user with the remote control is acting as the speed controller, commanding a torque request to your vehicle as desired.

    Is there a reason you are controlling all four motors independently? You are going to run into some interesting challenges in this application.  When controlling a pair of wheels independently the slightest difference in actual rotation will obviously have a noticeable effect on the driving experience.  It is much simpler to do the design like most real cars, where a single torque power plant is coupled/transmitted into each wheel so they are synchronized precisely.  Just know what you are getting into! :)

     

  • 0 in reply to ChrisClearman
    Intellectual 850 points

    My plan is to implement torque vectoring for improved handling.

    Roughly speaking I'm trying to replicate this guy's work:

    http://www.youtube.com/watch?v=SB5VcTMqHAQ