• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 84 subscribers
  • Views 2371 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.

TMS320F280049M: F280049 MotorWare / InstaSPIN support?

Giannis Roussos
Expert 2290 points
Part Number: TMS320F280049M
Other Parts Discussed in Thread: MOTORWARE, C2000WARE, DESIGNDRIVE, CONTROLSUITE

Hi, we have developed a family of motor controller products using F28027 and F28069 mcus and (heavily modified) MotorWare and are very intrigued by the F280049. However, I understand that although F280049M includes InstaSPIN functions, no official support is available yet.

Looking though the F280049 C2000Ware examples, it seems that porting our codebase from the MotorWare handle-based HAL/drivers to the new driverlib is not too difficult, however I am not yet convinced there is any point in doing so:

  1. The required InstaSPIN library and headers for F280049 are not released yet. Without them we could only modify our code to remove sensorless operation (i.e. FAST estimation) but even then we would need to reimplement some CTRL functions. Do I get this right?
  2. What is the schedule for official InstaSPIN support for F280049 by TI? Will it come as an Application SDK on top of C2000Ware? If yes, will it include support for F28027 and F28069 (although I don't see a driverlib for these)? That would be great, enabling a common code base for all InstaSPIN enebaled mcus. MotorWare HAL was unnecessarily separated for each Picollo line (separate but identical drivers etc), C2000 / driverlib seem to be in the right direction, will it support other Picollo lines (02x, 06x) in the future?
  3. Can TI at least release the required library and header files for F280049 so that we can use them with (ported) MotorWare?

Any info appreciated,

Giannis

  • 0
    TI__Guru** 119670 points

    We will release a MotorControl SDK in Q4 this year. It will include a version of C2000Ware and will initially provide support for InstaSPIN-FOC projects on F28004x devices.  Over time it will expand to include general motor control libraries, DesignDRIVE solutions, and support for other C2000 series. 

    Currently while XF280049M, F280049C,and F280041C devices include the InstaSPIN libraries in ROM, without the SDK you can't implement the solution.

    MotorWare will remain for F2806xF/M, F2805xF/M, F2802xF.  It will not support F28004x.

    MotorControl SDK will not specifically support any of the already released C2000 devices and will not be used for InstaSPIN on F2806xF/M, F2805xF/M, F2802xF.

  • 0 in reply to ChrisClearman
    Expert 2290 points

    Hi Chris,

    thank you for the detailed reply. So MotorWare and MotorControl SDK will coexist separately for separate product lines. That's a pitty because F280049 could be a great upgrade over F2802x/5x/6x if it was supported by the same software. From what I understand, the F280049 hardware peripherals are the same with other Picollo series, so supporting F280049 by the same SW architecture would be easy. Although I do prefer the newer C2000ware driverlib architecture, adding F280049 support in Motorware would be awesome. Alternatively, the best would be a convergence of MotorWare and MotorControl SDK, though I understand this would take more effort.

    In any case, given the InstaSPIN library and header files that will be included in MotorControl SDK, will I be able to add support for F280049 to MotorWare myself? Is something else needed, assuming that all peripheral drivers can either be copied from other F2802x/5x/6x (if they are indeed the same) or ported from C2000Ware?

    Thank you in advance,

    Giannis

  • 0 in reply to Giannis Roussos
    TI__Guru** 119670 points

    the InstaSPIN projects in MotorControl SDK will look very similar to what is in MotorWare. It will include a more full featured and supported driver lib (from C2000Ware) so this is a much better solution than trying to support F28004x in the old MotorWare.

    You will not use MotorWare for F28004x.

    The InstaSPIN projects will be in the SDK, in a very similar look & feel.

  • 0 in reply to ChrisClearman
    Expert 2290 points
    C2000Ware + MotorControl SDK does indeed sound better than current MotorWare framework. However, I was hoping that there was going to be a single SW framework (MotorWare or C2000Ware + SDK, preferably the latter) that could be used for all InstaSPIN enabled Piccolo MCUs. Thus it would remain possible to have a single SW architecture for a range of products using Piccolo MCUs. We do that already with MotorWare and F2802x/6x and were expecting that F280049 could be used for an upgrade / extension of the existing product line, maybe through a software migration to C2000Ware (for all MCUs that is).

    The plan you present forces a separate SW architecture for old InstaSPIN Piccolos and F280049, am I correct? This is rather odd, considering that F280049 seems exactly like an upgrade of the existing Piccolo models rather than something different altogether (and we saw that as a good thing!)
  • 0 in reply to Giannis Roussos
    TI__Guru** 119670 points
    it forces a separate use of MotorControl SDK vs. MotorWare + controlSUITE. The SW architectures are quite similar, with MotorControl SDK being full featured and complete, especially with the C2000Ware based drivers. The InstaSPIN portion of the SW is very, very similar.

    I understand that desire to have one software base for all devices, but unfortunately MotorWare for F2806x/5x/2x was released during a time before we built a more cohesive software story.

    The good news it will be a much better solution starting with F28004x and moving forward.
  • 0 in reply to ChrisClearman
    Expert 2290 points

    Ok then, I'm eagerly waiting for te MotorControl SDK, hoping that I will be able to merge it with our current (MotorWare-based) SW platform so that we have a single base for all products using Piccolo MCUs.

    I understand that MotorWare needs to be replaced, still I find it disapointing that MotorControl SDK wont support other Piccolo MCUs, especially given that as you say InstaSPIN code will have "a very similar look & feel" and that F280049 seems like a superset of F28026/5x/6x, so C2000Ware support for those MCUs too should be trivial.

    Thank you for the info.

    Giannis