From

Accept input from Goto block

Library:
Simulink / Signal Routing
HDL Coder / Signal Routing

Description

The From block accepts a signal from a corresponding Goto block, then passes it as output. The data type of the output is the same as that of the input from the Goto block. From and Goto blocks allow you to pass a signal from one block to another without actually connecting them. To associate a Goto block with a From block, enter the Goto block's tag in the Goto Tag parameter.

A From block can receive its signal from only one Goto block, although a Goto block can pass its signal to more than one From block.

This figure shows that using a Goto block and a From block is equivalent to connecting the blocks to which those blocks are connected. In the model at the left, Block1 passes a signal to Block2. That model is equivalent to the model at the right, which connects Block1 to the Goto block, passes that signal to the From block, then on to Block2.

The visibility of a Goto block tag determines the From blocks that can receive its signal. For more information, see Goto and Goto Tag Visibility. The block indicates the visibility of the Goto block tag:

A local tag name is enclosed in brackets ([]).
A scoped tag name is enclosed in braces ({}).
A global tag name appears without additional characters.

The From block supports signal label propagation.

Ports

Output

expand all

`Port_1` — Signal from connected Goto block
scalar | vector | matrix | N-D array

Signal from connected Goto block, output with the same dimensions and data type as the input to the Goto block.

Parameters

expand all

`Goto Tag` — Tag of the Goto block that forwards its signal to this block
`A` (default) | `<More Tags...>` | ...

Specify the tag of the Goto block that forwards its signal to this From block. To change the tag, select a new tag from the drop-down list.

The drop-down list displays the Goto tags that the From block can currently see. An item labeled <More Tags...> appears at the end of the list the first time you display the list in a Simulink^® session. Selecting this item causes the block to update the tags list to include the tags of Goto blocks residing in library subsystems referenced by the model containing this From block. Simulink software displays a progress bar while building the list of library tags. Simulink saves the updated tags list for the duration of the Simulink session or until the next time you select the adjacent Update Tags button. You need to update the tags list again in the current session only if the libraries referenced by the model have changed since the last time you updated the list.

Tip

If you use multiple From and Goto Tag Visibility blocks to refer to the same Goto tag, you can simultaneously rename the tag in all of the blocks. To do so, use the Rename All button in the Goto block dialog box.

To find the relevant Goto block, use the Goto Source hyperlink in the From block dialog box.

Programmatic Use

Block Parameter: GotoTag

Type: character vector

Values: 'A' | ...

Default: 'A'

`Update Tags` — Update list of visible tags

Updates the list of tags visible to this From block, including tags residing in libraries referenced by the model containing this From block. Update the tags list again in the current session only if the libraries referenced by the model have changed since the last time you updated the list.

`Goto Source` — Path to connected Goto block
block path

Path of the Goto block connected to this From block. Clicking the path displays and highlights the Goto block in your model.

`Icon Display` — Text to display on block icon
`Tag` | `Tag and signal name` | `Signal name`

Specifies the text to display on the From 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.

Programmatic Use

Block Parameter: IconDisplay

Type: character vector

Values:

'Signal name' | 'Tag' | 'Tag and signal
								name'

Default: 'Tag'

Model Examples

Signal Routing with the From, Goto, and Goto Tag Visibility Blocks

Use the From, Goto, and Goto Tag Visibility blocks to route signals in your model.

Open Model

Simulating Automatic Climate Control Systems

Simulate the working of an automatic climate control system in a car using Simulink® and Stateflow®. You can enter a temperature value you would like the air in the car to reach by double clicking the User Setpoint in Celsius Block and entering the temperature value. You can also set the External Temperature in Celsius in a similar way. The numerical display on the right-hand side of the model shows the reading of a temperature sensor placed behind the driver's head. This is the temperature that the driver should be feeling. When the model is run and the climate control is active, it is this display box whose value changes to show the change of temperature in the car.

Open Model

Friction Model with Hard Stops

Model friction one way in Simulink®. The two integrators in the model calculate the velocity and position of the system, which is then used in the Friction Model to calculate the friction force.

Open Model

Building a Clutch Lock-Up Model

Use Simulink® to model and simulate a rotating clutch system. Although modeling a clutch system is difficult because of topological changes in the system dynamics during lockup, this example shows how Simulink's enabled subsystems easily handle such problems. We illustrate how to employ important Simulink modeling concepts in the creation of the clutch simulation. Designers can apply these concepts to many models with strong discontinuities and constraints that may change dynamically.

Open Model

Block Characteristics

Data Types	`Boolean` \| `bus` \| `double` \| `enumerated` \| `fixed point` \| `integer` \| `single` \| `string`
Direct Feedthrough	`no`
Multidimensional Signals	`yes`
Variable-Size Signals	`yes`
Zero-Crossing Detection	`no`

More About

expand all

Search for Goto Tags

To search for Goto tags in libraries referenced by the model when opening the From block dialog box, use the FollowLinksWhenOpeningFromGotoBlocks model parameter with the set_param function.

'off' — Do not search for Goto tags (default).
'on' — Search for Goto tags.

Extended Capabilities

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. See also Required HDL Settings for Goto and From Blocks (HDL Coder).

HDL Architecture

This block has a single, default HDL architecture.

HDL Block Properties

ConstrainedOutputPipeline	Number of registers to place at the outputs by moving existing delays within your design. Distributed pipelining does not redistribute these registers. The default is `0`. For more details, see ConstrainedOutputPipeline (HDL Coder).
OutputPipeline	Number of output pipeline stages to insert in the generated code. Distributed pipelining and constrained output pipelining can move these registers. The default is `0`. For more details, see OutputPipeline (HDL Coder).

Documentation

From

Description