• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 356 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.

MCF8316A: Questions for Motor Studio...

Peter Tseng
Mastermind 6260 points
Part Number: MCF8316A


Hi Team,

I have questions about Motor Studio and MCF8316A.

1. From the website, the latest version of Motor Studio is V0.1.12, however, from the "About" of the installed program on PC, the version is still V0.1.9.

May I have your help to check this?

2. How to change the peak current value to a specific value, not a percentage?

Thanks.

  • 0
    TI__Genius 9220 points

    Hi Peter,

    Thanks for reporting the issues with Motor Studio.

    1. The version mismatch is simply a typo in the About window of the GUI. The v0.1.12 installer is the latest release version. We'll make sure future releases have correct information in the About page.

    2. This is a known issue for MCF8316A, the drop down menu options for various current limits are not displayed correctly due to error in the register map in the GUI. We've worked with our GUI developer to fix this in our internal builds and the next release will contain correct register map for the MCF8316A. In the current GUI, you will need to correlate the index of the selected current limit in the drop down to the current values listed in the register description in the datasheet.

      The Rated Peak Current input field in the quick spin page directly maps to the FAULT_CONFIG1.[ILIMIT] register. So for example:
      1. Selecting 5% means the register value is set to 0x0, which corresponds to 0.125 A in the datasheet
      2. Selecting 100% means the register value is set to 0xF, which corresponds to 8 A in the datasheet

    Apologies for the inconvenience this has caused. We are working to release and update to the GUI as soon as possible that resolves these issues.

    Regards,
    Eric C.