• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 926 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.

Workflow for testing Instaspin-BLDC using DRV8301 Kit without a GUI

Omkar Savant
Prodigy 210 points
Other Parts Discussed in Thread: INSTASPIN-BLDC, HALCOGEN, MOTORWARE, DRV8301

Hello,

I am trying to get a motor running with the DRV8301-LS12-Kit and have been able to successfully control it through the GUI using the Instaspin-BLDCsolution. However, I would like to program it using the Instaspin control solution but without operating the GUI. I am using CCS v5.4 because I was advised by a TI employee that v5.6 and later were incompatible with this kit. 

I have been modifying the project01  (C:\ti\Hercules\MotorWare\v1.0.3.03\sw\solutions\instaspin_bldc\boards\drv8301kit_revD\hercules\tms570ls1227\projects\ccs5\project01) by manually hardcoding parameter values of the GUI_obj because other aspects of the program are based on values of variables such as gGUIObj.TPSFlag. The end goal of this is to create implement a control algorithm that speeds up and slows the motor based on external sensors (essentially automating the user's manual operation of the GUI speed knobs) while using Instaspin for the actual commutation control. Is there a more elegant/simple way to do this without replacing the GUI_obj (perhaps through HalCoGen) or is this the only way to do it?

Thanks in advance for any help.

Note: I have also posted this question in the Instaspin forum inside the c2000 family of MCUs but realize the Instaspin-BLDC is quite different from FOC and Motion solutions, so I was not sure which would be most applicable. 

  • 0
    TI__Guru**** 191736 points
    Hi Omkar,
    We have received your post and will get back to you shortly.
  • 0 in reply to Charles Tsai
    TI__Guru 68920 points
    Omkar,

    Seems like you have earned your surname on this one ;) because you've gotten further than anyone else who has tried to pick up this project recently. I'm envious because I've been trying to get GUI composer working and no luck. I have started an internal thread w. the GUI composer team and it seems like there ie2e.ti.com/.../1902220 much work to do to bring the GUI up to CCSv6. Also apparently the version of GUI composer used for this project originally was really pre-5.3 which is the earliest that you can download now from TI.com.

    Did it just work for you? I imagine you must have had to do a lot of work to get it working... If you have a recipe that you can share it would be awesome.

    But anyway your question about the GUI object - non of this code comes from HalCoGen. HalCoGen only generates the low-level driver code - the motorware is an application on top of but not configurable with the HalCoGen GUI.
  • 0 in reply to Anthony F. Seely
    Prodigy 210 points

    Hi Anthony, 

    Thanks for the reply! I wish I could say I had been able to get my own GUI working, but I'm fairly new to these microcontrollers and all I did was use the pre-made GUI that came with the CD in the kit after moving the file "DRV8301_TMS570LS12_BLDC" into the ti/guicomposer/webapps directory. Regarding the GUI object, since none of the code comes from HalCoGen, would hardcoding the GUI object parameter values to circumvent the GUI-based user entry altogether be the way to go? 

    Regards,

    Omkar

  • 0 in reply to Omkar Savant
    TI__Guru 68920 points
    HI Omar,

    Yes I think so. I've only been able to get the motor to spin by manually poking these GUI object variables through CCS's expression window.

    If the GUI works properly then the controls on the GUI just translate to 'programatic' poking of these locations based on actions you perform with the HTML controls.

    So if you wanted to say change an HTML5 'switch' to a real physical switch then some software wrapper that converted the switch input to a write to the same 'gui object' variable should produce the same sort of response.