• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 387 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.

DRV8316REVM: Universal control lab using DRV8316REVM, LAUNCHXL-F280025C, BDLC motor

Shahar Cohen
Intellectual 331 points
Part Number: DRV8316REVM
Other Parts Discussed in Thread: LAUNCHXL-F280025C

Hey, 

In the User’s Guide Motor Control SDK Universal Project and Lab , I'm trying to do the Build Level 1 lab with no success.
I'm using :DRV8316REVM, LAUNCHXL-F280025C

In - 2.5.1.3 Run the Code when I'm trying to set the motorVars_M1.flagEnableRunAndIdentify to 1 (I check that systemVars.flagEnableSystem was automatically set to 1 before) the motorVars_M1.flagEnableRunAndIdentify instantly go back to zero 

I found out that the motor motorVars_M1.motorState = MOTOR_FAULT_STOP and when measuring with oscilloscope there is no output from the phases

predefined Symbols:

In addition I will note that i read this post and it did not help. 

I would appreciate your assistance, 

 

  • 0
    Intellectual 331 points

    Hi, 

    We have successfully identified the issue with the DRV8316REVM Evaluation Module (Rev. B). Upon careful examination of the User Guide DRV8316REVM Evaluation Module (Rev. B), specifically the quick start guide, we noticed a discrepancy. In the guide, it advises, "Ensure R13 on the bottom layer is not populated."

    However, after conducting further tests, we discovered that connecting R13 back to the driver resolved the problem. We are seeking clarification on the rationale behind this, and we would appreciate it if you could shed light on whether there might be an error in the provided user guide.

    Your prompt response and insights into this matter would be greatly appreciated.

    Thank you for your attention to this issue.

  • 0 in reply to Shahar Cohen
    TI__Genius 12231 points

    Thanks for posting,  Shahar.  

    Please let me look over this info and the behavior regarding R13 and follow-up by Monday. 

    Best Regards, 

    -Joshua 

  • 0 in reply to Joshua Maize
    TI__Genius 12231 points

    Hi Shahar, 

    I apologize for the long delay in communication. 

    R13 is the connection between the 3.3V buck supply and the launchpad's 3.3V USB supply, and the buck is responsible for the hall sensor power/motor state recognition. 

    It may be possible that if the buck were disabled then having R13 populated would allow the 3.3V from the launchpad to still power the hall sensors through buck connection, but leaving R13 unpopulated would leave the buck disabled completely. 

    Can you ensure that the BUCK_DIS bit in the register is set to 0b and not 1b? 

    Thank you for your patience. 

    Best Regards,

    -Joshua