Display

Display signal value during simulation

  • Library:
  • Simulink / Dashboard

Description

The Display block connects to a signal in your model and displays its value during simulation. You can configure the appearance and format for the Display block to make intuitive sense for the value it displays. You can edit the parameters of the Display block during simulation. Use the Display block with other Dashboard blocks to build an interactive dashboard of controls and indicators for your model.

Connecting Dashboard Blocks

Dashboard blocks do not use ports to connect to signals. To connect Dashboard blocks to signals in your model, use connect mode. Connect mode facilitates the process of connecting Dashboard blocks in your model, especially when you want to connect multiple blocks at once. If you only want to connect a single Dashboard block, you can also use the Connection table in the block dialog box to make the connection.

Tip

To facilitate understanding and debugging your model, you can modify Dashboard block connections in your model during normal and accelerator mode simulations.

To enter connect mode, click the Connect button that appears above your unconnected Dashboard block when you pause on it.

In connect mode, when you select one or more signals or blocks, a list of parameters and signals available for connection appears. Select a signal or parameter from the list to connect the selected Dashboard block. To connect another Dashboard block, pause on the block and click the Connect button above it. Then, make a selection of signals and blocks in your model, and choose a signal or parameter to connect.

When you finish connecting the Dashboard blocks in your model, click the Exit button in the upper-right of the canvas to exit connect mode.

Tip

You can hide the message shown on unconnected blocks using the set_param function and the ShowInitialText block parameter.

Limitations

  • Dashboard blocks can only connect to real scalar signals.

  • You cannot use the Connection table to connect a Dashboard block to a block that is commented out. When you connect a Dashboard block to a commented block using connect mode, the Dashboard block does not display the connected value until the you uncomment the block.

  • Dashboard blocks cannot connect to signals inside referenced models.

  • When you simulate a model hierarchy, Dashboard blocks inside referenced models do not update.

  • Dashboard blocks do not support rapid accelerator simulation.

  • Some signals are not available during accelerator mode simulations. To view such signals on a Dashboard block, mark the signal for logging.

Parameters

expand all

Select the signal to connect using the Connection table. Populate the Connection table by selecting signals of interest in your model. Select the radio button next to the signal you want to display. Click Apply to connect the signal. To facilitate understanding and debugging your model, you can connect Dashboard blocks to signals in your model during simulation.

Programmatic Use

Block Parameter: Binding
Type: Simulink.HMI.SignalSpecification
Default: []

Format for displaying numerical values. You can specify any format supported by the format command:

  • short — Scaled fixed-decimal format with four digits after the decimal point

  • long— Scaled fixed-decimal format with fifteen digits after the decimal point for double values and seven digits after the decimal point for single values

  • shortE — Scientific notation format with four digits

  • longE — Scientific notation format with fifteen digits after the decimal point for double values and seven digits after the decimal point for single values

  • shortG — Data takes the more compact format between fixed-decimal or scientific notation, with a total of five digits

  • longG — Data takes the more compact format between fixed-decimal or scientific notation, with a total of fifteen digits for double values and seven digits for single values

  • shortEng — Engineering notation where the exponent is a multiple of 3, with 4 digits after the decimal point

  • longEng — Engineering notation where the exponent is a multiple of 3, with 15 significant digits

  • + — Positive/negative format. +, -, and blank characters are displayed for positive, negative, and zero values, respectively

  • bank — Currency format with 2 digits after the decimal point

  • hex — Hexadecimal representation

  • rat — Ratio

Programmatic Use

Block Parameter: Format
Type: character array
Values: 'short' | 'long' | 'shortE' | 'longE' | 'shortG' | 'longG' | 'shortEng' | 'longEng' | 'bank' | '+' | 'hex' | 'rat'
Default: 'short'

Text alignment in the Display block.

Programmatic Use

Block Parameter: Alignment
Type: character array
Values: 'Left' | 'Center' | 'Right'
Default: 'Center'

Position of the block label. When the block is connected to an element in the model, the label is the name of the connected element.

Programmatic Use

Block Parameter: LabelPosition
Type: character vector
Values: 'Hide' | 'Bottom' | 'Top'
Default: 'Hide'

Opacity of the block, specified as a scalar value between 0 and 1.

Example: 0.5

Programmatic Use

Block Parameter: Opacity
Type: scalar
Default: 1

Foreground color for the block, including the text. You can select a color from a palette of standard colors, or you can specify a custom color.

Programmatic Use

Specify the ForegroundColor parameter for the block as a 1-by-3 [r g b] vector with values between 0 and 1.

Block Parameter: ForegroundColor
Type: [r g b] vector
Default: [0 0 0]

Block background color. You can select a color from a palette of standard colors, or you can specify a custom color.

Programmatic Use

Specify the BackgroundColor parameter for the block as a 1-by-3 [r g b] vector with values between 0 and 1.

Block Parameter: BackgroundColor
Type: [r g b] vector
Default: [1 1 1]

Block Characteristics

Data Types

double | single | Boolean | base integer | fixed point | enumerated

Direct Feedthrough

No

Multidimensional Signals

No

Variable-Size Signals

No

Zero-Crossing Detection

No

Extended Capabilities

Introduced in R2017b