• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 81 subscribers
  • Views 1504 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.

Block commutation control instead of sine commutation

Oliver Haala
Prodigy 220 points

Other Parts Discussed in Thread: TMDSCNCD28069, CONTROLSUITE, DRV8301

Hi,

I am using the Inverter DRV8301-HC-EVM Rev D together with the control card TMDSCNCD28069. I am using InstaSPIN-FOC for sensorless FOC. I am aware of the fact that sinusoidal commutation is superior to block commutation in most application cases. However, we need to fulfill this customer requirement.

Ideally, I would like to use the InstaSPIN Lab02b and extend it by the block commutation mode. It should be possible to switch between sensorless FOC and block commutation under load. Could anyone provide a code segment which covers the block commutation mode and elaborate briefly on how to integrate it into the existing control scheme?

Kind regards,

Oliver

  • 0
    TI__Guru** 119680 points
    Oliver,
    this isn't something we provide. I do know some e2e users have implemented this though.

    BLDC block commutation at start-up can provide more torque than FOC if done correctly. Typically customers are using HALL sensors as well for the commutation. So they start-up under HALL BLDC and then transition to FOC. You would need to use a method like we demonstrate in:
    C:\ti\controlSUITE\development_kits\DRV8312-C2-KIT_v128\BLDC_Sensored

    there isn't a released version of this for DRV8301 EVM, but I posed a working Hall BLDC example on the Motor Drive e2e forum several years ago.


    In proj_lab11e we start-up with Hall sensors, but we aren't doing strict BLDC commutation. We are still generating a fixed angle (60, 120, 180, etc) but running it through the SVPWM module. Also, this lab has some other problems that we are going to fix for the next release, so I don't recommend spending time on it at the moment.