Scope Module

PN301Posted on August 25, 2025 Updated on July 29, 2026

Table of Contents

This article describes how to use the Cockpit Scope module to interact with the user code running on imperix controllers. This page provides a detailed explanation of all of the module’s features, along with some usage examples.

For users seeking getting-started assistance with Cockpit itself, a separate article is available in PN300.

Scope module basics

The Scope module allows the user to display control signals on an oscilloscope-like interface by capturing and plotting every sample of the scoped user variables. The acquisition is done at the control task rate (i.e. the main interrupt frequency of the controller), ensuring that each and every sample is scoped. 

The scope module can monitor up to 100 MBytes of data. The window length and the control task rate will affect how many user variables can be scoped.  If the control task is set to a standard frequency of 20kHz, it represents scoping one variable for 21 minutes or 32 variables (maximum number of scoped variables) for 40 seconds.

Scope module interface

Screenshot of the imperix Cockpit Scope module interface. The upper section features an oscilloscope-like display with a plot preview (1) and main plot areas (2) showing three-phase sinusoidal signals (Vg_a, Vg_b, Vg_c) and a sawtooth waveform (theta). The interface is annotated with numbers 1 through 21, highlighting key features such as the trigger position (3), y-axis limits (4), and a toolbar containing view controls and an active green "ACQUIRING" state button (17). The bottom bar (21) displays a detailed table of the scoped user variables, including their display styles, scale, offset, units, and calculated metrics like minimum, maximum, and average values.
Scope module interface

The plot preview shows an overview of all the scoped signals. The vertical axis of the preview is automatically scaled so all of the signals fit the plot. The plot preview can be collapsed to optimize space when using Cockpit on a small monitor.

This is the area where the scoped signals are displayed. User variables can be dragged and dropped from the project pane into a plot, which will add them to the acquisition and display the corresponding samples in the area.
The x-axis range (when no zoom is applied) is defined by the Window [ms] field of the Trigger pane (located in the right bar). If multiple plots are created, their x-axis will always remain synchronized, including when zooming.
The user can remove a variable from a plot in the Scope tab of the bottom bar or through the variable plot context menu accessed by right-clicking on the plotted signal.

The plot containing the trigger signal will have two extra cursors added to it. The user can move these cursors to adjust the trigger level and position to set the trigger point (more information in the trigger configuration chapter).

When hovering over the y-axis of each plot, two input fields will show, displaying the current limits of the y-axis range. Inputting a new value into the fields will adjust the upper and lower limit of the range accordingly.

When hovering over the y-axis of each plot, a lock icon will show. Through it the user can lock the y-axis range, preventing unwanted zooming or auto-scaling.

Starts or stops the acquisition. Note that at least one variable must be added to a plot for the acquisition to start.

Force the acquisition of one window, bypassing the trigger mechanism. This is useful when the trigger is configured in Normal or Single mode.

Perform an autoscale on the horizontal and vertical axis, ensuring that the acquired signals fit in the plots.

Perform an autoscale on the horizontal axis of every plot while keeping the vertical axis unchanged.

Perform an autoscale on the vertical axis of every plot while keeping the horizontal axis unchanged.

When switched on, this feature performs a vertical autoscale on every plot after each new acquisition window.

When switched on, a pair of slideable vertical cursors are shown. The cursors allow the user to mark an interval inside which several metrics are calculated on the scoped signals and displayed in the bottom bar.

Clicking this button opens a window that allows the user to create a new scope variable based on a mathematical formula. The formula can combine any of the variables currently displayed inside the Scope module. More details given in the Cockpit Formula Builder section.

Clicking this button opens a window where the user can examine the signals acquired by the scope in the frequency domain. The displayed spectra correspond one-to-one with the user and math variables displayed in the scope. A full overview is given on the Cockpit Spectral Analyzer page.

Shorthand button to toggle displaying ADC channel data on all oversampled probe variables currently acquired in the Scope. Oversampled probes are explained in the Oversampled signals section.

Save the current curves in a snapshot for future comparison. The snapshot mechanism is explained in the Cockpit user guide.

Displays the current acquisition state. The possible acquisition states are:

  • Stopped: the acquisition is stopped. The displayed data is from the last acquisition.
  • Waiting: the acquisition has started and is now waiting for a trigger event to occur.
  • Acquiring: the trigger event has occurred and the signals are being captured. 
  • Offline: the target is disconnected from the host computer or the user code is not running on the target.

The loading bar displays the acquisition and transmission status of the acquired window. 
Note that it is normal to see the loading bar partially filled and blocked when the acquisition is in Waiting state.

Starting from Cockpit version 2026.1, the height of plot areas in all modules can be resized by dragging the border between them. This button resets all plots in the Scope to an equal height.

Creates an empty plot area at the bottom of the scope module.

The scoped variables are displayed in the Scope tab of the bottom bar. The bottom bar Scope tab menus allow the user to:

  • Modify each variable’s display style, scale multiplier, offset value, and measurement unit
  • Remove a variable from scope
  • Toggle a variable’s visibility without removing it
  • Move variables between scope plot areas

In addition to this, the position and the distance between vertical cursors are displayed here, along with the metrics calculated inside the interval defined by the cursors if they are enabled. If the cursors are not enabled, the metrics are calculated over the entire acquisition window. 

 

Advanced scope features

The Scope module offers several advanced features, accessible through the plot footer buttons and the right bar menus.

Trigger configuration

The trigger mechanism of the Scope module behaves the same way as the trigger on a regular oscilloscope. The Trigger pane located in the right bar allows the configuration of the scope trigger.

Screenshot of the Scope module Trigger configuration pane in imperix Cockpit software. The panel displays several trigger settings with numbered annotations from 1 to 6, which correspond to the features detailed in the article. These point to the Window [ms] input field (1), the Edge dropdown set to Rising (2), the Signal dropdown set to Vg_a [Plot 0] (3), the Mode dropdown set to Auto (4), the Position [ms] and Level numerical input fields (5), and an enabled Ripple reject checkbox (6).
Trigger configuration pane

Defines the acquisition window length and changes the x-axis length. This value affects the total number of acquired points.

Defines whether to trigger on rising, falling, or both edges of the trigger signal.

This field defines on which signal the trigger will be applied. This signal will be marked with (T) in the plot legend and can also be changed by right-clicking on a variable and setting it as a trigger through the context menu.
Note that only variables added to the scope module are present in this drop-down list.

Defines the trigger acquisition mode.
In Normal mode, a window is acquired if the input signal reaches the defined trigger point. 
In Auto mode (which is set by default), the trigger acts like in normal mode. However, the window acquisition is forced by a timer set to 100 ms, which ensures acquisition even if no trigger event occurs.
In Single mode, a single window is acquired if the input signal reaches the defined trigger point. After that, the acquisition is stopped.

Change these values to set the trigger point. Alternatively, the trigger position and level can be adjusted directly in the plot area by moving the trigger level and position icons.

This feature improves trigger stability on oversampled ADC signals by avoiding triggering on ripples. Note: This option is only available on the B-Box 4, with SDK 2026.2 or newer.

Oversampled signals

Thanks to an upgraded scoping protocol on the B-Box 4, the user can now display data from hardware resource channels directly in the Cockpit Scope Module. These signals are unbounded by the user code control frequency. For example, ADC signals are acquired at the ADC chip acquisition rate of 20 MSps (or 10 MSps if any of the ADC channels 12-23 are used) while PWM signals are acquired with a resolution of up to 4ns.

There are three types of oversampled signals currently available in the Scope:

  • ADC channel signals
  • Digital I/O (PWM, GPI/O, FLT) channel signals
  • Oversampled probes

The first two types of signals can be found below the User Variables list (left bar in Cockpit). They correspond to the channels defined by the ADC, GPI, GPO, FLT and various PWM blocks in the user code. To display them in the Scope, simply drag and drop them like you would any other user variable.

On the other hand, oversampled probes are user variables that are connected directly (or through a constant gain and offset) to an ADC block in the user code. In the Scope, the user can choose to toggle between displaying just the data acquired at the CPU rate and a combination of user variable and ADC channel data.

Oversampled probes showing the difference between data available in the CPU and the data acquire by the ADCs

Starting with SDK 2026.2, any oversampled signal added to the Scope can be selected as a trigger source.
For oversampled probes, if ADC channel data is visible, triggering occurs on the oversampled signal. If ADC data is toggled off, triggering is done on CPU-rate data. The Ripple Reject option, which is enabled by default, improves trigger stability on signals with large ripples.
Additionally, the Scope can now be triggered on protection trips generated by the controller or when the PWM is enabled.

Screenshot of the imperix Cockpit Scope module Trigger configuration pane. The image highlights the expanded "Signal" dropdown menu, which displays various available trigger sources. The listed options include system events such as "PROTECTION TRIP" and "PWM ENABLED," user variables like "Iout_meas [Plot 0]" (which is currently highlighted/selected) and "Vin_meas [Plot 2]," as well as oversampled hardware channel signals including GPI, GPO, and PWM channels.

All oversampled signals are compatible with the various metrics calculated in the bottom bar, as well as with the Formula Builder. ADC channel signals and Oversampled probes are also compatible with the FFT/THD module, enabling the user to see the spectra of these signals above the Nyquist frequency defined by the control loop rate.

FFT/THD module showing the a current with its switching harmonics.

Transient generator configuration

The transient generator allows the user to apply a predefined signal on multiple user variables, provided they are connected to the Tunable parameter block. The signal is defined as a sequence of transient events at different positions within the scope acquisition window.

In the following example, three transient events are applied to Ig_d_ref. It can be seen that these events are generated simultaneously with the acquisition of Ig_a, Ig_b, Ig_c, and Ig_d.

Scope module containing the result of a transient sequence (on the left). Transient configuration pane (on the right)

This field defines on which variable the defined signal will be applied. In this example, the variable Ig_d_ref is used.

This field defines a vector of positions at which the transient signal values will be applied. In the example, the events are set at 50ms, 100ms, and 150ms.

This field is a vector of values that will be applied on the transient variable. In the above example, the values [10, 5, 15] are applied at [50, 100, 150] ms. The initial value of the tunable variable Ig_d_ref was set to 2.5 and that value is held until the first event at 50ms.

This field defines whether the set values are held until the next event (the Steps option) or used to define linear ramps between the event points (the Linear option). After the last event, the set value is held until the end of the acquisition window regardless of the picked interpolation option.

The transient generator allows entering multiple transient sequences on different variables.
In this example, the second transient sequence is unused.

These two buttons allow the removal or the addition of transient events. There is no limit to the number of transient events.

Clicking the preview button toggles the transient preview in the scope. The transient preview of a given variable shows up as an editable signal in the same plot area as the original acquired variable. Toggling the preview and editing it does not fire the transient or affect the scope acquisition in any way.

Clicking on this button will initiate the transient sequence on all transient variables. Once the sequence is finished, the acquisition will be in Stopped state while the transient variables will go back to the value that was set before the transient was fired.

Defining transients graphically

Starting from Cockpit version 2024.3, the transient input signal can be set using an interactive graphical interface. Clicking the preview button or any of the transient event fields causes the transient preview to show up in the scope, provided that:

  • The transient events and transient event definitions are valid
  • The variable set in the Variable field is added to the Scope
Transient preview from the previous example after selecting the Linear interpolation option and dragging one transient event point

Once the preview shows up, the transient event points, if any are set, will show up as large dots. Using the mouse, the dots can be dragged to set the transient event position and value in one move. To add new points, double click near the editable transient signal and a new dot will show up. To remove existing points, right click on the point and select the ‘Remove point’ option from its context menu.

All of these actions immediately update the corresponding transient event in the right bar. Editing the transient preview does NOT affect the actual Tunable variable or the scope acquisition in any way, unless the ‘Fire transient’ button is pressed. To exit the transient preview mode without firing the transient, simply press the Transient preview button in the right bar again.

Cockpit Formula Builder

The Formula Builder allows the user to create math variables that are then added to the Scope module. Math variables are created based on a mathematical formula that can include any of the currently Scoped variables.

The math variables are calculated on the PC side after the acquisition of a scope window. This alleviates the need to define every variable to monitor in the user code, saving on hardware resources while still allowing the user to track them live through Cockpit. This also saves time, as new math variables can be added or their formula edited without having to recompile the user code.

With the exception of constant expressions and scalar-valued functions, all of the mathematical operators and functions provided by the Formula Builder are applied element-wise. This means that the formula is applied to each and every sample of the variables included in the expression, creating a new signal to be plotted in the scope.

Layout of the Cockpit Formula Builder

To create a Math Variable, it needs a valid name. The name has to be unique and cannot be edited after creation.

While not necessary for Math Variable creation, the unit of the new variable can be set while building its formula. If not set here, the unit can always be edited, like with any other variable, from the bottom bar.

This option allows the user to choose where the created Math Variable should be plotted or even create a new area to plot it in. After creation, the Math Variable can be moved around between plots like any other scoped variable. 

This button controls the appearance of the list of formulae of previously created Math Variables.

Here, the formula is defined either by typing it or clicking on the options in the menus below.

The list contains all of the formulae of the previously successfully created Math Variables.

This menu contains all of the binary operators usable for building a math formula.

This list contains all of the functions usable while building a math formula. The functions are grouped into three categories:

  1. General math is a collection of elementary (abs, exp, log, sgn, sqrt) and rounding functions (ceil, floor, round, trunc)
  2. Trigonometry includes all of the typical trigonometric and hyperbolic functions, along with conversion functions between degrees, radians, and gradians
  3. Scalar-valued functions are grouped based on the fact that they all evaluate into one number.

This list contains all the variables currently displayed in the scope, including acquired user variables and other math variables. The mathematical formula can use all the variables in this list as operands.

As the math formula is being typed, the errors provided by the formula parser are displayed here. None of these errors are critical to Cockpit operation; they serve as guidance to creating a math expression that can be properly interpreted and used to evaluate the new Math Variable.

Clicking on Save variable will attempt to save the Math Variable with the currently entered parameters. If successful, the window will close, and the saved variable will be displayed in the selected Scope plot area.

Clicking on Cancel will close the Formula Builder window without saving anything.

Interacting with Scope graphs and plots

The Scope module consists of one or more plot areas that display graphs based on variables defined by the user code. This section lists out the tips and tricks for manipulating plot variables and plot areas in the Scope.

Managing plot variables

To add a variable to a plot, select it in the USER VARIABLE, ANALOG INPUTS or DIGITAL I/O section in the project pane, drag and drop it over the plot. To add multiple variables to a plot, keep the Ctrl key pressed and click on the desired variables to select them. Alternatively, click on the first variable to select it, keep the Shift key pressed, and click on the last variable to select. Variables selected like this can then be dragged and dropped into a plot all at once.

Added variables will show up as rows in a table in the bottom bar tab corresponding to the module. Here, variables can be removed, their style and visibility and plotting order can be managed and they can be moved from plot to plot. Statistical metrics calculated from the graph data (min, max, average, root-mean-square, peak-to-peak,…) can be read here as well.

All of these actions can also be accessed from context menus by right-clicking on a plotted variable or on the empty space in the plots.

Managing plot areas

New plot areas can be added by clicking on the + button in the bottom right of the module. The total module height can be freely distributed between the plots. To resize plot heights click on the border between the plot areas and drag.

  • To zoom in and out along the horizontal axis, place the mouse cursor over the area of interest. Then, use the mouse wheel to zoom in or out around the location of the mouse cursor.
  • To zoom in and out along the vertical axis, place the mouse cursor over the area of interest. Then press the Ctrl key and use the mouse wheel to zoom in or out around the location of the mouse cursor.
  • To zoom on a specific area, click and drag to draw a blue rectangle over the zoom area.
  • To achieve a horizontal auto-scale, right-click and drag horizontally. A light grey horizontal strip will appear. Release the mouse button to perform the horizontal auto-scale.
  • To achieve a vertical auto-scale, right-click and drag vertically. A light grey vertical strip will appear. Release the mouse button to perform the vertical auto-scale.
  • To enter panning mode press and hold the mouse middle button or Ctrl + Left mouse button and move the mouse.
  • To prevent a plot from changing the displayed range of values, hover over the y-axis and click the lock icon that shows up. The same can be done frome the y-axis pane menu in the right bar.

Scope application examples

The following examples illustrate some use cases of the Scope module:

  • Measuring the speed tracking performance of an electric motor drive controller.

Related Articles