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

DRV8316: DRV8316R and LaunchXL-F280049C support request

Shlok Desai
Prodigy 65 points
Part Number: DRV8316
Other Parts Discussed in Thread: MOTORWARE,

Hi Team,

Working on Field oriented control of a BLDC Motor I had bought this LaunchXL F280049C Microcontroller and the DRV8316R Motor driver, I tried to find support for a similar rig online but only found the GUI composer studio support, for FOC using code I found TI E2E FAQ's regarding the use of Motorware SDK for source code implementation on DRV8316R (Link for the FAQ). But this did not seem to work for me. 

What all I tried- 

  1. Tested the independent functionality of the LaunchXL 320049C, where everything works well, all the GPIO's, Timers, Interrupts, ePWM's, UART communication and CAN communication as well. So it does not seem to be a problem with the eval board.
  2. Then to get the motor up and running, tried using the Universal GUI (DRV8316xEVM_InstaSPIN_UNIVERSAL_GUI), which when set up according to the TI tutorials as well as the datasheet, identifies all the motor parameters except the inductance of the motor, the GUI then goes from stage to stage to identify the motor where when it starts with the ramp up part of the program there is some movement seen in the motor and then nothing happens, the state is then displayed IDLE. While all this is happening, the inductance is still displayed 0, can this be because of my using a low inductance motor? For trying to run the motor with the GUI I have thoroughly gone through all the documentation available from TI as well as anything available on the net but had no luck on making the motor run.
  3. This is when I came up with the motorware SDK and found there were some example codes for motor identification which works in a similar fashion to that of the GUI that is when i tested the code as well, which builds with errors and is not possible to flash directly, is there some changes required in the code specific to the rig ones using.

Can you help me out with this?

  • If possible help me out with any changes if required in the examples present in the motorware SDK.
  • Can you suggest the reason why my GUI does not work

Thanks,
Shlok Desai