Component Design

Check for potentially delayed function-call block return values

Not Run

Not Run

Identify block output signals with continuous sample time and non-floating point data type

Not Run

Check Merge block usage

Not Run

Check consistency of initialization parameters for Outport and Merge blocks

Not Run

Check data store block sample times for modeling errors

Not Run

Check for potential ordering issues involving data store access

Not Run

Identify questionable operations for strict single-precision design

Not Run

Simulink Coder

Identify blocks using one-based indexing

Not Run

Check solver for code generation

Not Run

Check for blocks not supported by code generation

Not Run

Check for blocks that have constraints on tunable parameters

Not Run

Check for model reference configuration mismatch

Not Run

Check sample times and tasking mode

Not Run

Embedded Coder

Check for blocks not recommended for C/C++ production code deployment

Not Run

Identify lookup table blocks that generate expensive out-of-range checking code

Not Run

Check output types of logic blocks

Not Run

Check the hardware implementation

Not Run

Identify questionable software environment specifications

Not Run

Identify questionable code instrumentation (data I/O)

Not Run

Check for blocks not recommended for MISRA-C:2004 compliance

Not Run

Check configuration parameters for MISRA-C:2004 compliance

Not Run

Identify questionable subsystem settings

Not Run

Identify blocks that generate expensive fixed-point and saturation code

Not Run

Identify questionable fixed-point operations

Not Run

Identify blocks that generate expensive rounding code

Not Run

Simscape

Check consistency of block parameter units

Not Run

Check for outdated Simscape blocks

Not Run

Simulink Verification and Validation

Modeling Standards

DO-178C/DO-331 Checks

Not Run

Check for blocks that do not link to requirements

Not Run

Check usage of Math blocks

Not Run

Check Stateflow charts for ordering of states and transitions

Not Run

Not Run

Check Stateflow debugging options

Not Run

Check usage of lookup table blocks

Not Run

Check for blocks not recommended for C/C++ production code deployment

Not Run

Not Run

Check Stateflow charts for uniquely defined data objects

Not Run

Not Run

Not Run

Not Run

Check for MATLAB Function block interfaces with inherited properties

Not Run

Not Run

IEC 61508, ISO 26262, and EN 50128 Checks

Not Run

Display model version information

Not Run

Not Run

Not Run

Not Run

Not Run

Check for blocks not recommended for C/C++ production code deployment

Not Run

Not Run

Check for model objects that do not link to requirements

Not Run

Not Run

Not Run

Not Run

Check for MATLAB Function block interfaces with inherited properties

Not Run

Not Run

Check for root Inports with missing range definitions

Not Run

Not Run

Check for root Outports with missing range definitions

Not Run

Not Run

MathWorks Automotive Advisory Board Checks

Not Run

Check font formatting

Not Run

Check transition orientations in flowcharts

Not Run

Check for nondefault block attributes

Not Run

Check signal line labels

Not Run

Check for propagated signal labels

Not Run

Check default transition placement in Stateflow charts

Not Run

Check return value assignments of graphical functions in Stateflow charts

Not Run

Check entry formatting in State blocks in Stateflow charts

Not Run

Check usage of return values from a graphical function in Stateflow charts

Not Run

Check for pointers in Stateflow charts

Not Run

Check for event broadcasts in Stateflow charts

Not Run

Check transition actions in Stateflow charts

Not Run

Check for MATLAB expressions in Stateflow charts

Not Run

Check for indexing in blocks

Not Run

Check file names

Not Run

Check folder names

Not Run

Check for prohibited blocks in discrete controllers

Not Run

Check for prohibited sink blocks

Not Run

Check positioning and configuration of ports

Not Run

Check for matching port and signal names

Not Run

Check whether block names appear below blocks

Not Run

Check for mixing basic blocks and subsystems

Not Run

Check for unconnected ports and signal lines

Not Run

Check position of Trigger and Enable blocks

Not Run

Check use of tunable parameters in blocks

Not Run

Check Stateflow data objects with local scope

Not Run

Check for Strong Data Typing with Simulink I/O

Not Run

Check usage of exclusive and default states in state machines

Not Run

Check Implement logic signals as Boolean data (vs. double)

Not Run

Check model diagnostic parameters

Not Run

Check the display attributes of block names

Not Run

Check display for port blocks

Not Run

Check subsystem names

Not Run

Check port block names

Not Run

Check character usage in signal labels

Not Run

Check character usage in block names

Not Run

Check Trigger and Enable block names

Not Run

Check for Simulink diagrams using nonstandard display attributes

Not Run

Check visibility of block port names

Not Run

Check orientation of Subsystem blocks

Not Run

Check configuration of Relational Operator blocks

Not Run

Check use of Switch blocks

Not Run

Check for signal bus and Mux block usage

Not Run

Check for bitwise operations in Stateflow charts

Not Run

Check for comparison operations in Stateflow charts

Not Run

Check for unary minus operations on unsigned integers in Stateflow charts

Not Run

Check for equality operations between floating-point expressions in Stateflow charts

Not Run

Check input and output settings of MATLAB Function blocks

Not Run

Check for mismatches between names of Stateflow ports and associated signals

Not Run

Not Run

Check scope of From and Goto blocks

Not Run

Requirements Consistency

Identify requirement links with missing documents

Not Run

Identify requirement links that specify invalid locations within documents

Not Run

Identify selection-based links having description fields that do not match their requirements document text

Not Run

Identify requirement links with path type inconsistent with preferences

Not Run

Simulink Control Design

Identify time-varying source blocks interfering with frequency response estimation

Not Run

By Task

Code Generation Efficiency

Check optimization settings

You should turn on the following optimization(s):

	Block reduction
	Remove code from floating-point to integer conversions that wraps out-of-range values
	Inline invariant signals
	The Simulation range checking diagnostic is enabled. Because this diagnostic can increase the time it takes to simulate your model, you should consider turning it off, by setting its value to `none`.
	Ignore testpoints when generating code
	Pass reusable subsystem outputs as individual arguments

Identify blocks using one-based indexing

Check the model for blocks configured for one-based indexing

Warning
The following blocks use one-based indexing:

Recommended Action
Set the index to use zero-based indexing and update the supporting blocks as required.
_________________________________________________________________________________________

Check for blocks requiring one-based indexing

Passed
No blocks requiring one-based indexing were found

Identify questionable software environment specifications

Passed

Identify lookup table blocks that generate expensive out-of-range checking code

These settings can lead to inefficient code generation when inputs always fall within the range of valid breakpoint values for lookup table blocks, including Lookup Table blocks, Prelookup blocks and Interpolation blocks.

Passed
The lookup table blocks have been configured to generate range-checking free code.

Identify questionable code instrumentation (data I/O)

Passed

Check output types of logic blocks

Identify logic blocks that are outputting non-Boolean data types.

Passed
All logic blocks are being used appropriately.

Identify blocks that generate expensive rounding code

Not Run

Identify questionable fixed-point operations

Not Run

Identify blocks that generate expensive fixed-point and saturation code

Not Run

Frequency Response Estimation

Identify time-varying source blocks interfering with frequency response estimation

Not Run

Managing Data Store Memory Blocks

Check Data Store Memory blocks for multitasking, strong typing, and shadowing issues

Not Run

Check data store block sample times for modeling errors

Not Run

Check for potential ordering issues involving data store access

Not Run

Managing Library Links And Variants

Identify disabled library links

Passed

Identify parameterized library links

Passed

Identify unresolved library links

Passed

Identify model reference variants and variant subsystems that override variant choice

Identify model or subsystem for model reference variants and variant subsystems that specify variant choice using the override option instead of using the active variant control.

Passed
No model reference variants or variant subsystems found which override their choice.

Model Referencing

Check for model reference configuration mismatch

Not Run

Check for parameter tunability information ignored for referenced models

Passed

Check for implicit signal resolution

Passed

Check root model Inport block specifications

Not Run

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:

SF104A_MotCurrRegCfg/MotInduDaxEstimd

SF104A_MotCurrRegCfg/MotInduQaxEstimd

SF104A_MotCurrRegCfg/MotREstimd

SF104A_MotCurrRegCfg/MotVelMrf

SF104A_MotCurrRegCfg/VehSpd

SF104A_MotCurrRegCfg/IvtrLoaMtgtnEna

SF104A_MotCurrRegCfg/CurrMeasLoaMtgtnEna

SF104A_MotCurrRegCfg/MotCurrEolCalSt

SF104A_MotCurrRegCfg/DualEcuMotCtrlMtgtnEna

Modeling Guidelines for MISRA-C:2004

Check for blocks not recommended for MISRA-C:2004 compliance

Not Run

Check configuration parameters for MISRA-C:2004 compliance

Not Run

Modeling Physical Systems

Check consistency of block parameter units

Not Run

Modeling Signals and Parameters using Buses

Check for optimal bus virtuality

Passed

Check for partial structure parameter usage with bus signals

Not Run

Identify questionable operations for strict single-precision design

Not Run

Modeling Single-Precision Systems

Not Run

Modeling Standards for DO-178C/DO-331

Display model version information

Not Run

Check for blocks that do not link to requirements

Not Run

Check usage of Math blocks

Not Run

Check usage of lookup table blocks

Not Run

Check for blocks that have constraints on tunable parameters

Not Run

Check for Discrete-Time Integrator blocks with initial condition uncertainty

Not Run

Check for model reference configuration mismatch

Not Run

Check for parameter tunability information ignored for referenced models

Not Run

Check for potentially delayed function-call block return values

Not Run

Check model for known block upgrade issues

Not Run

Check root model Inport block specifications

Not Run

Check sample times and tasking mode

Not Run

Check solver for code generation

Not Run

Check the hardware implementation

Not Run

Identify disabled library links

Not Run

Identify parameterized library links

Not Run

Identify unresolved library links

Not Run

Check for blocks not recommended for C/C++ production code deployment

Not Run

Check Merge block usage

Not Run

Not Run

Identify questionable subsystem settings

Not Run

Identify unconnected lines, input ports, and output ports

Not Run

Identify requirement links that specify invalid locations within documents

Not Run

Identify requirement links with missing documents

Not Run

Identify requirement links with path type inconsistent with preferences

Not Run

Identify selection-based links having description fields that do not match their requirements document text

Not Run

Check use of tunable parameters in blocks

Not Run

Check for Strong Data Typing with Simulink I/O

Not Run

Check Stateflow data objects with local scope

Not Run

Check usage of exclusive and default states in state machines

Not Run

Check Stateflow charts for ordering of states and transitions

Not Run

Not Run

Check Stateflow debugging options

Not Run

Check Stateflow charts for uniquely defined data objects

Not Run

Not Run

Not Run

Not Run

Not Run

Check for MATLAB Function block interfaces with inherited properties

Not Run

Not Run

Not Run

Modeling Standards for EN 50128

Not Run

Not Run

Not Run

Check for root Inports with missing range definitions

Not Run

Not Run

Check for root Outports with missing range definitions

Not Run

Check for blocks not recommended for C/C++ production code deployment

Not Run

Not Run

Not Run

Not Run

Not Run

Not Run

Not Run

Check for model objects that do not link to requirements

Not Run

Not Run

Check for MATLAB Function block interfaces with inherited properties

Not Run

Not Run

Modeling Standards for IEC 61508

Not Run

Not Run

Not Run

Check for root Inports with missing range definitions

Not Run

Not Run

Check for root Outports with missing range definitions

Not Run

Check for blocks not recommended for C/C++ production code deployment

Not Run

Not Run

Not Run

Not Run

Not Run

Not Run

Not Run

Check for model objects that do not link to requirements

Not Run

Not Run

Check for MATLAB Function block interfaces with inherited properties

Not Run

Not Run

Modeling Standards for ISO 26262

Not Run

Display number of elements and name, level, and depth of subsystems for the model or subsystem

Model metrics information
Display number of elements for Simulink blocks and Stateflow constructs

Summary

Element Type	Count
Inport	93
Outport	86
SubSystem	53

Simulink

Block Type	Count
Inport	93
Outport	86
Constant	81
SubSystem	53
S-Function	22
Product	20
Merge	14
From	10
Math	8
Width	8
Sum	7
ActionPort	6
SignalConversion	6
Goto	5
DataTypeConversion	5
DataStoreWrite	4
Selector	4
UnaryMinus	4
If	3
EnablePort	2
DataStoreMemory	2
TriggerPort	2
Step	2
DataStoreRead	1
Abs	1
Logic	1
RelationalOperator	1

∧ Less

Model complexity information
Display name, level, and depth of subsystems

Maximum Subsystem Depth: 8

Subsystem Depth

Subsystem Name	Level	Depth
CopyRight2	1	1
Enabled Subsystem	1	1
Enabled Subsystem1	1	1
MotCurrRegCfg	1	7
MotCurrRegCfg/CopyRight2	2	1
MotCurrRegCfg/MotCurrRegCfgInit1	2	2
MotCurrRegCfg/MotCurrRegCfgInit1/CopyRight2	3	1
MotCurrRegCfg/MotCurrRegCfgInit1/FilLpInit	3	1
MotCurrRegCfg/MotCurrRegCfgPer1	2	6
MotCurrRegCfg/MotCurrRegCfgPer1/2nd_Order_Damping_Terms	3	2
MotCurrRegCfg/MotCurrRegCfgPer1/2nd_Order_Damping_Terms/CopyRight2	4	1
MotCurrRegCfg/MotCurrRegCfgPer1/2nd_Order_Damping_Terms/LimStat_f1	4	1
MotCurrRegCfg/MotCurrRegCfgPer1/2nd_Order_Damping_Terms/LimStat_f32	4	1
MotCurrRegCfg/MotCurrRegCfgPer1/Calc MotAgElecDly	3	2
MotCurrRegCfg/MotCurrRegCfgPer1/Calc MotAgElecDly/CopyRight2	4	1
MotCurrRegCfg/MotCurrRegCfgPer1/Calc MotAgElecDly/LimStat_f32	4	1
MotCurrRegCfg/MotCurrRegCfgPer1/CopyRight2	3	1
MotCurrRegCfg/MotCurrRegCfgPer1/FilLpUpdOutp	3	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling	3	5
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/CopyRight2	4	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Enumerated Constant	4	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled	4	4
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Calculate_Gains	5	3
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Calculate_Gains/2nd Order Disabled	6	2
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Calculate_Gains/2nd Order Disabled/CopyRight2	7	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Calculate_Gains/2nd Order Enabled	6	2
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Calculate_Gains/2nd Order Enabled/CopyRight2	7	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Calculate_Gains/CopyRight2	6	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/CopyRight2	5	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/FixdToFloat_f32_u1	5	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/FixdToFloat_f32_u16	5	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/FixdToFloat_f32_u2	5	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/FixdToFloat_f32_u3	5	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/LimStat_f1	5	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/LimStat_f2	5	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/LimStat_f3	5	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/LimStat_f32	5	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Use_Lookup_Table	5	2
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Use_Lookup_Table/CopyRight2	6	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Use_Lookup_Table/FloatToFixd_u16_f32	6	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Use_Lookup_Table/LnrIntrpn_u16_u16VariXu16VariY	6	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Use_Lookup_Table/LnrIntrpn_u16_u16VariXu16VariY1	6	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Use_Lookup_Table/LnrIntrpn_u16_u16VariXu16VariY2	6	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Use_Lookup_Table/LnrIntrpn_u16_u16VariXu16VariY3	6	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Use_Max	5	2
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_ Enabled/Use_Max/CopyRight2	6	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_Disabled	4	2
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/Feedback_Control_Disabled/CopyRight2	5	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/LimStat_f1	4	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/LimStat_f2	4	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/LimStat_f3	4	1
MotCurrRegCfg/MotCurrRegCfgPer1/PI_Gain_Scheduling/LimStat_f32	4	1

∧ Less

Identify unconnected lines, input ports, and output ports in the model

Passed
There are no unconnected lines, input ports, and output ports in this model.

Check for root Inports with missing range definitions

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	SF104A_MotCurrRegCfg/MotInduDaxEstimd	Missing port dimension Missing signal data type Missing port sample time
2	SF104A_MotCurrRegCfg/MotInduQaxEstimd	Missing port dimension Missing signal data type Missing port sample time
3	SF104A_MotCurrRegCfg/MotREstimd	Missing port dimension Missing signal data type Missing port sample time
4	SF104A_MotCurrRegCfg/MotVelMrf	Missing port dimension Missing signal data type Missing port sample time
5	SF104A_MotCurrRegCfg/VehSpd	Missing port dimension Missing signal data type Missing port sample time
6	SF104A_MotCurrRegCfg/IvtrLoaMtgtnEna	Missing port dimension Missing signal data type Missing port sample time
7	SF104A_MotCurrRegCfg/CurrMeasLoaMtgtnEna	Missing port dimension Missing signal data type Missing port sample time
8	SF104A_MotCurrRegCfg/MotCurrEolCalSt	Missing port dimension Missing signal data type Missing port sample time
9	..../DualEcuMotCtrlMtgtnEna	Missing port dimension Missing signal data type Missing port sample time

Missing port dimension: Model contains Inport blocks with inherited port dimension (-1). Specify port dimension for the listed Inport blocks.
Missing signal data type: Model contains Inport blocks with inherited data type. Specify a data type for the listed Inport blocks.
Missing port sample time: Model contains Inport blocks with inherited sample time (-1). Specify sample time information for the listed Inport blocks. Note: The sample time of root Inports with bus type must match the sample times specified at the leaf elements of the bus object.

Not Run

Check for root Outports with missing range definitions

Not Run

Check for blocks not recommended for C/C++ production code deployment

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
SF104A_MotCurrRegCfg/Step	Step	Yes	No
SF104A_MotCurrRegCfg/Step1	Step	Yes	No

Not Run

Compares the state machine type of all Stateflow charts to the desired type.

Passed
The model does not contain Stateflow charts.

Input Parameters Selection

Name	Value
State Machine Type	Common

Not Run

Not Run

Not Run

Not Run

Check for model objects that do not link to requirements

Check consistent usage of vector indexing methods across the model or subsystem

Passed
All the blocks in the model use 'one-based' vector indexing.

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:

∧ Less
Recommended Action
For each object in the list, in the Model Editor, right-click the block, select Requirements, and specify a requirement.

Check for MATLAB Function block interfaces with inherited properties

Not Run

Check character usage in signal labels

Not Run

Modeling Standards for MAAB

Naming Conventions

Check file names

Identify file names with incorrect characters or formatting.

See Also

MathWorks Automotive Advisory Board Guideline: ar_0001

Passed
All files have correct names.

Check folder names

Identify folders using incorrect characters and formatting.

See Also

MathWorks Automotive Advisory Board Guideline: ar_0002

Passed
All folder names have correct formatting.

Check subsystem names

Identify subsystem names that use characters that are not correct in C code.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0201

Warning
The following subsystem names contain incorrect characters:

Error	Subsystem block
Name contains incorrect characters.	SF104A_MotCurrRegCfg/Enabled Subsystem
Name contains incorrect characters.	SF104A_MotCurrRegCfg/Enabled Subsystem1
Name contains incorrect characters.	..../Feedback_Control_ Enabled
Name starts with a number [0123456789].	..../Calculate_Gains/2nd Order Disabled
Name starts with a number [0123456789].	..../Calculate_Gains/2nd Order Enabled

Recommended Action
Rename the subsystem blocks using correct characters.

Check port block names

Identify names of Inport or Outport blocks that use characters that are not correct in C code.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0211

Passed
All the Inport or Outport block names use correct characters.

Identify signal labels that are not correct for C variable names.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0221

Passed
All signal labels use correct characters.

Check character usage in block names

Identify block names that use characters that are not correct in C code.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0231

Warning
The following block names use characters that are not correct for C code:

Error type	Block
Name contains incorrect characters.	..../Function-Call Generator
Name contains incorrect characters.	..../Function-Call Generator

Recommended Action
Rename the block using correct characters.

Model Architecture

Check for mixing basic blocks and subsystems

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

MathWorks Automotive Advisory Board Guideline: db_0143

Warning
The following level(s) in the model include basic blocks and subsystems:

System	Block path
SF104A_MotCurrRegCfg	SF104A_MotCurrRegCfg/CopyRight2
SF104A_MotCurrRegCfg	SF104A_MotCurrRegCfg/Step
SF104A_MotCurrRegCfg	SF104A_MotCurrRegCfg/Step1
SF104A_MotCurrRegCfg/MotCurrRegCfg	..../MotCurrRegCfg/CopyRight2
..../MotCurrRegCfg/MotCurrRegCfgPer1	..../MotCurrRegCfgPer1/CopyRight2
..../MotCurrRegCfg/MotCurrRegCfgPer1	..../MotCurrRegCfgPer1/Data Store Write
..../MotCurrRegCfg/MotCurrRegCfgPer1	..../MotCurrRegCfgPer1/FilLpUpdOutp
..../MotCurrRegCfgPer1/PI_Gain_Scheduling	..../PI_Gain_Scheduling/Constant
..../MotCurrRegCfgPer1/PI_Gain_Scheduling	..../PI_Gain_Scheduling/Constant1
..../MotCurrRegCfgPer1/PI_Gain_Scheduling	..../PI_Gain_Scheduling/CopyRight2
..../MotCurrRegCfgPer1/PI_Gain_Scheduling	..../PI_Gain_Scheduling/Enumerated Constant
..../MotCurrRegCfgPer1/PI_Gain_Scheduling	..../PI_Gain_Scheduling/LimStat_f1
..../MotCurrRegCfgPer1/PI_Gain_Scheduling	..../PI_Gain_Scheduling/LimStat_f2
..../MotCurrRegCfgPer1/PI_Gain_Scheduling	..../PI_Gain_Scheduling/LimStat_f3
..../MotCurrRegCfgPer1/PI_Gain_Scheduling	..../PI_Gain_Scheduling/LimStat_f32
..../MotCurrRegCfgPer1/PI_Gain_Scheduling	..../PI_Gain_Scheduling/Logical Operator
..../MotCurrRegCfgPer1/PI_Gain_Scheduling	..../PI_Gain_Scheduling/Relational Operator
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/Constant
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/Constant2
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/Constant3
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/Constant4
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/Constant5
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/Constant6
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/Constant7
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/CopyRight2
..../Feedback_Control_ Enabled	..../FixdToFloat_f32_u1
..../Feedback_Control_ Enabled	..../FixdToFloat_f32_u16
..../Feedback_Control_ Enabled	..../FixdToFloat_f32_u2
..../Feedback_Control_ Enabled	..../FixdToFloat_f32_u3
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/LimStat_f1
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/LimStat_f2
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/LimStat_f3
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/LimStat_f32
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/Product
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/Product1
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/SizeOf_1
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/SizeOf_2
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/SizeOf_3
..../Feedback_Control_ Enabled	..../Feedback_Control_ Enabled/SizeOf_4
..../Calculate_Gains	..../Calculate_Gains/Constant
..../Calculate_Gains	..../Calculate_Gains/CopyRight2

∧ Less

Recommended Action
If possible, replace blocks at the identified level of the model hierarchy with basic blocks. Move nonvirtual blocks into the identified subsystem.

Model Configuration Options

Check Implement logic signals as Boolean data (vs. double)

Identify whether Implement logic signals as Boolean data (vs. double) is selected.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0011

Passed
Implement logic signals as Boolean data (vs. double) is selected.

Check model diagnostic parameters

Identify diagnostic parameters that are set to none.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0021

Passed
All of the diagnostic parameters are set to error or warning.

Simulink

Check for Simulink diagrams using nonstandard display attributes

Identify nonstandard display attributes in Simulink diagrams.

See Also

MathWorks Automotive Advisory Board Guideline: na_0004

_________________________________________________________________________________________

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

Recommended Action
Set the format options to the recommended value.
_________________________________________________________________________________________

Check block colors
Identify blocks using nonstandard colors.

Warning
The following blocks use nonstandard colors:

Recommended Action
Set the block foreground color to black and the background color to white.
_________________________________________________________________________________________

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:

∧ Less
Recommended Action
For each listed diagram, select View > Zoom > Normal View (100%).

Check font formatting

Identify inconsistent formatting of text.

See Also

MathWorks Automotive Advisory Board Guideline: db_0043

Warning
Font formatting is not consistent.

The following font characteristics are used in the model/subsystem. Font characteristics are sorted by number of occurrences. The most common characteristics are bold.

Font Name	Font Size	Font Style
Helvetica Arial	10 14 9	normal

Recommended Action
To have consistent font formatting, click Modify All Fonts to apply the font formatting selected in the input parameters above to all objects.

Input Parameters Selection

Name	Value
Font Name	Common
Font Size	Common
Font Style	Common

Check positioning and configuration of ports

Identify input and output ports with incorrect positioning and configurations.

See Also

MathWorks Automotive Advisory Board Guideline: db_0042

_________________________________________________________________________________________

Check Inport blocks position
Identify Inport blocks that result in left-flowing signals.

Passed
There are no Inport blocks in the model that result in left-flowing signals.
_________________________________________________________________________________________

Check Outport block position
Identify Outport blocks that result in left-flowing signals.

Passed
There are no Outport blocks in the model that result in left-flowing signals.
_________________________________________________________________________________________

Check port orientation
Identify port blocks with nondefault orientation.

Passed
All ports use the default orientation.
_________________________________________________________________________________________

Check for duplicate Inports blocks
Identify duplicate Inport blocks.

Passed
All Inport blocks in the model are used once.

Check visibility of block port names

Identify port block names that are not uniformly displayed. The block names must all be displayed or none displayed. Library blocks are an exception to this rule. This check ignores masked and subsystem blocks.

See Also

MathWorks Automotive Advisory Board Guideline: na_0005

_________________________________________________________________________________________

Check for incorrect port name display
Identify ports that are incorrectly displaying names.

Passed
Subsystem blocks are correctly displayed.
_________________________________________________________________________________________

Check for incorrect subsystem port name display
Identify subsystems that are incorrectly displaying names.

Passed
Subsystem blocks are correctly displayed.

Input Parameters Selection

Name	Value
Display all port names (Diagram > Format > Show Block Name).	true

Check display for port blocks

Identify Inport and Outport blocks that do not specify Port number for the Icon display block parameter.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0081

Passed
All port blocks display the port number.

Check whether block names appear below blocks

Not Run

Check the display attributes of block names

Identify whether to display block names.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0061

_________________________________________________________________________________________

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:

Recommended Action
Modify the block name to provide descriptive information, or hide the block name by deselecting (Diagram > Format > Show Block Name).
_________________________________________________________________________________________

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:

∧ Less
Recommended Action
Modify the blocks to show the block name (Diagram > Format > Show Block Name).

Check position of Trigger and Enable blocks

Identify Trigger and Enable blocks that are not centered in the upper third of the model diagram.

See Also

MathWorks Automotive Advisory Board Guideline: db_0146

Passed
The model does not contain Trigger and Enable blocks, or the blocks are in the upper third of the model diagram.

Check for nondefault block attributes

Identify blocks that use and fail to display nondefault values.

See Also

MathWorks Automotive Advisory Board Guideline: db_0140

Passed
Model displays all block parameter values that are not default values.

Check for matching port and signal names

Not Run

Check Trigger and Enable block names

Not Run

Check signal line labels

Identify blocks that require labeled signals. A subset of source and destination blocks require labeled signals.

See Also

MathWorks Automotive Advisory Board Guideline: na_0008

_________________________________________________________________________________________

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:

∧ Less
Recommended Action
Add a new or propagated label to the signal line.
_________________________________________________________________________________________

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:

∧ Less
Recommended Action
Add a new or propagated label to the signal line.

Check for propagated signal labels

Identify propagated labels on signal lines.

See Also

MathWorks Automotive Advisory Board Guideline: na_0009

_________________________________________________________________________________________

Check subsystem input labels
Identify subsystem inputs that are labeled and display propagated signals.

Passed
All inputs to the subsystem have labels and display propagated signals.
_________________________________________________________________________________________

Check subsystem output labels
Identify outputs from subsystems that are labeled and display signal propagation.

Passed
All outputs from the subsystem have labels and display propagated signals.
_________________________________________________________________________________________

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.

Check for unconnected ports and signal lines

Identify unconnected block input ports, output ports, and signal lines.

See Also

MathWorks Automotive Advisory Board Guideline: db_0081

Passed
All lines and ports in the model are connected.

Check for prohibited blocks in discrete controllers

Identify blocks that are not allowed in discrete controllers. Prohibited blocks include all continuous blocks and some source and sink blocks.

See Also

Passed
All blocks in the model are allowed in discrete controllers.

Check for blocks not recommended for C/C++ production code deployment

Block	Block Type	Code generation support	Recommendation for C/C++ production code deployment
SF104A_MotCurrRegCfg/Step	Step	Yes	No
SF104A_MotCurrRegCfg/Step1	Step	Yes	No

Check for prohibited sink blocks

Identify sink blocks that must be removed prior to code generation.

See Also

MathWorks Automotive Advisory Board Guideline: hd_0001

Passed
There are no prohibited blocks in the subsystem.

Check scope of From and Goto blocks

Identify incorrect scoping of From and Goto blocks. For signal flows, From and Goto blocks must use local scope. Control flow can use global scope.

See Also

MathWorks Automotive Advisory Board Guideline: na_0011

Passed
All From and Goto blocks are used correctly.

Check use of Switch blocks

Not Run

Check configuration of Relational Operator blocks

Not Run

Check for indexing in blocks

Identify blocks that use zero-based indexing.

See Also

MathWorks Automotive Advisory Board Guideline: db_0112

Passed
All blocks in the system are configured to use one-based indexing.

Check for signal bus and Mux block usage

Not Run

Check use of tunable parameters in blocks

Identify tunable parameters used to specify expressions, data type conversions, or indexing operations.

See Also

MathWorks Automotive Advisory Board Guideline: db_0110

Passed
Tunable parameters are not used in the model.

Check orientation of Subsystem blocks

Not Run

Stateflow

Check usage of exclusive and default states in state machines

Identify Stateflow charts and substates that incorrectly use or define exclusive and default states.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: db_0137

_________________________________________________________________________________________

Check Stateflow charts for exclusive states
Identify Stateflow charts that have singular exclusive (OR) states.

Passed
The Stateflow charts do not have singular exclusive (OR) states.
_________________________________________________________________________________________

Check Stateflow charts for undefined default states
Identify Stateflow charts that do not define default states.

Passed
Each Stateflow chart defines a default state.
_________________________________________________________________________________________

Check for multiple states assigned as the default state
At the root level in the Stateflow hierarchy only one state should be assigned as the default.

Passed
The root level of the chart has only one default state assigned.
_________________________________________________________________________________________

Check for substates with singular OR states
States configured as OR should always be part of a group of states.

Passed
No singular OR states were detected.
_________________________________________________________________________________________

Check for substates without default states defined
At every level in the Stateflow hierarchy a default state should be assigned.

Passed
All substates have default states assigned.
_________________________________________________________________________________________

Check for substates with multiple default states defined
At every level in the Stateflow hierarchy only one state should be assigned as the default.

Passed
All levels of the chart have only one default state assigned.

Check transition orientations in flowcharts

Identify transitions in Stateflow flowcharts that are drawn incorrectly.

See Also

MathWorks Automotive Advisory Board Guideline: db_0132

_________________________________________________________________________________________

Check for conditions drawn vertically
Condition expressions should be drawn on the horizontal segments of flowcharts.

Passed
All conditions expressions were drawn horizontally.
_________________________________________________________________________________________

Check for action transitions drawn vertically
Transition actions should be drawn on the vertical segments of flowcharts.

Passed
All transitions actions where drawn vertically.
_________________________________________________________________________________________

Check for junctions for default transitions
All Junctions in a flow chart should have a default exit transition.

Passed
All Junctions 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.

Passed
No combined expressions where found in the chart.

Check entry formatting in State blocks in Stateflow charts

Identify missing line breaks between entry action (en), during action (du), and exit action (ex) entries in states. Identify missing line breaks after semicolons (;) in statements.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0501

Passed
No Stateflow charts were found.

Check return value assignments of graphical functions in Stateflow charts

Identify graphical functions with multiple assignments of return values in Stateflow charts.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0511

Passed
No Stateflow charts were found.

Check default transition placement in Stateflow charts

Identify all groupings of states that do not have a default transition or do not have the default state as the top-most state.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0531

Passed
No Stateflow charts were found.

Check for Strong Data Typing with Simulink I/O

Identify whether Stateflow charts have Use Strong Data Typing with Simulink I/O cleared.

See Also

MathWorks Automotive Advisory Board Guideline: db_0122

Passed
No Stateflow charts were found.

Check Stateflow data objects with local scope

Identify Stateflow data objects with local scope that are not scoped at the chart level or below.

See Also

MathWorks Automotive Advisory Board Guideline: db_0125

Passed
No Stateflow charts were found.

Check usage of return values from a graphical function in Stateflow charts

Identify calls to graphical functions that are used in conditional expressions.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0521

Passed
No conditional expressions containing calls to graphical functions were found.

Check for MATLAB expressions in Stateflow charts

Identify Stateflow objects that use MATLAB expressions that are not suitable for code generation.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: db_0127

Passed
No Stateflow objects that use MATLAB expressions were found.

Check for pointers in Stateflow charts

Identify pointer operations on custom code variables.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: jm_0011

Passed
No pointer operations were found.

Check for event broadcasts in Stateflow charts

Identify undirected event broadcasts that might cause recursion during simulation and generate inefficient code.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: jm_0012

Passed
No instances of undirected event broadcast were found.

Check transition actions in Stateflow charts

Identify missing line breaks between transition actions.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: db_0151

Passed
All transition actions are formatted correctly.

Check for bitwise operations in Stateflow charts

Not Run

Check for unary minus operations on unsigned integers in Stateflow charts

Not Run

Check for comparison operations in Stateflow charts

Not Run

Check for equality operations between floating-point expressions in Stateflow charts

Not Run

Check for mismatches between names of Stateflow ports and associated signals

Not Run

MATLAB Functions

Check input and output settings of MATLAB Function blocks

Not Run