Component Design
Component Documentation
- EA4-x NTC 0x0A5(0-5) WheelImbalanceRejection.html
- SF015A_WhlImbRejctn_Peer Review Checklist Design.html
This is the multi-page printable view of this section. Click here to print.
NTC Overview
NTC 0x0A5.(0-5) Wheel Imbalance Rejection
Description:
•This diagnostic logs a when computed wheel imbalance rejection command has any of the following features
–Exceeds maximum threshold
–DC trend in cancellation command
–Frequency of cancellation is incorrect
–Wheel Speed inputs are incorrect
–Persistance of cancellation command
Diagnostic Overview:
•The system function is designed to produce an cancellation command at appropriate frequency, amplitude and phase. If any of the thresholds with respect to amplitude, frequency or phase are exceeded, a diagnostic flag is set
•The diagnostic flag shuts down the wheel imbalance cancellation output wither immediately or through controlled ramping depending upon the type of fault
•The diagnostic shall also attempt to recover from the fault. Throughout the entire recovery, the final cancellation output shall be zero.
•This fault is a recovarable fault and shall reset all the internal variables to start producing the cancellation output from scratch.
Typical Fault Response:
•Response for this diagnostic is F3.
•This fault is recoverable once the values fall within an ignition cycle.
 
Probable Sources 
(Most to Least Probable):
•Improper wheel speeds information from serial communication
•Maximum magnitude due to very high wheel imbalance
•DC Trend in generated cancellation command
| Initialization | |
| Periodic | X | 
| Event | 
| Bit | Cause | 
| 0 | Maximum Magnitude Fault | 
| 2 | DC Trend Fault | 
| 3 | Frequency Diagnostic Fault | 
| 4 | Wheel Speed Correlation Fault | 
| 5 | Maximum Persistance Fault | 
| Date | Revision | Initials | 
| 08FE16 | Initial Release | JK | 
| 10Au16 | Update the bits table with 3 bits used in the NTC | PP | 
| Description of Unusual Event setting NTC | Root Cause / Explanation | 
| Date | FDD & Rev | Modifications to Diagnostic Function | 
Algorithm Changes / Lessons Learned / Revision Log

| This is the master list of questions. |  | ADVANCED FILTER CRITERIA | ||||||
| A macro is used to filter and populate separate spreadsheets for each engineering discipline. | Artifact | Domain1 | Domain2 | |||||
| Number | Artifact | Checklist Item | Domain1 | Domain2 | ||||
| 1 | dict | Is Filename of Data Dictionary in correct format? | Process | none | ||||
| 2 | dict | Is the FDD.Version property correctly updated? | Process | none | ||||
| 3 | dict | Are the following values correct for Runnables: .Context | Process | Software | Should be Architect | |||
| 4 | dict | Are the following values correct for Runnables: .TimeStep | Process | Apps | Should be Architect | |||
| 5 | dict | Are the following values correct for SrvRunnables: .Return | Process | Software | Should be Architect | |||
| 6 | dict | Are the following values correct for SrvRunnables: .Arguments | Process | Software | Should be Architect | |||
| 7 | dict | Are the following values correct for all Ip/Op/IrvSignals: .EngDT | Process | none | Should be Architect | |||
| 8 | dict | Are the following values correct for all Ip/Op/IrvSignals: .DocUnit | Process | none | Should be Architect | |||
| 9 | dict | Are the following values correct for all Ip/Op/IrvSignals: .EngInit | Process | none | Should be Architect | |||
| 10 | dict | Are the following values correct for all Ip/Op/IrvSignals: .EngMin | Process | none | Should be Architect | |||
| 11 | dict | Are the following values correct for all Ip/Op/IrvSignals: .EngMax | Process | none | Should be Architect | |||
| 12 | dict | Are the following values correct for all Ip/Op/IrvSignals: .ReadIn/WrittenIn | Process | none | ||||
| 13 | dict | Are the following values correct for all Ip/Op/IrvSignals: .ReadType/WriteType | Process | none | ||||
| 14 | dict | Are the following values correct for all Calibrations: .EngDT | SME | none | ||||
| 15 | dict | Are the following values correct for all Calibrations: .DocUnit | Apps | Process | ||||
| 16 | dict | Are the following values correct for all Calibrations: .EngMax | Apps | none | ||||
| 17 | dict | Are the following values correct for all Calibrations: .Cardinality | Apps | none | ||||
| 18 | dict | Are the following values correct for all Calibrations: .CustomerVisible | Apps | none | ||||
| 19 | dict | Are the following values correct for all Calibrations: .Impact | Apps | Safety | ||||
| 20 | dict | Are the following values correct for all Calibrations: .GraphLink | Apps | none | ||||
| 21 | dict | Are the following values correct for all Calibrations: .Monotony | Apps | none | ||||
| 22 | dict | Are the following values correct for all Calibrations: .PortName | Software | Process | ||||
| 23 | dict | Are the following values correct for all NVM: .EngDT | SME | none | ||||
| 24 | dict | Are the following values correct for all NVM: .DocUnit | Process | Apps | ||||
| 25 | dict | Are the following values correct for all NVM: .EngInit | Software | none | ||||
| 26 | dict | Are the following values correct for all NVM: .Alias | Software | none | ||||
| 27 | dict | Are the following values correct for all NVM: .InitRowCol | Software | none | ||||
| 28 | dict | Are the following values correct for all Display Variables: .EngDT | SME | none | ||||
| 29 | dict | Are the following values correct for all Display Variables: .DocUnit | Apps | none | ||||
| 30 | dict | Are the following values correct for all Display Variables: .EngMin | Software | none | ||||
| 31 | dict | Are the following values correct for all Display Variables: .EngMax | Software | none | ||||
| 32 | dict | Are the following values correct for all Display Variables: .InitRowCol | Software | none | ||||
| 33 | dict | Are the following values correct for all PIM: .EngDT | SME | none | ||||
| 34 | dict | Are the following values correct for all PIM: .DocUnit | Process | none | ||||
| 35 | dict | Are the following values correct for all PIM: .EngMin | Software | none | ||||
| 36 | dict | Are the following values correct for all PIM: .EngMax | Software | none | ||||
| 37 | dict | Are the following values correct for all PIM: .InitRowCol | Software | none | ||||
| 38 | dict | Are the following values correct for all Constants: .EngDT | SME | none | ||||
| 39 | dict | Are the following values correct for all Constants: .DocUnit | Process | none | ||||
| 40 | dict | Are the following values correct for all Calibrations: .EngVal | Apps | none | ||||
| 41 | dict | Are the following values correct for all Calibrations: .EngMin | Apps | none | ||||
| 43 | dict | Are the following values correct for all Calibrations: .TuningOwner | Safety | Apps | ||||
| 47 | dict | Are the following values correct for all Calibrations: .Online | Safety | Apps | ||||
| 44 | dict | Does the FDD .DesignASIL property match requirements? | Safety | none | ||||
| 45 | dict | Does FDD Long Name, Short Name, and Description match requirements? | Apps | Process | ||||
| 46 | dict | Do output signal ranges match requirements? | Apps | Process | ||||
| 42 | dict | Are lookup tables using compatible table dimensions? | Safety | Software | ||||
| 48 | dict | Do signal and parameter names accurately describe their purpose? | Apps | none | ||||
| 49 | dict | Do all .Description properties provide useful information? | Apps | none | ||||
| 50 | dict | Has Static Register evaluation has been completed and updated for any register data that is written to? | SME | none | ||||
| 51 | dict | Are all clients from model defined in dictionary? | Process | Software | ||||
| 52 | dict | Do client definitions match their corresponding server runnable? | Process | Software | ||||
| 53 | dict | Is NVM defined in the appropriate number of blocks (separate for EOL vs saved at power-off)? | Process | Software | ||||
| 54 | dict | Is NVM with multiple values defined as a structure? | Process | Software | ||||
| 55 | dict | Are NVM structure members arranged largest-to-smallest datatype? | Process | Software | ||||
| 56 | dict | Are local Constants unique from global constants available in xx999A dictionaries? | Process | Software | ||||
| 57 | dict | Are calibration tables named correctly (e.g. AssiX and AssiY)? | Process | Apps | ||||
| 58 | dict | Are Constant names abbreviated properly (ALLCAPS are not checkable by tools)? | Process | none | ||||
| 59 | dict | Is the Data Dictionary Verification report error free? | Process | none | ||||
| 60 | dict | Are all data types represented by released Data_Management classes? | Process | none | ||||
| 61 | model | Are all the Memory Store blocks for PIM and Display Variables located on the 2nd level of model? | Process | Software | ||||
| 62 | model | Is each diagnostic (NTC) capable of being set to "PASS"? | Process | Software | ||||
| 63 | model | Does non-zero intialization of PIM occur in the function's Init runnable? | Process | Software | ||||
| 64 | model | Does design properly include Set Ram Block Status when NVM RAM values change? | Process | Software | ||||
| 65 | model | Are NTCs set only outside an IRQ (not related to the typical periodic OS)? | Process | Software | ||||
| 66 | model | Are NTCs set and read only at periodic steps no less than 2 ms? | Process | Software | ||||
| 67 | model | Does model execute without errors/warnings after loading NxtrMBDConfig configuration set? | Process | Apps | ||||
| 68 | model | Is filename of model in correct format? | Process | none | ||||
| 69 | model | Is Top level of model annotated with Requirements Baseline? | Process | none | ||||
| 70 | model | Is the Top level of the model annotated with Tool Dependencies? | Process | none | ||||
| 71 | model | Is Top level of model annotated with Change Log or History? | Process | none | ||||
| 72 | model | Is the 2nd level of model free from subsystems that are not Function-Call Subsystems? | Process | none | ||||
| 73 | model | Is the 2nd level of model free from arithmetic and logic operations? | Process | none | ||||
| 74 | model | Are the Runnable trigger signals named as "call_<Runnable>"? | Process | none | ||||
| 75 | model | Does 2nd level of model have a properly updated annotation with name, description, and intended baseline number? | Process | none | ||||
| 76 | model | Are all data flow layers free of Function-Call Subsystems and Memory Store blocks? | Process | none | ||||
| 77 | model | Does the Model have the confidentiality and copyright information inside all its Subsystems? | Process | none | ||||
| 78 | model | Are all requirements links of the format <FDDNumber>_<ObjectID>? | Process | none | ||||
| 79 | model | Does requirements HTML report reference only the DOORS module of this component for all links in the design? | Process | none | ||||
| 80 | model | Was Model Advisor run with the correct configuration settings? | Process | none | ||||
| 81 | model | Is the Model Advisor rerport free from "Fails". | Process | none | ||||
| 82 | model | Does the model execute? | Process | none | ||||
| 83 | model | Are Model Advisor report ISO26262 warnings acceptable? | Safety | none | ||||
| 84 | model | Is model free from dynamic array size allocation? | Safety | Software | ||||
| 85 | model | Does model include adequate annotation throughout? | Apps | none | ||||
| 86 | model | Is model free from data type conversion blocks that do not explicitly state desired data type? | Safety | Software | ||||
| 87 | model | Does model refrain from using Display Variable values in downstream operations? | Safety | Software | ||||
| 88 | model | Are all GOTO/FROM blocks restricted in scope to their own subystem level? | Safety | Software | ||||
| 89 | model | If model has ADC input, is failure boolean input and appropriate fault response been included? | Safety | Process | ||||
| 90 | model | Does design calculate PIM values only within their defined range? | Software | none | ||||
| 91 | model | Does design include output limiting blocks? | Software | Safety | ||||
| 92 | model | Do cal ranges & logic ensure freedom from divide-by-zero? | Software | Safety | ||||
| 93 | model | Do cal ranges & logic ensure no incompatible values for their datatype? | Software | Process | ||||
| 94 | model | Are Model Advisor report MISRA warnings acceptable? | Software | none | ||||
| 95 | model | Is design free of unreachable logic? | Software | none | ||||
| 96 | model | Do state machines provide exits of all non-latch states? | Software | none | ||||
| 97 | model | Is design free from recursive logic that could cause indefinate waits? | Software | none | ||||
| 98 | model | Does design maintain data size consistency? | Software | none | ||||
| 99 | model | Are "magic numbers" acceptable? | Process | Software | ||||
| 100 | model | Are the following values correct for all NTC: .NtcTyp | Apps | Safety | ||||
| 101 | model | Are display variables appropriately placed? | Apps | none | ||||
| 102 | model | Does design provide appropriate tuning flexibility? | Apps | none | ||||
| 103 | model | Are blocks linked to the correct requirements? (watch for problems due to copy/pasted blocks) | Apps | none | ||||
| 104 | model | Is the list of unlinked blocks acceptable? | Apps | none | ||||
| 105 | model | Does design account for all requirements? | Apps | none | ||||
| 106 | model | Is design of a managable size and easy to understand? | Apps | Software | ||||
| 107 | model | Is design easily disabled via calibration? | Apps | none | ||||
| 108 | model | Does model include appropriate logic for dealing with missing or corrupted NVM data? | SME | Safety | ||||
| 109 | model | Does design either work with global signal units or contain necessary unit-conversion logic? | SME | Apps | ||||
| 110 | model | Does the design prevent Integrator drifting? | SME | none | ||||
| 111 | model | Does design make proper use of limiters to prevent integrator windup and runaway values? | SME | none | ||||
| 112 | model | Are all IIR filters free of potential instability over their defined calibration ranges? | SME | none | ||||
| 113 | model | Is Stateflow used only for state machines not easily represented in Simulink? | Software | none | ||||
| 114 | model | Do IF..ELSEIF blocks also contain an ELSE condition? | Process | none | ||||
| 115 | model | Do SWITCH CASE blocks also contain a DEFAULT condtion? | Process | none | ||||
| 116 | model | Are ELSE and DEFAULT branching conditions reachable when dependent on internal variables? | Process | none | ||||
| 117 | model | Is model free from over-nested IF logic or redundant IF..ELSEIF..ELSEIF.. Conditions? | Software | none | ||||
| 118 | model | Is model free from arithmetic operations on Boolean values? | Software | none | ||||
| 119 | model | Is model optimized to minimize redundant calculations? | Process | none | ||||
| 120 | package | Does NTC Summary sheet adequately describe NTC usage? | Apps | none | ||||
| 121 | package | Does review meet 'inspection' criteria? | Safety | Process | ||||
| 122 | package | Does Design folder contain only the model, data dictionary, and (optionally) a simulation setup script? | Process | none | ||||
| 123 | package | Does Doc folder contain a zipped HTML webview model? | Process | none | ||||
| 124 | package | Was webview model created without requirements highlighted? | Process | none | ||||
| 125 | package | Does Doc folder contain appropriate number of NTC Summary sheets? | Process | none | ||||
| 126 | package | Does Reports folder contain only the data dictionary verification report, Model Advisor report, and zipped requirements traceability report? | Process | none | ||||
| 127 | package | Has author performed basic simulations to screen for problems? | SME | none | ||||
| Rev | Change | Author | 
| 01.00.05 | Added lesson learned #3.5 | MDK | 
| 01.00.06 | Added lesson learned #3.6, 3.7 - Structure and writing of NVM in mfiles and models. | MDK | 
| 02.00.00 | Combined ESG and Systems into one, compatible with Data_Management 2.13.0 of CreateDD and VerifyDD. | K. Derry | 
| 02.01.00 | Added: Does FDD.DesignASIL match requirements? Added: Was webview model created without requirements highlighted? Removed: Redundant row in Data Dictionary section. Formatting: Column C now consistently center-justified. | K. Derry | 
| 02.02.00 | Added: Are all data types represented by released Data_Management classes? Removed: Are all runnables defined? Rationale: Automated tools checking. Removed: Does the Component shortname match data dictionary FDD metadata? Removed: "Data store name must resolve to Simulink signal object" Edited: Model Advisor report should now be left unzipped. | K. Derry | 
| 3.0.0 | New concept of discipline-specific checklists. New sheets for Project Info, Safety, Software, Apps, SME, and Master. New VBA code to distribute master list onto appropriate discipline sheets. Major reformatting, many line item checks added/deleted/modified. | K. Derry | 
| Model Advisor Report - SF015A_WhlImbRejctn.slx | |
| Simulink version: 8.2 | Model version: 1.411 | 
| System: SF015A_WhlImbRejctn | Current run: 13-Feb-2017 16:41:12 | 
| Model Advisor configuration: ...NxtrModelAdvisorConfig.mat | |
| Pass | Fail | Warning | Not Run | Total | 
|  |  |  |  | 359 | 
You should turn on the following optimization(s):
| none. | |
Your model contains root-level Inport blocks with undefined attributes, such as dimensions, sample time, or data type. If you do not explicitly define these attributes, Simulink will use back-propagation from downstream blocks to assign values to the attributes when updating the model. This can lead to undesired simulation results. To avoid this, fully define the attributes of all of your model's root-level Inport blocks.
The following root-level Inport blocks have undefined attributes:
SF015A_WhlImbRejctn/WhlImbRejctnDi
Identify Inport blocks in the top-level of the model with missing or inherited sample times, data types, or port dimensions
Warning
The following Inport blocks have undefined or inherited sample times, data types or port dimensions
| Inport | Link | Conditions | 
| 1 | SF015A_WhlImbRejctn/HwTq | Missing port dimension Missing signal data type Missing port sample time | 
| 2 | SF015A_WhlImbRejctn/WhlLeFrq | Missing port dimension Missing signal data type Missing port sample time | 
| 3 | SF015A_WhlImbRejctn/WhlRiFrq | Missing port dimension Missing signal data type Missing port sample time | 
| 4 | SF015A_WhlImbRejctn/VehSpdVld | Missing port dimension Missing signal data type Missing port sample time | 
| 5 | SF015A_WhlImbRejctn/VehSpd | Missing port dimension Missing signal data type Missing port sample time | 
| 6 | SF015A_WhlImbRejctn/WhlImbRejctnDi | Missing port dimension Missing signal data type Missing port sample time | 
| 7 | SF015A_WhlImbRejctn/WhlImbRejctnCustEna | Missing port dimension Missing signal data type Missing port sample time | 
| 8 | SF015A_WhlImbRejctn/WhlFrqVld | Missing port dimension Missing signal data type Missing port sample time | 
| 9 | SF015A_WhlImbRejctn/SysSt | Missing port dimension Missing signal data type Missing port sample time | 
Identify blocks not supported by code generation or not recommended for C/C++ production code deployment.
Warning
The following blocks are not supported or not recommended for C/C++ production code deployment:
| Block | Block Type | Code generation support | Recommendation for C/C++ production code deployment | 
| SF015A_WhlImbRejctn/Clock | Clock | Yes | No | 
| SF015A_WhlImbRejctn/Step2 | Step | Yes | No | 
| SF015A_WhlImbRejctn/Step3 | Step | Yes | No | 
| SF015A_WhlImbRejctn/Step4 | Step | Yes | No | 
Compares the state machine type of all Stateflow charts to the desired type.
Check for Classic state machines
Identify Stateflow charts using the Classic state machine type.
Warning
The following charts using Classic state machines were found in the model:
Check for Mealy state machines
Identify Stateflow charts using the Mealy state machine type.
Passed
No charts using Mealy state machines were found in the model.
_________________________________________________________________________________________
Check for Moore state machines
Identify Stateflow charts using the Moore state machine type.
Passed
No charts using Moore state machines were found in the model.
| Name | Value | 
| State Machine Type | Common | 
Check Simulink blocks and Stateflow objects that do not link to a requirements document
Warning
The following blocks do not link to a requirement document:
Identify subsystem names that use characters that are not correct in C code.
See Also
Identify names of Inport or Outport blocks that use characters that are not correct in C code.
See Also
| Error | Incorrect port block | 
| Name contains incorrect characters. | ..../Adaptive Filter - FloatingL/x Ref | 
| Name contains incorrect characters. | ..../Adaptive Filter - FloatingR/x Ref | 
| Name contains incorrect characters. | ..../Input Signal | 
| Name contains incorrect characters. | ..../Signal Frequency [Hz] | 
| Name starts with a number [0123456789]. | ..../Filter 1/1//Mag | 
| Name starts with a number [0123456789]. | ..../Filter 2/1//Mag | 
| Name contains incorrect characters. | ..../Enable Ramp/Enable In | 
| Name contains incorrect characters. | ..../Determine Enabled Amt/Enable Ramp/RampY | 
| Name contains incorrect characters. | ..../WIR Diagnostics/SlowSpeedDiagc | 
| Name contains incorrect characters. | ..../Diagnostic Threshold/Fault Present | 
| Name contains incorrect characters. | ..../WIR Diagnostics/Set NTC Block/DC Trend | 
| Name contains incorrect characters. | ..../Update Persistence Band 3/NVM Var | 
| Name contains incorrect characters. | ..../Update Persistence Band1/NVM Var | 
| Name contains incorrect characters. | ..../Update Persistence Band2/NVM Var | 
| Name starts with a number [0123456789]. | ..../CalcZeroPole/1//Mag at freq | 
| Name starts with a number [0123456789]. | ..../Calc Filter Coefficients/1//Mag | 
| Name contains incorrect characters. | ..../Adjusted Signal | 
| Name contains incorrect characters. | ..../SpanTi | 
| Name contains incorrect characters. | ..../Enable Ramp/Ramped Enable | 
| Name contains incorrect characters. | ..../SpanTi | 
| Name contains incorrect characters. | ..../SpanTi | 
| Name contains incorrect characters. | ..../SpanTi | 
| Name contains incorrect characters. | ..../EnableDiag/Notch Comparison/UGR /y Filt | 
| Name contains incorrect characters. | ..../SpanTi | 
| Name contains incorrect characters. | ..../Tapped Signal | 
| Name contains incorrect characters. | ..../Tapped Signal | 
| Name contains incorrect characters. | ..../UGR L/y Filt | 
| Name contains incorrect characters. | ..../UGR R/y Filt | 
| Name contains incorrect characters. | ..../SpanTi | 
| Name contains incorrect characters. | ..../SpanTi | 
| Name contains incorrect characters. | ..../SpanTi | 
| Name contains incorrect characters. | ..../SpanTi | 
| Name contains incorrect characters. | ..../WhlImbRejctnPer2/SlowSpeedDiagc | 
Identify signal labels that are not correct for C variable names.
See Also
Identify block names that use characters that are not correct in C code.
See Also
| Error type | Block | 
| Name contains incorrect characters. | ..../Function-Call Generator | 
| Name contains incorrect characters. | ..../Function-Call Generator | 
| Name contains incorrect characters. | ..../Function-Call Generator | 
Identify levels in the model that include basic blocks and subsystems. Each level of a model must be designed with blocks of the same level (for example, only subsystems or only basic blocks).
See Also
Identify nonstandard display attributes in Simulink diagrams.
See Also
Check format settings
Identify incorrect model-level format options.
Warning
The following format display options are incorrect.
| Display Attribute | Recommended Value | Actual Value | 
| Display > Signals & Ports > Wide Nonscalar Lines | on | off | 
| View > Model Browser Options > Model Browser | off | on | 
| Display > Library Links > All | none | disabled | 
Check block colors
Identify blocks using nonstandard colors.
Warning
The following blocks use nonstandard colors:
Check canvas colors
Identify canvases that are not white.
Passed
All diagrams use a white canvas.
_________________________________________________________________________________________
Check diagram zoom
Identify diagrams that do not have zoom factor set to 100 %.
Warning
The following diagrams do not have zoom factor set to 100 percent:
Identify whether to display block names.
See Also
Check for blocks with hidden names and obvious function
Identify block names that are displayed but can be hidden due to obvious behavior.
Passed
All blocks with obvious behavior have hidden names.
_________________________________________________________________________________________
Check for non-descriptive displayed block names
Identify block names that are displayed but should be hidden due to a lack of a descriptive name.
Warning
The following blocks have a name displayed, however, the name is not descriptive:
Check for missing block names
Identify block names that are hidden but should be displayed to show a descriptive name.
Warning
The following blocks have descriptive names, however, the names are hidden:
Identify Trigger and Enable blocks that are not centered in the upper third of the model diagram.
See Also
Identify blocks that require labeled signals. A subset of source and destination blocks require labeled signals.
See Also
Check source block labels
The following source blocks require labeled signals; Inport, From, Data Store Read, Constant, Bus Selector, Demux, Selector. If the signal name is visible on the block, this rule is considered met.
Warning
The following signals have no label:
Check destination block labels
The following destination blocks require labeled signals; Outport, Goto, Data Store Write, Bus Creator, Mux, Subsystem, Chart. If the signal name is visible on the source block, this rule is considered met.
Warning
The following signals have no label:
Identify propagated labels on signal lines.
See Also
Check subsystem block input labels
Identify inputs to subsystem blocks to verify that the signals have labels.
Warning
The following subsystem-level Inport block signals should propagate signal labels from the parent system.
Check subsystem output labels
Identify signals originating in Subsystem blocks to verify that the signals have labels.
Warning
The following signal labels are not propagated. Propagate signals coming from Subsystem blocks.
Signal propagation for nonsubsystem blocks
Identify the signal propagation status for both transformative and nontransformative blocks.
Passed
All outputs from non subsystem blocks correctly use labels and display propagated signals.
Identify blocks that are not allowed in discrete controllers. Prohibited blocks include all continuous blocks and some source and sink blocks.
See Also
Identify blocks not supported by code generation or not recommended for C/C++ production code deployment.
Warning
The following blocks are not supported or not recommended for C/C++ production code deployment:
| Block | Block Type | Code generation support | Recommendation for C/C++ production code deployment | 
| SF015A_WhlImbRejctn/Clock | Clock | Yes | No | 
| SF015A_WhlImbRejctn/Step2 | Step | Yes | No | 
| SF015A_WhlImbRejctn/Step3 | Step | Yes | No | 
| SF015A_WhlImbRejctn/Step4 | Step | Yes | No | 
Identify blocks that use zero-based indexing.
See Also
Identify transitions in Stateflow flowcharts that are drawn incorrectly.
See Also
Check for conditions drawn vertically
Condition expressions should be drawn on the horizontal segments of flowcharts.
Warning
The following transitions have condition expressions that are not horizontal:
Check for action transitions drawn vertically
Transition actions should be drawn on the vertical segments of flowcharts.
Warning
The following transitions have action expressions that are not vertical:
Check for junctions for default transitions
All Junctions in a flow chart should have a default exit transition.
Warning
The following Junctions do not have a default exit transition:
Check for transitions that combine condition and action
Flowcharts should not combine condition evaluations and action expressions in a single transition.
Warning
The following transition have a mixture of condition and assignment actions:
This model contains the following C-MEX S-functions:
Consider setting Solver data inconsistency [?] to either error or warning (currently set to none) to validate whether S-functions adhere to the ODE solver consistency rules that Simulink applies to its built-in blocks.
Consider setting ArrayBounds exceeded [?]to either error or warning (currently set to none) to check if S-functions are writing outside array boundaries.
Note: These runtime diagnostics may slow down simulation considerably. You should set them back to none once you have verified that they do not cause any warnings or errors during simulation.
SF015A_WhlImbRejctn/Data Store Memory
SF015A_WhlImbRejctn/Data Store Memory1
SF015A_WhlImbRejctn/Data Store Memory10
SF015A_WhlImbRejctn/Data Store Memory11
SF015A_WhlImbRejctn/Data Store Memory12
SF015A_WhlImbRejctn/Data Store Memory13
SF015A_WhlImbRejctn/Data Store Memory14
SF015A_WhlImbRejctn/Data Store Memory2
SF015A_WhlImbRejctn/Data Store Memory3
SF015A_WhlImbRejctn/Data Store Memory4
SF015A_WhlImbRejctn/Data Store Memory5
SF015A_WhlImbRejctn/Data Store Memory6
SF015A_WhlImbRejctn/Data Store Memory7
SF015A_WhlImbRejctn/Data Store Memory8
SF015A_WhlImbRejctn/Data Store Memory9
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory1
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory10
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory11
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory12
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory13
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory14
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory15
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory16
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory17
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory18
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory19
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory2
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory20
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory21
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory22
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory23
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory24
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory25
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory26
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory27
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory28
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory29
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory3
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory30
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory31
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory32
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory33
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory34
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory35
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory36
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory37
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory38
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory39
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory4
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory40
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory41
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory42
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory43
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory44
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory45
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory46
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory47
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory48
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory49
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory5
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory50
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory51
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory52
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory53
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory54
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory55
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory56
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory57
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory58
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory59
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory6
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory60
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory61
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory62
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory63
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory64
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory65
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory66
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory67
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory7
SF015A_WhlImbRejctn/Data Store Memory
SF015A_WhlImbRejctn/Data Store Memory1
SF015A_WhlImbRejctn/Data Store Memory10
SF015A_WhlImbRejctn/Data Store Memory11
SF015A_WhlImbRejctn/Data Store Memory12
SF015A_WhlImbRejctn/Data Store Memory13
SF015A_WhlImbRejctn/Data Store Memory14
SF015A_WhlImbRejctn/Data Store Memory2
SF015A_WhlImbRejctn/Data Store Memory3
SF015A_WhlImbRejctn/Data Store Memory4
SF015A_WhlImbRejctn/Data Store Memory5
SF015A_WhlImbRejctn/Data Store Memory6
SF015A_WhlImbRejctn/Data Store Memory7
SF015A_WhlImbRejctn/Data Store Memory8
SF015A_WhlImbRejctn/Data Store Memory9
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory1
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory10
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory11
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory12
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory13
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory14
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory15
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory16
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory17
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory18
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory19
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory2
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory20
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory21
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory22
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory23
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory24
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory25
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory26
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory27
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory28
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory29
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory3
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory30
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory31
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory32
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory33
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory34
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory35
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory36
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory37
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory38
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory39
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory4
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory40
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory41
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory42
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory43
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory44
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory45
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory46
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory47
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory48
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory49
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory5
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory50
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory51
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory52
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory53
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory54
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory55
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory56
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory57
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory58
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory59
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory6
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory60
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory61
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory62
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory63
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory64
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory65
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory66
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory67
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory7
SF015A_WhlImbRejctn/Data Store Memory
SF015A_WhlImbRejctn/Data Store Memory1
SF015A_WhlImbRejctn/Data Store Memory10
SF015A_WhlImbRejctn/Data Store Memory11
SF015A_WhlImbRejctn/Data Store Memory12
SF015A_WhlImbRejctn/Data Store Memory13
SF015A_WhlImbRejctn/Data Store Memory14
SF015A_WhlImbRejctn/Data Store Memory2
SF015A_WhlImbRejctn/Data Store Memory3
SF015A_WhlImbRejctn/Data Store Memory4
SF015A_WhlImbRejctn/Data Store Memory5
SF015A_WhlImbRejctn/Data Store Memory6
SF015A_WhlImbRejctn/Data Store Memory7
SF015A_WhlImbRejctn/Data Store Memory8
SF015A_WhlImbRejctn/Data Store Memory9
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory1
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory10
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory11
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory12
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory13
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory14
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory15
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory16
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory17
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory18
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory19
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory2
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory20
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory21
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory22
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory23
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory24
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory25
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory26
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory27
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory28
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory29
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory3
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory30
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory31
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory32
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory33
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory34
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory35
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory36
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory37
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory38
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory39
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory4
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory40
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory41
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory42
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory43
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory44
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory45
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory46
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory47
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory48
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory49
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory5
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory50
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory51
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory52
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory53
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory54
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory55
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory56
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory57
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory58
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory59
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory6
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory60
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory61
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory62
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory63
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory64
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory65
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory66
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory67
SF015A_WhlImbRejctn/WhlImbRejctn/Data Store Memory7
Note: These runtime diagnostics may slow down simulation considerably. You should set them back to Disable all once you have verified that they do not cause any warnings or errors during simulation.