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.

ADS1247EVM: Establish communication ADS1247EVM to ADCPro

Part Number: ADS1247EVM

Hi again,

thanks to Bob Benjamin, I was able to install ADCPro and the correct plugin for my ADS1247 evaluationboard. The board is recognised by my operating system (WIN10), but unfortunately communication cannot be established. Once I select my EVM board in the software, an error message pops up: Error loading Front Panel. See "Current Plugin Errors.txt". 'FILEPATH'. The file only includes this text line: 'Bad VIs in ads1247evmPanel'.

Maybe this is helpful aswell: when I power up the MMB3 board, which is connected to the EVM board a couple of this appear on the display:

First: BRD TST, after pressing the control stick it says LCD TST and afterwards every displayelement goes high. After pressing the controler again PRESSUP appears. When moving the control stick in any direction the corresponding arrow appears, but nothing else happens until the controller ist pressed again. Then PRESSED appears, then DAC, then 2.5V appears and the LED to the left of the display goes on, then 4.5V. Afterwards the LED goes off and the display says NODEV, then 96, then HRD OH and finally FAIL and nothing happens except, when resetting the Board.

I'm looking forward to any reply. Many thanks in advance :)

Best regards, Dominik

  • Hi Dominik,

    ADCPro was designed to work with XP/Win7 and has not been fully tested to work with Win10.  I also use Win10 and have gotten ADCPro to work with some plugins such as the ADS1247.  I can see a number of possible reasons why you might see an error following installation.  ADCPro and the plugin installation requires Adminstrator rights for the install.  I'm unsure why you are seeing a FILEPATH error.  If you attempted to run the installer from the zip, I would highly recommend that you unzip (extract) the file first then run the installer.  The plugin should have installed in directory:

    Program Files (x86)\ADCPro\plugins\evm\ADS1247

    In the folder is a file called 'installLog.txt.  Can you send me that file when you reply to this post?

    The MMB3 uses special driver for the TUSB3410 to create a virtual COM port in the USB enumeration.  The MMB3 should not be connected to the USB when the driver is installed as a part of the plugin installation.  Win10 may need a different driver installation as I'm not sure the TUSB3410 drivers were signed.  You can download more recent driver from the following link:

    http://www.ti.com/lit/zip/sllc428

    The MMB3 you have is loaded with the test firmware used in production testing.  Each EVM used on the MMB3 has it's own version of firmware.  When the plugin starts there is a search for the correct COM port used for the MMB3.  If the port cannot be found there will be an attempt to download the firmware required for communication.  If you know the correct COM port you can manually select the proper port for communication.  The firmware download process will start and you will need to follow the screen prompts in the GUI for proper installation.

    If you did not install ADCPro with Administrator rights, you will need to uninstall/install ADCPro.  Next steps would be to make sure you are using Administrator rights and then uninstall/reinstall the plugin making sure the MMB3 is not connected and ADCPro is not running.  Install the most recent driver for the TUSB3410 used on the MMB3.  Plugin in the MMB3 and make sure that it is properly recognized by the OS (and check which COM port is assigned in Device Manager).  Start ADCPro, and load the plugin.  You should see something like is shown above with the firmware installation process starting.

    Best regards,

    Bob B

  • Hi Bob, 

    thanks for your response again! First I hav to mention that I've made a typo... I'm running WIN7 not WIN10...

    Anyways, I followed your instructions: uninstalled ADCPro, reinstalled it with admin rights, then installed the plug in and the latest driver for the MMB3.

    When connected to my computer, it is recognised by the OS at COM port 20...but for some reason it still does not work for me...

    The install log looks like this:

    '
    Log started 02/19/2019 at 07:58:36
    Preferred installation mode : win32
    Trying to init installer in mode win32
    Mode win32 successfully initialized
    [07:58:39] ---INITIALIZATION ACTIONS---
    [07:58:39] Logging system information to installation log file to assist with troubleshooting installation issues.
    If you encounter an issue during installation, please email this log file with a discription of the problem to pa_deltasigma_apps@ti.com.
    [07:58:39] Operating System: Windows 7 unknown Service Pack 1 (Version #: 6.1)
    [07:58:39] OS is 64-bits
    [07:58:39] System Locale: de
    [07:58:39] Detected an active Windows antivirus program...
    [07:58:39] Detected an active firewall program...
    [07:58:39] UAC Enabled: 1
    [07:58:39] Installer is running as administrator: 1
    [07:58:39] The installation directory is located at: C:\Program Files (x86)\ADCPro\plugins\evm\ADS1247
    [07:58:39] Free disk space = 15571248 KB (11309 KB required).
    [07:58:39] ---PRE-INSTALLATION ACTIONS---
    Preparing to Install
    [07:58:44] ---READY TO INSTALL ACTIONS---
    Preparing to Install
    Directory already exists: D:\Users\Dominik\AppData\Local\Temp\ADS1247
    Unpacking files
    Unpacking D:\Users\Dominik\AppData\Local\Temp\ADS1247\TI License.pdf
    Unpacking D:\Users\Dominik\AppData\Local\Temp\ADS1247\ADS1247EVM-PDK-SW_2.0.0_manifest.html
    Unpacking D:\Users\Dominik\AppData\Local\Temp\ADS1247\ads1247-adcproplugin-2.0.0.exe
    [07:58:45] ---POST-INSTALLATION ACTIONS---
    Launching installer...
    Executing D:\Users\Dominik\AppData\Local\Temp\ADS1247\ads1247-adcproplugin-2.0.0.exe
    Script exit code: 0

    Script output:

    Script stderr:

    Installation completed
    Log finished 02/19/2019 at 07:59:05
    [07:59:14] ---FINAL PAGE ACTIONS---
    '

    When loading the ADS1247EVM i got the same error message as described before..

    Error log file in cludes these lines:

    '
    Error Code 5015: libadcpro.lvlib:ErrorLoad_Main.vi<ERR>
    Error Loading Front Panel
    See "Current Plugin Errors.txt" for more.


    <b>Complete call chain:</b>
    libadcpro.lvlib:ErrorLoad_Main.vi
    libadcpro.lvlib:Plugin.lvclass:loadPanelVI.vi
    libadcpro.lvlib:Plugin.lvclass:init.vi
    libadcpro.lvlib:SignalPlugin.lvclass:init.vi
    libadcpro.lvlib:EVMPlugin.lvclass:init.vi
    ads1247evm.lvlib:ads1247evm.lvclass:ads1247evmFactory.vi
    libadcpro.lvlib:Plugin.lvclass:createWithFactory.vi
    libadcpro.lvlib:Plugin.lvclass:loadFromFolder.vi
    Shell - Main.vi 19.02.2019:08:13:06 Mitteleuropäische Zeit
    Error Code 5015: libadcpro.lvlib:ErrorLoad_Main.vi<ERR>
    Error Loading Front Panel
    See "Current Plugin Errors.txt" for more.


    <b>Complete call chain:</b>
    libadcpro.lvlib:ErrorLoad_Main.vi
    libadcpro.lvlib:Plugin.lvclass:loadPanelVI.vi
    libadcpro.lvlib:Plugin.lvclass:init.vi
    libadcpro.lvlib:SignalPlugin.lvclass:init.vi
    libadcpro.lvlib:EVMPlugin.lvclass:init.vi
    ads1247evm.lvlib:ads1247evm.lvclass:ads1247evmFactory.vi
    libadcpro.lvlib:Plugin.lvclass:createWithFactory.vi
    libadcpro.lvlib:Plugin.lvclass:loadFromFolder.vi
    Shell - Main.vi 19.02.2019:08:21:09 Mitteleuropäische Zeit
    '

    and the Current Plugin Errors file:

    'Bad VIs in ads1247evmPanel'

    I hope I was able to provide you with all the information you needed

    Best regards,

    Dominik

  • Hi Dominik,

    I must say I'm very stumped. It seems like the program is not finding the files or that they may be corrupted. I used the same download as you, so I don't think there is a file corruption. We can try to narrow things down a bit by loading one of the other standard plugins, such as File Reader, or TripleGen. That would at least tell us if it is a main application issue or something specific to the plugin.

    I recently had a weird issue with another customer (different software) that acted in a way where the program would crash at a certain point. The issue was related to anti-virus software. They disabled it and reinstalled and now it works as expected. Does the file structure look the same to what I initially showed in my first post for the plugin directory? This may also show a clue.

    I will continue to look into this some more, but I have a hard deadline coming up so it might be a few days before I can really dig into it. There was one thing I did notice and that I should mention is that the program installation is on the C: drive but it appears that the users's folders are on the D: drive based on the installation info. There is a file search path in the adcpro.ini file (under C:\Program Files (x86)\ADCPro). Open the file with a text editor and verify the paths are valid. Also send me the contents of the file as well.

    Best regards,
    Bob B
  • Hi Bob,

    So, the plugin directory looks exactly the same as yours, file names and file sizes are the same. I also checkt the ini file and every path is valid except for the shared directory. That folder does not exist...

    Here's the file's content:

    [ADCPro]
    Version =2.0.1
    Build =4
    PluginsDir =C:\Program Files (x86)\ADCPro\plugins
    ToolsDir =C:\Program Files (x86)\ADCPro\tools
    PDKLib =C:\Program Files (x86)\ADCPro\pdk_lib
    DataDir =D:\Users\Public\Documents\ADCPro\saved
    SharedDir =C:\Program Files (x86)\ADCPro\shared
    HideRootWindow = TRUE
    DebugServerWaitOnLaunch = TRUE
    EnableLauncher =TRUE
    viSearchPath =<topvi>:\*; C:\Program Files (x86)\ADCPro\pdk_lib\*; C:\Program Files (x86)\ADCPro\plugins\shared\*; C:\Program Files (x86)\ADCPro\plugins\*

    Thanks for your help!

    Best Regards

    Dominik

  • Hi Dominik,

    Were you able to try and load one of the standard ADCPro plugins?  There are two standard plugins that should show up when you click on the EVM drop down menu in ADCPro besides the ADS1247EVM plugin.  

    Thanks,

    Bob B

  • Hi Bob,

    my problem is solved now... Initially I installed ADCPro without standard plugins. After reinstalling ADCPro with those plugins (to check, if they work properly) for some reason also my required plugin worked.

    thanks for your help!

    Best regards, Dominik

  • Hi Dominik,

    Great news on finding the solution! And thanks for responding with the solution.

    Best regards,
    Bob B