# Setting Up the Oscilloscope in SCPI Programs

Migration Guide

- Migration Guide
- SCPI Differences
- SCPI Similarities
- SCPI Command Subsystem Comparison
- SCPI Programming Tools
- Setting Up the Oscilloscope in SCPI Programs
- Synchronizing Analysis with Acquired Data in SCPI Programs
- Querying Measurement Results
- Querying Waveform Data
- Waveform Load/Save Format Support
- Debugging SCPI Programs
- Example Programs for Common Oscilloscope Tasks, Old vs. New

Default setup (`*RST` or `:SYSTem:DEFault`), factory default (`:SYSTem:FACTory`), or autoscale (`:SYSTem:AUToscale`) are fine starting points for oscilloscope setup, but because they mimic graphical user interface (GUI) actions, they leave acquisitions running.

When acquisitions are running, setting changes interrupt and restart acquisition-analysis cycles (and make it unclear whether analysis happens on old or new data, see Synchronizing Analysis with Acquired Data in SCPI Programs). To avoid the performance hit of interrupting and restarting acquisitions, it is good for acquisitions to be stopped (`:ACQuire:STOP`) and the display to be cleared (`:ACQuire:CDISplay`) when setting up the oscilloscope.

When setting up for waveform memories, it is not possible to set up with a clear display. However, you can temporarily turn off analysis during setup by using the `:SYSTem:AENable OFF` command and then turn analysis back on when you have completed setup and you ready to analyze acquired data.