• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 46 subscribers
  • Views 400 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.

Original question:

ADC12DJ3200EVM: ADCxxDJxx00 GUI not connecting to device

ADC12DJ3200EVM: Cannot connect the GUI software anymore

Sai Mohan Kilambi
Prodigy 210 points
Part Number: ADC12DJ3200EVM

Hi,

I have the ADC12DJ3200EVM Rev A eval board and I have been using it for quite some time now with TSW14J57. I am not sure what happened but now the GUI software doesnt connect to the board anymore. I have the board connected to the 5V supply and the current limit is set to 5 Amps which is plenty. I just get an FTDI Device not connected error message 

  • 0
    Prodigy 210 points

    Now i am getting this after i uninstalled and reinstalled. I installed 2014 and 2018 labview runtime but it still gives me this.

  • 0 in reply to Sai Mohan Kilambi
    Prodigy 210 points
    I was able to solve this. I uninstalled all NI related drivers by first installing the Labview runtime from NI website. When you install this, it install a proper way to uninstall NI components from system menu in windows. After I uninstalled everything, I did a fresh install for the ADC software and it recognized that Labview runtime also needs to be installed. I did this and it started to work again.

    Just a word of advice. When you uninstall ADC related software, it should also uninstalled any Labview runtime dependencies. I wasted two days trying to fix this only because this was not happening.
  • 0 in reply to Sai Mohan Kilambi
    TI__Mastermind 43930 points
    Hello Sai
    Thanks for following up with the details of how you resolved this.
    I will share the issue related to uninstalling the ADC GUI software and related runtime dependencies with our software team.
    Best regards,
    Jim B