The TI E2E™ design support forums will undergo maintenance from July 11 to July 13. If you need design support during this time, open a new support request with our customer support center.

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.

LAUNCHXL-F28379D: dual_axis_servo_drive example run issues

Part Number: LAUNCHXL-F28379D

Tool/software:

Hi,

I'm using LaunchXL-F28379D and trying the dual_axis_servo_drive example. I'm strictly following the steps described in Dual-Axis Motor Control Using FCL and SFRA On a Single C2000Tm MCU

I have the same hardware as required and had no problems to get the system setup to the stage I was trying the LEVEL 1 build firmware.  On CCS, running from Debug perspective is working fine. I can monitor the variables on "Expressions" and capture the data with "Graph" tool.

However, I can't get the outcome as suggested in the document (PWM channel should output variable duty times but mine are static 0 - obviously not being calculated). The interrupts are all working and their counter updating. I believe the reason might be:

"control state" is always in "stop" (ctrlState: CTRL_STOP)

"run motor" is also in "stop" mode (runMotor: MOTOR_STOP

I tried modify code to force them to "RUN" without success. I also tried disable all error checking without success. There are actually no error flags after I plugged in both BoostXL boards. So, I'm stuck. The document just says Run the program without any mentioning of how to "start the motor" (although for level 1 build there's not actual motor connected, I guess it still needs to be in Run state for other part to work?) 

  • Hi,

    Which SDK version are you using? Please use latest if you're is fairly outdated.

    Can you confirm the ISR is being entered OK (ISR counter variable increasing)? And you say the graphs below are matching- to confirm angle gen and SVGEN are working.

    "control state" is always in "stop" (ctrlState: CTRL_STOP)

    "run motor" is also in "stop" mode (runMotor: MOTOR_STOP

    I think you may need to change one of these variables to enable PWMs. Believe CTRL_RUN needs to be set in expressions.

    Best,

    Kevin