What decides the real performance of a high-speed ADC or DAC board: clock jitter and the SNR it allows, power supply noise, grounding and partitioning, the analog input and filter, FPGA interface timing, and how to measure the result.
A 14-bit converter promises about 86 dB of signal-to-noise ratio in theory and quotes somewhat less in practice. On a real board you will almost never beat the datasheet; you will lose some of it, and the whole game is how little. The loss comes from four places: the clock, the power supply, the analog path and the layout. Fix them in that order of importance, and measure after each change so that you know which one helped.
Sampling at the wrong instant by a tiny amount produces an error proportional to how fast the input is changing. The signal-to-noise ratio that clock jitter alone allows is
SNR = −20 · log10(2π · f_in · t_jitter)
For a 10 MHz input and 1 ps of RMS jitter, that is about 84 dB, already below the 86 dB of an ideal 14-bit converter. At 50 MHz with the same jitter, it falls to about 70 dB. Two consequences follow. The higher the input frequency, the harder the clock requirement, so converters sampling intermediate-frequency signals need exceptional clocks. And a jittery clock cannot be repaired afterwards.
Converters have finite power-supply rejection, and noise on the analog supply, especially at the frequencies where it falls inside your band, appears in the output. Switching regulators are noisy at their switching frequency and its harmonics, and these are often the spurious tones that show up in the spectrum.
The old advice to split the ground into an analog and a digital island, joined at one point, is easy to misapply and frequently makes things worse, because it forces return currents on detours and creates antennas at the splits. The usual better practice on a mixed-signal board is a single, solid ground plane, with the analog and digital parts placed in separate regions so that digital return currents never flow beneath the analog circuitry. Route digital signals only over their own region, and never across a gap in the plane. Follow the converter manufacturer's recommendation for how to treat its pins, since it knows how the part was designed.
High-speed converters use parallel or serial LVDS or similar interfaces with a clock that travels with the data. Constrain it properly: match the lengths in each group, terminate at the receiver, and write the timing constraints in the FPGA tool so that the setup and hold at the receiving flip-flops are checked and met across voltage and temperature. A capture that works on one board and fails on another is almost always a timing margin problem. Keep the digital outputs' edge rates no faster than needed, and keep their return currents away from the analog side. We use a Lattice FPGA on that fiber board to handle a 14-bit, 80 MSPS converter and a 16-bit, 50 MSPS converter, which is a typical division of labour: the FPGA moves and processes data at fixed timing, and the analog design decides how clean the data is.
Acquire a clean sine wave from a good source at a frequency chosen to be coherent with the sample rate, so that the FFT of the capture shows the tone in a single bin with no leakage. From the spectrum, read the signal-to-noise ratio, the signal-to-noise-and-distortion ratio and the effective number of bits, plus the spurious tones. Then compare the numbers with the datasheet, change one thing at a time, and watch which change moves them. A tone at a fixed frequency usually names its source: a switching regulator, a clock harmonic or a digital signal. Compare with the input shorted, to separate the noise the board adds from the noise in the source. We did exactly this on our fiber board, which reaches a signal-to-noise ratio above 50 dB over a 1000 m link.
We design mixed-signal boards, from the analog front end to the FPGA and the firmware that processes the data. See our hardware design service and our guide to the hardware design process.
Contact us for customized solutions and quotes