• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 82 subscribers
  • Views 583 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.

TMDSCNCD28379D: communications drop-out with TMDSCNCD28379D control card

Imre Kiss1
Intellectual 510 points
Part Number: TMDSCNCD28379D
Other Parts Discussed in Thread: LAUNCHXL-F28379D, CONTROLSUITE, TMDSHSECDOCK

We are having trouble running the TMDSCNCD28379Dcontrol card.  USB communications is lost very quickly after the start of program execution.  This happens for any program we load.  We have four copies of the card and no luck with any of them.  On the other hand, running the same programs on the launch pad LAUNCHXL-F28379D , everything runs perfectly.  We tried all dip switch combinations with no change. (1) are the cards specially susceptible to static and might we have damaged them or (2) are there known communications problems for this card.

 

Thanks,

Imre Kiss

  • 0
    TI__Expert 3795 points

    Hi Imre,

    I have not seen such issues while using control card. I have both the control card and launchpad and both runs fine. Which USB Program are you trying to run?

    Thanks and Regards

    Harshmeet Singh

  • 0 in reply to Harsh Singh
    Intellectual 510 points

    Harshmeet,

    Thanks for the quick response.  The main program I am trying to run is "Sensored Field Oriented Control of 3-Phase Permanent Magnet Synchronous Motors using F2837x"  with associated software "C:\TI\ controlSUITE\development_kits\TMDSIDDK_v2.0\IDDK_PM_Servo_F2837x".  My intent is to convert this to a sensorless application.  I managed to create the running stub on the launchpad by disarming and altering the appropriate trip zone functions and faking AD inputs.  But I cannot port to the control card.  Other simple programs from the examples such as "C:\ti\controlSUITE\device_support\F2837xD\v210\F2837xD_examples_Cpu1\blinky" had similar issues.  Since there are no known card issues, I m beginning to think that unlikely as it may be, we may have damaged the cards through handling.  We have three more copies coming and will open the packages under strict conditions to get to the bottom.

    Thanks,

    Imre

  • 0 in reply to Imre Kiss1
    TI__Guru 57255 points

    Hi Imre,

    Based on experience, disconnection could occur when running a power stage with some of these controlCARDs - and usually under high transient circumstances.  A resolution for this type of behavior for others has been to reduce the value of (or remove) the physically large capacitor that bridges the isolation boundary between the MCU and the on-card emulator. Additionally/Alternatively, using EMI ferrites can improve performance.

    However, it is very strange that the cCARD is disconnecting, even when running a simple example (especially if this example was being run on simple hardware, like a TMDSHSECDOCK).  If this is the case, then like you are, I would suspect damage to the controlCARD.

    Let us know what you find.


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    TI__Expert 3795 points
    Hi Imre,

    Is there any update?

    Thanks and Regards
    Harshmeet
  • 0 in reply to Harsh Singh
    Intellectual 510 points

    Harshmeet

    Thanks for the message.  I was about to update but you beat me to it.  In fact the problem appeared to be a corrupted CCS development environment.  I probably failed to copy something into my local environment and changed some globally.  In any case, the result was an odd behavior.  The communications was sporadic and ADC channels not properly working.  When I triad running the unchanged sample program, it would not behave properly either.  Then going to another computer computer, the sample program ran OK.  I then reinstalled the entire CCS ecosystem on my computer and incrementally rebuilt my application and everything runs just fine.  So in the end it was me.  Sorry for the false alarm and thanks for your help.

    Imre