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.

TMS320F28378D: interface to absolute position encoders

Part Number: TMS320F28378D
Other Parts Discussed in Thread: CONTROLSUITE

Hi:

We are working in a motor control application with TMS320F28378D microcontroller. We should be able to manage the following interfaces and encoder types:  quadarture, hiperface, EnDat01, BiSS-C and preferably also SSI. We have analysed the support provided by you and we have some questions we would like to clarify:

  • Do you recommend the use of your libraries in MotorControlSDK or is it better to use ControlSuite with CLB and modify it according to our necessities?
  • Do you think is it possible with existing CLBs to provide support to all that type of Encoder?
  • We already have the HW and many of our I/O are allready used. How could we configure CLBs in that scenario?
  • Is available the Hiperface (not Hiperface DSL) example?

 Thanks for your support.

Rober

  • Hi Roberto,

    Do you recommend the use of your libraries in MotorControlSDK or is it better to use ControlSuite with CLB and modify it according to our necessities?

    Our latest software is in the MotorControl SDK. For absolute encoder interfaces, only T-format is in the SDK and fully documented with source code.

    Do you think is it possible with existing CLBs to provide support to all that type of Encoder?
    quadarture

    quadrature decode is supported by our eQEP peripheral 

    EnDat01, BiSS-C

    EnDat2.1 and BiSS-C are not supported in the MotorControl SDK at this time. Unfortunately we do not have a solid schedule I could share with you. 

    hiperface

    We do not have a hiperface or hiperface DSL example

    We already have the HW and many of our I/O are allready used. How could we configure CLBs in that scenario?

    Since the EnDat2.1 and BiSS-C are only available as a demonstration libraries (in controlSUITE) the i/o usage will be mostly fixed. The design guide for each has a table that details which signals can be modified outside of the library. 

    Regards,

    Lori