• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 81 subscribers
  • Views 234 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

C2000WARE-MOTORCONTROL-SDK: Motor control lab guide is03_hardware_test issues

johan olofsson
Prodigy 80 points
Part Number: C2000WARE-MOTORCONTROL-SDK
Other Parts Discussed in Thread: LAUNCHXL-F280049C, BOOSTXL-DRV8320RS

I have followed the instruction for laboration 3. But first a picture of my setup just for the record:

LaunchXL-F280049C, BoostXL-DRV8320RS, Teknic M2310P motor. Supply voltage 36V

Here I have added the 3a code to connect the inputs of the PWMDAC. (Function call is spelled wrong in the guide!)

First problem, I do not know at what pin's these PWMDAC1-4 signals are generated?


Anyhow I started the code and just Measured the phase voltage signals to see what where going on. When the motor was disconnected from the phases.
Running the code without setting the flagEnableSys, this is what happens. All phases except the yellow (phase A) idle high, as i think de default should..
Phase A = ch1 (yellow), Phase B= Ch2 (Green), Hase C= Ch3 (Blue). I tried to replace the hardware circuit boards to another pair, and the same problem, so the only I have not changed is the code. 

What could the issue be causing this? It seem that the phase A control signals is not generated by PWM hardware.. Looked at the gatesignals and the same problem there..

  • 0
    TI__Guru** 109730 points

    Sorry for confusing you in the lab guide, the PWMDAC can't be supported on the LaunchXL-F280049C board directly, it's only supported by the high voltage kit. You have to add a RC filter on the related PWM pins by manual as below or you might just ignore this step for using PWMDAC in the labs.

  • 0 in reply to Yanming Luo
    Prodigy 80 points

    Ok, thanks for that information. Anyhow there is still the main problem that phase A is not working properly.

  • 0 in reply to johan olofsson
    TI__Guru** 109730 points
    johan olofsson said:
    Anyhow there is still the main problem that phase A is not working properly.

    Could you please have a detailed description of this?

    Lab03 is an open loop control with v/f method, you only need to set the right values below. This lab is just for hardware verification, can't run the motor at a high speed or with a heavy load.

    #define USER_MOTOR_FREQ_LOW_HZ (20.0) // Hz
    #define USER_MOTOR_FREQ_HIGH_HZ (400.0) // Hz
    #define USER_MOTOR_VOLT_MIN_V (4.0) // Volt
    #define USER_MOTOR_VOLT_MAX_V (24.0) // Volt

  • 0 in reply to Yanming Luo
    Prodigy 80 points

    #define USER_MOTOR_FREQ_LOW_HZ (20.0) // Hz
    #define USER_MOTOR_FREQ_HIGH_HZ (400.0) // Hz
    #define USER_MOTOR_VOLT_MIN_V (4.0) // Volt
    #define USER_MOTOR_VOLT_MAX_V (24.0) // Volt

    Well anyhow I do not have the motor connected to start with, so loading is not an issue. What bothers me due, is that phase A is not ideling as the other phases. Is this correct?

  • 0 in reply to johan olofsson
    TI__Guru** 109730 points

    What do you mean "phase A is not working properly" and "phase A is not ideling as the other phases"? What signals are you monitoring?

  • 0 in reply to Yanming Luo
    Prodigy 80 points

    Anyhow I started the code and just Measured the phase voltage signals to see what where going on. When the motor was disconnected from the phases.
    Running the code without setting the flagEnableSys, this is what happens. All phases except the yellow (phase A) idle high, as i think de default should..
    Phase A = ch1 (yellow), Phase B= Ch2 (Green), Hase C= Ch3 (Blue). I tried to replace the hardware circuit boards to another pair, and the same problem, so the only I have not changed is the code. 

    What could the issue be causing this? It seem that the phase A control signals is not generated by PWM hardware.. Looked at the gatesignals and the same problem there..

  • 0 in reply to johan olofsson
    TI__Guru** 109730 points

    Please use lab02 first to check if the PWM outputs are correct on the input of the boostpack, and the voltage on the three phases should be the same in this lab without connecting the motor.

  • 0 in reply to Yanming Luo
    Prodigy 80 points

    Hi, I do all laboration in order. I have done that one and passed it. There all 3 phases generates 50% pwm. Think I actually        mentioned that lab2 in another thread here that you answered.

  • 0 in reply to johan olofsson
    TI__Guru** 109730 points

    Measure the voltage with a multimeter on motor connector, all of the three phase voltage should be equal to half of dc bus voltage.

    Or monitor the output on motor connector, it should be 50% PWM also with dc bus voltage amplitude.

    If not as above, that means the inverter should be not good if you connect the boosxt board to lauchxl board correctly and don't change the example lab.

  • 0 in reply to Yanming Luo
    Prodigy 80 points

    No it's more likely a software issue. I can run the lab 2 without problem, all gate signals works as they should do. But in lab 3 this issue occur. Have tried again running lab 2, all is fine..

  • 0 in reply to johan olofsson
    TI__Guru** 109730 points

    The voltage will be different between the three phases on the connector, and the PWM duty will be variable from 0% to 100%. You can connect the motor to the inverter board if you want to run the lab03 without any changes on the example lab, and make sure that the output  on the motor connector in lab02 as mentioned above.