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.

AFE5812EVM: What versions of hardware, software, etc will allow this to function with TSW1400EVM

Part Number: AFE5812EVM
Other Parts Discussed in Thread: AFE5812

Tool/software:

I pulled out an AFE5812EVM and TSW1400 that I've had for some time to begin working on a new project.

The computer is running Windows 10 Pro.  I downloaded Version 6.0 (latest, I think) of the DataconverterPro SW.  This functions fine with the 1400EVM.

However, the DeviceGUI (I can find version 1.0 on your website) continually crashes.  I have dug through your forums and documentation and found threads about requiring the 32-bit 2010 LabView Runtime library installed.  I've tried both original RTL and the Service Pack 1 version.  Despite others claiming that they've been able to run the GUI on Windows 10, the software constantly crashes.  This happens no matter if running in Windows 7 compatibility mode with/without running it in Administrator mode.

I've started to rummage around for a machine I can throw Windows 7 onto.  However, before I jump through all of these hoops to bring this up, I'm concerned there is potential for some of the DataconvertersPro software versions to not be compatible with the older OS.

Can someone verify what versions of OS/Device GUI/DataconverterPro will function together?  I've lost a good day looking into this already and simply want to have confidence that the next thing I will try will work.

Which specific LabView RTL version should be used with the device GUI?  Is there a particular order that the EVM software packages and Labview RTLs need to be installed in to ensure a working platform?

If I 'downgrade' to Windows 7, are there some versions of the DataconverterPro SW that will or more importantly won't work?

Is there a newer version of the Device GUI, rather than the V1.0 that I have found under the AFE5812EVM page?

It does seem odd that the 'obsolete' 1400 has newer software than the 'active' AFE5812 GUI....

  • Hi,

    You can try once with the  older version of DataconverterPro version ?  I was able to test it with v5.0 successfully in windows 10.

    Also can you please elaborate on crashing ? Did you see any warning/error message ? 

  • I can try that later, certainly.

    However, the crashing behavior is not coming from DataConverterPro.  With version 6 of DataConverterPro V 6, it connects to the 1400, I can select and upload firmware to the board, and it appears to function.

    It is coming from the DeviceGUI for the AFE5812.  If I launch that executable, I will see a Labview icon appear in the task bar at the bottom of the screen for a few seconds and then it will close.  Checking in Event Viewer shows and Exception thrown when launching the RTL dll (0xC0000005).  Just to be clear, it is lvrt.dll 

    The following is the Software I'm referring to, downloaded from the AFE5812EVM webpage.

    SLOC323 — AFE5812EVM GUI 

  • I've only received on reply that answers a non-issue, at least for me.

    Is there anything else that I can add that would solicit more ideas/responses?

    Is there another pathway for TI support?

  • Just so anyone that comes across this has a path forward:

    I installed a seat of Windows 7 SP 1 64-bit onto an older machine.

    I downloaded the 2010 SP1 32 bit LabView Run-time engine from NI.

    Downloaded and installed the SLOC323 AFE5812EVM GUI

    Verified that it ran without crashing.  However did not initially have USB drivers to actually connect with the board.  I left the driver issue unresolved while moving through the rest of the setup.

    I downloaded and installed Version 6 (latest) of DataConverterPro.  This downloaded and installed other versions of the LabView RTL.  It also supposedly installed USB drivers.

    DataConverterPro launched and seemed to function, but could not connect to the 1400 due to USB driver issues.

    I went to the FTDI USB website and downloaded Windows 7 drivers.  However, when I tried to install them (from the driver bundle that had ALL implementation types in one download) I received an unsigned driver error and the driver refused to install.  I then set Windows to 'Ignore' driver signing and the driver seemed to install.

    However, launching both the device GUI and DataConverterPro, neither could connect to the boards.  I launched Device Manager and while I could see the boards 'connected' there was still a driver issue.

    I went back to the FTDI website and downloaded only the VCP drivers and unzipped the download.  Then from the Device Manager went into the Update Driver option and pointed it to the folder holding the VCP driver download.  The install then worked properly.

    At this point the Device GUI and the DataConverterPro packages function and work properly.

    As another datapoint, although others have stated being able to get the Device GUI running under Windows 10, I never could.