Measurement Computing TempScan/1100 - Manual (Page 73)

TempScan / MultiScan User's Manual 879596 System Configuration 4-15
If the Post-Stop stop parameter of the Set Counts ( Y ) command is set to a non-zero value, the
TempScan/1100 or MultiScan/1200 will begin sampling Post-Stop data upon the occurrence of the Stop
event, and will acquire the specified number of Post-Stop scans.
When the specified number of Post-Stop scans have been collected, the unit will terminate the current
acquisition and return to a non-acquiring state. If, however, the Post-Stop
stop parameter of the Set
Counts ( Y ) command is zero, the unit will return immediately to a non-acquiring state upon the occurrence
of the Stop event (unless the Auto Re-arm feature is used).
The Post-Stop state may be detected by querying the Stop Event Bit (Bit 1) and the Acquisition Complete
Bit (Bit 0) of the Event Status Register (
ESR ). If and only if the Stopped Bit (Bit 1) of the ESR is set, and
the Acquisition Complete Bit (Bit 0) of the ESR is not set, then the TempScan/1100 or MultiScan/1200 unit
is in the Post-Stop state. The unit will exit the Post-Stop state when the specified number of Post-Stop
scans have been acquired. When this occurs, the Acquisition Complete Bit (Bit 0) of the
ESR will be set
and the unit will return to a non-acquiring state (unless the Auto Re-arm feature is used).
Continuous, Gap-Free Acquisition with Two Timebases
The TempScan/1100 or MultiScan/1200 unit can be configured to have different timebases for its Pre-
Trigger (normal scan interval) and Post-Trigger (acquisition scan interval) states. When the user-specified
Trigger condition is satisfied, the unit switches from the Pre-Trigger to the Post-Trigger state, changing its
timebase if configured to do so. This feature, along with Auto Re-arm, can be used to collect continuous,
gap-free data at two different timebases.
To ensure that the collected data is gap-free, the Pre-Trigger
pre parameter of the Set Counts ( Y )
command must be set to -1 . If a value of 0 or higher is used as the Pre-Trigger pre value, then that value
is the maximum number of Pre-Trigger scans that can be placed in the Acquisition Buffer after the Trigger
condition is satisfied.