• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 83 subscribers
  • Views 413 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

motorware style coding structure on 2837x

Yichao Zhang
Intellectual 495 points
Other Parts Discussed in Thread: MOTORWARE, CONTROLSUITE

Hi,

I like the motorware objective oriented coding structure. I wonder if there is similar structure designed for F2837x series chips. I took a look a control suite. there is actually a motor_control folder under lib.


Is it possible to migrate the INSTASPIN style code from F28069 to F28377? it use eQEP instead of sensorless.

Thank you

Yichao

  • 0
    TI__Prodigy 690 points
    Yichao,

    I am really glad to hear that you like the motorware style of coding! As for your question, unfortunately we have only supported processors with the FAST observer that is built in ROM. These processors are 2806xF, 2806xM, 2802xF, 2805xM piccolos. An objective of writing the object oriented software was so we could migrate between processors easily. Because the 2806x products are floating point, you could use the motorware sw/modules that are written for it in floating point. The floating point versions of the modules will be contained in the sw/modules/*/src/float folder. The floating point code that is written for the 2806x should migrate to other floating point processors. We have not created any driver or hal files for the F28377 in motorware format. We have removed the qep driver dependence from the enc.c and enc.h files, so you could use this file also, although it is fixed point.

    -Eric
  • 0 in reply to Eric (ASP) Thomas
    TI__Guru** 118750 points
    a similar coding style is used in controlSUITE for the F28027 Launchpad. This style will start being offered on F2837x/07x devices in the future, but I believe not til 2016. So in the future - for new devices - you will be able to choose the classic bit-field/macro approach or object oriented.