• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 269 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.

LAUNCHXL-F280049C: sensor motion control examples

Baruch Einziger
Intellectual 350 points
Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: DRV8320, , BOOSTXL-DRV8320RS, TMDXIDDK379D

hi all

i am looking for  motor control with sensors example for launchxl-f280049c  + DRv8320,
where could i find this examples?

thanks

Baruch Einziger

  • 0
    TI__Genius 10006 points

    Hello Baruch,

    Sincere apologies for the delay in response! Looking through our existing examples, it appears that for the specific combination of the LAUNCHXL-F280049C and the BOOSTXL-DRV8320RS, the C2000 Motor Control SDK (MCSDK) has several examples for sensorless motor control, but no fully implemented sensored control.

    However, the sensorless examples do have initialization code for the eQEP peripheral that can be enabled (by setting _EQEP_EN_ as a predefine in the project properties, as shown here:

    Additionally, the following examples in the MCSDK have F28004x sensored control implementations which can be used as a reference to adapt the DRV8320RS projects:

    • boostxl_3phganinv
      • dual_axis_servo_drive_fcl_qep_f28004x.projectspec
      • I recommend referring to this example in particular, as it is a launchpad + boosterpack example.
    • servo_drive_with_can
      • servo_drive_with_can_f28004x.projectspec
    • tidm_02006_multi_axis_drive
      • multi_axis_nodeY_f28004x_cpu.projectspec where 'Y' is 1, 2, 3, or 4
    • tmdxiddk379d
      • fcl_f28004x_tmdxiddk.projectspec

    I hope that is helpful. If you need any explanations on what I'm referring to, don't hesitate to ask. I'll respond much more promptly in the future!

    Regards,
    Jason Osborn