
Publication No. 980938 Rev. K
Model T940 User Manual
Astronics Test Systems
Advanced Topics 8-13
In a DRS, Local Errors can be counted/logged in coupled sequencers while
the Master sequencer is simultaneously counting/logging DRS Errors.
In addition, one could use a different BERREN when counting/logging
Qualified
Local
Errors if that is useful. But there are limitations. See Appendix
A for those limitations.
Notes:
1. The T940 is designed to accurately count/log DRS Errors in the Master at
a 50MHz data rate.
2. When a Sequencer is Independent, the “DRS/Linked” option will not
Count or Log anything.
Pipelining and non-Pipelining
Before Jumping and Halting on various Pass/Fail conditions can be
presented, an understanding of pipelining is required.
•
The pipeline may be from 0-16 Patterns deep. The “0” pipeline
depth will hereafter be called a “zero pipeline depth” or “non-
pipelined”. A pipeline depth of “1-16” will hereafter be called a
“non-zero pipeline depth” or “pipelined”.
•
A zero pipeline depth is primarily used when it’s desired to
perform a Jump on Pass/Fail in a Seq. Step where the deciding
Error may occur on even the last Pattern of the Seq. Step. This
allows one to Halt immediately on Patterns that have a Fail or
Pass. There are performance limitations for the “zero pipeline
depth” covered in the
below.
•
A non-zero pipeline depth means that the Error is offset/delayed
by the depth of the pipeline. In this case, a Halt on Pass or Fail will
occur later by the depth of the pipeline. For Jumping on a Pass or
Fail, there is a Jump Pass/Fail attribute that affects how Jumps
are handled. This is detailed in Section 7. The non-zero pipeline
depth will handle data rates at 50MHz but there is a minimum
pipeline depth required depending on the Data Rate. This is
covered in the
The Pipeline Depth is set on the Edit>Data Sequencer A/B>Sequence
Parameters panel.
The relevant VXI
plug&play
API and ARI functions are:
•
API: tat964_setConditionPipelineMask
•
ARI: AssignPtgPipelineMask