Uploaded May 2026 | Updated September 2026, 2 weeks ago
Learn how to use the Simulink® Scope block to speed up debugging and analysis with interactive inspection, automated data capture, and built-in measurements. The Scope block is much more than a visualization tool and can log data directly to the MATLAB® workspace and manage performance for long-running or high-sample-rate simulations. Additionally, it can quantify signal behaviour with measurement tools such as Signal Statistics and Peak Finder. It can also use triggers to capture key events, such as overshoots in a step response of a controlled system, without manually searching through long time histories. Finally, signals logged using the Scope block can be viewed in the Simulation Data Inspector to compare multiple simulation results for iterative tuning and design verification.
If you found this video useful, like and subscribe for more Simulink tips. Share your questions or use cases in the comments.
Learn more:
- Simulink Scope Block: bit.ly/3N7b3Wy
- DC Motor Shaft-Speed Control Model: bit.ly/4u1tEGW
- Common Simulink Scope Block Tasks: bit.ly/4wqoXYX
Chapters:
00:00 – Introduction: Why the Scope block matters
00:32 – Model overview: DC motor speed control with PID, disturbance, and noise
01:10 – Visualizing signals: Frame-based vs. sample-based processing
01:40 – Logging data: Log to workspace and choose a format
02:19 – Logging strategy: Scope logging vs. single simulation output
02:45 – Performance tips: Limit data points and use decimation
04:00 – Measurements: Signal Statistics for quick sanity checks
04:36 – Measurements: Peak Finder for overshoot and transient behavior
05:06 – Event capture: Triggers for threshold crossings
06:00 – Analyze a running simulation: Pause, step forward, and step back
06:36 – Snapshot: Freeze traces to inspect transients during long simulations
07:08 – Simulation Data Inspector: Unified view and multi-run comparisons
08:27 – Conclusion: The Scope block, much more than an oscilloscope
--------------------------------------------------------------------------------------------------------
Get a free product trial: goo.gl/ZHFb5u
Learn more about MATLAB: goo.gl/8QV7ZZ
Learn more about Simulink: goo.gl/nqnbLe
See what's new in MATLAB and Simulink: goo.gl/pgGtod
© 2026 The MathWorks, Inc. MATLAB and Simulink are registered trademarks of The MathWorks, Inc.
See mathworks.com/trademarks for a list of additional trademarks. Other product or brand names may be trademarks or registered trademarks of their respective holders.
Learn how to use the Simulink® Scope block to speed up debugging and analysis with interactive inspection, automated data capture, and built-in measurements. The Scope block is much more than a visualization tool and can log data directly to the MATLAB® workspace and manage performance for long-running or high-sample-rate simulations. Additionally, it can quantify signal behaviour with measurement tools such as Signal Statistics and Peak Finder. It can also use triggers to capture key events, such as overshoots in a step response of a controlled system, without manually searching through long time histories. Finally, signals logged using the Scope block can be viewed in the Simulation Data Inspector to compare multiple simulation results for iterative tuning and design verification.
If you found this video useful, like and subscribe for more Simulink tips. Share your questions or use cases in the comments.
Learn more:
- Simulink Scope Block: bit.ly/3N7b3Wy
- DC Motor Shaft-Speed Control Model: bit.ly/4u1tEGW
- Common Simulink Scope Block Tasks: bit.ly/4wqoXYX
Chapters:
00:00 – Introduction: Why the Scope block matters
00:32 – Model overview: DC motor speed control with PID, disturbance, and noise
01:10 – Visualizing signals: Frame-based vs. sample-based processing
01:40 – Logging data: Log to workspace and choose a format
02:19 – Logging strategy: Scope logging vs. single simulation output
02:45 – Performance tips: Limit data points and use decimation
04:00 – Measurements: Signal Statistics for quick sanity checks
04:36 – Measurements: Peak Finder for overshoot and transient behavior
05:06 – Event capture: Triggers for threshold crossings
06:00 – Analyze a running simulation: Pause, step forward, and step back
06:36 – Snapshot: Freeze traces to inspect transients during long simulations
07:08 – Simulation Data Inspector: Unified view and multi-run comparisons
08:27 – Conclusion: The Scope block, much more than an oscilloscope
--------------------------------------------------------------------------------------------------------
Get a free product trial: goo.gl/ZHFb5u
Learn more about MATLAB: goo.gl/8QV7ZZ
Learn more about Simulink: goo.gl/nqnbLe
See what's new in MATLAB and Simulink: goo.gl/pgGtod
© 2026 The MathWorks, Inc. MATLAB and Simulink are registered trademarks of The MathWorks, Inc.
See mathworks.com/trademarks for a list of additional trademarks. Other product or brand names may be trademarks or registered trademarks of their respective holders.
