| Type | Trigger | Generated Code | Automotive Use |
|---|---|---|---|
| Virtual | Always (with parent) | Inlined into parent function | Organisation only; no separate function |
| Atomic | Always | Separate C function void Func_step() | Unit-testable component |
| Enabled | When Enable port != 0 | Function with conditional call | Active only in certain modes |
| Triggered | On rising/falling/either edge | Function called on trigger | Event-driven (CAN message Rx) |
| Function-Call | Called by Stateflow or Scheduler block | Explicit function call | AUTOSAR Runnable; OS task body |
Subsystem Types and Generated Code
Model Reference Architecture
Model Reference Hierarchy
VehicleEMS.slx (top-level)
|
+-- [Model Block] AirPathControl.slx
| separate .slx file
| compiled to separate .o for code gen
| incremental compile: only rebuilds when changed
|
+-- [Model Block] FuelControl.slx
|
+-- [Model Block] IgnitionControl.slx
|
+-- [Model Block] DiagnosticManager.slx
Benefits of Model Reference:
- Separate versioning: each .slx has own Git history
- Parallel development: different engineers own different .slx files
- Independent unit testing: test each .slx in isolation
- Reuse: same model referenced in multiple top-level models
- Incremental build: unchanged models skip compilationAtomic Subsystem Configuration
MATLABatomic_subsystem_cfg.m
% Set subsystem as Atomic (generates separate C function)
% Right-click subsystem > Block Parameters > Treat as atomic unit
set_param("VehicleEMS/SpeedController", ...
"TreatAsAtomicUnit", "on");
% Generates:
% void SpeedController_step(SpeedController_inputs_T *in,
% SpeedController_outputs_T *out)
% { ... }
% Create Model Reference:
% 1. Create AirPathControl.slx with inports/outports
% 2. In parent: add Model block from Library Browser
% 3. Set Model block "Model name" = "AirPathControl"
% 4. Connect ports to match AirPathControl interface
% Verify model reference compatibility:
[status, reasons] = modelrefsim("VehicleEMS/AirPathControl");
if ~isempty(reasons)
disp("Incompatible:"); disp(reasons);
end
% Build all referenced models for code generation:
slbuild("VehicleEMS"); % builds all referenced models firstSummary
The Atomic Subsystem vs Model Reference choice has significant project management implications beyond code generation. For multi-engineer teams, Model Reference is essential: each engineer owns a separate .slx file that can be independently checked out, modified, reviewed, and tested. Atomic Subsystems inside a single .slx file create merge conflicts when multiple engineers edit the top-level model simultaneously. The rule: if a component will be reused across multiple top-level models (e.g., a common PID library used by both engine and transmission controllers), or owned by a separate team, use Model Reference. If it is a one-off component inside a single engineers model, Atomic Subsystem is simpler.
🔬 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.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.