Fixed-Point Design & Scaling

% Overflow mode on Discrete-Time Integrator:
% "Wrap"     -- silent wraparound (fastest; unsafe for safety signals)
% "Saturate" -- clamp to min/max (REQUIRED for safety-critical)
set_param("MyModel/SpeedIntegrator", ...
    "OutDataTypeStr",             "fixdt(1,32,8)", ...
    "SaturateOnIntegerOverflow",  "on");

% Rounding mode for Data Type Conversion blocks:
% "Floor"    -- truncate toward -inf (fast; biased for signed)
% "Nearest"  -- round half-up (MAAB recommended; unbiased)
% "Zero"     -- truncate toward zero (ISO C truncation)

% Fixed-Point Tool workflow:
% 1. Simulate with double (reference output)
% 2. Fixed-Point Tool: Analysis > Fixed-Point Tool
% 3. Run simulation; collect signal ranges
% 4. Propose data types: Fixed-Point Tool > Convert > Apply
% 5. Run again with proposed types
% 6. Back-to-back comparison: compare to step 1 output
% 7. Check overflow events: must be zero
% 8. Check precision loss: quantisation error within spec

🔬 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.