Subsystem masking in Simulink - Step-by-Step Execution

Concept Flow - Subsystem masking

Create Subsystem Block

↓

Open Mask Editor

↓

Add Mask Parameters

↓

Define Mask Dialog

↓

Link Parameters to Subsystem

↓

Save and Apply Mask

↓

Use Masked Subsystem in Model

This flow shows how to create a masked subsystem in Simulink by adding parameters and linking them to the subsystem for easier reuse.

Execution Sample

Simulink

1. Create a Subsystem block in Simulink.
2. Open Mask Editor from the block's context menu.
3. Add parameters like sliders or edit boxes.
4. Define dialog appearance and parameter properties.
5. Link parameters to block mask variables.
6. Save and close the Mask Editor.
7. Use the masked subsystem with custom parameters.

This sequence creates a masked subsystem with user-friendly parameters to control internal block settings.

Execution Table

Step	Action	Parameter Added	Mask Variable Set	Effect on Subsystem
1	Create Subsystem block	None	None	Subsystem block appears in model
2	Open Mask Editor	None	None	Mask dialog ready for editing
3	Add parameter slider	GainSlider	gainValue	Parameter GainSlider added
4	Add parameter edit box	OffsetEdit	offsetValue	Parameter OffsetEdit added
5	Link parameters to mask variables	GainSlider, OffsetEdit	gainValue, offsetValue	Parameters control internal variables
6	Save and close Mask Editor	None	None	Mask applied to subsystem
7	Use masked subsystem	User sets GainSlider=5, OffsetEdit=2	gainValue=5, offsetValue=2	Subsystem behavior changes accordingly
8	Exit	N/A	N/A	Masking complete, subsystem ready for reuse

💡 Mask applied and subsystem ready for use with custom parameters

Variable Tracker

Variable	Start	After Step 3	After Step 4	After Step 5	After Step 7	Final
gainValue	None	Linked to GainSlider	Linked to GainSlider	Linked to GainSlider	5	5
offsetValue	None	None	Linked to OffsetEdit	Linked to OffsetEdit	2	2

Key Moments - 3 Insights

Why do we need to link mask parameters to variables?

Linking mask parameters to variables connects the user input in the mask dialog to the internal subsystem settings, as shown in execution_table step 5.

What happens if we don't save the mask after editing?

If the mask is not saved (step 6), the parameters won't apply, and the subsystem remains unmasked, so user inputs won't affect it.

Can we use different parameter types in the mask?

Yes, you can add sliders, edit boxes, checkboxes, etc., as shown in steps 3 and 4, to make the mask user-friendly.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what parameter is added?

A gainValue

B OffsetEdit

C GainSlider

D offsetValue

💡 Hint

Check the 'Parameter Added' column at step 3 in the execution_table.

At which step are the mask parameters linked to internal variables?

A Step 5

B Step 6

C Step 4

D Step 7

💡 Hint

Look for 'Link parameters to mask variables' in the Action column of execution_table.

If the user sets GainSlider to 10 at step 7, what happens to gainValue?

A gainValue remains unchanged

B gainValue becomes 10

C gainValue becomes 5

D gainValue is removed

💡 Hint

Refer to variable_tracker for gainValue changes after step 7.

Concept Snapshot

Subsystem Masking in Simulink:
- Create a subsystem block.
- Open Mask Editor to add parameters.
- Link parameters to mask variables.
- Save mask to apply.
- Use masked subsystem with custom inputs.
- Makes complex blocks user-friendly and reusable.

Full Transcript

Subsystem masking in Simulink lets you create a user-friendly interface for a subsystem block. You start by creating a subsystem, then open the Mask Editor to add parameters like sliders or edit boxes. These parameters are linked to internal variables controlling the subsystem's behavior. After saving the mask, the subsystem can be used with custom inputs that change its function easily. This process helps make complex models simpler to use and share.

Practice

1. What is the main purpose of masking a subsystem in Simulink?

easy

A. To automatically generate code

B. To hide the internal details and provide a simple interface

C. To increase the simulation speed

D. To change the solver settings

Solution

1. Step 1: Understand what masking does

   Masking a subsystem hides its internal blocks and connections from the user.

2. Step 2: Identify the main benefit

   This makes the subsystem easier to use by showing only relevant parameters and controls.

3. Final Answer:

   To hide the internal details and provide a simple interface -> Option B

4. Quick Check:

   Masking = Hide complexity [OK]

Hint: Masking simplifies subsystems by hiding details [OK]

Common Mistakes:

• Thinking masking speeds up simulation
• Confusing masking with code generation
• Assuming masking changes solver settings

2. Which of the following is the correct way to add a mask parameter in Simulink?

easy

A. Drag parameter block inside subsystem

B. Double-click subsystem > Add block > Parameter

C. Right-click subsystem > Properties > Add parameter

D. Right-click subsystem > Mask > Create Mask > Add parameter

Solution

1. Step 1: Locate mask creation menu

   In Simulink, you right-click the subsystem and select Mask > Create Mask to start masking.

2. Step 2: Add parameters in mask editor

   Inside the mask editor, you can add parameters to customize the subsystem interface.

3. Final Answer:

   Right-click subsystem > Mask > Create Mask > Add parameter -> Option D

4. Quick Check:

   Mask parameters added via Mask Editor [OK]

Hint: Use Mask Editor from right-click menu to add parameters [OK]

Common Mistakes:

• Trying to add parameters by adding blocks inside subsystem
• Using Properties instead of Mask menu
• Double-clicking subsystem does not add mask parameters

3. Given this mask initialization code:

gainValue = str2double(get_param(gcb, 'GainParam'));
set_param([gcb '/Gain'], 'Gain', num2str(gainValue));

What does this code do when the mask parameter GainParam changes?

medium

A. It updates the internal Gain block's Gain parameter to the new value

B. It resets the entire subsystem to default settings

C. It changes the mask parameter name to 'Gain'

D. It causes a syntax error due to missing semicolon

Solution

1. Step 1: Read the initialization code

   The code reads the mask parameter 'GainParam' as a string, converts it to a number, then sets the internal Gain block's 'Gain' parameter.

2. Step 2: Understand the effect on the subsystem

   Changing the mask parameter updates the internal block's gain value accordingly.

3. Final Answer:

   It updates the internal Gain block's Gain parameter to the new value -> Option A

4. Quick Check:

   Mask init code updates internal block parameters [OK]

Hint: Mask init code links mask params to internal blocks [OK]

Common Mistakes:

• Confusing parameter update with subsystem reset
• Thinking parameter name changes
• Assuming syntax error due to semicolon (semicolon is optional in MATLAB)

4. You created a mask with a parameter named Threshold. The initialization code is:

threshold = get_param(gcb, 'Threshold');
set_param([gcb '/Compare'], 'Threshold', threshold);

But the internal Compare block's threshold does not update. What is the likely error?

medium

A. The Compare block does not have a 'Threshold' parameter

B. The internal block parameter name is incorrect; it should be 'RelationalOperator'

C. The initialization code is missing a conversion from string to number

D. The mask parameter name 'Threshold' is misspelled in the code

Solution

1. Step 1: Check internal block parameter names

   The Compare block in Simulink does not have a parameter named 'Threshold'; it uses 'RelationalOperator' and inputs for comparison.

2. Step 2: Identify why setting 'Threshold' fails

   Since 'Threshold' is not a valid parameter, set_param silently fails or has no effect.

3. Final Answer:

   The Compare block does not have a 'Threshold' parameter -> Option A

4. Quick Check:

   Block parameters must match internal block's actual names [OK]

Hint: Verify internal block parameter names before setting [OK]

Common Mistakes:

• Assuming all mask parameters map directly to internal block parameters
• Not checking block documentation for parameter names
• Ignoring type conversions when needed

5. You want to create a masked subsystem that lets users select a filter type ('Lowpass', 'Highpass') and set a cutoff frequency. Which approach correctly connects mask parameters to internal blocks?

hard

A. Create separate subsystems for each filter type without masking

B. Add only numeric mask parameters and manually change internal blocks after simulation

C. Add popup mask parameter for filter type, numeric parameter for cutoff, then in init code set internal blocks' parameters accordingly

D. Use mask initialization code to change the mask parameters dynamically during simulation

Solution

1. Step 1: Design mask parameters for user input

   Use a popup parameter for filter type and a numeric parameter for cutoff frequency to simplify user choices.

2. Step 2: Use initialization code to update internal blocks

   In the mask initialization code, read these parameters and set the internal filter blocks' types and cutoff frequencies accordingly.

3. Final Answer:

   Add popup mask parameter for filter type, numeric parameter for cutoff, then in init code set internal blocks' parameters accordingly -> Option C

4. Quick Check:

   Mask parameters + init code = dynamic internal block setup [OK]

Hint: Use mask parameters plus init code to control internal blocks [OK]

Common Mistakes:

• Not using mask parameters for user input
• Trying to change mask parameters during simulation
• Avoiding masking by creating multiple subsystems