Output Port
SubsystemsThe OutPort (Output Port) block establishes an output interface for a Subsystem container. It collects signals computed by internal blocks and exposes them on the external boundary of the Subsystem block.
Placing an OutPort inside a subsystem automatically adds an output terminal to the parent Subsystem block in the enclosing diagram, facilitating modular reuse, clean encapsulation, and scalable system architecture.
Mathematical Model
The OutPort block functions as an ideal transparent signal boundary pass-through from internal subsystem blocks to external connections:
where:
- is the signal emitted by internal subsystem blocks connected to the InPort port.
- is the output signal available on the parent Subsystem block's external pin.
- Signal transmission across the boundary introduces zero transport latency and zero numerical distortion:
Inputs & Outputs
| Direction | ID | Label | Type | Status |
|---|---|---|---|---|
| → In | in |
Internal Input | number | Required |
Parameters
| Parameters | Label | Type | Default | Description |
|---|---|---|---|---|
portName |
Port Name | text | output1 |
Usage Examples
Example 1: Actuator Command Output from Controller Subsystem
Encapsulating a motor drive controller within a subsystem. The filtered control signal generated by an internal PID block is wired to an OutPort named "motor_voltage". On the main canvas, the subsystem displays a clean "motor_voltage" pin ready for connection to an electric motor plant model.
Example 2: Multi-Sensor Processing Subsystem Outputs
Packaging an attitude estimation algorithm inside a subsystem. Connecting estimated pitch, roll, and yaw signals to three separate OutPort blocks named "pitch", "roll", and "yaw" provides three distinct output pins on the subsystem boundary for connection to 3D visualization and logging displays.
Remarks & Best Practices
- Hierarchical Output Pin Creation: Each OutPort block placed inside a subsystem dynamically generates an external output terminal on the parent Subsystem block.
- Zero Simulation Latency: Signals pass across the subsystem boundary within the exact same simulation timestep with zero phase lag.
- Single Internal Source Convention: Each OutPort should be driven by exactly one internal signal wire; use a
SumorMuxblock if multiple internal signals need to be combined. - Canvas Layout Alignment: Group OutPort blocks on the right side of the subsystem canvas to preserve clear, standard West-to-East signal flow.