• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 83 subscribers
  • Views 510 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.

EVM selection for Control DC motor position

FRANK1
Expert 8805 points

Other Parts Discussed in Thread: LAUNCHXL-F280025C, BOOSTXL-3PHGANINV, C2000WARE-MOTORCONTROL-SDK, MOTORWARE, LAUNCHXL-F280049C, C2000WARE, BOOSTXL-DRV8320RS, DRV8320

Hi sir,

A customer wants to use TI EVM board for best feature we can use to control DC motor position.
he wants to control his two DC motors with the help of driver and optical encoders ,

so for that he wants to use TI MCU board which has feature for this specific application which is eCAP and QEI for motor control.
so he wants to which one is better so that he can chooses one board.
TIVA C for QEI and C2000 for eCAP.
suitable board for motor position control and GPIO can output at least 10mA current.

Thanks a lot for your suggestion.

Regards,

  • 0
    TI__Guru** 119680 points

    For C2000 you would use eQEP peripheral for incremental encoder feedback, not eCAP.

    LAUNCHXL-F280025C is the LaunchPad I would recommend.

    2 of BOOSTXL-3PHGANINV is the BoosterPack 3ph inverter I would recommend

    C2000Ware-MotorControl-SDK has an example of 2 axis servo position control for this combination

  • 0 in reply to ChrisClearman
    Guru 56168 points
    ChrisClearman said:
    LAUNCHXL-F280025C is the LaunchPad I would recommend.

    Do the new SDK's even work with older MCU classes? Are not the older versions of C2000 Motorware suite required?

    However the LauchXL-x49c has 2 eQEP header inputs and SDK supports dual motors, supposedly via two BoostXL-drv8230rs booster packs.

    The NexFETS 40 amp current drive is robust easily adding 20mm +5v fans over head also USB powered via isolation jumpers. The USB CCS real time silicon debug isolation is also a huge diagnostic engine.

  • 0 in reply to Genatco
    TI__Guru** 119680 points

    The application SDKs have projects for Gen3 devices (Gen 3 described at www.ti.com/c2000 Portfolio) 

    F280025C is Gen 3.

    LAUNCHXL-F280049C is also a valid choice, it has a 2 servo example using BOOSTXL-3PHGANINV.  The combination with DV8320RS is for sensorless InstaSPIN-FOC control.

    MotorWare is application examples for older Gen 2 devices enabled with InstaSPIN technology.

    If you are asking if you should use TIVA or C2000 for QEP based servo control, the answer is clearly C2000.

  • 0 in reply to ChrisClearman
    Guru 56168 points
    ChrisClearman said:
    F280025C is Gen 3

    Interesting dual axis code omits drv8320rs NexFET boards given current drive servos under load demand. A consensus being GAN drives do not have the best current drive needed for motor control <40kHz. GAN's are great for DC/AC converters (40-100kHz) with little to no Trr dv/dt and oddly ring heavily rise/fall times. 

    ChrisClearman said:
    MotorWare is application examples for older Gen 2

    Not sure why I was believing x25 was mated with Motorware suite, perhaps since it has a slower MOSC.  

    ChrisClearman said:
    LAUNCHXL-F280049C is also a valid choice, it has a 2 servo example using BOOSTXL-3PHGANINV.

    That would seem like a better match 100Mhz MCU with dual motors and 2 QEP interrupts.

    ChrisClearman said:
    he combination with DV8320RS is for sensorless InstaSPIN-FOC control.

    Yet the SDK folder drop list shows inclusive QEP drive and DRV8320rs has dual motor control projects. Perhaps it requires project modifications to tie in QEP drives. I had asked this QEP question drv8320rs roughly month ago, if both projects are SVPWM based FOC why not. 

    C:\ti\C2000Ware_MotorControl_SDK_2_01_00_00\solutions\boostxl_posmgr\f28004x\source\qepdiv.c or pto_qepdiv.c

    C:\ti\C2000Ware_MotorControl_SDK_2_01_00_00\solutions\common\sensored_foc\source\dual_axis_servo_drive_user.c

  • 0 in reply to Genatco
    TI__Guru** 119680 points

    I'm not sure that's true about GaN, but the primary reason we use that BoosterPack for servo is the inline current sensing.

    Not sure what slower MOSC means. Both F28002x and F28004x are 100 MHz.  Also, I just noticed that the LAUNCHXL-F280025C support is not listed on the table of solutions on the MotorControl SDK.  There is a new update going out tomorrow and should have proper support updatees.

    Again, F280025 also has 2 QEP and 100 MHz. It is fully capable of dual axis servo and is being used in production systems.  Memory is of course tight for some applications.

    You can certainly do sensored control with the DRV8320RS, we just chose to us a different BoosterPack for Servo vs. Sensorless.

  • 0 in reply to ChrisClearman
    Guru 56168 points
    ChrisClearman said:
    Again, F280025 also has 2 QEP and 100 MHz.

    I had checked MOSC (main oscillator) was shown to be 90Mhz on TI web pages some time ago. On reason to choose x49c beside the higher current drive of BoostXL-drv8320rs 60A extremely low RDS NexFET's. When given 1" copper areas for cooling and of course with built in heat sinks on top another great advantage. 

    ChrisClearman said:
    You can certainly do sensored control with the DRV8320RS, we just chose to us a different BoosterPack for Servo vs. Sensorless.

    That seems to make sense why the folders are common but custom code generation is complex and time consuming for many. Seemingly the GAN project could be ported to use 2 drv8320rs SPIA/B drives. If the 3PHGAN is a dual motor control Booster pack that might be another good reason to select GAN drives.

  • 0 in reply to Genatco
    TI__Guru** 119680 points

    The MCU selection has nothing to do with the current drive of the Booster pack of course, which I think you know.

    We just provide these as examples, and we don't want to try to support every possible combination of LP + BP.   The porting of example code from one LP to another is pretty straight forward for anyone capable of making an embedded software product.

    Both the DRV8320 and 3PHGAN are single inverters, so we use two of each for any dual inverter applications.

    In your example case it's easier to start with the project for the BoosterPack you like and port from one LaunchPad to the one you would like to use, not vice versa.