Pass block input to From blocks
Simulink / Signal Routing
HDL Coder / Signal Routing
The Goto block passes its input to its corresponding From blocks. The input can be a real- or complex-valued signal or vector of any data type. From and Goto blocks allow you to pass a signal from one block to another without actually connecting them.
A Goto block can pass its input signal to more than one From block, although a From block can receive a signal from only one Goto block. The input to that Goto block is passed to the From blocks associated with it as though the blocks were physically connected.
For example, this model uses a Goto block and a From block.
An equivalent model passes the Sine Wave block signal directly to the Gain block.
Goto blocks and From blocks are matched by the use of Goto tags.
The Tag visibility parameter determines where From blocks can access the signal.
The Goto block supports signal label propagation. For more information, see Signal Label Propagation.
Port_1 — Input signal
scalar | vector | matrix | N-D array
Input signal to be passed to the corresponding From block, specified as a scalar, vector, matrix, or N-D array.
fixed point |
Goto tag — Block identifier
A (default) | ...
The Goto block identifier. This parameter identifies the Goto block whose scope is defined in this block.
|Type: character vector|
Tag visibility — Scope of the Goto block tag
local (default) |
The scope of the Goto block tag, specified as
global. When you set this parameter to
scoped, you must use a Goto Tag Visibility block to
define the scope of tag visibility.
local(default) — From and Goto blocks that use the same tag must be in the same subsystem. A local tag name is enclosed in brackets (
scoped— From and Goto blocks that use the same tag must be either:
In the same subsystem.
At any level in the model hierarchy below the Goto Tag Visibility block that does not entail crossing a nonvirtual subsystem boundary. In other words, they must be within the boundary of an atomic, conditionally executed, or function-call subsystem or a model reference.
A scoped tag name is enclosed in braces (
global— From and Goto blocks using the same tag can be anywhere in the model except in locations that span nonvirtual subsystem boundaries.
The rule that From-Goto block connections cannot cross nonvirtual subsystem boundaries has the following exception. A Goto block connected to a state port in one conditionally executed subsystem is visible to a From block inside another conditionally executed subsystem.
Goto block in a masked system is visible only in that
subsystem and in the nonvirtual subsystems it contains. Simulink® generates an error if you run or update a diagram that has
a Goto Tag Visibility block at a higher level in the
block diagram than the corresponding
Goto block in the masked subsystem.
Use local tags when the Goto and From blocks using the same tag name reside in the same subsystem. You must use global or scoped tags when the Goto and From blocks using the same tag name reside in different subsystems. When you define a tag as global, all uses of that tag access the same signal. A tag defined as scoped can be used in more than one place in the model.
|Type: character vector|
Icon display — Text to display on block icon
Tag (default) |
Signal name |
Tag and signal name
Specifies the text to display on the block icon. The options are the block tag, the name of the signal that the block represents, or both the tag and the signal name.
|Type: character vector|
Rename All — Propagate name throughout model
Rename the Goto tag. The new name propagates to all From and Goto Tag Visibility blocks that are listed in the Corresponding blocks box.
Alternatively, when you change the tag on the Goto block icon, propagate the new name to all corresponding From and Goto Tag Visibility blocks by pressing Shift+Enter.
Corresponding blocks — Blocks connected to this Goto block
block path | ...
List of the From blocks and Goto Tag Visibility blocks connected to this Goto block. Click an entry in the list to display and highlight the corresponding From and Goto Tag Visibility blocks.
Alternatively, in the Simulink Editor, select the Goto block to highlight the corresponding From and Goto Tag Visibility blocks.
When a corresponding From or Goto Tag Visibility block is not in the current diagram, the Subsystem block that contains the block is highlighted.
To show a corresponding block in an open diagram or new tab, select the Goto block and pause on the ellipsis. Then, select Related Blocks from the action bar. When multiple blocks correspond to the selected block, a list of related blocks opens. You can filter the list of related blocks by entering a search term in the text box. After you select a related block from the list, window focus goes to the open diagram or new tab that shows the related block.
C/C++ Code Generation
Generate C and C++ code using Simulink® Coder™.
HDL Code Generation
Generate Verilog and VHDL code for FPGA and ASIC designs using HDL Coder™.
HDL Coder™ provides additional configuration options that affect HDL
implementation and synthesized logic. HDL code generation does not support
Tag Visibility of the blocks set to
global. See also Required HDL Settings for Goto and From Blocks (HDL Coder).
This block has one default HDL architecture.
Number of input pipeline stages
to insert in the generated code. Distributed pipelining and constrained
output pipelining can move these registers. The default is
PLC Code Generation
Generate Structured Text code using Simulink® PLC Coder™.
Design and simulate fixed-point systems using Fixed-Point Designer™.
Introduced before R2006a