12.07.2015 Views

CompuScope SDK for L.. - Egmont Instruments

CompuScope SDK for L.. - Egmont Instruments

CompuScope SDK for L.. - Egmont Instruments

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

As an example, consider a signal where the feature of interest is 20,000 samples long butbegins 100,000 samples after the trigger event. In this case, the SegmentSize and Depthshould be set to 20,000. The Trigger Delay value should be set to 100,000. Without theTrigger Delay feature, the user would be <strong>for</strong>ced to set the Depth to 120,000 Samples andwaste 100,000 Samples of memory, even though only the last 20,000 were downloaded.Using the Trigger Delay feature, however, only the data of interest are retained in<strong>CompuScope</strong> memory.<strong>CompuScope</strong> Acquisition Timing DiagramThe timing diagram below is provided as an aid <strong>for</strong> understanding the timing of eventsduring the acquisition of a segment or record. The pseudo—signals are indicated asHIGH when the labeled function is active.A <strong>CompuScope</strong> system always acquires from the beginning of the Segment Start pulseand continues until the Depth counter’s count-down has expired. The memory allotted tothe acquisition is equal to the Segment Size and is arranged in a circular fashion. Noticethat raw trigger events are ignored until the Trigger Holdoff time has elapsed.Note also that, although pre-trigger data are acquired throughout the time betweenSegment Start and the Trigger Event, most of the acquired pre-trigger data have beenoverwritten in the diagram below and only a small fraction are available <strong>for</strong> download.<strong>CompuScope</strong> <strong>SDK</strong> <strong>for</strong> LabVIEW <strong>for</strong> Windows 29

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!