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.

ADS1178EVM-PDK / MMB0 - (Host-PC) API for Accessing EVM Data Directly

Other Parts Discussed in Thread: ADS1278EVM-PDK, ADCPRO, ADS1278
My colleagues are evaluating an ADS1178EVM-PDK/MMB0 and would like to access data directly with our own application.
We would like to obtain as much information as possible regarding the (PC) API information, and additional information relating to plug-ins, drivers, etc. (on both the PC and EVM side) which you would deem relevant to this request.
 
I see that you have answered to a similar request "ADS1278EVM-PDK MMB0 - ADCPro Plug in Question" elsewhere in this forum.
 
Could you please re-summarize specific to the ADS1178EVM-PDK, and directly provide as much information as possible, perhaps, including the source code for ADCPro?
If you could also comment briefly regarding the roles of NI-VISA, LibUSB, and USBStyx in the EVM configuration and data retrieval processes, it would be helpful to our understanding if working with limited documentation and code samples, as you indicated might be the case for the ADS1278.
 
Thanks.
Allan L. Scribner
  • Mr Scribner -

    I first will ask if the post from the link before helps to answer any of your questions?

    http://e2e.ti.com/support/data_converters/precision_data_converters/f/73/t/30698.aspx

    The software communications used for ADCPro and communications on the evaluation platforms does not lend itself well to real time data access and applications.  As mentioned in the above post, the communications uses Styx protocol, which enables a "virtual file system" to be used for communications.  The firmware used to achieve this is probably not what would be desired for a real time data acquisition system.

    That being said, the items that you mentioned (NI-VISA,LibUSB etc) are all part of the communications stack the permit communications between the PC (User Interface) and the ADC via the DSP.

  • Greg:
     
    It think the post you pointed out will be a good start for what we are trying to do:
     
    To be candid, I am playing "middle man" on this request, and I don't have an ADCPro installation (or LabView) on my own machine to review your response in depth.  (I will forward the information to my colleagues and advise further).
     
    Can you please review my comments below to confirm (or correct) my assumptions so far?
     
    1. ADCPro and the appropriate plugin for the ADS1178EVM-PDK are written in LabView code and presently built under LabView 8.5.1.
    The plugin (and ALL LabView code for the plugin), will be found in a ...\plugins\ADS1178EVM directory and we should be able to review this code using LabView.
    We can also retrieve the applicable plugin: "ads1178evm-pdk-plugin-1.0.0.exe" at ftp://ftp.ti.com/pub/data_acquisition/ADCPro/Plugins/ .
     
    2. The EVM Plugin communicates to the EVM over the USB using DLL's which can be found in a "libADCPro" directory.
    I assume that we should be able to understand the interface/calls to the DLL's by reviewing the above LabView code.
     
    3. You have cautioned us that the "virtual file system" implemented for interfacing with the EVM may not be suitable for a real time data acquisition system.
    Can you make any statements regarding the items listed below:
    - maximum "file size" supported in the EVM for a given sample group, (or maximum number of data samples).
    - maximum sample rates or sample rate restrictions while a "data file" is being acquired in the EVM.
     
    Thanks
    Allan L. Scribner
  • Mr Scribner -

    Regarding your questions:

    1. Yes..alot of the actual code is installed in the ADCPro directory on your PC as raw LV VIs.  All the plug-in information should be installed under the "plugins" directory.  The current code was written using LV8.5.1.

    2. You should be able to get an idea of the communication protocol from the provided link and the LV code.

    3.  The reason for the caution is that there is some overhead associated with the USB transfer.  Because of this, we capture the block of data first, then transfer the data via PC once the collection is complete.

    The maximum sample size is 64ksamples.

    The sample rate is restricted to the decimal equivalent (0-4) of DR[2:0] setting in CONFIG0.

     

    An additional note, please keep in mind that we provide this software for evaluation purposes and as is, and therefore do not provide any support for modifications/changes.

     

  • Greg:

    Thanks for the update.

    Regarding the "maximum sample size of 64ksamples", does this means 64ksamples x 8 Channels x 16 Bits = 1Mbytes?

    Thks

    Allan L. Scribner

     

     

  • Mr Scribner -

    Yes...you are correct that the sample size is per channel.