Solution
When a TDR offset is applied, there is a change in the NI Digital Pattern Instrument to drive signals early so that it arrives at the DUT at the appropriate time, to compensate for the flight time. In a similar way, for sampling, the instrument will sample late by the flight time to give the signal an opportunity to travel from the DUT back to the tester pin.
When using TDR functions in the API (LabVIEW, C, .NET, Python, etc) to enable and configure your offset, you don't need to manually add the TDR offset to the following timing edges, or modifications. It is taken into account automatically. For example:
- Once you apply the TDR offsets using the nidigitalApplyTDROffsets function, or the nidigitalTDR function with nidigitalApplyTDROffsets = TRUE, then the driver/firmware automatically applies these offsets on all subsequent operations. In other words, you don't need to manually add the TDR offset to your timing values.
- If your TDR offsets need to be changed later in your application, then you should call ApplyTDROffsets again to apply the new offsets.