Simulink Subsystems

By on

 Unlock Model Clarity & Power: Your Essential Guide to Simulink Subsystems

1. Enabled Subsystems: Execute only when a control signal is true (useful for mode changes or conditional execution).


Port's Datatype:
  1. Input:
    half | single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image

  2. Enable:
    single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point

  3. Output:
     half | single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image
2. Triggered Subsystems: Execute only when a specific event (like a rising edge) occurs (great for event-driven logic).


Port's Datatype:
  1. Input:
    half | single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image

  2. Trigger:
    single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point

  3. Output:
    half | single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image
3. Function-Call Subsystems: Act like functions that are called by a Stateflow chart or another block (powerful for complex control logic).


Port's Datatype:
  1. Input:
    single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image

  2. Function Call:
    A Trigger type of function-call makes the block a Function-Call port block that accepts function-call events.

  3. Output:
    single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image
4. Atomic Subsystems: These execute as a single unit and are often used for code generation to create distinct functions.

 
Port's Datatype:
  1. Input:
    half* | single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image

  2. Output:
    half* | single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image

5. Variant Subsystems: Allow you to switch between different implementations of a subsystem based on conditions, useful for design iterations or different product configurations.




Port's Datatype:
  1. Input:
    half* | single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image

  2. Output:
    half* | single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | Boolean | fixed point | enumerated | bus | image

*** Happy Learning ***


Location: Bengaluru, Karnataka, India

Comments

Post a Comment

Popular posts from this blog

Simulink Solver

By on
Image
Mastering Your Simulation Speed & Accuracy: A Deep Dive into Simulink Solvers Fixed-Step Solvers: Predictable & Powerful for Real-Time   Fixed-step solvers march through your simulation using a constant time interval (the "step size"). This step size never changes, regardless of what's happening in your model. Model Configuration Setting: Simulink Model for showcasing how the step size is considering for the system / pre-defined for the system. Exported Result from "To Workspace" Block Result:                 Common Fixed-Step Solvers in Simulink: - ode1 (Euler) - ode1be (Backward Euler)   - ode2 (Heun) - ode3 (Bogacki-Shampine) - ode4 (Runge-Kutta) - ode5 (Dormand-Prince) - ode8 (Dormand-Prince) - ode14x (extrapolation) - Discrete (for purely discrete-time models) - FixedStepAuto (Simulink automatically selects an appropriate fixed-step solver and step size based on model characteristics). Variable-Step Solvers:...
Read more

Saturation Block

By on
Image
 🚗Implementing Saturation Block Logic Without Using the Built-In Saturation Block in Simulink When working on control systems or signal conditioning in Simulink , you’ll often need to limit a signal within a certain range — for example, to ensure an actuator input never exceeds its physical constraints or to prevent numeric overflow. Simulink provides a convenient Saturation block , but what if you want to implement the same functionality manually — for learning, custom modeling, or to comply with modeling guidelines (like MAAB or ISO 26262) ... (i) By using Simulink Method: Use Case 1: By inputting the value to 0 with the help of manual switch, the Output will be 0. Use Case 2:  By inputting the value to 1.1 with the help of manual switch, the Output will be 1. Simulink Blocks Used: 1. Inport 2. Constant 3. Manual Switch 4. MinMax 5. Outport (ii) By using MATLAB Scripting Method: Results: Conclusion: Saturation can be implemented easily without using the built-in block. T...
Read more