• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 629 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.

MSP-EXP430F5529LP: MSP430 Communication Loss while using BOOSTXL-DRV8320RS Motor Driver Module

Ricardo De La Paz
Prodigy 10 points

Part Number: MSP-EXP430F5529LP
Other Parts Discussed in Thread: BOOSTXL-DRV8320RS, ENERGIA

Tool/software:

Hello everyone,

I'm experiencing a communication loss issue between my MSP430 microcontroller, the BOOSTXL-DRV8320RS motor driver module, and the COM port on my computer. The communication works fine initially, but when I try to jump between phases (jumping 2 or more instead of sequentially), the COMS dies on the MSP430, and I'm unable to regain connection until I power cycle the system.

I've checked the power supply, noise, and glitches on the communication lines, but I'm still unable to resolve the issue.

Here are the details of my setup:

  • MSP430 microcontroller
  • BOOSTXL-DRV8320RS motor driver module
  • 3-phase motor
  • Power supply: 45V

I've tried the following troubleshooting steps:

  • Checked the power supply and noise on the communication lines
  • Verified the communication protocol and baud rate

I'd appreciate any help or guidance on resolving this issue. Has anyone else experienced similar problems? Any insight on what may be happening and any potential solutions?

  • 0
    TI__Mastermind 25427 points
    Ricardo De La Paz said:
    I've checked the power supply, noise, and glitches on the communication lines, but I'm still unable to resolve the issue.

    Any large noise seen on UART?

    Or can you confirm which operation you done to motor or MSP430 system will cause COM port disconnection?

    Ricardo De La Paz said:
    I've tried the following troubleshooting steps:

    Can you confirm whether you can keep debug connected and try to re-produce the issue, directly check system status in debug mode.

    Or you need to monitor MSP430 status using GPIO toggle in freerun mode.

  • 0 in reply to Helic Chi
    Prodigy 10 points
    Helic Chi said:
    can you confirm which operation you done to motor or MSP430 system will cause COM port disconnection?

    When operating the motor I cycle through phases 1-6 sequentially to go one directions and 6-1 to go the other. There are cases where I will need to jump 2 phases when switching directions. In these cases when jumping 2 or more phases it will intermittently drop the COM port and stop communicating with the rest of the system not allowing me to further control it. 

     

    Helic Chi said:
    Can you confirm whether you can keep debug connected and try to re-produce the issue, directly check system status in debug mode.

    I will attempt this now and see if I can get more data around the point of failure.

  • 0 in reply to Ricardo De La Paz
    TI__Mastermind 25427 points
    Ricardo De La Paz said:
    When operating the motor I cycle through phases 1-6 sequentially to go one directions and 6-1 to go the other. There are cases where I will need to jump 2 phases when switching directions. In these cases when jumping 2 or more phases it will intermittently drop the COM port and stop communicating with the rest of the system not allowing me to further control it. 

    In this condition, usually the current or voltage maybe changed a lot.

    Have you ever try to stop motor and then start the another direction?

    See if using a gentler control method will still cause disconnection.

    Then find out the difference between current and voltage and optimize control software flow.

    Ricardo De La Paz said:
    I will attempt this now and see if I can get more data around the point of failure.

    Got it.

  • 0 in reply to Helic Chi
    Prodigy 10 points

    I changed the control methods but and haven't seen any failures yet but I'm still curious why this happens. I do know that I lose both COM ports when this occurs. Would it be beneficial for me to use the debugger still?

     

    If so, there are a few of the debugger tools available (IAR or CCS software environments, MSP430Flasher, Elprotronic's FET-Pro430, mspgcc, and Energia). Which do you recommend me use and are there any useful "how to" videos for them. I'm new to the MSP430 troubleshooting world so any direction helps. 

  • 0 in reply to Ricardo De La Paz
    TI__Mastermind 25427 points
    Ricardo De La Paz said:
    Would it be beneficial for me to use the debugger still?

    The reason we use UART to debug motor application is that large current will influence debug interface easily.

    It better to use UART or RS485 to debug a motor application.

    Inappropriate operation will indeed cause the noise to increase and the chip to disconnect, it's common.

    Ricardo De La Paz said:
    If so, there are a few of the debugger tools available (IAR or CCS software environments, MSP430Flasher, Elprotronic's FET-Pro430, mspgcc, and Energia). Which do you recommend me use and are there any useful "how to" videos for them. I'm new to the MSP430 troubleshooting world so any direction helps. 

    The first thing is to make sure you control the motor in a proper way.

    Secondly, it is correct to choose UART for debugging.

    Further anti-interference debugging is to use RS485(UART+transceiver)

**Attention** This is a public forum