• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 48 subscribers
  • Views 637 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

TSW14J56EVM: HSDCPro Automation DLL with MATLAB

TSW14J56EVM: Continuous data capture using automation DLL

Aravind Venkitasubramony
Intellectual 835 points

Part Number: TSW14J56EVM

Hi

I am interested in a somewhat continuous data capture process through MATLAB using the HSDC Pro Automation DLL. I am able to run the commands using the dll manual and the help provided with this forum.

I was wondering if the easiest way to do continuous capture with the DLL is to include the pass_capture_event followed by the save_raw_data_as_binary_file in a loop and repeat it for a predetermined number of times. Or is the software trigger, a better way to accomplish this. From what I understand the "Enter" press is the trigger mechanism and I do not want to keep pressing enter if I want like say 100 files recorded. I understand I will have to change the file name within the loop and also provide the sufficient Timeout_in_ms, but does this sound like a reasonable way of achieving what I described? 

Also, is there a way to get the FFT data ( real and imaginary) and not just the magnitiude of FFT data using the script? 

  • 0
    TI__Guru* 91947 points

    Aravind, 

    In HSDC Pro, the Software trigger behaves like while pressing the Generate trigger button in the GUI, the firmware will actually send out a trigger pulse to the TRIG_OUT pins, and also looks for a trigger in the TRIG_IN pin. If no trigger input is connected, then the GUI will throw a ‘No Trigger Occurred’ popup and the Generate trigger button has to be pressed for every trigger generation and capture. It is similar to the Capture button press. The capture button does a capture without looking for any trigger, whereas Generate trigger will do a capture after it receives a trigger.

    Yes, we can do a continuous capture with the Software trigger. For this, we have to first do the trigger settings for the Software trigger in the 'Trigger Option' menu. We also have an automation function for this. Later, we have to call the 'Generate Trigger' automation function every time to look for a trigger. After a successful capture, we can save the data to a file using the automation function 'ADC_Save_Raw_Data_As_Binary_File'. The code will be like calling the Generate trigger and ADC_Save_Raw_Data_As_Binary_File in a loop for a certain number of times or till an error occurs due to no trigger.

    Regarding the FFT data, as of now, HSDC Pro gives out only the magnitude of FFT data.

    Regards,

    Jim

  • 0 in reply to jim s
    Intellectual 835 points

    Thank you Jim! I will try the suggestion. Currently, I am doing this by the following construct for say 10 files. Is this any different in performance than what you have suggested with the software trigger? 

    for ii=1:10

    BinaryFilePathWithName = sprintf('%s%s%d%s',folder,filename,ii,extension);

    [Error_Status] = calllib('HSDCProAutomation_64Bit','Pass_Capture_Event',TimeoutInMs);

    [Error_Status] = calllib('HSDCProAutomation_64Bit','ADC_Save_Raw_Data_As_Binary_File',BinaryFilePathWithName,TimeoutInMs);

    end

  • 0 in reply to Aravind Venkitasubramony
    TI__Guru* 91947 points

    There will not be much difference in the performance between the normal capture and the software trigger, as the software trigger will look for a trigger only after the button press.