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.

DRV8316REVM: About the he motor identification algorithm

Expert 1065 points
Part Number: DRV8316REVM
Other Parts Discussed in Thread: DRV8316

Tool/software:

Hi team,

I am using the instaSPIN-FOC GUI for the motor identification function with two motors. One has 7 pole pairs, and when the GUI runs the motor identification algorithm, the motor power consumption reaches 20W and overheats severely. Another motor with 8 pole pairs,the motor identification algorithm runs successfully and the GUI shows "motor identified", but when I click RUN, the motor only vibrates once and does not spin.

Does the motor identification algorithm have specific requirements for the parameters of the motor?The following image and video are the motor with PP of 8.

  • Hi Suy,

    I apologize for the delay. I will look into the issue and get back to you!

    Thanks,

    Joseph

  • Hi Suy,

    It seems like your motor is being identified correctly as it populates the pole pair value correctly as well as the other motor paramaters. 

    Would you be able to gather some waveforms of INHx, INLx, OUTx, and nFAULT during when you are trying to spin the motor with the GUI?

    Can you go to the SPI tab of the GUI and read the registers? I'm wondering if there is a fault somewhere that needs to be addressed?

    Thanks,

    Joseph

  • Hi Joseph,

     Did the pole pairs value is entered manually?I filled the value when i run the identification function.

     Now i run the  identification function again then disconnect the GUI and reconnected,the motor can spin well,but i found that the speed of setting is 10Hz,i use the tachometer measuring the actual speed is 750RPM.When i change to another motor the identified sucessfully but it is very hot and not spinning.

    Another two questions:

    1,When the motor is be identified correctly,once power off the motor must be  identified  again,can the motor be driven to spin directly power on again?

    2,When the motor stops spinning under external force, how can it respin without power off?

    Theshows registersregistersregisters registers values

    May I ask if DRV8316 supports the input of ABI encoder? I want to control the motor speed through the encoder. Is the motor recognition algorithm with the GUI for controlling motors with encoder applicable to this?

    How to use our own FPGA/MCU to control the operation of the DRV8316 drivering the motor with encoder?

  • Hi Suy,

    It is good that you are getting functionality when you power cycle the board at least. I'm not sure why your other motor is heating up.

    1. I think the motor must be identified again if power is reset. 

    2. You can try to write the CLR_FLT bit to the GUI. I suspect maybe there is a latched fault that prevents the device from spinning, which clears when you reset power to the board, but maybe the CLR_FLT bit can be used instead of resetting power.

    3. For custom MCU inputs, you can review the EVM user guide and design files in order to locate the connections you need to supply from MCU. (inputs, hall signals, etc) also make sure Hall GND and MCU board GND are connected.

    I have connected custom MCU code to our EVM's this way using jumper wires to the launch pad connections that are necessary, this may be the solution for your situation.

    Thank you,

    Joseph

  • Hi Joseph,

      I got the 1th and 2nd. for the 3th can you share the MCU code with me?

      Additionally the speed configured via the GUI differs from the speed measured by the speedometer. What are the potential causes of this discrepancy? 

  • Hi Suy,

    I tested custom MCU code for customer and cannot share the code publicly. You would have to write your own code to test.

    You should be able to use jumper wires from your MCU to the EVM in order to control the EVM with your own code.

    The motor speed on the GUI should be calculated using feedback from the motor's electrical cycles so there may potentially be some difference.

    Thank you,

    Joseph