• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 3 answers
  • Subscribers 46 subscribers
  • Views 241 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DATACONVERTERPRO-SW: Automation Setup Procedure

ryota-miyamoto
Prodigy 120 points
Part Number: DATACONVERTERPRO-SW

Hello TI,

We are currently working with TSW14J57 and ADC12DJ5200 for the purpose of automating the capture process. Our plan is to initiate data acquisition by inputting an external signal into TSW14J57. This external signal will be continuous and will be input multiple times.

In the process of setting up automation, I have explored AutomationDLL and read through the documentation. I have a few questions:

  1. How should I go about configuring AutomationDLL? I've looked at sample programs, but I'm interested in understanding the essential configurations.

  2. I assume that data is only acquired when an external signal is input. Is there a way to confirm that data has been acquired?

  3. After completing data acquisition in external trigger mode, do I need to reconfigure the settings again? I'd like to know what steps to take to acquire data again after the initial acquisition.

  4. How long does the communication between HSDC and AutomationDLL typically take?

Thank you very much.

  • 0
    TI__Mastermind 20755 points

    Hi Ryota,

    1. There is no single basic approach to configure the automation dll. In python, we load using CDLL. After that, you may use whichever functions you want. Example:HSDC_Pro = ctypes.cdll.LoadLibrary(hsdc_dll_path)

    2. No external signal is required to capture data. This is done using the Pass_Capture_Event function of the DLL. If the device is setup for trigger mode, “TriggerModeEnable” has to be enabled(1) and “SoftwareTriggerEnable” and “ArmOnNextCaptureButtonPress” has to be disabled(0). TriggerCLKDelays is used as a mask in this case to account for dll time. It is 8-bit so max possible number will be 255. The clock is referring to the reference clock frequency.

    3. The settings in #2 do not have to be re-written. To get the data, you will use Read_DDR_Memory function.

    4. This is system dependent and can vary so we cannot give a guarantee. On my system, it usually takes around 1/2 second per function but if many things are using processor and memory it may take longer. The important thing is to set the TimeoutInMs field in most of these functions to a value which is longer than the time for your pc. Usually, I will have a global variable for TimeoutInMs which is set to 10000. This is 10,000 milliseconds or 10 seconds. If HSDC cannot respond to the DLL call, it will pass and return error allowing next line in script to run.

    Regards, Chase

  • 0 in reply to Chase W
    TI__Mastermind 20755 points

    Hi Ryota,

    I misunderstood your question #3, to get the data you will use Read_DDR_Memory, but you will need to use ADC_Auto_ReArm_Trigger_Settings as well to re-arm the FPGA. This will let the FPGA capture data on the next trigger received.

    Regards, Chase

  • 0 in reply to Chase W
    Prodigy 120 points

    Hi Chase,

    1. Understood.

    2. Understood.

    3. Can Auto_ReArm_Trigger_Setting be used with TSW14J57? While AutomationDLL mentioned it's only for TSW14J56, the HSDC datasheet states it's compatible with the TSW14J5x series.

    4. Understood.

    Thank you for your response.

  • 0 in reply to ryota-miyamoto
    TI__Mastermind 20755 points

    I believe that if the firmware being used supports trigger then it should work as expected. Many devices do not have firmware that support trigger. I am not as familiar with the details on TSW14J57 so I cannot explain with certainty myself.