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.

TSW1400EVM: TSW1400 with AFE5805 running HSDC data capture questions

Part Number: TSW1400EVM

Hello,

Im currently working with a TSW1400 EVM along with the AFE5805 EVM to capture ultrasound

signals. So far I am only using 1 channel and 4096 samples, which is sufficient for my project.
Ill first explain how I want the system to work. Since the purpose of this work is for an

automated signal capturing system we want it to work with fewer human interaction as possible,

so much of the information displayed on the HSDCPro software is not needed. I want to capture

data with an external trigger signal at around 1-5kHz. As mentioned before I have no interest on

the FFT, just the raw ADC data. A large amount of data from various acquisitions should be

either stored on memory (1GB DDR2) for later retrieval or the data should  be constantly

transferred as it is captured to the PC and stored on a HD (without displaying the time domain

and FFT graphs on the HSDCPro software).

The problem Im facing is the time it takes to capture a single data, as it should send the

capture command, retrieve data from memory, send it back to the PC via USB, calculate the FFT

and plot both time domain and FFT graphs on the HSDCPro software.

I also explored the "HSDCPro Automation DLL" fodler which contains the .dll for MATLAB, C or

LabVIEW code customization, but when using the "Read_DDR_memory" fuction with the external

trigger option from the DLL (or the normal capture mode without trigger) the HSDCPro graphs are

always updated to the last capture. This way Im unable to capture data at a 1-5kHz rate as I

require it.

As mentioned in

e2e.ti.com/.../1022451
the TSW1400 was made to run along a computer and the HSDCPro software. So the HSDCPro is

indispensable to work with the TSW1400? My colleague emailed a TI engineer a few weeks ago

asking for the HSDCPro LabVIEW source code but was denied it.

I was wondering if the solution to my problem lies in the .rbf firmware file loaded into the

FPGA or is it in modifying the .dll (if it is possible) file.

I hope I was clear on my explanation and would appreciate any enlightenment. Thanks for spending

your time reading this.

Regards,

Guilherme O.

  • Guillermo,

    The automation DLL was written to control HSDC Pro as HSDC Pro is the control software for 4-5 different hardware platforms.  This method allows someone to automate the hardware without having to support 4-5 different software and firmware trunks.  We are not staffed appropriately to support this level of maintenance for the software and firmware.

    As such we only made the auotmation DLL to control HSDC Pro which in turn controls the hardware.  This was the most simple way to allow automation control of our eval platforms without having to maintain custom builds.

    However this does not make the system fast or efficient.  This was a tradeoff of making it simple.

    If you want to make a fast and efficient custom capture card that is something you will need to do in terms of making new firmware and also new software to replace the existing firmware and HSDC Pro control software.

    Ken.