Contents

Diagnostics

hisl_0043: Configuration Parameters > Diagnostics > Solver

ID: Titlehisl_0043: Configuration Parameters > Diagnostics > Solver
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Solver section to:

 

Compile-Time

  • Algebraic loop to error.

  • Minimize algebraic loop to error.

  • Unspecified inheritability of sample times to error.

  • Automatic solver parameter selection to error.

  • State name clash to warning.

 

Run-Time

  • Block priority violation to error if you are using block priorities.

Note

Enabling diagnostics pertaining to the solver provides information to detect violations of other guidelines.

If Diagnostic Parameter...Is Not Set As Indicated, Then ...
Algebraic loopAutomatic breakage of algebraic loops can go undetected and might result in unpredictable block order execution.
Minimize algebraic loopAutomatic breakage of algebraic loops can go undetected and might result in unpredictable block order execution.
Block priority violationBlock execution order can include undetected conflicts that might result in unpredictable block order execution.
Unspecified inheritability of sample timesAn S-function that is not explicitly set to inherit sample time can go undetected and result in unpredictable behavior.
Automatic solver parameter selectionAn automatic change to the solver, step size, or simulation stop time can go undetected and might the operation of generated code.
State name clashA name being used for more than one state might go undetected.

You can set the following solver diagnostic parameters to anyvalue:

Min step size violation
Sample hit time adjusting
Consecutive zero crossings violation
Solver data inconsistency
Extraneous discrete derivative signals
RationaleSupport generation of robust and unambiguous code.
Model Advisor Checks

By Task > Modeling Standards for DO-178C/DO-331 > Check safety-related diagnostic settings for solvers

References
  • IEC 61508-3, Table A.3 (3) 'Language subset'

  • ISO 26262-6, Table 1 (b) 'Use of language subsets'

  • EN 50128, Table A.4 (11) 'Language Subset'

  • DO-331, MB.6.3.3.e 'Software architecture conforms to standards'

See Also
Last ChangedR2013b

hisl_0044: Configuration Parameters > Diagnostics > Sample Time

ID: Titlehisl_0044: Configuration Parameters > Diagnostics > Sample Time
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Sample Time section to error:

 

Compile-Time

  • Source block specifies -1 sample time

  • Discrete used as continuous

  • Multitask rate transition

  • Single task rate transition

  • Multitask conditionally executed subsystem

  • Tasks with equal priority

  • Enforce sample times specified by Signal Specification blocks

If the target system does not allow preemption between tasks that have equal priority, set Tasks with equal priority to none.

 

Run-Time

Not applicable
Note

Enabling diagnostics pertaining to the solver provides information to detect violations of other guidelines.

If Diagnostic Parameter...Is Not Set As Indicated, Then ...
Source block specifies -1 sample timeUse of inherited sample times for a source block, such as Sine Wave, can go undetected and result in unpredictable execution rates for source and downstream blocks.
Discrete used as continuousInput signals with continuous sample times for a discrete block, such as Unit Delay, can go undetected. You cannot use signals with continuous sample times for embedded real-time software applications
Multitask rate transitionInvalid rate transitions between two blocks operating in multitasking mode can go undetected. You cannot use invalid rate transitions for embedded real-time software applications.
Single task rate transitionA rate transition between two blocks operating in single-tasking mode can go undetected. You cannot use single-tasking rate transitions for embedded real-time software applications.
Multitask conditionally executed subsystemsA conditionally executed multirate subsystem, operating in multitasking mode. might go undetected and corrupt data or show unexpected behavior in a target system that allows preemption.
Tasks with equal priorityTwo asynchronous tasks with equal priority might go undetected and show unexpected behavior in target systems that allow preemption.
Enforce sample times specified by Signal Specification blocksInconsistent sample times for a Signal Specification block and the connected destination block might go undetected and result in unpredictable execution rates.

RationaleASupport generation of robust and unambiguous code.
Model Advisor Checks

By Task > Modeling Standards for DO-178C/DO-331 > Check safety-related diagnostic settings for sample time

References
  • IEC 61508-3, Table A.3 (3) 'Language subset'

  • ISO 26262-6, Table 1 (b) 'Use of language subsets'

  • EN 50128, Table A.4 (11) 'Language Subset'

  • DO-331, Section MB.6.3.1.b 'High-level requirements are accurate and consistent'
    DO-331, Section MB.6.3.2.b 'Low-level requirements are accurate and consistent'
    DO-331, Section MB.6.3.3.b 'Software architecture is consistent'

See AlsoDiagnostics Pane: Sample Time in the Simulink documentation
Last ChangedR2013b

hisl_0301: Configuration Parameters > Diagnostics > Compatibility

ID: Titlehisl_0301: Configuration Parameters > Diagnostics > Compatibility
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Compatibility section to:

 

Compile-Time

S—function upgrades needed > error

 

Run-Time

Not applicable

Note

There are two categories of diagnostics — compile-time and run-time. Prior to a simulation, compile-time diagnostics run once. During a simulation, run-time diagnostics are active at every time step. Because run-time diagnostics are active during a simulation, they impact the simulation speed. For simulations outside of a verification and validation context, consider disabling run-time diagnostics.

Rationale

Improve robustness of design.

Model Advisor Checks

By Task > Modeling Standards for DO-178C/DO-331 > Check safety-related diagnostic settings for compatibility

See Also

Diagnostics Pane: Compatibility in the Simulink documentation

Last ChangedR2012b

hisl_0302: Configuration Parameters > Diagnostics > Data Validity > Parameters

ID: Titlehisl_0302: Configuration Parameters > Diagnostics > Data Validity >Parameters
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Data Validity > Parameters section to:

 

Compile-Time

Detect downcast> error

Detect precision loss> error

 

Run-Time

Detect overflow> error

Detect underflow> error

Note

There are two categories of diagnostics — compile-time and run-time. Prior to a simulation, compile-time diagnostics run once. During a simulation, run-time diagnostics are active at every time step. Because run-time diagnostics are active during a simulation, they impact the simulation speed. For simulations outside of a verification and validation context, consider disabling run-time diagnostics.

Rationale

Improve robustness of design.

Model Advisor Checks

By Task > Modeling Standards for DO-178C/DO-331 > Check safety-related diagnostic settings for parameters

See Also

Diagnostics Pane: Data Validity in the Simulink documentation

Last ChangedR2012b

hisl_0303: Configuration Parameters > Diagnostics > Data Validity > Merge block

ID: Titlehisl_0303: Configuration Parameters > Diagnostics > Data Validity > Merge block
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Data Validity > Merge block section to:

 

Compile-Time

Not applicable
 

Run-Time

Detect multiple driving blocks executing at the same time step > error

Note

There are two categories of diagnostics — compile-time and run-time. Prior to a simulation, compile-time diagnostics run once. During a simulation, run-time diagnostics are active at every time step. Because run-time diagnostics are active during a simulation, they impact the simulation speed. For simulations outside of a verification and validation context, consider disabling run-time diagnostics.

Rationale

Improve robustness of design.

See Also

Diagnostics Pane: Data Validity in the Simulink documentation

Last ChangedR2011b

hisl_0304: Configuration Parameters > Diagnostics > Data Validity > Model Initialization

ID: Titlehisl_0304: Configuration Parameters > Diagnostics > Data Validity > Model Initialization
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Data Validity > Model Initialization section to:

 

Compile-Time

Not applicable
 

Run-Time

Underspecified initialization detection > Simplified

Note

There are two categories of diagnostics — compile-time and run-time. Prior to a simulation, compile-time diagnostics run once. During a simulation, run-time diagnostics are active at every time step. Because run-time diagnostics are active during a simulation, they impact the simulation speed. For simulations outside of a verification and validation context, consider disabling run-time diagnostics.

Rationale

Improve robustness of design.

Model Advisor Checks

By Task > Modeling Standards for DO-178C/DO-331 > Check safety-related diagnostic settings for model initialization

See Also

Diagnostics Pane: Data Validity in the Simulink documentation

Last ChangedR2012b

hisl_0305: Configuration Parameters > Diagnostics > Data Validity > Debugging

ID: Titlehisl_0305: Configuration Parameters > Diagnostics > Data Validity >Debugging
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Data Validity > Debugging section to:

 

Compile-Time

Model Verification block enabling > Disable All

 

Run-Time

Not applicable
Note

There are two categories of diagnostics — compile-time and run-time. Prior to a simulation, compile-time diagnostics run once. During a simulation, run-time diagnostics are active at every time step. Because run-time diagnostics are active during a simulation, they impact the simulation speed. For simulations outside of a verification and validation context, consider disabling run-time diagnostics.

Rationale

Improve robustness of design.

See Also

Diagnostics Pane: Data Validity in the Simulink documentation

Last ChangedR2011b

hisl_0306: Configuration Parameters > Diagnostics > Connectivity > Signals

ID: Titlehisl_0306: Configuration Parameters > Diagnostics > Connectivity > Signals
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Connectivity > Signals section to:

 

Compile-Time

Not applicable

 

Run-Time

Signal label mismatch> error

Unconnected block input ports> error

Unconnected block output ports> error

Unconnected line> error

Note

There are two categories of diagnostics — compile-time and run-time. Prior to a simulation, compile-time diagnostics run once. During a simulation, run-time diagnostics are active at every time step. Because run-time diagnostics are active during a simulation, they impact the simulation speed. For simulations outside of a verification and validation context, consider disabling run-time diagnostics.

Rationale

Improve robustness of design.

Model Advisor Checks

By Task > Modeling Standards for DO-178C/DO-331 > Check safety-related diagnostic settings for signal connectivity

See Also

Diagnostics Pane: Connectivity in the Simulink documentation

Last ChangedR2012b

hisl_0307: Configuration Parameters > Diagnostics > Connectivity > Buses

ID: Titlehisl_0307: Configuration Parameters > Diagnostics > Connectivity > Buses
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Connectivity > Buses section to:

 

Compile-Time

Not applicable

 

Run-Time

Unspecified bus object at root Outport block> error

Element name mismatch > error

Mux blocks used to create bus signals > error

Non-bus signals treated as bus signals > error

Repair bus selection > Warn and repair

Note

There are two categories of diagnostics — compile-time and run-time. Prior to a simulation, compile-time diagnostics run once. During a simulation, run-time diagnostics are active at every time step. Because run-time diagnostics are active during a simulation, they impact the simulation speed. For simulations outside of a verification and validation context, consider disabling run-time diagnostics.

Rationale

Improve robustness of design.

Model Advisor Checks

By Task > Modeling Standards for DO-178C/DO-331 > Check safety-related diagnostic settings for bus connectivity

See Also

Diagnostics Pane: Connectivity in the Simulink documentation

Last ChangedR2012b

hisl_0308: Configuration Parameters > Diagnostics > Connectivity > Function calls

ID: Titlehisl_0308: Configuration Parameters > Diagnostics > Connectivity > Function calls
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Connectivity > Function calls section to:

 

Compile-Time

Invalid function-call connection > error

 

Run-Time

Context—dependent inputs > Enable all

Note

There are two categories of diagnostics — compile-time and run-time. Prior to a simulation, compile-time diagnostics run once. During a simulation, run-time diagnostics are active at every time step. Because run-time diagnostics are active during a simulation, they impact the simulation speed. For simulations outside of a verification and validation context, consider disabling run-time diagnostics.

Rationale

Improve robustness of design.

Model Advisor Checks

By Task > Modeling Standards for DO-178C/DO-331 > Check safety-related diagnostic settings that apply to function-call connectivity

See Also

Diagnostics Pane: Connectivity in the Simulink documentation

Last ChangedR2012b

hisl_0309: Configuration Parameters > Diagnostics > Type Conversion

ID: Titlehisl_0309: Configuration Parameters > Diagnostics > Type Conversion
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Type Conversion section to:

 

Compile-Time

Vector / matrix block input conversion> error

 

Run-Time

Not applicable

Note

There are two categories of diagnostics — compile-time and run-time. Prior to a simulation, compile-time diagnostics run once. During a simulation, run-time diagnostics are active at every time step. Because run-time diagnostics are active during a simulation, they impact the simulation speed. For simulations outside of a verification and validation context, consider disabling run-time diagnostics.

Rationale

Improve robustness of design.

Model Advisor Checks

By Task > Modeling Standards for DO-178C/DO-331 > Check safety-related diagnostic settings for type conversions

See Also

Diagnostics Pane: Type Conversion in the Simulink documentation

Last ChangedR2012b

hisl_0310: Configuration Parameters > Diagnostics > Model Referencing

ID: Titlehisl_0310: Configuration Parameters > Diagnostics > Model Referencing
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Model Referencing section to:

 

Compile-Time

Model block version mismatch > error

Port and parameter mismatch> error

Invalid root Inport / Outport block connection> error

Unsupported data logging > error

 

Run-Time

Not applicable

Note

There are two categories of diagnostics — compile-time and run-time. Prior to a simulation, compile-time diagnostics run once. During a simulation, run-time diagnostics are active at every time step. Because run-time diagnostics are active during a simulation, they impact the simulation speed. For simulations outside of a verification and validation context, consider disabling run-time diagnostics.

Rationale

Improve robustness of design.

Model Advisor Checks

By Task > Modeling Standards for DO-178C/DO-331 > Check safety-related diagnostic settings for model referencing

See Also

Diagnostics Pane: Model Referencing in the Simulink documentation

Last ChangedR2012b

hisl_0311: Configuration Parameters > Diagnostics > Stateflow

ID: Titlehisl_0311: Configuration Parameters > Diagnostics > Stateflow
Description

For models used to develop high-integrity systems, in the Configuration Parameters dialog box, on the Diagnostics pane, set the parameters of the Stateflow section to:

 

Compile-Time

Unexpected backtracking > error

Invalid input data access in chart initialization > error

No unconditional default transitions > error

Transitions outside natural parent > error

Transition shadowing > error

 

Run-Time

Not applicable

Note

There are two categories of diagnostics — compile-time and run-time. Prior to a simulation, compile-time diagnostics run once. During a simulation, run-time diagnostics are active at every time step. Because run-time diagnostics are active during a simulation, they impact the simulation speed. For simulations outside of a verification and validation context, consider disabling run-time diagnostics.

Rationale

Improve robustness of design.

See Also

Diagnostics Pane: Stateflow in the Simulink documentation

Last ChangedR2012b

Was this topic helpful?