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.

TIDM-02007: Problem:The motor does not start properly

Part Number: TIDM-02007

Hi Team,

My customer is currently debugging based on TIDM-02007. At present, when testing Level 4, it is found that the motor cannot start normally (it shows that the motor does not move, but there is current, which is similar to motor stall)

In the current test, if the ABI interface is not inserted, the motor can work in the state of “Wait for index ” and rotate at low speed. This shows that the hardware and software are normal.

This can also happen if the UVW is wired incorrectly during my previous tests. However, after the customer changed the UVW wiring, the motor still does not rotate (but there is current).

Due to the current impact of covid-19, I cannot enter the laboratory for testing experiments, so I seek your support. Do you have any comments on this?

Thanks

Jenson

  • Hi

    I'm the customer Jenson mention. Here's some additional info;

    The behavour is that when setting a speed value, the motor just rotate 2-3degrees, then stop with high DC current applied. If I change speed value to a negative, the motor turns in the other direction 2-3degress then stops with DC current. The trailing order of the AB-signals shifts accordingly.

    If I remove the encoder signals and restart the system, the motor rotates fine waiting for the index signal. 

    Is there any breakpoint to set or expression to watch in the code to identify what makes the motor stop in this stall+current state? 

    Or any other tips how to identify what casues this condition (disable control sections in the code or else?)

    Thanks

    Magnus

  • Seems like the rotor position can not be detected by using the encoder. Please make sure that the encoder is connected to the right connector on the LaunchXL, and then check if the outputs of the encoder are right by running the lab with FCL_LEVEL2. The motorVars[0/1].speedRef should be equal to the motorVars[0/1].speedWe, if not, that means the encoder/motor connections are not right, follow the guide to connect the encoder and motor. If the user is using their own motor, make sure that the encoder has the right output on LaunchX and set the right lines in the header file.

  • Thanks for your guidance!

    I've checked motorVars[0/1].speedRef is equal to the motorVars[0/1].speedWe.

    Tested with both your motor and our own. What could be wrong next? 

    Regards

    Magnus 

  • Using your own motor? Or the motor (Teknic_M2310PLN04K) shown in guide?

    Did you check the A, B, I signals with an oscilloscope if these 3 signals are correct? The feedback will be equal to the target speed if A and B signals are correct, but the Index signal can't be verify in this level.

  • Tested with both the Teknic and our own. ABI signals are just fine with oscilloscope. 

    I would like to be able to analyse what state the SW is at when it stop rotate. Do you have any help in what expressions to watch or where to set breakpoints to see where in the code this happens?

  • Which launchXL board are you using? Do you follow the guide to set the switches on the launchXL board?

  • We're using the F280049C. But I just narrowed in the problem a bit more. Until now I've just used one of the BoostXL boards and one motor ("INV1"). To assure that the system wasn't affected by this, I hooked up also INV2 and the second motor. To my surprise INV2 and its motor worked just perfect. But INV1 and its motor still had the same problems as reported above. All jumpers are set according to the guide, using the USB as power supply for 5V and 3V3.

    I've tried to swap BoostXL-boards, motors and LauchXL board but the problems is the same. Do you have any idea what in the code could cause this behavour?

  • You have to check if the counter and status registers for QEP are updated correctly when you try to run the lab with level 2. Seems like there are something wrong on the LaunchXL. I can't repeat your question on the board I had.

  • Thanks for all your guidance and time Yanming! I have tested with three different, brand new LaunchXL, as behaving the same. So something is strange in the SW. QEP counter and registers are all fine at Level 2.

    We don't have time to fault trace this no more, so we'll have to skip this solution. Your assistance has been highly appreciated though!

  • OK. Let's know if you have any further questions when you try this again.