|
<< Contents
<< Workbar
<< Setup ToolBar
|
| |
|
|
| |
 |
| |
|
The PreStore edit box / list box defines the location of the Trigger in the trace capture.
|
| |
|
The PreStore value is a percentage of the Sample Depth. If the Sample Depth is 1M with a 10% PreStore, then the Trigger sample appears on sample 100K in the captured trace data.
|
| |
|
The list box provides 0% to 100% PreStore values in 10% steps.
|
| |
|
A 0% PreStore places the trigger sample at the trace capture start.
|
| |
|
A 50% PreStore places the trigger sample at the trace capture middle.
|
| |
|
A 100% PreStore places the trigger sample at the trace capture end.
|
| |
|
A custom PreStore value can also be entered into the edit box area.
|
| |
|
The logic analyzer hardware allows the trigger location to be specified to within about ± 8 samples. However, exact precision is not be guaranteed. The trigger sample resolution varies with the sampling mode.
|
| |
|
Therefore, a 0% PreStore may be preceded by a few "lead in" samples.
|
| |
|
Likewise, a few samples may exist after a 100% PreStore.
|
| |
|
|
| |
|
The Pre-fill ensures the requested PreStore value can be met.
|
| |
|
The logic analyzer's trigger circuits are disabled when the logic analyzer starts running.
|
| |
|
The trigger circuits are enabled after enough samples are captured to meet the requested PreStore.
|
| |
|
By definition, the trigger event cannot be detected until enough samples are stored to meet the PreStore.
|
| |
|
When a slow sample rate is active, waiting for the pre-fill period to expire may take a very long time. This is especially true when the sample depth is very large.
|
| |
|
Transitional Timing and Selective Storage are two cases where the trace data may fill the logic analyzer memory very slowly.
|
| |
|
When trace data is stored to memory slowly, waiting for Pre-fill period can take a very long time.
|
| |
|
Copyright and trademark information
|
|