This is a question about the operation of the AD9144.My customers are evaluating the AD9144.My customer is trying to output sawtooth waves from AD9144.T = 200 nS, + 100 count → -100 countThe customer inputs the code and evaluates the output waveform.Strangely, the output slope bounces small around 0 count.Customers suspect this as miscounts.Is this due to the nature of T-DAC?Do you have any views?Please advise me.
Is this phenomenon called MIDSCALE GLITCH?Where should I check to isolate it from mistakes in circuit design?Best regards
I am grateful for your attention to my post.I feel encouraged by the help of experts.
The following is a fragment of the plot.
This is a new plot obtained after posting.The height of the saw blade is +50 count at the peak and -50 count at the valley.I expect you to find something in the middle of the slope connecting the peaks and valleys.The slope is formed by changing the count along time.I guess this is the same as your "time domain".According to customer's explanation, something happens where the data switches from all zero to all FF.I have never touched the DPG Downloader, but I guess that this plot is not from the DPG Downloader.
After posting, I guessed that the something was noise from other places that occur along time.The case assumed by me is that one of the measuring instruments generates noise along the measurement cycle.I requested the customer to try some waveforms.The result denied my hypothesis.Something occurred along the count and did not occur along the cycle.
I requested a customer a + 100 to 0 sawtooth.Something appeared in the bottom of the saw (0: all zero to all FF points).
I requested the customer a sawtooth wave from 0 to -100.Something did not show up.
I am sorry, I regret that I do not understand your "vector".I hope the information is not insufficient.
A circuit design issue wouldn't be my first guess, as the AD9144 had been on the market for a few years now.
Can you post a plot of the output?
Was the sawtooth waveform vector generated in DPG Downloader?
I am not entirely clear on what you mean by sawtooth wave "count". Are you referring to the sample values, in time domain?
Do you see the glitch at the midscale of the DACs full scale range if you add a small DC offset? Or does it stay with the vector's midscale?
If you are playing a vector, you need to make sure it wraps around properly. Or make it longer with multiple cycles and use a trigger on start. Making it longer could help in either case.
I think I caught a few questions here, let me try to clarify:
vector is simply a "vector of samples", so effectively the .txt that holds the samples you feed into the DAC. These are the samples that define your sawtooth signal.
time domain, as opposed to frequency domain, is just another way to view the signal. So the plot you showed is a time domain plot. If you played this sawtooth into a spectrum analyzer, or did an FFT on the time domain samples, you would get the frequency domain representation of that signal.
per your comments, it sounds like the glitch is due to the sample transitions, so NOT the midscale of the DAC full-scale range, but rather related to bit transitions in the DAC core itself.
Let me think about this a bit more..
Thank you.I am negotiating to present my customer 's vector data to my customers.Best regards