Define variant choice in Variant Source and Sink blocks.

Each variant choice in a Simulink® model is associated with a conditional expression called a variant control. The variant control that evaluates to true determines the active variant choice in the model. This example shows how to create variant controls in your model using an in-memory enumeration class. The enumeration is created using the Simulink.VariantConfigurationData function. You do not need to save the enumeration in a MATLAB® file. In code generation, enumerated types improve readability because condition values are represented as meaningful names instead of literal values.

Each variant choice in a Simulink® model is associated with a conditional expression called a variant control. The variant control which evaluates to true determines the active variant choice in the model. This example shows how to create variant controls in your model using a MATLAB® enumeration in the variant condition expressions. In code generation, enumerated types improve readability because condition values are represented as meaningful names instead of literal values.

Variant 모델은 이 모델과 연결된 여러 Variant 구성을 가질 수 있습니다. 각 구성은 Variant 제어 값의 조합을 나타내며, 이 조합으로 특정 Variant 선택지를 활성화합니다. Variant 축소기를 사용하여 단일 Variant 구성을 나타내는 Variant 모델의 축소 버전을 생성할 수 있습니다. 모델을 축소하려면 Simulink® Design Verifier™ 라이선스가 필요합니다. 이 예제에서는 프로그래밍 방식 및 Variant 관리자를 사용하여 모델을 축소하는 방법을 보여줍니다.

Verify and validate variant models with code compile variant activation time using Simulink® Design Verifier™ and Simulink Test™.

Use model reference variants. A Model block is used to reference one Simulink® model from another Simulink model. A Variant Subsystem block can contain Model blocks as variants. A variant describes one of N possible modes in which a Variant Subsystem block can operate. Each variant references a specific model with its associated model-specific arguments. For a given Variant Subsystem block, only one variant is active during simulation. You can switch the active variant by changing the values of variables in the base workspace or by manually overriding variant selection using the Variant Subsystem block dialog box.

Use the inline variant blocks — Manual Variant Source and Manual Variant Sink. The Manual Variant Source Block provides variation on the source of a signal. The block is a toggle switch that can have two or more input ports and one output port. Each input port is associated with a variant choice. Only one input port can be active during simulation, which in turn determines the active variant region. Similarly, the Manual Variant Sink block provides variation on the destination of a signal. The block can have two or more output ports and one input port. Only one output port can be active during simulation, and the blocks connected to that port determine the active variant.

The slexVariantExamples model contains a set of conceptual examples that demonstrate capabilities of Simulink® variants.

Run iterative simulations on a fog lamp controller system using fast restart. The fog lamp controller system can operate in Driver Switch mode or in Sensor Connected mode. In Driver Switch mode, the driver controls the intensity of the fog lamps. In Sensor Connected mode, a sensor adjusts the intensity of the fog lamps based on the intensity of ambient light in the external environment.

Simulate a Variant Subsystem with startup activation time using parsim. You can simulate multiple configurations in parallel with the Variant activation time set to startup using parsim. Each configuration will have one active variant.

Simulate and generate code for an export function model.

Simulate a protected model in the code compile and startup variant activation times.

Verify and validate variant models with startup variant activation time using Simulink Design Verifier and test it using Simulink Test.

Simulate Variant Source and Variant Sink blocks in accelerator and rapid accelerator mode with startup variant activation time.

Generate code with startup variant activation time. The generated code contains all variant choices with regular if statements.

Illustrates how code compile and startup variant activation time can be used together in two nested variant subsystems.

Generate a C code that contains all the active and inactive values of variant parameters. The values are enclosed in preprocessor conditionals #if and #elif that enables you to compile the code conditionally based on the condition that evaluates to true.

Generate an executable that runs for different set of variant parameter values without needing to recompile the code for each set of values.

Create a standalone executable with a Variant Subsystem using the Simulink Compiler workflow. You can use the same workflow for the Variant Source and Sink blocks as well.