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.

ADC12J2700EVM - FTDI settings and driver

Other Parts Discussed in Thread: ADC12J2700, ADC12J2700EVM

I've tried following the steps in the documentation for the ADC12J2700 EVM and the TSW14J56 EVM. After powering up both boards and starting the ADC12J2700 GUI, I get an error "FTDI Device not connected properly!"

I've tried reinstalling the GUI software, as well as renaming the description of the device to "ADC12J2700EVM" using FT_PROG, and nothing seems to resolve it. Can anyone verify what the "product description name" field should be, and what should show up in the device manager for this device?

Thanks in advance!

  • Never mind, I think it's resolved now. Renaming the description to "ADC12J2700_A0" (as seen in the "FTDI cfg.ini" file in the ADC GUI directory) and reconnecting the device / letting the FTDI drivers reinstall seems to have done the trick.
  • Hi Isaac

    Let me know if you have any problems with board functionality now that the GUI is able to communicate with the board. If there are functional problems the board may be the earlier revision that requires an earlier version of the GUI. If that is the case, you can use this GUI installer here:

    /cfs-file/__key/communityserver-discussions-components-files/73/8132.ADC12J2700EVM-GUI-E2-Installer.zip

    You will need to change the board description back to ADC12J2700_E2 for it to be recognized by the earlier revision GUI.

    Let me know how it goes.

    Best regards,

    Jim B

  • Jim-
    Sure enough, I did have some functional issues getting the TSW and the ADC boards communicating correctly. I renamed the FTDI chip description back to "ADC12J2700_E2" and used the older version of the GUI that you supplied and it worked great.

    The only minor issue I still have is that the "TEMP" LED on the ADC board stays lit. The temp sensor values are all reading "127", and we're in a temperature controlled environment, so I think it's more likely to be a stuck signal than an actual temperature issue. It's not affecting the functionality in any way so I'm particularly not worried, it's just a slight annoyance.

    Thanks for all the help!

    Isaac

  • Hi Isaac

    I'm glad it's working now.

    There is a design issue with that earlier revision board that prevents the data interface between the FTDI chip and the temperature sensor chip from working.

    The temperature sensor LED will always be illuminated, but it doesn't indicate anything is wrong.

    The newer revision board has a fix which enables the temperature sensor and related circuitry to work properly.

    Best regards,

    Jim B