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.

MCF8316AEVM: [Own design] MCF8316AEVM connection's problem with GUI ver 1.1.8

Part Number: MCF8316AEVM
Other Parts Discussed in Thread: MSP430FR2355

Hi Team,

I have a fan design project, we are using TI's MCF8316AVRGFR driver and MCU MSP430FR2355. So we are designing our MCF8316AEVM board with a GUI connection for the first design version.

I attached 2 files of the principle we designed below:


Test results with the driver are pretty good when there are no problems.

Input voltage VM: 15V

Output VBK: 5V

AVDD: 3.3V

DVDD: 1.5V

FAULT: 3.4V = No-Fault

I have problems connecting to GUI 1.1.8. With the principle of the circuit, I designed as 2 pictures above.

I have the following connection:

R12=logic high BRAKE=ON

R13=logic high DIR=ABC

R11=logic high DRVOFF=ON

3V3COM=3.3V, VR1 rotate for output to 0V.

When I connect to GUI 1.1.8 it shows the following image.


Hardware connected, 32 registers read. But my motor is not spinning yet.


TI can help me check if I am wrong in hardware or software.
How to know if MCU has I2C communication with MCF8316?

How to set up the Motor's parameter in order to display " Motor status"? Are there any other parameters we need to set? Thanks!

When I don't connect USB wire from the PC to the board, the LED4 bypass pin "FAULT" is displayed. Could you explain more clearly them?

Regards,

N.T. Vuong

  • Hi N.T. Vuong,

    Thanks for your question on the Motor Drives E2E Forum. 

    It may take some time to look over this but I will aim to provide an answer on this early next week!

    Best,

    Robert

  • Hi Robert,

    I look forward to hearing from you!

  • Hi Robert,

    Thanks for your response to your question. We have the solution to the problem. We used the firmware project for the MSP430FR2355 on the MCF8316AEVM from Eric Chen: e2e.ti.com/.../MCF8316AEVM_5F00_MSP430FR2355_5F00_Firmware.zip

    So we connect successfully, and the VM_Voltage 15V is displayed on the "Motor Status". We follow step by step the MCF8316AEVM Tunning Guide However, when we set up the I2C Speed Control, we have another problem with our BLDC Motor, the motor parameters (MPET) is not active after we active I2C speed control, and the Fault Status is not active during we set up. So our motor didn't spin.

    We hope your team will provide answers to your problems. And we have two other questions:

    1. We suspect the firmware project we attached is incomplete, so could you help us check your firmware project above, especially the I2C connection's code?

    2. When we connect 3 phases of our BLDC motor for 3 phase-output of the EVM board, we didn't care about the phase's order. So could you check with us about the phase connection with the EVM board?

    I look forward to hearing from your team!

    Regards,

    N.T. Vuong

  • Hi N.T. Vuong,

    We are glad that you found that resource on our other E2E post. I will look to compile answers to your questions early next week.

    Best,

    Robert

  • Hi N.T. Vuong,

    I see that you were able to communicate with the GUI so it is my belief that the MSP430 firmware is working correctly. The I2C code should also be fine, otherwise the GUI would give an error immediately when the auto read buttons are enables.

    It seem like you may be running into errors when running MPET. I suggest that you turn off the auto-read motor status and fault buttons and then try to run MPET. If the fault LED comes on, then toggle on and off the auto-read buttons to read the fault.

    For your second question, does your motor have a directional load? If so, you would need to ensure that the phase wires are connected in the right order that spins your motor in the desired direction. This shouldn't impact MPET. However, it can affect the speed loop Kp/Ki values that MPET measures.

    Best,

    Robert

  • Hi N.T. Vuong,

    If there are no more questions, could you please help mark this thread as resolved?

    I will close the thread for now, but feel free to open it again if you have an additional question around this topic.

     

    Best,

    Robert

  • Hi Robert,

    Thank you!