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.

DRV8313: Differences in motor drive

Part Number: DRV8313
Other Parts Discussed in Thread: DRV8316, , DRV10974, DRV8300, LAUNCHXL-F280049C

Hi Dear,

1-Does the BLDC motor driver chip DRV8313 and DRV8316 require an additional Hall sensor?

2-Do all BLDC Drivers in the following figure do not require Hall sensors?

3-

Regarding DRV8313 and DRV10974, one is BLDC drive and the other is trapezoidal control motor drive. Ignoring the difference in power parameters, is the biggest difference whether to integrate control algorithms

  • Hi Anna,

    Thank you for posting this question! In order:

    1. Systems with the DRV8313 or DRV8316 can be implemented with or without Hall sensors. Since the actual control algorithm is implemented on the MCU, you can choose to implement sensored or sensorless control algorithms such as trapezoidal or FOC. The DRV8316 has built in current sense amplifiers, whereas the DRV8313 will need external sense resistors connected to the PGNDx pins in order to implement sensorless control.

    2. In the image you shared, any of these motor drivers can be controlled through sensored or sensorless algorithms. Since the control signal itself comes from the MCU, the implementation of the control algorithm is up to your design parameters. However, some devices such as the DRV8316 or 8317 make sensorless control easier by providing integrated current sense circuits in the device, whereas other devices such as the DRV8300 will require external components to accomplish current sensing.

    3. You are correct. Besides power/performance metrics, the DRV8313 requires a commutation algorithm to be implemented on an external MCU and communicated to the driver. The DRV10974 automatically implements the commutation algorithm within the device, but you have the ability to control features such as motor speed from an external MCU. Additionally, the DRV10974 already implements sensorless control, so there is no need for external sense circuits or Hall sensors.

    Please let me know if this information answers your questions.

    Best,

    Davis

  • Hi Davis,

    If DRV8316 is implemented with a Hall sensor, how should Hall be connected to the circuit? Connected to MCU? Do I have to write my own algorithm for MCU? Can I use an integrated FOC algorithm mcu?

    I see that DRV8316xEVM is paired with LAUNCHXL-F280049C, while F280049C is internally integrated with FOC algorithm, so what is the impact of connecting a Hall sensor on this?

  • Hi Anna,

    If you want to connect the Hall Sensors, I believe they should be connected to available GPIO pins on your MCU. The DRV8316xEVM board comes with Hall sensor connection ports for each of the phases of the motor and connects directly with the LAUNCHXL-F280049C as you mentioned. 

    The EVM board is most useful for evaluating which conditions and parameters suit your application best. Please refer to this user manual for more information on running the EVM: https://www.ti.com/lit/ug/slvubz9b/slvubz9b.pdf?ts=1685714007418&ref_url=https%253A%252F%252Fwww.ti.com%252Ftool%252FDRV8316REVM. Section 6 in particular includes steps needed to download the EVM GUI which already implements the desired control algorithm and allows for quick parameter experimentation during testing. Connecting the Hall sensors to the EVM while working with this GUI is prerequisite for use of sensored control methods.

    For more in depth software development, this SDK includes the tools needed to program sensored FOC control: https://www.ti.com/tool/C2000WARE-MOTORCONTROL-SDK?keyMatch=C2000%20MOTOR%20CONTROL%20SDK. It is designed for the C2000 MCU which comes on the LAUNCHXL-F280049C. I believe Code Composer Studio IDE is required as well.

    Please let me know if you have further questions on motor control algorithms or EVM hardware setup.

    Best,

    Davis

  • Hi Anna,

    Please mark this thread as "resolved" if this answered your question. I am going to move the thread to closed for now.

    Best,

    Davis