Synchronization In The Programming Flow - Agilent Technologies InfiniiVision 3000 Programmer's Manual

37
Synchronizing Acquisitions

Synchronization in the Programming Flow

Most remote programming follows these three general steps:
1
2
3
Set Up the Oscilloscope
Before making changes to the oscilloscope setup, it is best to make sure it
is stopped using the :STOP command followed by the *OPC? query.
It is not necessary to use *OPC?, hard coded waits, or status checking when setting up the
N O T E
oscilloscope. After the oscilloscope is configured, it is ready for an acquisition.
Acquire a Waveform
When acquiring a waveform there are two possible methods used to wait
for the acquisition to complete. These methods are blocking and polling.
The table below details when each method should be chosen and why.
Use When
Advantages
Disadvantages
Implementation
Details
Retrieve Results
Once the acquisition is complete, it is safe to retrieve measurements and
statistics.
1078
Set up the oscilloscope and device under test (see
Acquire a waveform (see
Retrieve results (see
Blocking Wait
You know the oscilloscope will
trigger based on the oscilloscope
setup and device under test.
No need for polling.
Fastest method.
Remote interface may timeout.
Device clear only way to get control
of oscilloscope if there is no trigger.
See "Blocking Synchronization"
page 1079.
Agilent InfiniiVision 3000 X-Series Oscilloscopes Programmer's Guide
page 1078).
page 1078).
on
page 1078).
Polling Wait
You know the oscilloscope may or
may not trigger on the oscilloscope
setup and device under test.
Remote interface will not timeout
No need for device clear if no trigger.
Slower method.
Requires polling loop.
Requires known maximum wait time.
See "Polling Synchronization With
Timeout" on page 1080.