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.

MCF8316A: Migrating from DRV10987

Part Number: MCF8316A
Other Parts Discussed in Thread: DRV10987, , , MCF8315A

I have an existing design using a DRV10987.  I want to upgrade to the MCF8316A, and use the same motor.  I remember it was painful to figure out how to program all configuration parameters on the DRV10897. Is there a cheat sheet for how to use the configuration parameters from the DRV10987 to program the MCF8316A?

  • Hi David,

    DRV10987 and MCF8316A are completely different devices in terms of design, pinouts, register mapping etc. Unfortunately, we don't have a tool to convert DRV10987 configurations to MCF8316A. However, we have MCF8316A GUI through which tuning can be done quickly using the MCF8316AEVM. Link to download the GUI can be found in Datasheet (page-1). In the GUI homepage, click "Start Guided tuning" and you will see step by step guide on how to tune the motor. Please let me know if you see any issues.

    Regards,

    Vishnu

  • Hi Vishnu,

    We go the eval board.  My coworker has been beating his head against a wall for a couple of days now.  The guided tuning doesn't work and the GUI gives no indications what it is doing or what is wrong.  Sometimes we can get the motor to spin slowly for a few seconds before it stops.  The user guide is very sparse on information.

  • David,

    Can you point us to the exact step in the guided tuning where you are stuck at?

    Please make sure the "Auto read motor status" and "Auto read fault status are disabled". 

    Regards,

    Vishnu

  • Hi Vishnu,

    "disabled"?  I have those enabled so I get some idea of what is happening.

    I get stuck in "testing for successful start-up in closed loop".  Pressing the "clear" button does not seem to do anything.  I can't get the motor status back to "idle".

  • Hi David,

    Device I2C communication fails and will get stuck in unknown state when the registers are constantly read during motor operation. This is fixed in MCF8315A. Please do not read any registers during motor operation.

    Regards,

    Vishnu

  • Hi Vishnu,

    OK, we aren't auto updating the registers anymore.  We had a set of register settings that were working pretty well yesterday.  Today if we load the same file of register settings, the motor does not run if we give it a speed command.  If we hit "read all registers" to get an update of the motor status, if shows it is in idle.  What would make the controller ignore the speed command?

  • Can you make sure the jumper and switch settings are as mentioned in the EVM Users Guide? Are you commanding speed over I2C or SPEED pin (Analog/PWM)? When you click "Read all registers" does the GUI display "Read xx registers" after few seconds at the bottom left of the GUI? This is to confirm if the I2C communication is intact.