ADS9229: Additional latency with decimation

Part Number: ADS9229

Tool/software:

Dear TI team,

I have performed some measurements of the ADC latency (SMPL_CLK to data on the data lanes) in two different configurations.  I have a question about a delay I didn't understand in the second configuration I tested.

I connected a square signal generator to the ADC input and checked the data stream at the ADC output to see the step in the data.

Case 1: 2-lane output and decimation disabled

    The ADCs are configured as follows:

        Register 0xFB -> 0x0000

        Register 0x0D -> 0x2382

    In this case, I measured a latency close to 112 ns with jitter ranging from 0 to 50 ns.

    The jitter of 50 ns makes sense, as the square signal was not synchronized with the sampling clock.

    The 112 ns corresponds to the delay specified in the datasheet (page 11, td_SMPL_DATA), so the measurement seems correct.

Case 2: 1-lane output and decimation set to 2 samples averaged

    The ADCs are configured as follows:

        Register 0xFB -> 0x0002

        Register 0x0D -> 0x23C2

    In this case, I measured a latency of around 225 ns with a jitter of 0 to 100 ns.

    A jitter of 100 ns makes sense, as we are averaging two samples with a sampling period of 50 ns.

    However, I don't understand why the latency increased by around 113 ns.

Do you know what the reason for this higher latency is?

Does enabling decimation increase the latency?

Looking forward to your reply,

  • Hello Victor, 

    Welcome to TI's E2E Forum! Thank you for your question! 

    Thank you as well for the information provided, it is very helpful. 

    As you have mentioned, for a measurement in 2-lane mode without averaging the latency is ~112ns. This does match and the equation to calculate this latency is: 

    Which at 20MSPS, the latency is ~112ns

    For case 2, where averaging is enabled and there is an OSR = 2, the ADC output speed needs to be reconsidered

    The sampling speed is halved because the ADC needs OSR times of sample clocks to collect all the measurements and output an averaged out value.

    This would in turn end up being ~OSR * Latency --> making is ~112ns * 2 --> ~224ns

    Best regards, 

    Yolanda