• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 388 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.

MCT8316A: How to buy MCT8316AT (hardware config variant)?

Mitcham Tuell
Prodigy 150 points
Part Number: MCT8316A
Other Parts Discussed in Thread: MCF8316A,

Hello,

I've been using an MCF8316A for control of a custom BLDC motor. I have been encountering lots of frustrating problems using the GUI where the part will stop communicating its algorithm state and not respond to input, sometimes continuing to spin the motor or burn current without spinning. Apparently the only way to fix these states is to cycle power to the part (why isn't there a reset pin!?). 

I'm potentially interested in the hardware configurable MCT8316AT as a fallback option that will hopefully "just work" once I set the resistors. On looking at the product page for the part or the dev kit, it's not obvious how to order the "-T" variant for hardware config vs the "-V" variant for I2C. They appear to be lumped together into just an MCT8316A page with no selection of which variant. How can I buy a dev kit and some samples of MCT8316AT?

Thanks,

Mitcham

  • 0
    TI__Mastermind 18981 points

    Hi Mitcham, 

    Let me follow up with the team on this and try to get you a response by early next week 

    Best Regards, 
    Andrew 

  • 0
    TI__Mastermind 24415 points

    Mitcham,

    We understand the frustration. This is a new product and we have been working hard to provide the best user experience. If you are using MCF8316A EVM, I would recommend you to not "Auto read" registers while the motor is spinning. Auto reading registers consumes more bandwidth and loses I2C communication. This is a known errata and we will be fixing this problem in our next revision.  

    Unfortunately, we haven't released PMCT8316A1T to the market yet. Let me check with our marketing team and get back to you.

    Regards,

    Vishnu

  • 0 in reply to Vishnu Balaraj
    Prodigy 150 points

    Vishnu,

    From my testing it looks like the GUI completely gives up after a single I2C NAK, which is a pretty questionable software design. The deeper concern to me is whether the bad I2C read and other confusing behaviors come from the GUI side or the chip side. Failures on the chip side are worrying since I'm evaluating this part for a very high reliability medical application.

    We have also now seen two seemingly random failures of PMCF8316A parts where they will be working fine, then one day just don't start up. No motor drive, no I2C comms. I don't have any explanation for this related to my carrier board, leaving me to think the part is randomly failing or maybe the overcurrent protections are failing and allowing the part to overheat.

    Please let me know when the MCT8316AT will be available.

  • 0 in reply to Mitcham Tuell
    TI__Mastermind 24415 points

    Mitcham,

    Does the GUI lose I2C communication even after reading single register while the motor is spinning? We have seen this issue show up when we auto-read registers but I do agree that this issue can show up even after reducing the frequency of I2C reads but the probability of occurrence is much lower. We will have the I2C NACK issue fixed in the Rev B version of this device. 

    Regards,

    Vishnu

  • 0 in reply to Vishnu Balaraj
    TI__Mastermind 26046 points

    Hi Mitcham,

    Do you need assistance on this still? If not, please mark as "Resolved".

    Thanks,
    Aaron