๐Ÿ“ค

Goto

Signal Routing
Run the live example Free ยท no sign-up ยท runs in your browser

The Goto block is a wireless signal transmitter that publishes its incoming signal to all matching From blocks sharing the identical tag identifier.

In control engineering diagrams, feedback loops and multi-channel telemetry buses frequently span wide areas. Using Goto blocks together with From blocks eliminates long feedback wires, avoids line crossings, and maintains modular diagram aesthetics without introducing transport delay.

Mathematical Model

The Goto block binds its incoming scalar signal u(t)u(t) to the virtual tag bus register B[ฯ„]\mathcal{B}[\tau] where ฯ„=tag\tau = \text{tag}:

B[ฯ„](t)=u(t)\mathcal{B}[\tau](t) = u(t)

This signal is instantaneously mirrored by all corresponding receiver blocks:

yFrom,ฯ„(t)=B[ฯ„](t)=u(t)y_{\text{From}, \tau}(t) = \mathcal{B}[\tau](t) = u(t)

The transmission occurs within the identical solver step, maintaining causal algebraic consistency:

ฮ”trouting=0\Delta t_{\text{routing}} = 0

Inputs & Outputs

Direction ID Label Type Status
→ In in In number Required

Parameters

Parameters Label Type Default Description
tag Tag text A

Usage Examples

Example 1: Clean Feedback Loop Closure

Closing a state-feedback loop in a multi-stage mechanical simulation. The plant displacement output is connected to a Goto block with tag = "pos_feedback". A matching From block on the controller input captures the signal, keeping the forward and feedback paths completely separated and visually clean.

Example 2: Subsystem Health and Telemetry Broadcasting

Transmitting diagnostic health metrics (such as motor temperature or error flags) from deep inside a subsystem to a centralized monitoring panel. A Goto block tagged "temp_alert" sends telemetry directly to monitoring displays without wiring through multiple subsystem hierarchy levels.

Remarks & Best Practices

  • Single Transmitter Rule: Each tag should typically have exactly one Goto block acting as its source; multiple Goto blocks with identical tags can produce ambiguous routing.
  • Compile-Time Signal Binding: The simulation compiler resolves Goto-to-From connections during diagram initialization, ensuring zero CPU execution penalty.
  • Zero Propagation Latency: Signals propagate through the virtual tag connection within the exact same simulation step with no numerical phase lag.
  • Case Sensitivity: Tag matching is case-sensitive; verify consistent capitalization between Goto and From blocks.

Related Components

  • From: Wireless signal receiver block.
  • OutPort: Subsystem output boundary interface.
  • Mux: Combines multiple scalar lines into a vector connection.
  • Subsystem: Hierarchical model container block.