• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 32 subscribers
  • Views 565 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.

Original question:

[FAQ] DRV8316REVM: DRV8316REVM Source Code for MotorControl SDK

DRV8316REVM: Using this EVM with Motor Control SDK 5.0 and the LaunchXL-F280049C

Paul Eason
Prodigy 50 points
Part Number: DRV8316REVM
Other Parts Discussed in Thread: C2000WARE, , SYSCONFIG

We are developing a product that would use two DRV8316Rs and either a single or two independent C2000 processors (either would work for us).  I have the DRV8316EVM and the LaunchXLF280049C and using the universal GUI did the easy stuff making the motor spin... now the hard part, getting a control system that runs our motor (preferably with a current loop) that we can wrap a position loop around and perform positioning using either a sensored or sensor-less motor with an incremental encoder.

In earlier versions of the SDK, there were introductory labs that used the DRV8316EVM and the LaunchXLF280049C.  The labs in SDK 5.0 now refer to different processors and I'm having difficulty following how to get started with the SDK 5.0 with this combination.  It seems that there is a universal motor control lab that works with f28002x, f28003x, f280013x, and f280015x processors but not the f28004x.  It's not clear to me what support, documentation and examples there are for the DRV8316EVM and SYSCFG based Motor Control SDK (my preference).

  • Do I revert back to the old version of the SDK and forgo SYSCFG?
    • This is not ideal for us in the long run since we have considerable other code developed using SYSCFG that we would like to leverage
  • Is there a suitable set of labs that work with our current hardware configuration? 
  • I'm not opposed to changing our C2000 processor provided that there is a LaunchXL board that can be used with the DRV8316EVM and the Motor Control SDK. 

The key for us is the DRV8316R and how compact we can make the system using that chip.  

Please advise

  • 0
    TI__Mastermind 23676 points

    Hey Paul,

    Have you consulted this resource on C2000Ware_MotorControl_SDK (5.00.00.00)?

    https://dev.ti.com/tirex/explore/node?node=A__AM2QqKBFwgDul9ZI6vXPJQ__motor_control_c2000ware_sdk_software_package__0.jXikd__LATEST

    In the mean time I will let the C200 team comment on further guidance.

    Best,

    Akshay

  • 0 in reply to Akshay Rajeev Menon
    Prodigy 50 points

    Akshay, thank you for the reply.  Yes, that is where I got the list of available processors that work with the included labs.  I've dug through most of the examples but I'm looking for some prototypical examples that will help me move forward.

    I am a bit stuck on how to proceed.  Advice from the team and any others would be greatly appreciated. 

    Kind regards,

    Paul

  • 0 in reply to Paul Eason
    TI__Genius 11076 points

    Hello Paul,

    I've figured out what happened! Essentially, the DRV8316REVM labs were not natively included with the C2000Ware Motor Control SDK. Instead, they were a software package later released. The files can be found here and unfortunately do not include SysConfig configuration files.

    If you are open to other devices, the Universal Motor Control Lab is a broadly applicable, very useful resource that does have these files. I'd also recommend the C2000 Academy and the various other C2000Ware examples as fantastic resources on learning and using the SysConfig tool. The F280049C is available on these resources.

    Regards,
    Jason Osborn
    Note: Key takeaways from this post are bolded.

  • 0
    Prodigy 50 points

    Sorry, I've been away for about a week now, just getting back to this.  Per Jason, I'll have to down-rev my version of the SDK and perhaps C2000Ware to 3.0 level to make this work.  I have versions 4 and 5, so drop back to version 3?  Will I need older C2000Ware and an/or older version of CCS to make this work?  Sorry for the questions.  I have tomorrow (Friday 8/31) allocated to work on this project again.

    I am quite familiar with C2000 and CCS but the switches and changes in the Motor Control SDK have been exceptionally hard for me to follow since support for various processors and driver electronics has been changing every revision.  

    My program manager for this project has asked me to start evaluating other suppliers for motor control processors, I'm pushing back because I know the C2000s do a good job but soon I may be forced to change horses due to the lack of consistency and support for products that will fit our needs.

    Regards,

    Paul

  • 0 in reply to Paul Eason
    TI__Genius 11076 points

    Paul,

    Apologies for the delay, I was out of office. I am not aware of any changes in the C2000Ware Motor Control SDK that would result in incompatibilities between the drv8316revm labs and the current version of the MCSDK- the software package released in that FAQ should still be functional.

    This link (the release notes for the MCSDK) do not list any instances where a product was no longer supported. When have you seen this happen?

    Regards,
    Jason Osborn

  • 0 in reply to Jason Osborn
    Prodigy 50 points

    I will give the configuration with the current MSDK and the older program examples.  I have been wrapping up another project and will get back to this later in this week.  If it does work, I will let you know and we can close out this issue.

    Thank you,

    Paul