Math and Data Types

hisl_0045: Configuration Parameters > Math and Data Types > Implement logic signals as Boolean data (vs. double)

ID: Titlehisl_0045: Configuration Parameters > Math and Data Types > Implement logic signals as Boolean data (vs. double)
Description

To support unambiguous behavior when using logical operators, relational operators, and the Combinatorial Logic block, select configuration parameter Implement logic signals as Boolean data (vs. double)

.
Notes

Selecting Implement logic signals as Boolean data (vs. double) enables Boolean type checking, which produces an error when blocks that prefer Boolean inputs connect to double signals. This checking results in generating code that requires less memory.

RationaleAvoid ambiguous model behavior and optimize memory for generated code.
Model Advisor Checks
  • By Task > Modeling Standards for DO-178C/DO-331 > High-Integrity Systems > Configuration > Check safety-related optimization settings for logic signals

  • By Task > Modeling Standards for IEC 61508 > High-Integrity Systems > Configuration > Check safety-related optimization settings for logic signals

  • By Task > Modeling Standards for IEC 62304 > High-Integrity Systems > Configuration > Check safety-related optimization settings for logic signals

  • By Task > Modeling Standards for EN 50128 > High-Integrity Systems > Configuration > Check safety-related optimization settings for logic signals

  • By Task > Modeling Standards for ISO 26262 > High-Integrity Systems > Configuration > Check safety-related optimization settings for logic signals

For check details, see Check safety-related optimization settings for logic signals (Simulink Check).

References
  • DO-331, MB.6.3.1.e 'High-level requirements conform to standards'
    DO-331, MB.6.3,2.e 'Low-level requirements conform to standards'

  • IEC 61508-3, Table A.3 (2) 'Strongly typed programming language’

  • IEC 62304, 5.5.3 - Software Unit acceptance criteria

  • ISO 26262-6, Table 1 (1c) 'Enforcement of strong typing'

  • EN 50128, Table A.4 (8) 'Strongly Typed Programming Language'

  • MISRA C:2012, Rule 10.1

See AlsoImplement logic signals as Boolean data (vs. double) in the Simulink documentation.
Last ChangedR2018b

hisl_0048: Configuration Parameters > Math and Data Types > Application lifespan (days)

ID: Titlehisl_0048: Configuration Parameters > Math and Data Types > Application lifespan (days)
Description

To support the robustness of systems that run continuously, set configuration parameter Application lifespan (days) to inf.

Notes

Embedded applications might run continuously. Do not assume a limited lifespan for timers and counters. When you set Application lifespan (days) to inf, the simulation time is less than the application lifespan.

RationaleSupport robustness of systems that run continuously.
Model Advisor Checks
  • By Task > Modeling Standards for DO-178C/DO-331 > High-Integrity Systems > Configuration > Check safety-related optimization settings for application lifespan

  • By Task > Modeling Standards for IEC 61508 > High-Integrity Systems > Configuration > Check safety-related optimization settings for application lifespan

  • By Task > Modeling Standards for IEC 62304 > High-Integrity Systems > Configuration > Check safety-related optimization settings for application lifespan

  • By Task > Modeling Standards for EN 50128 > High-Integrity Systems > Configuration > Check safety-related optimization settings for application lifespan

  • By Task > Modeling Standards for ISO 26262 > High-Integrity Systems > Configuration > Check safety-related optimization settings for application lifespan

For check details, see Check safety-related optimization settings for application lifespan (Simulink Check).

References
  • DO-331, Section MB.6.3.1.g 'Algorithms are accurate’
    DO-331, Section MB.6.3.2.g 'Algorithms are accurate’

  • IEC 61508-3, Table A.4 (3) 'Defensive Programming’

  • IEC 62304, 5.5.3 - Software Unit acceptance criteria

  • ISO 26262-6, Table 1 (1d) 'Use of defensive implementation techniques'

  • EN 50128, Table A.3 (1) 'Defensive Programming'

See Also
Last ChangedR2018b