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: External trigger not detected for 50 MHz sample rate

Part Number: TSW1400EVM
Other Parts Discussed in Thread: ADS5474

I am working with the TSW1400EVM with the ADS5474 eval module. The sample rate for the design I am evaluating is 50 MHz. When I attempt to trigger acquisition using the external trigger option with "arm on next capture button press" activated, the detection of the trigger event is very inconsistent. Sometimes a trigger is detected, other times the software gives up and says that no trigger was detected. When I speed up the sample clock to 400 MHz, the trigger is detected 100% of the time. I guess I'm missing something as to how the trigger signal is detected or maybe my signal is ill-timed. The signal I am using as the external trigger is asynchronous to the sample clock and is a periodic pulse train of period 120 ms, pulse width 1.5 us with edge transitions of 5 ns. Also, the high and low logic levels for this trigger signal are 3.3V and 0V, respectively. Can you tell me if this signal is suitable and if so, what else could be giving rise the the lack of trigger detection for 50 MHz sample rate?

  • Christopher,

    We are looking into this. As far as I can tell, you are doing everything correct. Can you try just sending one pulse? Not sure why you are using a pulse train with trigger mode.

    Regards,

    Jim

  • Hi Jim,

                   Thanks for your response. I'm using the ADS5474 to capture an Arb waveform that repeats every 120ms. I need the first ADC sample to be deterministic so I'm using a sync output from the Arb as an external trigger - the pulse train arises because of the periodicity in the Arb waveform I'm capturing.

    Thanks for suggesting the single pulse test, the acquisition system appears to trigger flawlessly when it doesn't see a train of triggers. I guess the firmware is having a hard time to figure out which edge to use?

    -Chris

  • Chris,

    The firmware used by the TSW1400 for the ADS5474 is outdated and the trigger mode was never fully integrated with this part. This is something that might get updated but I do not have a time frame for this. I would suggest working with a single pulse for now.

    Regards,

    Jim

  • Jim,

                 After some further experimentation, it appears that even a single pulse trigger is no longer being detected. I've completely power cycled the eval boards and the host computer to no avail. In your previous post you said that this was being looked into. Is there any understanding as to why this erradic behavior might be occurring and how I might be able to work around it?

    -Chris 

  • Chris,

    Your finding explains what our firmware team thought. The trigger mode was never supported for this part. Due to limited manpower and budget, this is an effort we cannot work on in the near future. Sorry for the inconvenience. If there is any way you can justify us spending time and money on this project, we may re-consider. Is there any chance you can use one of our newer ADC's?

    Regards,

    Jim

  • Jim,

              The ADS5474 is being targeted for three reasons:

    (1) there is a space qualified version of this converter

    (2) it possesses at least 14-bit resolution

    (3) it can capture samples at a rate of 50 MHz

    If you can recommend a different converter that satisfies these criteria, we can probably consider it. 

    -Chris

  • Chris,

    What is the application? Who would be the end customer? If this works out, how many devices would be purchased on an annual rate?

    Regards,

    Jim