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.
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.
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.
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
Mr Scribner -
Yes...you are correct that the sample size is per channel.