Documentation Home Page RT-LAB Home Page
Pour la documentation en FRANÇAIS, utilisez l'outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

The Monitoring view displays CPU usage for each task/probe executed during real-time simulation.

  • It displays the duration of each probe and can display its start and stop time.
  • It detects overruns and highlights steps where overruns are detected.
  • It enables you to save the results and to export them to other software, such as Excel.

Monitoring your model helps you to profile your CPU usage and your tasks and to distribute your simulation by evaluating the time spent by each part of the simulation. See Monitoring Models for more information about monitoring.

To show the monitoring view in the current perspective, click Window > Show view > Other... menu and then select the RT-LAB > Monitoring item.


Here is what the Monitoring view looks like. Details about each area are explained below.

Probes Area


This area shows all probes currently visible. It also shows the model and subsystems probes that summarize the tasks for the model and the subsystems. By default, only commonly used probes are visible. To select which probes are visible, use the Filter dialog to edit and select filters.

Info Area


This area shows the main statistics of all visible probes. By default, only the CPU usage [%] is visible but it is also possible to show the minimum, maximum and mean durations of all visible probes for the current acquisition frame using the expand/collapse buttons of this area.

Data Area


This area shows the duration, start time and stop time for all visible probes for each time step of the acquisition frame. The expand/collapse buttons of this area show/hide the time steps with/without overruns. By default, only the steps with overruns are visible, and only the durations are visible in the cells but it is possible to add timing content from the view menu. When a time step contains an overrun, a red symbol appears at the top of the column.

Using the Monitoring View


Here are the steps to use the Monitoring view. See the following sections for more detail on the toolbar and menu items.

  • Select the model you want to monitor in the Project Explorer view.
  • Open the Monitoring view if necessary. Click Window > Show view > Other... menu and the select the RT-LAB > Monitoring item.
  • While the model is running, click the Get Probes or Get Probes constantly buttons to perform 1 or N monitoring acquisitions respectively.
  • If consecutive acquisitions are performed, click the Stop button to cancel the acquisition.
  • In the probe area, expand and collapse model and subsystem probe items to display the probes of interest.
  • If necessary, click the Filter button in the toolbar to apply different filters and change which probes are visible. By default, only the most commonly used probes are displayed.
  • Expand and collapse the Info and Data area to get more details on the probes.
  • Click the Units menu item and then use the Units dialog to change the units of all timing information.
  • Click the Properties menu item and then use the Monitoring Properties dialog to change the acquisition setting of the monitoring.
  • Search for time step with overrun in the data area.
  • To do so, use the Search overrun button from the toolbar, scroll through the column in the data area to find the error symbol or collapse the column without overruns using the expand/collapse button from the data area.
  • Save the monitoring results to a CSV file or copy the cells to your favorite text editor.

Toolbar

ICONDESCRIPTION

From top to bottom:

Get probes
Get probes from the running simulation. It acquires only one
acquisition frame of N consecutive steps.


Get probes constantly
Get probes from the running simulation. It acquires consecutive acquisition frames until an overrun is detected or until the stop button is pressed.


Stop probes
Stop consecutive monitoring acquisition.


Save as ...
Save monitoring information as a CSV file. CSV file can be easily imported into an Excel worksheet.


Show next overrun
Find in the current acquisition frame the next step where an overrun occurred.


Select probes

Select the probes to be displayed in the monitoring view by selecting filters based on their name

Menu

Select content > Start and Stop timesSelect the content to be displayed in cells of all steps acquired during a frame. When the start and stop times are selected, the cell contains, in addition to the probe’s duration, the probe’s start and stop time.
Sort BySorts the probes in the monitoring view by name, by chronological order or by the default order
UnitsOpens a dialog that configures the units used in the monitoring view.
PropertiesOpen a dialog that configures the main acquisition setting of the monitoring view.
Context Menu
CopyCopies the selected cell to the clipboard
DeleteDeletes the selected probe from the list of visible probes. When deleted a filter is automatically created.
Filter Dialog

This dialog selects the probes to be displayed in the Monitoring view.


Select AllSelects all filters from the list.
Deselect AllDeselects all filters from the list.
Add...Creates a new filter. It is useful when custom probes are inserted in the model.
Edit...Edits a filter and then change its name or its matching regular expression. For advanced users only.
Delete...Deletes a filter from the list.
RestoreRestores all filters to their default values.
Units Dialog

This dialog allows configuring of the units of the durations and start and stop times shown in the Monitoring view. Available units are seconds, milliseconds and microseconds. It is also possible to configure whether the start and stop times shown are relative to the beginning of the current acquisition frame or based on the absolute time of the simulation.

Monitoring Properties Dialog

This dialog allows you to change the acquisition settings for the monitoring.

Number of samples by frameThis setting allows you to change the number of consecutive steps (samples) by the frame that is acquired by the monitoring. This setting can be changed while the simulation is running.
Maximum number of samplesThis setting allows you to determine the maximum number of samples that could be set for one frame.
This setting is enabled when the model is not running and was property compiled.
TriggerThe trigger settings are not yet available from this dialog.
Number of visible steps before and after overrunsIt determines the number of steps visible before and after a time step with overruns. This setting is used when steps without overruns are hidden from the data area (using the expand/collapse button if the data area). It allows focussing on steps close to overruns.

Terminal View


The Terminal View provides quick access to the remote target by opening a telnet connection. From here, it is possible to gather information by sending commands to the target. This view is very useful for diagnostic and debug tasks.

The Terminal View appears in a tabbed notebook:

Terminal View


The next section presents how to connect to the remote target. Other sections show some examples and explain the toolbar and the contextual menu.

By default, the Terminal View is not included in the Edition perspective. To add it to the current perspective, click Window > Show view > Other... > Terminal > Terminal

How to Connect to Remote Target


Open the Terminal View


To open a new Terminal View on a specific target, click on the Telnet menu item from the Tools menu of the target.

Open Terminal view


Verify the terminal settings and then click OK. The view title settings can be changed if more than one terminal has to be opened at the same time.

Terminal Settings


Then, verify the connection status at the top left of the terminal view. It should be updated to CONNECTED. Ex.: Telnet: (192.168.0.201:23 - CONNECTED)

Login to remote target

To login to a remote target, you need to enter the login name and the password.

By default, the user name for a target is "root"

What does the Terminal View offer?


The Terminal View gives the opportunity to communicate with targets to:

  • Watch the running processes
  • Know which versions of the software are installed
  • Launch configuration scripts
  • Install new software
  • Debug models
  • Consult information logs
  • Open crash files
  • Execute operating system commands



Note: All Linux commands are available on OPAL-RT Linux (x86-based) targets. 





  • No labels