Variant Management in Models

% Variant Subsystem: select between petrol and diesel torque models

% Step 1: Define variant control variable (in sldd or workspace)
POWERTRAIN_TYPE = Simulink.Variant("POWERTRAIN_TYPE == 1");
% Variant 1: Petrol  (POWERTRAIN_TYPE == 1)
% Variant 2: Diesel  (POWERTRAIN_TYPE == 2)
% Variant 3: Hybrid  (POWERTRAIN_TYPE == 3)

% Step 2: In model, add Variant Subsystem block
% Add child subsystems: "Petrol", "Diesel", "Hybrid"
% Assign variant condition to each child:
%   Petrol: condition = "POWERTRAIN_TYPE == 1"
%   Diesel: condition = "POWERTRAIN_TYPE == 2"
%   Hybrid: condition = "POWERTRAIN_TYPE == 3"

% Step 3: Select variant for simulation/code gen
set_param("VehicleEMS/TorqueModel", ...
    "GeneratePreprocessorConditionals", "on");
% "on": generates #if POWERTRAIN_TYPE==1 ... #endif (compile-time)
% "off": runtime selection via if() in generated code

% Step 4: Build specific variant
set_param(model, "SystemTargetFile", "autosar.tlc");
POWERTRAIN_TYPE_val = 2;  % Diesel
slbuild(model);  % generates diesel variant only

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

• Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
• Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
• Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.