Documentation Center

  • Trial Software
  • Product Updates

View Simulation Results

What Are Scope Blocks, Signal Viewers, Test Points and Data Logging?

Scope blocks, signal viewers, test points, and data logging provide ways for you to display and capture results from your simulations.

These icons represent the various data display and data capture devices:

Scope Block and Scope Signal Viewer Differences

Use Scope blocks and scope signal viewers to display simulation results, but as shown in this table, they have different characteristics.

CharacteristicScope Signal ViewerScope Block
Interface

Attach to signal using Signal Selector or context menu

See Signal Selector

See Scope Signal Viewer Context Menu

Drag from Library Browser
Scope of Control

All viewers centrally managed from Signal and Scope Manager

See Signal and Scope Manager.

Each managed individually

Signals per axis

Multiple

One nonbus signal per axis or multiple signals fed through a mux or a bus

Axes per scope

Multiple

Creating a Multiple Axes Scope Signal Viewer

Multiple

Data handling

Save data to a signal logging object

Save variable data to workspace as structures or arrays

Data logging

Log data to model-wide data object

See Simulink.SimulationData.Dataset and Simulink.ModelDataLogs

None

Scrolling display data capability

Yes

No

Display
  • Data markers

  • Legends

  • Color and line codes distinguish signals

Color and line codes distinguish signals

Graph Refresh PeriodAdjustable

Fixed

Display of Minor StepsThe viewer does not display minor steps regardless of the value of the Refine parameter setting.Only displays major time step values. The scope displays additional interpolated points between major time steps if specified by the refine parameter.

Why Use Signal Generators and Signal Viewers Instead of Source Blocks and Scope Blocks?

You should use signal generators and signal viewers instead of Source and Scope blocks when you want to:

  • Navigate to and attach signal generators or signal viewers deep within a model hierarchy.

  • Centrally manage all signal generators and signal viewers present in your model.

  • Use the display features provided by signal viewers that are not available in Scope blocks.

  • Reduce clutter in your block diagram. Because signal viewers attach directly to signals, it is not necessary for you to route them to a Scope block. This results in fewer signal routes in your block diagram.

  • View data from referenced models. See Test Points for more information.

Was this topic helpful?